> Firstly: Are you a part of the "audio" group? If not, that will make
> everything cranky. You can fix this by adding yourself to the audio
> group. It'll just say "The user is already a member of audio"
> example:
> princess:~# adduser greg audio
> The user `greg' is already a m
On Sat, 2007-03-24 at 22:02 -0400, Mark Grieveson wrote:
> Hello. After a recent upgrade of Etch, I find I have no sound. The
> volume control thingy on the top panel of gnome suddenly had a red x
> beside it, and, when I pressed it, it gave me the following error:
>
> "The volume control did no
> Hi Mark,
> Have your tried doing aplay from a commandline just to eliminate Gnome
> as the source of the problem. I don't use gnome so I can't help you
> there. Can you get the alsamixer to work? Or does it also complain
> that it can't find any device?
> Cheers,
> Jonathan
Alsamixer only works
Mark Grieveson wrote:
>> Hi Mark,
>> What was the result of running alsaconf? Did it claim to have
>> installed the sound module?
>> What sound card are you using? Do you see its module showing up when
>> you do lsmod ?
>> Cheers,
>> Jonathan
>
> Hello Jonathan,
> The result of alsaconf is that i
> > So, has anyone else had this issue recently? I tried running
> > alsaconf, and installing various gstreamer stuff, but to no avail.
> >
> > Mark
> Hi Mark,
> What was the result of running alsaconf? Did it claim to have
> installed the sound module?
> What sound card are you using? Do you
Mark Grieveson wrote:
> Hello. After a recent upgrade of Etch, I find I have no sound. The
> volume control thingy on the top panel of gnome suddenly had a red x
> beside it, and, when I pressed it, it gave me the following error:
>
> "The volume control did not find any elements and/or devices
Hello. After a recent upgrade of Etch, I find I have no sound. The
volume control thingy on the top panel of gnome suddenly had a red x
beside it, and, when I pressed it, it gave me the following error:
"The volume control did not find any elements and/or devices to control.
This means either th
you may not be able to get sound because there is not enough free memory
below 16MB for the dma buffer.
in more recent 2.2.x kernels you gotta enable the persistant DMA buffers
in sound config and it will reserve the memory at boot. it may not solve
this problem, but its an idea :)
nate
Well, before I left for the weekend, I had my sound working. When I
returned, my machine had apparently lost power and was sitting there at
"invalid system disk" because I hada floppy in the drive. Anyway, my main
partition was hosed, so I had to run fsck manually.
Next, I fired up xmms to make
You know, none of the *play programs I've installed for debian have ever
worked. Go
figure. Anyway, the 'sndkit' you can get from sunsite has a program called
'vplay'
which has always worked well for me. I'm email you separately the source (+
compiled
binary in case you're not interested in buil
I have a SB Pro/16/WSS sound card on my mother board that I use for sound.
I have compiled sounds support as a module and included /dev/dsp and
/dev/audio support in the kernel. I Have isapnp setup and the sound
devices are detected and listed in /dev/sndstat. When I try to play
sound, the best I
11 matches
Mail list logo
