does /ect/sysconfig/network-scripts/ifcfg-eth0 have a line "BOOTPROTO=dhcp"? Or "IPADDR=xxx.xxx.xxx.xxx" <---replace with your assigned IP? (that's for static setup)

vectordrake;

there is a line as

'BOOTPROTO=static' and another line as
'IPADDR=139.179.217.2'

BTW, /lib/modules/2.4.21-0.31mdk/kernel/drivers/net is likely where you'd find the network drivers.

That card is supposed to be hotpluggable. Can you try an experiment and boot without the card in and then insert it? Have you done such a thing before?

vectordrake;

yes there is '8139too.o.gz' in /lib/modules/2.4.21-0.13mdk/kernel/drivers/net.

there is also '8139cp.o.gz' (i don't know if this information is helpful or not)

and did the experiment. After booting i tried ifconfig eth0 but it could not find it. After inserting i tried the same command and it found the eth0...

Since the card is reading as version C, which is a special chipset, I guess, try modprobe 8139cp and see if you can get online.

vectordrake;

modprobe 8139cp gave an error...
it says;

/lib/modules/2.4.21-0.31mdk/kernel/drivers/net/8139cp.o.gz: init_module : No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.

modprobe: insmod /lib/modules/2.4.21-0.31mdk/kernel/drivers/net/8139cp.o.gz failed
modprobe: insmod 8139cp failed

Okay, how old is your laptop? The yenta_socket mocule is a lot newer than the i82092 and i82365 modules. Perhaps you may have better luck with one of those instead of yenta_socket. If you boot without the card in, does Mandrake get excited and say "the card is gone!"? If you you then plug it back in, what modules load? Can you list them? I know you just did, but there's got to be something to this (perhaps a polite but insistant email to the manufacturer, who clearly states linux is supported, may yeild results).

****
there is also '8139cp.o.gz' (i don't know if this information is helpful or not)
***


extract that .gz file in the same folder which will give you the .o file .and then try a modprobe and insmod.
tar - zxvf 8139cp.o.gz

thats whats really you should have done a long time back. but i thought you said that a folder like that does not exist ??

once this is done make sure you add the line

alias eth1 8139cp

in modules.conf.

should have you up and running

and like vector said . try the cp version coz thats the chipset you seem to be using which would give you 8139cp.o instead of 8139too.o

vectordrake;

i am using an Compaq Armada 2333 and it is quite an old laptop (maybe more than 4 years old). I will write a mail to Compaq and inform you about the reply...

--- post again after i do the other things you and cyrus_the_yrus told...

Try unloading yenta_socket and replacing it with one of the other pcmcia bridges instead (do a lspci to find out which one it is)

vectordrake;

- i could not understand what you mean by saying "The yenta_socket mocule is a lot newer than the i82092 and i82365 modules. Perhaps you may have better luck with one of those instead of yenta_socket". Where am i using yenta_socket? how can i change it?

- after inserting the card two new modules are loaded. They are 8139too and mii.


cyrus_the_yrus;

-tar - zxvf 8139cp.o.gz does not work... The error message is as the following...

tar: This does not look like a tar archive
tar: Skipping to next header
tar: Error exit delayed from previous errors

and i want to ask something!!!

I am trying to compile 8139too.c ... write the command "make" and it gives this error, what does this mean?

make: *** No rule to make target '/usr/include/linux/version.h', needed by '8139too'. Stop.


Thanks A LOT

When you make kernel modules, you need all of the kernel source to compile against. Do you have a kernel source? ls -l should show a symbolic link from that to tour actual kernel source version. You already have the module. Don't bother compiling it again.

vectordrake;

i dont have /usr/src/linux...


what i have is...

/usr/src/RPM/RPMS/ and in this location there are 7 directories which are...

athlon
i386
i486
i586
i686
k6
and noarch

all of these directories are empty...

Therefore you can't compile a kernel module. You need a kernel to compile against.