Bug#357236: [Pkg-alsa-devel] Re: Bug#357236: linux-image-2.6.16-rc5-686: no sound on Lifebook P2120
On Mon, 19 Jun 2006 the mental interface of
Adam C Powell IV told:
> reassign 357236 linux-image-2.6.16-2-686
> forwarded 357236 https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1943
> thanks
>
> Hadn't noticed that the forward tag didn't work last time, sorry about
> that.
>
> Okay, it's been three months and upstream hasn't touched my bug. I'm
> wondering if I can get some help here, or at least vague ideas about
> what might be going wrong.
>
> On this laptop, fn-F3 toggles mute; when mute is turned off, there's an
> audible beep. When repeatedly toggling "mute unmute mute unmute", I
> noticed that this audible beep capability stops during the boot. By
> booting with init=/bin/bash and carefully going through things, I've
> managed to narrow it down to when the /etc/init.d/udev script runs
> udevtrigger.
>
> If I reboot and load the modules which udevtrigger would load, that does
> not cause the beeps to stop, but then running udevtrigger does stop
> them. I think something in udevtrigger somehow disables sound output.
>
> Any ideas?
No.
Which Kernel?
Which alsa-packages?
Wich distro (sarge|testing|sid)?
Did you build the latest drivers out of alsa-source 1.0.11-2?
What tells cat /proc/asound after a normal boot?
which modules are loaded then?
Are there any mixer settings muted?
> Could this be a Debian-specific problem?
Did you tried a live CD (grml|Knoppix|*buntu|Gentoo)?
> What do I test next? Do I stick a bunch of printfs and sleep commands into the
> udevtrigger source to pin things down further?
Best would be to run a Live CD first to exclude a hardware failure
here. And give some Infos about your system and check some audio
apps like moc, alsaplayer, xmms, mplayer......
> I've had no sound on this laptop for a year,
Waaaaoooow, so you are very patient ;)
> and finally have some time
> to put into this, but would rather not just flail about blindly...
Elimar
--
Do you smell something burning or ist it me?
Reply to: