RTL8111DL ethernet is UP but not RUNNING

Bug #310441 reported by nausicaa on 2008-12-22
26
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned

Bug Description

After a lot of effort trying to get this working, I am not sure where to go from here.
Hardware is the ASRock G41M-LE with the Realtek RTL8111DL gigabit ethernet.

I have tried configuring the interface(eth0) with dhcp and static address in /etc/network.
I can ping the loopback (127.0.0.1) as well as the static IP I assign (e.g. 192.168.1.222).
However no connection to any other IP (router, etc). The dhcp exchange times out with no DHCPOFFER received. I can get the interface to show UP BROADCAST MULTICAST, but I do not see RUNNING like my other machines.
mii-tool -v shows: SIOCGMIIPHY on 'eth0' failed: Operation not supported

One strange thing is lspci -vv shows the Realtek ethernet entry, but the kernel module listed at the bottom is r8169. I think this should be the r8168 module? Can anyone help?

Thanks!

GarthPS (garthps) wrote :

Same controleur same probleme here
Anay answer?

nausicaa (nausicaa-vow) wrote :

yes, here is a fix I posted for this problem...http://ubuntuforums.org/showthread.php?t=1022411

Fido (anbefales) wrote :

Please fix it in the Ubuntu 9.04 so we don't have to use the workaround posted by nausicaa.

David Tombs (dgtombs) 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 linux.

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)
David Tombs (dgtombs) wrote :

Also, please run the following command which will attach necessary information:

apport-collect 310441
if you are using Karmic Koala (9.10) or newer, or

apport-collect -p linux-image-`uname -r` BUGNUMBER
if you are using Jaunty Jackalope (9.04).

Bear in mind that you may need to install the python-launchpadlib package from the universe repository with 'sudo apt-get install python-launchpadlib'. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.

If you are using an older release or cannot use apport please at least add the following information (pay attention to lspci's additional options):

First run the following commands:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_signature > version.log
then attach the files separately to the bug report (not pasted into comments or tar/zip-ed).

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

Note: this is probably a dupe of bug 221499.

Changed in linux (Ubuntu):
status: New → Incomplete
Jeremy Foshee (jeremyfoshee) wrote :

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.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers