[Trac #258] No Functional Wireless Driver

[Zarro Boogs per Child]

#258: No Functional Wireless Driver
---------------------+------------------------------------------------------
 Reporter:  mfoster  |        Owner:  marcelo
     Type:  defect   |       Status:  new    
 Priority:  blocker  |    Milestone:  BTest-1
Component:  kernel   |   Resolution:         
 Keywords:           |  
---------------------+------------------------------------------------------
Comment (by marcelo):

 Replying to [comment:15 blizzard]:
 > Status update from Cambridge:
 >
 > o Dan fixed an oops that happened on module unload after a boot2 flash
 (a clearly correct fix)
 >
 > o NetworkManager was not running during any of these tests listed below
 >
 > o Dan and Chris were able to successfully flash back and forth from the
 old boot2 code to the new boot2 code for testing on a _a-test_ board
 >
 > o They bricked the wireless on 1 of 2 _b-test_ boards in Cambridge by:
 > - Flashed the 3104 boot2 code
 > - Did not reboot
 > - insmod the standard wireless driver without any module arguments and
 it oopsed
 >   http://dev.laptop.org/~cjb/libertas-oops
 > - rebooted and insmode the driver for normal operation
 > - driver reported boot2 3104, appeared to attempt to load firmware and
 failed at the end of the load
 >   http://dev.laptop.org/~cjb/libertas-dmesg
 > - it kept looping, trying to reload the firmware at this point

 I've committed a change which could help here... We were not resetting the
 retry counter, which could cause the driver to not wait long enough for
 the device to come up...

 Is the Marvell chip still bricked on this particular board?

-- 
Ticket URL: <http://dev.laptop.org/ticket/258#comment:18>
One Laptop Per Child <http://laptop.org/>