Re: Activation problems
If the icons are flashing, the firmware is already out of the picture. John Watlington wrote: I have two laptops here in Peru that refuse to activate. I have generated leases for (increasingly) 7 days, 3000 days, and 7999 days, and none work. I activated three other laptops using the same key/activation request and they work fine. They boot up and don't give any error messages. They just start flashing the SD, USB, and finally WiFi icons. When activating, they don't give any error message, they just say Powering off in 10 seconds. Any suggestions ? wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Activation problems
C. Scott Ananian wrote: On Mon, Apr 28, 2008 at 2:16 PM, John Watlington [EMAIL PROTECTED] wrote: You can try to search the SN of the laptops you're trying to activate in the lease.sig file to see if they're there... The activation leases in the lease.sig file seem fine. And I'm using a collector key to get the serial number/UUID, so I don't expect that it is a modified UUID causing the problem. The collector key also puts the laptop's idea of the current time in the laptops.dat file; you might check that it doesn't think it's living in 2037. Switching to VT1 will also tell you if python is throwing any errors or exceptions that might be relevant. Trying to generate a dev key (as Richard suggested) may also help diagnose the issue (bad UUID, bad key, etc). Finally, there were firmware changes made at one point which affect OFW's ability to read nand:/security. It's not entirely clear from your description, but if the machine boots successfully with the activation key in, but won't boot w/o the activation key, it could be firmware-related. Otherwise, Mitch seems correct that this doesn't look to be a firmware issue. --scott Richard's suggestion of holding the check key will give valuable clues about what the firmware is seeing during its portion of the process. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Activation problems
John Watlington wrote: When I reboot (after activating), it reports that the lease in nand:\security\lease.sig is expired. Then it finds valid signatures for the OS and proceeds. Can you get a developer key? If so, type: ok .clock ok more nand:\security\lease.sig ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Activation problems
Are you using a pendrive with the leases to activate the laptops? Or are you trying wireless? Which build are you using? You can try to search the SN of the laptops you're trying to activate in the lease.sig file to see if they're there... Emiliano On Mon, Apr 28, 2008 at 3:04 PM, John Watlington [EMAIL PROTECTED] wrote: I have two laptops here in Peru that refuse to activate. I have generated leases for (increasingly) 7 days, 3000 days, and 7999 days, and none work. I activated three other laptops using the same key/activation request and they work fine. They boot up and don't give any error messages. They just start flashing the SD, USB, and finally WiFi icons. When activating, they don't give any error message, they just say Powering off in 10 seconds. Any suggestions ? wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Emiliano Pastorino LATU - Plan Ceibal Av. Italia 6201 CP: 11500, Montevideo, Uruguay Tel: (598 2) 601 3724 int.: 469 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Activation problems
John Watlington wrote: They boot up and don't give any error messages. They just start flashing the SD, USB, and finally WiFi icons. When activating, they don't give any error message, they just say Powering off in 10 seconds. If you hold the check key during boot it shows some diags. Any suggestions ? Try a developer key. Then boot and go look at the file system and verify your lease file is correct and valid. -- Richard Smith [EMAIL PROTECTED] One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Activation problems
On Mon, Apr 28, 2008 at 2:16 PM, John Watlington [EMAIL PROTECTED] wrote: You can try to search the SN of the laptops you're trying to activate in the lease.sig file to see if they're there... The activation leases in the lease.sig file seem fine. And I'm using a collector key to get the serial number/UUID, so I don't expect that it is a modified UUID causing the problem. The collector key also puts the laptop's idea of the current time in the laptops.dat file; you might check that it doesn't think it's living in 2037. Switching to VT1 will also tell you if python is throwing any errors or exceptions that might be relevant. Trying to generate a dev key (as Richard suggested) may also help diagnose the issue (bad UUID, bad key, etc). Finally, there were firmware changes made at one point which affect OFW's ability to read nand:/security. It's not entirely clear from your description, but if the machine boots successfully with the activation key in, but won't boot w/o the activation key, it could be firmware-related. Otherwise, Mitch seems correct that this doesn't look to be a firmware issue. --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Activation problems
On Apr 28, 2008, at 2:37 PM, C. Scott Ananian wrote: On Mon, Apr 28, 2008 at 2:16 PM, John Watlington [EMAIL PROTECTED] wrote: You can try to search the SN of the laptops you're trying to activate in the lease.sig file to see if they're there... The activation leases in the lease.sig file seem fine. And I'm using a collector key to get the serial number/UUID, so I don't expect that it is a modified UUID causing the problem. The collector key also puts the laptop's idea of the current time in the laptops.dat file; you might check that it doesn't think it's living in 2037. It shows that both laptops think it is roughly today (4/28 or 4/29 2008). Switching to VT1 will also tell you if python is throwing any errors or exceptions that might be relevant. It boots for a while, then prints *** Activating *** mount: Mounting x on /mnt/xxx failed: No such device or address (a number of times for the expected values of ) FATAL: module ipv6 not found Trying to generate a dev key (as Richard suggested) may also help diagnose the issue (bad UUID, bad key, etc). I'll try this next. Finally, there were firmware changes made at one point which affect OFW's ability to read nand:/security. It's not entirely clear from your description, but if the machine boots successfully with the activation key in, but won't boot w/o the activation key, it could be firmware-related. If I boot with the activation inserted, it always powers off in 10 sec. How do I boot with activation key inserted ? Otherwise, Mitch seems correct that this doesn't look to be a firmware issue. --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Activation problems
RTFM. It looks like most of the problem was not deleting the boot directory on the key. Why this worked for 3 of five laptops, but not these last two, I don't know... On Apr 28, 2008, at 3:02 PM, C. Scott Ananian wrote: On Mon, Apr 28, 2008 at 2:53 PM, John Watlington [EMAIL PROTECTED] wrote: When I reboot (after activating), it reports that the lease in nand:\security\lease.sig is expired. Then it finds valid signatures for the OS and proceeds. That's very interesting. Once you have a dev key, can you ask OFW what's actually in nand:\security\lease.sig? Does it look reasonable? It is writable? If you could also note the mounting XYZ on /mnt options that are tried; the process should look like this: * try /dev/mmcblk0p1 (partitioned SD card) * /dev/mmcblk0 (unpartitioned SD card) * /dev/sdX for X in ['a1','a','b1','b','c1','c','b1','b','a1','a'] (we expect /dev/sda1 to work, so we try it again at the end in case the USB disk just took a while to be recognized) * wireless on channels 1, 6, 11, 1, 6, 11 If it doesn't make it all the way through this process, then what it likely happening is that it is successfully finding the lease and then failing to write it to NAND. So knowing how far it gets through this is useful. --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Activation problems
If you insert the key after the machine boots, then it shouldn't have been a problem having a /boot directory. A possible explanation of the inconsistent behavior could be when in the boot process you insert the key. -walter On Mon, Apr 28, 2008 at 3:07 PM, John Watlington [EMAIL PROTECTED] wrote: RTFM. It looks like most of the problem was not deleting the boot directory on the key. Why this worked for 3 of five laptops, but not these last two, I don't know... On Apr 28, 2008, at 3:02 PM, C. Scott Ananian wrote: On Mon, Apr 28, 2008 at 2:53 PM, John Watlington [EMAIL PROTECTED] wrote: When I reboot (after activating), it reports that the lease in nand:\security\lease.sig is expired. Then it finds valid signatures for the OS and proceeds. That's very interesting. Once you have a dev key, can you ask OFW what's actually in nand:\security\lease.sig? Does it look reasonable? It is writable? If you could also note the mounting XYZ on /mnt options that are tried; the process should look like this: * try /dev/mmcblk0p1 (partitioned SD card) * /dev/mmcblk0 (unpartitioned SD card) * /dev/sdX for X in ['a1','a','b1','b','c1','c','b1','b','a1','a'] (we expect /dev/sda1 to work, so we try it again at the end in case the USB disk just took a while to be recognized) * wireless on channels 1, 6, 11, 1, 6, 11 If it doesn't make it all the way through this process, then what it likely happening is that it is successfully finding the lease and then failing to write it to NAND. So knowing how far it gets through this is useful. --scott -- ( http://cscott.net/ ) ___ 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
