Intel Gibabit Ethernet NIC (82541PI) operating at 100Mbps instead of 1000Mbps after upgrading to Hardy

[Damon Timm]

After upgrading from Dapper to Hardy, my Intel Gibabit Ethernet NIC (82541PI) no longer operates at gigabit speeds (1000 Mbps) -- instead, it is limited to 100Mbps.

I am using 8.06 server edition of Ubuntu (2.6.24-21-server). I have tested my intermediary hardware (switch, router, cables, etc) as well as attempted to use ethtool to force speeds of 1000 (this causes the network to not function at all, and has to be restarted).

Another user on Ubuntu Forums has posted the same problem with this model (http://ubuntuforums.org/showthread.php?p=6330511) and an older bug seems to address the same issues, albeit with different hardware (https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/86437).

I suspect that, perhaps, the correct module isn't being loaded or something and the e1000_watchdog (whatever that is) is getting a bit of the action!

Here is some relevant (I hope) output:

Description: Ubuntu 8.04.1
Release: 8.04

[sudo ethtool eth0]

Settings for eth0:
 Supported ports: [ TP ]
 Supported link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         1000baseT/Full
 Supports auto-negotiation: Yes
 Advertised link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         1000baseT/Full
 Advertised auto-negotiation: Yes
 Speed: 100Mb/s
 Duplex: Full
 Port: Twisted Pair
 PHYAD: 0
 Transceiver: internal
 Auto-negotiation: on
 Supports Wake-on: umbg
 Wake-on: g
 Current message level: 0x00000007 (7)
 Link detected: yes

[NOTE: speed is at 100Mb/s while 1000 is available]

[sudo lshw -C network]

  *-network
       description: Ethernet interface
       product: 82541PI Gigabit Ethernet Controller
       vendor: Intel Corporation
       physical id: e
       bus info: pci@0000:00:0e.0
       logical name: eth0
       version: 05
       serial: 00:0e:0c:d9:ca:1f
       size: 100MB/s
       capacity: 1GB/s
       width: 32 bits
       clock: 66MHz
       capabilities: pm pcix bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e1000 driverversion=7.3.20-k2-NAPI duplex=full firmware=N/A ip=192.168.0.200 latency=64 link=yes mingnt=255 module=e1000 multicast=yes port=twisted pair speed=100MB/s

[dmesg | grep eth0]

[ 73.939047] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
[ 90.195654] e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX

[lspci -nn]

00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge [8086:7190] (rev 03)
00:01.0 PCI bridge [0604]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge [8086:7191] (rev 03)
00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 02)
00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01)
00:07.2 USB Controller [0c03]: Intel Corporation 82371AB/EB/MB PIIX4 USB [8086:7112] (rev 01)
00:07.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 02)
00:0d.0 RAID bus controller [0104]: 3ware Inc 7xxx/8xxx-series PATA/SATA-RAID [13c1:1001] (rev 01)
00:0e.0 Ethernet controller [0200]: Intel Corporation 82541PI Gigabit Ethernet Controller [8086:107c] (rev 05)
00:0f.0 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43)
00:0f.1 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43)
00:0f.2 USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev 04)
01:00.0 VGA compatible controller [0300]: nVidia Corporation NV4 [RIVA TNT] [10de:0020] (rev 04)

I haven't tried to upgrade this server to 8.10 -- I prefer to stick with the LTS version since it is an NAS, I would rather the stability. I also don't have an easy way to stick this card in another machine (all my other computers are Macs). If possible, would be great if an "in place" fix could be had.

EDIT: The OP in the forum post has reported that a clean install of Intrepid does not fix the issue.

Please let me know if you need more information.

Thanks,
Damon

[Michael Rooney (mrooney)]

Confirming based on similar experience from user in forums. I'll also post this bug there and hopefully that user will subscribe here.

[Damon Timm (damontimm)]

I wanted to add that I found some more information at: http://www.intel.com/support/network/sb/cs-009209.htm ... I tried some of the modprobe settings suggested by intel, and none of them produced working results ... although it did change my dmesg output slightly. For example:

sudo rmmod e1000
sudo modprobe e1000 AutoNeg=0x020

[dmesg shows]

[250502.329231] ACPI: PCI interrupt for device 0000:00:0e.0 disabled
[250523.062823] Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
[250523.062914] Copyright (c) 1999-2006 Intel Corporation.
[250523.063131] ACPI: PCI Interrupt 0000:00:0e.0[A] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
[250523.287477] e1000: 0000:00:0e.0: e1000_validate_option: AutoNeg advertising 1000/FD
[250523.290910] e1000: 0000:00:0e.0: e1000_probe: (PCI:33MHz:32-bit) 00:0e:0c:d9:ca:1f
[250523.511879] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
[250548.054127] ADDRCONF(NETDEV_UP): eth0: link is not ready

But I can't get eth0 to come back up and ethtool reports speed as "unknown" ... if I turn it back to the default, this is what I get ...

sudo rmmod e1000
sudo modprobe e1000

[dmesg shows]

[250564.744767] ACPI: PCI interrupt for device 0000:00:0e.0 disabled
[250569.360567] Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
[250569.360659] Copyright (c) 1999-2006 Intel Corporation.
[250569.360880] ACPI: PCI Interrupt 0000:00:0e.0[A] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
[250569.588495] e1000: 0000:00:0e.0: e1000_probe: (PCI:33MHz:32-bit) 00:0e:0c:d9:ca:1f
[250569.808326] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
[250569.836165] ADDRCONF(NETDEV_UP): eth0: link is not ready
[250578.464247] e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
[250578.467981] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[250589.302760] eth0: no IPv6 routers present

I'm not sure how else to troubleshoot this myself -- unless I find something more on the internet to guide me, I am be stuck!

Thanks,
Damon

[Bart Heinsius (bheinsius)]

Some additional info.

I experience the same behavior on:

- my 5 year old Dell Dimension 8300, which has a 82541PI Gigabit Ethernet Controller
- my brand new Dell Vostro 420, which has a RTL8111/8168B PCI Express Gigabit Ethernet controller.

When I connect the network cable to my Dell Precision M2300 laptop, which has a NetXtreme BCM5755M Gigabit Ethernet PCI Express card, it *does* connect at 1Gb/s.

When I compare the ethtool output from the two, I see that:
- my laptop supports and advertises link mode 1000baseT/Half whereas the Dimension and Vostro don't.
- my laptop has PHYAD 1 whereas the Dimension and Vostro have PHYAD 0.

-Bart

[Leann Ogasawara (leannogasawara)]

Hi thornomad,

Can you actually test the newer Intrepid Ibex 8.10 release which has a newer 2.6.27 based kernel?

[Damon Timm (damontimm)]

Hi Leann - at the present time, I don't have another machine I can throw the card in easily to test a later version ... sorry ... my situation may change in the next few weeks, but for now I use it as my primary NAS (not as a test machine).

I would mention that the original poster on UbuntuForums -- who has the same card as I do -- reportedly tested this both on Hardy and Intrepid and states that the problem persists. See: http://ubuntuforums.org/showpost.php?p=6318444&postcount=1 ... I assume this is the same Bart subscribed to this bug; perhaps he will have more input on Intrepid?

If there is anything I can try in terms of "in place" testing (on the LTS version I have installed), I would be happy to give it a try immediately.

Thanks,
Damon

[Bart Heinsius (bheinsius)]

I can confirm that the problem persists in Intrepid with the 2.6.27-9-generic kernel.

[Bart Heinsius (bheinsius)]

Is there a way around this problem?
Maybe using Intel's drivers?
I'm no C expert but can I do anything to help fix it?

[birrddog (john-globalholdings)]

I compiled Intel's latest driver 8.0.9 and still experience this problem.

It works on 100mb but if I try to set Speed to 1000 or AutoNeg to 0x020 ethtool eth0 displays:
Settings for eth0:
 Supported ports: [ TP ]
 Supported link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         1000baseT/Full
 Supports auto-negotiation: Yes
 Advertised link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         1000baseT/Full
 Advertised auto-negotiation: Yes
 Speed: Unknown! (65535)
 Duplex: Unknown! (255)
 Port: Twisted Pair
 PHYAD: 1
 Transceiver: internal
 Auto-negotiation: on
 Supports Wake-on: umbg
 Wake-on: g
 Current message level: 0x00000007 (7)
 Link detected: no

Any updates yet?

[Damon Timm (damontimm)]

I have not heard any updates myself, and actually got a new card (in
the meantime). Would love to put this card back to work.

On Thu, Feb 26, 2009 at 5:03 PM, birrddog <email address hidden> wrote:
> I compiled Intel's latest driver 8.0.9 and still experience this
> problem.
>
> It works on 100mb but if I try to set Speed to 1000 or AutoNeg to 0x020 ethtool eth0 displays:
> Settings for eth0:
>        Supported ports: [ TP ]
>        Supported link modes:   10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>                                1000baseT/Full
>        Supports auto-negotiation: Yes
>        Advertised link modes:  10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>                                1000baseT/Full
>        Advertised auto-negotiation: Yes
>        Speed: Unknown! (65535)
>        Duplex: Unknown! (255)
>        Port: Twisted Pair
>        PHYAD: 1
>        Transceiver: internal
>        Auto-negotiation: on
>        Supports Wake-on: umbg
>        Wake-on: g
>        Current message level: 0x00000007 (7)
>        Link detected: no
>
> Any updates yet?
>
> --
> Intel Gibabit Ethernet NIC (82541PI) operating at 100Mbps instead of 1000Mbps after upgrading to Hardy
> https://bugs.launchpad.net/bugs/309211
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Bart Heinsius (bheinsius)]

I replaced my Linksys SD2008 gigabit switch with a Netgear ProSafe.
Problem solved.

[Damon Timm (damontimm)]

Interesting - I have a NetGear ProSafe GS108 ... and my problem persists.

On Sat, Feb 28, 2009 at 9:58 AM, Bart Heinsius <email address hidden> wrote:
> I replaced my Linksys SD2008 gigabit switch with a Netgear ProSafe.
> Problem solved.
>
> --
> Intel Gibabit Ethernet NIC (82541PI) operating at 100Mbps instead of 1000Mbps after upgrading to Hardy
> https://bugs.launchpad.net/bugs/309211
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Jeff Van Epps (lordbah)]

My case: 8.04.2, Intel 82541PI, stuck at 10 Mb/s, cat6 cable, NetGEAR GS105 switch. The switch does make a 1000Mb/s connection with NetGEAR ReadyNAS Duo, on any switch port, with any of my cat6 cables.

[Jeff Van Epps (lordbah)]

I may have stumbled onto a fix.

Download e1000 driver version 8.0.9 from intel.com.
sudo make CFLAGS_EXTRA=-DE1000_MASTER_SLAVE=1 install
sudo rmmod e1000
sudo modprobe e1000 AutoNeg=0x28

It was the slave=1 part which finally made the difference. This setting "forces it to master mode". I don't know enough about it to understand what this means - I was just flipping all switches until things started to work.

[Damon Timm (damontimm)]

Recently, my Netgear GS108 network switch kicked it (flashing green
lights of death) -- I browsed around on the net and found a fix: by
replacing the blown capacitors with new ones (35v 1000uF capacitors)
things are up and running.

And: what do you know: I have gigabit speeds again with this card!

What is strange about this, though: is that while this particular card
was NOT reaching gigabit speeds for the past months since I upgraded
to Hardy, all the other machines on the router WERE ... this was the
only outlier. And it didn't matter which port I used. But now: it is
working.

Maybe there is something finicky about the card/diver ... but I am
happy to say it is working ... I suspect maybe one of the capacitors
went first (around the same time I upgraded) ... or, maybe, the newer
version of the driver is more finicky ...

I don't know. But it is working.

On Sat, Feb 28, 2009 at 9:40 PM, Jeff Van Epps <email address hidden> wrote:
> I may have stumbled onto a fix.
>
> Download e1000 driver version 8.0.9 from intel.com.
> sudo make CFLAGS_EXTRA=-DE1000_MASTER_SLAVE=1 install
> sudo rmmod e1000
> sudo modprobe e1000 AutoNeg=0x28
>
> It was the slave=1 part which finally made the difference. This setting
> "forces it to master mode". I don't know enough about it to understand
> what this means - I was just flipping all switches until things started
> to work.
>
> --
> Intel Gibabit Ethernet NIC (82541PI) operating at 100Mbps instead of 1000Mbps after upgrading to Hardy
> https://bugs.launchpad.net/bugs/309211
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[kstewart (kienan-stewart)]

I have the same bug, where the Intel Gigabit 82541PI NIC does not operate at 1000Mbps.

Network: Linksys 5 port workgroup switch (EG005Wv3); D-Link DI-724GU Gigabit Office Router (w/ Wireless). Windows machines operate at full gigabit speeds.

Computer: AMD Sempron 3000+, 512MB ram, intel 82541PI gigabit NIC, asus a2n-pv motherboard (on board nic also does not perform at gigabit speeds - nVidia MCP51 ethernet controller rev a3).

Software: Ubuntu 8.04 Hardy Heron; Ubuntu 8.10 Intrepid Ibex; Ubuntu 9.04 Jaunty Jackelope

Steps attempted:
Using ethtool the tune adapter connection speed
Compiling e1000 drivers (version 8.0.9).
Compiling above using CFLAGS_EXTRA=-DE1000_MASTER_SLAVE=1

[Jeff Van Epps (lordbah)]

Status update: I continue to have to rebuild the driver --> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/309211/comments/13
with the 2.6.27.14 kernel, and it continues to fix the problem, for me. Without doing this I get a 10 Mb/s connection.

[Jeff Van Epps (lordbah)]

Still have to rebuild the driver with 2.6.28-15.

[JasperE (jasper-e)]

I can confirm this bug, I also have this specific Intel NIC. Line speed is stuck at 100mbit on Hardy. It worked fine on Gbit before upgrading OS.

[JasperE (jasper-e)]

I was previously using a Linksys SD2005 Gbit switch. All Gbit capable devices did in fact get Gbit linespeed, except for ubuntu in combination with the Intel NIC.

I have now installed a Netgear prosafe 5 port Gbit switch instead of the SD2005. The Intel NIC in combination with Ubuntu does get Gbit linespeed on this switch. It didn't on the Linksys SD2005.

[Shawn Knisely (tshawn)]

I have a Gbit card in my Dell. After upgrade to 9.10, could only get 10mbs. Swapped cables, confirmed other computers getting full 100mbs. I replaced 4 port Linksys switch with a Belkin 4 port switch I had and now I can get 100mbs on my Ubunutu machine.

[Michael Malyshev (mike-malyshev)]

I can confirm this bug with my Intel adapter on Ubuntu 10.04 with 2.6.32-23-generic. My adapter runs on 10 mb instead of 100

lspci output:

00:19.0 Ethernet controller: Intel Corporation 82566DC-2 Gigabit Network Connection (rev 02)

ethtool -i eth0 output
driver: e1000e
version: 1.0.2-k2
firmware-version: 1.3-0
bus-info: 0000:00:19.0

I rebuilt drivers from e1000-8.0.19.tar.gz with CFLAGS_EXTRA=-DE1000_MASTER_SLAVE=1 and it solves the problem

p.s.: got he sources from http://www.intel.com/support/network/sb/cs-009209.htm

[Michael Malyshev (mike-malyshev)]

Update: I'm not sure that driver with CFLAGS_EXTRA=-DE1000_MASTER_SLAVE=1 solves the problem. Ubuntu reports 100Mb but my Ethernet switch indicates 10Mb on the port

[Thomas Antepoth (ta-ubuntu-antepoth)]

Another Update:
This still occurres on a fresh lucid lynx either with the stock driver modules or the CFLAGS_EXTRA-Settings.

root@sofa:~# ethtool -i eth0
driver: e1000
version: 8.0.19-NAPI
firmware-version: N/A
bus-info: 0000:05:00.0
root@sofa:~#

The switch to which the NIC is connected is a Linksys SD2005.

The errors on this NIC are:

root@sofa:~# ethtool -S eth0 | grep -v ": 0"
NIC statistics:
     rx_packets: 137916
     tx_packets: 125195
     rx_bytes: 198794208
     tx_bytes: 9016672
     rx_broadcast: 3
     tx_broadcast: 46
     tx_multicast: 25
     rx_errors: 16651
     rx_crc_errors: 9073
     rx_frame_errors: 48
     rx_align_errors: 48
     tx_tcp_seg_good: 8
     rx_long_byte_count: 198794208
     rx_csum_offload_good: 137686

Already tried an changed cables and tried to renegotiate via "ethtool -r eth0" but to no avail.

The NIC worked flawlessly during "Debian Lenny" and its stock kernel.

[Thomas Antepoth (ta-ubuntu-antepoth)]

When plugging the cable into the wall plug instead of the Linksys SD2005 the dmesg command shows that the same unchanged driver is in fact capable to do 1000MB:

From the freshly compiled 8.0.19 driver issued by intel which is loaded by "modprobe e1000 AutoNeg=0x28" as suggested earlier:

Command:"ethtool eth0"

Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes: 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Link partner advertised link modes: Not reported
        Link partner advertised pause frame use: No
        Link partner advertised auto-negotiation: No
        Speed: 100Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: umbg
        Wake-on: g
        Current message level: 0x00000007 (7)
        Link detected: yes

Command: "ethtool -i eth0"

driver: e1000
version: 8.0.19-NAPI
firmware-version: N/A
bus-info: 0000:05:00.0

Plugged into the SD2005 switch:
[32234.423251] e1000: eth0: e1000_watchdog_task: NIC Link is Down
[32243.193686] e1000: eth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX

Plugged into the wall plug:
[33467.172950] e1000: eth0: e1000_watchdog_task: NIC Link is Down
[33478.655021] e1000: eth0: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

And back to the switch again:
[33547.942638] e1000: eth0: e1000_watchdog_task: NIC Link is Down
[33563.045981] e1000: eth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX

Smells a bit like some issues in the speed negotiation between the NIC and the switch - most probably in "e1000_phy.c". Will dig some more into that.

[Damon Timm (damontimm)]

For me, this problem was resolved actually by replacing a hardware
capacitor in my switch - see this comment:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/309211/comments/14

Something is funny between the card and some switches. That is for certain.

On Wed, Aug 18, 2010 at 1:21 AM, Thomas Antepoth
<email address hidden> wrote:
> When plugging the cable into the wall plug instead of the Linksys SD2005
> the dmesg command shows that the same unchanged driver is in fact
> capable to do 1000MB:
>
> >From the freshly compiled 8.0.19 driver issued by intel which is loaded
> by "modprobe e1000 AutoNeg=0x28" as suggested earlier:
>
> Command:"ethtool eth0"
>
> Settings for eth0:
>        Supported ports: [ TP ]
>        Supported link modes:   10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>                                1000baseT/Full
>        Supports auto-negotiation: Yes
>        Advertised link modes:  100baseT/Full
>                                1000baseT/Full
>        Advertised pause frame use: No
>        Advertised auto-negotiation: Yes
>        Link partner advertised link modes:  Not reported
>        Link partner advertised pause frame use: No
>        Link partner advertised auto-negotiation: No
>        Speed: 100Mb/s
>        Duplex: Full
>        Port: Twisted Pair
>        PHYAD: 1
>        Transceiver: internal
>        Auto-negotiation: on
>        MDI-X: Unknown
>        Supports Wake-on: umbg
>        Wake-on: g
>        Current message level: 0x00000007 (7)
>        Link detected: yes
>
>
> Command: "ethtool -i eth0"
>
> driver: e1000
> version: 8.0.19-NAPI
> firmware-version: N/A
> bus-info: 0000:05:00.0
>
>
> Plugged into the SD2005 switch:
> [32234.423251] e1000: eth0: e1000_watchdog_task: NIC Link is Down
> [32243.193686] e1000: eth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
>
>
> Plugged into the wall plug:
> [33467.172950] e1000: eth0: e1000_watchdog_task: NIC Link is Down
> [33478.655021] e1000: eth0: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
>
> And back to the switch again:
> [33547.942638] e1000: eth0: e1000_watchdog_task: NIC Link is Down
> [33563.045981] e1000: eth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
>
> Smells a bit like some issues in the speed negotiation between the NIC
> and the switch - most probably in "e1000_phy.c". Will dig some more into
> that.
>
> --
> Intel Gibabit Ethernet NIC (82541PI) operating at 100Mbps instead of 1000Mbps after upgrading to Hardy
> https://bugs.launchpad.net/bugs/309211
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Thomas Antepoth (ta-ubuntu-antepoth)]

Finally my connectivity problems turned out to be caused by four blown up 470uF/25V capacitors by the infamous STONE-Company on the board of the Linksys SD2005. You might want to google for "stone badcap" and "linksys sd2005 bad caps" to get the whole story.

It took me quite a while to prove that by replacing the switch with a known good one.

Sorry for not checking that first, but the symptoms were just like the ones in this bug report and the driver README was too comfortable to follow.

[penalvch (penalvch)]

Damon Timm, This bug report is being closed due to your last comment regarding this being fixed by hardware maintenance. 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.