Does not recognize RTL-8168/8169/8101/8111 wired adapters.

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

Bug Description

Binary package hint: network-manager-gnome

During Ubuntu 6.06 installation no network card is recognized. After installation both eth0 and eth1 are available and work appropriately. This pattern applies on two separate notebooks. eth1 is Intel's IPW 3945 and network-manager-gnome can be used to connect to available wireless networks. eth0 is a Realtek RTL-8169SC Gigabit Ethernet controller and is not available in network-manager-gnome. Of course there is no auto-switching to a wired network so network-manager-gnome does not work properly.

Relevant lspci entries (pre sudo update-pciids)

0000:03:00.0 Network controller: Intel Corporation: Unknown device 4222 (rev 02)
0000:05:01.0 FireWire (IEEE 1394): Ricoh Co Ltd: Unknown device 0832
0000:05:01.1 0805: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
0000:05:01.2 System peripheral: Ricoh Co Ltd: Unknown device 0843 (rev 01)
0000:05:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a)
0000:05:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd.: Unknown device 8167 (rev 10)

Relevant lspci entries (post sudo update-pciids)

0000:03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
0000:05:01.0 FireWire (IEEE 1394): Ricoh Co Ltd: Unknown device 0832
0000:05:01.1 0805: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
0000:05:01.2 System peripheral: Ricoh Co Ltd: Unknown device 0843 (rev 01)
0000:05:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a)
0000:05:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169SC Gigabit Ethernet (rev 10)

Both appear in HAL (lshal | grep eth)

  net.interface = 'eth1' (string)
  linux.sysfs_path = '/sys/class/net/eth1' (string)
  net.interface = 'eth0' (string)
  linux.sysfs_path = '/sys/class/net/eth0' (string)

This issue appears to stem from Ubuntu's installer not recognizing the nic.

Revision history for this message
Carl Richell (carlrichell) wrote :

Update - After plugging in a USB ethernet adapter and restarting network manager recognizes the USB ethernet adapater but not the internal Realtek adapter.

Maybe this bug if filed in the wrong place. Appears to be a problem with the Realtek RTL-8169SC adapter.

Revision history for this message
William Grant (wgrant) wrote :

Can you please check if there is any manual configuration for eth0 in /etc/network/interfaces? If there is, Network Manager won't touch it.

Changed in network-manager:
status: Unconfirmed → Needs Info
Revision history for this message
Carl Richell (carlrichell) wrote :

/etc/network/interfaces only contains only the loopback device. This occurs on two separate laptops. NM works perfectly on eight others machines I work with.

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

Is this using the Live CD? Is the driver for the card being loaded? How exactly is this related to NetworkManager and not the installer?

Revision history for this message
Scott Robinson (scott-ubuntu) wrote : Re: [dapper] Does not recognize RTL-8169SC wired adapter.

Also, can you take a look at bug 59981 and let me know if that helps?

Revision history for this message
Carl Richell (carlrichell) wrote :

Is this using the Live CD? - Tested installation via LiveCD and Alternate install CD.

Is the driver for the card being loaded? - yes the r1000 driver is loaded

How exactly is this related to NetworkManager and not the installer? Maybe it is related to the installer; however, when I plug in a USB ethernet adapter it shows up in NM as a wired device. I also took a look at bug 59981 and this looks different in that the network devices (eth0 and eth1) are both visible in HAL.

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

Can you attach the results of "lshal"?

Revision history for this message
Carl Richell (carlrichell) wrote :

lshal is attached

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

There appears to be some common issue with the underlying driver. I'll have more time, this weekend, to help with tracking down the problem.

I have expanded the bug name to include all affected cards.

Revision history for this message
Carl Richell (carlrichell) wrote :

Thanks Scott - your help is very much appreciated over here

Revision history for this message
SFAOK (gary-breavington) wrote :

A couple of things: firstly, I think bug 63314 is a duplicate of this one. Secondly, the last daily live CD I used actually found my network card and set up my network connection automatically... however, the alternate CD for today (11th October) is still not detecting the NIC.

Revision history for this message
Tim (uwnt2bt) wrote :

I have just started using Feisty and the network-manager work great for wireless networks but I am unable to get it to connect with the RTL-8168 NIC in my laptop. I wanted to see if there was a work around or any type of fix. Network-manager always has the wired network grayed out and I have not found a way to turn it on.

Thanks,

Tim Pitts

Revision history for this message
ubunturox (ubunturox-kk) wrote :

I installed 704 on Asus Z92M with Realtek 8111/8168 PCIe card. The live CD also doesnt make the network work. It loads r8169 module but "wired connection" is greyed out. Finalyl I loaded r1000 driver and link is detected etc but doesnt get an IP from a DHCP. The DHCP server hands out the IP but the IP doesnt get assigned to the interface.

If any more info is needed, please let me know.

thanks,
Kalyan

Revision history for this message
AlexThompson (alex-thompson) wrote :

I was having the same problem as described with a Realtek 8111/8168B card, ubuntu 7.04 and network manager. I had a look at bug #86798 and it suggested unloading and reloading the module, after trying that, network manager found the wired network and successfully connected. The output from dmesg also shows the eth0 link being brought up.

Revision history for this message
Chris Wagner (chris-wagner) wrote :

Is this still a problem for anyone? And, if so, is it possible that it's a duplicate of #86798.

Revision history for this message
AlexThompson (alex-thompson) wrote :

This still effects me, but it does look like a duplicate of #86798 (At least for feisty)

Revision history for this message
StephW (swacongne) wrote :

With the r8169 module from Realtek (r8169-6.002.00), I "just" have to issue in root
#ethtool -s eth1 speed 1000 duplex full autoneg on
It seems that the card has some difficulties to configure itself...

My conf is Ubuntu Feisty
uname -a => Linux pc-0012 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux
lshw -C network => (just the extract for this card)
  *-network
       description: Ethernet interface
       product: RTL-8169 Gigabit Ethernet
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 1
       bus info: pci@0a:00.0
       logical name: eth1
       version: 10
       serial: 00:14:6c:8d:45:ff
       size: 1GB/s
       capacity: 1GB/s
       width: 32 bits
       clock: 66MHz
       capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=6.002.00 duplex=full ip=xxx.yyy.zzz.ttt latency=64 link=yes maxlatency=64 mingnt=32 multicast=yes port=twisted pair speed=1GB/s
       resources: ioport:5000-50ff iomemory:8c000000-8c0001ff irq:20

Revision history for this message
StephW (swacongne) wrote :

Eventually, I decided to edit my /etc/rc.local file in order to automate the process...

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.