Stuck at wl1251_sdio mmc2:0001:1: firmware: requesting wl1251-fw.bin


javaJake

Jacob Godserv
Joined
Sep 13, 2007
Messages
1,773
Location
USA
Website
myhumblecorner.wordpress.com
Wireless stopped working. I'm not sure what happened, but here's what I know: a friend of mine saw my Pandora and, being an engineer himself, was interested and asked if he could hold it. He played with the nubs and the keyboard, and then clicked the shoulder buttons rapidly. Now, at the time I had a little home-grown python script running as root, listening for keyboard input and filtering out to just shoulder buttons. This way I could restart Bluetooth or Wifi in the event they dropped connections. (I had gotten sick of using the terminal or right-clicking to do so.) The left shoulder button executes "/etc/init.d/bluetooth restart" and the right one executes "/etc/init.d/NetworkManager restart". These were executed multiple times, rapidly.


Ever since then Wifi on Gentoo has never been the same. I don't get it. I reboot into the official firmware and it works fine. I completely reformatted Gentoo back to the original installation I had when wifi was working, and I still get the same lockups and errors.


When booting up the Pandora on Gentoo, I noted occasional freezes. If I log in as root in a virtual terminal (outside X) and execute "iwconfig" it took up to 15 seconds or so to finally react. Ctrl+C does nothing during this time, which indicated a kernel-level lockup.


I looked at the logs next:



Code:
Sep 08 01:21:11 [kernel] [  959.023590] Sending insert event for MMC3...

Sep 08 01:21:11 [kernel] [  959.079040] mmc2: card claims to support voltages below the defined range. These will be ignored.

Sep 08 01:21:11 [kernel] [  959.079040] mmc2: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.

Sep 08 01:21:11 [kernel] [  959.093963] mmc2: new SDIO card at address 0001

Sep 08 01:21:12 [NetworkManager] <info>  (wlan0): driver supports SSID scans (scan_capa 0x01)._

Sep 08 01:21:12 [kernel] [  959.196990] wl1251: loaded

Sep 08 01:21:12 [kernel] [  959.196990] wl1251: initialized

Sep 08 01:21:12 [NetworkManager] <info>  (wlan0): new 802.11 WiFi device (driver: 'wl1251_sdio')_

Sep 08 01:21:12 [NetworkManager] <info>  (wlan0): exported as /org/freedesktop/Hal/devices/net_00_19_94_0f_b2_76_

Sep 08 01:21:16 [NetworkManager] <info>  (wlan0): device state change: 1 -> 2 (reason 2)_

Sep 08 01:21:16 [NetworkManager] <info>  (wlan0): bringing up device._

Sep 08 01:21:16 [kernel] [  963.289184] sdio_reset_comm():

Sep 08 01:21:16 [kernel] [  963.294525] wl1251_sdio mmc2:0001:1: firmware: requesting wl1251-fw.bin

Sep 08 01:22:16 [kernel] [ 1023.289398] wl1251: ERROR could not get firmware: -2

Sep 08 01:22:16 [NetworkManager] <WARN>  nm_device_hw_bring_up(): (wlan0): device not up after timeout!_

Sep 08 01:22:16 [NetworkManager] <info>  (wlan0): deactivating device (reason: 2)._

Sep 08 01:22:16 [kernel] [ 1023.343902] sdio_reset_comm():

Sep 08 01:22:16 [kernel] [ 1023.349243] wl1251_sdio mmc2:0001:1: firmware: requesting wl1251-fw.bin

Sep 08 01:22:41 [NetworkManager] <WARN>  nm_supplicant_interface_add_cb(): Unexpected supplicant error getting interface: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken._

Sep 08 01:23:16 [kernel] [ 1083.344085] wl1251: ERROR could not get firmware: -2


Basically, a clean install of Gentoo used to work. Now it doesn't. Official firmware still works.


I honestly don't know what to debug next. Googling says udev might be at fault, but I've tried all the fixes people say work and none have worked so far. I'm also using the same kernel modules and firmware and whatnot as I always have from the official rootfs. I don't know if this has anything to do with the latest hotfix either.
 
Last edited by a moderator:
Clarification: I'm looking for advice on what it can and can't be. Could it be a hardware bug? Could it be a software misconfiguration? Any ideas on which piece might be causing this issue?
 
Good idea, didn't think of that. (Duh!) I'll try an older version of the wireless drivers. I'll try some of the tags in git and see if I hit a magic combination. Thanks for the pointers! It helped! :)
 
Back
Top