Before today i was using 3.8-3.towo.siduction-amd64 and switching from wired (static ip) to wireless was no problem.
Last night I upgraded with a (dist-upgrade) to 3.8-3.towo.1-siduction-amd64 and wireless has been ok. When i took my laptop to work today and plugged in the ethernet my network manager (nm-applet) does not recognize anything. After a reboot the ethernet is working fine. However any plugging or unplugging, or trying to change connections causes it to die forcing a reboot to fix.
Update: info I got from the Arch forums is that a
echo on > /sys/class/net/eth0/device/power/control
will bring it back.
Does this make it a kernel bug or a network manager bug?
all dmesg gives me is this:
[ 663.703783] e1000e: eth0 NIC Link is Down
[ 744.185566] e1000e 0000:00:19.0: irq 40 for MSI/MSI-X
[ 745.948850] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[ 745.948865] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
Update, problem persists with 3.8-4
Quote from: "Super-Nathan"When i took my laptop to work today and plugged in the ethernet my network manager (nm-applet) does not recognize anything. After a reboot the ethernet is working fine. However any plugging or unplugging, or trying to change connections causes it to die forcing a reboot to fix.
Instead of rebooting, does
ifdown eth0ifup eth0 get your internet working ?
Are you behind a firewall at work ?
Same problem with my Laptop (Thinkpad X61).
With Kernel 3.7.X no problem. With 3.8.X a always have to enter
echo on > /sys/class/net/eth0/device/power/control
to activate my eth0 (using driver e1000e).
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
I think the problem is, that the autodetection of the link status. ifplugstatus always says before subitting the command:
$ ifplugstatus
eth0: unplugged
lo: link beat detected
wlan0: unplugged
@Super-Nathan: no it not the problem of nm, the problems lies deeper in the system.
Super-Nathan: for me kernel 3.9rc4 works without this issue. Ok this only a release candidate, so maybe don't try it at a productions system :)
Quote from: "hefee"Super-Nathan: for me kernel 3.9rc4 works without this issue. Ok this only a release candidate, so maybe don't try it at a productions system :)
Great!
I just tried it in 3.8-6 and it is persisting :(
Handbook:http://manual.siduction.org/de/sys-admin-kern-upg-de.htm#kern-upgrade
apt-get install linux-image-siduction-686 linux-headers-siduction-686
No problem with realtek-ethernet
Quote from: "DeKa"Handbook:http://manual.siduction.org/de/sys-admin-kern-upg-de.htm#kern-upgrade
apt-get install linux-image-siduction-686 linux-headers-siduction-686
No problem with realtek-ethernet
The problem is with the Atheros Ethernet, not Realtek.
Perhaps can the fixed driver be backported to 3.8 siduction kernel, towo?
Hi, my Kernel:
deka@deka-laptop:~$ inxi -F
System: Host: deka-laptop Kernel: 3.8-6.towo-siduction-686-pae i686 (32 bit) Desktop: Xfce 4.10.2
Old Kernel 3.8.0:deka@deka-laptop:~$ apt-cache policy linux-headers-3.8-0.towo-siduction-686
linux-headers-3.8-0.towo-siduction-686:
Installiert: (keine)
Installationskandidat: 3.8-1
Versionstabelle:
3.8-1 0
900 http://packages.siduction.org/siduction/ unstable/main i386 Packages
deka@deka-laptop:~$ apt-cache policy linux-image-3.8-0.towo-siduction-686
linux-image-3.8-0.towo-siduction-686:
Installiert: (keine)
Installationskandidat: 3.8-1
Versionstabelle:
3.8-1 0
900 http://packages.siduction.org/siduction/ unstable/main i386 Packages
Does it run with this kernel?
@DeKa/@DeepDayze: We are talking about problems with the driver e1000e (intel network card)
Quote from: "hefee"@DeKa/@DeepDayze: We are talking about problems with the driver e1000e (intel network card)
Oh my bad thought this was the thread about the Atheros Ethernet card issues
Think I forgot to put on my glasses to post :shock:
The problem does not exist on my e1000 card, on this system installed today:
don@suzdesk:~$ inxi -v3
System: Host: suzdesk Kernel: 3.8-6.towo-siduction-amd64 x86_64 (64 bit, gcc: 4.7.2)
Desktop: KDE 4.10.2 (Qt 4.8.2) Distro: siduction 12.2.0 Riders on the Storm - kde - (201212092131)
Machine: Mobo: Intel model: D975XBX2 version: AAD53350-509
Bios: Intel version: BX97520J.86A.2813.2008.0114.2256 date: 01/14/2008
CPU: Dual core Intel Core2 CPU X6800 (-MCP-) cache: 4096 KB flags: (lm nx sse sse2 sse3 ssse3 vmx) bmips: 13867.1
Clock Speeds: 1: 2926.00 MHz 2: 2926.00 MHz
Graphics: Card: NVIDIA GT200 [GeForce GTX 260] bus-ID: 01:00.0 X.Org: 1.12.4 driver: nvidia Resolution: 1280x1024@85.0hz
GLX Renderer: GeForce GTX 260/PCIe/SSE2 GLX Version: 3.3.0 NVIDIA 304.88 Direct Rendering: Yes
Network: Card: Intel 82573L Gigabit Ethernet Controller driver: e1000e ver: 2.1.4-k port: 1000 bus-ID: 03:00.0
IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:1c:c0:1f:54:35
Drives: HDD Total Size: 300.1GB (2.7% used) 1: model: WDC_WD3000HLFS
Info: Processes: 180 Uptime: 2:56 Memory: 1152.1/3958.2MB Runlevel: 5 Gcc sys: 4.7.2
Client: Shell (bash 4.2.45) inxi: 1.8.45
For me the problem was not triggered every time. Sometimes a could boot with correct wired status.