Re: debugging nm256: some results, many questions

[Florian Schlichting <Florian.Schlichting@gmx.de>]

[-- Attachment #1: Type: text/plain, Size: 2510 bytes --]

On Tue, Mar 14, 2006 at 09:16:28PM +0100, Takashi Iwai wrote:
> At Wed, 15 Mar 2006 03:59:46 +0800,
> Florian Schlichting wrote:
> > Also, there are some warnings during compile and a problem with depmod 
> > loops at install
> > ----------
> >   Building modules, stage 2.
> >   MODPOST
> > *** Warning: "snd_minor_info_oss_init" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > *** Warning: "snd_lookup_oss_minor_data" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > *** Warning: "snd_info_minor_unregister" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > *** Warning: "snd_minor_info_oss_done" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > *** Warning: "snd_info_minor_register" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > 
> > [...]
> > 
> > WARNING: Loop detected:
> > /lib/modules/2.6.15-max/kernel/sound/acore/snd.ko which needs snd.ko
> > again!
> > ----------
> > (and the rest of the ALSA modules is ignored), so although I could 
> > build things, it wouldn't "make install" and I can't make a final smoke 
> > test :-(
> 
> Hm, it sounds like CONFIG_PROC_FS isn't defined properly.
> Please check alsa-driver/include/linux/autoconf.h.  It's generated by
> configure script.

hmmm... do you mean this:

#define CONFIG_ACPI_SLEEP_PROC_FS 1
#undef CONFIG_ACPI_SLEEP_PROC_SLEEP
[...]
#undef CONFIG_PCI_LEGACY_PROC
[...]
#define CONFIG_SCSI_PROC_FS 1
[...]
#define CONFIG_PROC_FS 1
#define CONFIG_PROC_KCORE 1
[...]
#define CONFIG_SND_VERBOSE_PROCFS 1

-.-

I noticed the errors said something with oss. My compile commmand line
was './cvscompile --with-isapnp=no --with-sequencer=no --with-oss=no
--with-cards=nm256' and that still gives the above errors. I just
recompiled with just './cvscompile --with-cards=nm256' and there are no
errors, depmod runs fine, I can insert the module...  perfect! The mixer
settings also survive a suspend, apart from Master Volume which becomes
muted (but I guess that's intented? I can't confirm bug#1532)

Thus, are we done fixing an issue that has bugged poor nm256 owners for
years?? bug#328, bug#914 and kbug#3719 look like their
submitters/contributors might be interested in giving it a try...

Summary: treat the nm256 mixer as a write-only device so as to avoid
hangs on initialisation (fixes: bug#....[when confirmed]) and clean up
an older workaround in ac97_codec
Signed-off-by: Florian Schlichting <Florian.Schlichting@gmx.de>


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]