[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Sound stopped working in Sid



On 28 Sep 2007, Chris Lale wrote:
> Anthony Campbell wrote:
> > On 28 Sep 2007, Chris Lale wrote:
> >> Meanwhile, you could try my workaround [1] for Etch:
> >>
> >> "The problem in alsaconf is the result of the presence of the file
> >> /etc/modprobe.conf. This causes /etc/modprobe.d/ to be ignored by Debian
> >> packages (including alsaconf) which store their configuration files in
> >> /etc/modprobe.d/. The permanent solution is to move /etc/modprobe.conf out of
> >> the way. Do not delete it just in case there are modules listed in it by other
> >> applications that you may need to know about if those applications start
> >> misbehaving. Rename the file instead:
> >>
> >>  # mv /etc/modprobe.conf /etc/modprobe.conf.obsolete
> >>
> >> Now run alsaconf again and everything should work."
> >>
> > 
> > I don't have this file at all but still the problem occurs.
> > 
> > 
> 
> You could check that /etc/modprobe.d exists.
> 
> Have you tried running udevtrigger as user root? This is from bug no 430624 [1]:
> 
> # udevtrigger --verbose
> 
> "This should reload the modules you need. On next reboot, your system will find
> your soundcard. The module management is done by udev. You should not need to
> use alsaconf any more."
> 
> [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=430624
> 
> -- 
> Chris.
> 

I do have /etc/modprobe-d though I'm not sure what it does. I tried
udevtrigger but it didn't reload the module after alsaconf; I did it
with insmod, I think. Anyway, it's all fairly academic since now that I
have the entry in /etc/modules it loads automatically at each reboot.

-- 
Anthony Campbell - ac@acampbell.org.uk 
Microsoft-free zone - Using Linux Gnu-Debian
http://www.acampbell.org.uk (blog, book reviews, 
on-line books and sceptical articles)



Reply to: