On Saturday 10 July 2004 08:54 am, Christoph Sticksel wrote:
> | 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
> 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?
No, it doesn't have anything to do with the modules. On 2.4 kernels, if you
don't mount devfs, you can create the files in /dev manually, using the
snddevices script from the ALSA source. That's the route I've always taken,
mostly because devfs was very new and very broken when I switched to Linux,
and I had to turn it off. I've never bothered to turn it back on since.
I can't describe any of the alternatives without potentially filling your head
with a bunch crap, so it's better if I don't try. I'm not sure if devfs or
udev or whatever 2.6 kernels have is still optional, and not sure about a lot
of other related things either.
I've changed the subject. Hopefully someone with a clue here will step in.
At least you know where to look now.
--
Michael McIntyre ---- Silvan <[EMAIL PROTECTED]>
Linux fanatic, and certified Geek; registered Linux user #243621
http://www.geocities.com/Paris/Rue/5407/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
