Hi Pazzo, On Wed, 2010-07-21 at 19:27 +0200, ext Pazzo Da Legare wrote: > Dear All again, > > I've just test with compact-wireless-2010-07-20 but I've the same problem: > > root@hawkboard:~# ifconfig wlan0 192.168.0.1 up > [ 68.920000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-fw.bin > [ 69.100000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-nvs.bin > [ 69.510000] ADDRCONF(NETDEV_UP): wlan0: link is not ready > root@hawkboard:~# [ 70.020000] wl1271: ERROR ELP wakeup timeout! > [ 70.520000] wl1271: ERROR ELP wakeup timeout! > > > looking at dmesg: > > [ 68.920000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-fw.bin > [ 69.100000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-nvs.bin > [ 69.500000] wl1271: firmware booted (Rev 6.1.0.0.310) > [ 69.510000] ADDRCONF(NETDEV_UP): wlan0: link is not ready > [ 70.020000] wl1271: ERROR ELP wakeup timeout! > [ 70.520000] wl1271: ERROR ELP wakeup timeout! > > [ 68.920000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-fw.bin > [ 69.100000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-nvs.bin > [ 69.500000] wl1271: firmware booted (Rev 6.1.0.0.310) > [ 70.020000] wl1271: ERROR ELP wakeup timeout! > [ 70.520000] wl1271: ERROR ELP wakeup timeout! > > Do you have any clue? I'm not sure what this is, but usually an ERROR ELP wakeup timeout means that the firmware has crashed. Could you enable the following DEBUG flags in wl1271.h and send the logs again? Maybe they provide more clues... #define DEBUG_LEVEL (DEBUG_BOOT | DEBUG_ACX | DEBUG_CMD | DEBUG_PSM | \ DEBUG_IRQ | DEBUG_EVENT) -- Cheers, Luca. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
