On Mon, Jan 30, 2023 at 12:59 PM Georgi Naplatanov wrote:
> On 1/28/23 12:04, Timothy M Butterworth wrote:
> > All,
> >
> > I just upgraded to the 1/28/23 updates to KF5 102 and now I have no
> > audio devices found. My USB headset is plugged in but KDE does not see
&
On 1/28/23 12:04, Timothy M Butterworth wrote:
All,
I just upgraded to the 1/28/23 updates to KF5 102 and now I have no
audio devices found. My USB headset is plugged in but KDE does not see it.
lsusb lists my USB headphones:
Bus 001 Device 009: ID 046d:0a37 Logitech, Inc. USB Headset H540
On Sun, Jan 29, 2023 at 12:59 PM Brad Rogers wrote:
> On Sun, 29 Jan 2023 12:11:33 -0500
> Timothy M Butterworth wrote:
>
> Hello Timothy,
>
> >I did not try a new user. I did try deleting "~/.config/pulseaudio"
>
> Sorry to say, I've reached the limit of my knowledge on the subject.
> :-(
>
> -
On Sun, 29 Jan 2023 12:11:33 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>I did not try a new user. I did try deleting "~/.config/pulseaudio"
Sorry to say, I've reached the limit of my knowledge on the subject.
:-(
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
On Sun, Jan 29, 2023 at 12:11 PM Timothy M Butterworth <
timothy.m.butterwo...@gmail.com> wrote:
>
>
> On Sun, Jan 29, 2023 at 7:55 AM Brad Rogers wrote:
>
>> On Sun, 29 Jan 2023 07:22:02 -0500
>> Timothy M Butterworth wrote:
>>
>> Hello Timothy,
>>
>> >I upgraded to 5.27beta so far no new issue
On Sun, Jan 29, 2023 at 7:55 AM Brad Rogers wrote:
> On Sun, 29 Jan 2023 07:22:02 -0500
> Timothy M Butterworth wrote:
>
> Hello Timothy,
>
> >I upgraded to 5.27beta so far no new issues. I just installed Wayland
>
> Good to know. Thanks for the info.
>
> >so I can try it out. My sound cards ar
On Sun, 29 Jan 2023 07:22:02 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>I upgraded to 5.27beta so far no new issues. I just installed Wayland
Good to know. Thanks for the info.
>so I can try it out. My sound cards are still not working though.
Have you tried;
(a) checking volume lev
On Sun, Jan 29, 2023 at 5:19 AM Brad Rogers wrote:
> On Sat, 28 Jan 2023 10:41:38 -0500
> Timothy M Butterworth wrote:
>
> Hello Timothy,
>
> >I am looking forward to 5.27beta! It has a lot of good improvements.
>
> As I suggested, the migration to testing has started today. I'm holding
> off f
On Sat, 28 Jan 2023 10:41:38 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>I am looking forward to 5.27beta! It has a lot of good improvements.
As I suggested, the migration to testing has started today. I'm holding
off for a few days to be sure (well, as sure as I can be) that
everything
On Sat, Jan 28, 2023 at 7:50 AM Brad Rogers wrote:
> On Sat, 28 Jan 2023 05:04:59 -0500
> Timothy M Butterworth wrote:
>
> Hello Timothy,
>
> >This appears to be a KDE issue. Is anyone else having this problem?
> >Please note the problem started after installing KF5-102 and a reboot.
>
> KDE Pla
On Sat, 28 Jan 2023 05:04:59 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>This appears to be a KDE issue. Is anyone else having this problem?
>Please note the problem started after installing KF5-102 and a reboot.
KDE Plasma is undergoing big changes ATM. Soon(1) Plasma 5.27beta
(2) will
On Sat, 28 Jan 2023 07:37:01 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>I forgot to mention that I am using Bookworm.
It *was* in the subject header. :-)
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately
On Sat, Jan 28, 2023 at 5:04 AM Timothy M Butterworth <
timothy.m.butterwo...@gmail.com> wrote:
> All,
>
> I just upgraded to the 1/28/23 updates to KF5 102 and now I have no audio
> devices found. My USB headset is plugged in but KDE does not see it.
>
I forgot to me
All,
I just upgraded to the 1/28/23 updates to KF5 102 and now I have no audio
devices found. My USB headset is plugged in but KDE does not see it.
lsusb lists my USB headphones:
Bus 001 Device 009: ID 046d:0a37 Logitech, Inc. USB Headset H540
lspci lists my audio devices
04:00.5 Multimedia
From: David Wright
Date: Wed, 29 Sep 2021 22:35:11 -0500
> ... your case is like playing it later by pressing a key.
Acknowledged.
> As for the gain, you might always start at some default, but it would
> surely be useful to be able to adjust it for mumblers and shouters
> while it was p
On Wed 29 Sep 2021 at 12:25:49 (-0700), pe...@easthope.ca wrote:
> From: David Wright
> Date: Tue, 28 Sep 2021 18:31:34 -0500
> > No, you'd use alsamixer where you were taking an active rôle during
> > record/playback, or for discovering, inspecting and setting up a
> > system. Typically,
From: David Wright
Date: Tue, 28 Sep 2021 18:31:34 -0500
> sox /home/peter/a42.WAV -t alsa default
OK, good.
I can replace the PCI sound card. Then that or the system board
hardware will be the default.
How can a non-default device be specified?
Conceptually,
sox /home/peter/a42.WAV
Trimmed the reference list. =8~)
From: David Wright
Date: Tue, 28 Sep 2021 18:31:34 -0500
> No, you'd use alsamixer where you were taking an active rôle during
> record/playback, or for discovering, inspecting and setting up a
> system. Typically, you'd play "an audio message", or anyth
On Wed, 29 Sept 2021 at 16:57, wrote:
> On Tue, Sep 28, 2021 at 02:31:18PM -0700, pe...@easthope.ca wrote:
> > I haven't set a shell. According to https://wiki.debian.org/Shell
> > it's bash.
> It might be willing to tell you:
> echo $SHELL
I wouldn't give that advice, it's rather misleading
On Tue, Sep 28, 2021 at 02:31:18PM -0700, pe...@easthope.ca wrote:
> From: Greg Wooledge
> Date: Tue, 28 Sep 2021 13:32:02 -0400
> > Are you in csh/tcsh?
>
> I haven't set a shell. According to https://wiki.debian.org/Shell
> it's bash.
It might be willing to tell you:
echo $SHELL
On Tue 28 Sep 2021 at 13:49:37 (-0700), pe...@easthope.ca wrote:
> From: ghe2001
> Date: Tue, 28 Sep 2021 17:24:57 +
> > Try alsamixer. You can select the audio device there. It works for my
>
> >From the alsamixer manual,
> "DESCRIPTION
>alsamixer is an ncurses mixer progr
On Tue, Sep 28, 2021 at 02:31:18PM -0700, pe...@easthope.ca wrote:
> From: Greg Wooledge
> Date: Tue, 28 Sep 2021 13:32:02 -0400
> > Are you in csh/tcsh?
>
> I haven't set a shell. According to https://wiki.debian.org/Shell
> it's bash.
Do not guess. Do not assume defaults are in pla
From: Greg Wooledge
Date: Tue, 28 Sep 2021 13:32:02 -0400
> Are you in csh/tcsh?
I haven't set a shell. According to https://wiki.debian.org/Shell
it's bash.
> If you're in a more "normal" shell (bash or zsh),
> that set command doesn't do anything useful. Certainly nothing that
> wo
From: ghe2001
Date: Tue, 28 Sep 2021 17:24:57 +
> Try alsamixer. You can select the audio device there. It works for my
Thanks.
>From the alsamixer manual,
"DESCRIPTION
alsamixer is an ncurses mixer program for use with the ALSA soundcard
drivers. It supports multi
I've reordered this reply to get rid of top posting...
On Tue, 2021-09-28 at 17:38 +, Nils wrote:
> Am 28. September 2021 19:32:02 MESZ schrieb Greg Wooledge <
> g...@wooledge.org>:
> > On Tue, Sep 28, 2021 at 08:19:26AM -0700, pe...@easthope.ca wrote:
> > > > CONCLUSIONS
> > > >
> > > > Audi
I agree. In the "normal" shells, you need to use "export" instead of "set"!
Am 28. September 2021 19:32:02 MESZ schrieb Greg Wooledge :
>On Tue, Sep 28, 2021 at 08:19:26AM -0700, pe...@easthope.ca wrote:
>> > CONCLUSIONS
>> >
>> > Audio messages can be interpreted. Eg.,
>> > set AUDIODEV=plughw:
On Tue, Sep 28, 2021 at 08:19:26AM -0700, pe...@easthope.ca wrote:
> > CONCLUSIONS
> >
> > Audio messages can be interpreted. Eg.,
> > set AUDIODEV=plughw:CARD=ICH5,DEV=0; play m94.WAV
>
> Hasty reply. In further use, didn't always work. I removed the PCI
> sound card, removed the plastic cov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
‐‐‐ Original Message ‐‐‐
On Tuesday, September 28, 2021 9:19 AM, wrote:
> From:pe...@easthope.ca
> Date: Sat, 31 Jul 2021 09:52:21 -0700
>
> > In spite of the warning, sound is produced. Good! Might have a
> > reliable way to hear voice m
From: pe...@easthope.ca
Date: Sat, 31 Jul 2021 09:52:21 -0700
> In spite of the warning, sound is produced. Good! Might have a
> reliable way to hear voice messages.
>
> CONCLUSIONS
>
> Audio messages can be interpreted. Eg.,
> set AUDIODEV=plughw:CARD=ICH5,DEV=0; play m94.WAV
Hasty
The Subject of my preceding message was a blunder.
System board and PCI sound hardware
From: pe...@easthope.ca
Date: Thu, 29 Jul 2021 20:20:16 -0700
> Got sound from the Intel device on the system board. Oddly enough
> there was a plastic cover over the sockets on the chassis back. Pr
From: Reco
Date: Fri, 30 Jul 2021 19:37:49 +0300
> Aha. So, will this work?
> aplay -d dmix:CARD=Set,DEV=0 /usr/share/sounds/alsa/Noise.wav
peter@joule:/home/peter$ aplay -d dmix:CARD=Set,DEV=0
/usr/share/sounds/alsa/Noise.wav
aplay: main:653: invalid duration argument 'dmix:CARD=Set,DEV
On Fri, Jul 30, 2021 at 05:55:43AM -0700, pe...@easthope.ca wrote:
> From: Reco
> Date: Fri, 30 Jul 2021 08:56:04 +0300
> > You could've started a new thread as well.
>
> For sure at least one reader would think "#$%&*, there he goes; another
> thread broken!"
Broken threads are usual
From: Reco
Date: Fri, 30 Jul 2021 08:56:04 +0300
> You could've started a new thread as well.
For sure at least one reader would think "#$%&*, there he goes; another thread
broken!"
> aplay -L
> arecord -L
peter@joule:/home/peter$ aplay -L
null
Discard all samples (playback) or ge
Hi.
On Thu, Jul 29, 2021 at 08:20:16PM -0700, pe...@easthope.ca wrote:
> From: Reco , Sun, 20 Oct 2019 20:57:52 +0300
> > So, does it work?
>
> Got sound from the Intel device on the system board. Oddly enough
> there was a plastic cover over the sockets on the chassis back. Pried
> i
From: Reco , Sun, 20 Oct 2019 20:57:52 +0300
> So, does it work?
Got sound from the Intel device on the system board. Oddly enough
there was a plastic cover over the sockets on the chassis back. Pried
it off to plug the speaker jack.
Here is some further info.
Read https://wiki.debian.org/
From: Reco , Sun, 20 Oct 2019 20:57:52 +0300
> So, does it work?
Yes. At present dmix:CARD=Live,DEV=0 produces sound.
dmix:CARD=Live,DEV=1
and
dmix:CARD=Live,DEV=2
do not produce sound at present.
> Try hw:CARD=Set,DEV=1.
Will be trying it this week. Thanks.
> The reason why dmix fails y
efer to /proc/asound/Device/.
aplay -l
> > The way I see it, there's no need for these "predictable audio devices
> > names", they are here already.
>
> "dmix:CARD=PCH,DEV=0" could be a name in a hardware manual
> published in 1970.
Yet they are
CARD=Set,DEV=2 play MY/m85.WAV
ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave
play FAIL sox: Sorry, there is no default audio device configured
No option to list _configured_ devices? Maybe refer to /proc/asound/Device/.
> The way I see it, there's no need for these &quo
Peter Easthope wrote:
> Can an audio device be named similarly? Eg. given two USB audio
> adapters how would they be assigned the names "USBheadset" and
> "USBspeakers"?
>
I think it is important to do the proper indexing
/etc/modprobe.d/alsa-base.conf
options snd_hda_intel index=0
options sn
nd the problem that you're trying to solve by such "predictable" audio
devices is?
Reco
systemd provides a sane means to assign a human-chosen persistent name
to a network interface.
https://wiki.debian.org/NetworkInterfaceNames#CUSTOM_SCHEMES_USING_.LINK_FILES
Can an audio device be named similarly? Eg. given two USB audio
adapters how would they be assigned the names "USBheadset"
Hi there.
Suddenly my audio device isn't working. I didn't change anything (well,
not on purpose).
I'm running Debian stretch.
If I click System Settings -> Multimedia -> Audio and Video then I see
something like this:
https://www.jj5.net/file/2017-08-05-220654/disabled-audio-devices.png
Can
On Wed, 05 Oct 2011 17:45:00 +0100, richard2 wrote:
> On Wed, 2011-10-05 at 15:12 +, Camaleón wrote:
(...)
>> > Ie in a jack line:-
>> > $JACKD -R -P 50 -t -d alsa -r 48000 -C hw:M66 -P hw:M66 -n4 -p
>> > 512 -s &
>> >
>> > In debian this just drops to the default card.
>>
>> (...)
>
On Wed, 2011-10-05 at 15:12 +, Camaleón wrote:
> On Wed, 05 Oct 2011 10:54:08 +0100, Richard wrote:
>
> > When I was using Fedora I could set sounds cards by the name shown when
> > either aplay -l or /proc/asound/cards shows
> > 0 [SB ]: HDA-Intel - HDA ATI SB
> >
On Wed, 05 Oct 2011 10:54:08 +0100, Richard wrote:
> When I was using Fedora I could set sounds cards by the name shown when
> either aplay -l or /proc/asound/cards shows
> 0 [SB ]: HDA-Intel - HDA ATI SB
> HDA ATI SB at 0xfe024000 irq 16
> 1 [CX8801 ]: C
Hi
When I was using Fedora I could set sounds cards by the name shown when either
aplay -l or /proc/asound/cards
shows
0 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xfe024000 irq 16
1 [CX8801 ]: CX88x - Conexant CX8801
Conexant CX
st say it and I will look for what I have done age ago!!!
>> I will try to find that out, it should not be a problem. However, how
>> would this play with usb devices that I may connect after booting?
>>
>> Thanks.
>>
>
> Because I guess hald is looking for a
mane.org. Replies sent to my email address are just
> filtered to a folder in my mailbox and get periodically deleted without
> ever having been read.
Because I guess hald is looking for audio devices, and when it find the head
set it stop looking for other things. I got the same problem with
Thierry Chatelet wrote:
>
> You have to blacklist usb sound module. I dont remember how to do that, but
> googling it should give you the answer. If you dont know how to do it, xjust
> say it and I will look for what I have done age ago!!!
>
>
I will try to find that out, it should not be a
Nigel Henry wrote:
>
> Hi.
>
> Try adding the following line to /etc/modprobe.d/alsa-base
>
> options snd-usb-audio index=1
>
> That assumes that your soundcard is card0, and no other cards are using slot1.
Sorry, but what is slot 1? Is it the same as card 0. In other words, is
'card n' in 'sl
On Thursday 15 January 2009 20:39:57 H.S. wrote:
> Hello,
>
> On Debian Lenny and running KDE, I am using an audio card listed as:
> 02:0c.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
>
> and it works fine.
>
> However, if I plug in a headset to the USB port of the computer
> (Micr
On Thursday 15 January 2009 20:39, H.S. wrote:
> Hello,
>
> On Debian Lenny and running KDE, I am using an audio card listed as:
> 02:0c.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
>
> and it works fine.
>
> However, if I plug in a headset to the USB port of the computer
> (Micros
Hello,
On Debian Lenny and running KDE, I am using an audio card listed as:
02:0c.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
and it works fine.
However, if I plug in a headset to the USB port of the computer
(Microsoft LX-3000 in this case, though I don't think it matters) and
On Fri, Nov 21, 2008 at 11:14, H.S. <[EMAIL PROTECTED]> wrote:
> BTW, reading your earlier post I also tried to setup PA ... and it
> worked (aplay -Dpulse foo.wav worked) ! However, from PA's wiki page it
> appears that it doesn't work with audacious yet and neither with
> audacity. I use both.
On Fri,21.Nov.08, 14:14:34, H.S. wrote:
> BTW, reading your earlier post I also tried to setup PA ... and it
> worked (aplay -Dpulse foo.wav worked) ! However, from PA's wiki page it
> appears that it doesn't work with audacious yet and neither with
audacious works (for me at least) with pulse,
Kelly Clowers wrote:
>
> I dug around and found the modinfo command...
>
> $ sudo modinfo sound
> filename: /lib/modules/2.6.26-1-686/kernel/sound/oss/sound.ko
> author: Hannu Savolainen, et al.
> description:OSS Sound subsystem
>
>
> vs.
>
> $ sudo modinfo snd-pcm-oss
> file
On Fri, Nov 21, 2008 at 01:56, Ron Johnson <[EMAIL PROTECTED]> wrote:
> On 11/20/08 23:03, H.S. wrote:
>>
>> Kelly Clowers wrote:
>>>
>>> On Thu, Nov 20, 2008 at 7:58 PM, H.S. <[EMAIL PROTECTED]> wrote:
Ron Johnson wrote:
>
> If your machine runs kernel 2.6, it shouldn't have OSS.
Osamu Aoki wrote:
> Hi,
Hello,
> On Fri, Nov 21, 2008 at 10:39:15AM -0500, H.S. wrote:
>> Kelly Clowers wrote:
> ...
And in KDE's sound configuration gui, one of the
systems to choose from is OSS.
>>> Probably hardwired, and would show up in any case.
> ...
> this does make sense. Ho
Hi,
On Fri, Nov 21, 2008 at 10:39:15AM -0500, H.S. wrote:
> Kelly Clowers wrote:
...
> >> And in KDE's sound configuration gui, one of the
> >> systems to choose from is OSS.
> >
> > Probably hardwired, and would show up in any case.
...
this does make sense. However, if I select OSS from KDE's
Hi,
I agree that if you have modern system (bought new last 5 years or so),
you should be OK with ALSA. But let's be more precise beyond this.
On Fri, Nov 21, 2008 at 03:56:22AM -0600, Ron Johnson wrote:
...
> Given that OSS has been deprecated for FIVE years, and I *VERY STRONGLY*
> doubt that
Kelly Clowers wrote:
>
> I believe that is "provides" in the package dependency sense, and is
> for compatibility and because of alsa oss emulation. AFAIK, oss has
> no userspace component, so nothing would show up in apt.
Yes, that is what first did before starting this thread. It gave
nothing.
On 11/21/08 09:16, H.S. wrote:
Kelly Clowers wrote:
I think you do have it, but I doubt it is in use. You could look at
lsmod output and compare it to the modules in
/lib/modules/2.6.xxx/kernel/sound/oss.
I have a bunch of modules there. I will check if any of those are
loaded. Which brings me
Ron Johnson wrote:
>
> You have linux-sound-base. Well, so do I.
Good. But I recommend another post in this thread which gives useful
information about this.
> But there are only 2 OSS drivers in "recent" (going back to st least
st?
> 2.6.16) kernels, so even though you have linux-sound-bas
Kelly Clowers wrote:
>
> I think you do have it, but I doubt it is in use. You could look at
> lsmod output and compare it to the modules in
> /lib/modules/2.6.xxx/kernel/sound/oss.
I have a bunch of modules there. I will check if any of those are
loaded. Which brings me to this point: check for
On 11/21/08 08:52, H.S. wrote:
Ron Johnson wrote:
Here's a slightly different question: what makes you think that you *do*
have OSS?
Please see my other recent posts.
You have linux-sound-base. Well, so do I.
But there are only 2 OSS drivers in "recent" (going back to st least
2.6.16) ke
Ron Johnson wrote:
>
> Here's a slightly different question: what makes you think that you *do*
> have OSS?
Please see my other recent posts.
--
Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to
On 11/20/08 23:03, H.S. wrote:
Kelly Clowers wrote:
On Thu, Nov 20, 2008 at 7:58 PM, H.S. <[EMAIL PROTECTED]> wrote:
Ron Johnson wrote:
If your machine runs kernel 2.6, it shouldn't have OSS.
lsmod will list your loaded modules. snd_pcm_oss, snd_mixer_oss,
and snd_seq_oss, are all part of t
On Thu, Nov 20, 2008 at 21:03, H.S. <[EMAIL PROTECTED]> wrote:
> Kelly Clowers wrote:
>> On Thu, Nov 20, 2008 at 7:58 PM, H.S. <[EMAIL PROTECTED]> wrote:
>>> Ron Johnson wrote:
If your machine runs kernel 2.6, it shouldn't have OSS.
>
>>
>> lsmod will list your loaded modules. snd_pcm_oss, snd
Kelly Clowers wrote:
> On Thu, Nov 20, 2008 at 7:58 PM, H.S. <[EMAIL PROTECTED]> wrote:
>> Ron Johnson wrote:
>>> If your machine runs kernel 2.6, it shouldn't have OSS.
>
> lsmod will list your loaded modules. snd_pcm_oss, snd_mixer_oss,
> and snd_seq_oss, are all part of the alsa oss emulation.
On Thu, Nov 20, 2008 at 7:58 PM, H.S. <[EMAIL PROTECTED]> wrote:
> Ron Johnson wrote:
>>>
>>> Anyone?
>>
>> If your machine runs kernel 2.6, it shouldn't have OSS.
>>
>
> hmm ... ookay. Does that mean both are orthogonal? And, yes, I am
> running 2.6.
I am not sure that that is true. I think Debia
Ron Johnson wrote:
>>
>> Anyone?
>
> If your machine runs kernel 2.6, it shouldn't have OSS.
>
hmm ... ookay. Does that mean both are orthogonal? And, yes, I am
running 2.6.
--
Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my ema
On 11/20/08 21:29, H.S. wrote:
H.S. wrote:
Ron Johnson wrote:
And can I remove OSS in favor of Alsa?
Yes.
This is what I am most interested in ... how exactly?
Anyone?
If your machine runs kernel 2.6, it shouldn't have OSS.
--
Ron Johnson, Jr.
Jefferson LA USA
If you don't agree wit
H.S. wrote:
> Ron Johnson wrote:
>
>>> And can I remove OSS in favor of Alsa?
>> Yes.
>
> This is what I am most interested in ... how exactly?
>
>
Anyone?
--
Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are j
On Thu,20.Nov.08, 16:59:06, H.S. wrote:
> So my next query is how do I find out if any application in Debian
> requires OSS other than using the obvious brute force method? Is it even
> possible?
Usually the package description mentions it, but I doubt there is a
maintained software that doesn
H.S. wrote:
> Ron Johnson wrote:
>> http://en.wikipedia.org/wiki/Open_Sound_System#OSS_in_relation_to_ALSA
>>
>>OSS is the standard up through the 2.4 series of official
>>(kernel.org) Linux kernels. ALSA was added starting with 2.5,
>>and in those versions, Linux kernel authors marked
Ron Johnson wrote:
> On 11/20/08 14:27, H.S. wrote:
>> Hello,
>>
>> Could somebody give some insights in to how is OSS related to Alsa? When
>
> I hate to sound rude, but did you apply any effort in researching this
> yourself?
Yes, but it was a while ago. At that time, I must admit though, I kn
On 11/20/08 14:27, H.S. wrote:
Hello,
Could somebody give some insights in to how is OSS related to Alsa? When
I hate to sound rude, but did you apply any effort in researching
this yourself?
a headset is connected via USB, how is it supposed to be detected, as an
OSS device or as a USB de
Hello,
Could somebody give some insights in to how is OSS related to Alsa? When
a headset is connected via USB, how is it supposed to be detected, as an
OSS device or as a USB device?
And can I remove OSS in favor of Alsa?
Thanks.
--
Please reply to this list only. I read this list on its corr
Anssi Alhonen wrote:
>
>
> I noticed yesterday when I was trying to get my soundcard
> workingin potatoe that there are no sound devices like
> /dev/dsp and /dev/audio!
> Why?, should it be like this or have I screwed up my Linux
> box(I don't remeber that I would have deleted those
> files..)?
>
> I noticed yesterday when I was trying to get my soundcard
> workingin potatoe that there are no sound devices like
> /dev/dsp and /dev/audio!
They *should* be there. Try running MAKEDEV (which creates the standard
set of device files).
Greg
---
"With sufficient thrust, pigs fly just f
I noticed yesterday when I was trying to get my soundcard
workingin potatoe that there are no sound devices like
/dev/dsp and /dev/audio!
Why?, should it be like this or have I screwed up my Linux
box(I don't remeber that I would have deleted those
files..)?
How can I get those devices, is there
i just did a fresh install of slink, and for some reason, the audio
devices (most notably /dev/audio and /dev/dsp) were not created. was
this done by design? anyway, i created the necessary devices by doing
'(cd /dev ; ./MAKEDEV audio)' as root. the devices were created, but
the ow
82 matches
Mail list logo
