Re: [support-gang] A XO-1 BUA ("keyboard") replaced with a XO-1.75 BUA
Hey, This sounds great. I have a couple of XO-1s that could well do with this upgrade. Is it possible for the general public to buy the XO-1.75 BUA? Or even a XO-4 BUA if it's compatible. Cheers, Andrew On Tue, 2016-01-12 at 21:07 -0500, Adam Holt wrote: > Thanks Nathan! Am circulating to devel@laptop so we get more > thoughts- > On Jan 12, 2016 8:32 PM, wrote: > > > > A XO-1 BUA (Base Upper Assembly -- "keyboard" [ http://flickr.com/ > curiouslee/5932732888 http://flickr.com/curiouslee/5932732736 ] ) > replaced with a XO-1.75 BUA and no mechanical or software issues were > observed, (13.2.6 SD). No modification needed. > > If someone can confirm that XO-4 BUA is same as for XO-1.75 BUA, > then the BUA from any XO model can be used on the XO-1. > > > > Previously posted here by others that lower half of any XO model > could be used on the XO-1. > > > > I had been unable to obtain any answer as to the ongoing BUA > compatibility question, so made the test with the first XO-1.75 that > I got my hands on. :) > > > > Nathan Riddle > [There are hundreds of XO's out there than that are being refurb'd, > in Boston/Michigan/Nicaragua/Haiti especially, but we're only just > getting started: Nancie Severs & Paul Fox helped tremendously in > November!!] > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel -- Andrew Ruthven, Wellington, New Zealand MIITP, CITPNZ At work: andrew.ruth...@catalyst.net.nz At home: and...@etc.gen.nz Card : http://qr.catalyst.net.nz/907675e1 Cloud : NZs only real cloud - https://catalyst.net.nz/cloud GPG fpr: C603 FC4E 600F 1CEC D1C8 D97C 4B53 D931 E4D3 E863 LCA2016: LCA By the Bay, Geelong, AU - lca2016.linux.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] A XO-1 BUA ("keyboard") replaced with a XO-1.75 BUA
Thanks Nathan! Am circulating to devel@laptop so we get more thoughts- On Jan 12, 2016 8:32 PM, wrote: > > A XO-1 BUA (Base Upper Assembly -- "keyboard" [ http://flickr.com/curiouslee/5932732888 http://flickr.com/curiouslee/5932732736 ] ) replaced with a XO-1.75 BUA and no mechanical or software issues were observed, (13.2.6 SD). No modification needed. > If someone can confirm that XO-4 BUA is same as for XO-1.75 BUA, then the BUA from any XO model can be used on the XO-1. > > Previously posted here by others that lower half of any XO model could be used on the XO-1. > > I had been unable to obtain any answer as to the ongoing BUA compatibility question, so made the test with the first XO-1.75 that I got my hands on. :) > > Nathan Riddle [There are hundreds of XO's out there than that are being refurb'd, in Boston/Michigan/Nicaragua/Haiti especially, but we're only just getting started: Nancie Severs & Paul Fox helped tremendously in November!!] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] intermittent keyboard mismapping: 13.2.5 on XO-1 SKU39
G'day Caryl, If you're asking with respect to the discussion thread, go ahead with the latest 13.2.5, because the problem Adam is talking about won't affect you or the women and children, it is very minor. Otherwise, 13.2.5 is still the best for XO-1 because it can start every activity at once if necessary, and has all the latest updates. http://wiki.laptop.org/go/Release_notes/13.2.5/Installation/XO-1 On Tue, Aug 04, 2015 at 10:07:23AM -0600, Caryl Bigenho wrote: > Hi… > > So… the XO-1s at the project we have at a school at a women's shelter in > central Los Angeles will be updated in the next couple of weeks, getting ready > for September school start. What would be the safest build for them to use? I > won't be there to help, but it is in good hands with one of our SoCal > volunteers. I just want to make it easy for everything to go smoothly. > > Thanks, > Carul > > ━━━ > Date: Tue, 4 Aug 2015 09:28:23 -0400 > From: h...@laptop.org > To: support-g...@lists.laptop.org; de...@laptop.org > Subject: Re: [support-gang] intermittent keyboard mismapping: 13.2.5 on XO-1 > SKU39 > > Just an update that I've narrowed in on the/a pattern which triggers the > problem, with the help of James Cameron, and some workarounds: > > • Tapping the ESC key very rapidly during bootup causes the keyboard > mismapping (and hence, failure to enter Open Firmware). > • Holding down the ESC key during bootup (generally, but not always) avoids > the problem (entering Open Firmware). > • Typing no keys at all during initial bootup, appears (I hope) to be a > workaround to boot the OS properly, with keyboard functioning properly. > > Better yet, earlier firmware (e.g. q2e41 in this case) does not appear to show > the problem at all, so newer firmware may be available in future to solve this > annoying-but-less-serious-that-I-imagined problem. For all using SKU39 XO-1s > (or perhaps other/similar XO laptops having the modern touchpad?) > > On Mon, Aug 3, 2015 at 7:03 PM, Adam Holt <[1]h...@laptop.org> wrote: > > I haven't figured out the pattern yet, but perhaps 50% of the time these > XO-1s boot with an unusable keyboard (it's a "US Intl" keyboard, but the > keys end up mapped to all the wrong places, showing the wrong letters/ > numbers, such that not even the ESC key works to get to the Ok prompt). > > This pattern arises with "vanilla" 13.2.5 (without SD cards) as well as > 13.2.5 with SD cards. In other words both of these: > >[2]http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 >[3]http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card > > Running the "bye" command at the Ok prompt seems to trigger the problem > almost every time (possibly every time?). But that is not the only thing > that triggers the problem. Sometimes the XO just boots with unusable > keyboard, repeatedly. Then when I try to hit ESC on boot 20 times in a > row, I cannot reproduce the problem at other times. Problem occurs on all > SKU39 XO-1s I've tried so far. > > I've not yet tried other SKU's. My testing has only just begun, to see if > this same problem occurs with (both) 13.2.4 OS's and earlier. > > Any tips for debugging / identifying the source of this quite serious > gremlin? What should I and my small team of debugging volunteers look out > for and try? And I'll do more work on this when I get back home late > tonight, but all thoughts appreciated- > > (Also, any recommendations as to which older builds are best, as an > interim > workaround?) > > -- > Unsung Heroes of OLPC, interviewed live @ [4]http://unleashkids.org ! > > ___ support-gang mailing list > support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang > > References: > > [1] mailto:h...@laptop.org > [2] http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 > [3] http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card > [4] http://unleashkids.org/ > ___ > support-gang mailing list > support-g...@lists.laptop.org > http://lists.laptop.org/listinfo/support-gang -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] intermittent keyboard mismapping: 13.2.5 on XO-1 SKU39
Yes, it almost never happens for a child, has been known since 2011, is specific to the single panel touchpad assembly on XO-1, and is solved by following (to the letter) our community documentation: http://wiki.laptop.org/go/Ok ... instead of historic practices that were learned on the three panel touchpad assembly. ;-) On Tue, Aug 04, 2015 at 09:28:23AM -0400, Adam Holt wrote: > Just an update that I've narrowed in on the/a pattern which triggers the > problem, with the help of James Cameron, and some workarounds: > > • Tapping the ESC key very rapidly during bootup causes the keyboard > mismapping (and hence, failure to enter Open Firmware). > • Holding down the ESC key during bootup (generally, but not always) avoids > the problem (entering Open Firmware). > • Typing no keys at all during initial bootup, appears (I hope) to be a > workaround to boot the OS properly, with keyboard functioning properly. > > Better yet, earlier firmware (e.g. q2e41 in this case) does not appear to show > the problem at all, so newer firmware may be available in future to solve this > annoying-but-less-serious-that-I-imagined problem. For all using SKU39 XO-1s > (or perhaps other/similar XO laptops having the modern touchpad?) > > On Mon, Aug 3, 2015 at 7:03 PM, Adam Holt <[1]h...@laptop.org> wrote: > > I haven't figured out the pattern yet, but perhaps 50% of the time these > XO-1s boot with an unusable keyboard (it's a "US Intl" keyboard, but the > keys end up mapped to all the wrong places, showing the wrong letters/ > numbers, such that not even the ESC key works to get to the Ok prompt). > > This pattern arises with "vanilla" 13.2.5 (without SD cards) as well as > 13.2.5 with SD cards. In other words both of these: > > [2]http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 > [3]http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card > > Running the "bye" command at the Ok prompt seems to trigger the problem > almost every time (possibly every time?). But that is not the only thing > that triggers the problem. Sometimes the XO just boots with unusable > keyboard, repeatedly. Then when I try to hit ESC on boot 20 times in a > row, I cannot reproduce the problem at other times. Problem occurs on all > SKU39 XO-1s I've tried so far. > > I've not yet tried other SKU's. My testing has only just begun, to see if > this same problem occurs with (both) 13.2.4 OS's and earlier. > > Any tips for debugging / identifying the source of this quite serious > gremlin? What should I and my small team of debugging volunteers look out > for and try? And I'll do more work on this when I get back home late > tonight, but all thoughts appreciated- > > (Also, any recommendations as to which older builds are best, as an > interim > workaround?) > > -- > Unsung Heroes of OLPC, interviewed live @ [4]http://unleashkids.org ! > > References: > > [1] mailto:h...@laptop.org > [2] http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 > [3] http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card > [4] http://unleashkids.org/ > ___ > support-gang mailing list > support-g...@lists.laptop.org > http://lists.laptop.org/listinfo/support-gang -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] intermittent keyboard mismapping: 13.2.5 on XO-1 SKU39
Yes, it almost never happens for a child, has been known since 2011, is specific to the single panel touchpad assembly on XO-1, and is solved by following (to the letter) our community documentation: http://wiki.laptop.org/go/Ok ... instead of historic practices that were learned on the three panel touchpad assembly. ;-) On Tue, Aug 04, 2015 at 09:28:23AM -0400, Adam Holt wrote: > Just an update that I've narrowed in on the/a pattern which triggers the > problem, with the help of James Cameron, and some workarounds: > > • Tapping the ESC key very rapidly during bootup causes the keyboard > mismapping (and hence, failure to enter Open Firmware). > • Holding down the ESC key during bootup (generally, but not always) avoids > the problem (entering Open Firmware). > • Typing no keys at all during initial bootup, appears (I hope) to be a > workaround to boot the OS properly, with keyboard functioning properly. > > Better yet, earlier firmware (e.g. q2e41 in this case) does not appear to show > the problem at all, so newer firmware may be available in future to solve this > annoying-but-less-serious-that-I-imagined problem. For all using SKU39 XO-1s > (or perhaps other/similar XO laptops having the modern touchpad?) > > On Mon, Aug 3, 2015 at 7:03 PM, Adam Holt <[1]h...@laptop.org> wrote: > > I haven't figured out the pattern yet, but perhaps 50% of the time these > XO-1s boot with an unusable keyboard (it's a "US Intl" keyboard, but the > keys end up mapped to all the wrong places, showing the wrong letters/ > numbers, such that not even the ESC key works to get to the Ok prompt). > > This pattern arises with "vanilla" 13.2.5 (without SD cards) as well as > 13.2.5 with SD cards. In other words both of these: > > [2]http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 > [3]http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card > > Running the "bye" command at the Ok prompt seems to trigger the problem > almost every time (possibly every time?). But that is not the only thing > that triggers the problem. Sometimes the XO just boots with unusable > keyboard, repeatedly. Then when I try to hit ESC on boot 20 times in a > row, I cannot reproduce the problem at other times. Problem occurs on all > SKU39 XO-1s I've tried so far. > > I've not yet tried other SKU's. My testing has only just begun, to see if > this same problem occurs with (both) 13.2.4 OS's and earlier. > > Any tips for debugging / identifying the source of this quite serious > gremlin? What should I and my small team of debugging volunteers look out > for and try? And I'll do more work on this when I get back home late > tonight, but all thoughts appreciated- > > (Also, any recommendations as to which older builds are best, as an > interim > workaround?) > > -- > Unsung Heroes of OLPC, interviewed live @ [4]http://unleashkids.org ! > > References: > > [1] mailto:h...@laptop.org > [2] http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 > [3] http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card > [4] http://unleashkids.org/ > ___ > support-gang mailing list > support-g...@lists.laptop.org > http://lists.laptop.org/listinfo/support-gang -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] intermittent keyboard mismapping: 13.2.5 on XO-1 SKU39
G'day Caryl, If you're asking with respect to the discussion thread, go ahead with the latest 13.2.5, because the problem Adam is talking about won't affect you or the women and children, it is very minor. Otherwise, 13.2.5 is still the best for XO-1 because it can start every activity at once if necessary, and has all the latest updates. http://wiki.laptop.org/go/Release_notes/13.2.5/Installation/XO-1 On Tue, Aug 04, 2015 at 10:07:23AM -0600, Caryl Bigenho wrote: > Hi… > > So… the XO-1s at the project we have at a school at a women's shelter in > central Los Angeles will be updated in the next couple of weeks, getting ready > for September school start. What would be the safest build for them to use? I > won't be there to help, but it is in good hands with one of our SoCal > volunteers. I just want to make it easy for everything to go smoothly. > > Thanks, > Carul > > ━━━ > Date: Tue, 4 Aug 2015 09:28:23 -0400 > From: h...@laptop.org > To: support-g...@lists.laptop.org; de...@laptop.org > Subject: Re: [support-gang] intermittent keyboard mismapping: 13.2.5 on XO-1 > SKU39 > > Just an update that I've narrowed in on the/a pattern which triggers the > problem, with the help of James Cameron, and some workarounds: > > • Tapping the ESC key very rapidly during bootup causes the keyboard > mismapping (and hence, failure to enter Open Firmware). > • Holding down the ESC key during bootup (generally, but not always) avoids > the problem (entering Open Firmware). > • Typing no keys at all during initial bootup, appears (I hope) to be a > workaround to boot the OS properly, with keyboard functioning properly. > > Better yet, earlier firmware (e.g. q2e41 in this case) does not appear to show > the problem at all, so newer firmware may be available in future to solve this > annoying-but-less-serious-that-I-imagined problem. For all using SKU39 XO-1s > (or perhaps other/similar XO laptops having the modern touchpad?) > > On Mon, Aug 3, 2015 at 7:03 PM, Adam Holt <[1]h...@laptop.org> wrote: > > I haven't figured out the pattern yet, but perhaps 50% of the time these > XO-1s boot with an unusable keyboard (it's a "US Intl" keyboard, but the > keys end up mapped to all the wrong places, showing the wrong letters/ > numbers, such that not even the ESC key works to get to the Ok prompt). > > This pattern arises with "vanilla" 13.2.5 (without SD cards) as well as > 13.2.5 with SD cards. In other words both of these: > >[2]http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 >[3]http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card > > Running the "bye" command at the Ok prompt seems to trigger the problem > almost every time (possibly every time?). But that is not the only thing > that triggers the problem. Sometimes the XO just boots with unusable > keyboard, repeatedly. Then when I try to hit ESC on boot 20 times in a > row, I cannot reproduce the problem at other times. Problem occurs on all > SKU39 XO-1s I've tried so far. > > I've not yet tried other SKU's. My testing has only just begun, to see if > this same problem occurs with (both) 13.2.4 OS's and earlier. > > Any tips for debugging / identifying the source of this quite serious > gremlin? What should I and my small team of debugging volunteers look out > for and try? And I'll do more work on this when I get back home late > tonight, but all thoughts appreciated- > > (Also, any recommendations as to which older builds are best, as an > interim > workaround?) > > -- > Unsung Heroes of OLPC, interviewed live @ [4]http://unleashkids.org ! > > ___ support-gang mailing list > support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang > > References: > > [1] mailto:h...@laptop.org > [2] http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 > [3] http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card > [4] http://unleashkids.org/ > ___ > support-gang mailing list > support-g...@lists.laptop.org > http://lists.laptop.org/listinfo/support-gang -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: intermittent keyboard mismapping: 13.2.5 on XO-1 SKU39
Summary: while both 13.2.5 OS's for XO-1 SKU39 (and possibly similar SKU's) have a couple keyboard/mouse issues, arising from q2f20's EC firmware it seems -- the workaround to both issues appears very simple -- simply do not to touch the keyboard during these 2 critical moments: - during the first few seconds after powering on (hit/hold ESC key _after_ the XO kid appears in the center of your screen, if seeking the ok prompt on an unlocked XO) - when the XO is sleeping Yes there's now also a bulletproof workaround to the 1st issue (keyboard mismapping if ESC is tapped too early during bootup) if you downgrade firmware from q2f20 to http://dev.laptop.org/~quozl/q2f20ed.rom which includes EC Firmware E35, dated 2010-08-23. Wonderful that James Cameron isolated the problem. But this fix might not be worth the trouble, as keyboard+mouse variously go haywire after sleep/wake -- up particularly if you touch the keyboard while XO's sleeping -- regardless which of these 2 firmwares. Regardless, folks need to retrain (refrain) themselves on when to hit ESC on bootup: http://wiki.laptop.org/go/Ok#Unsecured Conclusion: I'm not educated enough to know whether q2f20 or q2f20ed is best for one deployment or another. Sticking with 13.2.5's stock firmware q2f20 (including EC Firmware 1.2.1) might well be easiest for many, certainly for now, sure the above 2 workarounds to require training, but both appear 100% effective so far. Or if you do choose to downgrade to q2f20ed, note the 4 small accompanying regressions/risks below, and judge for yourself: - you lose a fix for mouse activity at shutdown preventing reboot without keyboard, - you lose a fix for battery EEPROM corruption, which happens if you are holding the power button down and insert the battery, - you lose the AP (Auto Power) and CP (Constant Power) features for use as a server, and; - you lose RTC anti-rollback support, which you shouldn't be using anyway. Most important, let's all be very helpful James Cameron carefully explained the above tradeoff- whether XO-1 live forever or not as we shall see :-) On Tue, Aug 4, 2015 at 9:28 AM, Adam Holt wrote: > Just an update that I've narrowed in on the/a pattern which triggers the > problem, with the help of James Cameron, and some workarounds: > > - Tapping the ESC key very rapidly during bootup causes the keyboard >mismapping (and hence, failure to enter Open Firmware). >- Holding down the ESC key during bootup (generally, but not always) >avoids the problem (entering Open Firmware). >- Typing no keys at all during initial bootup, appears (I hope) to be >a workaround to boot the OS properly, with keyboard functioning properly. > > Better yet, earlier firmware (e.g. q2e41 in this case) does not appear to > show the problem at all, so newer firmware may be available in future to > solve this annoying-but-less-serious-that-I-imagined problem. For all > using SKU39 XO-1s (or perhaps other/similar XO laptops having the modern > touchpad?) > > On Mon, Aug 3, 2015 at 7:03 PM, Adam Holt wrote: > >> I haven't figured out the pattern yet, but perhaps 50% of the time these >> XO-1s boot with an unusable keyboard (it's a "US Intl" keyboard, but the >> keys end up mapped to all the wrong places, showing the wrong >> letters/numbers, such that not even the ESC key works to get to the Ok >> prompt). >> >> This pattern arises with "vanilla" 13.2.5 (without SD cards) as well as >> 13.2.5 with SD cards. In other words both of these: >> >>http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 >>http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card >> >> Running the "bye" command at the Ok prompt seems to trigger the problem >> almost every time (possibly every time?). But that is not the only thing >> that triggers the problem. Sometimes the XO just boots with unusable >> keyboard, repeatedly. Then when I try to hit ESC on boot 20 times in a >> row, I cannot reproduce the problem at other times. Problem occurs on all >> SKU39 XO-1s I've tried so far. >> >> I've not yet tried other SKU's. My testing has only just begun, to see >> if this same problem occurs with (both) 13.2.4 OS's and earlier. >> >> Any tips for debugging / identifying the source of this quite serious >> gremlin? What should I and my small team of debugging volunteers look out >> for and try? And I'll do more work on this when I get back home late >> tonight, but all thoughts appreciated- >> >> (Also, any recommendations as to which older builds are best, as an >> interim workaround?) >> >> -- >> Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! >> > -- Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Fwd: Re: [support-gang] intermittent keyboard mismapping: 13.2.5 on XO-1 SKU39
-- Forwarded message -- From: "James Cameron" Date: Aug 4, 2015 7:39 PM Subject: Re: [support-gang] intermittent keyboard mismapping: 13.2.5 on XO-1 SKU39 To: "Gonzalo Odiard" Cc: "Community Support Volunteers -- who help respond to help AT laptop.org" , "Danny Hembree" < danny-hemb...@dynamical.org>, "gl...@goodshepherdshelter.org" < gl...@goodshepherdshelter.org>, "Devel's in the Details" G'day Gonzalo, Thanks for the reminder. Yes, it matches somewhat with #11223 and #11468, especially the mapping of the keys that Adam observes. https://dev.laptop.org/ticket/11223 https://dev.laptop.org/ticket/11468 No fix is possible at the moment, but changing procedure works fine. p.s. my posts are not getting through to devel@ or support-gang@ due to the DNS damage affecting laptop.org. On Tue, Aug 04, 2015 at 03:17:02PM -0300, Gonzalo Odiard wrote: > I don't think the error reported by Alan is related with the last (or latest) > builds at all. > This is related to a very old bug, I was looking but couldn't find the ticket. > > Gonzalo > > On Tue, Aug 4, 2015 at 1:07 PM, Caryl Bigenho <[1]cbige...@hotmail.com> wrote: > > Hi… > > So… the XO-1s at the project we have at a school at a women's shelter in > central Los Angeles will be updated in the next couple of weeks, getting > ready for September school start. What would be the safest build for them > to use? I won't be there to help, but it is in good hands with one of our > SoCal volunteers. I just want to make it easy for everything to go > smoothly. > > Thanks, > Carul > > ━━━ > Date: Tue, 4 Aug 2015 09:28:23 -0400 > From: [2]h...@laptop.org > To: [3]support-g...@lists.laptop.org; [4]de...@laptop.org > Subject: Re: [support-gang] intermittent keyboard mismapping: 13.2.5 on > XO-1 SKU39 > > Just an update that I've narrowed in on the/a pattern which triggers the > problem, with the help of James Cameron, and some workarounds: > □ Tapping the ESC key very rapidly during bootup causes the keyboard > mismapping (and hence, failure to enter Open Firmware). > □ Holding down the ESC key during bootup (generally, but not always) > avoids the problem (entering Open Firmware). > □ Typing no keys at all during initial bootup, appears (I hope) to be a > workaround to boot the OS properly, with keyboard functioning properly. > Better yet, earlier firmware (e.g. q2e41 in this case) does not appear to > show the problem at all, so newer firmware may be available in future to > solve this annoying-but-less-serious-that-I-imagined problem. For all > using SKU39 XO-1s (or perhaps other/similar XO laptops having the modern > touchpad?) > > On Mon, Aug 3, 2015 at 7:03 PM, Adam Holt <[5]h...@laptop.org> wrote: > > I haven't figured out the pattern yet, but perhaps 50% of the time > these XO-1s boot with an unusable keyboard (it's a "US Intl" keyboard, > but the keys end up mapped to all the wrong places, showing the wrong > letters/numbers, such that not even the ESC key works to get to the Ok > prompt). > > This pattern arises with "vanilla" 13.2.5 (without SD cards) as well as > 13.2.5 with SD cards. In other words both of these: > >[6]http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 >[7] http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card > > Running the "bye" command at the Ok prompt seems to trigger the problem > almost every time (possibly every time?). But that is not the only > thing that triggers the problem. Sometimes the XO just boots with > unusable keyboard, repeatedly. Then when I try to hit ESC on boot 20 > times in a row, I cannot reproduce the problem at other times. Problem > occurs on all SKU39 XO-1s I've tried so far. > > I've not yet tried other SKU's. My testing has only just begun, to see > if this same problem occurs with (both) 13.2.4 OS's and earlier. > > Any tips for debugging / identifying the source of this quite serious > gremlin? What should I and my small team of debugging volunteers look > out for and try? And I'll do more work on this when I get back home > late tonight, but all thoughts appreciated- > > (Also, any recommendations as to which older builds are best, as an > interim workaround?) > >
Re: [support-gang] intermittent keyboard mismapping: 13.2.5 on XO-1 SKU39
I don't think the error reported by Alan is related with the last (or latest) builds at all. This is related to a very old bug, I was looking but couldn't find the ticket. Gonzalo On Tue, Aug 4, 2015 at 1:07 PM, Caryl Bigenho wrote: > Hi… > > So… the XO-1s at the project we have at a school at a women's shelter in > central Los Angeles will be updated in the next couple of weeks, getting > ready for September school start. What would be the safest build for them > to use? I won't be there to help, but it is in good hands with one of our > SoCal volunteers. I just want to make it easy for everything to go smoothly. > > Thanks, > Carul > > -- > Date: Tue, 4 Aug 2015 09:28:23 -0400 > From: h...@laptop.org > To: support-g...@lists.laptop.org; de...@laptop.org > Subject: Re: [support-gang] intermittent keyboard mismapping: 13.2.5 on > XO-1 SKU39 > > > Just an update that I've narrowed in on the/a pattern which triggers the > problem, with the help of James Cameron, and some workarounds: > >- Tapping the ESC key very rapidly during bootup causes the keyboard >mismapping (and hence, failure to enter Open Firmware). >- Holding down the ESC key during bootup (generally, but not always) >avoids the problem (entering Open Firmware). >- Typing no keys at all during initial bootup, appears (I hope) to be >a workaround to boot the OS properly, with keyboard functioning properly. > > Better yet, earlier firmware (e.g. q2e41 in this case) does not appear to > show the problem at all, so newer firmware may be available in future to > solve this annoying-but-less-serious-that-I-imagined problem. For all > using SKU39 XO-1s (or perhaps other/similar XO laptops having the modern > touchpad?) > > On Mon, Aug 3, 2015 at 7:03 PM, Adam Holt wrote: > > I haven't figured out the pattern yet, but perhaps 50% of the time these > XO-1s boot with an unusable keyboard (it's a "US Intl" keyboard, but the > keys end up mapped to all the wrong places, showing the wrong > letters/numbers, such that not even the ESC key works to get to the Ok > prompt). > > This pattern arises with "vanilla" 13.2.5 (without SD cards) as well as > 13.2.5 with SD cards. In other words both of these: > >http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 >http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card > > Running the "bye" command at the Ok prompt seems to trigger the problem > almost every time (possibly every time?). But that is not the only thing > that triggers the problem. Sometimes the XO just boots with unusable > keyboard, repeatedly. Then when I try to hit ESC on boot 20 times in a > row, I cannot reproduce the problem at other times. Problem occurs on all > SKU39 XO-1s I've tried so far. > > I've not yet tried other SKU's. My testing has only just begun, to see if > this same problem occurs with (both) 13.2.4 OS's and earlier. > > Any tips for debugging / identifying the source of this quite serious > gremlin? What should I and my small team of debugging volunteers look out > for and try? And I'll do more work on this when I get back home late > tonight, but all thoughts appreciated- > > (Also, any recommendations as to which older builds are best, as an > interim workaround?) > > -- > Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! > > > ___ support-gang mailing list > support-g...@lists.laptop.org > http://lists.laptop.org/listinfo/support-gang > > ___ > support-gang mailing list > support-g...@lists.laptop.org > http://lists.laptop.org/listinfo/support-gang > > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: intermittent keyboard mismapping: 13.2.5 on XO-1 SKU39
Just an update that I've narrowed in on the/a pattern which triggers the problem, with the help of James Cameron, and some workarounds: - Tapping the ESC key very rapidly during bootup causes the keyboard mismapping (and hence, failure to enter Open Firmware). - Holding down the ESC key during bootup (generally, but not always) avoids the problem (entering Open Firmware). - Typing no keys at all during initial bootup, appears (I hope) to be a workaround to boot the OS properly, with keyboard functioning properly. Better yet, earlier firmware (e.g. q2e41 in this case) does not appear to show the problem at all, so newer firmware may be available in future to solve this annoying-but-less-serious-that-I-imagined problem. For all using SKU39 XO-1s (or perhaps other/similar XO laptops having the modern touchpad?) On Mon, Aug 3, 2015 at 7:03 PM, Adam Holt wrote: > I haven't figured out the pattern yet, but perhaps 50% of the time these > XO-1s boot with an unusable keyboard (it's a "US Intl" keyboard, but the > keys end up mapped to all the wrong places, showing the wrong > letters/numbers, such that not even the ESC key works to get to the Ok > prompt). > > This pattern arises with "vanilla" 13.2.5 (without SD cards) as well as > 13.2.5 with SD cards. In other words both of these: > >http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 >http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card > > Running the "bye" command at the Ok prompt seems to trigger the problem > almost every time (possibly every time?). But that is not the only thing > that triggers the problem. Sometimes the XO just boots with unusable > keyboard, repeatedly. Then when I try to hit ESC on boot 20 times in a > row, I cannot reproduce the problem at other times. Problem occurs on all > SKU39 XO-1s I've tried so far. > > I've not yet tried other SKU's. My testing has only just begun, to see if > this same problem occurs with (both) 13.2.4 OS's and earlier. > > Any tips for debugging / identifying the source of this quite serious > gremlin? What should I and my small team of debugging volunteers look out > for and try? And I'll do more work on this when I get back home late > tonight, but all thoughts appreciated- > > (Also, any recommendations as to which older builds are best, as an > interim workaround?) > > -- > Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
intermittent keyboard mismapping: 13.2.5 on XO-1 SKU39
I haven't figured out the pattern yet, but perhaps 50% of the time these XO-1s boot with an unusable keyboard (it's a "US Intl" keyboard, but the keys end up mapped to all the wrong places, showing the wrong letters/numbers, such that not even the ESC key works to get to the Ok prompt). This pattern arises with "vanilla" 13.2.5 (without SD cards) as well as 13.2.5 with SD cards. In other words both of these: http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1 http://wiki.laptop.org/go/Release_notes/13.2.5#XO-1_with_SD_card Running the "bye" command at the Ok prompt seems to trigger the problem almost every time (possibly every time?). But that is not the only thing that triggers the problem. Sometimes the XO just boots with unusable keyboard, repeatedly. Then when I try to hit ESC on boot 20 times in a row, I cannot reproduce the problem at other times. Problem occurs on all SKU39 XO-1s I've tried so far. I've not yet tried other SKU's. My testing has only just begun, to see if this same problem occurs with (both) 13.2.4 OS's and earlier. Any tips for debugging / identifying the source of this quite serious gremlin? What should I and my small team of debugging volunteers look out for and try? And I'll do more work on this when I get back home late tonight, but all thoughts appreciated- (Also, any recommendations as to which older builds are best, as an interim workaround?) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Fwd: French keyboard map for XO-4 non-membrane keyboard
Hi all, Just a follow up on the "how to do a XO-4 non-membrane French keyboard". I've finally designed the French non-membrane keyboard. The SVG file is visible here [1]. Here [2] is the matching xmodmap file. Then, I'm doing a xmodmap call in the .xsession file to launch it a startup. xmodmap /etc/X11/french.xmodmap The new .xsession file is here [3]. Finally, here [4] is the script to launch on each XO-4 to update it. We plan to use it in our Saint-Ouen deployment at the north of Paris. Hope it could help. Lionel. [1] http://olpc-france.org/download/keyboard_french.svg [2] http://olpc-france.org/download/french.xmodmap [3] http://olpc-france.org/download/xbd.xbd [4] http://olpc-france.org/download/dokbfrupdate.sh ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
Well at least we know the reasons. Need to stay plugged in for the 2 older models for the time being! >-Original Message- >From: James Cameron [mailto:qu...@laptop.org] >Sent: Tuesday, September 23, 2014 11:47 AM >To: tkk...@nurturingasia.com >Cc: devel@lists.laptop.org >Subject: Re: Logitech USB wireless keyboard with trackpad on XO-1.75 > >Thanks. > >I've compared XO-1.75 and XO-1.5 kernel configurations. > >The device you are testing with (ID 046d:c52b) is not supported by >OLPC OS 13.2.1 on XO-1 and XO-1.5. > >To add support in a deployment, a kernel from our x86-3.3 branch may >be built with the configuration options: > > CONFIG_HID_LOGITECH_DJ > CONFIG_HID_LOGITECH > >There are other kernel configuration options that may be important. > >The configuration notes associated with these options in the kernel >sources say the device you are using is not fully compliant with HID >standard: > > > http://dev.laptop.org/git/olpc-kernel/tree/drivers/hid/Kconfig?h=x86-3.3#n246 > >Technical instructions for developers to rebuild the kernel for the >OLPC XO laptop can be found here: > > http://wiki.laptop.org/go/Kernel_Building > >OLPC does not plan to add support for this device on XO-1 or XO-1.5. > >-- >James Cameron >http://quozl.linux.org.au/ > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
Thanks. I've compared XO-1.75 and XO-1.5 kernel configurations. The device you are testing with (ID 046d:c52b) is not supported by OLPC OS 13.2.1 on XO-1 and XO-1.5. To add support in a deployment, a kernel from our x86-3.3 branch may be built with the configuration options: CONFIG_HID_LOGITECH_DJ CONFIG_HID_LOGITECH There are other kernel configuration options that may be important. The configuration notes associated with these options in the kernel sources say the device you are using is not fully compliant with HID standard: http://dev.laptop.org/git/olpc-kernel/tree/drivers/hid/Kconfig?h=x86-3.3#n246 Technical instructions for developers to rebuild the kernel for the OLPC XO laptop can be found here: http://wiki.laptop.org/go/Kernel_Building OLPC does not plan to add support for this device on XO-1 or XO-1.5. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
Yes I can confirm that with my current testing. Cheers >-Original Message- >From: James Cameron [mailto:qu...@laptop.org] >Sent: Tuesday, September 23, 2014 10:56 AM >To: tkk...@nurturingasia.com >Cc: devel@lists.laptop.org >Subject: Re: Logitech USB wireless keyboard with trackpad on XO-1.75 > >On Mon, Sep 22, 2014 at 02:11:45AM +, tkk...@nurturingasia.com wrote: >> Sorry for messing up the OS version. >> >> I didn't see the Logitec wireless device listed in the list of event when I >> type sudo evtest. >> >> >> lsusb output: >> http://pastebin.com/ks936UGE >> >> dmesg output: >> http://pastebin.com/c3MRPTSn > >Please confirm; it works with XO-1.75 on 13.2.1, but not XO-1 or >XO-1.5? If so, possibly kernel configuration options are the cause. > >Nothing else springs to mind as to cause. > >-- >James Cameron >http://quozl.linux.org.au/ > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
On Mon, Sep 22, 2014 at 02:11:45AM +, tkk...@nurturingasia.com wrote: > Sorry for messing up the OS version. > > I didn't see the Logitec wireless device listed in the list of event when I > type sudo evtest. > > > lsusb output: > http://pastebin.com/ks936UGE > > dmesg output: > http://pastebin.com/c3MRPTSn Please confirm; it works with XO-1.75 on 13.2.1, but not XO-1 or XO-1.5? If so, possibly kernel configuration options are the cause. Nothing else springs to mind as to cause. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
Sorry for messing up the OS version. I didn't see the Logitec wireless device listed in the list of event when I type sudo evtest. lsusb output: http://pastebin.com/ks936UGE dmesg output: http://pastebin.com/c3MRPTSn >-Original Message- >From: James Cameron [mailto:qu...@laptop.org] >Sent: Monday, September 22, 2014 09:38 AM >To: tkk...@nurturingasia.com >Cc: devel@lists.laptop.org >Subject: Re: Logitech USB wireless keyboard with trackpad on XO-1.75 > >On Mon, Sep 22, 2014 at 01:11:59AM +, tkk...@nurturingasia.com wrote: >> Tried both XO-1 and XO-1.5. Can't get usbutils to check the lsusb >> test (mirror fails to get file) > >It is there. Something wrong with your internet service. Perhaps >filtering or temporary outage. Try with different internet service. > >If you still have problems, the usbutils package is available from our >frozen repositories server: > >http://mock.laptop.org/cgit/koji.dist-f18-i686-updates-13.2.0/plain/RPMS/usbutils-006-4.fc18.i686.rpm > (for 13.2.1) > >or > >http://mock.laptop.org/cgit/koji.dist-f17-i686/plain/RPMS/u/usbutils-004-4.fc17.i686.rpm > (for 12.1.0) > >Can be downloaded with wget and installed with rpm --install. > >> Did the evtest and I don't see the 2 events for Logitech USB >> receiver unlike the XO 1.75 > >To clarify; you didn't see the device listed in the list of event >sources, or you didn't see device events once you had selected a >source? > >> Here is the dmesg >> >> http://pastebin.com/ydKGicV6 > >Thanks. Important parts are: > >[0.00] Linux version 3.3.8_xo1-20120705.1732.olpc.5d48a2f >(kern...@bob.laptop.org) (gcc version 4.7.0 20120507 (Red Hat 4.7.0-5) (GCC) ) >#1 PREEMPT Thu Jul 5 17:34:54 EDT 2012 >... >[ 235.630088] usb 2-2: new full-speed USB device number 2 using ohci_hcd >[ 235.925584] usbcore: registered new interface driver usbhid >[ 235.953665] usbhid: USB HID core driver >[ 392.102566] usb 2-2: USB disconnect, device number 2 >[ 1004.640092] usb 2-2: new full-speed USB device number 3 using ohci_hcd> > >The kernel version does not match 13.2.1, it should be >3.3.8_xo1-20140619.1058.olpc.355c89e.i686 >per >http://download.laptop.org/xo-1/os/official/13.2.1-14/32014o0.packages.txt >but is instead >3.3.8_xo1-20120705.1732.olpc.5d48a2f >which is the version in >http://download.laptop.org/xo-1/os/official/12.1.0-21/21021o0.packages.txt >so suddenly you've switched to testing with 12.1.0, which is terribly >uninteresting to me. > >Please test instead with 13.2.1, thanks. > >-- >James Cameron >http://quozl.linux.org.au/ > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
On Mon, Sep 22, 2014 at 01:11:59AM +, tkk...@nurturingasia.com wrote: > Tried both XO-1 and XO-1.5. Can't get usbutils to check the lsusb > test (mirror fails to get file) It is there. Something wrong with your internet service. Perhaps filtering or temporary outage. Try with different internet service. If you still have problems, the usbutils package is available from our frozen repositories server: http://mock.laptop.org/cgit/koji.dist-f18-i686-updates-13.2.0/plain/RPMS/usbutils-006-4.fc18.i686.rpm (for 13.2.1) or http://mock.laptop.org/cgit/koji.dist-f17-i686/plain/RPMS/u/usbutils-004-4.fc17.i686.rpm (for 12.1.0) Can be downloaded with wget and installed with rpm --install. > Did the evtest and I don't see the 2 events for Logitech USB > receiver unlike the XO 1.75 To clarify; you didn't see the device listed in the list of event sources, or you didn't see device events once you had selected a source? > Here is the dmesg > > http://pastebin.com/ydKGicV6 Thanks. Important parts are: [0.00] Linux version 3.3.8_xo1-20120705.1732.olpc.5d48a2f (kern...@bob.laptop.org) (gcc version 4.7.0 20120507 (Red Hat 4.7.0-5) (GCC) ) #1 PREEMPT Thu Jul 5 17:34:54 EDT 2012 ... [ 235.630088] usb 2-2: new full-speed USB device number 2 using ohci_hcd [ 235.925584] usbcore: registered new interface driver usbhid [ 235.953665] usbhid: USB HID core driver [ 392.102566] usb 2-2: USB disconnect, device number 2 [ 1004.640092] usb 2-2: new full-speed USB device number 3 using ohci_hcd> The kernel version does not match 13.2.1, it should be 3.3.8_xo1-20140619.1058.olpc.355c89e.i686 per http://download.laptop.org/xo-1/os/official/13.2.1-14/32014o0.packages.txt but is instead 3.3.8_xo1-20120705.1732.olpc.5d48a2f which is the version in http://download.laptop.org/xo-1/os/official/12.1.0-21/21021o0.packages.txt so suddenly you've switched to testing with 12.1.0, which is terribly uninteresting to me. Please test instead with 13.2.1, thanks. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
Tried both XO-1 and XO-1.5. Can't get usbutils to check the lsusb test (mirror fails to get file) Did the evtest and I don't see the 2 events for Logitech USB receiver unlike the XO 1.75 Here is the dmesg http://pastebin.com/ydKGicV6 >-Original Message- >From: James Cameron [mailto:qu...@laptop.org] >Sent: Monday, September 22, 2014 08:25 AM >To: tkk...@nurturingasia.com >Cc: devel@lists.laptop.org >Subject: Re: Logitech USB wireless keyboard with trackpad on XO-1.75 > >On Sun, Sep 21, 2014 at 11:40:19PM +, tkk...@nurturingasia.com wrote: >> When the USB wireless keyboard/trackpad is plugin unlike the XO 1.75 >> both won't work. Tried disabling the olpc-kbdshim but stil does not >> work. Using the 13.2.1 (build 4) on the XO-1. > >Thanks. On the XO-1, step back to the lsusb test, and do the evtest >as well. > >If lsusb does not show it, you may have an electrical problem or >damage to the XO-1. See if a different port works, or if a powered >hub works. > >If lsusb does show it, but evtest does not show it, then a kernel >driver may be missing. This is not surprising, because we made sure >XO-1 kernel was as small a possible, and many drivers were removed. > >If lsusb does show it, but evtest does not show it, please also >capture the output of dmesg and drop it in a pastebin [1] for us to >see. > >1. http://en.wikipedia.org/wiki/Pastebin > >-- >James Cameron >http://quozl.linux.org.au/ > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
On Sun, Sep 21, 2014 at 11:40:19PM +, tkk...@nurturingasia.com wrote: > When the USB wireless keyboard/trackpad is plugin unlike the XO 1.75 > both won't work. Tried disabling the olpc-kbdshim but stil does not > work. Using the 13.2.1 (build 4) on the XO-1. Thanks. On the XO-1, step back to the lsusb test, and do the evtest as well. If lsusb does not show it, you may have an electrical problem or damage to the XO-1. See if a different port works, or if a powered hub works. If lsusb does show it, but evtest does not show it, then a kernel driver may be missing. This is not surprising, because we made sure XO-1 kernel was as small a possible, and many drivers were removed. If lsusb does show it, but evtest does not show it, please also capture the output of dmesg and drop it in a pastebin [1] for us to see. 1. http://en.wikipedia.org/wiki/Pastebin -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
) >-Original Message- >From: Paul Fox [mailto:p...@laptop.org] >Sent: Saturday, September 20, 2014 11:19 PM >To: tkk...@nurturingasia.com >Cc: devel@lists.laptop.org >Subject: Re: Logitech USB wireless keyboard with trackpad on XO-1.75 > >tkk...@nurturingasia.com wrote: > > Tried this first thing in the morning. Disabling kdbshim and the > > MakeyMakey activity does the trick on my XO 1.75! > >thanks. would you be in a position to test a fix for this, if i sent >you a new olpc-kbdshim binary to try? i prepared a patch some time >ago for kbdshim, which causes it to (mostly) ignore external devices. >but since i don't have makeymakey hardware, it never really got >tested. i think the same patch may solve your problem. > >but first, please try this: >- disable kbdshim, as you have done previously. >- run "sudo evtest". this will show you a list of > system input devices. >- one of those devices should be your logitech device. select > it by number. >- it will dump a list of supported events and properties, then > it will loop, reporting individual events as they arrive from > that device. i'm only interested in the initial list of events > and properties, so you can use ^C to kill evtest as soon as you'd > like. >- send me the resulting output. > >paul > > > > > Thanks for the advice from all! There is so much to learn :-) > > > > Have a great weekend! > > > > > > >-Original Message----- > > >From: Paul Fox [mailto:p...@laptop.org] > > >Sent: Saturday, September 20, 2014 12:52 AM > > >To: tkk...@nurturingasia.com > > >Cc: devel@lists.laptop.org > > >Subject: Re: Logitech USB wireless keyboard with trackpad on XO-1.75 > > > > > >have you tried disabling kbdshim, as suggested by james? use either: > > > sudo systemctl stop olpc-kbdshim.service > > >or the MakeyMakey activity to do this. kbdshim can interfere with > > >the operation of some integrated multi-device hardware. > > > > > >paul > > > > > >tkk...@nurturingasia.com wrote: > > > > Managed to get via yum install usbutils > > > > > > > > "sudo lsusb -v" command gives a long list: > > > > > > > > For the Logitec k400r (wireless keyboard with trackpad) I get this > > > > output: > > > > > > > > Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver > > > > Device Descriptor: > > > > bLength 18 > > > > bDescriptorType 1 > > > > bcdUSB 2.00 > > > > bDeviceClass 0 (Defined at Interface level) > > > > bDeviceSubClass 0 > > > > bDeviceProtocol 0 > > > > bMaxPacketSize0 8 > > > > idVendor 0x046d Logitech, Inc. > > > > idProduct 0xc52b Unifying Receiver > > > > bcdDevice 12.01 > > > > iManufacturer 1 Logitech > > > > iProduct 2 USB Receiver > > > > iSerial 0 > > > > bNumConfigurations 1 > > > > Configuration Descriptor: > > > > bLength 9 > > > > bDescriptorType 2 > > > > wTotalLength 84 > > > > bNumInterfaces 3 > > > > bConfigurationValue 1 > > > > iConfiguration 4 RQR12.01_B0019 > > > > bmAttributes 0xa0 > > > > (Bus Powered) > > > > Remote Wakeup > > > > MaxPower 98mA > > > > Interface Descriptor: > > > > bLength 9 > > > > bDescriptorType 4 > > > > bInterfaceNumber 0 > > > > bAlternateSetting 0 > > > > bNumEndpoints 1 > > > > bInterfaceClass 3 Human Interface Device > > > > bInterfaceSubClass 1 Boot Interface Subclass > > > > bInterfaceProtocol 1 Keyboard > > > > iInterface 0 > > > > HID Device Descriptor: > > > > bLength 9 > > > > bDescriptorType 33 > > > > bcdHID 1.11 > > > > bCountryCode 0 Not supported > > > > bNumDescriptors 1 > > > > bDescriptorType 34 Report > > > > wDescriptorLength 59 > > > > Report Descriptors: > > > > ** UNAVAILABLE ** > > > > Endpoint Descriptor: > > > > bLength 7 > > > > bDescriptorType 5 > > > > bEndpointAddress 0x81 EP 1 IN > > > > bmAttributes 3 > > > > Transfer Type Interrupt > > > > Synch Type None > > > > Usage Type Data > > > > wMaxPacketSize 0
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
When the USB wireless keyboard/trackpad is plugin unlike the XO 1.75 both won't work. Tried disabling the olpc-kbdshim but stil does not work. Using the 13.2.1 (build 4) on the XO-1. >problem? >-Original Message- >From: James Cameron [mailto:qu...@laptop.org] >Sent: Monday, September 22, 2014 06:35 AM >To: tkk...@nurturingasia.com >Cc: devel@lists.laptop.org >Subject: Re: Logitech USB wireless keyboard with trackpad on XO-1.75 > >On Sat, Sep 20, 2014 at 12:17:13AM +, tkk...@nurturingasia.com wrote: >> The XO-1 does not recognise the USB wireless keyboard. Must be some >> missing drivers. > >Why do you think it is missing drivers and not the same olpc-kbdshim >problem? > >Did you try the disabling of olpc-kbdshim? > >> It has worked before as in this writeup. >> >> http://www.olpcnews.com/laptops/xo1/recommended_accessories_for_your_xo.html#sthash.mFC4Cqrj.dpuf > >That's from 2008, too old to be useful; because you aren't using an >operating system from 2008. Forget it. Also, I really doubt you have >the same product, so not useful for that reason as well. > >-- >James Cameron >http://quozl.linux.org.au/ > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
On Sat, Sep 20, 2014 at 12:17:13AM +, tkk...@nurturingasia.com wrote: > The XO-1 does not recognise the USB wireless keyboard. Must be some > missing drivers. Why do you think it is missing drivers and not the same olpc-kbdshim problem? Did you try the disabling of olpc-kbdshim? > It has worked before as in this writeup. > > http://www.olpcnews.com/laptops/xo1/recommended_accessories_for_your_xo.html#sthash.mFC4Cqrj.dpuf That's from 2008, too old to be useful; because you aren't using an operating system from 2008. Forget it. Also, I really doubt you have the same product, so not useful for that reason as well. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
On Sat, Sep 20, 2014 at 11:19:21AM -0400, Paul Fox wrote: > tkk...@nurturingasia.com wrote: > > Tried this first thing in the morning. Disabling kdbshim and the > > MakeyMakey activity does the trick on my XO 1.75! > > thanks. would you be in a position to test a fix for this, if i sent > you a new olpc-kbdshim binary to try? i prepared a patch some time > ago for kbdshim, which causes it to (mostly) ignore external devices. > but since i don't have makeymakey hardware, it never really got > tested. i think the same patch may solve your problem. > > but first, please try this: > - disable kbdshim, as you have done previously. > - run "sudo evtest". this will show you a list of > system input devices. > - one of those devices should be your logitech device. select > it by number. > - it will dump a list of supported events and properties, then > it will loop, reporting individual events as they arrive from > that device. i'm only interested in the initial list of events > and properties, so you can use ^C to kill evtest as soon as you'd > like. > - send me the resulting output. I'm interested in the output as well, or at least the conclusions made. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
Thanks and I will be happy to test the patch, etc. Wondering what is needed for XO-1 laptop to work. >-Original Message- >From: Paul Fox [mailto:p...@laptop.org] >Sent: Saturday, September 20, 2014 11:19 PM >To: tkk...@nurturingasia.com >Cc: devel@lists.laptop.org >Subject: Re: Logitech USB wireless keyboard with trackpad on XO-1.75 > >tkk...@nurturingasia.com wrote: > > Tried this first thing in the morning. Disabling kdbshim and the > > MakeyMakey activity does the trick on my XO 1.75! > >thanks. would you be in a position to test a fix for this, if i sent >you a new olpc-kbdshim binary to try? i prepared a patch some time >ago for kbdshim, which causes it to (mostly) ignore external devices. >but since i don't have makeymakey hardware, it never really got >tested. i think the same patch may solve your problem. > >but first, please try this: >- disable kbdshim, as you have done previously. >- run "sudo evtest". this will show you a list of > system input devices. >- one of those devices should be your logitech device. select > it by number. >- it will dump a list of supported events and properties, then > it will loop, reporting individual events as they arrive from > that device. i'm only interested in the initial list of events > and properties, so you can use ^C to kill evtest as soon as you'd > like. >- send me the resulting output. > >paul > > > > > Thanks for the advice from all! There is so much to learn :-) > > > > Have a great weekend! > > > > > > >-Original Message- > > >From: Paul Fox [mailto:p...@laptop.org] > > >Sent: Saturday, September 20, 2014 12:52 AM > > >To: tkk...@nurturingasia.com > > >Cc: devel@lists.laptop.org > > >Subject: Re: Logitech USB wireless keyboard with trackpad on XO-1.75 > > > > > >have you tried disabling kbdshim, as suggested by james? use either: > > > sudo systemctl stop olpc-kbdshim.service > > >or the MakeyMakey activity to do this. kbdshim can interfere with > > >the operation of some integrated multi-device hardware. > > > > > >paul > > > > > >tkk...@nurturingasia.com wrote: > > > > Managed to get via yum install usbutils > > > > > > > > "sudo lsusb -v" command gives a long list: > > > > > > > > For the Logitec k400r (wireless keyboard with trackpad) I get this > > > > output: > > > > > > > > Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver > > > > Device Descriptor: > > > > bLength 18 > > > > bDescriptorType 1 > > > > bcdUSB 2.00 > > > > bDeviceClass 0 (Defined at Interface level) > > > > bDeviceSubClass 0 > > > > bDeviceProtocol 0 > > > > bMaxPacketSize0 8 > > > > idVendor 0x046d Logitech, Inc. > > > > idProduct 0xc52b Unifying Receiver > > > > bcdDevice 12.01 > > > > iManufacturer 1 Logitech > > > > iProduct 2 USB Receiver > > > > iSerial 0 > > > > bNumConfigurations 1 > > > > Configuration Descriptor: > > > > bLength 9 > > > > bDescriptorType 2 > > > > wTotalLength 84 > > > > bNumInterfaces 3 > > > > bConfigurationValue 1 > > > > iConfiguration 4 RQR12.01_B0019 > > > > bmAttributes 0xa0 > > > > (Bus Powered) > > > > Remote Wakeup > > > > MaxPower 98mA > > > > Interface Descriptor: > > > > bLength 9 > > > > bDescriptorType 4 > > > > bInterfaceNumber 0 > > > > bAlternateSetting 0 > > > > bNumEndpoints 1 > > > > bInterfaceClass 3 Human Interface Device > > > > bInterfaceSubClass 1 Boot Interface Subclass > > > > bInterfaceProtocol 1 Keyboard > > > > iInterface 0 > > > > HID Device Descriptor: > > > > bLength 9 > > > > bDescriptorType 33 > > > > bcdHID 1.11 > > > > bCountryCode 0 Not supported > > > > bNumDescriptors 1 > > > > bDescriptorType 34 Report > > > > wDescriptorLength 59 > > > > Report Descriptors: > > > > ** UNAVAILABLE ** > > > > Endpoint Descriptor: > > > > bLength 7 > > > > bDescriptorType 5 > > > > bEndpointAddress 0x81 EP 1 IN > > > > bmAttributes 3 > > > > Transfer Type Interrupt > > > >
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
tkk...@nurturingasia.com wrote: > Tried this first thing in the morning. Disabling kdbshim and the > MakeyMakey activity does the trick on my XO 1.75! thanks. would you be in a position to test a fix for this, if i sent you a new olpc-kbdshim binary to try? i prepared a patch some time ago for kbdshim, which causes it to (mostly) ignore external devices. but since i don't have makeymakey hardware, it never really got tested. i think the same patch may solve your problem. but first, please try this: - disable kbdshim, as you have done previously. - run "sudo evtest". this will show you a list of system input devices. - one of those devices should be your logitech device. select it by number. - it will dump a list of supported events and properties, then it will loop, reporting individual events as they arrive from that device. i'm only interested in the initial list of events and properties, so you can use ^C to kill evtest as soon as you'd like. - send me the resulting output. paul > > Thanks for the advice from all! There is so much to learn :-) > > Have a great weekend! > > > >-Original Message- > >From: Paul Fox [mailto:p...@laptop.org] > >Sent: Saturday, September 20, 2014 12:52 AM > >To: tkk...@nurturingasia.com > >Cc: devel@lists.laptop.org > >Subject: Re: Logitech USB wireless keyboard with trackpad on XO-1.75 > > > >have you tried disabling kbdshim, as suggested by james? use either: > >sudo systemctl stop olpc-kbdshim.service > >or the MakeyMakey activity to do this. kbdshim can interfere with > >the operation of some integrated multi-device hardware. > > > >paul > > > >tkk...@nurturingasia.com wrote: > > > Managed to get via yum install usbutils > > > > > > "sudo lsusb -v" command gives a long list: > > > > > > For the Logitec k400r (wireless keyboard with trackpad) I get this > > > output: > > > > > > Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver > > > Device Descriptor: > > > bLength 18 > > > bDescriptorType 1 > > > bcdUSB 2.00 > > > bDeviceClass 0 (Defined at Interface level) > > > bDeviceSubClass 0 > > > bDeviceProtocol 0 > > > bMaxPacketSize0 8 > > > idVendor 0x046d Logitech, Inc. > > > idProduct 0xc52b Unifying Receiver > > > bcdDevice 12.01 > > > iManufacturer 1 Logitech > > > iProduct 2 USB Receiver > > > iSerial 0 > > > bNumConfigurations 1 > > > Configuration Descriptor: > > > bLength 9 > > > bDescriptorType 2 > > > wTotalLength 84 > > > bNumInterfaces 3 > > > bConfigurationValue 1 > > > iConfiguration 4 RQR12.01_B0019 > > > bmAttributes 0xa0 > > > (Bus Powered) > > > Remote Wakeup > > > MaxPower 98mA > > > Interface Descriptor: > > > bLength 9 > > > bDescriptorType 4 > > > bInterfaceNumber 0 > > > bAlternateSetting 0 > > > bNumEndpoints 1 > > > bInterfaceClass 3 Human Interface Device > > > bInterfaceSubClass 1 Boot Interface Subclass > > > bInterfaceProtocol 1 Keyboard > > > iInterface 0 > > > HID Device Descriptor: > > > bLength 9 > > > bDescriptorType 33 > > > bcdHID 1.11 > > > bCountryCode 0 Not supported > > > bNumDescriptors 1 > > > bDescriptorType 34 Report > > > wDescriptorLength 59 > > > Report Descriptors: > > > ** UNAVAILABLE ** > > > Endpoint Descriptor: > > > bLength 7 > > > bDescriptorType 5 > > > bEndpointAddress 0x81 EP 1 IN > > > bmAttributes 3 > > > Transfer Type Interrupt > > > Synch Type None > > > Usage Type Data > > > wMaxPacketSize 0x0008 1x 8 bytes > > > bInterval 8 > > > Interface Descriptor: > > > bLength 9 > > > bDescriptorType 4 > > > bInterfaceNumber 1 > > > bAlternateSetting 0 > > > bNumEndpoints 1 > > > bInterfaceClass 3 Human Interface Device > > > bInterfaceSubClass 1 Boot Interface Subclass > > > bInterfaceProtocol 2 Mouse > > > iInterface 0 > > > HID Device Descriptor: > > > bLength 9 > > > bDescriptorType 33 > > > bcdHID 1.11 > > > bCountryCode 0 Not supported > > > bNumDescriptors 1 > > > bDescriptorType 34 Report > > > wDesc
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
The XO-1 does not recognise the USB wireless keyboard. Must be some missing drivers. It has worked before as in this writeup. http://www.olpcnews.com/laptops/xo1/recommended_accessories_for_your_xo.html#sthash.mFC4Cqrj.dpuf XO wireless mouse: I admit it, before receiving the XO wireless mouse I wasn't quite sure whether I would really need it. But now I actually use it quite a lot! A wireless mouse also comes in handy when demonstrating Sugar to other people since you can stand in the back row while showing off the Journal, collaboration, etc. Cheers >-Original Message- >From: tkk...@nurturingasia.com [mailto:tkk...@nurturingasia.com] >Sent: Saturday, September 20, 2014 07:39 AM >To: 'Paul Fox' >Cc: devel@lists.laptop.org >Subject: Re: Logitech USB wireless keyboard with trackpad on XO-1.75 > >Tried this first thing in the morning. Disabling kdbshim and the MakeyMakey >activity does the trick on my XO 1.75! > >Thanks for the advice from all! There is so much to learn :-) > >Have a great weekend! > > >>-Original Message- >>From: Paul Fox [mailto:p...@laptop.org] >>Sent: Saturday, September 20, 2014 12:52 AM >>To: tkk...@nurturingasia.com >>Cc: devel@lists.laptop.org >>Subject: Re: Logitech USB wireless keyboard with trackpad on XO-1.75 >> >>have you tried disabling kbdshim, as suggested by james? use either: >> sudo systemctl stop olpc-kbdshim.service >>or the MakeyMakey activity to do this. kbdshim can interfere with >>the operation of some integrated multi-device hardware. >> >>paul >> >>tkk...@nurturingasia.com wrote: >> > Managed to get via yum install usbutils >> > >> > "sudo lsusb -v" command gives a long list: >> > >> > For the Logitec k400r (wireless keyboard with trackpad) I get this output: >> > >> > Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver >> > Device Descriptor: >> > bLength 18 >> > bDescriptorType 1 >> > bcdUSB 2.00 >> > bDeviceClass 0 (Defined at Interface level) >> > bDeviceSubClass 0 >> > bDeviceProtocol 0 >> > bMaxPacketSize0 8 >> > idVendor 0x046d Logitech, Inc. >> > idProduct 0xc52b Unifying Receiver >> > bcdDevice 12.01 >> > iManufacturer 1 Logitech >> > iProduct 2 USB Receiver >> > iSerial 0 >> > bNumConfigurations 1 >> > Configuration Descriptor: >> > bLength 9 >> > bDescriptorType 2 >> > wTotalLength 84 >> > bNumInterfaces 3 >> > bConfigurationValue 1 >> > iConfiguration 4 RQR12.01_B0019 >> > bmAttributes 0xa0 >> > (Bus Powered) >> > Remote Wakeup >> > MaxPower 98mA >> > Interface Descriptor: >> > bLength 9 >> > bDescriptorType 4 >> > bInterfaceNumber 0 >> > bAlternateSetting 0 >> > bNumEndpoints 1 >> > bInterfaceClass 3 Human Interface Device >> > bInterfaceSubClass 1 Boot Interface Subclass >> > bInterfaceProtocol 1 Keyboard >> > iInterface 0 >> > HID Device Descriptor: >> > bLength 9 >> > bDescriptorType 33 >> > bcdHID 1.11 >> > bCountryCode 0 Not supported >> > bNumDescriptors 1 >> > bDescriptorType 34 Report >> > wDescriptorLength 59 >> > Report Descriptors: >> > ** UNAVAILABLE ** >> > Endpoint Descriptor: >> > bLength 7 >> > bDescriptorType 5 >> > bEndpointAddress 0x81 EP 1 IN >> > bmAttributes 3 >> > Transfer Type Interrupt >> > Synch Type None >> > Usage Type Data >> > wMaxPacketSize 0x0008 1x 8 bytes >> > bInterval 8 >> > Interface Descriptor: >> > bLength 9 >> > bDescriptorType 4 >> > bInterfaceNumber 1 >> > bAlternateSetting 0 >> > bNumEndpoints 1 >> > bInterfaceClass 3 Human Interface Device >> > bInterfaceSubClass 1 Boot Interface Subclass >> > bInterfaceProtocol 2 Mouse >> > iInterface 0 >> > HID Device Descriptor: >> > bLength 9 >> > bDescriptorType 33 >> > bcdHID 1.11 >> > bCountryCode 0 Not supported >> > bNumDescriptors 1 >> > bDescriptorType 34 Report >> > wDescriptorLength 148 >> > Report Descriptors: >> > ** UNAVAILABLE ** >> > Endpoint Descriptor: >> > bLength 7 >> > bDescriptorType 5 >> > bEndpointAddress 0x82 EP 2 IN >> > bmAttributes 3 >> > Transfer Type Interrupt >> > Synch Type None >> > Usage Type Data >> >
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
Tried this first thing in the morning. Disabling kdbshim and the MakeyMakey activity does the trick on my XO 1.75! Thanks for the advice from all! There is so much to learn :-) Have a great weekend! >-Original Message- >From: Paul Fox [mailto:p...@laptop.org] >Sent: Saturday, September 20, 2014 12:52 AM >To: tkk...@nurturingasia.com >Cc: devel@lists.laptop.org >Subject: Re: Logitech USB wireless keyboard with trackpad on XO-1.75 > >have you tried disabling kbdshim, as suggested by james? use either: > sudo systemctl stop olpc-kbdshim.service >or the MakeyMakey activity to do this. kbdshim can interfere with >the operation of some integrated multi-device hardware. > >paul > >tkk...@nurturingasia.com wrote: > > Managed to get via yum install usbutils > > > > "sudo lsusb -v" command gives a long list: > > > > For the Logitec k400r (wireless keyboard with trackpad) I get this output: > > > > Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver > > Device Descriptor: > > bLength 18 > > bDescriptorType 1 > > bcdUSB 2.00 > > bDeviceClass 0 (Defined at Interface level) > > bDeviceSubClass 0 > > bDeviceProtocol 0 > > bMaxPacketSize0 8 > > idVendor 0x046d Logitech, Inc. > > idProduct 0xc52b Unifying Receiver > > bcdDevice 12.01 > > iManufacturer 1 Logitech > > iProduct 2 USB Receiver > > iSerial 0 > > bNumConfigurations 1 > > Configuration Descriptor: > > bLength 9 > > bDescriptorType 2 > > wTotalLength 84 > > bNumInterfaces 3 > > bConfigurationValue 1 > > iConfiguration 4 RQR12.01_B0019 > > bmAttributes 0xa0 > > (Bus Powered) > > Remote Wakeup > > MaxPower 98mA > > Interface Descriptor: > > bLength 9 > > bDescriptorType 4 > > bInterfaceNumber 0 > > bAlternateSetting 0 > > bNumEndpoints 1 > > bInterfaceClass 3 Human Interface Device > > bInterfaceSubClass 1 Boot Interface Subclass > > bInterfaceProtocol 1 Keyboard > > iInterface 0 > > HID Device Descriptor: > > bLength 9 > > bDescriptorType 33 > > bcdHID 1.11 > > bCountryCode 0 Not supported > > bNumDescriptors 1 > > bDescriptorType 34 Report > > wDescriptorLength 59 > > Report Descriptors: > > ** UNAVAILABLE ** > > Endpoint Descriptor: > > bLength 7 > > bDescriptorType 5 > > bEndpointAddress 0x81 EP 1 IN > > bmAttributes 3 > > Transfer Type Interrupt > > Synch Type None > > Usage Type Data > > wMaxPacketSize 0x0008 1x 8 bytes > > bInterval 8 > > Interface Descriptor: > > bLength 9 > > bDescriptorType 4 > > bInterfaceNumber 1 > > bAlternateSetting 0 > > bNumEndpoints 1 > > bInterfaceClass 3 Human Interface Device > > bInterfaceSubClass 1 Boot Interface Subclass > > bInterfaceProtocol 2 Mouse > > iInterface 0 > > HID Device Descriptor: > > bLength 9 > > bDescriptorType 33 > > bcdHID 1.11 > > bCountryCode 0 Not supported > > bNumDescriptors 1 > > bDescriptorType 34 Report > > wDescriptorLength 148 > > Report Descriptors: > > ** UNAVAILABLE ** > > Endpoint Descriptor: > > bLength 7 > > bDescriptorType 5 > > bEndpointAddress 0x82 EP 2 IN > > bmAttributes 3 > > Transfer Type Interrupt > > Synch Type None > > Usage Type Data > > wMaxPacketSize 0x0008 1x 8 bytes > > bInterval 2 > > Interface Descriptor: > > bLength 9 > > bDescriptorType 4 > > bInterfaceNumber 2 > > bAlternateSetting 0 > > bNumEndpoints 1 > > bInterfaceClass 3 Human Interface Device > > bInterfaceSubClass 0 No Subclass > > bInterfaceProtocol 0 None > > iInterface 0 > > HID Device Descriptor: > > bLength 9 > > bDescriptorType 33 > > bcdHID 1.11 > > bCountryCode 0 Not supported > > bNumDescriptors 1 > > bDescriptorType 34 Report > > wDescriptorLength 98 > > Report Descriptors: > > ** UNAVAILABLE ** > > Endpoint Descriptor: > > bLength 7 > > bDescriptorType 5 > > bEndpointAddress 0x83 EP 3 IN > > bmAttributes 3 > > Transfer Type Interrupt > > Synch Type None > > Usage Type Data > > wMaxPacketSize 0x0020 1x 32 bytes > > bInterval 2 > > Device Status: 0x > > (Bus Powered) > > >-Original Message- > > >From: James Cameron [mailto:qu...@laptop.org] > > >Sent: Friday, September 19, 2014 09:48 AM > > >To: tkk...@nurturingasia.com > > >Cc: 'T Gillett', devel@lists.laptop.org, p...@laptop.org > >
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
have you tried disabling kbdshim, as suggested by james? use either: sudo systemctl stop olpc-kbdshim.service or the MakeyMakey activity to do this. kbdshim can interfere with the operation of some integrated multi-device hardware. paul tkk...@nurturingasia.com wrote: > Managed to get via yum install usbutils > > "sudo lsusb -v" command gives a long list: > > For the Logitec k400r (wireless keyboard with trackpad) I get this output: > > Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x046d Logitech, Inc. > idProduct 0xc52b Unifying Receiver > bcdDevice 12.01 > iManufacturer 1 Logitech > iProduct 2 USB Receiver > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 84 > bNumInterfaces 3 > bConfigurationValue 1 > iConfiguration 4 RQR12.01_B0019 > bmAttributes 0xa0 > (Bus Powered) > Remote Wakeup > MaxPower 98mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 Human Interface Device > bInterfaceSubClass 1 Boot Interface Subclass > bInterfaceProtocol 1 Keyboard > iInterface 0 > HID Device Descriptor: > bLength 9 > bDescriptorType 33 > bcdHID 1.11 > bCountryCode 0 Not supported > bNumDescriptors 1 > bDescriptorType 34 Report > wDescriptorLength 59 > Report Descriptors: > ** UNAVAILABLE ** > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0008 1x 8 bytes > bInterval 8 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 Human Interface Device > bInterfaceSubClass 1 Boot Interface Subclass > bInterfaceProtocol 2 Mouse > iInterface 0 > HID Device Descriptor: > bLength 9 > bDescriptorType 33 > bcdHID 1.11 > bCountryCode 0 Not supported > bNumDescriptors 1 > bDescriptorType 34 Report > wDescriptorLength 148 > Report Descriptors: > ** UNAVAILABLE ** > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x82 EP 2 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0008 1x 8 bytes > bInterval 2 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 2 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 Human Interface Device > bInterfaceSubClass 0 No Subclass > bInterfaceProtocol 0 None > iInterface 0 > HID Device Descriptor: > bLength 9 > bDescriptorType 33 > bcdHID 1.11 > bCountryCode 0 Not supported > bNumDescriptors 1 > bDescriptorType 34 Report > wDescriptorLength 98 > Report Descriptors: > ** UNAVAILABLE ** > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 EP 3 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0020 1x 32 bytes > bInterval 2 > Device Status: 0x > (Bus Powered) > >-Original Message- > >From: James Cameron [mailto:qu...@laptop.org] > >Sent: Friday, September 19, 2014 09:48 AM > >To: tkk...@nurturingasia.com > >Cc: 'T Gillett', devel@lists.laptop.org, p...@laptop.org > >Subject: Logitech USB wireless keyboard with trackpad on XO-1.75 > > > >This deserves a new thread, as it is not related to purchase of > >replacement keyboards. So I'm changing subject of post and including > >your post below. > > > >On Fri, Sep 19, 2014 at 12:47:13AM +, tkk...@nurturingasia.com wrote: > >> I plug a logitech wireless trackpad with keyboard on to a > >> XO1.75. The keyboard is recognised but not the trackpad. No luck > >> with just a stand alone wireless mouse also. > >> > >> Are there things I need to do to get wireless input access on the > >> XO? > > > >Yes. > > > >There are too many Logitech wireless trackpads with keyboard to be > >able to identify your particular device; could you please supply the > >model number, and the USB vendor and product identifiers shown by the > >"sudo lsusb -v" command. > > >
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
Managed to get via yum install usbutils "sudo lsusb -v" command gives a long list: For the Logitec k400r (wireless keyboard with trackpad) I get this output: Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046d Logitech, Inc. idProduct 0xc52b Unifying Receiver bcdDevice 12.01 iManufacturer 1 Logitech iProduct 2 USB Receiver iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 84 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 4 RQR12.01_B0019 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 98mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 59 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 8 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 148 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 2 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 98 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0020 1x 32 bytes bInterval 2 Device Status: 0x (Bus Powered) >-Original Message- >From: James Cameron [mailto:qu...@laptop.org] >Sent: Friday, September 19, 2014 09:48 AM >To: tkk...@nurturingasia.com >Cc: 'T Gillett', devel@lists.laptop.org, p...@laptop.org >Subject: Logitech USB wireless keyboard with trackpad on XO-1.75 > >This deserves a new thread, as it is not related to purchase of >replacement keyboards. So I'm changing subject of post and including >your post below. > >On Fri, Sep 19, 2014 at 12:47:13AM +, tkk...@nurturingasia.com wrote: >> I plug a logitech wireless trackpad with keyboard on to a >> XO1.75. The keyboard is recognised but not the trackpad. No luck >> with just a stand alone wireless mouse also. >> >> Are there things I need to do to get wireless input access on the >> XO? > >Yes. > >There are too many Logitech wireless trackpads with keyboard to be >able to identify your particular device; could you please supply the >model number, and the USB vendor and product identifiers shown by the >"sudo lsusb -v" command. > >There are too many ways in which a device may present the USB HID >(human interface device) features to the host computer; if you can >provide the "sudo lsusb -v" command output then I can check that. > >You may need to "sudo yum install -y lsusb" to get the lsusb program >installed. > >Moving on to speculation: > >Some devices are not intentionally supported by OLPC OS, for reasons >of space. It is possible to add support. > >Some devices are not sadly not supported by Linux. This particular >device is unlikely to be affected, since other references to it show >support on other Linux distributions [1]. > >Our ticket #12616 [2] seems likely to be the cause of your problem. >Please check to see if any of the workarounds in that ticket fix it >for you. In particular, try stopping olpc-kbdshim process, > > sudo systemctl stop olpc-kbdshim.service > >But this also disables keyboard and touchpad idle detection, rotate >key, touchpad and arrow keys screen rotation support, grab scrolling >key, volume keys, and brightness keys. > >You might also try the MakeyMakey activity on Sugar Lab
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
Thanks for starting this thread. Neat to have no cables as keyboard/trackpad replacement when I have a few keyboards that failed badly on me :-( Just hoping for a plug and play solution Can't get the lsusb utility ... said package not found by yum. The wireless stuff are from Logitec...with model mk260 (logitech wireless combo with mouse) k400r (wireless keyboard with trackpad) Cheers and will try the workround. >-Original Message- >From: James Cameron [mailto:qu...@laptop.org] >Sent: Friday, September 19, 2014 09:48 AM >To: tkk...@nurturingasia.com >Cc: 'T Gillett', devel@lists.laptop.org, p...@laptop.org >Subject: Logitech USB wireless keyboard with trackpad on XO-1.75 > >This deserves a new thread, as it is not related to purchase of >replacement keyboards. So I'm changing subject of post and including >your post below. > >On Fri, Sep 19, 2014 at 12:47:13AM +, tkk...@nurturingasia.com wrote: >> I plug a logitech wireless trackpad with keyboard on to a >> XO1.75. The keyboard is recognised but not the trackpad. No luck >> with just a stand alone wireless mouse also. >> >> Are there things I need to do to get wireless input access on the >> XO? > >Yes. > >There are too many Logitech wireless trackpads with keyboard to be >able to identify your particular device; could you please supply the >model number, and the USB vendor and product identifiers shown by the >"sudo lsusb -v" command. > >There are too many ways in which a device may present the USB HID >(human interface device) features to the host computer; if you can >provide the "sudo lsusb -v" command output then I can check that. > >You may need to "sudo yum install -y lsusb" to get the lsusb program >installed. > >Moving on to speculation: > >Some devices are not intentionally supported by OLPC OS, for reasons >of space. It is possible to add support. > >Some devices are not sadly not supported by Linux. This particular >device is unlikely to be affected, since other references to it show >support on other Linux distributions [1]. > >Our ticket #12616 [2] seems likely to be the cause of your problem. >Please check to see if any of the workarounds in that ticket fix it >for you. In particular, try stopping olpc-kbdshim process, > > sudo systemctl stop olpc-kbdshim.service > >But this also disables keyboard and touchpad idle detection, rotate >key, touchpad and arrow keys screen rotation support, grab scrolling >key, volume keys, and brightness keys. > >You might also try the MakeyMakey activity on Sugar Labs [3], which >uses the same workaround. > >+CC Paul Fox, for interest as olpc-kbdshim author. > >References: > >[1] http://elinux.org/RPi_USB_Keyboards > >[2] http://dev.laptop.org/ticket/12616 > >[3] http://wiki.sugarlabs.org/go/Activities/MakeyMakey > >-- >James Cameron >http://quozl.linux.org.au/ > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
On Thu, Sep 18, 2014 at 9:48 PM, James Cameron wrote: > This deserves a new thread, as it is not related to purchase of > replacement keyboards. So I'm changing subject of post and including > your post below. > > On Fri, Sep 19, 2014 at 12:47:13AM +, tkk...@nurturingasia.com wrote: >> I plug a logitech wireless trackpad with keyboard on to a >> XO1.75. The keyboard is recognised but not the trackpad. No luck >> with just a stand alone wireless mouse also. >> >> Are there things I need to do to get wireless input access on the >> XO? > > Yes. > > There are too many Logitech wireless trackpads with keyboard to be > able to identify your particular device; could you please supply the > model number, and the USB vendor and product identifiers shown by the > "sudo lsusb -v" command. > > There are too many ways in which a device may present the USB HID > (human interface device) features to the host computer; if you can > provide the "sudo lsusb -v" command output then I can check that. > > You may need to "sudo yum install -y lsusb" to get the lsusb program > installed. > > Moving on to speculation: > > Some devices are not intentionally supported by OLPC OS, for reasons > of space. It is possible to add support. > > Some devices are not sadly not supported by Linux. This particular > device is unlikely to be affected, since other references to it show > support on other Linux distributions [1]. > > Our ticket #12616 [2] seems likely to be the cause of your problem. > Please check to see if any of the workarounds in that ticket fix it > for you. In particular, try stopping olpc-kbdshim process, > > sudo systemctl stop olpc-kbdshim.service FWIW, the MakeyMakey activity [1] does this for you. regards. -walter [1] http://activities.sugarlabs.org/en-US/sugar/addon/4729 > > But this also disables keyboard and touchpad idle detection, rotate > key, touchpad and arrow keys screen rotation support, grab scrolling > key, volume keys, and brightness keys. > > You might also try the MakeyMakey activity on Sugar Labs [3], which > uses the same workaround. > > +CC Paul Fox, for interest as olpc-kbdshim author. > > References: > > [1] http://elinux.org/RPi_USB_Keyboards > > [2] http://dev.laptop.org/ticket/12616 > > [3] http://wiki.sugarlabs.org/go/Activities/MakeyMakey > > -- > James Cameron > http://quozl.linux.org.au/ > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Logitech USB wireless keyboard with trackpad on XO-1.75
This deserves a new thread, as it is not related to purchase of replacement keyboards. So I'm changing subject of post and including your post below. On Fri, Sep 19, 2014 at 12:47:13AM +, tkk...@nurturingasia.com wrote: > I plug a logitech wireless trackpad with keyboard on to a > XO1.75. The keyboard is recognised but not the trackpad. No luck > with just a stand alone wireless mouse also. > > Are there things I need to do to get wireless input access on the > XO? Yes. There are too many Logitech wireless trackpads with keyboard to be able to identify your particular device; could you please supply the model number, and the USB vendor and product identifiers shown by the "sudo lsusb -v" command. There are too many ways in which a device may present the USB HID (human interface device) features to the host computer; if you can provide the "sudo lsusb -v" command output then I can check that. You may need to "sudo yum install -y lsusb" to get the lsusb program installed. Moving on to speculation: Some devices are not intentionally supported by OLPC OS, for reasons of space. It is possible to add support. Some devices are not sadly not supported by Linux. This particular device is unlikely to be affected, since other references to it show support on other Linux distributions [1]. Our ticket #12616 [2] seems likely to be the cause of your problem. Please check to see if any of the workarounds in that ticket fix it for you. In particular, try stopping olpc-kbdshim process, sudo systemctl stop olpc-kbdshim.service But this also disables keyboard and touchpad idle detection, rotate key, touchpad and arrow keys screen rotation support, grab scrolling key, volume keys, and brightness keys. You might also try the MakeyMakey activity on Sugar Labs [3], which uses the same workaround. +CC Paul Fox, for interest as olpc-kbdshim author. References: [1] http://elinux.org/RPi_USB_Keyboards [2] http://dev.laptop.org/ticket/12616 [3] http://wiki.sugarlabs.org/go/Activities/MakeyMakey -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
On Tue, Jun 17, 2014 at 12:32 AM, Basanta Shrestha < basanta.shres...@olenepal.org> wrote: > [snip] > > > > I think you need to change the xkb files, but I'm not sure. Do you > > have a mechanical keyboard you can test with? If not, you'll have to > > get someone else to do this. > > > Yes, I have one - the spanish one. What I need to know is how to > enable the key combination for language switching . > You can define new xb mappings in the symbols file for Nepali. Should be in: /usr/share/X11/xkb/symbols/np > > [snip] > > -- > Basanta Shrestha > Network Engineer > Open Learning Exchange (OLE) Nepal > Tel: +977.1.551, 5520075 Ext. 303 > Cell: +977.9818 605110 > http://www.olenepal.org > -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
On Mon, Jun 16, 2014 at 3:20 PM, James Cameron wrote: > On Mon, Jun 16, 2014 at 01:54:19PM +0545, Basanta Shrestha wrote: >> Hi all, >> We are planning on ordering the next lot of XO-4s and I need some >> suggestions on which keyboard model to choose -membrane or >> hard/clicky one. > > I think it is great to seek input from the community, but don't forget > to ask your OLPC contact for help as well. > >> We had membrane one for our first lot and keyboard switching was >> very convenient on that model. One reason not to choose hard/clicky >> one is that it doesn't have key for language switching ( correct me >> if I am wrong) -I have one spanish hard/clicky and it doesn't have >> that key - key 56 at >> http://wiki.laptop.org/go/OLPC_Keyboard_layouts. > > Yes, that's a good reason not to choose the mechanical keyboard; you > would have to customise your operating system build again, to add a > key combination for keyboard language switch. If the cost of > customising is too high, you should order membrane keyboard. I don't > know the relative costs of the keyboards, and their replacement rates, > but it might be factored in to your decision. The cost for customization and building again is not expensive. I have a build machine set up in front of me. > > You identified the lack of language switch key in this same thread on > sugar-devel@ back in November 2013, from which I'll draw some status: > > Walter says use a key combination: > http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045724.html > > And says that customisation will be needed: > http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045800.html > > Then you suggest alt+space: > http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045807.html > > Daniel Drake says to use olpc-os-builder: > http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045851.html > > And you asked about the alt+space: > http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045857.html > > But the thread dried up on that subject because the units you received > had a membrane keyboard, not a mechanical keyboard. Yes, that was exactly what happened. > > I think you need to change the xkb files, but I'm not sure. Do you > have a mechanical keyboard you can test with? If not, you'll have to > get someone else to do this. Yes, I have one - the spanish one. What I need to know is how to enable the key combination for language switching . > >> Hard/Clicky on the other hard is more convenient while typing. >> Please suggest. > > I don't understand why you think it is more convenient. To me the > keyboards are equally convenient for an inexperienced child. Perhaps > you intended to mention some characteristic? Parhaps you may be right, but It is really inconvenient when you want to type fast on membrane keyboard. The problem is exactly what Prof. Sameer Varma has pointed out later in this thread - "the outer edges of the fingers get in the way of a full key depress" but even thismay not be big issues for kids cause they mostly type character by character using two fingers. > > -- > James Cameron > http://quozl.linux.org.au/ -- Basanta Shrestha Network Engineer Open Learning Exchange (OLE) Nepal Tel: +977.1.551, 5520075 Ext. 303 Cell: +977.9818 605110 http://www.olenepal.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
On Mon, Jun 16, 2014 at 6:19 PM, John Watlington wrote: > > On Jun 16, 2014, at 9:05 PM, Walter Bender wrote: > > On Mon, Jun 16, 2014 at 9:03 PM, John Watlington wrote: >> >> >> Walter, >>You remember correctly. The hard/clicky/crunchy keyboards are not >> rated >> for as long a lifetime as the membrane/chewy keyboards. While the >> membrane >> keyboard design was tested to 5 million key presses, IIRC the clicky >> keyboard is >> only rated to 1 million key presses. (On the other hand, it takes one >> minute >> to replace a clicky keyboard versus twenty for a membrane keyboard.) > > > ..if you have a replacement keyboard... any insight into how easy it would > be to make replacement keys in the field? > > > I would say impossible, but that would be underestimating the creativeness > of > our deployments. > > At the electrical level, the crunchy and chewy keyboards have the same > contacts, > so I don't expect that to be the failure mechanism. Failure should be due > to the > mechanical parts (as it is with the membrane keyboards). If you pull off > the keycap > and the guide mechanism, the key still activates when you press on the > membrane > or the rubber cap (which provides both the spring action and presses on the > contacts) > glued to it. > Back in January 2013, while visiting Khairat (India) I saw a couple of girls using the eraser end of a pencil to push the torn keys on their XO-1s from 2007 (which BTW still hold charge and run the mesh!). Sameer > Cheers, > wad > >> WARNING: The clicky keyboard was not approved for use by small children >> by UL. The reason is that if the keys are pulled off they present a >> choking >> hazard. >> >> Cheers, >> wad >> > > > ___ > 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] seeking help to enable nepali keyboard input for XO-4
Sameer, We made a tooling change to improve that feeling --- we increased the chamfer around the key openings so that if you miss the key slightly, your finger slides into the opening more easily. Unfortunately, this didn't go into production until the XO-4 hit production. Thanks for pointing that out. I'm not sure if Subir and Rabi are aware that the original membrane keyboard is no longer available. The current membrane keyboard is covered by a plastic grid (making it much harder to peel off a key). See http://wiki.laptop.org/go/File:XO-1.75_siblings.jpg Cheers, wad On Jun 16, 2014, at 9:08 PM, Sameer Verma wrote: > On a related note, I was curious about deployment experiences with the > new membrane design with plastic grid in between keys. Although this > does help with premature peeling of keys, I've always had trouble with > these keyboards - the outer edges of my fingers get in the way of a > full key depress. Then again, the keys aren't designed for me, so I'm > curious how these do in the field. > > cheers, > Sameer > > On Mon, Jun 16, 2014 at 6:03 PM, John Watlington wrote: >> >> Walter, >> You remember correctly. The hard/clicky/crunchy keyboards are not rated >> for as long a lifetime as the membrane/chewy keyboards. While the membrane >> keyboard design was tested to 5 million key presses, IIRC the clicky >> keyboard is >> only rated to 1 million key presses. (On the other hand, it takes one >> minute >> to replace a clicky keyboard versus twenty for a membrane keyboard.) >> >> WARNING: The clicky keyboard was not approved for use by small children >> by UL. The reason is that if the keys are pulled off they present a >> choking >> hazard. >> >> Cheers, >> wad >> >> On Jun 16, 2014, at 7:13 AM, Walter Bender wrote: >> >> James, >> >> Do we have any data re the mechanical reliability/durability/repairability >> of the "hard/clicky" keyboards? We do know that although there were some >> issues with membrane pealing (presumably resolved with the newer design) >> there numerous ingenious local repairs such that most are still working >> after 7 years. >> >> regards. >> >> -walter >> >> >> On Mon, Jun 16, 2014 at 5:35 AM, James Cameron wrote: >>> >>> On Mon, Jun 16, 2014 at 01:54:19PM +0545, Basanta Shrestha wrote: >>>> Hi all, >>>> We are planning on ordering the next lot of XO-4s and I need some >>>> suggestions on which keyboard model to choose -membrane or >>>> hard/clicky one. >>> >>> I think it is great to seek input from the community, but don't forget >>> to ask your OLPC contact for help as well. >>> >>>> We had membrane one for our first lot and keyboard switching was >>>> very convenient on that model. One reason not to choose hard/clicky >>>> one is that it doesn't have key for language switching ( correct me >>>> if I am wrong) -I have one spanish hard/clicky and it doesn't have >>>> that key - key 56 at >>>> http://wiki.laptop.org/go/OLPC_Keyboard_layouts. >>> >>> Yes, that's a good reason not to choose the mechanical keyboard; you >>> would have to customise your operating system build again, to add a >>> key combination for keyboard language switch. If the cost of >>> customising is too high, you should order membrane keyboard. I don't >>> know the relative costs of the keyboards, and their replacement rates, >>> but it might be factored in to your decision. >>> >>> You identified the lack of language switch key in this same thread on >>> sugar-devel@ back in November 2013, from which I'll draw some status: >>> >>> Walter says use a key combination: >>> http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045724.html >>> >>> And says that customisation will be needed: >>> http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045800.html >>> >>> Then you suggest alt+space: >>> http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045807.html >>> >>> Daniel Drake says to use olpc-os-builder: >>> http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045851.html >>> >>> And you asked about the alt+space: >>> http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045857.html >>> >>> But the thread dried up on that subject because the units you received >>> had a membrane keyboard,
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
On Jun 16, 2014, at 9:05 PM, Walter Bender wrote: > On Mon, Jun 16, 2014 at 9:03 PM, John Watlington wrote: > > Walter, >You remember correctly. The hard/clicky/crunchy keyboards are not rated > for as long a lifetime as the membrane/chewy keyboards. While the membrane > keyboard design was tested to 5 million key presses, IIRC the clicky keyboard > is > only rated to 1 million key presses. (On the other hand, it takes one minute > to replace a clicky keyboard versus twenty for a membrane keyboard.) > > ..if you have a replacement keyboard... any insight into how easy it would be > to make replacement keys in the field? I would say impossible, but that would be underestimating the creativeness of our deployments. At the electrical level, the crunchy and chewy keyboards have the same contacts, so I don't expect that to be the failure mechanism. Failure should be due to the mechanical parts (as it is with the membrane keyboards). If you pull off the keycap and the guide mechanism, the key still activates when you press on the membrane or the rubber cap (which provides both the spring action and presses on the contacts) glued to it. Cheers, wad > WARNING: The clicky keyboard was not approved for use by small children > by UL. The reason is that if the keys are pulled off they present a choking > hazard. > > Cheers, > wad > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
On a related note, I was curious about deployment experiences with the new membrane design with plastic grid in between keys. Although this does help with premature peeling of keys, I've always had trouble with these keyboards - the outer edges of my fingers get in the way of a full key depress. Then again, the keys aren't designed for me, so I'm curious how these do in the field. cheers, Sameer On Mon, Jun 16, 2014 at 6:03 PM, John Watlington wrote: > > Walter, >You remember correctly. The hard/clicky/crunchy keyboards are not rated > for as long a lifetime as the membrane/chewy keyboards. While the membrane > keyboard design was tested to 5 million key presses, IIRC the clicky > keyboard is > only rated to 1 million key presses. (On the other hand, it takes one > minute > to replace a clicky keyboard versus twenty for a membrane keyboard.) > > WARNING: The clicky keyboard was not approved for use by small children > by UL. The reason is that if the keys are pulled off they present a > choking > hazard. > > Cheers, > wad > > On Jun 16, 2014, at 7:13 AM, Walter Bender wrote: > > James, > > Do we have any data re the mechanical reliability/durability/repairability > of the "hard/clicky" keyboards? We do know that although there were some > issues with membrane pealing (presumably resolved with the newer design) > there numerous ingenious local repairs such that most are still working > after 7 years. > > regards. > > -walter > > > On Mon, Jun 16, 2014 at 5:35 AM, James Cameron wrote: >> >> On Mon, Jun 16, 2014 at 01:54:19PM +0545, Basanta Shrestha wrote: >> > Hi all, >> > We are planning on ordering the next lot of XO-4s and I need some >> > suggestions on which keyboard model to choose -membrane or >> > hard/clicky one. >> >> I think it is great to seek input from the community, but don't forget >> to ask your OLPC contact for help as well. >> >> > We had membrane one for our first lot and keyboard switching was >> > very convenient on that model. One reason not to choose hard/clicky >> > one is that it doesn't have key for language switching ( correct me >> > if I am wrong) -I have one spanish hard/clicky and it doesn't have >> > that key - key 56 at >> > http://wiki.laptop.org/go/OLPC_Keyboard_layouts. >> >> Yes, that's a good reason not to choose the mechanical keyboard; you >> would have to customise your operating system build again, to add a >> key combination for keyboard language switch. If the cost of >> customising is too high, you should order membrane keyboard. I don't >> know the relative costs of the keyboards, and their replacement rates, >> but it might be factored in to your decision. >> >> You identified the lack of language switch key in this same thread on >> sugar-devel@ back in November 2013, from which I'll draw some status: >> >> Walter says use a key combination: >> http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045724.html >> >> And says that customisation will be needed: >> http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045800.html >> >> Then you suggest alt+space: >> http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045807.html >> >> Daniel Drake says to use olpc-os-builder: >> http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045851.html >> >> And you asked about the alt+space: >> http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045857.html >> >> But the thread dried up on that subject because the units you received >> had a membrane keyboard, not a mechanical keyboard. >> >> I think you need to change the xkb files, but I'm not sure. Do you >> have a mechanical keyboard you can test with? If not, you'll have to >> get someone else to do this. >> >> > Hard/Clicky on the other hard is more convenient while typing. >> > Please suggest. >> >> I don't understand why you think it is more convenient. To me the >> keyboards are equally convenient for an inexperienced child. Perhaps >> you intended to mention some characteristic? >> >> -- >> James Cameron >> http://quozl.linux.org.au/ > > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > > > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
On Mon, Jun 16, 2014 at 9:03 PM, John Watlington wrote: > > Walter, >You remember correctly. The hard/clicky/crunchy keyboards are not rated > for as long a lifetime as the membrane/chewy keyboards. While the > membrane > keyboard design was tested to 5 million key presses, IIRC the clicky > keyboard is > only rated to 1 million key presses. (On the other hand, it takes one > minute > to replace a clicky keyboard versus twenty for a membrane keyboard.) > ..if you have a replacement keyboard... any insight into how easy it would be to make replacement keys in the field? > > WARNING: The clicky keyboard was not approved for use by small children > by UL. The reason is that if the keys are pulled off they present a > choking > hazard. > > Cheers, > wad > > On Jun 16, 2014, at 7:13 AM, Walter Bender wrote: > > James, > > Do we have any data re the mechanical reliability/durability/repairability > of the "hard/clicky" keyboards? We do know that although there were some > issues with membrane pealing (presumably resolved with the newer design) > there numerous ingenious local repairs such that most are still working > after 7 years. > > regards. > > -walter > > > On Mon, Jun 16, 2014 at 5:35 AM, James Cameron wrote: > >> On Mon, Jun 16, 2014 at 01:54:19PM +0545, Basanta Shrestha wrote: >> > Hi all, >> > We are planning on ordering the next lot of XO-4s and I need some >> > suggestions on which keyboard model to choose -membrane or >> > hard/clicky one. >> >> I think it is great to seek input from the community, but don't forget >> to ask your OLPC contact for help as well. >> >> > We had membrane one for our first lot and keyboard switching was >> > very convenient on that model. One reason not to choose hard/clicky >> > one is that it doesn't have key for language switching ( correct me >> > if I am wrong) -I have one spanish hard/clicky and it doesn't have >> > that key - key 56 at >> > http://wiki.laptop.org/go/OLPC_Keyboard_layouts. >> >> Yes, that's a good reason not to choose the mechanical keyboard; you >> would have to customise your operating system build again, to add a >> key combination for keyboard language switch. If the cost of >> customising is too high, you should order membrane keyboard. I don't >> know the relative costs of the keyboards, and their replacement rates, >> but it might be factored in to your decision. >> >> You identified the lack of language switch key in this same thread on >> sugar-devel@ back in November 2013, from which I'll draw some status: >> >> Walter says use a key combination: >> http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045724.html >> >> And says that customisation will be needed: >> http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045800.html >> >> Then you suggest alt+space: >> http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045807.html >> >> Daniel Drake says to use olpc-os-builder: >> http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045851.html >> >> And you asked about the alt+space: >> http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045857.html >> >> But the thread dried up on that subject because the units you received >> had a membrane keyboard, not a mechanical keyboard. >> >> I think you need to change the xkb files, but I'm not sure. Do you >> have a mechanical keyboard you can test with? If not, you'll have to >> get someone else to do this. >> >> > Hard/Clicky on the other hard is more convenient while typing. >> > Please suggest. >> >> I don't understand why you think it is more convenient. To me the >> keyboards are equally convenient for an inexperienced child. Perhaps >> you intended to mention some characteristic? >> >> -- >> James Cameron >> http://quozl.linux.org.au/ >> > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/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] seeking help to enable nepali keyboard input for XO-4
Walter, You remember correctly. The hard/clicky/crunchy keyboards are not rated for as long a lifetime as the membrane/chewy keyboards. While the membrane keyboard design was tested to 5 million key presses, IIRC the clicky keyboard is only rated to 1 million key presses. (On the other hand, it takes one minute to replace a clicky keyboard versus twenty for a membrane keyboard.) WARNING: The clicky keyboard was not approved for use by small children by UL. The reason is that if the keys are pulled off they present a choking hazard. Cheers, wad On Jun 16, 2014, at 7:13 AM, Walter Bender wrote: > James, > > Do we have any data re the mechanical reliability/durability/repairability of > the "hard/clicky" keyboards? We do know that although there were some issues > with membrane pealing (presumably resolved with the newer design) there > numerous ingenious local repairs such that most are still working after 7 > years. > > regards. > > -walter > > > On Mon, Jun 16, 2014 at 5:35 AM, James Cameron wrote: > On Mon, Jun 16, 2014 at 01:54:19PM +0545, Basanta Shrestha wrote: > > Hi all, > > We are planning on ordering the next lot of XO-4s and I need some > > suggestions on which keyboard model to choose -membrane or > > hard/clicky one. > > I think it is great to seek input from the community, but don't forget > to ask your OLPC contact for help as well. > > > We had membrane one for our first lot and keyboard switching was > > very convenient on that model. One reason not to choose hard/clicky > > one is that it doesn't have key for language switching ( correct me > > if I am wrong) -I have one spanish hard/clicky and it doesn't have > > that key - key 56 at > > http://wiki.laptop.org/go/OLPC_Keyboard_layouts. > > Yes, that's a good reason not to choose the mechanical keyboard; you > would have to customise your operating system build again, to add a > key combination for keyboard language switch. If the cost of > customising is too high, you should order membrane keyboard. I don't > know the relative costs of the keyboards, and their replacement rates, > but it might be factored in to your decision. > > You identified the lack of language switch key in this same thread on > sugar-devel@ back in November 2013, from which I'll draw some status: > > Walter says use a key combination: > http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045724.html > > And says that customisation will be needed: > http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045800.html > > Then you suggest alt+space: > http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045807.html > > Daniel Drake says to use olpc-os-builder: > http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045851.html > > And you asked about the alt+space: > http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045857.html > > But the thread dried up on that subject because the units you received > had a membrane keyboard, not a mechanical keyboard. > > I think you need to change the xkb files, but I'm not sure. Do you > have a mechanical keyboard you can test with? If not, you'll have to > get someone else to do this. > > > Hard/Clicky on the other hard is more convenient while typing. > > Please suggest. > > I don't understand why you think it is more convenient. To me the > keyboards are equally convenient for an inexperienced child. Perhaps > you intended to mention some characteristic? > > -- > James Cameron > http://quozl.linux.org.au/ > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
I have no such data, sorry. On Mon, Jun 16, 2014 at 07:13:48AM -0400, Walter Bender wrote: > James, > > Do we have any data re the mechanical > reliability/durability/repairability of the "hard/clicky" keyboards? > We do know that although there were some issues with membrane > pealing (presumably resolved with the newer design) there numerous > ingenious local repairs such that most are still working after 7 > years. > > regards. > > -walter -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
James, Do we have any data re the mechanical reliability/durability/repairability of the "hard/clicky" keyboards? We do know that although there were some issues with membrane pealing (presumably resolved with the newer design) there numerous ingenious local repairs such that most are still working after 7 years. regards. -walter On Mon, Jun 16, 2014 at 5:35 AM, James Cameron wrote: > On Mon, Jun 16, 2014 at 01:54:19PM +0545, Basanta Shrestha wrote: > > Hi all, > > We are planning on ordering the next lot of XO-4s and I need some > > suggestions on which keyboard model to choose -membrane or > > hard/clicky one. > > I think it is great to seek input from the community, but don't forget > to ask your OLPC contact for help as well. > > > We had membrane one for our first lot and keyboard switching was > > very convenient on that model. One reason not to choose hard/clicky > > one is that it doesn't have key for language switching ( correct me > > if I am wrong) -I have one spanish hard/clicky and it doesn't have > > that key - key 56 at > > http://wiki.laptop.org/go/OLPC_Keyboard_layouts. > > Yes, that's a good reason not to choose the mechanical keyboard; you > would have to customise your operating system build again, to add a > key combination for keyboard language switch. If the cost of > customising is too high, you should order membrane keyboard. I don't > know the relative costs of the keyboards, and their replacement rates, > but it might be factored in to your decision. > > You identified the lack of language switch key in this same thread on > sugar-devel@ back in November 2013, from which I'll draw some status: > > Walter says use a key combination: > http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045724.html > > And says that customisation will be needed: > http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045800.html > > Then you suggest alt+space: > http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045807.html > > Daniel Drake says to use olpc-os-builder: > http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045851.html > > And you asked about the alt+space: > http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045857.html > > But the thread dried up on that subject because the units you received > had a membrane keyboard, not a mechanical keyboard. > > I think you need to change the xkb files, but I'm not sure. Do you > have a mechanical keyboard you can test with? If not, you'll have to > get someone else to do this. > > > Hard/Clicky on the other hard is more convenient while typing. > > Please suggest. > > I don't understand why you think it is more convenient. To me the > keyboards are equally convenient for an inexperienced child. Perhaps > you intended to mention some characteristic? > > -- > James Cameron > http://quozl.linux.org.au/ > -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
On Mon, Jun 16, 2014 at 01:54:19PM +0545, Basanta Shrestha wrote: > Hi all, > We are planning on ordering the next lot of XO-4s and I need some > suggestions on which keyboard model to choose -membrane or > hard/clicky one. I think it is great to seek input from the community, but don't forget to ask your OLPC contact for help as well. > We had membrane one for our first lot and keyboard switching was > very convenient on that model. One reason not to choose hard/clicky > one is that it doesn't have key for language switching ( correct me > if I am wrong) -I have one spanish hard/clicky and it doesn't have > that key - key 56 at > http://wiki.laptop.org/go/OLPC_Keyboard_layouts. Yes, that's a good reason not to choose the mechanical keyboard; you would have to customise your operating system build again, to add a key combination for keyboard language switch. If the cost of customising is too high, you should order membrane keyboard. I don't know the relative costs of the keyboards, and their replacement rates, but it might be factored in to your decision. You identified the lack of language switch key in this same thread on sugar-devel@ back in November 2013, from which I'll draw some status: Walter says use a key combination: http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045724.html And says that customisation will be needed: http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045800.html Then you suggest alt+space: http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045807.html Daniel Drake says to use olpc-os-builder: http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045851.html And you asked about the alt+space: http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045857.html But the thread dried up on that subject because the units you received had a membrane keyboard, not a mechanical keyboard. I think you need to change the xkb files, but I'm not sure. Do you have a mechanical keyboard you can test with? If not, you'll have to get someone else to do this. > Hard/Clicky on the other hard is more convenient while typing. > Please suggest. I don't understand why you think it is more convenient. To me the keyboards are equally convenient for an inexperienced child. Perhaps you intended to mention some characteristic? -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
Hi all, We are planning on ordering the next lot of XO-4s and I need some suggestions on which keyboard model to choose -membrane or hard/clicky one. We had membrane one for our first lot and keyboard switching was very convenient on that model. One reason not to choose hard/clicky one is that it doesn't have key for language switching ( correct me if I am wrong) -I have one spanish hard/clicky and it doesn't have that key - key 56 at http://wiki.laptop.org/go/OLPC_Keyboard_layouts. Hard/Clicky on the other hard is more convenient while typing. Please suggest. -Basanta On Wed, Nov 13, 2013 at 10:01 PM, Daniel Drake wrote: > On Tue, Nov 12, 2013 at 10:14 PM, Basanta Shrestha > wrote: >> Amazingly changing the manufacturing data didn't do the job but changing >> /etc/sysconfig/keyboard did. Wow! Now I have Nepali input system. Thank you >> all. >> >> Now I need to find a place to change default locale to ne_NP, so that the >> default interface is in Nepali. There is an option to do this in >> manufacturing data but it would be better if it can be done using file. > > If all you want to do is change default keyboard and language, you can > avoid doing any manufacturing data changes, and just do the [base] > olpc-os-builder configuration I mentioned in my last email. > > Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] How to change onscreen keyboard layout.
On Tue, Apr 29, 2014 at 6:21 PM, Martin Abente wrote: > As James mentioned, the first option is to provide a ne.xml layout file in > /usr/share/maliit/plugins/languages/ (ie., you could use es_us.xml as model, > or copy it entirely). > > The second option, IIRC, is to force maliit to always use a specific layout > (from the ones that are available) with a configuration file [1,2]. Let me > know if you try this option, so we can update [3], as I lost the fpasted > example (my bad). > > Refs: > 1. http://dev.laptop.org/attachment/ticket/12166/server.conf > 2. http://forum.xda-developers.com/showthread.php?p=44898616&postcount=33 > 3. http://dev.laptop.org/ticket/12750 > > HI Martin, Using option 1, I could choose which layout to use. I am using server.conf instead to use "en_us".xml now. This is how my server.conf look like now. [maliit] onscreen\active=libmaliit-keyboard-plugin.so:en_us pluginsettings\libmaliit-keyboard-plugin.so\current_style=olpc-xo onscreen\enabled=libmaliit-keyboard-plugin.so:en_us Thank you > On Tue, Apr 29, 2014 at 7:34 AM, Gonzalo Odiard > wrote: >> >> A fix for the arabic keyboard problem is in the rpm >> >> http://harvest.one-education.org/public/au1b-updates/RPMS/maliit-plugins-0.94.2-2.olpcau.fc18.armv7hl.rpm >> Accidentally was not included in the last 0.100 images, if you have the >> problem try installing it. >> >> Gonzalo >> >> >> On Tue, Apr 29, 2014 at 5:56 AM, James Cameron wrote: >>> >>> Arabic onscreen keyboard despite language selected ... this is a known >>> problem. >>> >>> Is there an ne_np.xml or ne.xml language file in >>> /usr/share/maliit/plugins/languages/ directory? >>> >>> If not, you have reproduced http://dev.laptop.org/ticket/12750 and you >>> will have to add a file to maliit-plugins upstream, or in your build. >>> >>> @tch, where's that paste? >>> >>> -- >>> James Cameron >>> http://quozl.linux.org.au/ >>> ___ >>> Sugar-devel mailing list >>> sugar-de...@lists.sugarlabs.org >>> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> >> >> >> -- >> Gonzalo Odiard >> >> SugarLabs - Software for children learning >> >> ___ >> Sugar-devel mailing list >> sugar-de...@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> > -- Basanta Shrestha Network Engineer Open Learning Exchange (OLE) Nepal Tel: +977.1.551, 5520075 Ext. 303 Cell: +977.9818 605110 http://www.olenepal.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: How to change onscreen keyboard layout.
On Tue, Apr 29, 2014 at 2:41 PM, James Cameron wrote: > Arabic onscreen keyboard despite language selected ... this is a known > problem. > > Is there an ne_np.xml or ne.xml language file in > /usr/share/maliit/plugins/languages/ directory? There was no ne.xml so I made of copy of en_US.xml as ne.xml and it works. So now I have english layout which is good but I wish I had some script that would generate ne.xml from /usr/share/X11/xkb/symbols/np > > If not, you have reproduced http://dev.laptop.org/ticket/12750 and you > will have to add a file to maliit-plugins upstream, or in your build. Sure I need to do it once I have prepared that file. Thank you . > > @tch, where's that paste? > > -- > James Cameron > http://quozl.linux.org.au/ -- Basanta Shrestha Network Engineer Open Learning Exchange (OLE) Nepal Tel: +977.1.551, 5520075 Ext. 303 Cell: +977.9818 605110 http://www.olenepal.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] How to change onscreen keyboard layout.
The package was already installed. On Tue, Apr 29, 2014 at 5:19 PM, Gonzalo Odiard wrote: > A fix for the arabic keyboard problem is in the rpm > http://harvest.one-education.org/public/au1b-updates/RPMS/maliit-plugins-0.94.2-2.olpcau.fc18.armv7hl.rpm > Accidentally was not included in the last 0.100 images, if you have the > problem try installing it. > > Gonzalo > > > On Tue, Apr 29, 2014 at 5:56 AM, James Cameron wrote: >> >> Arabic onscreen keyboard despite language selected ... this is a known >> problem. >> >> Is there an ne_np.xml or ne.xml language file in >> /usr/share/maliit/plugins/languages/ directory? >> >> If not, you have reproduced http://dev.laptop.org/ticket/12750 and you >> will have to add a file to maliit-plugins upstream, or in your build. >> >> @tch, where's that paste? >> >> -- >> James Cameron >> http://quozl.linux.org.au/ >> ___ >> Sugar-devel mailing list >> sugar-de...@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel > > > > > -- > Gonzalo Odiard > > SugarLabs - Software for children learning -- Basanta Shrestha Network Engineer Open Learning Exchange (OLE) Nepal Tel: +977.1.551, 5520075 Ext. 303 Cell: +977.9818 605110 http://www.olenepal.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] How to change onscreen keyboard layout.
As James mentioned, the first option is to provide a ne.xml layout file in /usr/share/maliit/plugins/languages/ (ie., you could use es_us.xml as model, or copy it entirely). The second option, IIRC, is to force maliit to always use a specific layout (from the ones that are available) with a configuration file [1,2]. Let me know if you try this option, so we can update [3], as I lost the fpasted example (my bad). Refs: 1. http://dev.laptop.org/attachment/ticket/12166/server.conf 2. http://forum.xda-developers.com/showthread.php?p=44898616&postcount=33 3. http://dev.laptop.org/ticket/12750 On Tue, Apr 29, 2014 at 7:34 AM, Gonzalo Odiard wrote: > A fix for the arabic keyboard problem is in the rpm > > http://harvest.one-education.org/public/au1b-updates/RPMS/maliit-plugins-0.94.2-2.olpcau.fc18.armv7hl.rpm > Accidentally was not included in the last 0.100 images, if you have the > problem try installing it. > > Gonzalo > > > On Tue, Apr 29, 2014 at 5:56 AM, James Cameron wrote: > >> Arabic onscreen keyboard despite language selected ... this is a known >> problem. >> >> Is there an ne_np.xml or ne.xml language file in >> /usr/share/maliit/plugins/languages/ directory? >> >> If not, you have reproduced http://dev.laptop.org/ticket/12750 and you >> will have to add a file to maliit-plugins upstream, or in your build. >> >> @tch, where's that paste? >> >> -- >> James Cameron >> http://quozl.linux.org.au/ >> ___ >> Sugar-devel mailing list >> sugar-de...@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> > > > > -- > Gonzalo Odiard > > SugarLabs - Software for children learning > > ___ > 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] How to change onscreen keyboard layout.
A fix for the arabic keyboard problem is in the rpm http://harvest.one-education.org/public/au1b-updates/RPMS/maliit-plugins-0.94.2-2.olpcau.fc18.armv7hl.rpm Accidentally was not included in the last 0.100 images, if you have the problem try installing it. Gonzalo On Tue, Apr 29, 2014 at 5:56 AM, James Cameron wrote: > Arabic onscreen keyboard despite language selected ... this is a known > problem. > > Is there an ne_np.xml or ne.xml language file in > /usr/share/maliit/plugins/languages/ directory? > > If not, you have reproduced http://dev.laptop.org/ticket/12750 and you > will have to add a file to maliit-plugins upstream, or in your build. > > @tch, where's that paste? > > -- > James Cameron > http://quozl.linux.org.au/ > ___ > Sugar-devel mailing list > sugar-de...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Gonzalo Odiard SugarLabs - Software for children learning ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: How to change onscreen keyboard layout.
Arabic onscreen keyboard despite language selected ... this is a known problem. Is there an ne_np.xml or ne.xml language file in /usr/share/maliit/plugins/languages/ directory? If not, you have reproduced http://dev.laptop.org/ticket/12750 and you will have to add a file to maliit-plugins upstream, or in your build. @tch, where's that paste? -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
How to change onscreen keyboard layout.
Hi Everyone, On my X0-4 with 13.2.0, when I flip the screen to book reader mode, I get some arabic keyboard layout. The only layout setting I have on my oob configuration file is under olpc-os-13.2.0-xo4.ini as below: [base] default_kbd_model=olpc default_kbd_layout=us,np default_kbd_variant=olpc2,olpc default_language=ne_NP.UTF-8 - where 'ne_NP' = nepali and Nepal 'np' is our layout which is devanagari. Thank you Basanta ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Using a new keyboard layout for XO4
Yeah it works. Now I have Nepali romanized keyboard layout in XO-4. Thanks
a lot Daniel, you rock !
Regards,
Basanta
On Sat, Dec 14, 2013 at 10:36 PM, Daniel Drake wrote:
> Hi Basanta,
>
> On Thu, Nov 21, 2013 at 4:27 AM, Basanta Shrestha
> wrote:
> > Dear all,
> > We are planing on using a different keyboard layout for XO4. The new
> layout we think is phonetically based and easier for children. I simply
> switched the /usr/share/X11/symbols/np file with a new one but did not
> work. I guess there are some other works that needs to be done before we
> can use this file. Can you suggest what needs to be done?
>
> Yeah, it's not quite that simple. You need to leave the interaction
> with the OLPC mode/variant in place. Add the following lines to the
> end of the file:
>
> partial alphanumeric_keys
> xkb_symbols "olpc" {
> include "np"
> include "group(olpc)"
> };
>
> Now it should work.
>
> Daniel
>
--
Basanta Shrestha
Network Engineer
Open Learning Exchange (OLE) Nepal
Tel: +977.1.551, 5520075 Ext. 303
Cell: +977.9818 605110
http://www.olenepal.org
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: Using a new keyboard layout for XO4
Hi Basanta,
On Thu, Nov 21, 2013 at 4:27 AM, Basanta Shrestha
wrote:
> Dear all,
> We are planing on using a different keyboard layout for XO4. The new layout
> we think is phonetically based and easier for children. I simply switched the
> /usr/share/X11/symbols/np file with a new one but did not work. I guess there
> are some other works that needs to be done before we can use this file. Can
> you suggest what needs to be done?
Yeah, it's not quite that simple. You need to leave the interaction
with the OLPC mode/variant in place. Add the following lines to the
end of the file:
partial alphanumeric_keys
xkb_symbols "olpc" {
include "np"
include "group(olpc)"
};
Now it should work.
Daniel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Using a new keyboard layout for XO4
On 21/11/13 23:27, Basanta Shrestha wrote: Dear all, We are planing on using a different keyboard layout for XO4. The new layout we think is phonetically based and easier for children. I simply switched the /usr/share/X11/symbols/np file with a new one but did not work. I guess there are some other works that needs to be done before we can use this file. Can you suggest what needs to be done? The layout I want to use is http://nepalinux.org/input/ne We did this for Maori. We used James's Tiny Core Linux based customization stick. See http://carrott.org/git/mktinycorexo_nz.git/blob/HEAD:/scripts/asroot for the script that is run _before the first boot of the laptop_ to insert the Maori keyboard, change the keyboard configuration and update the Maori translations. The Maori keyboard is called mi. You may also be interested in http://carrott.org/git/mktinycorexo_nz.git/blob/HEAD:/scripts/asolpc which changes the user's locale preferences. See http://carrott.org/git/mktinycorexo_nz.git/blob/HEAD:/mknzusb for the script which makes the customization flash drive. Be sure to read and understand it before running as it will wipe your disk and you will be sad if it wipes the wrong one! Clone the whole repo if you like, but my server's bandwidth is not great and there is about 50MB in there, so be patient. I should probably refactor it to use a submodule to get tinycorexo. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Using a new keyboard layout for XO4
Dear all, We are planing on using a different keyboard layout for XO4. The new layout we think is phonetically based and easier for children. I simply switched the /usr/share/X11/symbols/np file with a new one but did not work. I guess there are some other works that needs to be done before we can use this file. Can you suggest what needs to be done? The layout I want to use is http://nepalinux.org/input/ne -basanta ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
On Tue, Nov 12, 2013 at 10:14 PM, Basanta Shrestha wrote: > Amazingly changing the manufacturing data didn't do the job but changing > /etc/sysconfig/keyboard did. Wow! Now I have Nepali input system. Thank you > all. > > Now I need to find a place to change default locale to ne_NP, so that the > default interface is in Nepali. There is an option to do this in > manufacturing data but it would be better if it can be done using file. If all you want to do is change default keyboard and language, you can avoid doing any manufacturing data changes, and just do the [base] olpc-os-builder configuration I mentioned in my last email. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
On Wed, Nov 13, 2013 at 12:12 AM, Paul Fox wrote: > basanta wrote: > > Amazingly changing the manufacturing data didn't do the job but changing > > /etc/sysconfig/keyboard did. Wow! Now I have Nepali input system. Thank you > > all. > > i believe /etc/sysconfig/keyboard is created on first boot, using > information gleaned from manufacturing data. see > /usr/sbin/olpc-configure for details. this would explain why changing > the manufacturing tags didn't help -- they've already been consulted, > on your test laptop. > > paul > Yes. This means that if you reflash, it will use the keyboard specified in the manufacturing data, so you probably want to set it correctly. regards. -walter > > > > Now I need to find a place to change default locale to ne_NP, so that the > > default interface is in Nepali. There is an option to do this in > > manufacturing data but it would be better if it can be done using file. > > -basanta > > > > > > On Tue, Nov 12, 2013 at 6:22 PM, Walter Bender > wrote: > > > > > Makes things much easier. Now you just have to change the > > > manufacruring data as was suggested earlier, but you don't need to > > > modify the xkb symbol table. > > > > > > Good luck. > > > > > > -walter > > > > > > On Tue, Nov 12, 2013 at 4:24 AM, James Cameron wrote: > > > > Okay, that is consistent with the data we have for the SKU311 > > > > mentioned by Samuel on 8th November. > > > > > > > > The divide and multiply key is the language switch key. > > > > > > > > On Tue, Nov 12, 2013 at 01:36:35PM +0545, Basanta Shrestha wrote: > > > >> The laptops(XO-4) have arrived but it turns out the keyboard is the > > > other one > > > >> the rubber one (Improved Membrane Keyboard ?). > > > >> -Basanta > > > >> > > > >> > > > >> On Tue, Nov 12, 2013 at 10:36 AM, Basanta Shrestha < > > > >> basanta.shres...@olenepal.org> wrote: > > > >> > > > >> D > > > >> > > > >> > > > >> On Mon, Nov 11, 2013 at 11:23 PM, Daniel Drake > > > wrote: > > > >> > > > >> On Sun, Nov 10, 2013 at 5:18 PM, James Cameron < > > > qu...@laptop.org> > > > >> wrote: > > > >> > If you need to scale up this change to many laptops, contact > > > >> > reu...@laptop.org or myself. I must know the SKU number. > > > >> > > > >> In the particular case of changing language/keyboard defaults > > > as we > > > >> are discussing, instead of changing manufacturing data I would > > > >> recommend doing it via olpc-os-builder, configuration for > > > [base], see > > > >> > > > http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/base/ > > > >> README#n46 > > > >> > > > >> > > > >> Doing it via olpc-os-builder would be easier especially when we be > > > having > > > >> more than 200 laptops to work on. This way we won't have to deal > > > with each > > > >> and every laptop. So the lines I would have to add would be > > > following : > > > >> > > > >> [base] > > > >> default_language=us > > > >> > > > >> default_kbd_model=us > > > >> default_kbd_layout=us > > > >> default_kbd_variant=np > > > >> > > > >> > > > >> But where do we set the key combination to switch between default > > > and > > > >> nepali. I would like to assign alt+space or alt+shift as > > > combination. > > > >> > > > >> Note: We need to set default layout to english. Nepali input is > only > > > >> required for few activities in Epaath and for typing document in > > > Nepali. > > > >> > > > >> -basanta > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> -- > > > >> Basanta Shrestha > > > >> Network Engineer > > > >> Open Learning Exchange (OLE) Nepal > > > >> Tel: +977.1.551, 5520075 Ext. 303 > > > >> Cell: +977.9818 605110 > > > >> http://www.olenepal.org > > > > > > > > -- > > > > James Cameron > > > > http://quozl.linux.org.au/ > > > > > > > > > > > > -- > > > Walter Bender > > > Sugar Labs > > > http://www.sugarlabs.org > > > > > > > > > > > -- > > Basanta Shrestha > > Network Engineer > > Open Learning Exchange (OLE) Nepal > > Tel: +977.1.551, 5520075 Ext. 303 > > Cell: +977.9818 605110 > > http://www.olenepal.org > > part 2 text/plain 153 > > ___ > > Sugar-devel mailing list > > sugar-de...@lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > > =- > paul fox, p...@laptop.org -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
basanta wrote: > Amazingly changing the manufacturing data didn't do the job but changing > /etc/sysconfig/keyboard did. Wow! Now I have Nepali input system. Thank you > all. i believe /etc/sysconfig/keyboard is created on first boot, using information gleaned from manufacturing data. see /usr/sbin/olpc-configure for details. this would explain why changing the manufacturing tags didn't help -- they've already been consulted, on your test laptop. paul > > Now I need to find a place to change default locale to ne_NP, so that the > default interface is in Nepali. There is an option to do this in > manufacturing data but it would be better if it can be done using file. > -basanta > > > On Tue, Nov 12, 2013 at 6:22 PM, Walter Bender > wrote: > > > Makes things much easier. Now you just have to change the > > manufacruring data as was suggested earlier, but you don't need to > > modify the xkb symbol table. > > > > Good luck. > > > > -walter > > > > On Tue, Nov 12, 2013 at 4:24 AM, James Cameron wrote: > > > Okay, that is consistent with the data we have for the SKU311 > > > mentioned by Samuel on 8th November. > > > > > > The divide and multiply key is the language switch key. > > > > > > On Tue, Nov 12, 2013 at 01:36:35PM +0545, Basanta Shrestha wrote: > > >> The laptops(XO-4) have arrived but it turns out the keyboard is the > > other one > > >> the rubber one (Improved Membrane Keyboard ?). > > >> -Basanta > > >> > > >> > > >> On Tue, Nov 12, 2013 at 10:36 AM, Basanta Shrestha < > > >> basanta.shres...@olenepal.org> wrote: > > >> > > >> D > > >> > > >> > > >> On Mon, Nov 11, 2013 at 11:23 PM, Daniel Drake > > wrote: > > >> > > >> On Sun, Nov 10, 2013 at 5:18 PM, James Cameron < > > qu...@laptop.org> > > >> wrote: > > >> > If you need to scale up this change to many laptops, contact > > >> > reu...@laptop.org or myself. I must know the SKU number. > > >> > > >> In the particular case of changing language/keyboard defaults > > as we > > >> are discussing, instead of changing manufacturing data I would > > >> recommend doing it via olpc-os-builder, configuration for > > [base], see > > >> > > http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/base/ > > >> README#n46 > > >> > > >> > > >> Doing it via olpc-os-builder would be easier especially when we be > > having > > >> more than 200 laptops to work on. This way we won't have to deal > > with each > > >> and every laptop. So the lines I would have to add would be > > following : > > >> > > >> [base] > > >> default_language=us > > >> > > >> default_kbd_model=us > > >> default_kbd_layout=us > > >> default_kbd_variant=np > > >> > > >> > > >> But where do we set the key combination to switch between default > > and > > >> nepali. I would like to assign alt+space or alt+shift as > > combination. > > >> > > >> Note: We need to set default layout to english. Nepali input is only > > >> required for few activities in Epaath and for typing document in > > Nepali. > > >> > > >> -basanta > > >> > > >> > > >> > > >> > > >> > > >> > > >> -- > > >> Basanta Shrestha > > >> Network Engineer > > >> Open Learning Exchange (OLE) Nepal > > >> Tel: +977.1.551, 5520075 Ext. 303 > > >> Cell: +977.9818 605110 > > >> http://www.olenepal.org > > > > > > -- > > > James Cameron > > > http://quozl.linux.org.au/ > > > > > > > > -- > > Walter Bender > > Sugar Labs > > http://www.sugarlabs.org > > > > > > -- > Basanta Shrestha > Network Engineer > Open Learning Exchange (OLE) Nepal > Tel: +977.1.551, 5520075 Ext. 303 > Cell: +977.9818 605110 > http://www.olenepal.org > part 2 text/plain 153 > ___ > Sugar-devel mailing list > sugar-de...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
Amazingly changing the manufacturing data didn't do the job but changing /etc/sysconfig/keyboard did. Wow! Now I have Nepali input system. Thank you all. Now I need to find a place to change default locale to ne_NP, so that the default interface is in Nepali. There is an option to do this in manufacturing data but it would be better if it can be done using file. -basanta On Tue, Nov 12, 2013 at 6:22 PM, Walter Bender wrote: > Makes things much easier. Now you just have to change the > manufacruring data as was suggested earlier, but you don't need to > modify the xkb symbol table. > > Good luck. > > -walter > > On Tue, Nov 12, 2013 at 4:24 AM, James Cameron wrote: > > Okay, that is consistent with the data we have for the SKU311 > > mentioned by Samuel on 8th November. > > > > The divide and multiply key is the language switch key. > > > > On Tue, Nov 12, 2013 at 01:36:35PM +0545, Basanta Shrestha wrote: > >> The laptops(XO-4) have arrived but it turns out the keyboard is the > other one > >> the rubber one (Improved Membrane Keyboard ?). > >> -Basanta > >> > >> > >> On Tue, Nov 12, 2013 at 10:36 AM, Basanta Shrestha < > >> basanta.shres...@olenepal.org> wrote: > >> > >> D > >> > >> > >> On Mon, Nov 11, 2013 at 11:23 PM, Daniel Drake > wrote: > >> > >> On Sun, Nov 10, 2013 at 5:18 PM, James Cameron < > qu...@laptop.org> > >> wrote: > >> > If you need to scale up this change to many laptops, contact > >> > reu...@laptop.org or myself. I must know the SKU number. > >> > >> In the particular case of changing language/keyboard defaults > as we > >> are discussing, instead of changing manufacturing data I would > >> recommend doing it via olpc-os-builder, configuration for > [base], see > >> > http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/base/ > >> README#n46 > >> > >> > >> Doing it via olpc-os-builder would be easier especially when we be > having > >> more than 200 laptops to work on. This way we won't have to deal > with each > >> and every laptop. So the lines I would have to add would be > following : > >> > >> [base] > >> default_language=us > >> > >> default_kbd_model=us > >> default_kbd_layout=us > >> default_kbd_variant=np > >> > >> > >> But where do we set the key combination to switch between default > and > >> nepali. I would like to assign alt+space or alt+shift as > combination. > >> > >> Note: We need to set default layout to english. Nepali input is only > >> required for few activities in Epaath and for typing document in > Nepali. > >> > >> -basanta > >> > >> > >> > >> > >> > >> > >> -- > >> Basanta Shrestha > >> Network Engineer > >> Open Learning Exchange (OLE) Nepal > >> Tel: +977.1.551, 5520075 Ext. 303 > >> Cell: +977.9818 605110 > >> http://www.olenepal.org > > > > -- > > James Cameron > > http://quozl.linux.org.au/ > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > -- Basanta Shrestha Network Engineer Open Learning Exchange (OLE) Nepal Tel: +977.1.551, 5520075 Ext. 303 Cell: +977.9818 605110 http://www.olenepal.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
Makes things much easier. Now you just have to change the manufacruring data as was suggested earlier, but you don't need to modify the xkb symbol table. Good luck. -walter On Tue, Nov 12, 2013 at 4:24 AM, James Cameron wrote: > Okay, that is consistent with the data we have for the SKU311 > mentioned by Samuel on 8th November. > > The divide and multiply key is the language switch key. > > On Tue, Nov 12, 2013 at 01:36:35PM +0545, Basanta Shrestha wrote: >> The laptops(XO-4) have arrived but it turns out the keyboard is the other one >> the rubber one (Improved Membrane Keyboard ?). >> -Basanta >> >> >> On Tue, Nov 12, 2013 at 10:36 AM, Basanta Shrestha < >> basanta.shres...@olenepal.org> wrote: >> >> D >> >> >> On Mon, Nov 11, 2013 at 11:23 PM, Daniel Drake wrote: >> >> On Sun, Nov 10, 2013 at 5:18 PM, James Cameron >> wrote: >> > If you need to scale up this change to many laptops, contact >> > reu...@laptop.org or myself. I must know the SKU number. >> >> In the particular case of changing language/keyboard defaults as we >> are discussing, instead of changing manufacturing data I would >> recommend doing it via olpc-os-builder, configuration for [base], see >> http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/base/ >> README#n46 >> >> >> Doing it via olpc-os-builder would be easier especially when we be having >> more than 200 laptops to work on. This way we won't have to deal with >> each >> and every laptop. So the lines I would have to add would be following : >> >> [base] >> default_language=us >> >> default_kbd_model=us >> default_kbd_layout=us >> default_kbd_variant=np >> >> >> But where do we set the key combination to switch between default and >> nepali. I would like to assign alt+space or alt+shift as combination. >> >> Note: We need to set default layout to english. Nepali input is only >> required for few activities in Epaath and for typing document in Nepali. >> >> -basanta >> >> >> >> >> >> >> -- >> Basanta Shrestha >> Network Engineer >> Open Learning Exchange (OLE) Nepal >> Tel: +977.1.551, 5520075 Ext. 303 >> Cell: +977.9818 605110 >> http://www.olenepal.org > > -- > James Cameron > http://quozl.linux.org.au/ -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
Okay, that is consistent with the data we have for the SKU311 mentioned by Samuel on 8th November. The divide and multiply key is the language switch key. On Tue, Nov 12, 2013 at 01:36:35PM +0545, Basanta Shrestha wrote: > The laptops(XO-4) have arrived but it turns out the keyboard is the other one > the rubber one (Improved Membrane Keyboard ?). > -Basanta > > > On Tue, Nov 12, 2013 at 10:36 AM, Basanta Shrestha < > basanta.shres...@olenepal.org> wrote: > > D > > > On Mon, Nov 11, 2013 at 11:23 PM, Daniel Drake wrote: > > On Sun, Nov 10, 2013 at 5:18 PM, James Cameron > wrote: > > If you need to scale up this change to many laptops, contact > > reu...@laptop.org or myself. I must know the SKU number. > > In the particular case of changing language/keyboard defaults as we > are discussing, instead of changing manufacturing data I would > recommend doing it via olpc-os-builder, configuration for [base], see > http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/base/ > README#n46 > > > Doing it via olpc-os-builder would be easier especially when we be having > more than 200 laptops to work on. This way we won't have to deal with each > and every laptop. So the lines I would have to add would be following : > > [base] > default_language=us > > default_kbd_model=us > default_kbd_layout=us > default_kbd_variant=np > > > But where do we set the key combination to switch between default and > nepali. I would like to assign alt+space or alt+shift as combination. > > Note: We need to set default layout to english. Nepali input is only > required for few activities in Epaath and for typing document in Nepali. > > -basanta > > > > > > > -- > Basanta Shrestha > Network Engineer > Open Learning Exchange (OLE) Nepal > Tel: +977.1.551, 5520075 Ext. 303 > Cell: +977.9818 605110 > http://www.olenepal.org -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
The laptops(XO-4) have arrived but it turns out the keyboard is the other one the rubber one (Improved Membrane Keyboard ?). -Basanta On Tue, Nov 12, 2013 at 10:36 AM, Basanta Shrestha < basanta.shres...@olenepal.org> wrote: > D > > > On Mon, Nov 11, 2013 at 11:23 PM, Daniel Drake wrote: > >> On Sun, Nov 10, 2013 at 5:18 PM, James Cameron wrote: >> > If you need to scale up this change to many laptops, contact >> > reu...@laptop.org or myself. I must know the SKU number. >> >> In the particular case of changing language/keyboard defaults as we >> are discussing, instead of changing manufacturing data I would >> recommend doing it via olpc-os-builder, configuration for [base], see >> >> http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/base/README#n46 > > > Doing it via olpc-os-builder would be easier especially when we be having > more than 200 laptops to work on. This way we won't have to deal with each > and every laptop. So the lines I would have to add would be following : > > [base] > default_language=us > > default_kbd_model=us > default_kbd_layout=us > default_kbd_variant=np > > > But where do we set the key combination to switch between default and > nepali. I would like to assign alt+space or alt+shift as combination. > > Note: We need to set default layout to english. Nepali input is only > required for few activities in Epaath and for typing document in Nepali. > > -basanta > > > -- Basanta Shrestha Network Engineer Open Learning Exchange (OLE) Nepal Tel: +977.1.551, 5520075 Ext. 303 Cell: +977.9818 605110 http://www.olenepal.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
D On Mon, Nov 11, 2013 at 11:23 PM, Daniel Drake wrote: > On Sun, Nov 10, 2013 at 5:18 PM, James Cameron wrote: > > If you need to scale up this change to many laptops, contact > > reu...@laptop.org or myself. I must know the SKU number. > > In the particular case of changing language/keyboard defaults as we > are discussing, instead of changing manufacturing data I would > recommend doing it via olpc-os-builder, configuration for [base], see > > http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/base/README#n46 Doing it via olpc-os-builder would be easier especially when we be having more than 200 laptops to work on. This way we won't have to deal with each and every laptop. So the lines I would have to add would be following : [base] default_language=us default_kbd_model=us default_kbd_layout=us default_kbd_variant=np But where do we set the key combination to switch between default and nepali. I would like to assign alt+space or alt+shift as combination. Note: We need to set default layout to english. Nepali input is only required for few activities in Epaath and for typing document in Nepali. -basanta ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
I made the changes but how do we set the key combination to invoke the nepali layout. We need to have english as default and then nepali as and when required. -Basanta On Mon, Nov 11, 2013 at 5:03 AM, James Cameron wrote: > On Sun, Nov 10, 2013 at 11:08:18AM +0545, Basanta Shrestha wrote: > > But I am still wondering how we could alter/change the stored data > > to our preference or if we can do it ourselves. Please suggest. > > At the firmware ok prompt [1], you may change the tag values [2], for > example; > > ok tags( > ok delete-tag KL > ok add-tag KL np > ok delete-tag KV > ok add-tag KV olpc2 > ok )tags > > The )tags command will force a reboot. > > If you need to scale up this change to many laptops, contact > reu...@laptop.org or myself. I must know the SKU number. > > References: > > 1. http://wiki.laptop.org/go/Ok > 2. > http://wiki.laptop.org/go/Manufacturing_Data_Specification#Defined_Tags > > -- > James Cameron > http://quozl.linux.org.au/ > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
On Mon, 2013-11-11 at 11:38 -0600, Daniel Drake wrote: > On Sun, Nov 10, 2013 at 5:18 PM, James Cameron wrote: > > If you need to scale up this change to many laptops, contact > > reu...@laptop.org or myself. I must know the SKU number. > > In the particular case of changing language/keyboard defaults as we > are discussing, instead of changing manufacturing data I would > recommend doing it via olpc-os-builder, configuration for [base], see > http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/base/README#n46 > Or use TinyCore's xo-custom plugin to make the customizations to an existing image on an unlocked XO. http://dev.laptop.org/~quozl/mktinycorexo/HOWTO.xo-custom Jerry ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
On Sun, Nov 10, 2013 at 5:18 PM, James Cameron wrote: > If you need to scale up this change to many laptops, contact > reu...@laptop.org or myself. I must know the SKU number. In the particular case of changing language/keyboard defaults as we are discussing, instead of changing manufacturing data I would recommend doing it via olpc-os-builder, configuration for [base], see http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/base/README#n46 Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
On Sun, Nov 10, 2013 at 11:08:18AM +0545, Basanta Shrestha wrote: > But I am still wondering how we could alter/change the stored data > to our preference or if we can do it ourselves. Please suggest. At the firmware ok prompt [1], you may change the tag values [2], for example; ok tags( ok delete-tag KL ok add-tag KL np ok delete-tag KV ok add-tag KV olpc2 ok )tags The )tags command will force a reboot. If you need to scale up this change to many laptops, contact reu...@laptop.org or myself. I must know the SKU number. References: 1. http://wiki.laptop.org/go/Ok 2. http://wiki.laptop.org/go/Manufacturing_Data_Specification#Defined_Tags -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
Thank you so much Walter and sorry that I am very new to these thing. What I have understood so far is : .mfg-date will list the predefined set to stored data. And we need to set KL to 'np' ( this the name of maping file for Nepali under /usr/share/X11/xkb/symbols/ ) and we need to set some value ( np? ) to KV as well. And we need to decide on a key combination to invoke the keyboard switching between the default(English) and Nepali. Since there is no physical : Language key, I think keyboard combination like alt+space bar should be easy. Please suggest if there is other consideration we need to think of. But I am still wondering how we could alter/change the stored data to our preference or if we can do it ourselves. Please suggest. Regards, Basanta On Sat, Nov 9, 2013 at 6:50 PM, Walter Bender wrote: > On Fri, Nov 8, 2013 at 8:48 PM, Basanta Shrestha > wrote: > > They are hard/clicky ones. > > So I think what we should do is a combination of the suggestions made > previously: if you set the manufacturing data (KL) [1] to tell the > laptops that they have Nepali keyboards, you will be part of the way > there. But we need to make a new variant (KV) for the "hard/clicky" > (HS) keyboard. As I mentioned earlier, we need to decide what the key > combination for switching languages will be, since there is no > physical :Language key. > > -walter > > [1] http://wiki.laptop.org/go/Manufacturing_data > > > > > > On Fri, Nov 8, 2013 at 10:24 PM, Daniel Drake wrote: > >> > >> On Thu, Nov 7, 2013 at 11:23 PM, Basanta Shrestha > >> wrote: > >> > But for XO-4 we will just be getting ones with English layout. I was > >> > wondering how we can enable nepali keyboard input on it. > >> > >> Are these keyboards hard/clicky/high-school style, or soft/membrane? > >> > >> Daniel > > > > > > > > > > -- > > Basanta Shrestha > > Network Engineer > > Open Learning Exchange (OLE) Nepal > > Tel: +977.1.551, 5520075 Ext. 303 > > Cell: +977.9818 605110 > > http://www.olenepal.org > > > > ___ > > Sugar-devel mailing list > > sugar-de...@lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > -- Basanta Shrestha Network Engineer Open Learning Exchange (OLE) Nepal Tel: +977.1.551, 5520075 Ext. 303 Cell: +977.9818 605110 http://www.olenepal.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
On Sat, Nov 9, 2013 at 8:38 AM, Paul Fox wrote: > walter wrote: > > On Fri, Nov 8, 2013 at 8:48 PM, Basanta Shrestha > > wrote: > > > They are hard/clicky ones. > > > > So I think what we should do is a combination of the suggestions made > > previously: if you set the manufacturing data (KL) [1] to tell the > > laptops that they have Nepali keyboards, you will be part of the way > > there. But we need to make a new variant (KV) for the "hard/clicky" > > (HS) keyboard. As I mentioned earlier, we need to decide what the key > > combination for switching languages will be, since there is no > > physical :Language key. > > at what level is the language key handled, on laptops with the > membrane keyboards? (i.e., X? sugar?) that might influence what > sort of combination is available or useful for doing the switch. It is handled in X in the xkb symbol file. -walter > paul > > > > > -walter > > > > [1] http://wiki.laptop.org/go/Manufacturing_data > > > > > > > > > On Fri, Nov 8, 2013 at 10:24 PM, Daniel Drake wrote: > > >> > > >> On Thu, Nov 7, 2013 at 11:23 PM, Basanta Shrestha > > >> wrote: > > >> > But for XO-4 we will just be getting ones with English layout. I was > > >> > wondering how we can enable nepali keyboard input on it. > > >> > > >> Are these keyboards hard/clicky/high-school style, or soft/membrane? > > >> > > >> Daniel > > > > > > > > > > > > > > > -- > > > Basanta Shrestha > > > Network Engineer > > > Open Learning Exchange (OLE) Nepal > > > Tel: +977.1.551, 5520075 Ext. 303 > > > Cell: +977.9818 605110 > > > http://www.olenepal.org > > > > > > ___ > > > Sugar-devel mailing list > > > sugar-de...@lists.sugarlabs.org > > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > > > > > > > > > -- > > Walter Bender > > Sugar Labs > > http://www.sugarlabs.org > > ___ > > Sugar-devel mailing list > > sugar-de...@lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > > =- > paul fox, p...@laptop.org -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
walter wrote: > On Fri, Nov 8, 2013 at 8:48 PM, Basanta Shrestha > wrote: > > They are hard/clicky ones. > > So I think what we should do is a combination of the suggestions made > previously: if you set the manufacturing data (KL) [1] to tell the > laptops that they have Nepali keyboards, you will be part of the way > there. But we need to make a new variant (KV) for the "hard/clicky" > (HS) keyboard. As I mentioned earlier, we need to decide what the key > combination for switching languages will be, since there is no > physical :Language key. at what level is the language key handled, on laptops with the membrane keyboards? (i.e., X? sugar?) that might influence what sort of combination is available or useful for doing the switch. paul > > -walter > > [1] http://wiki.laptop.org/go/Manufacturing_data > > > > > > On Fri, Nov 8, 2013 at 10:24 PM, Daniel Drake wrote: > >> > >> On Thu, Nov 7, 2013 at 11:23 PM, Basanta Shrestha > >> wrote: > >> > But for XO-4 we will just be getting ones with English layout. I was > >> > wondering how we can enable nepali keyboard input on it. > >> > >> Are these keyboards hard/clicky/high-school style, or soft/membrane? > >> > >> Daniel > > > > > > > > > > -- > > Basanta Shrestha > > Network Engineer > > Open Learning Exchange (OLE) Nepal > > Tel: +977.1.551, 5520075 Ext. 303 > > Cell: +977.9818 605110 > > http://www.olenepal.org > > > > ___ > > Sugar-devel mailing list > > sugar-de...@lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > Sugar-devel mailing list > sugar-de...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
On Fri, Nov 8, 2013 at 8:48 PM, Basanta Shrestha wrote: > They are hard/clicky ones. So I think what we should do is a combination of the suggestions made previously: if you set the manufacturing data (KL) [1] to tell the laptops that they have Nepali keyboards, you will be part of the way there. But we need to make a new variant (KV) for the "hard/clicky" (HS) keyboard. As I mentioned earlier, we need to decide what the key combination for switching languages will be, since there is no physical :Language key. -walter [1] http://wiki.laptop.org/go/Manufacturing_data > > > On Fri, Nov 8, 2013 at 10:24 PM, Daniel Drake wrote: >> >> On Thu, Nov 7, 2013 at 11:23 PM, Basanta Shrestha >> wrote: >> > But for XO-4 we will just be getting ones with English layout. I was >> > wondering how we can enable nepali keyboard input on it. >> >> Are these keyboards hard/clicky/high-school style, or soft/membrane? >> >> Daniel > > > > > -- > Basanta Shrestha > Network Engineer > Open Learning Exchange (OLE) Nepal > Tel: +977.1.551, 5520075 Ext. 303 > Cell: +977.9818 605110 > http://www.olenepal.org > > ___ > 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: seeking help to enable nepali keyboard input for XO-4
They are hard/clicky ones. On Fri, Nov 8, 2013 at 10:24 PM, Daniel Drake wrote: > On Thu, Nov 7, 2013 at 11:23 PM, Basanta Shrestha > wrote: > > But for XO-4 we will just be getting ones with English layout. I was > > wondering how we can enable nepali keyboard input on it. > > Are these keyboards hard/clicky/high-school style, or soft/membrane? > > Daniel > -- Basanta Shrestha Network Engineer Open Learning Exchange (OLE) Nepal Tel: +977.1.551, 5520075 Ext. 303 Cell: +977.9818 605110 http://www.olenepal.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
If these are the SKU 311 units the Manufacturing Data on the wiki implies they have membrane keyboards. If so I don't see any reason using the keyboard manufacturing tags used for previous Nepali manufacturing runs (or used testing out the settings in /etc/sysconfig/keyboard manually) shouldn't work. The %/X key will just become the language key again. But if no virtual keyboard exists for Nepali you will not have touchscreen/virtual keyboard access to that language. On Fri, Nov 8, 2013 at 11:41 AM, Walter Bender wrote: > I believe Basanta said that they were the hard click keyboards > > On Fri, Nov 8, 2013 at 11:39 AM, Daniel Drake wrote: > > On Thu, Nov 7, 2013 at 11:23 PM, Basanta Shrestha > > wrote: > >> But for XO-4 we will just be getting ones with English layout. I was > >> wondering how we can enable nepali keyboard input on it. > > > > Are these keyboards hard/clicky/high-school style, or soft/membrane? > > > > Daniel > > ___ > > Devel mailing list > > Devel@lists.laptop.org > > http://lists.laptop.org/listinfo/devel > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > 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: seeking help to enable nepali keyboard input for XO-4
On Thu, Nov 7, 2013 at 11:23 PM, Basanta Shrestha wrote: > But for XO-4 we will just be getting ones with English layout. I was > wondering how we can enable nepali keyboard input on it. Are these keyboards hard/clicky/high-school style, or soft/membrane? Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: seeking help to enable nepali keyboard input for XO-4
I believe Basanta said that they were the hard click keyboards On Fri, Nov 8, 2013 at 11:39 AM, Daniel Drake wrote: > On Thu, Nov 7, 2013 at 11:23 PM, Basanta Shrestha > wrote: >> But for XO-4 we will just be getting ones with English layout. I was >> wondering how we can enable nepali keyboard input on it. > > Are these keyboards hard/clicky/high-school style, or soft/membrane? > > Daniel > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/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] seeking help to enable nepali keyboard input for XO-4
On 8 Nov 2013, at 14:24, Chris Leonard wrote: > What about a virtual touch keyboard layout? Just wondering? FWIW: I'm pretty sure (check [1] & [2]) that Nepali layouts were not part of the Maliit set I was asked to work on for the XO-4 touch keyboard layouts. It's been over a year ago, and a lot of things were going on, so my memory is a little rusty. If the XO-4's in question do have the touch screen hardware support, creating a layout file is not too difficult (as long as the required fonts glyphs are already installed). That is a beauty of touch screen keyboards, they may not be as good as tactile keyboards, but you can have almost any language layout you want with no hardware changes. [1] http://wiki.sugarlabs.org/go/User:Garycmartin/Maliit_Layouts [2] http://wiki.sugarlabs.org/go/User_talk:Garycmartin/Maliit#Currently_available_language_layouts Regards, --Gary > On Fri, Nov 8, 2013 at 8:46 AM, Basanta Shrestha > wrote: >> Hi Walter >> We don't have plans to use stickers at the moment. The stickers won't last >> long in the hands of kids. But we need to have some mechanism to input >> Nepali characters. For now we can give them a printout of the keyboard >> layout. >> Regards, >> Basanta >> >> >> >> On Fri, Nov 8, 2013 at 5:58 PM, Walter Bender >> wrote: >>> >>> A bit tricky because we don't have that key anymore (but we could come >>> up with some other key combination to enable it). Also, are you >>> planning to use stickers or some other way to add the proper glyths to >>> the keyboard? >>> >>> Happy to explore this with you further. >>> >>> regards. >>> >>> -walter >>> >>> On Fri, Nov 8, 2013 at 12:23 AM, Basanta Shrestha >>> wrote: >>>> Hi, >>>> >>>> I am writing this mail seeking a clue on where to start looking to >>>> enable >>>> Nepali input in XO4. For XO-1 we had nepali keyboard and there was a >>>> button >>>> just below the "enter" button which would switch input between English >>>> and >>>> Nepali. And that was very convenient. >>>> >>>> But for XO-4 we will just be getting ones with English layout. I was >>>> wondering how we can enable nepali keyboard input on it. I can see that >>>> the >>>> key maping file for nepali is already there under >>>> /usr/share/X11/xkb/symbols/ >>>> >>>> Thank you . >>>> >>>> -- >>>> Basanta Shrestha >>>> OLE Nepal >>>> >>>> ___ >>>> Sugar-devel mailing list >>>> sugar-de...@lists.sugarlabs.org >>>> http://lists.sugarlabs.org/listinfo/sugar-devel >>>> >>> >>> >>> >>> -- >>> Walter Bender >>> Sugar Labs >>> http://www.sugarlabs.org >> >> >> >> >> -- >> Basanta Shrestha >> Network Engineer >> Open Learning Exchange (OLE) Nepal >> Tel: +977.1.551, 5520075 Ext. 303 >> Cell: +977.9818 605110 >> http://www.olenepal.org >> >> ___ >> 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 signature.asc Description: Message signed with OpenPGP using GPGMail ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard
I think issue is enabling the switching back and forth. We have a dedicated key on the membrane keyboards, but not the 'standard' keyboards. Maybe we make it an altgr key of some sort... -walter On Fri, Nov 8, 2013 at 10:48 AM, Tim Moody wrote: > I don't know if this helps, but it's what I use for Devanagari. Of course, > it's aimed at people familiar with Roman keyboards. > > http://www.ubcsanskrit.ca/keyboards.html > > > > Message: 3 > Date: Fri, 8 Nov 2013 07:13:01 -0500 > From: Walter Bender > To: Basanta Shrestha > Cc: OLPC Devel , Sugar Devel > > Subject: Re: [Sugar-devel] seeking help to enable nepali keyboard > input for XO-4 > Message-ID: > > Content-Type: text/plain; charset=ISO-8859-1 > > A bit tricky because we don't have that key anymore (but we could come > up with some other key combination to enable it). Also, are you > planning to use stickers or some other way to add the proper glyths to > the keyboard? > > Happy to explore this with you further. > > regards. > > -walter > > On Fri, Nov 8, 2013 at 12:23 AM, Basanta Shrestha > wrote: >> >> Hi, >> >> I am writing this mail seeking a clue on where to start looking to enable >> Nepali input in XO4. For XO-1 we had nepali keyboard and there was a >> button >> just below the "enter" button which would switch input between English and >> Nepali. And that was very convenient. >> >> But for XO-4 we will just be getting ones with English layout. I was >> wondering how we can enable nepali keyboard input on it. I can see that >> the >> key maping file for nepali is already there under >> /usr/share/X11/xkb/symbols/ >> >> Thank you . >> >> -- >> Basanta Shrestha >> OLE Nepal >> >> ___ >> 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 -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard
I don't know if this helps, but it's what I use for Devanagari. Of course, it's aimed at people familiar with Roman keyboards. http://www.ubcsanskrit.ca/keyboards.html Message: 3 Date: Fri, 8 Nov 2013 07:13:01 -0500 From: Walter Bender To: Basanta Shrestha Cc: OLPC Devel , Sugar Devel Subject: Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4 Message-ID: Content-Type: text/plain; charset=ISO-8859-1 A bit tricky because we don't have that key anymore (but we could come up with some other key combination to enable it). Also, are you planning to use stickers or some other way to add the proper glyths to the keyboard? Happy to explore this with you further. regards. -walter On Fri, Nov 8, 2013 at 12:23 AM, Basanta Shrestha wrote: Hi, I am writing this mail seeking a clue on where to start looking to enable Nepali input in XO4. For XO-1 we had nepali keyboard and there was a button just below the "enter" button which would switch input between English and Nepali. And that was very convenient. But for XO-4 we will just be getting ones with English layout. I was wondering how we can enable nepali keyboard input on it. I can see that the key maping file for nepali is already there under /usr/share/X11/xkb/symbols/ Thank you . -- Basanta Shrestha OLE Nepal ___ 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] seeking help to enable nepali keyboard input for XO-4
What about a virtual touch keyboard layout? Just wondering? On Fri, Nov 8, 2013 at 8:46 AM, Basanta Shrestha wrote: > Hi Walter > We don't have plans to use stickers at the moment. The stickers won't last > long in the hands of kids. But we need to have some mechanism to input > Nepali characters. For now we can give them a printout of the keyboard > layout. > Regards, > Basanta > > > > On Fri, Nov 8, 2013 at 5:58 PM, Walter Bender > wrote: >> >> A bit tricky because we don't have that key anymore (but we could come >> up with some other key combination to enable it). Also, are you >> planning to use stickers or some other way to add the proper glyths to >> the keyboard? >> >> Happy to explore this with you further. >> >> regards. >> >> -walter >> >> On Fri, Nov 8, 2013 at 12:23 AM, Basanta Shrestha >> wrote: >> > Hi, >> > >> > I am writing this mail seeking a clue on where to start looking to >> > enable >> > Nepali input in XO4. For XO-1 we had nepali keyboard and there was a >> > button >> > just below the "enter" button which would switch input between English >> > and >> > Nepali. And that was very convenient. >> > >> > But for XO-4 we will just be getting ones with English layout. I was >> > wondering how we can enable nepali keyboard input on it. I can see that >> > the >> > key maping file for nepali is already there under >> > /usr/share/X11/xkb/symbols/ >> > >> > Thank you . >> > >> > -- >> > Basanta Shrestha >> > OLE Nepal >> > >> > ___ >> > Sugar-devel mailing list >> > sugar-de...@lists.sugarlabs.org >> > http://lists.sugarlabs.org/listinfo/sugar-devel >> > >> >> >> >> -- >> Walter Bender >> Sugar Labs >> http://www.sugarlabs.org > > > > > -- > Basanta Shrestha > Network Engineer > Open Learning Exchange (OLE) Nepal > Tel: +977.1.551, 5520075 Ext. 303 > Cell: +977.9818 605110 > http://www.olenepal.org > > ___ > 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] seeking help to enable nepali keyboard input for XO-4
Hi Walter We don't have plans to use stickers at the moment. The stickers won't last long in the hands of kids. But we need to have some mechanism to input Nepali characters. For now we can give them a printout of the keyboard layout. Regards, Basanta On Fri, Nov 8, 2013 at 5:58 PM, Walter Bender wrote: > A bit tricky because we don't have that key anymore (but we could come > up with some other key combination to enable it). Also, are you > planning to use stickers or some other way to add the proper glyths to > the keyboard? > > Happy to explore this with you further. > > regards. > > -walter > > On Fri, Nov 8, 2013 at 12:23 AM, Basanta Shrestha > wrote: > > Hi, > > > > I am writing this mail seeking a clue on where to start looking to enable > > Nepali input in XO4. For XO-1 we had nepali keyboard and there was a > button > > just below the "enter" button which would switch input between English > and > > Nepali. And that was very convenient. > > > > But for XO-4 we will just be getting ones with English layout. I was > > wondering how we can enable nepali keyboard input on it. I can see that > the > > key maping file for nepali is already there under > > /usr/share/X11/xkb/symbols/ > > > > Thank you . > > > > -- > > Basanta Shrestha > > OLE Nepal > > > > ___ > > Sugar-devel mailing list > > sugar-de...@lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > -- Basanta Shrestha Network Engineer Open Learning Exchange (OLE) Nepal Tel: +977.1.551, 5520075 Ext. 303 Cell: +977.9818 605110 http://www.olenepal.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
A bit tricky because we don't have that key anymore (but we could come up with some other key combination to enable it). Also, are you planning to use stickers or some other way to add the proper glyths to the keyboard? Happy to explore this with you further. regards. -walter On Fri, Nov 8, 2013 at 12:23 AM, Basanta Shrestha wrote: > Hi, > > I am writing this mail seeking a clue on where to start looking to enable > Nepali input in XO4. For XO-1 we had nepali keyboard and there was a button > just below the "enter" button which would switch input between English and > Nepali. And that was very convenient. > > But for XO-4 we will just be getting ones with English layout. I was > wondering how we can enable nepali keyboard input on it. I can see that the > key maping file for nepali is already there under > /usr/share/X11/xkb/symbols/ > > Thank you . > > -- > Basanta Shrestha > OLE Nepal > > ___ > 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
seeking help to enable nepali keyboard input for XO-4
Hi, I am writing this mail seeking a clue on where to start looking to enable Nepali input in XO4. For XO-1 we had nepali keyboard and there was a button just below the "enter" button which would switch input between English and Nepali. And that was very convenient. But for XO-4 we will just be getting ones with English layout. I was wondering how we can enable nepali keyboard input on it. I can see that the key maping file for nepali is already there under /usr/share/X11/xkb/symbols/ Thank you . -- Basanta Shrestha OLE Nepal ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC New Zealand] Māori Macrons & olpc keyboard
On Sat, Jul 06, 2013 at 09:00:42AM +1200, Tom Parker wrote: > On 06/07/13 05:37, Jerry Vonau wrote:> > > > > On 5 July 2013 07:01, Tom Parker > <mailto:t...@carrott.org>> wrote: > > > > I now have a USB that re-flashes if you hold down the game keys, > > reboots, sets the timezone, the language and the keyboard and then > > prompts the user to press enter to shut down. If you don't hold down > > the game keys it just does the customization which can be done more > > than once without damage. > > > > > > Care to share the forth scripting? Remember to have the AC plugged in > > for the first boot, there maybe a firmware update in the image. I've > > taken a slightly path using a menu for different operations and install > > new firmware if present before installing the image. > > No additional scripting, I'm relying on the built-in > hold-down-game-keys-for-signed-build-reflash to select the > behaviour. I see. The u:\fsN.zip handles the initial install, then when it reboots the u:\boot\olpc.fth is handling the customisation. > > There is a "press enter to shutdown" routine build into xo-custom are > > you scripting the reboot question also? > > If you're talking about the read < /dev/tty1 > /dev/tty1 I haven't > changed it. It usually doesn't work. When it doesn't work, after > pressing enter once, every second key-press is passed to the shell, > until you press enter again and then it shuts down. Sounds like concurrent I/O conflict with the shell on tty1. Perhaps xo-custom should chvt 8 and read and write from /dev/tty8. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC New Zealand] Māori Macrons & olpc keyboard
On 06/07/13 05:37, Jerry Vonau wrote:> > > On 5 July 2013 07:01, Tom Parker <mailto:t...@carrott.org>> wrote: > > I now have a USB that re-flashes if you hold down the game keys, > reboots, sets the timezone, the language and the keyboard and then > prompts the user to press enter to shut down. If you don't hold down > the game keys it just does the customization which can be done more > than once without damage. > > > Care to share the forth scripting? Remember to have the AC plugged in > for the first boot, there maybe a firmware update in the image. I've > taken a slightly path using a menu for different operations and install > new firmware if present before installing the image. No additional scripting, I'm relying on the built-in hold-down-game-keys-for-signed-build-reflash to select the behaviour. > There is a "press enter to shutdown" routine build into xo-custom are > you scripting the reboot question also? If you're talking about the read < /dev/tty1 > /dev/tty1 I haven't changed it. It usually doesn't work. When it doesn't work, after pressing enter once, every second key-press is passed to the shell, until you press enter again and then it shuts down. > Do you mind sharing your > scripts? I plan on using some examples in creating some better > documentation for a how-to. Attached. I wouldn't necessarily recommend the way I'm inserting the keyboard as I'm not following all the recommendations on the various keyboard related pages. #!/bin/bash cat << EOF > ~/.i18n LANG="mi_NZ.utf8" LANGUAGE="mi_NZ.utf8:en_NZ.utf8:en_GB.utf8:en_US.utf8" EOF gconftool-2 -s /desktop/sugar/date/timezone --type string Pacific/Auckland #!/bin/bash cp /usr/share/zoneinfo/Pacific/Auckland /etc/localtime cp /media/mi /usr/share/X11/xkb/symbols sed -i -e 's/us/mi/' /etc/sysconfig/keyboard ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC New Zealand] Māori Macrons & olpc keyboard
On 5 July 2013 07:01, Tom Parker wrote: > On 01/07/13 19:53, James Cameron wrote: > >> On Mon, Jul 01, 2013 at 07:35:03PM +1200, Tom Parker wrote: >> >>> xkbcomp $DISPLAY orig.xkb >>> patch -p0 >> sudo cp orig.xkb /usr/share/X11/xkb/symbols/mi >>> sudo vi /etc/sysconfig/keyboard >>> ... >>> >>> Is Jerry's xs.custom >>> http://lists.laptop.org/**pipermail/server-devel/2013-**June/006510.html<http://lists.laptop.org/pipermail/server-devel/2013-June/006510.html> >>> suitable for customizing an XO? >>> >> >> Yes. It would apply the changes you describe reasonably easily. >> > > Indeed it does work, although I had to add support for the XO-4 HS Touch > and XO-4 Touch, I've sent you a patch. > > Thanks, > I now have a USB that re-flashes if you hold down the game keys, reboots, > sets the timezone, the language and the keyboard and then prompts the user > to press enter to shut down. If you don't hold down the game keys it just > does the customization which can be done more than once without damage. > > Care to share the forth scripting? Remember to have the AC plugged in for the first boot, there maybe a firmware update in the image. I've taken a slightly path using a menu for different operations and install new firmware if present before installing the image. > The only wrinkle is that most of the time I have to press enter twice to > get it to quit at the end which is hardly worth complaining about but had > me stumped for a minute or two the first time. > > There is a "press enter to shutdown" routine build into xo-custom are you scripting the reboot question also? > Also I had trouble finding the xo-custom thing, so for the record, it's an > optional configuration of Tiny Core Linux described at > http://wiki.laptop.org/go/**Tiny_Core_Linux<http://wiki.laptop.org/go/Tiny_Core_Linux>You > will have to clone the git repo and build it from scratch to get the > xo-custom behavior. > > I'm going to place the Tiny Core files to be available for download so all you have to add is your own scripting. Do you mind sharing your scripts? I plan on using some examples in creating some better documentation for a how-to. Thanks for testing, Jerry __ > OLPC-NZ mailing list > olpc...@lists.laptop.org > http://lists.laptop.org/**listinfo/olpc-nz<http://lists.laptop.org/listinfo/olpc-nz> > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC New Zealand] Māori Macrons & olpc keyboard
On 01/07/13 19:53, James Cameron wrote: On Mon, Jul 01, 2013 at 07:35:03PM +1200, Tom Parker wrote: xkbcomp $DISPLAY orig.xkb patch -p0 http://lists.laptop.org/pipermail/server-devel/2013-June/006510.html suitable for customizing an XO? Yes. It would apply the changes you describe reasonably easily. Indeed it does work, although I had to add support for the XO-4 HS Touch and XO-4 Touch, I've sent you a patch. I now have a USB that re-flashes if you hold down the game keys, reboots, sets the timezone, the language and the keyboard and then prompts the user to press enter to shut down. If you don't hold down the game keys it just does the customization which can be done more than once without damage. The only wrinkle is that most of the time I have to press enter twice to get it to quit at the end which is hardly worth complaining about but had me stumped for a minute or two the first time. Also I had trouble finding the xo-custom thing, so for the record, it's an optional configuration of Tiny Core Linux described at http://wiki.laptop.org/go/Tiny_Core_Linux You will have to clone the git repo and build it from scratch to get the xo-custom behavior. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC New Zealand] Māori Macrons & olpc keyboard
On Mon, Jul 01, 2013 at 07:35:03PM +1200, Tom Parker wrote: > xkbcomp $DISPLAY orig.xkb > patch -p0 sudo cp orig.xkb /usr/share/X11/xkb/symbols/mi > sudo vi /etc/sysconfig/keyboard > ... > > Is Jerry's xs.custom > http://lists.laptop.org/pipermail/server-devel/2013-June/006510.html > suitable for customizing an XO? Yes. It would apply the changes you describe reasonably easily. (In my opinion the file name should have been HOWTO.xo-custom and that's how I'm merging this contribution from Jerry.) The XO must be unsecured, or the deployment keys must be used to sign the kernel and initrd files. Beware that unlike the original OLPC customisation stick, Tiny Core Linux is not a secure environment, and so if you find yourself signing make sure that the only reason you are doing it is for ease of use, not deployment security. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC New Zealand] Māori Macrons & olpc keyboard
On 26/06/13 22:16, Tom Parker wrote: What is the best way to modify the laptops? Copying modified output of xkbcomp to /usr/share/X11/xkb/symbols/mi and running setxkbmap mi does the trick, but setting the content of /home/olpc/.Xkbmap to mi does not make this the default after reboot. There is a clue on the Manufacturing Data page on the olpc wiki, you need to modify /etc/sysconfig/keyboard and change the "us" to "mi". So to recap, To create and install a new Maori keyboard using the maori.patch from my previous mail: xkbcomp $DISPLAY orig.xkb patch -p0 This isn't the "right" way to do it, but it works and is probably good enough for now. If the users like the layout we'll do what we need to do to get it into the build. Is Jerry's xs.custom http://lists.laptop.org/pipermail/server-devel/2013-June/006510.html suitable for customizing an XO? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC New Zealand] Māori Macrons & olpc keyboard
On 26/06/13 10:52, Walter Bender wrote:
The widget was broken until recently. Not sure my patches have landed
in any releases yet. But we should be able to make a layout that works
for both English and Maori without any end-user intervention. Will try
to get to it this week.
Attached is a patch to the output of xkbcomp on an XO-4 with mechanical
keyboard. Sorry it's not in style of the files in /usr/share/X11/xkb, I
still haven't been able to unravel how those files work. I think I can
make an mi file that just has the changed lines, which layout should I
use as a base? I'm guessing I might need to do something different for
the membrane and mechanical keyboards?
What is the best way to modify the laptops? Copying modified output of
xkbcomp to /usr/share/X11/xkb/symbols/mi and running
setxkbmap mi
does the trick, but setting the content of /home/olpc/.Xkbmap to mi does
not make this the default after reboot.
--- orig.xkb 2013-06-26 09:28:21.770500621 +
+++ test.xkb 2013-06-26 09:28:07.050500619 +
@@ -1188,7 +1188,7 @@
key {
type= "FOUR_LEVEL_ALPHABETIC",
repeat= No,
-symbols[Group1]= [ e, E, oe, OE ]
+symbols[Group1]= [ e, E, U0113, U0112 ]
};
key {
type= "FOUR_LEVEL_SEMIALPHABETIC",
@@ -1208,17 +1208,17 @@
key {
type= "FOUR_LEVEL_SEMIALPHABETIC",
repeat= No,
-symbols[Group1]= [ u, U, U032D, U032D ]
+symbols[Group1]= [ u, U, U016B, U016A ]
};
key {
type= "FOUR_LEVEL_SEMIALPHABETIC",
repeat= No,
-symbols[Group1]= [ i, I, U032C, U032C ]
+symbols[Group1]= [ i, I, U012B, U012A ]
};
key {
type= "FOUR_LEVEL_SEMIALPHABETIC",
repeat= No,
-symbols[Group1]= [ o, O, U0323, U0323 ]
+symbols[Group1]= [ o, O, U014D, U014C ]
};
key {
type= "FOUR_LEVEL_SEMIALPHABETIC",
@@ -1246,7 +1246,7 @@
key {
type= "FOUR_LEVEL_ALPHABETIC",
repeat= No,
-symbols[Group1]= [ a, A, ae, AE ]
+symbols[Group1]= [ a, A, U0101, U0100 ]
};
key {
type= "FOUR_LEVEL_SEMIALPHABETIC",
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: [OLPC New Zealand] Māori Macrons & olpc keyboard
On 26/06/13 00:22, Barry Vercoe wrote: > Tom, it's not correct to say the laptops will remain in Maori. Sorry, I should have clarified that I was referring to the keyboard only. I think the difference between the current olpc keyboard and a customized Maori one will be minor. We'll replace the æ œ ̬ ̣ ̭ characters with the macron vowels. I don't think this will present any problems if we make it difficult to reverse until a Maori keyboard and a keyboard chooser are built into the operating system. I don't know how to do the windows style grave modifier on linux and for consistency with other Linux Maori keyboards, I think alt-gr - vowel will be a better starting place than the default setup. Switching the rest of the laptop to other languages is a different matter and I wouldn't propose to stop that! ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Māori Macrons & olpc keyboard
Maybe the font used is related to this issue? You can test using abiword from gnome or the terminal, and try different fonts. Gonzalo On Mon, Jun 24, 2013 at 7:53 AM, Tom Parker wrote: > Hi, > > I'm looking at how you enter a macron for Māori language users. > > It seems that the olpc us international keyboard binds a ̄ COMBINING > MACRON (unicode U+0304) to algr + hyphan. When typed after the letter a you > get ā which is similar to but not the same as ā LATIN SMALL LETTER A WITH > MACRON (unicode U+0101). > > Issues I've noted with a small amount of testing: > > On older builds, Write does not correctly load files containing the > combining macron. > The combining macron is not rendered at the correct height for lower case > letters. (on older builds this seems to be the case all the time, on newer > builds, it is rendered correctly after loading a file until you delete a > following character the on the same line, then it jumps up) > You can have more than one combining macron, they stack. > You have to delete twice, once to delete the macron and again to delete > the character. > > Have these issues come up before? I don't see any. I will raise tickets > for the bugs rendering the macron in the latest version of write shortly. > I'm not sure if anyone wants a ticket for older builds? Obviously stacking > macrons is by-design when using the combining macron character (see > https://twitter.com/glitchr_/ for more improbable outcomes of combining > characters, perhaps your browser will crash). > > I haven't yet experimented with entering the ā U+0101 characters into > sugar (tomorrow!) > > Apparently on Windows, the Māori keyboard is set up such that when you hit > the grave (apparently this is what I have always called the backtick) key > and then one of the vowels, you get the macron version of the vowel. I > haven't seen this in action but Māori typists claim it is very efficient. > > Gnome on Ubuntu on my laptop binds right-alt-a to ā U+0101 when using the > Māori keyboard layout. I'm not sure how Maori typists feel about this > inconsistency with windows. > > When you choose the language in sugar, can this change the keyboard layout > too? If not, what is the recommended way to configure this? > > How complex is it to change the localization of the keyboard for the Maori > language? The xkb files don't look too complicated. Is the grave - vowel = > macron vowel possible while still preserving the backtick for shell > scripting? I haven't seen the laptops in question but I'm told they have > the Australian simplified key caps, so changing the existing alt-gr > mappings to render macron vowels (ie to mimic the Maori keyboard option on > Gnome-Ubuntu) instead of the existing mappings won't confuse the key caps. > > Obviously touching all the laptops to change how the keyboard works is a > pain and the change is potentially erased by future updates. > __**_ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/**listinfo/devel<http://lists.laptop.org/listinfo/devel> > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC New Zealand] Māori Macrons & olpc keyboard
The widget was broken until recently. Not sure my patches have landed in any releases yet. But we should be able to make a layout that works for both English and Maori without any end-user intervention. Will try to get to it this week. -walter On Tue, Jun 25, 2013 at 9:07 AM, Sridhar Dhanapalan wrote: > On 24/06/2013 9:43 PM, "Walter Bender" wrote: >> >> Which build are you running? In the latest Sugar builds, there is a >> keyboard settings control panel section. We could probably backport it >> to your build if it is reasonably recent. > > I remember that perhaps a year ago we had to remove the keyboard applet > because it was causing some weird side effects. It wasn't a concern at the > time because our focus was on English. -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC New Zealand] Māori Macrons & olpc keyboard
On 24/06/2013 9:43 PM, "Walter Bender" wrote: > > Which build are you running? In the latest Sugar builds, there is a > keyboard settings control panel section. We could probably backport it > to your build if it is reasonably recent. I remember that perhaps a year ago we had to remove the keyboard applet because it was causing some weird side effects. It wasn't a concern at the time because our focus was on English. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Māori Macrons & olpc keyboard
Tom, it's not correct to say the laptops will remain in Maori. Many schools have both Maori and English classes, and the ability of these machines to cross the boundary, to have a child work either in their first language or (with a simple switch in Settings->Language) to gain experience in another, is one of our strong features. Having the switch relatively easy is a great, and I've seen some kids do it while I'm supposedly talking to them. Incidentally, there's a _bug _when declaring the second language second. It seems that whichever language is _last declared_ becomes the current language in which alternative languages are expressed -- as for instance for the list within _Speak_. Since I don't yet have a Maori version of the ESPEAK voice engine (takers anyone?), and since English pronunciation and prosody is a poor substitute, I routinely tell the children typing in Maori to set the _Speak _language to Vietnamese. This is a surprisingly good substitute. But it becomes hard to find if someone has last set the login 2nd language to Arabic. This bug shouldn't be hard to fix. Until then, declare your #2 language first, and your #1 language last. -- barry On 25/06/2013 10:51 p.m., Tom Parker wrote: On 24/06/13 23:43, Walter Bender wrote: Which build are you running? In the latest Sugar builds, there is a keyboard settings control panel section. We could probably backport it to your build if it is reasonably recent. I don't know which build they are running. I've tried One Education OS 1.2 (build au889) with Sugar 0.94.1 13.2.0 for XO-4 (build 10) with Sugar 0.98.7 XO-system 1a for XO-4 (build 34) with Sugar 0.98.7 and none of them have a keyboard settings thing. I don't think a keyboard settings control panel is immediately necessary as the laptops will remain in Maori. It would be good in a future release if we could say "after reflashing, set your language and keyboard to maori" without having to resort to customizations. Meanwhile, we may have to make a new X keyboard symbols file for you that does the right thing. Not impossible to get upstreamed. I wasn't really able understand the /usr/share/X11/xkb directory, but using xkbcomp to retrieve the current config, modify it and return it to the X server does the trick. Is there a document that describes the "right" way to add a keyboard and select it? Using xkbcomp in a startup script might work but is obviously a hack. http://wiki.laptop.org/go/Creating_A_New_Keyboard_Layout seems to cover this but appears to be out of date. Until we get feedback from the actual users about what they want their keyboards to do, I think it's best to customize the build they have rather than upstream something and get a new build. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Māori Macrons & olpc keyboard
On 24/06/13 23:43, Walter Bender wrote: Which build are you running? In the latest Sugar builds, there is a keyboard settings control panel section. We could probably backport it to your build if it is reasonably recent. I don't know which build they are running. I've tried One Education OS 1.2 (build au889) with Sugar 0.94.1 13.2.0 for XO-4 (build 10) with Sugar 0.98.7 XO-system 1a for XO-4 (build 34) with Sugar 0.98.7 and none of them have a keyboard settings thing. I don't think a keyboard settings control panel is immediately necessary as the laptops will remain in Maori. It would be good in a future release if we could say "after reflashing, set your language and keyboard to maori" without having to resort to customizations. Meanwhile, we may have to make a new X keyboard symbols file for you that does the right thing. Not impossible to get upstreamed. I wasn't really able understand the /usr/share/X11/xkb directory, but using xkbcomp to retrieve the current config, modify it and return it to the X server does the trick. Is there a document that describes the "right" way to add a keyboard and select it? Using xkbcomp in a startup script might work but is obviously a hack. http://wiki.laptop.org/go/Creating_A_New_Keyboard_Layout seems to cover this but appears to be out of date. Until we get feedback from the actual users about what they want their keyboards to do, I think it's best to customize the build they have rather than upstream something and get a new build. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC New Zealand] Māori Macrons & olpc keyboard
Hi, on SHC 205002233 running 13.1.0 for XO-1.75 (build 20) with Sugar 0.98.2 firmware Q4D24 For Text in both Write and Turtle Art (the Title panel): vowel + altgr - gives the Combining Macron, i.e. two bkspcs to remove the letter But if either Activity is saved to the Journal and we write into its Description panel vowel + altgr - gives the Unicode version, i.e. one bksp removes the letter. So we do have the right behavior in there somewhere. -- barry On 25/06/2013 12:13 a.m., Walter Bender wrote: On Mon, Jun 24, 2013 at 8:12 AM, Jerry Vonau wrote: On 24 June 2013 06:43, Walter Bender wrote: Which build are you running? In the latest Sugar builds, there is a keyboard settings control panel section. We could probably backport it to your build if it is reasonably recent. In OLPC's & Dextrose's versions of sugar the sugar-cp-keyboard rpm doesn't get installed. Think there is a conflict over the keyboard with olpc-configure supplied by olpc-utils. I can poke around to see if I can get it to work. -walter Jerry Meanwhile, we may have to make a new X keyboard symbols file for you that does the right thing. Not impossible to get upstreamed. regards. -walter On Mon, Jun 24, 2013 at 6:53 AM, Tom Parker wrote: Hi, I'm looking at how you enter a macron for Māori language users. It seems that the olpc us international keyboard binds a ̄ COMBINING MACRON (unicode U+0304) to algr + hyphan. When typed after the letter a you get ā which is similar to but not the same as ā LATIN SMALL LETTER A WITH MACRON (unicode U+0101). Issues I've noted with a small amount of testing: On older builds, Write does not correctly load files containing the combining macron. The combining macron is not rendered at the correct height for lower case letters. (on older builds this seems to be the case all the time, on newer builds, it is rendered correctly after loading a file until you delete a following character the on the same line, then it jumps up) You can have more than one combining macron, they stack. You have to delete twice, once to delete the macron and again to delete the character. Have these issues come up before? I don't see any. I will raise tickets for the bugs rendering the macron in the latest version of write shortly. I'm not sure if anyone wants a ticket for older builds? Obviously stacking macrons is by-design when using the combining macron character (see https://twitter.com/glitchr_/ for more improbable outcomes of combining characters, perhaps your browser will crash). I haven't yet experimented with entering the ā U+0101 characters into sugar (tomorrow!) Apparently on Windows, the Māori keyboard is set up such that when you hit the grave (apparently this is what I have always called the backtick) key and then one of the vowels, you get the macron version of the vowel. I haven't seen this in action but Māori typists claim it is very efficient. Gnome on Ubuntu on my laptop binds right-alt-a to ā U+0101 when using the Māori keyboard layout. I'm not sure how Maori typists feel about this inconsistency with windows. When you choose the language in sugar, can this change the keyboard layout too? If not, what is the recommended way to configure this? How complex is it to change the localization of the keyboard for the Maori language? The xkb files don't look too complicated. Is the grave - vowel = macron vowel possible while still preserving the backtick for shell scripting? I haven't seen the laptops in question but I'm told they have the Australian simplified key caps, so changing the existing alt-gr mappings to render macron vowels (ie to mimic the Maori keyboard option on Gnome-Ubuntu) instead of the existing mappings won't confuse the key caps. Obviously touching all the laptops to change how the keyboard works is a pain and the change is potentially erased by future updates. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ OLPC-NZ mailing list olpc...@lists.laptop.org http://lists.laptop.org/listinfo/olpc-nz -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC New Zealand] Māori Macrons & olpc keyboard
Could you please try with the latest version of Turtle Art (v182)? thx -walter On Mon, Jun 24, 2013 at 9:30 AM, Barry Vercoe wrote: > Hi, on SHC 205002233 > running 13.1.0 for XO-1.75 (build 20) > with Sugar 0.98.2 > firmware Q4D24 > > For Text in both Write and Turtle Art (the Title panel): > vowel + altgr - gives the Combining Macron, i.e. two bkspcs to remove > the letter > But if either Activity is saved to the Journal and we write into its > Description panel > vowel + altgr - gives the Unicode version, i.e. one bksp removes the > letter. > > So we do have the right behavior in there somewhere. > -- barry > > > On 25/06/2013 12:13 a.m., Walter Bender wrote: > > On Mon, Jun 24, 2013 at 8:12 AM, Jerry Vonau wrote: > > On 24 June 2013 06:43, Walter Bender wrote: > > Which build are you running? In the latest Sugar builds, there is a > keyboard settings control panel section. We could probably backport it > to your build if it is reasonably recent. > > In OLPC's & Dextrose's versions of sugar the sugar-cp-keyboard rpm doesn't > get installed. Think there is a conflict over the keyboard with > olpc-configure supplied by olpc-utils. > > I can poke around to see if I can get it to work. > > -walter > > Jerry > > Meanwhile, we may have to make a new X keyboard symbols file for you > that does the right thing. Not impossible to get upstreamed. > > regards. > > -walter > > On Mon, Jun 24, 2013 at 6:53 AM, Tom Parker wrote: > > Hi, > > I'm looking at how you enter a macron for Māori language users. > > It seems that the olpc us international keyboard binds a ̄ COMBINING > MACRON > (unicode U+0304) to algr + hyphan. When typed after the letter a you get > ā > which is similar to but not the same as ā LATIN SMALL LETTER A WITH > MACRON > (unicode U+0101). > > Issues I've noted with a small amount of testing: > > On older builds, Write does not correctly load files containing the > combining macron. > The combining macron is not rendered at the correct height for lower > case > letters. (on older builds this seems to be the case all the time, on > newer > builds, it is rendered correctly after loading a file until you delete a > following character the on the same line, then it jumps up) > You can have more than one combining macron, they stack. > You have to delete twice, once to delete the macron and again to delete > the > character. > > Have these issues come up before? I don't see any. I will raise tickets > for > the bugs rendering the macron in the latest version of write shortly. > I'm > not sure if anyone wants a ticket for older builds? Obviously stacking > macrons is by-design when using the combining macron character (see > https://twitter.com/glitchr_/ for more improbable outcomes of combining > characters, perhaps your browser will crash). > > I haven't yet experimented with entering the ā U+0101 characters into > sugar > (tomorrow!) > > Apparently on Windows, the Māori keyboard is set up such that when you > hit > the grave (apparently this is what I have always called the backtick) > key > and then one of the vowels, you get the macron version of the vowel. I > haven't seen this in action but Māori typists claim it is very > efficient. > > Gnome on Ubuntu on my laptop binds right-alt-a to ā U+0101 when using > the > Māori keyboard layout. I'm not sure how Maori typists feel about this > inconsistency with windows. > > When you choose the language in sugar, can this change the keyboard > layout > too? If not, what is the recommended way to configure this? > > How complex is it to change the localization of the keyboard for the > Maori > language? The xkb files don't look too complicated. Is the grave - vowel > = > macron vowel possible while still preserving the backtick for shell > scripting? I haven't seen the laptops in question but I'm told they have > the > Australian simplified key caps, so changing the existing alt-gr mappings > to > render macron vowels (ie to mimic the Maori keyboard option on > Gnome-Ubuntu) > instead of the existing mappings won't confuse the key caps. > > Obviously touching all the laptops to change how the keyboard works is a > pain and the change is potentially erased by future updates. > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > OLPC-NZ mailing list > olpc...@lists.laptop.org > http://lists.laptop.org/listinfo/olpc-nz > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > > -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC New Zealand] Māori Macrons & olpc keyboard
On Mon, Jun 24, 2013 at 8:12 AM, Jerry Vonau wrote: > > > On 24 June 2013 06:43, Walter Bender wrote: >> >> Which build are you running? In the latest Sugar builds, there is a >> keyboard settings control panel section. We could probably backport it >> to your build if it is reasonably recent. >> > > In OLPC's & Dextrose's versions of sugar the sugar-cp-keyboard rpm doesn't > get installed. Think there is a conflict over the keyboard with > olpc-configure supplied by olpc-utils. I can poke around to see if I can get it to work. -walter > > Jerry > >> >> Meanwhile, we may have to make a new X keyboard symbols file for you >> that does the right thing. Not impossible to get upstreamed. >> >> regards. >> >> -walter >> >> On Mon, Jun 24, 2013 at 6:53 AM, Tom Parker wrote: >> > Hi, >> > >> > I'm looking at how you enter a macron for Māori language users. >> > >> > It seems that the olpc us international keyboard binds a ̄ COMBINING >> > MACRON >> > (unicode U+0304) to algr + hyphan. When typed after the letter a you get >> > ā >> > which is similar to but not the same as ā LATIN SMALL LETTER A WITH >> > MACRON >> > (unicode U+0101). >> > >> > Issues I've noted with a small amount of testing: >> > >> > On older builds, Write does not correctly load files containing the >> > combining macron. >> > The combining macron is not rendered at the correct height for lower >> > case >> > letters. (on older builds this seems to be the case all the time, on >> > newer >> > builds, it is rendered correctly after loading a file until you delete a >> > following character the on the same line, then it jumps up) >> > You can have more than one combining macron, they stack. >> > You have to delete twice, once to delete the macron and again to delete >> > the >> > character. >> > >> > Have these issues come up before? I don't see any. I will raise tickets >> > for >> > the bugs rendering the macron in the latest version of write shortly. >> > I'm >> > not sure if anyone wants a ticket for older builds? Obviously stacking >> > macrons is by-design when using the combining macron character (see >> > https://twitter.com/glitchr_/ for more improbable outcomes of combining >> > characters, perhaps your browser will crash). >> > >> > I haven't yet experimented with entering the ā U+0101 characters into >> > sugar >> > (tomorrow!) >> > >> > Apparently on Windows, the Māori keyboard is set up such that when you >> > hit >> > the grave (apparently this is what I have always called the backtick) >> > key >> > and then one of the vowels, you get the macron version of the vowel. I >> > haven't seen this in action but Māori typists claim it is very >> > efficient. >> > >> > Gnome on Ubuntu on my laptop binds right-alt-a to ā U+0101 when using >> > the >> > Māori keyboard layout. I'm not sure how Maori typists feel about this >> > inconsistency with windows. >> > >> > When you choose the language in sugar, can this change the keyboard >> > layout >> > too? If not, what is the recommended way to configure this? >> > >> > How complex is it to change the localization of the keyboard for the >> > Maori >> > language? The xkb files don't look too complicated. Is the grave - vowel >> > = >> > macron vowel possible while still preserving the backtick for shell >> > scripting? I haven't seen the laptops in question but I'm told they have >> > the >> > Australian simplified key caps, so changing the existing alt-gr mappings >> > to >> > render macron vowels (ie to mimic the Maori keyboard option on >> > Gnome-Ubuntu) >> > instead of the existing mappings won't confuse the key caps. >> > >> > Obviously touching all the laptops to change how the keyboard works is a >> > pain and the change is potentially erased by future updates. >> > ___ >> > Devel mailing list >> > Devel@lists.laptop.org >> > http://lists.laptop.org/listinfo/devel >> >> >> >> -- >> Walter Bender >> Sugar Labs >> http://www.sugarlabs.org >> ___ >> OLPC-NZ mailing list >> olpc...@lists.laptop.org >> http://lists.laptop.org/listinfo/olpc-nz > > -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Māori Macrons & olpc keyboard
Which build are you running? In the latest Sugar builds, there is a keyboard settings control panel section. We could probably backport it to your build if it is reasonably recent. Meanwhile, we may have to make a new X keyboard symbols file for you that does the right thing. Not impossible to get upstreamed. regards. -walter On Mon, Jun 24, 2013 at 6:53 AM, Tom Parker wrote: > Hi, > > I'm looking at how you enter a macron for Māori language users. > > It seems that the olpc us international keyboard binds a ̄ COMBINING MACRON > (unicode U+0304) to algr + hyphan. When typed after the letter a you get ā > which is similar to but not the same as ā LATIN SMALL LETTER A WITH MACRON > (unicode U+0101). > > Issues I've noted with a small amount of testing: > > On older builds, Write does not correctly load files containing the > combining macron. > The combining macron is not rendered at the correct height for lower case > letters. (on older builds this seems to be the case all the time, on newer > builds, it is rendered correctly after loading a file until you delete a > following character the on the same line, then it jumps up) > You can have more than one combining macron, they stack. > You have to delete twice, once to delete the macron and again to delete the > character. > > Have these issues come up before? I don't see any. I will raise tickets for > the bugs rendering the macron in the latest version of write shortly. I'm > not sure if anyone wants a ticket for older builds? Obviously stacking > macrons is by-design when using the combining macron character (see > https://twitter.com/glitchr_/ for more improbable outcomes of combining > characters, perhaps your browser will crash). > > I haven't yet experimented with entering the ā U+0101 characters into sugar > (tomorrow!) > > Apparently on Windows, the Māori keyboard is set up such that when you hit > the grave (apparently this is what I have always called the backtick) key > and then one of the vowels, you get the macron version of the vowel. I > haven't seen this in action but Māori typists claim it is very efficient. > > Gnome on Ubuntu on my laptop binds right-alt-a to ā U+0101 when using the > Māori keyboard layout. I'm not sure how Maori typists feel about this > inconsistency with windows. > > When you choose the language in sugar, can this change the keyboard layout > too? If not, what is the recommended way to configure this? > > How complex is it to change the localization of the keyboard for the Maori > language? The xkb files don't look too complicated. Is the grave - vowel = > macron vowel possible while still preserving the backtick for shell > scripting? I haven't seen the laptops in question but I'm told they have the > Australian simplified key caps, so changing the existing alt-gr mappings to > render macron vowels (ie to mimic the Maori keyboard option on Gnome-Ubuntu) > instead of the existing mappings won't confuse the key caps. > > Obviously touching all the laptops to change how the keyboard works is a > pain and the change is potentially erased by future updates. > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
