Comment 16 for bug 708712

I'm seeing this problem too with Natty Beta 1 with the latest updates. Sometimes it works after a cold boot, sometimes not.

After one cold boot I saw these messages in dmesg, which I'm not sure have been mentioned previously:

rtl819xE:Nic is disabled! Can't tx packet len=82 qidx=6!!!
and
rtl819xE:Download Firmware: Put code fail!
rtl819xE:ERR in CPUcheck_maincodeok_turnonCPU()
rtl819xE:ERR in init_firmware()
rtl819xE:ERR!!! NicIFEnableNIC(): initialization is failed!

Another problem is that the driver doesn't see channels 12 or 13, though I'm in the UK and it should see them. There are several APs around here all sending "GB " in their beacon frames. Dmesg includes these messages:

cfg80211: World regulatory domain updated:
cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

The Voria driver works fine with channel 13 on Maverick, but it's not yet available for Natty.

I'm attaching the full output from dmesg.