#6279 HIGH Retriag: cannot see Linksys AP
Zarro Boogs per Child
bugtracker at laptop.org
Thu Jan 31 11:37:04 EST 2008
#6279: cannot see Linksys AP
-----------------------+----------------------------------------------------
Reporter: gildea | Owner: dwmw2
Type: defect | Status: new
Priority: high | Milestone: Retriage, Please!
Component: wireless | Version: Build 653
Resolution: | Keywords:
Verified: 0 | Blocking:
Blockedby: |
-----------------------+----------------------------------------------------
Changes (by cscott):
* cc: kim, carrano (added)
* owner: dcbw => dwmw2
* priority: normal => high
* component: network manager => wireless
* milestone: Update.1 => Retriage, Please!
Comment:
I suspect this is related to the wireless firmware, rather than network
manager (but I could be wrong). The wireless firmware hasn't changed much
between 656 and update.1, but I'd guess the first step would be to try to
reproduce this with an update.1 candidate and/or the latest joyride.
Stephen, 'olpc-update joyride-1617' will give the latest joyride, which
has wireless firmware 5.110.22.p1. At the moment, the update.1 candidate
has a slightly older firmware: 'olpc-update update.1-690' will give you
5.110.20.p49. The latest stable build 656 has firmware 2:5.110.20.p47.
You can check your wireless firmware version with 'rpm -qa | fgrep
libertas'.
My suspicion is that none of these will actually solve your problem, but
I'd like to be pleasantly surprised. We're trying to figure out if
5.110.22.p1 is enough of an improvement over 5.110.20.p49 to merit its
inclusion in update.1 (even though we're in code freeze); clearly a report
that one worked for you but not the other could inform that choice.
If you find that none of these work, I'll expect we'll want logs against
the latest firmware (the version in joyride). dcbw and/or carrano can
give you instructions there; I'm not sure exactly what logs will be
useful. If you can manually configure the network
('/etc/init.d/NetworkManager stop' and then 'iwconfig eth0 essid ....' and
'dhclient eth0') that would tend to implicate NetworkManager; if not even
manual configuration will work, it would implicate the firmware and/or the
kernel driver.
(Actually, since your problem is that it doesn't show up in the network
view, the output of 'iwlist eth0 scan' would be useful as well -- does it
show up there, by any chance?)
--
Ticket URL: <http://dev.laptop.org/ticket/6279#comment:1>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system
More information about the Bugs
mailing list