Gutsy turns off LAN port on Intel D945GCLF (ATOM)

[Richard Reid]

When Gutsy boots up it turns off the D945GCLF LAN port (the link beat led goes off). This cpu/mb works fine with Windows XP. Had similar bug with another 945 chipset mb which I worked around by enabling Wake on LAN in the bios (see bug #130305). That did not work here. I tried this with both the LiveCD and installing Gutsy to the hdd and booting from there. If you want more info you will have to tell me where to look.

[Richard Reid (richardr98)]

A little more info. Gutsy works ok (both liveCd and off hdd) if I start from power on. It does not work if I reboot.

[Richard Reid (richardr98)]

OK, I 'm not sure what changed, either one of the updates I did or the bios reset I did, but gutsy now seams to work OK.
So please close this bug report.

[ouellettesr (ouellette-kevin)]

I am having this same exact problem, no solutions yet.

[mace (o-launchpad-net-drhaehnel-de)]

Same with hardy,
look at http://ubuntuforums.org/showthread.php?t=843398& to fix

[Ian Weisser (ian-weisser)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[Florian Effenberger (floeff)]

I have similar issues with my board. Using recent Ubuntu 8.04 kernel, downloading latest driver from Realtek website, compiling it and blacklisting r8169 seems to cure the issue.

[Ian Weisser (ian-weisser)]

Florian,

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Unfortunately we can't fix it without a bit more information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

[Florian Effenberger (floeff)]

Sure, here you are!

Linux nibbler 2.6.24-21-server #1 SMP Tue Oct 21 23:40:13 UTC 2008 x86_64 GNU/Linux

But be advised that these are the log files AFTER I manually compiled the correct kernel module and blacklisted r8169.

[kernel-janitor (kernel-janitor)]

Hi richardr98,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 239595

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]