Re: [Trac #278] Bad firmware causes WeirdShit® to happen.

[Zarro Boogs per Child]

#278: Bad firmware causes WeirdShit® to happen.
--------------------+-------------------------------------------------------
 Reporter:  dwmw2   |        Owner:  marcelo
     Type:  defect  |       Status:  new    
 Priority:  normal  |    Milestone:  BTest-1
Component:  distro  |   Resolution:         
 Keywords:          |  
--------------------+-------------------------------------------------------
Comment (by dcbw):

 Replying to [comment:6 dwmw2]:
 > Wireless works when the hardware doesn't screw up, but NetworkManager
 isn't.
 >
 > {{{
 > Nov  4 15:02:46 localhost NetworkManager: <WARNING>
 nm_device_802_11_wireless_set_essid (): error setting ESSID to '' for
 device eth0: Invalid argument
 > }}}
 > {{{
 > Nov  4 15:04:04 localhost NetworkManager: <WARNING>
 nm_dbus_get_networks_cb (): error received:
 org.freedesktop.DBus.Error.NoReply - Did not receive a reply. Possible
 causes include: the remote application did not send a reply, the message
 bus security policy blocked the reply, the reply timeout expired, or the
 network connection was broken..
 > }}}

 This appears to be a driver bug; I'll need to clean this up when doing the
 async association in work queus.  The driver needs to accept '' as the
 "association to any" setting.

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