I have updated the bios. Rauno rmoisto wrote on It has a Atheros Communications Inc. There is a feature request to include alx on Fedora kernel. Also it is still applicable to 3. I found a sollution 10 minutes ago here: You can learn more about bug statuses at https:
|Date Added:||12 April 2009|
|File Size:||17.71 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
[ubuntu] Atheros AR/ PCI-E Gigabit Ethernet Controller Driver
There is a workaround: In Network manager, set the ethernet connection’s MTU value from automatic to Both the Ethernet as well as wireless are not working. This is still linhx fixed. I can confirm that, on Ubuntu Piotr At8161 Konopelko oxide94 wrote on Joseph Salisbury jsalisbury on If the mainline kernel does not fix this bug, please add the following tags: Using WiFi is only a viable workaround when it’s available and stable which is not always the case.
I cannot find that. Thank you for your interest in this question. Hence, let us mark this Triaged for now.
I did not try removing this driver. Upgraded to vivid on 3 days ago dmi. I see you already found it: I have tried various upstream kernel packages.
Right now I am relying on thumbdrive to transfer files. Mark Sapiro msapiro on I’m now using Ubuntu I have a windows partition on the machine and I booted windows sr8161 downloaded the bios update from http: Remote bug watches linux-kernel-bugs Edit Bug watches keep track of this bug in other bug trackers.
Home Questions Tags Users Unanswered. You will need to check the following packages on your system: Don’t know the reason. It will allow additional upstream developers to examine the issue.
Mark Sapiro, then it appears you have a downstream patch that is causing this issue. Here is uname-a and partial ifconfig with 3.
Qualcomm Atheros AR8161, AR8162, QCA8171, QCA8172 Ethernet controllers
AR Gigabit Ethernet rev 08 This looks like a new product whose drivers are not built into Ubuntu. Otherwise people won’t know it isn’t fixed there! I had the same issue after the 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.
For a fresh install of Fedora So these are all the steps I made: