Topic: wireless can't connect after using falconwing 1.0.3 image

Device: Insignia Infocast 3.5"

I dd'ed the falconwing 1.0.3 image from here to another sd card and wireless didn't work, could see some ssid's listed but unable to connect to any.
Ok, it's this image it's old, doesn't work, I thought.

Back to the original sd card with 1.0.7, and the problem is still present.

driver loads fine at boot:

[   14.400000] phy0 -> rt2500usb_init_eeprom: Error - Invalid RT chipset detected.
[   14.400000] phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
[   14.440000] usbcore: registered new interface driver rt2500usb
[   15.020000] phy1: Selected rate control algorithm 'minstrel'
[   15.030000] Registered led device: rt73usb-phy1::radio
[   15.040000] Registered led device: rt73usb-phy1::assoc
[   15.040000] Registered led device: rt73usb-phy1::quality
[   15.060000] usbcore: registered new interface driver rt73usb
[   15.600000] rt73usb 1-1.1:1.0: firmware: requesting rt73.bin

but then:

[   40.920000] wlan0: direct probe to AP c3bf122c (try 1)
[   40.920000] wlan0: direct probe responded
[   40.920000] wlan0: authenticate with AP c3bf122c (try 1)
[   52.210000] wlan0: direct probe to AP c3bf122c (try 1)
[   52.220000] wlan0: direct probe responded
[   52.220000] wlan0: authenticate with AP c3bf122c (try 1)
[   60.390000] wlan0: direct probe to AP c3bf122c (try 1)
[   69.180000] wlan0: direct probe to AP c3bf122c (try 1)
[   69.180000] wlan0: direct probe responded
[   69.180000] wlan0: authenticate with AP c3bf122c (try 1)
[   80.500000] wlan0: direct probe to AP c3bf122c (try 1)
[   80.510000] wlan0: direct probe responded
[   80.510000] wlan0: authenticate with AP c3bf122c (try 1)
[   84.980000] wlan0: direct probe to AP c3bf122c (try 1)
[   84.990000] wlan0: direct probe responded
[   84.990000] wlan0: authenticate with AP c3bf122c (try 1)
[  246.430000] NET: Registered protocol family 10
[  246.440000] ADDRCONF(NETDEV_UP): wlan0: link is not ready

console message(repeats):
[  614.000000] ADDRCONF(NETDEV_UP): wlan0: link is not ready

It scans ok:
# iwlist wlan0 scan
wlan0     Scan completed :
          Cell 01 - Address: 00:1F:F3:BB:5D:EC
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
                    Quality=30/70  Signal level=-80 dBm 
                    Encryption key:on
                    ESSID:"mini"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=00000001163d0d91
                    Extra: Last beacon: 490ms ago
                    IE: Unknown: 00046D696E69
                    IE: Unknown: 010882848B962430486C
                    IE: Unknown: 03010B
                    IE: Unknown: 2A0100
                    IE: Unknown: 2F0100
                    IE: Unknown: 32040C121860
                    IE: Unknown: 2D1A1C181BFFFF000000000000000000000000000000000000000000
                    IE: Unknown: 3D160B081100000000000000000000000000000000000000
                    IE: Unknown: DD090010180200F0050000
                    IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
                    IE: Unknown: DD1E00904C331C181BFFFF000000000000000000000000000000000000000000
                    IE: Unknown: DD1A00904C340B081100000000000000000000000000000000000000

I tried WPA2-PSK AP mode to my router, WEP AP mode to another device and WEP keyless adhoc to my Mac and none worked.

I tried the wireless usb on my Mac but the RALINK Wireless Utility just kept crashing, will try on a Windows and Linux machine tomorrow.

But, is it possible that when the 1.0.3 firmware loaded the firmware to the ralink chip it somehow "damaged" it?
Any help or hint is most welcomed.

Re: wireless can't connect after using falconwing 1.0.3 image

Make that two of us. I have 3 "real" Chumby but thought this would be a great deal. It has been nothing but a headache trying to get it to connect to wireless.
Anyone have any insight on this?