root = /dev/hda2
image = /boot/vmlinuz
label = Backtrack
read-only


root = /dev/hda4
image = /boot/vmlinuz
label = Slackware
read-only




so this is correct ?

Yes, run lilo in Backtrack and reboot, I bet it will automatically find the netcard and load the module on next slackware boot

[edit]
You deleted /etc/modprobe.d/e-100.ko right ?

haha when i choose slackware on lilo , it boots on backtrack lolz


hmmm checking what i did wrong

edit : when i choose BT , it boots on Slack and vice et versa ...


and slackware is still running the 2.6.21.5

Ok, lilo multiboot is not easy :/ I think the root lines before image lines in lilo.conf is not correct...
One quick fix would be:
Boot in Backtrack, edit lilo.conf again, redo what I said sorry (put the image line before the root lines)
make a temp mount point in /mnt, say mkdir /mnt/hd
mount slackware in /mnt/hd (mount /dev/hda4 /mnt/hd)
find the real slackware kernel file name: ls -l /mnt/hd/boot/vmlinuz
copy slackware kernel file in backtrack /boot (cp /mnt/hd/boot/<slackware kernel> /boot)
and edit lilo.conf and change the image line for slackware (change it to the slackware kernel name)
run lilo and reboot

JESUS Christ i love you

Many thanks for the help

i did a lot of search on the web but i could n have done without you guys


keefaz are u an expert with dual screen and slackware too ? /lol

That worked ? Slackware boots ok ? no problem with /sbin/netconfig ?
If yes, cool There must be a more elegant way to multiboot with lilo though...

yes yes it worked thanks again

Congratulation dude.

lilo is easy but i like the grub's way.

CU.

For lilo I think the trick is to install lilo on slackware,
do a single boot config on slackware /etc/lilo.conf with boot=/dev/hda4 instead of boot=/dev/hda
run lilo on /dev/hda4 (so it will be installed on hda4 DBR, /sbin/lilo /dev/hda4)
Boot in Backtrack and delete slackware lines in Backtrack lilo.conf and replace with:
other=/dev/hda4
label=Slackware
and run lilo (/sbin/lilo) to take the change in account.
If you don't fix lilo multiboot, it will be harder to install a new kernel in slackware
(need to copy Slackware kernel in Backtrack /boot, boot Backtrack, run lilo, not convenient)

But do some search on lilo, as I could be wrong again

Hi,
The command is 'ifconfig'

Whenever you receive a error with a request for a command you should provide back (post) the error. This will assist in diagnosis of the problem.

Hi,

After reading through the whole thread now. It does seem the OP was using a shared kernel and not booting the Slackware. The OP should run lilo on his Slackware partition then include the proper configuration in the BT 'lilo.conf' with a stanza pointing to the Slackware lilo.

Edit:In the future you should post the information requested along with any unedited error information.