(K)networkmanager unable to connect with eth0, but with wlan0

nils · 2010-09-27 20:58:59

Hello,

I'm running Archlinux within a few days on my new lenovo thinkpad, before I used gentoo on another notebook. Nearly everything runs well except networkmanager. I installed it and the knetworkmanager, too. Connecting to a wireless connection works very well, if the WLAN is on, it connects automatically. But it does not work with a wired LAN connecton, Knetworkmanager always says „Cable unplugged". I didn't try out to boot with cable already plugged in.
Here the important parts of my rc.conf:

#eth0="dhcp"

INTERFACES=(!eth0 !wlan0)

DAEMONS=(@syslog-ng dbus @hal !netfs !network @crond @alsa @bluetooth networkmanager @ntpd @samba kdm)

That's all as it is described in the wiki, iirc.

Thanks for help.

Regards,
Nils

andr3as · 2010-09-27 21:40:55

Hi,

does the kernel recognize your ethernet chipset? I.e. does eth0 even exist? For example, older kernels would not recognize the ethernet chip of my acer timelineX laptop, but it worked with a newer kernel.

Greetings
Andr3as

karol · 2010-09-27 21:55:13

andr3as wrote:

Hi,
does the kernel recognize your ethernet chipset? I.e. does eth0 even exist? For example, older kernels would not recognize the ethernet chip of my acer timelineX laptop, but it worked with a newer kernel.
Greetings
Andr3as

Exactly.
Post the output of 'ifconfig -a'.

nils · 2010-09-28 16:25:08

Hi,

[nils@Eagle ~]$ ifconfig -a
eth0      Link encap:Ethernet  HWaddr F0:DE:F1:01:0B:86  
          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
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:20 Memory:f2400000-f2420000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:219 errors:0 dropped:0 overruns:0 frame:0
          TX packets:219 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:8099 (7.9 Kb)  TX bytes:8099 (7.9 Kb)

wlan0     Link encap:Ethernet  HWaddr 00:24:D7:39:F9:CC  
          inet addr:192.168.178.34  Bcast:192.168.178.255  Mask:255.255.255.0
          inet6 addr: fe80::224:d7ff:fe39:f9cc/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3551 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3922 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2038590 (1.9 Mb)  TX bytes:574612 (561.1 Kb)

As 'lspci' displays this is my ethernet hardware:

00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 06)
03:00.0 Network controller: Intel Corporation WiFi Link 6000 Series (rev 35)

The kernel is btw from arch repo 2.6.35.

Regards,
Nils

P.S.: During the arch installation (before using networkmanager) eth0 worked well.

Last edited by nils (2010-09-28 16:27:01)

karol · 2010-09-28 16:46:39

You wlan is running - UP BROADCAST RUNNING MULTICAST - and your eth0 is not. I have no idea how networkmanager works, try to get and IP manually.

I think your module gets loaded, but you can check it:

lspci -v | grep -i -A20 ethernet

to see which kernel module do you need and then check

lsmod | grep <modulename>

if it's loaded. Try to load it by hand and see if it starts working then.

Boot with the cable plugged in and also check it on another computer if the cable is OK - ti maybe a hardware fault.

Last edited by karol (2010-09-28 16:50:44)

nils · 2010-09-28 19:10:10

I see my incomplete knowledge takes revenge

The cable was all right, because it worked with another computer.
As you expected the kernel module was not loaded, here it would be called 'e1000e'. When booting with cable plugged in, the connection works
So I think it would be right to add 'e1000e' to MODULES=() in /etc/rc.conf ?

Thanks for the help!

Regards,
Nils

karol · 2010-09-28 19:12:22

Do you have 'MOD_AUTOLOAD="yes"' in your rc.conf? If so, something's not right. If not, enable it, or do as you suggested: add 'e1000e' to MODULES=().

nils · 2010-09-29 15:14:51

MOD_AUTOLOAD is enabled. I don't know what goes wrong then, but I put "e1000e" into MODULES and now everything works well.

Thanks,
Nils

Arch Linux

#1 2010-09-27 20:58:59

(K)networkmanager unable to connect with eth0, but with wlan0

#2 2010-09-27 21:40:55

Re: (K)networkmanager unable to connect with eth0, but with wlan0

#3 2010-09-27 21:55:13

Re: (K)networkmanager unable to connect with eth0, but with wlan0

#4 2010-09-28 16:25:08

Re: (K)networkmanager unable to connect with eth0, but with wlan0

#5 2010-09-28 16:46:39

Re: (K)networkmanager unable to connect with eth0, but with wlan0

#6 2010-09-28 19:10:10

Re: (K)networkmanager unable to connect with eth0, but with wlan0

#7 2010-09-28 19:12:22

Re: (K)networkmanager unable to connect with eth0, but with wlan0

#8 2010-09-29 15:14:51

Re: (K)networkmanager unable to connect with eth0, but with wlan0

Board footer