Comment 13 for bug 47706

OTOH - Abbreviation for "On The Other Hand"..

After unblacklisting, you might get away with simply inserting the module
again, with no reboot. Try this on the command line:
"modprobe nm256_audio"

Then check dmesg.

Cheers,
Danny

On 24/11/2007, pwii <email address hidden> wrote:
>
> I don't know what OTOH is...
>
> unblacklisting nm256, is that in /etc/modprobe.d/blacklist-oss
> [nm256_audio]
> ?
>
> I guess after unblacklisting I will need to reboot.
>
> Thx again -- Peter
>
>
> On Nov 23, 2007 11:32 PM, Lee Revell <email address hidden> wrote:
>
> > On Nov 23, 2007 5:07 PM, Peter Willaert <email address hidden> wrote:
> > > Now that's quick! As far as I can see (I once had 5+ years of
> > experience in
> > > HP-UX, but that's 10 years ago, so please excuse me for unclarities)
> the
> > > same behaviour as reported in
> > >
> > > http://ubuntuforums.org/showthread.php?t=209882
> > >
> > > that is:
> > >
> > > lspci reports the card/soundchip allright
> > > dmesg report nm256 as being blacklisted, loading stopped?
> > >
> >
> > OK. If this is the case then it looks like a different bug (the
> > notorious old nm256 bug was that the system would reboot or lock up
> > hard when loading the module). This OTOH is a "no sound" bug...
> >
> > Try un-blacklisting nm256 and see if that works...
> >
> > Lee
> >
> >
>
> --
> snd_nm256 module in dapper broken. Does not include oss sound module
> nm256_audio
> https://bugs.launchpad.net/bugs/47706
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Danny Staple MBCS
OrionRobots
http://orionrobots.co.uk/blogs/dannystaple
(Full contact details available through website)