alx: does not work for my Atheros AR8161

Bug #1176108 reported by Anomaly
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Ubuntu 13.04 includes the "alx" driver but it does not work for me.

lspci gives :
03:00.0 Ethernet controller: Atheros Communications Inc. AR8161 Gigabit Ethernet (rev 08)

The module is automatically loaded and there is an eth0 interface created, but no IP is associated with it. The network system tries to connect to it in a infinite loop and always fail.

The booting time is very long, and the screen is filled by messages from alx.

I am not the only one :
http://askubuntu.com/questions/286880/13-04-ethernet-adapter-not-connecting-ar8161

Compiling from compat-wireless 3.6.8 worked wonderfully with Ubuntu 12.04 LTS. That's not an option since Raring features kernel 3.8. I tried several versions of compat-drivers but none would compile for me for unknown reasons.

Anyway since Ubuntu now provides the alx driver, it should work, but it does not. Please tell me if I can give out more informations to help solving this problem.
---
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3194 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CasperVersion: 1.331
DistroRelease: Ubuntu 13.04
IwConfig:
 ppp0 no wireless extensions.

 eth0 no wireless extensions.

 lo no wireless extensions.
LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: System manufacturer System Product Name
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=fr keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
RfKill:
 1: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Tags: raring
Uname: Linux 3.8.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 02/15/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0324
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H77-V
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0324:bd02/15/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-V:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1176108

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Anomaly (bertrand3000) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected raring
description: updated
Revision history for this message
Anomaly (bertrand3000) wrote : BootDmesg.txt

apport information

Revision history for this message
Anomaly (bertrand3000) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Anomaly (bertrand3000) wrote : HookError_cloud_archive.txt

apport information

Revision history for this message
Anomaly (bertrand3000) wrote : Lspci.txt

apport information

Revision history for this message
Anomaly (bertrand3000) wrote : Lsusb.txt

apport information

Revision history for this message
Anomaly (bertrand3000) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Anomaly (bertrand3000) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Anomaly (bertrand3000) wrote : ProcModules.txt

apport information

Revision history for this message
Anomaly (bertrand3000) wrote : PulseList.txt

apport information

Revision history for this message
Anomaly (bertrand3000) wrote : UdevDb.txt

apport information

Revision history for this message
Anomaly (bertrand3000) wrote : UdevLog.txt

apport information

Revision history for this message
Anomaly (bertrand3000) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Anomaly (bertrand3000) wrote :

The report comes from the distribution running from live USB stick (I reverted back to Ubuntu 12.04 LTS on the hard drive because of this issue). The problem is worse (very long booting time, screen filled with alx-related messages) once the OS is installed.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0].

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'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-raring/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Ed McDonagh (ed-mcdonagh) wrote :

I've tried booting with linux-image-3.9.0-030900-generic_3.9.0-030900.201304291257_amd64 and associated headers, and the problem persists.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Anthony Wong (anthonywong) wrote :

Seems you met the same issue as bug 927782, see comment #91. Can you update your kernel to latest version 3.8.0-22.33 and confirm if it can fix your problem?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Ed McDonagh (ed-mcdonagh) wrote :

As of today's kernel update - 3.8.0-23.34 - the networking now works with my Atheros AR8161 and Raring 13.04.

Revision history for this message
Ed McDonagh (ed-mcdonagh) wrote :

Should I now change the status to Fix Released? And do I need to comment on https://bugs.launchpad.net/bugs/927782?

Revision history for this message
Anomaly (bertrand3000) wrote :

I confirm that the new kernel update « 3.8.0-23.34 » indeed fixes the problem. Alx driver is now working properly.

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.