🚀 go-pugleaf

Hello!

Kurniadi Asrigo <kuas@corelcity.com> wrote:
>Yes, I tried all the suggestion here. But I am still having the trouble.
>
>I followed Anthony advice to do "depmod -a". Then I continued with
>"modprobe sb.o". But the error I got just exactly the same when it was
>in booting time, which is:
>
>/lib/modules/2.2.13/misc/sb.o: init_module:Device or resource busy
>
>That's the error I had.

I have a strange feeling that you have compiled your kernel with soundcard
handling built-in, not as a module... That's why the sb.o module cannot be
loaded and you get the message "device or resource busy". Check it.

>For Venex:

OK, I'll let me read it, because I'm still the same person, only my
nickname has changed recently ;-)

>(...)
>Actually my conf.modules is like this:
>------------------------
>alias eth0 ne2k-pci 
>alias eth1 rt18139 
>alias parport_lowlevel parport_pc 
>pre-install pcmcia_core /etc/rc.d/init.d/pcmcia start 
>alias sound sb 
>pre-install sound insmod sound dmabuf=1 
>options opl3 io=0x388 
>alias midi awe_wave 
>post-install awe_wave /bin/sfxload /etc/midi/GU11-ROM.SF2 
>alias sdla sdla 
>------------------------
>
>I don't know why I have the pcmcia_core, I don't need it but it's there.

I don't need it either, but I still have it. AFAIK if you don't have pcmcia
port, the module is simply not loaded, it's just for the compatibility.

>And I don't understand what is parport.

It has to do something with printers, Linux need this lowlevel parallel port
management to deal with them properly. But I don't know much about the
details...

> For the sounds as you all can
>see it does not have that dma and irq setting. How do I add them? Just
>edit this conf? What should I change?

I'm not familiar with AWE soundcards, so I just don't know. Everything depends
on your soundcard... For example I'm using both Gravis Ultra Sound and old Sound
Blaster Pro, and for either of those configurations /etc/conf.modules looks as
follows:

GUS:
--
alias parport_lowlevel parport_pc
pre-install pcmcia_core /etc/rc.d/init.d/pcmcia start
alias sound gus
pre-install sound insmod sound dmabuf=1
options gus io=0x240 irq=5 dma=5
--

SB:
--
alias parport_lowlevel parport_pc
pre-install pcmcia_core /etc/rc.d/init.d/pcmcia start
options gus io=0x240 irq=5 dma=5
alias sound sb
pre-install sound insmod sound dmabuf=1
alias midi opl3
options opl3 io=0x388
options sb io=0x220 irq=7 dma=1
--

>in addition of the previous situation, i should also tell you this error
>when I am running "sndconfig":
>
>You don't seem to be running a kernel with modular sound enable.
>(soundcore.o was not found in the module search path). To run sndconfig,
>you must be running a kernel with modular....blabla.. 

Maybe I'm stubborn as a donkey, but I still think that you have your soundcard
management built in into your kernel ;-) That's why at the same beginning the
card is initialized, and afterwards, when Linux tries to load a module, it can't
do this, because the soundcard had been already enabled...

>Did I missed something, when I was compiling the kernel? If so, do I
>have to compile everything again? Or just set everything to 'n' and only
>that part I compile with module. Run "make modules" then "make
>modules_install". Is that how, so I can run modprobe?

You can either recompile your kernel and set up the soundcard handling as a
module, or just remove the following lines from /etc/conf.modules (remember
about backup!):

>alias sound sb 
>pre-install sound insmod sound dmabuf=1 
>options opl3 io=0x388 
>alias midi awe_wave 
>post-install awe_wave /bin/sfxload /etc/midi/GU11-ROM.SF2 

I'd suggest the last solution. But it will not change anything anyway, you will
only not get error messages any more. It comes from the fact, that if your
soundcard had been enabled during bootup by the kernel, the sound settings
located in /etc/conf.modules were skipped anyhow :-)

Good luck!
--
Calder