<div dir="ltr">Thanks for all the help. First I'm going to try to fix module loading. I think instead of using the 4.8 kernel I'm going to use olpc-3.10 but update it to 3.10.108, and enable CONFIG_FHANDLE for systemd.<div> </div><div>I have another tiny question:</div><div>In olpc-os-builder where does the kernel come from? I see it defined as "kernel" in a package list, but how does it know what OLPC branch to use, etc?</div><div class="gmail_extra"> <div><div class="gmail_signature"><div dir="ltr"><div dir="ltr"><div> </div><div>Ethan Nelson-Moore</div></div></div></div></div></div><div class="gmail_extra"><div><div class="gmail-m_464342028254111934gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div></div></div></div></div></div></div></div> <div class="gmail_quote">On Thu, Dec 28, 2017 at 11:00 AM, <<a href="mailto:soas-request@lists.sugarlabs.org" target="_blank">soas-request@lists.sugarlabs.org</a>> wrote: <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send SoaS mailing list submissions to <a href="mailto:soas@lists.sugarlabs.org" target="_blank">soas@lists.sugarlabs.org</a> To subscribe or unsubscribe via the World Wide Web, visit <a href="http://lists.sugarlabs.org/listinfo/soas" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/soas</a> or, via email, send a message with subject or body 'help' to <a href="mailto:soas-request@lists.sugarlabs.org" target="_blank">soas-request@lists.sugarlabs.org</a> You can reach the person managing the list at <a href="mailto:soas-owner@lists.sugarlabs.org" target="_blank">soas-owner@lists.sugarlabs.org</a> When replying, please edit your Subject line so it is more specific than "Re: Contents of SoaS digest..." Today's Topics: 1. How to: Partially working Fedora 26 Sugar on a Stick on the XO-1 (Ethan) 2. Re: How to: Partially working Fedora 26 Sugar on a Stick on the XO-1 (James Cameron) ---------------------------------------------------------------------- Message: 1 Date: Wed, 27 Dec 2017 20:33:41 -0600 From: Ethan <<a href="mailto:parrotgeek1@gmail.com" target="_blank">parrotgeek1@gmail.com</a>> To: <a href="mailto:soas@lists.sugarlabs.org" target="_blank">soas@lists.sugarlabs.org</a> Subject: [SoaS] How to: Partially working Fedora 26 Sugar on a Stick on the XO-1 Message-ID: <<a href="mailto:CAHW1XJ0qbUN4HX8A9D%2BXN83ky4p5keSB9kUkcNPwORChaWCKbQ@mail.gmail.com" target="_blank">CAHW1XJ0qbUN4HX8A9D+XN83ky4p5keSB9kUkcNPwORChaWCKbQ@mail.gmail.com</a>> Content-Type: text/plain; charset="utf-8" Hello everyone, I was able to make my own kernel 4.15 for the XO-1 in order to boot SoaS Fedora 26 on the XO-1. Here is how I did it. I would like help fixing the bugs. Instructions -------------------------------------- the xo needs to be unlocked with dev key AND update firmware to latest version otherwise new kernel doesn't boot! download soas i386 iso Fedora-SoaS-Live-i386-26-1.5 from <a href="http://dl.fedoraproject.org/pub/fedora-secondary/releases/26/Spins/i386/iso/" rel="noreferrer" target="_blank">http://dl.fedoraproject.org/pub/fedora-secondary/releases/26/Spins/i386/iso/</a> put soas i386 iso in vmware connect 4gb+ usb drive to it and share in vmware give yourself a name, color, grade open terminal, run sudo liveinst select sdb1 as device go to custom partitioning delete all partitions create "/" as standard, ext2! not ext3 or ext4 set / type to standard not lvm! change / partition label to "SoaS" EXACTLY click update settings click done multiple times, accept changes click begin installation click root password. type olpc for root password, click done twice make user olpc with admin, password also olpc (for compatibliity with old activities), click done twice when installer done (note: it will say 100% for a long time): close installer reboot vm by clicking reboot on xo guy. NOT by closing window run in terminal cd /run/media/liveuser/SoaS curl -Lo /tmp/a.zip <a href="http://parrotgeek.com/downloads/xofix.zip" rel="noreferrer" target="_blank">parrotgeek.com/downloads/xofix.zip</a> sudo unzip /tmp/a.zip sudo cp boot/initramfs*i686.img boot/xoinitrd.img note: the kernel in xofix.zip is from: <a href="https://github.com/parrotgeek1/linuxXO" rel="noreferrer" target="_blank">https://github.com/parrotgeek1/linuxXO</a> SHUT DOWN the vm by clicking shut down on xo guy. NOT by closing window do NOT reboot from the USB on a computer other than XO! then plug the usb into xo and boot! it should work ---------------------------- Critical Bugs: !!! When Xorg starts there is a weird LCD fade effect like DCON hardware is being initialized wrong 5+ minute boot time due to firewalld, sssd failing to start. After login, XO sits for a very long time at only a mouse cursor, with the mic light on Screen is not scaled to 200 DPI. Attempts to copy xorg.conf from an XO image resulted in Xorg not starting. Also, Xorg is using fbdev not geode. no wifi (Need firmware. Also no kernel modules are loading) Impossible to open frame with mouse unless change corner size to 5px, maybe dpi issue? Rotate button doesn't work (maybe because it isn't using geode driver) Power management does not work at all. Disk and Wifi lights don't work. webcam does not work (No modules are loading) On keyboard, the increasing size dots, and 2 boxes overlapping keys do not work Brightness keys work but super slow to change brightness it doesn't see the nand (driver loads but fail to init) /ofw not mounted Cosmetic bugs: Not asked for name at first boot, instead it is "olpc" Login screen shows instead of auto login [SoaS bug] Loading mouse cursor is the gnome one not xo one Hostname is localhost not like xo-4b-e0-31 Sudo needs a password [VTE bug] "777 notify command completed" in terminal No splash screen or shutdown screen Need to decrease activity launch animation rate like xo official image does It shows "Log out" in xo menu Ctrl+Alt+F1...F5 don't work Ctrl+Alt+Backspace don't work. It can be re-enabled by setting the DontZap xorg.conf option to False OLPC specific tools missing Probably other things I haven't thought of Good luck, Ethan Nelson-Moore -------------- next part -------------- An HTML attachment was scrubbed... URL: <<a href="http://lists.sugarlabs.org/archive/soas/attachments/20171227/94057f66/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/archive/soas/attachments/20171227/94057f66/attachment-0001.html</a>> ------------------------------ Message: 2 Date: Thu, 28 Dec 2017 14:10:28 +1100 From: James Cameron <<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>> To: Development of live Sugar distributions <<a href="mailto:soas@lists.sugarlabs.org" target="_blank">soas@lists.sugarlabs.org</a>> Subject: Re: [SoaS] How to: Partially working Fedora 26 Sugar on a Stick on the XO-1 Message-ID: <<a href="mailto:20171228031028.GG7823@us.netrek.org" target="_blank">20171228031028.GG7823@us.netrek.org</a>> Content-Type: text/plain; charset=iso-8859-1 On Wed, Dec 27, 2017 at 08:33:41PM -0600, Ethan wrote: > Hello everyone, > I was able to make my own kernel 4.15 for the XO-1 in order to boot SoaS Fedora > 26 on the XO-1. Here is how I did it. I would like help fixing the > bugs. help in the form of advice below. > Instructions > -------------------------------------- > > the xo needs to be unlocked with dev key > AND update firmware to latest version otherwise new kernel doesn't boot! > > download soas i386 iso Fedora-SoaS-Live-i386-26-1.5 from > [1]<a href="http://dl.fedoraproject.org/pub/fedora-secondary/releases/26/Spins/i386/iso/" rel="noreferrer" target="_blank">http://dl.fedoraproject.org/pub/fedora-secondary/releases/26/Spins/i386/iso/</a> > > put soas i386 iso in vmware > connect 4gb+ usb drive to it and share in vmware > give yourself a name, color, grade > open terminal, run > > sudo liveinst > > select sdb1 as device > go to custom partitioning > delete all partitions > create "/" as standard, ext2! not ext3 or ext4 > set / type to standard not lvm! > change / partition label to "SoaS" EXACTLY > click update settings > click done multiple times, accept changes > click begin installation > > click root password. type olpc for root password, click done twice > make user olpc with admin, password also olpc (for compatibliity with old > activities), click done twice > > when installer done (note: it will say 100% for a long time): > close installer > > reboot vm by clicking reboot on xo guy. NOT by closing window > run in terminal > > cd /run/media/liveuser/SoaS > curl -Lo /tmp/a.zip [2]<a href="http://parrotgeek.com/downloads/xofix.zip" rel="noreferrer" target="_blank">parrotgeek.com/downloads/xofix.zip</a> > sudo unzip /tmp/a.zip > sudo cp boot/initramfs*i686.img boot/xoinitrd.img > > note: the kernel in xofix.zip is from: [3]<a href="https://github.com/parrotgeek1/" rel="noreferrer" target="_blank">https://github.com/parrotgeek1/</a> > linuxXO thanks, i'll review those patches. you might compare some of the kernel config changes against my work on this last year; <a href="http://dev.laptop.org/git/olpc-2.6/commit/?h=olpc-4.8&id=4731695ff517ccb145e60d68acd2f7f15eb4ab6b" rel="noreferrer" target="_blank">http://dev.laptop.org/git/olpc-2.6/commit/?h=olpc-4.8&id=4731695ff517ccb145e60d68acd2f7f15eb4ab6b</a> and your dcon changes look a bit like mine; <a href="https://github.com/parrotgeek1/linuxXO/commit/8d0c96ebf50b6584f027998cf334df9cd598c16b" rel="noreferrer" target="_blank">https://github.com/parrotgeek1/linuxXO/commit/8d0c96ebf50b6584f027998cf334df9cd598c16b</a> <a href="http://dev.laptop.org/git/olpc-2.6/commit/?h=olpc-4.8&id=e6f94ddd3c4227bb0367e6048f95bac5b09c9389" rel="noreferrer" target="_blank">http://dev.laptop.org/git/olpc-2.6/commit/?h=olpc-4.8&id=e6f94ddd3c4227bb0367e6048f95bac5b09c9389</a> > SHUT DOWN the vm by clicking shut down on xo guy. NOT by closing window > > do NOT reboot from the USB on a computer other than XO! > > then plug the usb into xo and boot! it should work > > ---------------------------- > > Critical Bugs: > > !!! When Xorg starts there is a weird LCD fade effect like DCON hardware is > being initialized wrong yes, i've seen that. i've no idea what caused it, but it should be easy to find using git bisect. suspect console dpms switching. > 5+ minute boot time due to firewalld, sssd failing to start. interesting, thanks. i've no idea why that should be a problem. > After login, XO sits for a very long time at only a mouse cursor, with the mic > light on you might attach serial adapter or use ssh to diagnose the system at this point. the mic light can be ignored for the moment, i think, as the audio driver has changed since we last had it working. > Screen is not scaled to 200 DPI. Attempts to copy xorg.conf from an XO image > resulted in Xorg not starting. Also, Xorg is using fbdev not geode. yes, x server has changed, you'll need to adapt the xorg.conf accordingly. also make sure a geode driver is present. > no wifi (Need firmware. Also no kernel modules are loading) yep, fix kernel module loading, fix firmware loading; which is different in later kernels to what it once was. > Impossible to open frame with mouse unless change corner size to > 5px, maybe dpi issue? you might use xdotool to print the cursor position and compare to the display dimensions shown by xdpyinfo. > Rotate button doesn't work (maybe because it isn't using geode > driver) because olpc-kbdshim isn't used. > Power management does not work at all. use olpc-powerd. > Disk and Wifi lights don't work. don't think we had disk lights working on xo-1. wifi lights will work once you have wireless firmware and libertas driver loaded. > webcam does not work (No modules are loading) once you fix module loading, you may find the ov7670 module won't work with the camera anymore, as it got changed since it last worked. hit that myself when i was looking at v4.9. > On keyboard, the increasing size dots, and 2 boxes overlapping keys > do not work use olpc-kbdshim. > Brightness keys work but super slow to change brightness in the absence of olpc-kdbshim support, sugar receives the key press event and uses a shell script to handle the keys. this is very slow, as it rises through consolekit. > it doesn't see the nand (driver loads but fail to init) that's a new bug since v4.8; jffs2 and nandflash were working fine for me then. use git bisect. > /ofw not mounted interesting. guess the driver may have been removed, or by not including olpc-utils the filesystem was not mounted. > Cosmetic bugs: > > Not asked for name at first boot, instead it is "olpc" not a bug; that's a deliberate soas feature. > Login screen shows instead of auto login not a bug; that's a deliberate soas feature. > [SoaS bug] Loading mouse cursor is the gnome one not xo one think the sugar mouse cursor was removed, as sugar steals the gnome setting, and it infects gnome desktop when it is used. have a look at the fedora packaging patches. > Hostname is localhost not like xo-4b-e0-31 that's a feature of olpc-utils, not soas. > Sudo needs a password that's a feature of olpc-utils, not soas. > [VTE bug] "777 notify command completed" in terminal that's a bug in fedora, known for years. it does not happen on debian or ubuntu. > No splash screen or shutdown screen that's a feature of olpc-powerd, not soas. > Need to decrease activity launch animation rate like xo official > image does indeed, the animation consumes most of the available processor resources; and i fixed that years ago. you can see the customisation in olpc-os-builder. > It shows "Log out" in xo menu that's a normal feature of sugar. olpc-os-builder removes it. > Ctrl+Alt+F1...F5 don't work no idea, but check the keyboard mapping, and test with chvt. > Ctrl+Alt+Backspace don't work. It can be re-enabled by setting the DontZap > xorg.conf option to False it hasn't worked for years, intentionally. > OLPC specific tools missing > Probably other things I haven't thought of yes, lots and lots. soas is not olpc os, they have diverged. > Good luck, > Ethan Nelson-Moore sounds like fun, well done! -- James Cameron <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> ------------------------------ Subject: Digest Footer _______________________________________________ SoaS mailing list <a href="mailto:SoaS@lists.sugarlabs.org" target="_blank">SoaS@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/soas" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/soas</a> ------------------------------ End of SoaS Digest, Vol 73, Issue 4 *********************************** </blockquote></div> </div></div>