Re: Kernel 2.6 and sound ymfpci

[Christoph Sticksel <spamwonderfulspam@gmx.net>]

Silvan wrote:
> On Tuesday 06 July 2004 11:00 am, Christoph Sticksel wrote:
>> What is the preferred way to load modules? modconf or
>> /etc/also/modultils/0.5? Does is matter that /etc/alsa/0.9 is empty?
>
> I don't know what the "preferred" way is, I don't suppose.  I always use
> modconf, but that's mostly because it was the first thing I tried, and it
> worked.  :)

modconf still seems to work with 2.6 kernels, so I'll also continue using
it.
 
>> For the record: this is /etc/alsa/modutils/0.5 after unsuccessfully
>> running alsaconf (see below)
> 
> 0.5 is *seriously* ancient.  You're probably looking at meaningless cruft.
>  I don't even have an /etc/alsa/modutils/ at all, and my /etc/alsa/0.9 is
> empty.

Good to have that ruled out.

>> I tried to manually modprobe -r snd-ymfpci and then modprobe it again and
>> modprobe hangs and cannot be killed even by killing the terminal it runs
>> in. dmesg shows the same "kobject_register failed for opl3sa2 (-17)" as
> 
> I'm not a kernel hacker, and I have no real clue what that
> kobject_register stuff means.

That still is my guess to why all that fails. 
 
> What's it actually trying to open that isn't there?  Is it just something
> in /dev perchance?
> 
> strace -eopen alsamixer 2>&1 > /tmp/post-me
>
> You'll have to ^C out of it.

I didn't, see the last line :-)

| open("/etc/ld.so.preload", O_RDONLY)    = -1 ENOENT (No such file or 
directory)
| open("/etc/ld.so.cache", O_RDONLY)      = 3
| open("/lib/libncurses.so.5", O_RDONLY)  = 3
| open("/usr/lib/libasound.so.2", O_RDONLY) = 3
| open("/lib/tls/libm.so.6", O_RDONLY)    = 3
| open("/lib/tls/libdl.so.2", O_RDONLY)   = 3
| open("/lib/tls/libpthread.so.0", O_RDONLY) = 3
| open("/lib/tls/libc.so.6", O_RDONLY)    = 3
| open("/usr/share/alsa/alsa.conf", O_RDONLY) = 3
| open("/dev/snd/controlC0", O_RDONLY)    = -1 ENODEV (No such device)
| open("/dev/aloadC0", O_RDONLY)          = -1 ENODEV (No such device)
| open("/dev/snd/controlC0", O_RDWR)      = -1 ENODEV (No such device)
| open("/dev/snd/controlC0", O_RDONLY)    = -1 ENODEV (No such device)
| open("/dev/aloadC0", O_RDONLY)          = -1 ENODEV (No such device)
| open("/dev/snd/controlC0", O_RDWR)      = -1 ENODEV (No such device)
| alsamixer: function snd_ctl_open failed for default: No such device

> What I'm kind of expecting to see there is that it's trying to open /dev
> stuff
> that you don't have.  How you get the /dev stuff for a 2.6 kernel is
> beyond my experience (udev?), but at least I can confirm or deny that's
> where you need to look.

You guessed right, some /devs are missing. So is this normal, or do the
files in /dev get created when the module is actually loaded?
 
Thanks for your ideas anyways,
Chris