Slackware64 current Core i7 6GB RAM lspci -v : 3:00.0 Network controller: Atheros Communications Inc. AR9287 Wireless Network Adapter (PCI-Express) (rev 01) Subsystem: Foxconn International, Inc. Device e034 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at c0100000 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [60] Express Legacy Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 00-15-17-ff-ff-24-14-12 Capabilities: [170] Power Budgeting <?> Kernel driver in use: ath9k dhcpcd --version: dhcpcd 5.2.12 Since 3.6-rc1, dhcpcd do not detect carrier anymore at boot. Therefore it doesn't get an IP address, and I have to configure wpa_supplicant and restart dhcpcd manually to get network connectivity. The slack's script starts dhcpcd after wpa_supplicant (which actually manage to authenticate, but not fast enough to prevent dhcpcd from testing the carrier). dhcpcd tells: Jul 17 21:39:53 pierre dhcpcd[2279]: eth0: carrier lost then timeout (instead of acquiring the carrier). So it seems an event is lost somewhere in networking notification code, or userspace API is broken.
I have the same the problem.. [root@pvbook ~]# dmesg | grep ath [ 11.208242] ath: EEPROM regdomain: 0x60 [ 11.208246] ath: EEPROM indicates we should expect a direct regpair map [ 11.208249] ath: Country alpha2 being used: 00 [ 11.208251] ath: Regpair used: 0x60 [ 11.411738] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control' [ 11.411964] Registered led device: ath9k-phy0 07:00.0 Network controller: Atheros Communications Inc. AR5418 Wireless Network Adapter [AR5008E 802.11(a)bgn] (PCI-Express) (rev 01) Subsystem: Atheros Communications Inc. Device 3072 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 19 Region 0: Memory at feaf0000 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit- Address: 00000000 Data: 0000 Capabilities: [60] Express (v1) Legacy Endpoint, MSI 00 DevCap:>MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset- DevCtl:>Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta:>CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap:>Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us ClockPM- Surprise- LLActRep- BwNot- LnkCtl:>ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta:>Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- Capabilities: [90] MSI-X: Enable- Count=1 Masked- Vector table: BAR=0 offset=00000000 PBA: BAR=0 offset=00000000 Capabilities: [100 v1] Advanced Error Reporting UESta:<>DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol- UEMsk:<>DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt:>DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta:<>RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk:<>RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- AERCap:>First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [140 v1] Virtual Channel Caps:<->LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl:<->ArbSelect=Fixed Status:>InProgress- VC0: Caps:<->PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl:<->Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status:>NegoPending- InProgress- Kernel driver in use: ath9k Kernel modules: ath9k Sep 3 16:51:29 pvbook dhcpcd[3205]: version 5.5.6 starting Sep 3 16:51:29 pvbook network: dhcpcd[3205]: version 5.5.6 starting Sep 3 16:51:29 pvbook dhcpcd[3205]: all: not configured to accept IPv6 RAs Sep 3 16:51:29 pvbook network: dhcpcd[3205]: all: not configured to accept IPv6 RAs Sep 3 16:51:29 pvbook network: dhcpcd[3205]: wlan0: using hwaddr 00:15:af:53:f6:02 Sep 3 16:51:29 pvbook network: dhcpcd[3205]: wlan0: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT Sep 3 16:51:29 pvbook network: dhcpcd[3205]: wlan0: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER Sep 3 16:51:29 pvbook dhcpcd[3205]: wlan0: waiting for carrier Sep 3 16:51:29 pvbook network: dhcpcd[3205]: wlan0: waiting for carrier Sep 3 16:51:29 pvbook dhcpcd[3205]: timed out Sep 3 16:51:29 pvbook network: dhcpcd[3205]: timed out [root@pvbook ~]# uname -a Linux pvbook.localdomain 3.6.0-pure-emerald-alt0.rc3 #1 SMP PREEMPT Wed Aug 29 16:18:27 UTC 2012 i686 GNU/Linux
could you please try the latest and see if the issue occurs http://www.orbit-lab.org/kernel/compat-wireless/compat-wireless-2012-09-02.tar.bz2
(In reply to comment #2) > could you please try the latest and see if the issue occurs > > http://www.orbit-lab.org/kernel/compat-wireless/compat-wireless-2012-09-02.tar.bz2 Unfortunately did not help..
Update: Still present in 3.6 final (even compiled in release build).
Could this be related to ath9k driver issues? Check this bug: 48151
I've tried to bisect, but it fails as v3.5 from git failed, whereas v3.5 from kernel.org succeeds. I therefore diff'ed my .config from my git bisection: it was modified by make menuconfig of v3.6-rc1 and lost this config entry: CONFIG_WIRELESS_EXT_SYSFS=y which is quite logical: if there are no sysfs entry for the driver, waiting for the carrier will fail. This option has disappeared from "include/config/auto.conf", but I don't know where this option is on v3.6 and I'm afraid this was deprecated since I found something related to this option in Documentation directory.
It indeed seems to have been removed from 3.6. 3.5 says: Say N. If you know you have ancient tools requiring it, like very old versions of hal (prior to 0.5.12 release), say Y and update the tools as soon as possible as this option will be removed soon. Therefore Slackware 13.37 version of hal or dhcpcd are not recent enough to run Linux v3.6, however they are only one year old so I guess it was too early to remove them. I'll upgrade to Slackare 14 in the next days and see if the problem is still there.
I've just upgraded to Slackware 14 and userspace now manages to connect to network. So this kernel requires recent userspace tools. Closing this bug therefore.