> Did anything change w.r.t. SBPCD handling in the last kernel change?
> Did I make a dumbass mistake? Any advice on how to approach debugging
> this?
I don't know any of the changes, but I can give advice on how to debug
this.
try running:
/bin/dmesg
The kernel keeps a little buffer of all the messages that it prints.
This command will display them. Now, the buffer isn't infinetely large,
so after a while the oldest messages will not appear with this command.
After a reboot, you are pretty sure to have a complete list of boot time
messages (the same ones that fly by when you boot up). I would review
them (maybe running "dmesg | more") and look for your soundblaster card
being detected. That information would likely be informative as to the
cause of the problem.
I would think that running as root:
/sbin/modprobe sbpcd
might help. But I have don't have the same hardware/redhat version as
you, and have linux problems of my own ;) I'm fairly certain that the
above commands cannot hurt, and have a good chance of sheding important
light on the situation.
Good luck,
Kenneth Topp
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
