D-Link DFE-528TX PCI NIC not detected

[Moritz Schneider]

D-Link DFE-528TX is not detected by Breezy

Ethernet controller: D-Link System Inc RTL8139 Ethernet 1186:1300 (rev 10)

Workaround:
Shutdown, power down. Unplug your host (this cuts power to the card if wake-on-lan power is maintained). Wait 15 seconds. Plug in. Boot ubuntu.

[Matt Zimmerman (mdz)]

Please show us the output from "lspci" and "lspci -n" on the system with this device

[Ben Collins (ben-collins)]

Closing, inactive.

[PabloRQ (pablo-romeroquinteros)]

Still not working in Ubuntu 11.04.

$ lspci
00:00.0 RAM memory: nVidia Corporation MCP67 Memory Controller (rev a2)
00:01.0 ISA bridge: nVidia Corporation MCP67 ISA Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation MCP67 SMBus (rev a2)
00:01.2 RAM memory: nVidia Corporation MCP67 Memory Controller (rev a2)
00:02.0 USB Controller: nVidia Corporation MCP67 OHCI USB 1.1 Controller (rev a2)
00:02.1 USB Controller: nVidia Corporation MCP67 EHCI USB 2.0 Controller (rev a2)
00:04.0 USB Controller: nVidia Corporation MCP67 OHCI USB 1.1 Controller (rev a2)
00:04.1 USB Controller: nVidia Corporation MCP67 EHCI USB 2.0 Controller (rev a2)
00:06.0 IDE interface: nVidia Corporation MCP67 IDE Controller (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP67 PCI Bridge (rev a2)
00:09.0 IDE interface: nVidia Corporation MCP67 AHCI Controller (rev a2)
00:0a.0 Ethernet controller: nVidia Corporation MCP67 Ethernet (rev a2)
00:12.0 VGA compatible controller: nVidia Corporation C68 [GeForce 7025 / nForce 630a] (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:06.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
01:07.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI]

$ lspci -n
00:00.0 0500: 10de:0547 (rev a2)
00:01.0 0601: 10de:0548 (rev a2)
00:01.1 0c05: 10de:0542 (rev a2)
00:01.2 0500: 10de:0541 (rev a2)
00:02.0 0c03: 10de:055e (rev a2)
00:02.1 0c03: 10de:055f (rev a2)
00:04.0 0c03: 10de:055e (rev a2)
00:04.1 0c03: 10de:055f (rev a2)
00:06.0 0101: 10de:0560 (rev a1)
00:08.0 0604: 10de:0561 (rev a2)
00:09.0 0101: 10de:0550 (rev a2)
00:0a.0 0200: 10de:054c (rev a2)
00:12.0 0300: 10de:053e (rev a2)
00:18.0 0600: 1022:1100
00:18.1 0600: 1022:1101
00:18.2 0600: 1022:1102
00:18.3 0600: 1022:1103
01:06.0 0200: 1186:1300 (rev 10)
01:07.0 0401: 1274:5000

[PabloRQ (pablo-romeroquinteros)]

The card to bu used is:
01:06.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)

I'm using the other one to connect to internet and try to find a solution. (00:0a.0 Ethernet controller: nVidia Corporation MCP67 Ethernet (rev a2))

[PabloRQ (pablo-romeroquinteros)]

Some kind of solution.

After searching the web I found this weird (windows like) workaround (http://ubuntuforums.org/showthread.php?t=538448):

"If your ethernet cable is connected at boot time and you are experiencing the no link problem, try this: Shutdown, power down. Unplug your host (this cuts power to the card if wake-on-lan power is maintained). Wait 15 seconds. Plug in. Boot ubuntu."

I thought it was a joke, but it works and now i'm posting from the Dlink ethernet card.

Ethernet Card Model in the box: D-Link DFE-528TX
Ethernet Card recognized: D-Link System Inc RTL8139

[komputes (komputes)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect BUGNUMBER
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[PabloRQ (pablo-romeroquinteros)]

Apport won't let me send the collected info because this bug is closed. The same issue happens about bug #123358.

$ sudo apport-collect 22084
or
$ sudo apport-collect 123358

Message:
Usted no es el informador o suscriptor de este informe de problemas, o el informe es un duplicado o ya está cerrado.
Cree un nuevo informe usando «apport-bug».

Anyway, with the previous (windows like) workaround the net card is fully working (i'm connected through it) and don't know if apport can bring usefull information.

If there's something i can do for help, just let me know.

[komputes (komputes)]

Hi parq, The error was my fault since I marked this bug as a duplicate. Please run 'apport-collect 22084' again. It should work now.

[PabloRQ (pablo-romeroquinteros)]

After that (#5) the card works fine.
Now I've changed the motherboard and i'm not using it anymore.
If no one else can report about it, please close it.

[penalvch (penalvch)]

Moritz Schneider, 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 in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

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 . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested.

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', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

[Thomas Hotz (thotz-deactivatedaccount)]

Closing because of no response.