8 Feb
2003
8 Feb
'03
2:46 p.m.
Es geschah am Freitag, 7. Februar 2003 09:23 als Clemens Ladisch schrieb:
I know, sorry, I just typed that to get all in one.
Yes, it is.
Ok, at least
after a 'modprobe snd-seq-oss' I got the /dev/snd/seq
device,
/dev/snd/seq is the ALSA sequencer device. The OSS sequencer would be
/dev/sequencer. but I have to
do that manually everytime I reboot. So why isn't this
module loaded automatically? According to my modules.conf it should:
...
alias sound-service-0-1 snd-seq-oss
...
Please check that the /dev/sequencer file has major/minor numbers 14, 1. And when you access /dev/sequencer, the module should
be loaded, or there
is an error message written to /var/log/messages.
Correct, accessing /dev/sequencer loads the module and /dev/snd/seq appears,
but shouldn't the Alsa seq module be loaded automatically on startup? Alsa
apps won't try to access /dev/sequencer before they actually open
/dev/snd/seq, right? Thus, no Alsa app will work after a reboot without me
having loaded the Alsa seq module manually (or having accessed
/dev/sequencer).
Hope you still have patience to answer me ;)
Regards, Christian