Re: xo-1 os300 -- switch off mesh?
martin wrote: Hi all, Is there a way to tweak the os300 build so that it brings up the Libertas device just as eth0 (and doesn't enable the 802.11s features in the firmware)? echo 0 /sys/class/net/eth0/lbs_mesh as per http://wiki.laptop.org/go/Mesh_Network_Details#Disabling_the_mesh_network Not sure what it does exactly but the msh0 interface is gone and the wireless led does not randomly blink when in suspend mode (laptop closed). ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Trac#10232: WiFi dies on suspended XO-1, os300
Excerpts from Hal Murray's message of Wed Jul 14 20:27:37 + 2010: A simple edit makes suspend/wakeup from WiFi work on XO-1 running os300. So I've been testing it. It works most of the time, but occasionally stops waking up from WiFi. Wakeup from touchpad works fine. There's a very annoying and easy to trigger race condition regarding suspend. If a wake-up event happens while we are still suspending (either between the last check in powerd and triggering the suspend using rtcwake, and/or already on the kernel side) it will be ignored. For input devices this isn't as bad because any further event (key press / release, touchpad movement) will wake up the XO. But AIUI the libertas chip will wait for the host (= CPU / kernel) to confirm the wake-up event without ever retrying. (delete the a from ethtool -s eth0 wol ua in /usr/sbin/powerd) FWIW I'm using pum. This allows IPv6 to work transparently (IPv6 uses multicast for neighbour discovery). You could add b (broadcast) as a replacement for a (ARP), but at least on some of the networks I'm connected to regularly this is impractical (both Windows SMB and proprietary Cisco router management broadcast traffic). The WiFi LED is off. It blinks when I wake it up by poking the touchpad, but the LED stays off and ping doesn't work. This suggests you lost association to the access point while in suspend. Unfortunately this seems to be a firmware bug (specific to the chip in the XO-1, you won't have this problem on an XO-1.5) that we cannot easily work around in the kernel. If the chip looses association while in suspend, it neither wakes up the host nor tells it about having lost association when the host eventually wakes up. As there's no way for the host to query the current association status (at least I didn't find one in the sparse documentation), the kernel has no way to detect this. The blinking you see upon resume is a WiFi scan. I haven't looked into who triggers this scan - presumably NetworkManager. But since the kernel and thus user space never notices we lost association, this isn't really of interest. So far my tests suggested that WPA rekeying wakes up the host, so the reason for disassociation is probably something else. Even without suspend the XO-1 will disassociate about once or twice a day on average which makes this plausible. But it's merely a loose time-based correlation; I haven't done any specific test to be sure about it. Feel free to copy this to Trac - I just didn't have time to do so yet (and wanted to do some other tests first, but didn't get around to that either). Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
os206 - slow ethernet
Disclaimer: I am not asking for help; I am sharing my experiences. I notice that with os206, ethernet data transfers into the XO-1.5 are running at 2/3 the speed of ethernet data transfers into XO-1 systems. I did not notice with which XO-1.5 build this slow ethernet problem started - but I believe that with os196 and previous, ethernet data transfers into the XO-1.5 ran at the same rate as ethernet data transfers into XO-1 systems. [I'm assuming that the hardware did not recently develop weak transistors.] mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
behaviour of F-keys on XO HS
Hi, On the XO HS (highschool edition, the one with a more normal keyboard) we're facing some questions about how the F keys should function, under sugar and GNOME. The technicalities are in http://dev.laptop.org/ticket/10213 and here is a picture of the keyboard: http://wiki.laptop.org/go/OLPC_Spanish_Non-membrane_Keyboard Under non-sugar environments (e.g. GNOME), myself and Paul are in agreement that in order to change brightness and volume, you should press e.g. Fn+F9 (to decrease brightness). This matches behaviour of normal laptops, including the Dell that I'm writing on. Linux already has mechanisms (once through hal, now through udev) so that when I press Fn+F8 on my Dell, X receives the volume down key press (instead of the Fn+F8 key press), matching what is printed on the keyboard. We want all of the unmodified F-keys to send the normal F-key events (we don't want to map them especially). This is for maximum compatibility with non-sugar environments. For Sugar we have an open question. The F1-F4 keys have the zoom levels printed on them, and pressing the keys unmodified will cause the zoom levels to change (because this is how Sugar is already coded, it responds to the literal F1 keypress). The other keys are: - F5: search/journal - F6: frame - F9: brightness down - F10: brightness up - F11: volume down - F12: volume up For these other keys, when using Sugar, should the user have to press the Fn modifier while pressing the key in order to reach the named function? The advantage of not having to press Fn (i.e. the keys would work unmodified) is that sugar works the way it always has on XO (we retain consistency with XO-1). As for the other option, the advantage of requiring Fn is that we gain consistency between Sugar and GNOME, and between the XO HS and normal laptops (where Fn *is* necessary to reach those alternate functions). (but we do end up with some confusion with the zoom level keys,which will continue to work unmodified) If we decide to make the keys available unmodified in Sugar we would have to change sugar (worldwide, not interested in downstream forked patches) so that F5 on any system opens the journal, F6 on any system opens the frame, etc. How would people feel about that? cheers, Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] behaviour of F-keys on XO HS
On 16 July 2010 10:50, Daniel Drake d...@laptop.org wrote: Under non-sugar environments (e.g. GNOME), myself and Paul are in agreement that in order to change brightness and volume, you should press e.g. Fn+F9 (to decrease brightness). This matches behaviour of normal laptops, including the Dell that I'm writing on. Linux already has mechanisms (once through hal, now through udev) so that when I press Fn+F8 on my Dell, X receives the volume down key press (instead of the Fn+F8 key press), matching what is printed on the keyboard. This convention appears to be changing. My very recent HP notebook requires th Fn button to be pushed to reach the function keys. Everything is reversed. While I don't have the empirical evidence to support a claim that users prefer to have quick access to volume brightness, I think this could be an argument to say that whatever the path of least resistance (in terms of developer cycles) is fine. Tim ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] behaviour of F-keys on XO HS
On 15 Jul 2010, at 23:59, Tim McNamara paperl...@timmcnamara.co.nz wrote: On 16 July 2010 10:50, Daniel Drake d...@laptop.org wrote: Under non-sugar environments (e.g. GNOME), myself and Paul are in agreement that in order to change brightness and volume, you should press e.g. Fn+F9 (to decrease brightness). This matches behaviour of normal laptops, including the Dell that I'm writing on. Linux already has mechanisms (once through hal, now through udev) so that when I press Fn+F8 on my Dell, X receives the volume down key press (instead of the Fn+F8 key press), matching what is printed on the keyboard. This convention appears to be changing. My very recent HP notebook requires th Fn button to be pushed to reach the function keys. Everything is reversed. +1 on Tim's observation, all three Apple laptops I've owned have brightness/volume/exposé/dashboard/etc mapped by default to a single key press, if you want an Fn key you need to hold the Fn button down. There is a system preference to toggle this behaviour, but the majority of Mac applications avoid the use of function keys (same as most Sugar Activities do). Regards, --Gary While I don't have the empirical evidence to support a claim that users prefer to have quick access to volume brightness, I think this could be an argument to say that whatever the path of least resistance (in terms of developer cycles) is fine. Tim ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] behaviour of F-keys on XO HS
May be it's too late, but i was modifying Paint to use the slider keys (F5,F6,F7,F8) to change the size of the brush. I know there aren't other uses of slider in Sugar, but I think it's useful and expressive to have keys to enlarge or reduce the brush, the fonts,etc. If we need F5 and F6 to the journal and the frame we can use F7 and F8 to change sizes but will be different in the actual keyboards and the HS keyboard. You will have other problem with the actual keyboard definition.Pressing fn with any slider key gives no event at all. Gonzalo On Thu, Jul 15, 2010 at 7:50 PM, Daniel Drake d...@laptop.org wrote: Hi, On the XO HS (highschool edition, the one with a more normal keyboard) we're facing some questions about how the F keys should function, under sugar and GNOME. The technicalities are in http://dev.laptop.org/ticket/10213 and here is a picture of the keyboard: http://wiki.laptop.org/go/OLPC_Spanish_Non-membrane_Keyboard Under non-sugar environments (e.g. GNOME), myself and Paul are in agreement that in order to change brightness and volume, you should press e.g. Fn+F9 (to decrease brightness). This matches behaviour of normal laptops, including the Dell that I'm writing on. Linux already has mechanisms (once through hal, now through udev) so that when I press Fn+F8 on my Dell, X receives the volume down key press (instead of the Fn+F8 key press), matching what is printed on the keyboard. We want all of the unmodified F-keys to send the normal F-key events (we don't want to map them especially). This is for maximum compatibility with non-sugar environments. For Sugar we have an open question. The F1-F4 keys have the zoom levels printed on them, and pressing the keys unmodified will cause the zoom levels to change (because this is how Sugar is already coded, it responds to the literal F1 keypress). The other keys are: - F5: search/journal - F6: frame - F9: brightness down - F10: brightness up - F11: volume down - F12: volume up For these other keys, when using Sugar, should the user have to press the Fn modifier while pressing the key in order to reach the named function? The advantage of not having to press Fn (i.e. the keys would work unmodified) is that sugar works the way it always has on XO (we retain consistency with XO-1). As for the other option, the advantage of requiring Fn is that we gain consistency between Sugar and GNOME, and between the XO HS and normal laptops (where Fn *is* necessary to reach those alternate functions). (but we do end up with some confusion with the zoom level keys,which will continue to work unmodified) If we decide to make the keys available unmodified in Sugar we would have to change sugar (worldwide, not interested in downstream forked patches) so that F5 on any system opens the journal, F6 on any system opens the frame, etc. How would people feel about that? cheers, Daniel ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] behaviour of F-keys on XO HS
On Thu, Jul 15, 2010 at 8:23 PM, Gonzalo Odiard godi...@gmail.com wrote: May be it's too late, but i was modifying Paint to use the slider keys (F5,F6,F7,F8) to change the size of the brush. I know there aren't other uses of slider in Sugar, but I think it's useful and expressive to have keys to enlarge or reduce the brush, the fonts,etc. If we need F5 and F6 to the journal and the frame we can use F7 and F8 to change sizes but will be different in the actual keyboards and the HS keyboard. You will have other problem with the actual keyboard definition.Pressing fn with any slider key gives no event at all. Presumably there is a way to detect which keyboard is installed in the machine? While I love Gonzalo's use of the F5-F8 keys, the need for Frame and Journal keys on the non-membrane keyboards is more important in my experience. regards. -walter Gonzalo On Thu, Jul 15, 2010 at 7:50 PM, Daniel Drake d...@laptop.org wrote: Hi, On the XO HS (highschool edition, the one with a more normal keyboard) we're facing some questions about how the F keys should function, under sugar and GNOME. The technicalities are in http://dev.laptop.org/ticket/10213 and here is a picture of the keyboard: http://wiki.laptop.org/go/OLPC_Spanish_Non-membrane_Keyboard Under non-sugar environments (e.g. GNOME), myself and Paul are in agreement that in order to change brightness and volume, you should press e.g. Fn+F9 (to decrease brightness). This matches behaviour of normal laptops, including the Dell that I'm writing on. Linux already has mechanisms (once through hal, now through udev) so that when I press Fn+F8 on my Dell, X receives the volume down key press (instead of the Fn+F8 key press), matching what is printed on the keyboard. We want all of the unmodified F-keys to send the normal F-key events (we don't want to map them especially). This is for maximum compatibility with non-sugar environments. For Sugar we have an open question. The F1-F4 keys have the zoom levels printed on them, and pressing the keys unmodified will cause the zoom levels to change (because this is how Sugar is already coded, it responds to the literal F1 keypress). The other keys are: - F5: search/journal - F6: frame - F9: brightness down - F10: brightness up - F11: volume down - F12: volume up For these other keys, when using Sugar, should the user have to press the Fn modifier while pressing the key in order to reach the named function? The advantage of not having to press Fn (i.e. the keys would work unmodified) is that sugar works the way it always has on XO (we retain consistency with XO-1). As for the other option, the advantage of requiring Fn is that we gain consistency between Sugar and GNOME, and between the XO HS and normal laptops (where Fn *is* necessary to reach those alternate functions). (but we do end up with some confusion with the zoom level keys,which will continue to work unmodified) If we decide to make the keys available unmodified in Sugar we would have to change sugar (worldwide, not interested in downstream forked patches) so that F5 on any system opens the journal, F6 on any system opens the frame, etc. How would people feel about that? cheers, Daniel ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] behaviour of F-keys on XO HS
On Thu, Jul 15, 2010 at 8:23 PM, Gonzalo Odiard godi...@gmail.com wrote: May be it's too late, but i was modifying Paint to use the slider keys (F5,F6,F7,F8) to change the size of the brush. I know there aren't other uses of slider in Sugar, but I think it's useful and expressive to have keys to enlarge or reduce the brush, the fonts,etc. If we need F5 and F6 to the journal and the frame we can use F7 and F8 to change sizes but will be different in the actual keyboards and the HS keyboard. You will have other problem with the actual keyboard definition.Pressing fn with any slider key gives no event at all. This is a regression. It used to (2007) return keycodes. -walter Gonzalo On Thu, Jul 15, 2010 at 7:50 PM, Daniel Drake d...@laptop.org wrote: Hi, On the XO HS (highschool edition, the one with a more normal keyboard) we're facing some questions about how the F keys should function, under sugar and GNOME. The technicalities are in http://dev.laptop.org/ticket/10213 and here is a picture of the keyboard: http://wiki.laptop.org/go/OLPC_Spanish_Non-membrane_Keyboard Under non-sugar environments (e.g. GNOME), myself and Paul are in agreement that in order to change brightness and volume, you should press e.g. Fn+F9 (to decrease brightness). This matches behaviour of normal laptops, including the Dell that I'm writing on. Linux already has mechanisms (once through hal, now through udev) so that when I press Fn+F8 on my Dell, X receives the volume down key press (instead of the Fn+F8 key press), matching what is printed on the keyboard. We want all of the unmodified F-keys to send the normal F-key events (we don't want to map them especially). This is for maximum compatibility with non-sugar environments. For Sugar we have an open question. The F1-F4 keys have the zoom levels printed on them, and pressing the keys unmodified will cause the zoom levels to change (because this is how Sugar is already coded, it responds to the literal F1 keypress). The other keys are: - F5: search/journal - F6: frame - F9: brightness down - F10: brightness up - F11: volume down - F12: volume up For these other keys, when using Sugar, should the user have to press the Fn modifier while pressing the key in order to reach the named function? The advantage of not having to press Fn (i.e. the keys would work unmodified) is that sugar works the way it always has on XO (we retain consistency with XO-1). As for the other option, the advantage of requiring Fn is that we gain consistency between Sugar and GNOME, and between the XO HS and normal laptops (where Fn *is* necessary to reach those alternate functions). (but we do end up with some confusion with the zoom level keys,which will continue to work unmodified) If we decide to make the keys available unmodified in Sugar we would have to change sugar (worldwide, not interested in downstream forked patches) so that F5 on any system opens the journal, F6 on any system opens the frame, etc. How would people feel about that? cheers, Daniel ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] behaviour of F-keys on XO HS
This is a regression. It used to (2007) return keycodes. May be. Where is the keyboard definition? Gonzalo ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] behaviour of F-keys on XO HS
On 15 July 2010 18:26, Walter Bender walter.ben...@gmail.com wrote: Presumably there is a way to detect which keyboard is installed in the machine? While I love Gonzalo's use of the F5-F8 keys, the need for Frame and Journal keys on the non-membrane keyboards is more important in my experience. Yes, let's limit this discussion to the non-membrane keyboard. Not planning any changes in the membrane keyboard (without separate discussion). Walter, what's your opinion? Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] behaviour of F-keys on XO HS
daniel wrote: On 15 July 2010 18:26, Walter Bender walter.ben...@gmail.com wrote: Presumably there is a way to detect which keyboard is installed in the machine? While I love Gonzalo's use of the F5-F8 keys, the need for Frame and Journal keys on the non-membrane keyboards is more important in my experience. Yes, let's limit this discussion to the non-membrane keyboard. Not planning any changes in the membrane keyboard (without separate discussion). Walter, what's your opinion? i guess i don't understand why the question is either/or. as i've coded it (so color me biased :-), when running gnome (or anything not sugar), all of the function keys are available to applications. only four of the keys with special labels on them have any meaning in gnome (i.e., the four brightness/volume keys) and those are available with the Fn key. i think everyone (except apple, i'm learning tonight) agrees this is the correct setup when not in sugar. when in sugar (assuming a small patch to sugar, which could presumably be made XO-dependent) all of the specially labeled keys are available without an Fn modifier, and as such act just as they do on the membrane keyboard. this includes the brightness/volume keys. this felt both more compatible and discoverable to me, and to cjb, but this laptop is for an older audience, so maybe that doesn't matter. in addition, the brightness and volume keys are available with Fn. for more uniformity, the rest of the special-labeled F1-F6 could be made available in sugar with Fn as well, with a bit more udev keybinding. as far as i understood, sugar doesn't make much use of the function keys above F1-F4, so i didn't think there was a need to keep them all clear. am i wrong about this? my limited sugar use has been on XO laptops -- i don't have much experience with SoaS. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New XO-1 10.1.2 build 301
El Wed, 14-07-2010 a las 18:39 -0400, Chris Ball escribió: -NetworkManager-0.7.2.997-2.git20100609.fc11.i586 +NetworkManager-0.7.2.997-2.git20100609.fc11.olpc1.i586 Shouldn't this be .olpc1.fc11? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[Server-devel] Offline update
Is it possible to do an offline update of the XS (i.e. download updates and then run them offline?) David Leeming ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
