Page 1 of 1

[Solved] How to exchange ethernet device driver?

Posted: Wed 14 Oct 2015, 04:48
by Graf_Koks
I have a new computer and want to use my puppy which I have saved and configured on an usb-device and which successfully runs on an old machine (http://murga-linux.com/puppy/viewtopic.php?t=101288).

On the new computer, Precise-Puppy is not detecting the ethernet device. What I know is, that the old machine uses the r8169 driver. With Ubuntu, the new machine uses the e1000e driver (via lspci -v) which works fine. The same (similar?) driver is also part Precise-Puppy.

I added the e1000e module to be loaded when Precise-Puppy is booting and lsmod shows the module, similar as if Ubuntu is loaded. But if I run lspci -n via Ubuntu, I get "Kernel driver in use: e1000e" which is missing using Precise-puppy.

Anyone any idea what I missed? Do I have to blacklist the r8169-module?

Thanks in advance.

Posted: Wed 14 Oct 2015, 06:23
by cthisbear
Your old machine is a Lenovo.

http://murga-linux.com/puppy/viewtopic.php?t=101288

What are your new specs.

Chris.

Posted: Wed 14 Oct 2015, 07:58
by Graf_Koks
cthisbear wrote:Your old machine is a Lenovo.
No, the new one is a Lenovo.

What infos do you need in particular?

Posted: Wed 14 Oct 2015, 17:56
by Graf_Koks
So I checked the messages from boot via dmesg:

Something like (this is copied from https://askubuntu.com/questions/650953/ ... ot-working because I have the real output not at hand):

[ 0.847256] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[ 0.847260] e1000e: Copyright(c) 1999 - 2014 Intel Corporation.

and then there is no further message anymore.

Posted: Thu 15 Oct 2015, 05:51
by Graf_Koks
For the old machine, dmesg shows in addition to the stuff above

link up

messages for the r8169 driver. Moreover, ifconfig -a returns on the lenovo machine the lo-interface and a

usb0

No one any idea?

Posted: Fri 16 Oct 2015, 17:19
by Graf_Koks
I downloaded the current e1000e driver version:

3.2.7.1 (you can check this via modinfo)

from sourceforge and compiled it (Ubuntu 14.04 LTS uses 2.3.2). I exchanged the e1000e.ko files and loaded the new module via

modprobe e1000e

Now eth0 is working.

Regards,
Graf_Koks