Re: [support-gang] Customization Sticks fails on 13.1.0 & 12.1.0 for XO-1
On 03/11/2013 10:48 PM, John Watlington wrote: That policy is fine but perhaps needs to be more visible to the people going into areas where secure laptops were distributed and we should try to be helpful to those people when they request developer keys. If someone isn't being helpful about providing developer keys, let me know. No specific instances that I know of but for some of these people its a daunting task especially if they have limited Internet. Just a friendly reminder that some of these people may need a bit of hand holding. I know because I've helped several of them in the past and sometimes it can be a bit frustrating. :) -- Richard A. Smith One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] Customization Sticks fails on 13.1.0 & 12.1.0 for XO-1
On Mar 11, 2013, at 10:44 PM, Richard A. Smith wrote: > On 03/11/2013 10:08 PM, John Watlington wrote: > >> Please don't redistribute secure laptops --- OLPC's policy since early 2009 >> has >> been to deprecate the security system. The exceptions have been deployments >> "large" enough to have dedicated support staff capable of handling their own >> keys. > > That policy is fine but perhaps needs to be more visible to the people going > into areas where secure laptops were distributed and we should try to be > helpful to those people when they request developer keys. If someone isn't being helpful about providing developer keys, let me know. wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] Customization Sticks fails on 13.1.0 & 12.1.0 for XO-1
On 03/11/2013 10:08 PM, John Watlington wrote: Nod. Kejector for small deployments is new to me. I thought keyjector was only for special cases. I don't think most of the folks on say the support-gang list have any idea that keyjector is an option for them. I don't think it is an option. A keyjector should not be made publicly available. That is more along the line of what I thought was status quo. Please don't redistribute secure laptops --- OLPC's policy since early 2009 has been to deprecate the security system. The exceptions have been deployments "large" enough to have dedicated support staff capable of handling their own keys. That policy is fine but perhaps needs to be more visible to the people going into areas where secure laptops were distributed and we should try to be helpful to those people when they request developer keys. The point of my comments was clarification that olpc-os-builder is not an end all solution to the lack of the customization key not working anymore and should not be offered up as such. Doing customization by a bash script after boot is a fine solution and now people can invest time in polishing that script. -- Richard A. Smith One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] Customization Sticks fails on 13.1.0 & 12.1.0 for XO-1
On Mar 11, 2013, at 1:54 PM, Richard A. Smith wrote: > On 03/11/2013 10:26 AM, Daniel Drake wrote: > >>> would have to be signed by OLPC or Reuben would have to give them a Haiti >>> key thats installed via keyjector. >> >> This is not a new situation for us, and the approach we have taken in >> the past is to help such deployments un-secure all of their laptops, >> or provide a keyjector to insert custom keys, upon their request. > > Nod. Kejector for small deployments is new to me. I thought keyjector was > only for special cases. > > I don't think most of the folks on say the support-gang list have any idea > that keyjector is an option for them. I don't think it is an option. A keyjector should not be made publicly available. Please don't redistribute secure laptops --- OLPC's policy since early 2009 has been to deprecate the security system. The exceptions have been deployments "large" enough to have dedicated support staff capable of handling their own keys. wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Possible fix for Gray dots forever problem
This bug is is Trac #12618 When Nancie was at Twine she left me an XO-1 with this condition. Based on Adams observation that laptops in this state also seem to ignore the power button I suspected that powerd problems were the root cause. The root of the problem appears to be that the system date on the affected laptop was set to sometime in 1968. This date is prior to the unix epoch date of 1970 and therefore all the timestamps were negative causing powerd to ignore all events. Updating the system date to be current fixed both problems. The mechanism for how this happens is currently unknown. In general the Linux kernel on our machines ignores the century field from the RTC and adds 2000 to the year value. I was unable to find a setting of the RTC that would make linux read 1968 for the date. The proposed fix is to either set the date from OFW using ok ntp-set-clock (you need a valid wifi or USB ethernet network) or by using the check key to boot to linux and doing: date --utc --set="-MM-DD HH:MM:SS" hwclock --systohc The hwclock --systohc is necessary because 'date' only updates the systemclock and not the RTC. If this fixes it I would recommend a reinstall of the OS after you do this to reset the date on a lot of files that that created when the OS first boots. The funky date may cause other problems yet undiscovered. Nancie: You can help us figure out how this happens. Before you try to fix your machines that have this problem please boot them (holding the check button) and look to see what the system date is set to. Load up terminal and run 'date' If the year is less than 1970 please do the following: dmesg > dmesg-n.log (where n is a number for each log file) sudo hwclock -r Send me the dmesg output files and the dates reported by hwclock If the date is not less than 1970 please hold that machine for further inspection. Hope this helps. -- Richard A. Smith One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] Customization Sticks fails on 13.1.0 & 12.1.0 for XO-1
On 03/11/2013 10:26 AM, Daniel Drake wrote: would have to be signed by OLPC or Reuben would have to give them a Haiti key thats installed via keyjector. This is not a new situation for us, and the approach we have taken in the past is to help such deployments un-secure all of their laptops, or provide a keyjector to insert custom keys, upon their request. Nod. Kejector for small deployments is new to me. I thought keyjector was only for special cases. I don't think most of the folks on say the support-gang list have any idea that keyjector is an option for them. -- Richard A. Smith One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] gray dots forever: when 12.1.0 & 13.1.0 never fully boot (XO-1 especially? 11.3.1 too)
On Mon, Mar 11, 2013 at 10:31 AM, Nancie Severs wrote: > I had it with a brand new blue high school XO-1.5 (that booted normally > before I flashed it to 12.1.0). I took that one to the Boston office & > Richard Smith watched the boot and figured out the work around. Adam has it > for Haiti now. I have XO-1's that do this that I can provide to someone to > hook up & log as you suggest. And I have a few new 1.5's that we can try and > reproduce it on also, if helpful. My point is that the problem is not > limited to the XO-1s. > > Richard, would it be helpful for me to bring some affected XOs down to the > office if I can get to Boston later this week? That would be excellent, we'd just have to make sure that Richard and I have time to work through this at the right moment. Would you be leaving XOs there for a day or two, or would you need to take them away with you when you leave a couple of hours later? We won't be able to diagnose anything if we can't reproduce the problem of course, and it sounds like that at least today you are having trouble hitting this. That would complicate things. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] Customization Sticks fails on 13.1.0 & 12.1.0 for XO-1
On Sun, Mar 10, 2013 at 12:58 PM, Richard A. Smith wrote: > Perhaps I don't understand but I don't see how OOB can work for a setup like > Adam is describing in Haiti where they have laptops in the mix that are > secure. Unless they first un-secure every laptop a custom OS build wth OOB > would have to be signed by OLPC or Reuben would have to give them a Haiti > key thats installed via keyjector. This is not a new situation for us, and the approach we have taken in the past is to help such deployments un-secure all of their laptops, or provide a keyjector to insert custom keys, upon their request. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: gray dots forever: when 12.1.0 & 13.1.0 never fully boot (XO-1 especially? 11.3.1 too)
Hi, On Sun, Mar 10, 2013 at 2:41 PM, Holt wrote: > On 3/10/2013 3:39 PM, Nancie Severs wrote: > > Going to 12 and 13, I am still getting a % of XOs that get stuck at the grey > dots when booting after the reflash is complete. Richard Smith figured out > that this is a Pretty Boot issue. He had a workaround that worked on an XO > 1.5, but I have not been successful had getting that to work on an XO 1.0. > > > I've the same issue with an XO-1 running Release 11.3.1 -- it was previously > running March 6th's 13.1.0 > > Now it freezes at the end of prettyboot (once all grey dots have formed a > circle). I think this is the first report we have of this issue. To diagnose further, it would be good if someone could hook up a serial console and log the boot messages. I know it's not trivial to have this available, but I can't think of other debugging approaches. Also, it is always helpful to know at exactly which point the system hangs. In Adam's case this was stated clearly (I interpret: once all the dots in the circle go dark grey after they have 'spun around' for a while) but in Nancie's case it wasn't. The other thing to keep in mind is that first boot takes longer than subsequent boot. So be sure to have a little patience before declaring the system as hung. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
