In Other Network Topics. I guess I had assumed the Atheros device showing up within lspci was the Wifi card instead of ethernet. The workaround mentioned in my first post is still neccesary in order to get kernel 3. I am not convinced a driver is loaded for the MCP61 as that would normally be the forcedeth driver. This new method doesn’t work with the old kernel, and the old method doesn’t work with the new kernel.

Uploader: Guramar
Date Added: 7 May 2008
File Size: 17.37 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 83463
Price: Free* [*Free Regsitration Required]

Penalver penalvch on Once you’ve tested the upstream kernel, please remove the ‘needs- upstream- testing’ tag Only that one tag, please leave the other tags.

Networking and ACPI conflicts 7. The idea would have been to post some fault hunting info, say from your lspci command. Thanks Christopher – bug submitted – id https: The board has a built in ethernet port but it went “bad” a while ago which is the reason I haven’t beeen using the computer.

This enabled both networking and regular ACPI functions. I tried the first two work arounds again but nothing is working.


The PCI ID Repository

Marco Aicardi launchpad-net-aicardi wrote on The reply is currently minimized Show. If you booted normally without following either of the above steps and then tried to modprobe, it wouldn’t work.

Sometimes replacements exist, other times they are hard to find. Status changed to Confirmed For the D-Link, drivers are not loaded.

Install Network Problem

However, the results are the same. No need exists to comment here at this time. I see an Atheros ethernet device, but not wireless. To Be Filled By O. Step one in fixing the bug is getting Ubuntu to pay attention.

[SOLVED] No Network Connection — [Archive] – Ubuntu Forums

Gannin spacesword wrote on I tested kernel 3. Marco Aicardi launchpad-net-aicardi on The output of lspci: Download full text 6. I searched quite a while on how to solve the issue with recent ubuntu versions e.

The bug is still present, I’ve just spent an afternoon trying to fix 10ve on Arch Linux, but it’s the same bug in the driver. The workaround mentioned in my first post is still neccesary in order to get kernel 3. I will also try to reseat the card tonight as well.


I guess considering the lack of movement on this bug, the only real longterm solution is to not use an ASrock motherboard. Any help would be greatly appreciated.

Joseph Salisbury jsalisbury wrote on Likes Highest Vote Latest Oldest. Comment on this change optional. But as the bug was never even assigned to anyone, I’m beginning to feel this is going to be another one of those Ubuntu bugs that’s show-stopping for some, but quietly slips into the ether and never gets fixed.

Please let us know your results.