Bug#509176: sound card losing configuration (upgrade-reports) additional info
Package: upgrade-reports
Severity: critical
Justification: breaks the whole system
[additional information]
Upon rebooting Debian Etch which was upgraded on 12/16/2008
linux-image-2.6.18-6-486 (2.6.18.dfsg.1-23) to 2.6.18.dfsg.1-23etch1
sound is redirected to /dev/null. XMMS reporting following error message:
upon reboot clicking on XMMS on any oss sound file gives the error
#------------------------------------------
"Couldn't open audio"
Please check that
Your sound card is configured properly
You have the correct output plugin selected
No other program is blocking the soundcard
#------------------------------------------
Running alsaconf the processes
2975 [esd]
3069 [mixer-applet2]
are being terminated. It appears the following kernel modules are unloaded and then reloaded
snd-hda-intel {/lib/modules/2.6.18-6-486/kernel/sound/pci/hda/snd-hda-intel.ko}
snd-hda-codec {/lib/modules/2.6.18-6-486/kernel/sound/pci/hda/snd-hda-codec.ko}
snd-pcm-oss {/lib/modules/2.6.18-6-486/kernel/sound/core/oss/snd-pcm-oss.ko}
snd-mixer-oss {/lib/modules/2.6.18-6-486/kernel/sound/core/oss/snd-mixer-oss.ko}
snd-pcm {/lib/modules/2.6.18-6-486/kernel/sound/core/snd-pcm.ko}
snd-timer {/lib/modules/2.6.18-6-486/kernel/sound/core/snd-timer.ko}
snd-page-alloc {/lib/modules/2.6.18-6-486/kernel/sound/core/snd-page-alloc.ko}
Suspecting a mapping problem in the core module snd-hda-intel.ko
It can be replicated every time upon reboot, no sound even though speaker is turned up all the way and sound is NOT muted. After running alsaconf the sound works fine, but it is annoying having to run alsaconf every time that you boot the system. This was never necessary since installing Etch as a network install. Not sure if doing a new, full network install manifests the same problem, if a new install does not have this bug, the system build must have something missing between old binary and the new. No changes have been made to any hardware and otherwise everything works. Problem became apparent after secondary update on 12/18/2008, not sure if lib6c, dpkg, or locales may have something to do with it. It's conceivable that I did not reboot system for 2 days after kernel update, but I am convinced that after a kernel update, you are forced to reboot. I always had to do this on SuSE after any kernel update. Why do the alsaconf settings not hold between
successive reboot? Not sure if I should rebuild the affected kernel modules with full debug info to track down the bug further. Any suggestions?
With kindest regards,
Arkady
Reply to: