Re: [Testing] first play with new XO 1.5 machines
On Thu, Oct 22, 2009 at 4:03 AM, Daniel Drake d...@laptop.org wrote: We already discussed this a lot in another thread. It should not be automatic. The thread is titled [Sugar-devel] [Design] Ad-hoc networks - New Icons Yep -- I did read that thread, way back. In ad-hoc, there is just one beacon master. Due to cheap radios and interference etc, the beacon master will switch around frequently So there is a scheme for beacon master-y to switch around? If it works in practice -- that actually may do the right thing. 2. This kind of situation will happen frequently: A - B - C B can see both users A and C on his network view. A can only see B, and C can only see B. B shares an activity. Both A and C join. However, anything done by A cannot be seen by C and vice-versa, because they are too far apart. Ok, but if they are close enough it will work. The question is: if we tell all our nodes to use the same ESSID (or a set of 3 ESSIDs, one per freq), will independently created networks join and split reasonably well? Ad-hoc will work well for the cases where the children get together in a small space and explicitly create a throwaway network. The small space works with younger kids. The explicitly create... doesn't. H. If we wanted the unreliable mesh instead of the unreliable ad-hoc... On F11-XO-1.5 we are lacking - 802.11s driver/firmware (which could be sub'd by open80211s) - NM support (does it play ball w open80211s?) - Sugar support. For F-11 on XO-1 - NM support - Sugar support Would that be correct? cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] first play with new XO 1.5 machines
2009/10/22 Martin Langhoff martin.langh...@gmail.com: On Thu, Oct 22, 2009 at 4:03 AM, Daniel Drake d...@laptop.org wrote: We already discussed this a lot in another thread. It should not be automatic. The thread is titled [Sugar-devel] [Design] Ad-hoc networks - New Icons Yep -- I did read that thread, way back. In ad-hoc, there is just one beacon master. Due to cheap radios and interference etc, the beacon master will switch around frequently So there is a scheme for beacon master-y to switch around? If it works in practice -- that actually may do the right thing. It rarely does. Ad-hoc is based on the concept shout unless you hear someone else shouting. In reality it just ends up with a lot of shouting. 2. This kind of situation will happen frequently: A - B - C B can see both users A and C on his network view. A can only see B, and C can only see B. B shares an activity. Both A and C join. However, anything done by A cannot be seen by C and vice-versa, because they are too far apart. Ok, but if they are close enough it will work. The question is: if we tell all our nodes to use the same ESSID (or a set of 3 ESSIDs, one per freq), will independently created networks join and split reasonably well? No - ad-hoc is so simple that there is nothing in the design to make this happen. It could happen by coincidence though, if circumstances were to arise such that B were to become beacon master. This would only happen if the existing beacon master dropped out for a while *and* if B has a faster clock than the other remaining node. But then, a few minutes later, consider B becoming the beacon master, C hosting a shared activity with a new node D, which cannot see B. Same problem, and no coincidental solution other than everyone moving into good radio range of each another. If we wanted the unreliable mesh instead of the unreliable ad-hoc... On F11-XO-1.5 we are lacking - 802.11s driver/firmware (which could be sub'd by open80211s) - NM support (does it play ball w open80211s?) - Sugar support. For F-11 on XO-1 - NM support - Sugar support Would that be correct? Yes. The XO-1 stuff is pretty much done - Sugar patches are available, and the NM support is in NM-0.8 and scheduled to be included in NM-0.7 after the next release. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] first play with new XO 1.5 machines
2009/10/22 Daniel Drake d...@laptop.org: Ok, but if they are close enough it will work. The question is: if we tell all our nodes to use the same ESSID (or a set of 3 ESSIDs, one per freq), will independently created networks join and split reasonably well? No - ad-hoc is so simple that there is nothing in the design to make this happen. It could happen by coincidence though, if circumstances were to arise such that B were to become beacon master. This would only happen if the existing beacon master dropped out for a while *and* if B has a faster clock than the other remaining node. But then, a few minutes later, consider B becoming the beacon master, C hosting a shared activity with a new node D, which cannot see B. Same problem, and no coincidental solution other than everyone moving into good radio range of each another. Oops, I misread the part of the mail you were responding too. Ignore my example :) But my point still remains - networks will split undesirably, there will be some joins too but you can't control them and they will be unlikely to be as desired. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] first play with new XO 1.5 machines
On Thu, Oct 22, 2009 at 09:41:22AM +0200, Martin Langhoff wrote: On Thu, Oct 22, 2009 at 4:03 AM, Daniel Drake d...@laptop.org wrote: 2. This kind of situation will happen frequently: A - B - C B can see both users A and C on his network view. A can only see B, and C can only see B. B shares an activity. Both A and C join. However, anything done by A cannot be seen by C and vice-versa, because they are too far apart. Ok, but if they are close enough it will work. The trouble is that even in the same 10m diameter room, close enough will stop working under certain conditions, some of the time. The signal measured by the radio can vary through: 1. distance, 2. angle of antennae relative to the other antennae, 3. reflections, 4. refractions, 5. noise from other radio sources (including laptops in the same room that may have missed a beacon). The question is: if we tell all our nodes to use the same ESSID (or a set of 3 ESSIDs, one per freq), will independently created networks join and split reasonably well? I've not tested that scenario. Interesting possibility. Ad-hoc will work well for the cases where the children get together in a small space and explicitly create a throwaway network. The small space works with younger kids. The explicitly create... doesn't. XO-1 explicitly or spontaneously creates, based on icon trigger in Neighborhood View. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Test firmware
On 22.10.2009, at 01:05, Rafael Enrique Ortiz Guerrero wrote: On Tue, Oct 20, 2009 at 5:10 PM, Mitch Bradley w...@laptop.org wrote: It also has a fun feature for your amusement: ok screen-ih iselect ok 40 30 set-scaled-resolution (It also works with more conventional resolutions like d# 1024 d# 768 set-scaled-resolution, but not with resolutions larger than the screen's native size of 1200 x 900.) Nice. Nice indeed :) I assume the gribblies along the edges come from using a bitmap font, which cannot tile the other resolutions perfectly? - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] first play with new XO 1.5 machines
On Thu, Oct 22, 2009 at 11:51 AM, Daniel Drake d...@laptop.org wrote: 2009/10/22 Tomeu Vizoso to...@sugarlabs.org: What would be more reliable in the under a tree use case: ad-hoc or mesh with a max of 1 hop? Mesh, since everyone does their own beaconing. That's my guess too. But the hard-to-answer question is how much more reliable? So we can answer is it worth the big effort? But they would both break our ideas of collaboration quite significantly. IME, successful uses of under-a-tree are not using multi-hop -- at least not to any advantage. Why do you say 1-hop mesh would break significantly? One of the biggest headaches we have to deal with, even when we have infrastructure networks, is the bug where every XO has a different set of neighbours on the neighbourhood view. That is true from a user PoV, but in practice it lives higher in the stack -- Salut and Telepathy in general is where the issue lies. We still have bugs there that are hard to fix. I now realize we'd forgotten about Cerebro. If anyone is going to take the hard road, it may be a viable option -- did we ever have a clear plan of what it'd take to integrate it fully (where 'fully' means that things just work at least roughly to where they do on 8.2.1). cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] first play with new XO 1.5 machines
On Thu, Oct 22, 2009 at 03:36:50PM +0545, Daniel Drake wrote: One of the biggest headaches we have to deal with, even when we have infrastructure networks, is the bug where every XO has a different set of neighbours on the neighbourhood view. Now we'd be making that bug a feature. Isn't this bug/feature an explicit goal of Gadget/Sugar: 1) They'll see their friends, the result of the active searches and a maximum of $N random buddies and $N' random activities http://lists.sugarlabs.org/archive/sugar-devel/2008-June/006351.html 2) jarabe/model/neighborhood.py line 39 40: http://cgit.sugarlabs.org/sugar/mainline/tree/src/jarabe/model/neighborhood.py#n39 ...it's used around line 130, among others: http://cgit.sugarlabs.org/sugar/mainline/tree/src/jarabe/model/neighborhood.py#n130 I've never liked that limitation, but I suspect I'm not understanding something because it seems crazy to intentionally limit the results that way. I'm glad I spent the 30 seconds to find the code so I can hack it out :). Daniel Martin pgpM7njDiG7cE.pgp Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] first play with new XO 1.5 machines
2009/10/22 Martin Langhoff martin.langh...@gmail.com: That's my guess too. But the hard-to-answer question is how much more reliable? So we can answer is it worth the big effort? I think both the beaconing and the forwarding will have a big effect on the reliability of the network, but it still won't bring us to any degree of reliability. So, I don't think it's worth the effort. Not that we seem to have any resources to do this anyway - or are you volunteering? :) Plus for most of the time when the laptops are used in environments where they are in a position to network with others, the children are at school using infrastructure networks. IME, successful uses of under-a-tree are not using multi-hop -- at least not to any advantage. Why do you say 1-hop mesh would break significantly? For under a tree, it wouldn't. But in this scenario I feel like our only option is either mesh as we have it, or manually created ad-hoc. In every other scenario, it would fail quite badly, but I know that deployments and kids would try to use it. I think an automatically created global ad-hoc network would send the wrong message, and that conceptually it should be something that the UI communicates as a throwaway network. The other thing to note is that creating an ad-hoc network from sugar is *really* easy. Try it. You don't even have to name the network. I know that I'm usually advocating for making things require less than 1 click, but in this case I don't see a technically feasible option to do better, and the unreliable nature of the created network fits nicely with the concept of having to create it from the UI every time. One of the biggest headaches we have to deal with, even when we have infrastructure networks, is the bug where every XO has a different set of neighbours on the neighbourhood view. That is true from a user PoV, but in practice it lives higher in the stack -- Salut and Telepathy in general is where the issue lies. We still have bugs there that are hard to fix. Not in the case of networks like ad-hoc though - it will become a direct result of the network type, and nothing that can be fixed higher in the stack. Your connection to a network and your ability to see a certain neighbour will mean nothing in terms of the set of other neighbours you can see. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
tap-to-click feedback
Just wanted to communicate an experience from the deployment here: A while back, we (OLPC + community) discussed the behaviour of the new XO touchpads which have tap-to-click on by default. We debated including the fairly large software changes to be able to disable this functionality with the interest of retaining the behaviour of the old touchpad. We decided against it and shipped software with tap-to-click enabled, in hope that it wouldn't cause problems and users would adjust. Well, in my 3-4 months here in Nepal I've heard repeated cries for disabling this, since it is causing confusion for children and teachers in the schools. Really I think the biggest issue is that they press it by accident while typing or making other motions and have no idea why the screen has changed significantly (they don't understand that it's because they clicked, or that their hand was near the pad). Do other deployments share the same experience? Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] first play with new XO 1.5 machines
On Thu, Oct 22, 2009 at 11:31, Martin Dengler mar...@martindengler.com wrote: On Thu, Oct 22, 2009 at 03:36:50PM +0545, Daniel Drake wrote: One of the biggest headaches we have to deal with, even when we have infrastructure networks, is the bug where every XO has a different set of neighbours on the neighbourhood view. Now we'd be making that bug a feature. Isn't this bug/feature an explicit goal of Gadget/Sugar: 1) They'll see their friends, the result of the active searches and a maximum of $N random buddies and $N' random activities http://lists.sugarlabs.org/archive/sugar-devel/2008-June/006351.html Well, this is only when you are staring at the neighborhood level and there's more results that we can represent. Then we limit with those heuristics and a hard limit. But it's not a goal of Sugar to limit the amount of people with whom can be collaborated, it's just that we miss a list view in the neighborhood zoom level. Regards, Tomeu 2) jarabe/model/neighborhood.py line 39 40: http://cgit.sugarlabs.org/sugar/mainline/tree/src/jarabe/model/neighborhood.py#n39 ...it's used around line 130, among others: http://cgit.sugarlabs.org/sugar/mainline/tree/src/jarabe/model/neighborhood.py#n130 I've never liked that limitation, but I suspect I'm not understanding something because it seems crazy to intentionally limit the results that way. I'm glad I spent the 30 seconds to find the code so I can hack it out :). Daniel Martin -- «Sugar Labs is anyone who participates in improving and using Sugar. What Sugar Labs does is determined by the participants.» - David Farning ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] first play with new XO 1.5 machines
On Thu, Oct 22, 2009 at 12:36 PM, Daniel Drake d...@laptop.org wrote: I think both the beaconing and the forwarding will have a big effect on the reliability of the network, but it still won't bring us to any degree of reliability. In first reading, t sounds self-contradictory -- but what you are saying is that it will get significantly worse. I haven't used ad-hoc much, and the bit I did was long ago -- hence my questions. So, I don't think it's worth the effort. Not that we seem to have any resources to do this anyway - or are you volunteering? :) I have a ton on the XS side and related things. And my priority -- in as much as I can find time to hack on XO side is the XO-talks-to-XS. But I do think that we can flesh out WTH is the situation. Plus for most of the time when the laptops are used in environments where they are in a position to network with others, the children are at school using infrastructure networks. That is in the dployments where you've been :-) IME, successful uses of under-a-tree are not using multi-hop -- at least not to any advantage. Why do you say 1-hop mesh would break significantly? For under a tree, it wouldn't. But in this scenario I feel like our only option is either mesh as we have it, or manually created ad-hoc. Right -- and that is the scenario I want to ensure works well. The other thing to note is that creating an ad-hoc network from sugar is *really* easy. Try it. You don't even have to name the network. But then you have to associate from every other laptop, right? Maybe the laptops could auto-associate to ad-hoc beacons with names following a certain pattern? m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: tap-to-click feedback
I can only relate personal experience ... yes, it caught me by surprise quite a few times in the past few days. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: tap-to-click feedback
On 22.10.2009, at 14:01, James Cameron wrote: I can only relate personal experience ... yes, it caught me by surprise quite a few times in the past few days. Me too - e.g., in TamTamMini it's easy to accidentally touch the pad while hammering on the keys. - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] first play with new XO 1.5 machines
Martin Langhoff wrote: I now realize we'd forgotten about Cerebro. If anyone is going to take the hard road, it may be a viable option -- did we ever have a clear plan of what it'd take to integrate it fully (where 'fully' means that things just work at least roughly to where they do on 8.2.1). On the XO-1, the answer was reverse-engineer the Libertas firmware, recode Cerebro from scratch in C to run at the network layer, even when the CPU is off, and write a new kernel driver that can interface with it. Now that XO-1.5 can no longer forward packets in suspend, reaching parity is somewhat simpler. It still requires, at a minimum, that someone complete the abandoned Telepathy-Synapse connection-manager. In short, it's a major engineering effort involving 802.11 and Telepathy. I would love for someone to take it on, but I haven't heard any noise about it in months. signature.asc Description: OpenPGP digital signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] first play with new XO 1.5 machines
Martin Langhoff wrote: On Thu, Oct 22, 2009 at 11:51 AM, Daniel Drake d...@laptop.org wrote: 2009/10/22 Tomeu Vizoso to...@sugarlabs.org: What would be more reliable in the under a tree use case: ad-hoc or mesh with a max of 1 hop? Mesh, since everyone does their own beaconing. That's my guess too. But the hard-to-answer question is how much more reliable? So we can answer is it worth the big effort? There is only one way to find out. Both Salut (Clique and Avahi) and 802.11 ad-hoc beaconing have complex behavior in the face of unreliable connections. I do not think we are likely to be able to predict the result of their interaction. That's why OLPC has a testing team. signature.asc Description: OpenPGP digital signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: tap-to-click feedback
Daniel Drake wrote: Really I think the biggest issue is that they press it by accident while typing or making other motions and have no idea why the screen has changed significantly (they don't understand that it's because they clicked, or that their hand was near the pad). Normally, Synaptics touchpads use logic that (1) ignores large-area contact, assuming it's an accidental touch with the palm, and (2) disables the touchpad while the keyboard is active. If those measures are not in place, there will be a problem regardless of tap-to-click. I don't know where in the stack this logic lives. If that logic is already active, then it sounds like further measures are warranted. signature.asc Description: OpenPGP digital signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] XO in 2 identical SSID scenario
On Wed, Oct 21, 2009 at 6:26 PM, Andrés Nacelle anace...@plan.ceibal.edu.uy wrote: Hello pals, some time ago I did some research on the behavior from the XO in places with more than one access point with the same SSID, and the results The original thread has some rather good info. The key debugging trick was provided by Dan Williams (author of NM) http://lists.laptop.org/pipermail/devel/2009-August/025343.html Can you run the test Dan is proposing? What does the wpa_supplicant file look like? cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: tap-to-click feedback
On Thu, Oct 22, 2009 at 02:40:04PM +0200, Bert Freudenberg wrote: On 22.10.2009, at 14:01, James Cameron wrote: I can only relate personal experience ... yes, it caught me by surprise quite a few times in the past few days. Me too - e.g., in TamTamMini it's easy to accidentally touch the pad while hammering on the keys. Sorry to say me too, but, yeah. I manage to spuriously click about 5% (well, maybe that's harsh) of the time. - Bert - Martin pgpSBv3yWVxl4.pgp Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: tap-to-click feedback
benjamin m. schwartz wrote: Daniel Drake wrote: Really I think the biggest issue is that they press it by accident while typing or making other motions and have no idea why the screen has changed significantly (they don't understand that it's because they clicked, or that their hand was near the pad). Normally, Synaptics touchpads use logic that (1) ignores large-area contact, assuming it's an accidental touch with the palm, and (2) disables the touchpad while the keyboard is active. If those measures are not in place, there will be a problem regardless of tap-to-click. I don't know where in the stack this logic lives. If that logic is already active, then it sounds like further measures are warranted. i'm not sure where that lives either, but the initial key to the puzzle is that we don't currently use the synaptics kernel driver, which i believe is required for disabling tap-to-click. we tried the synaptics driver initially (when we got the new touchpads) but by itself it caused extremely erratic (perhaps not erratic, exactly, but just way-too-fast) mouse cursor behavior. at the time it seemed like we were going to need more changes further up the stack (new X driver? not sure), and since behavior was reasonable with the generic mouse driver (with the minor worry about tap-to-click), we left things as they were. so: to eliminate tap-to-click, someone needs to build a new kernel with the synaptics driver enabled (maybe just the module can be built), then they need to figure out how to make it all work well. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: tap-to-click feedback
Hi, so: to eliminate tap-to-click, someone needs to build a new kernel with the synaptics driver enabled (maybe just the module can be built), then they need to figure out how to make it all work well. I might be wrong, but I think we just need the X driver -- yum install xorg-x11-drv-synaptics. Xorg drivers are generally not layered on top of kernel drivers, outside of the case of DRI. - Chris. -- Chris Ball c...@laptop.org One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: tap-to-click feedback
2009/10/22 Chris Ball c...@laptop.org: I might be wrong, but I think we just need the X driver -- yum install xorg-x11-drv-synaptics. Xorg drivers are generally not layered on top of kernel drivers, outside of the case of DRI. Didn't work for me: http://www.mail-archive.com/devel@lists.laptop.org/msg20268.html I think Paul is right but I have not confirmed. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: tap-to-click feedback
we tried the synaptics driver initially (when we got the new touchpads) but by itself it caused extremely erratic (perhaps not erratic, exactly, but just way-too-fast) mouse cursor behavior. There seems to be something wrong with general Linux mouse behavior. Even on ordinary optical mice (like the HP I'm using now), the mouse works fine about 98% of the time; then it jumps to the top of the screen inappropriately. (Running Ubuntu Jaunty with 2.6.28-11-server kernel.) I'd noticed this with touchpads and assumed it was a buggy touchpad, but it seems to be a more generic bug somewhere in Linux. The latest Ubuntu (karmic beta) disables tap-to-click by default, which is a regression (see https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/378391 with it's more-than-a-dozen duplicates and see also #441013). It turned out that there was a lot of complicated interaction behind the scenes that would make it work, fail, work, fail, ... with different versions of various packages. John ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] XS on Netbook
On Thu, Oct 22, 2009 at 3:49 PM, Gerald Ardito gerald.ard...@gmail.com wrote: Sameer, I have tried to install the XS on a Dell Laptop (not netbook). It runs great, but the wireless indicator is not on. Could there be missing drivers? If so, what can I do? Probably uses broadcom drivers. Do lspci and check. I am not sure what is the best option, I am not sure which version of Fedora the XS is based on. Best bet is to do lspci and find out what chipset you have and see what other Fedora users have done. Dave Thanks. Gerald On Tue, Oct 20, 2009 at 1:00 AM, Sameer Verma sve...@sfsu.edu wrote: On Mon, Oct 19, 2009 at 4:35 PM, Gerald Ardito gerald.ard...@gmail.com wrote: Hello, Has anyone installed the XS on a netbook? The big issue is that there is no optical drive, but beyond that I was wondering if that would work. Thanks. Gerald ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel I have it running on a Fujitsu Lifebook P2120 (http://asia.cnet.com/reviews/notebooks/0,39050488,39009460p,00.htm), from an era when small laptops were expensive and were not called netbooks. This thing has a 933 MHz Crusoe processor, with 384 MB RAM. It doesn't complain for small set of XOs. Now that you've brought it up, I will try a netbook as well. cheers, Sameer -- Dr. Sameer Verma, Ph.D. Associate Professor, Information Systems Director, Center for Business Solutions San Francisco State University http://verma.sfsu.edu/ http://cbs.sfsu.edu/ http://is.sfsu.edu/ ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel -- Dave Bauer d...@solutiongrove.com http://www.solutiongrove.com ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: tap-to-click feedback
On Oct 22 2009, at 13:10, Chris Ball was caught saying: Hi, so: to eliminate tap-to-click, someone needs to build a new kernel with the synaptics driver enabled (maybe just the module can be built), then they need to figure out how to make it all work well. I might be wrong, but I think we just need the X driver -- yum install xorg-x11-drv-synaptics. Xorg drivers are generally not layered on top of kernel drivers, outside of the case of DRI. I recalled that I poked at this last year and there is a series of bugs I opened in trac around synaptics issues. See http://dev.laptop.org/ticket/9101. ~Deepak ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Test firmware
On Wed, Oct 21, 2009 at 4:05 PM, Rafael Enrique Ortiz Guerrero dir...@gmail.com wrote: On Tue, Oct 20, 2009 at 5:10 PM, Mitch Bradley w...@laptop.org wrote: http://dev.laptop.org/~wmb/q3a13c.rom This is a brown bag release whose main purpose is to test the effectiveness of Richard's EC fixes for the keyboard stops working problem. Did 4 reboot cycles with q3a13c and haven't seen again the keyboard problem, I'm seeing the keyboard stops working problem on my XO1.5B2, and since the keyboard doesn't work, I can hit x to get to ofw prompt to flash the new rom. Any suggestions? Sameer ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Test firmware
[ replying on-list ] sameer wrote: On Wed, Oct 21, 2009 at 4:05 PM, Rafael Enrique Ortiz Guerrero dir...@gmail.com wrote: On Tue, Oct 20, 2009 at 5:10 PM, Mitch Bradley w...@laptop.org wrote: http://dev.laptop.org/~wmb/q3a13c.rom This is a brown bag release whose main purpose is to test the effectiveness of Richard's EC fixes for the keyboard stops working problem. Did 4 reboot cycles with q3a13c and haven't seen again the keyboard problem, I'm seeing the keyboard stops working problem on my XO1.5B2, and since the keyboard doesn't work, I can hit x to get to ofw prompt to flash the new rom. Any suggestions? have you removed the battery and AC power? that should bring your keyboard back. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: F11 wired vs. jabber
Hi Mikus, On 22 Oct 2009, at 18:52, Mikus Grinbergs wrote: I don't have wireless (i.e., no AP), but use a local ethernet LAN. When I boot a F11 system, usually Neighborhood View shows me the (running) XOs connected to my ethernet. But sometimes what I see is the XOs connected to the Jabber server I have defined. To reach that Jabber server, the connection has to go over the ethernet, through a proxy (I had to tell telepathy that the proxy exists), and then over the internet. [I am leaving the Jabber server name in 'My Settings' -- I am not adding/removing it dynamically.] Which set of XOs I get to see seems to be random. [Still happens that way both on XO-1 and on XO-1.5.] Any ideas on how, with my setup, I could favor seeing jabber over seeing wired ? Not that this helps, but Salut (local network) is the fallback when Gabble (remote jabber server) fails, so if you have a jabber server set, and it intermittently shows you remote vs. loca buddiesl, then the jabber connection is intermittently failing. If a jabber server is specified Gabble attempts to connect from time to time (not sure where the actual code is but it feels like 5-10min to me). So (for whatever reason) sounds like Gabble isn't able to hold up the connection to the Jabber server, or the Jabber server you have set is flakey (FWIW: jabber.sugarlabs.org has been ropey as hell for me lately, I switched my collaboration testing to Salute some weeks back so I could have more Sugar testing control and less random remote server failures/issues). Regards, --Gary Thanks, mikus ___ Fedora-olpc-list mailing list fedora-olpc-l...@redhat.com https://www.redhat.com/mailman/listinfo/fedora-olpc-list ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: tap-to-click feedback
On Thu, Oct 22, 2009 at 10:46:30AM -0700, John Gilmore wrote: There seems to be something wrong with general Linux mouse behavior. I felt this as well on Debian in the past few months ... I couldn't fix it easily, ended up disabling the new kernel based input feature. I *think* this is all I did: xorg.conf: Section ServerFlags Option AutoAddDevices False EndSection -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] XS on Netbook
Sameer, I have tried to install the XS on a Dell Laptop (not netbook). It runs great, but the wireless indicator is not on. Could there be missing drivers? If so, what can I do? Thanks. Gerald On Tue, Oct 20, 2009 at 1:00 AM, Sameer Verma sve...@sfsu.edu wrote: On Mon, Oct 19, 2009 at 4:35 PM, Gerald Ardito gerald.ard...@gmail.com wrote: Hello, Has anyone installed the XS on a netbook? The big issue is that there is no optical drive, but beyond that I was wondering if that would work. Thanks. Gerald ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel I have it running on a Fujitsu Lifebook P2120 (http://asia.cnet.com/reviews/notebooks/0,39050488,39009460p,00.htm), from an era when small laptops were expensive and were not called netbooks. This thing has a 933 MHz Crusoe processor, with 384 MB RAM. It doesn't complain for small set of XOs. Now that you've brought it up, I will try a netbook as well. cheers, Sameer -- Dr. Sameer Verma, Ph.D. Associate Professor, Information Systems Director, Center for Business Solutions San Francisco State University http://verma.sfsu.edu/ http://cbs.sfsu.edu/ http://is.sfsu.edu/ ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] Nepal XS customizations
Here are the customizations we're making on top of XS-0.6 here in Nepal. This version will start being distributed to the field on Monday. Kickstart file modifications: - no GUI, just use text mode - auto reboot at the end of installation - no interactivity during installation - timezone and root password hardcoded - packages added: dansguardian, dependencies for nepal's E-library system (www.pustakalaya.org) e.g. mysql, some php modules, ImageMagick, java - added a nepal-specific nexs-custom customization package, and a script from that package to run on firstboot (details below) - nepal-specific XS build number written to /etc/motd and /etc/issue Build scripts including the customization file can be found at http://hg.olenepal.org/NEXS-image-builder/ The customizations from nexs-custom: - udev rules to make sure that onboard LAN is eth1, and USB ethernet adapter (for WAN) is eth0 - apache configs to set up aliases for our various content components and E-library - mysql config file to enable storage in /library and 1-file-per-table innodb setting - a script to simplify eth0 configuration - a self test system (details below) - various usbmount scripts to enable automatic content installation from USB The firstboot script from nexs-custom: - configure and enable dansguardian - setup admin user account, with a predetermined SSH public key and password - configure and enable mysql - enable moodle admin account and set a predetermined password - beep and print some instructions to the screen Notes on self test: - 32 tests performed, to check that: hostname has been set, both ethernet interfaces present, all the regular XS services running, Nepal content has been installed - it runs on every boot, logging the test results and info into /var/log (max 500 logs kept) - it can also be run from a usbmount script which is triggered by a file named nexs-run-self-test on the USB disk. In this mode it will use aural beep codes to indicate test success and failure, in addition to logging the test results and info back to the USB disk. nexs-custom code is found at http://hg.olenepal.org/NEXS_scripts/ The content that we add: - Fedora Commons (www.fedora.info) and Fez frontend, and huge content collection -- a clone of pustakalaya.org - a clone of http://en.wiktionary.org - an English definition dictionary - a clone of www.nepalisabdakos.com - a Nepali definition dictionary - wikipedia for schools (http://schools-wikipedia.org/) - latest full version of OLE Nepal's huge educational content activity, including the whole years worth of lessons (this is also present on the XOs but only for a certain time period at a time -- the overall activity is split into 6 different XO activities which are distributed at different times through the year, the full version is too big to store on XO) - some world maps, an atlas, and educational videos some scripts we use for supporting the above content installation can be found at http://hg.olenepal.org/NEXC-maint/ Daniel ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
