Realtek 8111C chip - still not working at 1000 MBit on 12.04 LTS

Bug #1091049 reported by LAZA
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I got new hardware and now mentioned the problem again and again...

Hardware:
Mainboard: Gigabyte GA-MA790GP-UD4H (rev. 1.0); BIOS F7c
NIC: Realtek 8111C chip (10/100/1000 Mbit)
http://www.gigabyte.de/products/product-page.aspx?pid=3003#sp

Cable: Cat5e and higher
Router: AVM FRITZ!BOX Fon WLAN 7360 SL in Port 1/2
http://www.avm.de/de/Produkte/FRITZBox/FRITZ_Box_7360/index.php

.

Description: Ubuntu 12.04.1 LTS
Release: 12.04

Linux xubuntu3 3.2.0-34-generic #53-Ubuntu SMP Thu Nov 15 10:48:16 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

lsmod:
Module Size Used by
usb_storage 49198 0
pci_stub 12622 1
vboxpci 23200 0
vboxnetadp 25670 0
vboxnetflt 23441 0
vboxdrv 320210 3 vboxpci,vboxnetadp,vboxnetflt
parport_pc 32866 0
ppdev 17113 0
vesafb 13844 1
snd_hda_codec_hdmi 32474 1
snd_hda_codec_realtek 224173 1
snd_hda_intel 33773 7
snd_hda_codec 127706 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 13668 1 snd_hda_codec
snd_seq_midi 13324 0
snd_pcm 97188 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_rawmidi 30748 1 snd_seq_midi
snd_seq_midi_event 14899 1 snd_seq_midi
sp5100_tco 13791 0
snd_seq 61896 2 snd_seq_midi,snd_seq_midi_event
snd_timer 29990 2 snd_pcm,snd_seq
snd_seq_device 14540 3 snd_seq_midi,snd_rawmidi,snd_seq
fglrx 4713309 373
psmouse 97443 0
serio_raw 13211 0
edac_core 53746 0
edac_mce_amd 23709 0
snd 78855 24 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
it87 43384 0
hwmon_vid 12827 1 it87
k10temp 13166 0
i2c_piix4 13301 0
mac_hid 13253 0
soundcore 15091 1 snd
snd_page_alloc 18529 2 snd_hda_intel,snd_pcm
wmi 19256 0
lp 17799 0
parport 46562 3 parport_pc,ppdev,lp
pata_atiixp 13204 0
r8169 62099 0

ethtool:
Settings for eth0:
 Supported ports: [ TP MII ]
 Supported link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         1000baseT/Half 1000baseT/Full
 Supported pause frame use: No
 Supports auto-negotiation: Yes
 Advertised link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         1000baseT/Half 1000baseT/Full
 Advertised pause frame use: Symmetric Receive-only
 Advertised auto-negotiation: Yes
 Link partner advertised link modes: 10baseT/Half 10baseT/Full
                                      100baseT/Half 100baseT/Full
 Link partner advertised pause frame use: Symmetric Receive-only
 Link partner advertised auto-negotiation: Yes
 Speed: 100Mb/s
 Duplex: Full
 Port: MII
 PHYAD: 0
 Transceiver: internal
 Auto-negotiation: on
Cannot get wake-on-lan settings: Operation not permitted
 Current message level: 0x00000033 (51)
          drv probe ifdown ifup
Cannot get link status: Operation not permitted

Attached is the dmesg, and requested cat /proc/version_signature > version.log, sudo lspci -vnvn > lspci-vnvn.log

Revision history for this message
LAZA (laza74) wrote :
Revision history for this message
LAZA (laza74) wrote :
Revision history for this message
LAZA (laza74) wrote :
description: updated
description: updated
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: precise
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.7 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-raring/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
LAZA (laza74) wrote :

atm i got problems to install the mainline kernel, 'sudo dpkg -i *.deb' comes back within seconds and no kernel installed. Perhaps i have to uninstall fglrx and virtualbox...

Meanwhile, i installed the 3.5-kernel which is provided by Ubuntu and there the problem is not fixed!

I hope, this will help a bit to approach to the source of error.

Revision history for this message
LAZA (laza74) wrote :
Revision history for this message
LAZA (laza74) wrote :
Revision history for this message
LAZA (laza74) wrote :

I managed the installation of the Mainline Kernel 3.7.1 and got while the installation errors about missing firmware for the NIC - log is attached.

Revision history for this message
LAZA (laza74) wrote :

Okay, here some more attachments, that might help

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
LAZA (laza74) wrote :
Revision history for this message
LAZA (laza74) wrote :

Changed to original Realtek module r8168 - still only 100 MBit and works not as flawless as the r8169. :-(

For those who wanna try it:
http://www.rvdavid.net/how-to-get-gigabit-speeds-from-rtl81118168b-pci-express-gigabit-ethernet-controller-on-ubuntu-linux/

Revision history for this message
LAZA (laza74) wrote :

So, now we have the problem:

Since some days my network information says "speed: 100 Mb/s".

In use is the "r8169" kernel modul, with the Linux 3.5.0-21-generic #32~precise1-Ubuntu kernel, and ethtool gives me this:

 Supported ports: [ TP MII ]
 Supported link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         1000baseT/Half 1000baseT/Full
 Supported pause frame use: No
 Supports auto-negotiation: Yes
 Advertised link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         1000baseT/Half 1000baseT/Full
 Advertised pause frame use: Symmetric Receive-only
 Advertised auto-negotiation: Yes
 Link partner advertised link modes: 10baseT/Half 10baseT/Full
                                      100baseT/Half 100baseT/Full
                                      1000baseT/Half 1000baseT/Full
 Link partner advertised pause frame use: Symmetric Receive-only
 Link partner advertised auto-negotiation: Yes
 Speed: 1000Mb/s
 Duplex: Full
 Port: MII
 PHYAD: 0
 Transceiver: internal
 Auto-negotiation: on
 Supports Wake-on: pumbg
 Wake-on: g
 Current message level: 0x00000033 (51)
          drv probe ifdown ifup

So thanks for the attention, i may be help you out if there are more questions.
Maybe it is the upstream kernel from Ubuntu (but which did not work for the first time i tried!)...

Revision history for this message
LAZA (laza74) wrote :

Sorry for the confusion!

The sentence have to read (as in the output of ethtools to see):
Since some days my network information says "speed: 1000 Mb/s" !!!

But i'm still unsure what was the trigger to get gigabit network working...

Revision history for this message
LAZA (laza74) wrote :

Some more infomations:

I buyed a SSD and did a new installation, 1000 MBit working out of the box!

Got some problems before with an Windows 8 installation (shut NIC down forever!) but now it works perfectly.
So anybody has to test more.

Thanks in advance!

Revision history for this message
Christopher M. Peñalver (penalvch) wrote :

LAZA, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1091049/comments/15 regarding this being fixed with a reinstall. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

tags: added: needs-kernel-logs needs-upstream-testing regression-potential
Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers