Boot on new 1.75
Hi: The deployment preparation g-ds are not being kind to me today. I have prepared about 35 XO 1.75s to go out. However, I have another 15 that are causing me new grief. The messages on boot are: USB devices: /usb@d420800/hub@0,0 OLPC 1C2, 800MHz, 1GiB memory, 4 GB internal storage, S/N SHC23500C88 Open Firmware Q4D34 EC Firmware 1.0.01 2013-09-06 00:54:24 UTC WARNING TS tag is not SHIP Type the Esc key to interrupt automatic startup Boot device: /wlan Arguments: Scan for OLPCFW not found buffer@fda3f514:0; Can't open boot device i have used the same 5 USB .sticks for the 35 that worked, and the 15 that havent. I flashed the firmware from the USB and that worked and rebooted as above I did a 4key build install using 32013o2.zd and the fs2.zip and that went through the reflash process seemed to go through fine, but the reboot comes back with the above message. The icon comes up, the sound plays, then the above messages come up. After the reflash, there are two other messages under the first /usb@d420800 /hub@0 with the same start then a /scsi@4,0 and another with a /scsi@4 ,0/disk i tried a test-all, and it seemed to go very well up to a point wherein there were a ton of IO_RW_DIRECT response=CMD state; invalid function; sdio-poll-di-ready failed. Any ideas? If it were a 1.5, I'd try to swap the SDHC card, but these are 1.75's :-) Thanks KG ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Boot on new 1.75
This is normal. You have been given units with incomplete manufacturing data. How did that happen? Please pick two units, a working unit and a failed unit, and get to the ok prompt. Type .mfg-data and compare the output. You should find you will need to: - delete the TS tag (ok delete-tag TS), - add the TS tag with a value of SHIP (ok add-tag TS SHIP), - delete the BD tag (ok delete-tag BD), Then try booting. On Thu, Sep 05, 2013 at 09:07:33PM -0400, Kevin Gordon wrote: Hi: The deployment preparation g-ds are not being kind to me today. I have prepared about 35 XO 1.75s to go out. However, I have another 15 that are causing me new grief. The messages on boot are: USB devices: /usb@d420800/hub@0,0 OLPC 1C2, 800MHz, 1GiB memory, 4 GB internal storage, S/N SHC23500C88 Open Firmware Q4D34 EC Firmware 1.0.01 2013-09-06 00:54:24 UTC WARNING TS tag is not SHIP Type the Esc key to interrupt automatic startup Boot device: /wlan Arguments: Scan for OLPCFW not found buffer@fda3f514:0; Can't open boot device i have used the same 5 USB .sticks for the 35 that worked, and the 15 that havent. I flashed the firmware from the USB and that worked and rebooted as above I did a 4key build install using 32013o2.zd and the fs2.zip and that went through the reflash process seemed to go through fine, but the reboot comes back with the above message. The icon comes up, the sound plays, then the above messages come up. After the reflash, there are two other messages under the first /usb@d420800/ hub@0 with the same start then a /scsi@4,0 and another with a /scsi@4,0/disk i tried a test-all, and it seemed to go very well up to a point wherein there were a ton of IO_RW_DIRECT response=CMD state; invalid function; sdio-poll-di-ready failed. Any ideas? If it were a 1.5, I'd try to swap the SDHC card, but these are 1.75's :-) Thanks KG ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Boot on new 1.75
On Thu, Sep 5, 2013 at 9:16 PM, James Cameron qu...@laptop.org wrote: This is normal. You have been given units with incomplete manufacturing data. How did that happen? Please pick two units, a working unit and a failed unit, and get to the ok prompt. Type .mfg-data and compare the output. You should find you will need to: - delete the TS tag (ok delete-tag TS), - add the TS tag with a value of SHIP (ok add-tag TS SHIP), - delete the BD tag (ok delete-tag BD), Then try booting. Thanks, that kind of worked, except the screen backlight keeps on dimming and brightening randomly. It does boot and connect to an AP though :-) I'll check some more units So I went back to 12.1 and same thing. Screen On Thu, Sep 05, 2013 at 09:07:33PM -0400, Kevin Gordon wrote: Hi: The deployment preparation g-ds are not being kind to me today. I have prepared about 35 XO 1.75s to go out. However, I have another 15 that are causing me new grief. The messages on boot are: USB devices: /usb@d420800/hub@0,0 OLPC 1C2, 800MHz, 1GiB memory, 4 GB internal storage, S/N SHC23500C88 Open Firmware Q4D34 EC Firmware 1.0.01 2013-09-06 00:54:24 UTC WARNING TS tag is not SHIP Type the Esc key to interrupt automatic startup Boot device: /wlan Arguments: Scan for OLPCFW not found buffer@fda3f514:0; Can't open boot device i have used the same 5 USB .sticks for the 35 that worked, and the 15 that havent. I flashed the firmware from the USB and that worked and rebooted as above I did a 4key build install using 32013o2.zd and the fs2.zip and that went through the reflash process seemed to go through fine, but the reboot comes back with the above message. The icon comes up, the sound plays, then the above messages come up. After the reflash, there are two other messages under the first /usb@d420800/ hub@0 with the same start then a /scsi@4,0 and another with a /scsi@4 ,0/disk i tried a test-all, and it seemed to go very well up to a point wherein there were a ton of IO_RW_DIRECT response=CMD state; invalid function; sdio-poll-di-ready failed. Any ideas? If it were a 1.5, I'd try to swap the SDHC card, but these are 1.75's :-) Thanks KG ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Boot on new 1.75
On Thu, Sep 05, 2013 at 09:32:18PM -0400, Kevin Gordon wrote: Thanks, that kind of worked, except the screen backlight keeps on dimming and brightening randomly. It does boot and connect to an AP though :-) I'll check some more units So I went back to 12.1 and same thing. Yes, I've seen that with clock being wrong, please check that? Also check that you have adequate ambient light in your workplace. Also please capture or check other .mfg-data output, see http://wiki.laptop.org/go/Firmware/Remote for how to do this semiautomatically for mailing. Are you on IRC? Easier to support therein. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Boot on new 1.75
logging into olpc-help ...handle is KGMAC On Thu, Sep 5, 2013 at 9:41 PM, James Cameron qu...@laptop.org wrote: On Thu, Sep 05, 2013 at 09:32:18PM -0400, Kevin Gordon wrote: Thanks, that kind of worked, except the screen backlight keeps on dimming and brightening randomly. It does boot and connect to an AP though :-) I'll check some more units So I went back to 12.1 and same thing. Yes, I've seen that with clock being wrong, please check that? Also check that you have adequate ambient light in your workplace. Also please capture or check other .mfg-data output, see http://wiki.laptop.org/go/Firmware/Remote for how to do this semiautomatically for mailing. Are you on IRC? Easier to support therein. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Boot on new 1.75
All fixed up, thanks so very much, James!! On Thu, Sep 5, 2013 at 10:04 PM, Kevin Gordon kgordon...@gmail.com wrote: logging into olpc-help ...handle is KGMAC On Thu, Sep 5, 2013 at 9:41 PM, James Cameron qu...@laptop.org wrote: On Thu, Sep 05, 2013 at 09:32:18PM -0400, Kevin Gordon wrote: Thanks, that kind of worked, except the screen backlight keeps on dimming and brightening randomly. It does boot and connect to an AP though :-) I'll check some more units So I went back to 12.1 and same thing. Yes, I've seen that with clock being wrong, please check that? Also check that you have adequate ambient light in your workplace. Also please capture or check other .mfg-data output, see http://wiki.laptop.org/go/Firmware/Remote for how to do this semiautomatically for mailing. Are you on IRC? Easier to support therein. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel