At least now, we may have some hint with the complete error messages
Could you post the first lines (4-5) of /etc/modprobe.d/e100.ko ?
less /etc/modprobe.d/e100.ko

Also the output with ' uname -r ', I tought the slackware 12.1 default kernel version was 2.6.24.5 (?)

You said you're using slackware 12.1 and slackware 12.1 comes with "2.6.24.5" kernel but your kernel is 2.6.21.5.

Sound likes you went back to slackware 12.

hmmmm sorry being a noob dude :/ but i don t even get the first command .

what do you mean by change to your nic ?

i type exactly the same command as you typed above and shell is returning me "module" and that's all


Once again i'm deeply sorry i m just trying to understand

NIC = Network Interface Card.

It will be eth0 or eth1 if you had two NICs.

you can know whet is your NIC with ifconfig.

Post the the result of these commands and type (ifconfig) and (uname -r) in both of slackware and backtrack.

Hmmm weird .....

Kernel is actually 2.6.21.5 on my slackware , and on my other computer i have the 2.6.24.5 wich i have installed both computers with the same cds imo ........


i did a nano /etc/modprobe.d/e100.ko and imo the file is corrupted because there is SO much ASCII char on the first line of the part of each line .....

anyway the first readable lines are line 30 :

ASCII ASCII ASCII e100,mdio ctrl[s] won t go ready
:" " " e100 s s no space for CB
" " " cannot map devices register

etc etc

Lot of line like the ones above

Then

ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII

Slackware :



ifconfig : lo Link encap inet 127.0.0.1 mask 255.255.255.0
UP Loopback runningMTU 16436 metric 1

ifconfig eth0: error fetching interface information : Device Not found

uname -r :2.6.21.5


Backtrack:
everything seems good and i can connect to the internet , i have saved my config in the rc.inet file but i have to reconfig the eth0 each time the pc is rebooting


ifconfig eth0: Link encap:ethernet HWadrr : mymac
inetaddr: myprivateaddr broadcast : x mask : mymask
interrupt:21

uname -r: 2.6.21.5

what happens if you delete /etc/modprobe.d/e100.ko and re-try a modprobe e100 ? Does it re-create it ?

Would you use a separate /boot partition by any chance ? and is this /boot partition shared by both Backtrack and Slackware ?
I have a feeling you're loading the Backtrack kernel in your Slackware system (I could be wrong)

i can delete /etc/modprob.d/e100.ko

here is the return of a new modprobe e100 :
WARNING ERROR inserting mii (/lib/modules/2.6.21.5/kernel/drivers/net/mi.ko :Invalid module format

WARNING ERROR inserting e100 /lib/modules/2.6.21.5/kernel/drivers/net/e100.ko 100:Invalid module format


hmmm my disks are like this :

HDA1: winxp
HDA2:Backtrack
HDA3:Swap
HDA4:Slackware


maybe i should delete my hda4 partition and just leave it alone , i am already using slackware at the moment on another computer

Maybe nothing is lost..
Could you post the output with:
cat /etc/fstab
cat /etc/lilo.conf

fstab :

/dev/hda3 / swap defaults 0 0
/dev/hda4 / ext3 defaults 1 1
/dev/hda1 /winxp ntfs umask=x 1 0
/dev/cdrom /mnt/cdrom auto noauto
/dev/fd0 /mnt/floppy auto noauto
devpts /dev/pts devpts gid=x
proc /proc proc defaults
tmpfs /dev/sim tmpfs defaults



i don t have installed lilo on that partition. i ve just modified lilo on my backtrack .
Do you think i need to put the backtrack lilo here ?

hmmm maybe i know what s wrong :

here is my lilo on my backtrack:

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

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


what do you guys think

The fstab is ok, so lilo.conf may be the issue
Yes, I think it would be interesting to see the backtrack /etc/lilo.conf

[edit]
I think you figured out the error now

Erm....

You DID install the kernel and modules from the Slackware install disk, right?

Yes and Yes

hehe but i have no idea about how to allow a triple boot now ... do i have to reinstall slackware WITH lilo and what should my lilo.conf after that

no, just put the root lines in Backtrack lilo.conf before the image lines
like:
...
root = /dev/hda4
image = /boot/vmlinuz
...
And run lilo in Backtrack to take change in account
But I am not lilo expert (I use grub) so I could be wrong