e1000e NIC - networkmanager connects, wicd not

merlyn · 2012-03-09 10:45:19

Hi all,

I have a problem with my Thinkpad X200 laptop and network connections. I'm using wicd, but ethernet network card is not working with wicd. In dmesg

[  774.445067] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  781.173517] e1000e 0000:00:19.0: eth0: changing MTU from 1500 to 576
[  781.335918] e1000e 0000:00:19.0: eth0: changing MTU from 576 to 1500
[  781.880938] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X
[  781.933354] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X
[  781.934254] ADDRCONF(NETDEV_UP): eth0: link is not ready

Changing mtu with 'ifconfig eth0 mtu 1492' as suggested by some post here (iirc) doesn't help.
However networkmanager is working with no problem with ethernet network card (but has big troubles with wireless and i really hate those new not working things as policykit, hundreds of daemons just to connect to network etc).

Does anyone faced same problem? Is there any solution other than running networkmanager for connect and then disabling it?
Thanks,
merlyn

Strike0 · 2012-03-09 14:26:25

What's your rc.conf daemon array like when you use wicd?

merlyn · 2012-03-09 16:29:59

I've tried
DAEMONS=(syslog-ng acpid dbus wicd slim)
DAEMONS=(syslog-ng !networking acpid dbus wicd slim)
and even
DAEMONS=(syslog-ng networking acpid dbus wicd slim)
but none of them works.

Strike0 · 2012-03-09 17:29:30

There is no "networking", you mean "network" there. You can try starting wicd in the background by adding a "@" before.

What happens if you stop networking daemons you currently run and then start wicd (sudo rc.d restart wicd) manually?

merlyn · 2012-03-10 09:16:59

Sure, you are right, it's network, just tested with network instead of networking, but doesn't work. I've also tried adding @ and re/staring all possiblem daemons, but still no change. The same problem appears even when running dhcpcd or dhclient.

skunktrader · 2012-03-10 09:51:04

Please delete this post

Last edited by skunktrader (2012-03-10 09:56:27)

Strike0 · 2012-03-10 14:56:18

merlyn wrote:

Sure, you are right, it's network, just tested with network instead of networking, but doesn't work. I've also tried adding @ and re/staring all possiblem daemons, but still no change. The same problem appears even when running dhcpcd or dhclient.

Please give more detail on your problem/the output of your trials next time. E.g. we cannot guess what the result of your manual daemon start is.. Done? Fail? Also the output of your dhcp is unclear. Does it timeout or not find an interface?

You will have seen from other threads here that the e1000e driver is not unproblematic generally.
If you just want to avoid networkmanager, another option clearly is to use network to setup the eth link. Personally I never had problems with network and another connection manager in conjunction, but there are other experiences also.

cfr · 2012-03-12 01:31:01

Can you get it working manually i.e. without using either networkmanager or wicd?

Arch Linux

#1 2012-03-09 10:45:19

e1000e NIC - networkmanager connects, wicd not

#2 2012-03-09 14:26:25

Re: e1000e NIC - networkmanager connects, wicd not

#3 2012-03-09 16:29:59

Re: e1000e NIC - networkmanager connects, wicd not

#4 2012-03-09 17:29:30

Re: e1000e NIC - networkmanager connects, wicd not

#5 2012-03-10 09:16:59

Re: e1000e NIC - networkmanager connects, wicd not

#6 2012-03-10 09:51:04

Re: e1000e NIC - networkmanager connects, wicd not

#7 2012-03-10 14:56:18

Re: e1000e NIC - networkmanager connects, wicd not

#8 2012-03-12 01:31:01

Re: e1000e NIC - networkmanager connects, wicd not

Board footer