Realtek RTL8139/810x Family Fast not working (Hardy 8.04)

Bug #215450 reported by Blackpaw
24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Installed Kubuntu 8.04 via the wubi installer

No network access - eht0 is found but won't acquired a ip address via dhcp
Tried setting a static address via /etc/network/interfaces. Did not work either
No apparent errors in dmesg

Previous Ububtu LiveCD's (7.10) have acquired a ip lease via DHCP with no problems.

Network Card (on motherboard):
  Realtek RTL8139/810x Family Fast

Revision history for this message
romeudu (eduardo-kees) wrote :

I have this problem to!!!!

My laptop use a Realtek RTL8139!!!

Instaled Ubuntu 8.04 and No network access, the Kernel know my network card, no apparent errors in log system....but no Work.

Before i use Ubuntu 7.10 no problem.

Revision history for this message
Blackpaw (lindsay-mathieson-optusnet) wrote :

I resolved this manually by editing the /etc/network/interfaces file:

iface wlan0 inet dhcp
wireless-essid blackpaw
wireless-channel 6
wireless-key [1] XXXXXXX open [1]
auto wlan0

Channel 6 is not the default for my country (AU) but there's to much interference on the normal channel so I use Channel 6 - perhaps that is the problem?

Revision history for this message
Leeland Heins (leeh) wrote :

I am also having the same problem. I don't think the solution suggested by Blackpaw will work because he is talking about WiFi, and the problem I am having is with the RTL8139 which is a wired Ethernet interface.

Revision history for this message
RafaCortes (r-cortes-jimenez) wrote :

I have the same problem with ubuntu 8.04.
My computer is Laptop Asus Z92M
The wired ethernet interface NO WORK.
I don't find one solution for this critical bug!!! without Ethernet is not possible to work.

Revision history for this message
RoutineT (routinet) wrote :

Can confirm here also. Installed Ubuntu 8.04 on an Intel D945GCLF with Realtek 8101e. After install, the network was found, but DHCP failed during discovery. A static IP assignment does not work.

I noticed that the r8169 module was installed. I removed it (sudo rmmod r8169) and attempted to replace it with the r8101 package from Intel's site (r8101-1.006.00.zip). That package would not compile. I then downloaded the r8101 package from Realtek's site (r8101-1.009.00.tar.bz2), and that installation went fine. On reboot, the connection worked. On next reboot, it did not. Looking at lsmod, both r8169 and r8101 were listed. I blacklisted r8169 with /etc/modprobe.d/blacklist and rebooted. The connection did not work, and the r8169 package was STILL listed under lsmod.

I have found that I can consistently get the connection working by using modprobe r8169 and rebooting. I have not found any way to keep r8169 from being loaded.

During a failure, lspci reports (the entire entry):

01:00.0 Ehternet controler [0200]: Realtek Semiconductor Co., Ltd. RTL8101E PCI Express Fast Ethernet controller [10ec:8136] (rev ff) (prog-if ff)
        !!! Unknown header type 7f

During a success, lspci reports (partial entry, first two lines):

01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E PCI Express Fast Ethernet controller [10ec:8136] (rev 02)
        Subsystem: Intel Corporation Unknown device [8086:0001]

During success or failure, dmesg reports the same. Here is a sample:

[ 19.806419] r8169 Gigabit Ethernet driver 2.2LK loaded
[ 19.806468] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
[ 19.806500] PCI: Setting latency timer of device 0000:01:00.0 to 64
[ 19.806517] r8169 0000:01:00.0: unknown MAC (27a00000)
[ 19.807088] eth0: RTL8169 at 0xffffc20000170000, 00:1c:c0:5d:69:93, XID 24a00000 IRQ 508
[ 33.954513] r8169: eth0: link up
[ 33.954528] r8169: eth0: link up

eth0 is always found, and the link is always reported as up. ifdown/ifup work as expected, but dhclient will not find a DHCP server during a failure state.

I'm unsure if this is related, but during shutdown I'm receiving some error messages related to nm_hal_deinit() and others. They go by quickly, so I have not been able to record them. Is there a log anywhere that should receive these messages? I'm also getting an intermittent failure to boot, around 1 out every 5 attempts. The failure comes after the GRUB pre-menu countdown ("press <ESC> for menu"), after the "kernel alive" message, but before "Loading...please wait" appears at the top of the screen. The screen will blank and what appears to be a log output will scroll by, with the last line reporting "trying to release idle task". Not verbatim, but I've been unable to locate these messages in any log either. The top of the scroll that I can see starts at [17.xx], so I'm pretty sure there's a bit I'm missing.

Agostino Russo (ago)
Changed in wubi:
status: New → Invalid
Revision history for this message
Matt (meh106) wrote :

I can confirm I am seeing the same problems as RoutineT using 8.04 server edition (kernel 2.6.24-19-server #1 SMP Wed Aug 20 23:54:28 UTC 2008) - both the fault with the built in ethernet controller; plus the intermittent failure to boot.

Revision history for this message
Novi_Andrea (andreacorti84) wrote :

I can confirm too. I try tooday the new Ubuntu 8.10 version to see if the bug was fixed, but no way, it doesn't connect with DHCP and also with manual setting!! The same problem in last Debian Release that i try to install last week.

Revision history for this message
Khristian Alexander Schönrock (der-kosak) wrote :

I can confirm this bug too on Ubuntu 8.10. I have a Foxconn A6VMX motherboard which has the rtl8101e onboard network adapter, and it is unable to connect via DHCP on my LG ADSL modem (LAM 400c). The strange thing is that, when I connect my PC directly to the modem, "sudo dhclient eth0" says "send_packet:message too long" and can't connect to anything else anymore until reboot. Now, if I connect the modem to another machine I have (running Windows XP and with ICS set up), the XP machine gets a connection, and my machine connected to the XP machine gets a DHCP address with no further problems.

Revision history for this message
Brian Murray (brian-murray) wrote :

Khristian - you are experiencing bug 274069 where the MTU for your network interface is set to a lower number than it should be. You can workaround this is issue by removing 'interface-mtu' from 'request' section of '/etc/dhcp3/dhclient.conf'. Thanks!

Revision history for this message
Paul L (plakra) wrote :

I was going to raise this as a separate bug but might be related here. I installed Ubuntu server 9.04 on a PIII with an old 3com network card. Everything worked with the card recognised and using eth0 but I discovered it was only connecting at 10 meg. I discovered this is a known issue and found it too much hassle to change the settings on the card. Easier to replace it with a new card. The new card was from Maplin in the UK and has the Realtek chipset. I put the card in the same PCI slot as the 3com and booted up to find the network not working. Without labouring this, for some reason the card is allocated eth1 during bootup. There is a line saying:
udev: renamed eth0 to eth1
I renamed eth0 to eth1 in /etc/network/interfaces, restarted networking with /etc/inet.d/networking restart, and the network now works normally at 100 meg.
I assume the system has some memory of the old card and for that reason is allocating eth1 but is not updating the interfaces file to match.

Revision history for this message
Philip Muškovac (yofel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in the kernel.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Can you still reproduce this bug? Which Ubuntu version do you use?

summary: - Realtek RTL8139/810x Family Fast not working u(Hardy 8.04)
+ Realtek RTL8139/810x Family Fast not working (Hardy 8.04)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
no longer affects: wubi
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.