On Tuesday 06 July 2004 11:00 am, Christoph Sticksel wrote:

> That's what I thought. This is what lsmod tells me about loaded modules

> | snd_ac97_codec         70020  1 snd_ymfpci
[etc...]

That looks fine off-hand, though I don't know exactly what I should see there 
for your hardware.  I don't think you have a module problem at all.

> snd-opl3sa2 is there as well. BTW, what do you mean by picking another?

What I meant was you said you did "modprobe -v opl3sa1" which was clearly not 
the right thing to do, since that would load an OSS module.  I wanted to make 
sure you understood the distinction.

> 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.  :)

> 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.

> 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.

> sound was now configured. However that did not work. alsamixer run
> afterwards said "function snd_ctl_open failed for default: No such device"

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.

Ugh.  Don't do it from an xterm you ever want to use again either.

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.

If this isn't it, then I'm out of ideas.  Perhaps other than pointing out I 
can think of four other people who are having problems with 2.6 kernels and 
ALSA right now.  It sure isn't making me eager to try the thing out.

-- 
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]

Reply via email to