red hat 9 vs ALSA vs SB live (ARRRG)
 

hi all

i have an SB LIVE 5.1 wich works under windows , it never ever worked in linux till now , ive spent the last few days trying to change that but it was useless

heres the problem

during instalation (RH9) the card was ¨automatically detected¨(wo messages) and installed in the kernel as ¨creative esoniq¨ well i dont have one esoniq and the kernel option for emu10k1 its disabled..
so i tried recompiling the kernel to change that.. useless the new kernel wont start (kernel panic)
well then i decided to just disable manually the drive (modprobe -r) and i installed a fresh new one (ALSA)

but everytime i try to load the alsa drive he gives me th Ismod error and say that the device is probrably busy or there is probrably a problem with the irq

is there ANY way of fixing that stuff out? i mean im tired of having to reboot under linux only to listen to my music

anyone???

:newbie:

"installed in the kernel as ¨creative esoniq¨ well i dont have one esoniq "

Esoniq is the name of the company that makes the chipsets for the SoundBlaster brand. You have to compile the correct kernel module for the chipset on your Creative Soundblaster card. So read the Esoniq chipset number off of your sound card. Then look through the help in the make xconfig until you find the sound module that supports that chipset.

yup
 

i tried that sorry if i was not clear enough in my post
i tried recompiling the kernel with the good option , been through the make xconfig then make dep them make clean then make modules and make modules_install

then i put the new kernel in /boot and modify lilo.conf (without forgeting to execute lilo)

but the new kernel does not boot :( he just kernel panic itself....

"then i put the new kernel in /boot and modify lilo.conf (without forgeting to execute lilo)"

The only thing that I can think of is that you may need to create a new initrd if you are using initrd.

i did that now

no luck
i still get the message about not finding root

changed lilo.conf to give the root=/dev/hdb2 option but also no luck

and one strange thing is that i use
vga=792 in lilo

and with my normal kernel the vga text mode do enter (while loading linux i get everything in a nice resolution with a little tux icon)

but with the new one even WAY before doing kernel panic the launching messages are already in the old text way (dos like resolution) thats not a bug or a serious thing it just show me in the very begnning that something is wrong :)


my ONLY theory is the System.map file that i did no touch
bu it doesnt say anything about her in everyplace i read about kernel compiling and it would not be logical (if i needed to have only one System.map AND for one version only it would not make sense to dual boot between different versions of the kernel.


help anybody?

It has to do with how redhat uses LABEL=/ to mount its root, the mount command inside the initrd understands the use of LABEL, but not the kernel. You should be able to boot it if you specify the root using the device node /dev/hdX to the kernel parameter and the /etc/fstab file, if you compiled essential components(file system driver etc) inside the kernel.
However you shouldn't need to recompile the module, since the kernel that comes with redhat actually already has almost everything compiled as a module,
Try this emu10k1 driver:
http://sourceforge.net/projects/emu10k1/
(it works very well for my audigy card(it also supports live series), and has many configurable options(like enabling digital out etc)

it was actually a good idea , i just tried but no succes nonetheles :(

as rdev seemed a good idea and i just tried too