New USB device strings: To make this even more fun, every third of fourth reboot it works and the network interfaces stays up. To post a comment you must log in. To be filled by O. Will try custom module build next. It will allow additional upstream developers to examine the issue.
|Date Added:||21 June 2012|
|File Size:||18.25 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Installing the latest Atheros driver v1. I think I don’t use NFS. This change has been made by an automated script, ilnux by the Ubuntu Kernel Team. Writing to NFS server did not work.
If you don’t see what you’re looking for, just browse the ftp server. We do not support this driver. If this happens, modify your kernel’s boot line and add this kernel parameter: See full activity log. I hope someone else could verify what requested above MGGermany max-gutberlet wrote on If you try and build vendor version 1.
atl1: Attansic L1 ethernet driver
With this driver my network adapter would not even negotiate the media type successfully. George Politis gpolitis wrote on I have the same problem while diskless booting from karmic. Unfortunately I cannot test the development version since my Ubuntu machine is running critical tasks at the moment I have the same problem in Lucid Lynx. Thanks again for posting your work around. Maybe this evening I’m away at the moment.
atl1: Attansic L1 ethernet driver 
Scott scott-binrock wrote on Hell, problem not solved after all. Attansic has been acquired by Atheros.
TSO is broken, and that results in horrible transmit performance. It has been backported to 2. The fragmentation will still occur, but the atl1 driver won’t spew the error message that contributes to network slowdown.
I should have run more tests before I speak myself.
Linux Kernel: drivers/net/ethernet/atheros/atlx/atl1.h Source File
Then I downloaded latest atheros driver at http: If you encounter this problem, modify your kernel’s boot line and add this kernel parameter: Either this is a very buggy driver or a very buggy chipset.
Email me about changes to this bug report. If you know of other mainboards that include this device, please email me.
It’s offered here merely as a courtesy to make your life easier. Still having issues with atl11 mainline kernel: The only way to regain nautilus was to reboot the machine.
On Feb 9, the atl1 driver was merged into the mainline kernel with kernel version 2. You need to log in to change this bug’s status. The Asus will eventually gradually freeze up and certain processes firefox for example cannot be killed even with signal 9.