WiFi troubles


moxie

The voice of reason, sense and exasperation
Staff member
Joined
Aug 15, 2006
Messages
2,704
Age
51
Location
South of Sweden
I have not gotten wifi in order yet. Not that I have tried very hard, but today I did some experimenting and concluded that something is indeed a bit wrong. No matter whether I use the firmware driver or the experimental beta driver, I cannot turn on the wifi system. Wifi led does not come on. A bit of dmesg gives me this, which looks a bit troubling:



Code:
[   33.541137] Pandora WiFi: Probe started

[   33.570678] Sending insert event for MMC3...

[   33.575012] Pandora WiFi: Probe done

[   33.625976] mmc2: card claims to support voltages below the defined range. These will be ignored.

[   33.634979] mmc2: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.

[   33.648498] mmc2: new SDIO card at address 0001

[   33.688415] wl1251: using dedicated interrupt line

[   33.688507] mmci-omap mmci-omap.2: MMC IRQ 0x208003 : CC TC ERRI DCRC

[   33.688690] wl1251: ERROR sdio write failed (-84)

[   33.711303] mmci-omap mmci-omap.2: MMC IRQ 0x208003 : CC TC ERRI DCRC

[   33.711456] wl1251: ERROR sdio read failed (-84)

[   33.727050] mmci-omap mmci-omap.2: MMC IRQ 0x208003 : CC TC ERRI DCRC

[   33.727111] wl1251: ERROR sdio read failed (-84)

[   33.742523] mmci-omap mmci-omap.2: MMC IRQ 0x208003 : CC TC ERRI DCRC

[   33.742889] wl1251: ERROR sdio read failed (-84)

[   33.758178] mmci-omap mmci-omap.2: MMC IRQ 0x208003 : CC TC ERRI DCRC

[   33.758636] wl1251: ERROR sdio read failed (-84)

[   33.773742] mmci-omap mmci-omap.2: MMC IRQ 0x208003 : CC TC ERRI DCRC

[   33.773895] wl1251: ERROR sdio read failed (-84)

[   33.789428] mmci-omap mmci-omap.2: MMC IRQ 0x208003 : CC TC ERRI DCRC

[   33.789611] wl1251: ERROR sdio read failed (-84)

[   33.824981] mmci-omap mmci-omap.2: MMC IRQ 0x208003 : CC TC ERRI DCRC

[   33.825134] wl1251: ERROR sdio read failed (-84)

[   33.829864] wl1251: WARNING failed to read MAC address from EEPROM

[   34.151397] phy0: Selected rate control algorithm 'minstrel'

[   34.152252] wl1251: loaded

[   34.154998] wl1251: initialized

[   34.480834] udev: renamed network interface wlan0 to wlan12

[   34.726928] sdio_reset_comm():

[   34.759490] mmci-omap mmci-omap.2: MMC IRQ 0x208003 : CC TC ERRI DCRC

[   34.760070] wl1251: ERROR sdio read failed (-84)

[   34.764739] wl1251: ERROR unsupported chip id: 0x22222222

[   34.922180] sdio_reset_comm():

[   34.931823] wl1251_sdio mmc2:0001:1: firmware: requesting wl1251-fw.bin

[   38.838348] wl1251: ERROR timeout waiting for the hardware to complete initialization


It finds the card, then gets a bunch of failed reads (can't read the MAC adress?), then does what looks like reasonable things, then says "Unsupported chip", then requests firmware, then gets a hardware timeout? Half of this looks to me like I have some sort of broken driver (failed download or something), whilst other things - timeouts, failed reads - looks like hardware trouble. Anybody who can shed some light on it for me?


(Oh, and if someone should say "You broke it while opening it" - Nope, it was like this from the start)
 
It could be hardware trouble, but normally, each unit is being tested by Craig to connect to WiFi, so unless he missed this one, hardware should be fine.


It COULD also be a broken firmware, unfortunately, flashing to mtd has no checksum. Sounds more like hardware to me as well, but you should try anything that COULD also cause that first.


Try reflashing (best use the latest HF5 Beta 2) and retry.


If it works, then you're happy.


If the same error keeps happening, it sounds like some broken line to the WiFi module :/
 
Hm. Considering that wifi is not terribly important to me, I'll wait until hotfix 5 is out of beta and try it then. After all, I have to save the planet from Shinra, save princess Toadstool from that weird sword-shaped baddie and return the peace to monster land :)


I did a quick check today so that it wasn't as simple as the antenna cable having come loose, but no such luck.
 
Well, come to think of it, the first times I used it, it found the wifi router but could not connect. Now it does not find it at all. So something has changed. Oh, well. As I said, we'll see, further on :)
 
I can't flash the units without the wifi test succeeding, so it would have had to have passed the test.
Well actually the old flasher did first flash and then test.. Only newer one from last week will do like you say.

The one I have tests the wifi before doing anything else, if it fails all I can do is press enter to power down.
 
It is the same, unfortunately. And by now I have also tried reflashing with hotfix 5, which didn't help. So, quite likely:


* It is hardware related, and


* I quite possibly caused (or at least worsened) it myself, since, looking back, I did get other things before I opened it up to look at my shoulder buttons. At first, I could turn on wifi and get a proper scan of the local hotspots, and that doesn't happen now.


If that is so, it is still not too bad: Considering how I use it, my shoulder buttons are more important than the wifi :) I'll quite likely have a little discussion with Craig in the future on how to resolve this (I.e. how to fix it and who shall pay for it), but since it is not incredibly damaging to me, I'll hold back on that to let the team concentrate on churning out the new ones.
 
Back
Top