Re: ANNOUNCE: F11 for the XO-1 build 140py released
I have observed this problem a couple of times, although only after reflashing the OS. The machine would hang after displaying the frame of the boot animation with just one dot. So far, if I've been running a machine, and it has hung -- and if it doesn't want to reboot -- I will do the EC reset thing (unplug the AC, take out the battery for a couple of minutes). If an EC reset might be required also after reflashing the OS, then the person doing the reflashing ought to be warned somehow (Release notes? Wiki?). My reason for mentioning the hang I saw was that I had not been expecting a reflash to require an EC reset to make the os boot work. Please, take note of how you triggered it and how exactly you managed to solve it. I triggered it by doing a 'copy-nand u:\os140py.img', then powering off, pulling the USB stick, and powering on (while pressing the 'check' game button). [I already was using q2e42e from before doing the reflash.] I never solved it - I repeated the power-up (I think twice) - and finally the boot worked. [Never did any explicit EC reset.] mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ANNOUNCE: F11 for the XO-1 build 140py released
yioryos wrote: --- On Wed, 4/14/10, Mikus Grinbergs mi...@bga.com wrote: If not present, OFW (q2e42e) gave the message No signature for our key list My XO-1 has security disabled and boots fine. With the exception of the first boot that something on olpc.fth blocks it (with no OFW messages) and never goes to console. what changed between the first and second boots that might have made the second successful after the first failed? paul Regarding the freeze at the camera-check boot point, I had it with os129py (not with os140py yet) but I considered it a consequence of my broken camera. Maybe not then. =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ANNOUNCE: F11 for the XO-1 build 140py released
--- On Thu, 4/15/10, Paul Fox p...@laptop.org wrote: From: Paul Fox p...@laptop.org Subject: Re: ANNOUNCE: F11 for the XO-1 build 140py released To: Yioryos Asprobounitis mavrot...@yahoo.com Cc: OLPC Devel devel@lists.laptop.org, Fedora OLPC List fedora-olpc-l...@redhat.com Date: Thursday, April 15, 2010, 8:12 AM yioryos wrote: --- On Wed, 4/14/10, Mikus Grinbergs mi...@bga.com wrote: If not present, OFW (q2e42e) gave the message No signature for our key list My XO-1 has security disabled and boots fine. With the exception of the first boot that something on olpc.fth blocks it (with no OFW messages) and never goes to console. what changed between the first and second boots that might have made the second successful after the first failed? See http://lists.laptop.org/pipermail/devel/2010-April/028172.html above :-) To repeat, I loaded the olpc.fth from my SDcard instead the internal NAND. It looked like that: \ Boot script root=/dev/mtdblock0 rootfstype=jffs2 console=ttyS0,115200 console=tty0 fbcon=font:SUN12x22 selinux=0 to boot-file nand:\boot\vmlinuz to boot-device nand:\boot\initrd.img to ramdisk setup-smbios unfreeze dcon-unfreeze visible boot Set up os140py. Removed the SDcard and rebooted. paul Regarding the freeze at the camera-check boot point, I had it with os129py (not with os140py yet) but I considered it a consequence of my broken camera. Maybe not then. =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ANNOUNCE: F11 for the XO-1 build 140py released
yioryos wrote: --- On Thu, 4/15/10, Paul Fox p...@laptop.org wrote: From: Paul Fox p...@laptop.org Subject: Re: ANNOUNCE: F11 for the XO-1 build 140py released To: Yioryos Asprobounitis mavrot...@yahoo.com Cc: OLPC Devel devel@lists.laptop.org, Fedora OLPC List fedora-olpc-l...@redhat.com Date: Thursday, April 15, 2010, 8:12 AM yioryos wrote: --- On Wed, 4/14/10, Mikus Grinbergs mi...@bga.com wrote: If not present, OFW (q2e42e) gave the message No signature for our key list My XO-1 has security disabled and boots fine. With the exception of the first boot that something on olpc.fth blocks it (with no OFW messages) and never goes to console. what changed between the first and second boots that might have made the second successful after the first failed? See http://lists.laptop.org/pipermail/devel/2010-April/028172.html above :-) To repeat, I loaded the olpc.fth from my SDcard instead the internal NAND. It looked like that: \ Boot script root=/dev/mtdblock0 rootfstype=jffs2 console=ttyS0,115200 console=tty0 fbcon=font:SUN12x22 selinux=0 to boot-file nand:\boot\vmlinuz to boot-device nand:\boot\initrd.img to ramdisk setup-smbios unfreeze dcon-unfreeze visible boot Set up os140py. Removed the SDcard and rebooted. so one possibility is that os140py isn't successfully enabling smbios, or not recognizing the results correctly. what firmware is installed on our XO-1? and -- question for bernie -- does os140py include a new firmware? paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ANNOUNCE: F11 for the XO-1 build 140py released
On 15 April 2010 09:48, Yioryos Asprobounitis mavrot...@yahoo.com wrote: what changed between the first and second boots that might have made the second successful after the first failed? See http://lists.laptop.org/pipermail/devel/2010-April/028172.html above This sounds like http://dev.laptop.org/ticket/9100 Your workaround is interesting. For me, this bug isn't specific to first boot, it's a from-time-to-time type thing. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ANNOUNCE: F11 for the XO-1 build 140py released
On 15 April 2010 10:01, Paul Fox p...@laptop.org wrote: so one possibility is that os140py isn't successfully enabling smbios, or not recognizing the results correctly. (assuming this bug is indeed an instance of #9100...) SMBIOS should not be required for not-crashing during early boot. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ANNOUNCE: F11 for the XO-1 build 140py released
--- On Thu, 4/15/10, Paul Fox p...@laptop.org wrote: From: Paul Fox p...@laptop.org Subject: Re: ANNOUNCE: F11 for the XO-1 build 140py released To: Yioryos Asprobounitis mavrot...@yahoo.com Cc: OLPC Devel devel@lists.laptop.org, Fedora OLPC List fedora-olpc-l...@redhat.com Date: Thursday, April 15, 2010, 9:01 AM yioryos wrote: --- On Thu, 4/15/10, Paul Fox p...@laptop.org wrote: From: Paul Fox p...@laptop.org Subject: Re: ANNOUNCE: F11 for the XO-1 build 140py released To: Yioryos Asprobounitis mavrot...@yahoo.com Cc: OLPC Devel devel@lists.laptop.org, Fedora OLPC List fedora-olpc-l...@redhat.com Date: Thursday, April 15, 2010, 8:12 AM yioryos wrote: --- On Wed, 4/14/10, Mikus Grinbergs mi...@bga.com wrote: If not present, OFW (q2e42e) gave the message No signature for our key list My XO-1 has security disabled and boots fine. With the exception of the first boot that something on olpc.fth blocks it (with no OFW messages) and never goes to console. what changed between the first and second boots that might have made the second successful after the first failed? See http://lists.laptop.org/pipermail/devel/2010-April/028172.html above :-) To repeat, I loaded the olpc.fth from my SDcard instead the internal NAND. It looked like that: \ Boot script root=/dev/mtdblock0 rootfstype=jffs2 console=ttyS0,115200 console=tty0 fbcon=font:SUN12x22 selinux=0 to boot-file nand:\boot\vmlinuz to boot-device nand:\boot\initrd.img to ramdisk setup-smbios unfreeze dcon-unfreeze visible boot Set up os140py. Removed the SDcard and rebooted. so one possibility is that os140py isn't successfully enabling smbios, or not recognizing the results correctly. I'm not sure. It should not work in subsequent boots also then. No? Looks like that needs something that is provided by the OS/initrd (/ofw?) but is generated after the first successful run. what firmware is installed on our XO-1? as said (:-) q2e42d and -- question for bernie -- does os140py include a new firmware? Did not offer to upgrade the FW at any point (initial or later boots) though it was plugged for that exact reason. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ANNOUNCE: F11 for the XO-1 build 140py released
--- On Thu, 4/15/10, Daniel Drake d...@laptop.org wrote: From: Daniel Drake d...@laptop.org Subject: Re: ANNOUNCE: F11 for the XO-1 build 140py released To: Yioryos Asprobounitis mavrot...@yahoo.com Cc: Paul Fox p...@laptop.org, OLPC Devel devel@lists.laptop.org, Fedora OLPC List fedora-olpc-l...@redhat.com Date: Thursday, April 15, 2010, 9:06 AM On 15 April 2010 09:48, Yioryos Asprobounitis mavrot...@yahoo.com wrote: what changed between the first and second boots that might have made the second successful after the first failed? See http://lists.laptop.org/pipermail/devel/2010-April/028172.html above This sounds like http://dev.laptop.org/ticket/9100 Your workaround is interesting. For me, this bug isn't specific to first boot, it's a from-time-to-time type thing. os140py only has half a dozen reboots so far but the problem did not reappear. Also it _might_ be different than #9100 since pressing the power button turns the XO off almost immediately. When in kernel land I have the feeling it takes a bit longer (from my mess-ups with different distros, kernels and initrds :-). Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ANNOUNCE: F11 for the XO-1 build 140py released
On Wed, 2010-04-14 at 17:08 -0500, Mikus Grinbergs wrote: Was unable to boot XO-1 with build140py installed on jffs2, unless develop.sig was present. If not present, OFW (q2e42e) gave the message No signature for our key list I think Stephen Parrish is preparing to release an F11-XO1 image signed with OLPC's private key. If deployments ask for it, I can provide instructions for creating OS images similar to ours, but signed with their private keys. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ANNOUNCE: F11 for the XO-1 build 140py released
On Wed, 2010-04-14 at 17:54 -0500, Mikus Grinbergs wrote: I usually bring the system up with messages being displayed (NOT in pretty-boot). Several times now, the system has paused/hung at about the time it should be running through /etc/rc.d/rc0.d (or suchlike). [Note: the camera LED is on.] After SEVERAL MINUTES nothing more has happened - so I just reboot. [I can not bring up a text console, so I can't take a dump.] The hang is random - so the next boot usually works. As far as I am concerned, if the machines in the field also encounter this hang -- it is a blocker to the release of build 140py. I have observed this problem a couple of times, although only after reflashing the OS. The machine would hang after displaying the frame of the boot animation with just one dot. In my case, a simple reboot would not cure the problem. Pulling the battery did the job. Therefore, I suspect it may be caused by upgrading the EC code, which wouldn't be a big concern since we have found an easy workaround. Let me know if you see it again on laptops that are already running the latest open firmware code. Please, take note of how you triggered it and how exactly you managed to solve it. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ANNOUNCE: F11 for the XO-1 build 140py released
--- On Thu, 4/15/10, Bernie Innocenti ber...@codewiz.org wrote: From: Bernie Innocenti ber...@codewiz.org Subject: Re: ANNOUNCE: F11 for the XO-1 build 140py released To: Paul Fox p...@laptop.org Cc: Yioryos Asprobounitis mavrot...@yahoo.com, OLPC Devel devel@lists.laptop.org, Fedora OLPC List fedora-olpc-l...@redhat.com Date: Thursday, April 15, 2010, 8:33 PM On Thu, 2010-04-15 at 09:01 -0400, Paul Fox wrote: and -- question for bernie -- does os140py include a new firmware? Yes, it includes q2e42d. It works on all our laptops, and smbios is enabled. Yioryos, did you have AC plugged in when you flashed your laptop? Yes. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ANNOUNCE: F11 for the XO-1 build 140py released
--- On Wed, 4/14/10, Bernie Innocenti ber...@codewiz.org wrote: From: Bernie Innocenti ber...@codewiz.org Subject: ANNOUNCE: F11 for the XO-1 build 140py released To: OLPC Devel devel@lists.laptop.org Cc: IAEP i...@lists.sugarlabs.org, Fedora OLPC List fedora-olpc-l...@redhat.com Date: Wednesday, April 14, 2010, 12:22 PM This is a custom OS image for the XO-1 released by the Paraguay Educa technology team: http://people.sugarlabs.org/bernie/olpc/f11-xo1-py/os140py.img http://people.sugarlabs.org/bernie/olpc/f11-xo1-py/os140py.crc http://people.sugarlabs.org/bernie/olpc/f11-xo1-py/os140py.img.fs.zip Downloaded and installed twice but failed to boot. Stopped at loading olpcrd.img... every time However, booting with a simple olpc.fth in an SDcard, booted fine and after setting up the os (user/icon/network) subsequent reboots with the NAND olpc.fth worked fine. This is on an XO-1, CL1, with q2e42d. A very fast run through the activities revealed 2 issues. Record activity spits a Cannot find cached 0sugar launch implementation error. I guess something was left out in the build. Ruler activity, is out of scale (~half of the proper). I guess the XO screen resolution was not considered appropriately? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ANNOUNCE: F11 for the XO-1 build 140py released
Was unable to boot XO-1 with build140py installed on jffs2, unless develop.sig was present. If not present, OFW (q2e42e) gave the message No signature for our key list mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ANNOUNCE: F11 for the XO-1 build 140py released
I usually bring the system up with messages being displayed (NOT in pretty-boot). Several times now, the system has paused/hung at about the time it should be running through /etc/rc.d/rc0.d (or suchlike). [Note: the camera LED is on.] After SEVERAL MINUTES nothing more has happened - so I just reboot. [I can not bring up a text console, so I can't take a dump.] The hang is random - so the next boot usually works. As far as I am concerned, if the machines in the field also encounter this hang -- it is a blocker to the release of build 140py. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ANNOUNCE: F11 for the XO-1 build 140py released
--- On Wed, 4/14/10, Mikus Grinbergs mi...@bga.com wrote: From: Mikus Grinbergs mi...@bga.com Subject: Re: ANNOUNCE: F11 for the XO-1 build 140py released To: Bernie Innocenti ber...@codewiz.org Cc: OLPC Devel devel@lists.laptop.org, Fedora OLPC List fedora-olpc-l...@redhat.com Date: Wednesday, April 14, 2010, 6:08 PM Was unable to boot XO-1 with build140py installed on jffs2, unless develop.sig was present. If not present, OFW (q2e42e) gave the message No signature for our key list My XO-1 has security disabled and boots fine. With the exception of the first boot that something on olpc.fth blocks it (with no OFW messages) and never goes to console. Regarding the freeze at the camera-check boot point, I had it with os129py (not with os140py yet) but I considered it a consequence of my broken camera. Maybe not then. mikus ___ olpc mailing list o...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/olpc ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
