ethernet card not detected.

Bug #52532 reported by Sebastian
This bug report is a duplicate of:  Bug #86798: r8169 driver does not detect link. Edit Remove
10
Affects Status Importance Assigned to Milestone
Baltix
Invalid
Undecided
Unassigned
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

On a asus a6jm laptop the ethernet card is not detected by network-manager. The card works when configured in /etc/network/interfaces. After commenting all interfaces (except "lo") wireless works but the ethernet card is not detected.
lspci output:
0000:02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.: Unknown device 8159 (rev 01)
0000:03:00.0 Network controller: Intel Corporation: Unknown device 4222 (rev 02)

I also tryied downloading and compiling the drivers from the realktek site but nothing changes.

I'm using dapper with kernel 2.6.15-25-686 smp. The kernel in the installation cd does not recognize the ethernet card at all, it was fixed in a kernel upgrade (i coudn't determine in wich kernel version)

description: updated
Revision history for this message
Steven Harms (sharms) wrote :

Please attach your /etc/network/interfaces and output of ifconfig -a and screenshots of network manager.

Changed in network-manager:
status: Unconfirmed → Needs Info
Revision history for this message
Sebastian (sebastianhgil) wrote :

Here is the output, right now I don't have a wifi access so network manager shows no networks, but the LAN cable is plugged. With this configuration there's no networking. But if I add:
auto eth0
iface eth0 inet dhcp
to "interfaces" and restart networking I have a network connection working ok but that's not managed by n-m (in both cases the n-m applet looks like in the screenshots)

Here you can find the screenshots:
http://www.flickr.com/photos/54218449@N00/

----------------------------------------------------------------------------------------------

sebas@stan:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

----------------------------------------------------------------------------------------------

sebas@stan:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:17:31:2E:30:A8
          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:169 Base address:0xc800

eth1 Link encap:Ethernet HWaddr 00:13:02:49:3D:78
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:1 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:177 Base address:0x6000 Memory:fe1ff000-fe1fffff

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:7 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:372 (372.0 b) TX bytes:372 (372.0 b)

sit0 Link encap:IPv6-in-IPv4
          NOARP MTU:1480 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:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Revision history for this message
Sebastian (sebastianhgil) wrote :

This is the output of nm-tool
Ethernet card is not listed here:

NetworkManager Tool

State: connected

- Device: eth1 ----------------------------------------------------------------
  NM Path: /org/freedesktop/NetworkManager/Devices/eth1
  Type: 802.11 Wireless
  Driver: ipw3945
  Active: yes
  HW Address: 00:13:02:49:3D:78

  Capabilities:
    Supported: yes
    Speed: 2 Mb/s

  Wireless Settings
    Scanning: yes
    WEP Encryption: yes
    WPA Encryption: yes
    WPA2 Encryption: yes

  Wireless Networks (* = Current Network)
    *wircasa: Infrastructure Mode, Freq 0.000 MHz, Rate 0 Mb/s, Strength 61%, Encrypted (WPA), Hidden

  IP Settings:
    IP Address: 192.168.1.9
    Subnet Mask: 255.255.255.0
    Broadcast: 192.168.1.255
    Gateway: 192.168.1.1
    Primary DNS: 192.168.1.1
    Secondary DNS: 0.0.0.0

Revision history for this message
9johnny (s.j.) wrote :

I have the same problem.
have a laptop with intel ipw2200 AND broadom bcm4400, using edgy:
If I do not load my wireless driver (ipw2200) at boot then I get the wired network, but no wireless. otherwise I only get wireless. It would be nice to be able to have one tool for both networks (now I use ifplugd and nm). I thing this is a problem if one has more than one net card????
regs
John

Revision history for this message
9johnny (s.j.) wrote :

Hi!
I just ound out the problem with mine, hope it helps.
If you comment out every interface line (except lo) of your /etc/network/interfaces file it works.
regs
J

Revision history for this message
Scott Robinson (scott-ubuntu) wrote :

Does this still occur in dapper? How about in edgy?

Revision history for this message
9johnny (s.j.) wrote :

sorry, it was in edgy.
 but I couldn't find this bug, to edit it.
The only thing I needed to do is to remove the lines for eth0 in /etc/network/interfaces , now it works.

Revision history for this message
Steven Harms (sharms) wrote :

Configuration error - user needed to remove interface from /etc/network/interfaces

Changed in network-manager:
status: Needs Info → Rejected
Revision history for this message
Sebastian (sebastianhgil) wrote :

Sorry, as i post in the description in my configuration the lines in /etc/network /interfaces *ARE* commented...
Please look at the comment with the nm-tool output.. the card is not being recognized by network manager

I can't test it on edgy as it is my work laptop and i don't feel like installing development version.

Thank you

Revision history for this message
Steven Harms (sharms) wrote :

Please attach /etc/network/interfaces

Revision history for this message
9johnny (s.j.) wrote :

maybe your network card doesn't detect if a cable is plugged in or not? did you try ifplugd to test?

Revision history for this message
Scott Robinson (scott-ubuntu) wrote :

Sebastian, can you please attach the results of an "lshal"?

Revision history for this message
Sebastian (sebastianhgil) wrote :

Hi, thanks for the fast replies

Steven: this is how my interface file looks:

sebas@stan:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

#auto eth0
#iface eth0 inet dhcp

J: I installed the ifplugd package but i notice no difference. Please take a look to the screenshots at http://www.flickr.com/photos/54218449@N00/ I don't have a "wired network" (red cableada) option, just "wireless network" (red inalambrica)

Scott: I've attached the output of lshal

Thanks again
Sebastian

Revision history for this message
Scott Robinson (scott-ubuntu) wrote :

Can you run a "sudo update-pciids" and copy-paste in your new "lspci -v" results? I think this may be related to bug 54411, and would like to combine the two.

Hal is detecting the net card as wireless, so NM should be picking it up. This bug is subtle and requires more information.

Changed in network-manager:
status: Rejected → Needs Info
Revision history for this message
Sebastian (sebastianhgil) wrote :

Hi Scott, I did "sudo update-pciids" and attached is the lspci -v output

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.