i just recompiled my kernel. but the lilo.conf file which i edited and ran /sbin/lilo is in my secondary hard disk (i dual boot Win98). i use a floppy boot to get to slack as lilo somehow corrupts my MBR.

my boot floppy was made during the initial install. i'm wondering now... is it booting up to my new re-compiled kernel or the old default one? if it's booting up to the old one, how do i get it to boot to the re-compiled kernel?

i tried to do a ls on the boot floppy but gives me this error:
EXT2 - fs error (device fd(2,0)) ext2_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0

don't know if this work`s but try running setup as # and slect configure.
and make a new lilo boot disk...

You might want to try man lilo..

Next time you boot just do "uname -a" to see what kernel your using.

which part of the output is supposed to tell me that?

i saw 2.2.19 (which is currently the only kernel i have on board). during the install, i selected the 2.2.19 kernel. when i recompiled the kernel, it was for 2.2.19 as well.

which er... reverts me back to the orignal question. does the floppy boot up to the newly re-compiled kernel or to the old one? (what i'm trying to say is does it read the lilo.conf found in my secondary hard disk where slack is installed?)

kinda important coz i'm troubleshooting my sound on slack.

the modprobe sound works fine, but when i try to play something on xmms, it still tells mw that either the device is busy (which it shouldn't be coz it doesn't even play the kde error beeps) or my sound card is not configured properly.

when i do a
modprobe sb io=0x220 irq=5 dam=1 dam16=3
it tells me that the device or resource is busy... why is this?

i've got a creative vibra card.

Creative vibra 128 pci cards use the es1371 module.

thanks Aussie!
a simple
modprobe es1371
did the trick! it's dandy now. doh...

another question. i added this line to my /etc/lilo.conf file
append = "hdb=ide-scsi"

but i don't think that was effected. how to do this? (i boot from the floppy)...

If you want to have the same kernel on a floppy like you have on your system, after you have compiled your kernel you can give this command:
Of course you have to be in the same dir where your bzImage resides or put the pathname to your freshly compiled bzImage in the cp command. Also, no mounting of the floppy is necessary.
This makes you a bootable disk without lilo but with the kernel you had just built.

ok thanks!