Weird WLAN problem after stupid upgrade attempt
Tom Seago
tom at tomseago.com
Wed Jan 9 19:20:02 EST 2008
I've updated to the Q2D08 firmware now.
Whereas the '07 firmware seemed to run the test /wlan ok, but the wlan
card wasn't visible to the regular OS, now when I run the same command
on the '08 firmware I get
ok test /wlan
Device /wlan not found.
ok
So what's the verdict. Do folks think I should RMA this thing? It
seems like it got busted merely via software - which one would
normally not expect to be possible.
(-: Tom ;-)
On Jan 6, 2008, at 12:56 AM, Tom Seago wrote:
> Hi Mitch. I got my developer key and ran "test /wlan" at the ofw
> prompt. That seemed to work! At least, it scrolled a fairly large
> amount of info up the screen which appeared to be the stats of
> various visible wifi networks. However, all my problems where the
> OS can't see the card remain.
>
> It makes me happy that this appears to be software not hardware. It
> still confuses me how I managed to get into this bizarre situation
> though. Is there a way to do any more complete of a device wipe
> beyond the normal reflashing procedure using the signed build from a
> usb stick?
>
> I appreciate your help. I hope we can figure out what's up with this
> thing.
>
> (-: Tom ;-)
>
>
> On Jan 4, 2008, at 10:22 AM, Mitch Bradley wrote:
>
>> Tom Seago wrote:
>>> ...
>>> Another thing I have done is run the POST diagnostics by holding
>>> the left rocker button during boot. I did this on both machines
>>> at the same time to diff the results. Both say that usb port 0
>>> is in use - good. But the working machine did scroll some wlan
>>> diagnostic information up the screen at the end of the the video
>>> tests that the broken machine did not do. The broken machine did
>>> not report an error - but it clearly did not run the same wlan
>>> test.
>>>
>>>
>>
>> Chris Ball wrote:
>>> Hi Tom,
>>>
>>> Once you have your developer key, please run:
>>>
>>> ok test /wlan
>>>
>>> If that fails too, it should be clear that we need to RMA and
>>> replace
>>> your laptop. Thanks!
>>
>> The POST diags that Tom ran include the "test /wlan" step. That
>> diagnostic info that scrolled by is a dump of the access point scan
>> info. It happens just before the touchpad test.
>>
>> My recommendations:
>>
>> a) Remove all power - AC and battery - for a few seconds to reset
>> the wireless really well, then reboot and try the POST diags again.
>>
>> b) If that doesn't fix it, email me when you get your developer key
>> and I'll work with you on IRC to see if we can learn more about the
>> failure details.
>>
>> Mitch Bradley
>>
>>
>
More information about the Devel
mailing list