Where is this on the priority list? What can I do to help?
("Go away until the release is out." might be the right answer.)
There are (at least) 4 tickets on this:
http://dev.laptop.org/ticket/10232 WiFi dies on suspended XO-1, os300
http://dev.laptop.org/ticket/10092 Networking broken over
I have blundered into what may be a workaround for bug 10232
http://dev.laptop.org/ticket/10232
The fix is to edit
/usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service
and add " -dddt" to the end of the Exec line. It ends up looking like:
Exec=/usr/sbin/wpa_supplicant -c
On 08/24/2010 06:51 PM, Hal Murray wrote:
> I've got the back of a system off. Is there a handy place to get a
> scope/meter on the wakeup signal from the WiFi module to the EC? Is that
> signal edge triggered or level sensitive?
Easiest place is on the WLAN module Pin 49. Its connected to EC
hal wrote:
>
> I have blundered into what may be a workaround for bug 10232
> http://dev.laptop.org/ticket/10232
>
> The fix is to edit
> /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service
> and add " -dddt" to the end of the Exec line. It ends up looking like:
> is this still consistent for you?
No, it started hanging again shortly after I sent that message. :( ??
> i've just released a new powerd-27 which contains a fix for XO-1 which might
> affect whether power to the wlan is maintained in some cases, and might also
> cause wake-on-wlan to be dis
[cc += olpc-devel]
El Wed, 25-08-2010 a las 11:05 +1000, fors...@ozonline.com.au escribió:
> OS373pyg
> Wifi is locked up after resume from sleep, must restart.
> I presume this bug is being tracked at dev.laptop.org/ in one of the 4
> tickets below
> http://dev.laptop.org/ticket/10232 WiFi d
tony -- thanks for this. if you could, please open a trac ticket (bug
report) at http://dev.laptop.org to describe this issue. the next
time it occurs, in order to more simply gather most of the information
bernie asked for, plus a little more that may be useful, please run
the command "olpc-log"
Bernie
Sorry, on closer inspection its not locked up, it just looks like its locked up
because it is doing something else for a long time.
Can be replicated 100%. Shut the lid for a while, 5 minutes is not long enough
1.5 hours is. Resume from sleep. The Wifi shows it is connected at 100% signa
> If you spot this bug again, could you please:
>
> * check whether eth0 is still visible with "ifconfig -a"
>
> * check whether the Marvell 8xxx is still visible with "lsusb"
>
> * "dmesg >dmesg.out" and attach it to the bug. Dextrose enables
>libertas debug in /etc/rc.local to help diag
> * "dmesg >dmesg.out" and attach it to the bug. Dextrose enables
>libertas debug in /etc/rc.local to help diagnose this bug.
took me 10 minutes after it came good to work out dmesg so this is a bit later
than the event:
[0.00] Linux version 2.6.31_xo1-20100701.1605.1.olpc.a8f1b26
El Wed, 25-08-2010 a las 20:45 +1000, fors...@ozonline.com.au escribió:
> > * "dmesg >dmesg.out" and attach it to the bug. Dextrose enables
> >libertas debug in /etc/rc.local to help diagnose this bug.
>
> took me 10 minutes after it came good to work out dmesg so this is a bit
> later than
attached file dmesg___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
> That's odd, debug does not seem to be on.
>
> Is this really os373py? What's in /etc/rc.local?
Still getting my head round this stuff. I presume [xx.xx] is the timestamp in
seconds. The log activity dmesg captures the first 16 seconds after startup,
dmesg in terminal shows [xx.xx]=1 apro
13 matches
Mail list logo
