fedora 10 update seems to nuke my sound
It happened once with Fedora 9, I upgraded to 10, and now it's happened again. I assume it's the automatic update, because I haven't changed anything else - suddenly no sound. This is kernel 184.108.40.206-170.2.5.fc10.x86_64. If I go back to 220.127.116.11-117.fc10.x86_64, the sound is back again. I'm sure I'm missing something obvious, but would really appreciate some help.
Post output of
relevant part of
check mixer (volume)
try to reload alsa
file a bug report
[almac@localhost ~]$ lspci
00:00.0 Host bridge: nVidia Corporation nForce3 Host Bridge (rev a4)
00:01.0 ISA bridge: nVidia Corporation nForce3 LPC Bridge (rev f6)
00:01.1 SMBus: nVidia Corporation nForce3 SMBus (rev a4)
00:02.0 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
00:02.1 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
00:02.2 USB Controller: nVidia Corporation nForce3 USB 2.0 (rev a2)
00:05.0 Ethernet controller: nVidia Corporation nForce3 Ethernet (rev a5)
00:08.0 IDE interface: nVidia Corporation nForce3 IDE (rev a5)
00:0a.0 PCI bridge: nVidia Corporation nForce3 PCI Bridge (rev a2)
00:0b.0 PCI bridge: nVidia Corporation nForce3 AGP Bridge (rev a4)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:04.0 Communication controller: Conexant HSF 56k HSFi Modem (rev 01)
01:05.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 0c)
01:06.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
01:06.1 Input device controller: Creative Labs SB Audigy Game Port (rev 04)
01:06.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04)
01:08.0 RAID bus controller: Promise Technology, Inc. PDC20378 (FastTrak 378/SATA 378) (rev 02)
01:09.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
02:00.0 VGA compatible controller: ATI Technologies Inc Radeon R350 [Radeon 9800 Pro]
02:00.1 Display controller: ATI Technologies Inc Radeon R350 [Radeon 9800 Pro] (Secondary)
mixer volume seems to be right up
... and I don't appear to have /sbin/alsa/reload
Thanks for responding, though
Oh - forgot lsmod:
snd_emu10k1_synth 15616 0
snd_emux_synth 43392 1 snd_emu10k1_synth
snd_seq_virmidi 14080 1 snd_emux_synth
ata_generic 14084 0
snd_seq_midi_emul 14080 1 snd_emux_synth
pata_acpi 13184 0
snd_emu10k1 152720 5 snd_emu10k1_synth
snd_rawmidi 30848 2 snd_seq_virmidi,snd_emu10k1
snd_ac97_codec 121160 1 snd_emu10k1
ac97_bus 10112 1 snd_ac97_codec
snd_seq_dummy 11396 0
snd_seq_oss 39104 0
snd_seq_midi_event 14848 2 snd_seq_virmidi,snd_seq_oss
snd_seq 61968 8 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_pcm_oss 52224 0
snd_mixer_oss 23168 1 snd_pcm_oss
snd_pcm 85512 4 snd_emu10k1,snd_ac97_codec,snd_pcm_oss
snd_seq_device 15380 7 snd_emu10k1_synth,snd_emux_synth,snd_emu10k1,snd_rawmidi,snd_seq_dummy,snd_seq_oss,snd_seq
snd_timer 30352 3 snd_emu10k1,snd_seq,snd_pcm
snd_page_alloc 16656 2 snd_emu10k1,snd_pcm
snd_util_mem 12416 2 snd_emux_synth,snd_emu10k1
snd_hwdep 16392 2 snd_emux_synth,snd_emu10k1
emu10k1_gp 11392 0
serio_raw 14084 0
snd 68984 24 snd_emu10k1_synth,snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_emu10k1,snd_rawmidi,snd_ac97_ codec,snd_seq_dummy,snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_device,snd_timer,s nd_util_mem,snd_hwdep
soundcore 14992 1 snd
Also, the settings for Alsa mixer and for PulseAudio volume control are the same for the kernel that works and the one that doesn't.
/sbin/alsa reload is a command to be typed in a terminal.
Open a terminal window and type 'su -' without the quotes to become root.
Type in the root password when prompted.
Type in '/sbin/alsa reload' without the quotes to restart the alsa program.
Others have also had this problem. If the reload doesn't help you can boot with the old kernal until a fix comes along.
I don't have /sbin/alsa, all that seems close is /sbin/alsactl, and reload doesn't work with that. I guess I'll stick to the older kernel, but should I refuse updates, and how will I know when a fix comes along?
Sorry to spout so many questions. Good to know I'm not alone - well, good to know I'm not an only dumb one, and that others get this too.
It's not a good idea to refuse the updates as they may fix things far more serious than missing sound such as security holes.
If alsactl reload didn't work you may want to try
btw: when posting outputs of things like 'lspci' and 'lsmod' surround the info with:
[ code ] and [ /code ] (without the spaces)
This will format the output nicely and make it much easier to read.
Here is the output of 'lsmod | grep snd' from my system.
and this is the one that does work:
Oh, did I say, the soundcard is an Audigy 2 ZS
... annd the alsamixer shows output up in the red?
They look identical to me Alan. It's definately a kernel issue.
Check this thread.
And check if any of these suggestions work for you.
and today, it works! Go figure, as they say. Thanks very much for your patience, Laserman.
|All times are GMT -5. The time now is 03:25 PM.|