[Bug 47706] Re: snd_nm256 module in dapper broken. Does not include oss sound module nm256_audio
danny at orionrobots.co.uk
Tue Nov 27 22:53:27 UTC 2007
I would advise not closing the bug report until you have found out how to
exactly solve the issue, and like Fern mentioned, it has been solved in an
automatic user friendly way in the distribution. Even a downloadable
"download and run this magic" script would be better than the current
scenario of users with no sound.
Unfortunately, although I know Linux commands, I do not own or have said
hardware to try it out myself. My advice would be to gather up an idea of
the kernel modules that are otherwise interacting with/supporting the
hardware, and rmmod them. Maybe you could post the full output of lsmod, and
that might be a starting point.
On 27/11/2007, pwii <peter.willaert at mail.com> wrote:
> After some further research, I now tend to believe that the problem is not
> *bug*, but has to do with a configuration issue on this type of laptop (HP
> Omnibook 4150). The root cause seems to be the fact that the audio chip
> on the PCI bus but is emulated as an ISA card. Apparently this is not
> handled well during hardware autodetection, resulting in no sound. Can you
> agree to this diagnosis?
> I have found some information on the net indicating that the OSS sound
> system seems to be capable to delete the standard drivers and re-detect
> sound chip in its correct configuration. I believe that this should also
> possible from a command window using standard Linux configuration
> However, I have no idea how to do that. Could anyone of you point me into
> useful direction?
> Maybe it's also a good idea to close this bug report?
> Best regards,
> snd_nm256 module in dapper broken. Does not include oss sound module
> You received this bug notification because you are a direct subscriber
> of the bug.
Danny Staple MBCS
(Full contact details available through website)
snd_nm256 module in dapper broken. Does not include oss sound module nm256_audio
You received this bug notification because you are a member of Kernel
Bugs, which is a direct subscriber.
More information about the kernel-bugs