On Sat, 03 Mar 2001, [EMAIL PROTECTED] wrote:
> Richard [EMAIL PROTECTED] wrote:
> > Please elaborate, what are you trying to do, exacht command, o yes and "Please"
> > next time write down the "whole" error message.
>
> Ok, Richard, thanks for the answer.
> Exactly i'm trying to load the module sb.o, it is in directory
>/lib/modules/2.2.17/misc
> i have this modules:
> soundcore: using /lib/modules/2.2.17/misc/soundcore.o
> sound: using /lib/modules/2.2.17/misc/sound.o
> uart401: using /lib/modules/2.2.17/misc/uart401.o
> When i try to load sb.o, the bash answer is:
> using /lib/modules/2.2.17/misc/sb.o
> lib/modules/2.2.17/misc/sb.o: init_module:Device busy
> i suspect that i must change modules.conf but...i'm not sure.
Do you really need sb.o to operate your soundcard,? you already have sound.o
loaded and that is the cause of Device Busy when you do modprobe sb.
>From your information i would remove all sound modules with 'rmmod' then try
modprobe sb.o, however that may not work as simple as i write it.
I suggest you take a look at /usr/src/linux/Documantation/sound/* and look for
a file concerning your type/make of soundcard.
You do not say what type/make it is but if i was looking for information on a
soundcard i would do;
cd /usr/src/linux/Documentation/sound
grep <cardtype> *
<cardtype> would be something like AWE32 or PRO100 etc etc.
Normally speaking when one uses a "stock kernel" from a distribution cd, then
most drivers are in module form eliminating the need to recompile a kernel to
support your card. This means dont get worried by documentation saying you need
to recompile a kernel with xx.o support, check /lib/modules/kernel-version/*
directorys first.
> Thanks you very much, again.
> Regards. Jose Luis. Madrid. Spain.
--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
