I’m trying to install linux network features on two old ibm thinkcenter but I can’t have a functionnal network.
The driver used is e100 it is recognized and I have an interface eth0 for this driver.
ifconfig -a gives eth0 but is the encap:Ether indicates something wrong with this driver ?
anyway, there is no way to get an ip address using dhcp, all the other computers on the lan received the ip but those two ibm thinkcenter 8183…
there is no apipa address once dhclient finished trying to get a dhcpoffer… that is why I’m thinking this driver e100 is not the correct one or need particular options which I have no idea.
Is someone got similar issues with that kind of driver ?
with static address i can have an ip address.
problem is that the network is 192.168.1.0 and packets can’t join 192.168.1.1 the address of the gateway.
I have destination host unreachable message using ping tool.
I disabled ipv6 features and I’m using traditionnal ifup method. I enabled the firewall.
I really have no idea why dhcp is not working on this interface. The loopback interface is working so the ip stack is operationnal…
My first idea for a workaround was to change a more efficient driver for this network card but I’m unable to locate which should fit and should work better than the one probed when installing 11.2.
And due to the different changes operated I’m not sure that insmod or modprobe will set the driver to be inserted to the kernel at boot time, each time I reboot the computer I have to reload it.
I did insmod /lib/modules/…/kernel/drivers/net/3c95x.ko (ie)
then depmod -a
but there is no way to have this module inserted into the kernel, due to the fact I have not an internet connection I can’t download the kernel tools to compile the kernel to include another driver(s) into the kernel.
But I’m not sure this is a good solution…
I will check the cables and connexion slots on the hub I use.
It is the first time since suse 6.0 that I have such an issue like this one… that is very strange…
All my apologizes… there was a confusing situation because I started considering the hub where all the computers were connected was working as expected.
In reality, checking all cables one by one, connected to the dlink DE-809TC hub itself connected to a switch, only the computer connected on SLOT 1 was able to receive transmit packets !!!
e100 driver was working good from the beginning, I hope this issue hasn’t waisted your time too much :{
Thank you anyway for the help given, it may be usefull later if I got a REAL issue with a specific driver !!