did you compile a new kernel? If yes, then you need to reemerge alsa-driver after 'make modules_install'. To start alsa you can switch between the different states with '/etc/init.d/alsasound zap'.
Hope this helps
MfG Michael
D.J. Bolderman wrote:
Guys,
For some reason, alsa sound stopped working. Xmms produces no sound
output. Xawtv and mpg123 are working fine. Last night I was fiddling
around with Mythtv, but I can't remember to have changed anything
which could affect alsa.
I re-emerged alsa-driver and alsa-xmms, but to no avail...
Restarting alsasound seems to give some problems:
bash-2.05b# /etc/init.d/alsasound restart
* ALSA driver is already running.
bash-2.05b# /etc/init.d/alsasound stop * ERROR: "alsasound" has not yet been started.
bash-2.05b# /etc/init.d/alsasound start
* ALSA driver is already running.
lsmod shows:
Module Size Used by Not tainted
snd-pcm-oss 39652 0 (autoclean)
snd-mixer-oss 13752 0 (autoclean) [snd-pcm-oss]
i2c-dev 4772 0 (unused)
tuner 10144 1 (autoclean)
tvaudio 12892 0 (autoclean) (unused)
msp3400 17036 1 (autoclean)
bttv 69888 1 i2c-algo-bit 8360 1 [bttv]
radeon 104392 2 agpgart 14772 3 (autoclean)
i2c-proc 7472 0 i2c-core 16232 0 [i2c-dev tuner tvaudio msp3400 bttv
i2c-algo-bit i2c-proc]
snd-cs46xx 72252 1 snd-rawmidi 15712 0 [snd-cs46xx]
snd-seq-device 4420 0 [snd-rawmidi]
snd-ac97-codec 42232 0 [snd-cs46xx]
snd-pcm 68512 0 [snd-pcm-oss snd-cs46xx]
snd-page-alloc 7060 0 [snd-cs46xx snd-pcm]
snd-timer 16900 0 [snd-pcm]
snd 34756 1 [snd-pcm-oss snd-mixer-oss
snd-cs46xx snd-rawmidi snd-seq-device snd-ac97-codec snd-pcm
snd-timer]
soundcore 4580 6 [bttv snd]
Relevant cat /proc/pci:
Bus 0, device 9, function 0: Multimedia audio controller: Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion Audio Accelerator] (rev 1). IRQ 5. Master Capable. Latency=32. Min Gnt=4.Max Lat=24. Non-prefetchable 32 bit memory at 0xef101000 [0xef101fff]. Non-prefetchable 32 bit memory at 0xef000000 [0xef0fffff].
What could be the problem here ?
Thanks Dick
-- [EMAIL PROTECTED] mailing list
--
/* These are the most dangerous and useful defines. They do printk() during
* the interrupt processing routine(s), so if you manage to get "flooded" by
* irq's, start thinking about the "Power off/on" button...
*/
2.2.16 /usr/src/linux/drivers/sbus/char/aurora.h
-- [EMAIL PROTECTED] mailing list