You are not logged in.
Pages: 1
A fresh install of 64-bit flavored Arch Linux on my Dell XPS L401x and my (via lspci)
12:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000
card is doing nothing at all. dmesg | grep iwl shows me lots of this:
iwlagn 0000:12:00.0: Error sending REPLY_CT_KILL_CONFIG_CMD: time out after 500ms.
iwlagn 0000:12:00.0: REPLY_CT_KILL_CONFIG_CMD failed
iwlagn 0000:12:00.0: Error sending POWER_TABLE_CMD: time out after 500ms.
iwlagn 0000:12:00.0: set power fail, ret = -110
iwlagn 0000:12:00.0: Error sending REPLY_RXON: time out after 500ms.
iwlagn 0000:12:00.0: Error setting new RXON (-110)
iwlagn 0000:12:00.0: Error sending REPLY_CT_KILL_CONFIG_CMD: time out after 500ms.
iwlagn 0000:12:00.0: REPLY_CT_KILL_CONFIG_CMD failed
iwlagn 0000:12:00.0: Error sending POWER_TABLE_CMD: time out after 500ms.
iwlagn 0000:12:00.0: set power fail, ret = -110
iwlagn 0000:12:00.0: Error sending REPLY_RXON: time out after 500ms.
iwlagn 0000:12:00.0: Error setting new RXON (-110)
iwlagn 0000:12:00.0: Error sending REPLY_CT_KILL_CONFIG_CMD: time out after 500ms.
iwlagn 0000:12:00.0: REPLY_CT_KILL_CONFIG_CMD failed
iwlagn 0000:12:00.0: Error sending POWER_TABLE_CMD: time out after 500ms.
iwlagn 0000:12:00.0: set power fail, ret = -110
iwlagn 0000:12:00.0: Error sending REPLY_RXON: time out after 500ms.
iwlagn 0000:12:00.0: Error setting new RXON (-110)
iwlagn 0000:12:00.0: Error sending REPLY_CT_KILL_CONFIG_CMD: time out after 500ms.
iwlagn 0000:12:00.0: REPLY_CT_KILL_CONFIG_CMD failed
iwlagn 0000:12:00.0: Error sending POWER_TABLE_CMD: time out after 500ms.
iwlagn 0000:12:00.0: set power fail, ret = -110
iwlagn 0000:12:00.0: Error sending REPLY_RXON: time out after 500ms.
iwlagn 0000:12:00.0: Error setting new RXON (-110)
iwlagn 0000:12:00.0: PCI INT A disabled
iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
iwlagn: Copyright(c) 2003-2010 Intel Corporation
iwlagn 0000:12:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwlagn 0000:12:00.0: setting latency timer to 64
iwlagn 0000:12:00.0: Detected Intel(R) Centrino(R) Wireless-N 1000 BGN, REV=0x6C
iwlagn 0000:12:00.0: device EEPROM VER=0x15d, CALIB=0x6
iwlagn 0000:12:00.0: Tunable channels: 13 802.11bg, 0 802.11a channels
iwlagn 0000:12:00.0: irq 49 for MSI/MSI-X
iwlagn 0000:12:00.0: loaded firmware version 128.50.3.1 build 13488
phy0: Selected rate control algorithm 'iwl-agn-rs'
iwlagn 0000:12:00.0: Error sending REPLY_CT_KILL_CONFIG_CMD: time out after 500ms.
iwlagn 0000:12:00.0: REPLY_CT_KILL_CONFIG_CMD failed
iwlagn 0000:12:00.0: Error sending POWER_TABLE_CMD: time out after 500ms.
iwlagn 0000:12:00.0: set power fail, ret = -110
iwlagn 0000:12:00.0: Error sending REPLY_RXON: time out after 500ms.
iwlagn 0000:12:00.0: Error setting new RXON (-110)
Totally lovely right? If I try to
ifconfig wlan0 up
I get
SIOCSIFFLAGS: Connection timed out
most of the time. Once every ten or so tries it will succeed, but I can't do anything beyond that. Setting an essid or anything like that won't actually do anything. I think I've successfully iwlist scanned once. iwconfig wlan0, anyone?
wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
I've tried setting the Tx-Power to reasonable values, and I've tried ifconfig upping the device with Power Management both on and off. Toggling the hardware killswitch poops this out in dmesg:
iwlagn 0000:12:00.0: RF_KILL bit toggled to disable radio.
iwlagn 0000:12:00.0: RF_KILL bit toggled to enable radio.
Oh yeah, speaking of killswitches, how about a little rfkill list!
galactica# rfkill list
0: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
I've toggled those back and forth more than... well a bunch of times. Hmmm. What am I missing? Something I'm sure. I'll be happy to post the output of commands y'all like, if you can save me from this nasty little issue. I don't think in all my years of Linuxing I've ever had to resort to posting on a forum for help.
xoxo
Offline
Oh by the way, when I do this, that happens.
galactica# ifconfig wlan0 up
galactica# iwlist wlan0 scan
wlan0 Failed to read scan data : Resource temporarily unavailable
Offline
Iwlagn works fine. I'd rather be concerned about your card than about the driver itself . Looks like a hardware and not a software problem.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
Nope... its a kernel problem. Had the same. Look at this thread, there is the solution: https://bbs.archlinux.org/viewtopic.php … 31#p869831
Offline
Those errors don't look anything like the topic starter here is having?
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
Mmmh... no idea... I answered, because I have the Dell XPS L501x with the same card and I had also weird behavior, but with this fix in the thread I have posted, all works for me. But maybe I'm wrong, then sorry....
Offline
Don't apologise for suggesting a solution. I'm curious as well. Let's see how it works out .
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
I will try that tomorrow morning, as soon as I have time, and get back to y'all.
Offline
I found a patch for 2.6.37 to not reload fw if WiMAX own the RF
http://dev.gentoo.org/~mpagano/genpatch … -fix.patch
Offline
I installed 2.6.38-rc2 with experimental uCode support enabled. This led to some different errors and iwlagn definitely was not functioning. I am too busy to continue looking into this. I'll have to put up with an ethernet cable run across my living room for the time being. As soon as I have the time I'll be fully testing the driver under .38 and filing bug reports where they belong.
[edit]
@slytux I don't believe that this card is WiMAXed out, if you know what I mean.
Last edited by txa-ea (2011-01-29 02:29:17)
Offline
I don't own this hardware. I'm only intereseted because someone I know also has it and can't get it working. From another thread, a user reported using clocksource=jiffies as a kernel boot option.
Offline
Pages: 1