[Trac #258] No Functional Wireless Driver
Zarro Boogs per Child
bugtracker at laptop.org
Sun Nov 12 01:39:53 EST 2006
#258: No Functional Wireless Driver
---------------------+------------------------------------------------------
Reporter: mfoster | Owner: marcelo
Type: defect | Status: new
Priority: blocker | Milestone: BTest-1
Component: kernel | Resolution:
Keywords: |
---------------------+------------------------------------------------------
Comment (by jg):
Commits:
e1d3b3f94931b69207ceef3dd636621fe6f47d0d
e37aa4d8558921a916eafc4efe649bd7764a32b8
4daea8dc46cab7db7ec1d253068e1b361e886208
Should have it working again, with some niggling problems remaining.
o Deferred association patch is pushed to infradead libertas-2.6
- Fixes the eccentric iwconfig command ordering constraints
- Fixes a bunch of odd errors on association due to the above
- WPA is almost completely untested; not a blocker. Unencrypted
and WEP have been tested
- needs more testing, will be in a kernel build tonight
- 'iwconfig ethX essid any' doesn't work yet, trivial fix but
needs some small amount of investigation
- Ad-Hoc association might not choose correct channel
- on my laptop, apps block in ICE X11 session management stuff
after a while hanging on name resolution; however pinging
unresolved stuff from a terminal works, nslookup of previously
unknown hostnames works, etc. This is likely glibc not noticing
updated resolv.conf. Remains to be seen whether this is a
problem on the boards themselves.
- driver takes a long time (10 - 30 seconds) to make itself known
to HAL, and therefore to NetworkManager. Symptoms are that
NetworkManager doesn't detect the presence of the card for
a while after an 'insmod'. This is because HAL does not see
the card for a while. Could be a udev problem or the driver
not poking the right things on startup.
- 'iwconfig chan' and 'iwconfig freq' don't go through the
new deferred association process, but the driver only allows
setting the channel/frequency in Ad-Hoc mode anyway. Needs
to be fixed before Sunday night but not a blocker.
- Driver still doesn't verify firmware before load; this is a
trivial fix and not a blocker.
- Haven't had time to test the forced-8388 hard reset on the ECO'd
board Jim did; Chris Ball may test tonight and it will
surely be run through tomorrow
o NetworkManager
- Needs a few fixes for Ad-Hoc networking on startup and such; may
not be a blocker.
- Needs testing with the new driver on the boards
o NM Sugar applet
- Need to implement the wireless key request callback and UI bits,
fairly trivial
- Needs some more testing with the new wireless driver
- Possibly add a "Create wireless network" item; not a blocker
--
Ticket URL: <http://dev.laptop.org/ticket/258#comment:22>
One Laptop Per Child <http://laptop.org/>
More information about the Bugs
mailing list