Thanks to Xiong Huang of Attansic for writing the original vendor version of the driver and for granting permission to make the driver available for inclusion in the kernel. Writing to NFS server did not work. You are not directly subscribed to this bug’s notifications. Connecting it to an AVM Fritz! Will try custom module build next. If you know of other mainboards that include this device, please email me.
|Date Added:||25 October 2012|
|File Size:||13.71 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
atl1: Attansic L1 ethernet driver
The Attansic L1 is included as the onboard linyx device for the following Asus mainboards. This has been fixed in the 2.
It was written by Attansic.
You are not directly subscribed to this bug’s notifications. If this happens, modify your kernel’s boot line linix add this kernel parameter: Installing the latest Atheros driver 1.
Linux source code: drivers/net/ethernet/atheros/atlx/atl1.c (v) – Bootlin
The only way to regain nautilus was to reboot the machine. Other bug subscribers Subscribe someone else. George Linuxx gpolitis wrote on ISO CD images are available from http: Then I downloaded latest atheros driver at http: This bug was filed against a series that is no longer supported and so is being marked as Won’t Fix.
Scott scott-binrock wrote on Will try custom module build next. It has been backported to 2.
For the standalone drivers below, just untar the tarball, cd into the resulting directory, and execute “sudo make install”.
I found another bug here which could be similar. I had a very similar problem in the linked url and can confirm that using the above driver atp1 the issue for me. Asus, Linux, Attansic, and Atheros are registered trademarks of the respective companies.
Attansic L1 driver
Maybe this evening I’m away at the moment. To Be Filled By O. On Feb 9, the atl1 driver was merged into the mainline kernel with kernel version 2.
My problem is very similar to this report: Glad to be helpful. Thanks again for posting your work around. I should have run more tests before I speak myself. When the L1 hardware receives a fragmented packet, it sets an error flag in one of its registers, and the driver, upon seeing the error bit, spews the “hw csum wrong” message.
CONFIG_ATL1: Atheros/Attansic L1 Gigabit Ethernet support
If this issue still exists in a supported series, please file a new bug. Here’s where the hardware bug comes into play. Then I finally had my eth device working with NFS protocol. I purchased a foxconn minipc http: If you try and build vendor version 1. It’s fixed in 1. These were works in progress as we moved toward acceptance in late and early This bug affects 8 people.