I’ve got a Dell Latitude E6400 with Intel network card (details of lspci below), which worked fine with 11.4 and cannot detect even a cable connect when I boot to 12.1. Both systems are clean installs on separate hdds, so it’s not an unclean upgrade issue as far as I can see. Also ethtool cannot access the device anymore:
# ethtool eth0
Settings for eth0:
Cannot get device settings: No such device
Cannot get wake-on-lan settings: No such device
Cannot get message level: No such device
Cannot get link status: No such device
No data available
It’s the regular 3.1.9-1.4-desktop kernel on 12.1, network controlled through networkmanager. The kernel log says “eth0: link is not ready”, all dhcp and direct connection attempts time out.
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
Subsystem: Dell Device 0233
Flags: fast devsel, IRQ 22
Memory at f6fe0000 (32-bit, non-prefetchable) [disabled] [size=128]
Memory at f6fdb000 (32-bit, non-prefetchable) [disabled] [size=4]
I/O ports at efe0 [disabled] [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [e0] PCI Advanced Features
Kernel driver in use: e1000e
Thanks for any help/hints!
(how do I cross-post on kernel and 64bit branches of the forum? )[/size][/size][/size]
You can post the output into SuSE Paste here: SUSE Paste
Make sure to select Delete After (in middle bottom) as Never. Put in your** forum name** and give it an appropriate title. Then, post the web link here in a forum message for your final SuSE Paste product. Make sure to remove any wireless passwords, should they be found and exist. The resulting data can helpful to determine just what might be wrong on your PC.
Thanks for the hint, I’ve generated the info file and will attach it in the next message. However to keep things short and simple I also add the output from /sbin/ifconfig here to reply on your comment:
The error from ethtool eth0, just means there is no eth0 but don’t assume that is its name.
Apparently the device is there and it’s called eth0. I can also manipulate it via ifconfig, but with no real success, as the link detection fails.
eth0 Link encap:Ethernet HWaddr 00:26:B9:B3:2F:5F
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
I will give it a try, though it refers to kernels up to 2.6.35. In my case it worked perfectly up to kernel 184.108.40.206 inclusive, and stopped only with the 3.x series when I installed the OSE12.1.
A few snippets from the logs with old(working) and new(failing) kernels:
both have lines with “e1000e 0000:00:19.0: PME# disabled”, suppose it’s harmless
old: e1000e 0000:00:19.0: irq 41 for MSI/MSI-X
new: e1000e 0000:00:19.0: irq 46 for MSI/MSI-X
e1000e 0000:00:19.0: BAR 0: set to [mem 0xf6fe0000-0xf6ffffff] (PCI address [0xf6fe0000-0xf6ffffff])
e1000e 0000:00:19.0: BAR 1: set to [mem 0xf6fdb000-0xf6fdbfff] (PCI address [0xf6fdb000-0xf6fdbfff])
e1000e 0000:00:19.0: BAR 2: set to [io 0xefe0-0xefff] (PCI address [0xefe0-0xefff])
Just in case anyone else hits this problem - here’s the solution (learned from e1000-devel mailing lists):
The driver enters powermanagement mode D3 and doesn’t wake up when it should. Obviously the newer kernels (in 12.2) have this fixed already, one may expect that it will eventually be backported to the kernel in 12.1.
The explicit method to turn the card on is to run (as root):
echo on > /sys/bus/pci/devices/0000:00:19.0/power/control
instead of 0000:00:19.0 put the actual pci address of your card (find it via lspci).