Re: Firmware issu
On Tue, Aug 28, 2012 at 08:30:16AM -0400, Kevin Gordon wrote: > I believe you have something here. Something is wrong with the > Linux reboots. Perhaps it isnt shutting down 'deep enough' before > starting up again anymore. I have a theory that some of the other > discussions about date saving and the hwclock behaviour might also > be related to what is happening on a Linux reboot. I cannot get the > date change to persist to the hw clock on these XO 1.0s without > explicitly issuing the hwclock command before then doing an explicit > shutdown on these machines. A reboot doesnt work. I will increase > the testing of this to other builds and architectures on the other > 'date' thread. I agree this may represent something different about how our Linux kernel is rebooting. Could you please test with older operating system releases against the same latest firmware? Observe the power LED pattern, speaker click, and lid warning. See if it changes as you go back in time. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
12.1.0 release candidate 8 (build 21) released
Hi, We're pleased to announce the next release candidate of our new 12.1.0 software release. Information and installation instructions can be found here: http://wiki.laptop.org/go/Release_notes/12.1.0 Quick links for those who know which files need to be grabbed and save to USB disks: http://download.laptop.org/xo-1.75/os/candidate/12.1.0-21/ http://download.laptop.org/xo-1.5/os/candidate/12.1.0-21/ http://download.laptop.org/xo-1/os/candidate/12.1.0-21/ This is a signed release candidate that can be installed on all XOs, even those with security enabled. We're looking for testing and feedback on all aspects of the system. Thanks for any help you can offer, and for all the feedback that was received throughout development. This is expected to be the final release candidate before official release. Please review the "Known problems" section of the release notes. Some documented issues are carried over from previous releases, but others are new and are things that we will aim to fix in the time remaining before release. Compared to 12.1.0 release candidate 7 (build 20), we have fixed: The XO-1.5 was hanging when suspending while networking was disabled (#12043) Browse was crashing after logging into the school server moodle page for the first time (SL#3825) Some javascript-related Browse crashiness was fixed on XO-1.75 (SL#3776) Thanks! ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Impossible to set date in 11.3.0?
On Tue, Aug 28, 2012 at 2:48 PM, Martin Langhoff wrote: > You are correct, the switch to systemd means we no longer sync from > system clock to hw clock. I spotted that early, and documented it in > the release notes: > http://wiki.laptop.org/go/Release_notes/12.1.0#Base_system I'll also note that this is OT on this thread, which is about 11.3.x, based on F14, with no systemd involvement. m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Impossible to set date in 11.3.0?
On Mon, Aug 27, 2012 at 2:24 PM, Hal Murray wrote: > qu...@laptop.org said: >> "date" followed by a successful normal shutdown should work, because a >> normal shutdown runs hwclock ... but "hwclock --systohc" is handy in case >> you aren't sure that a normal shutdown will happen next. > > It used to do that on shutdown as part of /etc/rc.d/init.d/halt and friends, > but I think it got dropped as part of the switch to systemd. >grep hwclock > /etc -r< doesn't find anything. > > Does anybody know if it moved to someplace I haven't looked yet and/or if it > was deliberately dropped or just fell through the cracks? You are correct, the switch to systemd means we no longer sync from system clock to hw clock. I spotted that early, and documented it in the release notes: http://wiki.laptop.org/go/Release_notes/12.1.0#Base_system I also pestered upstream (systemd) to fix ntpdate and friends. See http://lists.freedesktop.org/archives/systemd-devel/2012-April/005023.html and https://dev.laptop.org/ticket/11483 hth, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Trac slowness diagnosis
On Thu, Aug 23, 2012 at 3:42 PM, Paul Fox wrote: > shep was just filing a ticket, and had no way of finding someone's > trac nick, based on their real name. that reminded me that we could > still use a page of some sort that lets one do that lookup. Started this page: http://wiki.laptop.org/go/Trac_usernames Perhaps people can edit and add themselves. Then a trac admin could add a link to it from the front page of trac. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Firmware issu
On Tue, Aug 28, 2012 at 2:24 AM, James Cameron wrote: > On Mon, Aug 27, 2012 at 08:21:33AM -0400, Kevin Gordon wrote: > > On Mon, Aug 27, 2012 at 1:42 AM, James Cameron wrote: > > > Q2F12 added support for automatic power down if lid is closed > > > while at ok prompt, per ticket #11095, svn 2991. If you have been > > > using previous firmware, you may never have seen this message. > > > > > > It has been a feature of XO-1.5 and XO-1.75 already. > > > > > > On XO-1, the lid switch is wired to the CS5536 companion chip, as > > > well as to the the embedded controller. Open Firmware is reading > > > from the GPIO pin array in the CS5536. Hal observed a confused > > > embedded controller or battery error may trigger this issue. > > > > > > Kevin, Robert, please remove the external power, and the main > > > battery, wait ten seconds, then reinsert both, and see if the > > > problem persists. > > > > Problem persists. > > Thanks. That test excludes insanity of the embedded controller as a > cause. > > > Just a reminder this lid message only appears upon entering firmware > > after a reboot from linux. Doesn't happen on entering "reboot" from > > firmware or a cold start. > > Interesting, thanks. It suggests the fault is in how Linux reboots, > or that Linux has changed the embedded controller behaviour. > I believe you have something here. Something is wrong with the Linux reboots. Perhaps it isnt shutting down 'deep enough' before starting up again anymore. I have a theory that some of the other discussions about date saving and the hwclock behaviour might also be related to what is happening on a Linux reboot. I cannot get the date change to persist to the hw clock on these XO 1.0s without explicitly issuing the hwclock command before then doing an explicit shutdown on these machines. A reboot doesnt work.I will increase the testing of this to other builds and architectures on the other 'date' thread. > > When you say "cold start", do you mean removal of main battery and > external power, or do you mean pressing the power button when the > power LED is off? > Either. I only ever see this spurious lid message when booting into firmware fimmediately upon doing a restart or reboot from Linux on an XO-1 with 12.1.0 and Q2F12. Happens every time on every XO 1. > > > Noted one other "symptom": when I do the reboot from firmware, I do > > hear a little 'click' as the battery LED flashes, I don't hear that > > click on the reboot from Linux. It occurs whether doing a restart > > from the GUI on Linux or entering "reboot" from terminal. > > Not interesting, but thanks. Neither the speakers nor the battery LED > have any direct connection to the lid switch. > Again, not doing any lid-switch testing at all, just mentioning any differences when rebooting into firmware from a linux reboot/restart. This is one other thing that is 'different' from a cold restart or a reboot command from firmware. > > > > If it does, please get to the ok prompt, type lid-off and press > > > enter (to stop the timer), then test the lid switch like this: > > > > > > ok lid? . cr d# 500 ms many > > > > After rebooting from Linux seeing the symptom and entering lid-off > > after entering the above command, saw > > > > fff > > fff > > fff > > fff > > . > > . > > > > > > After rebooting from firmware, and not seeing the symprom, and > > entering teh above command, saw > > 0 > > 0 > > 0 > > 0 > > > > At no time during this whole process was the lid ever closed. > > Thanks. This suggests a pullup resistor is missing, or that the > embedded controller is not managing the signal correctly. > > How many units are affected? > All XO 1's at 12.1.0 and firmware Q2F12/13 > > How many units are unaffected? > Any XO 11.3.1 or earlier with Q2E45 or earlier do not exhibit this message > > If there are some unaffected units, please provide a unit serial > number of an affected and unaffected unit, thanks. > > On Mon, Aug 27, 2012 at 08:49:55AM -0400, Kevin Gordon wrote: > > At the risk of too much info. I have also noticed that the lid-off > > message when entering firmware does not ever happen on the XO 1.5. > > Really? It should! If you close the lid or use a magnet. > Sorry, I was unclear, I dont see it on the XO 1.5 because I wasn't actually testing the lid switch, I think it works fine. :-) I'm trying to explain when I see the spurious lid switch message when entering firmware - i.e. it wouldnt actually be 'spurious' if I closed the lid or used a magnet. I do not see the spurious message on any install on the 1.5 when I do a Linux reboot/restart, ever. > > > Consistently on all machines, whether I do a shut-down or a restart > > from Linux the screen goes to text console, (last message ; dcon > > freeze) then goes to the warning screen, then goes blank. > > > > Then on the 1.5 whether doing restart/reboot from Linux or doing a > > shut-down, the power light blinks multiple times bef
Announcing Q3C09 for XO-1.5
http://wiki.laptop.org/go/OLPC_Firmware_q3c09 This release fixes a boot hang or fs-update failure if the microSD card is missing, an antenna test that can now test individual antennas, support for ISO 9660 images on USB storage, support for the new fs-load command previously released with Q4D21, and support for fs-update file size checks if olpc-os-builder is also suitably patched. Test reports are encouraged, especially of the antenna test. See http://wiki.laptop.org/go/Antenna_testing for details of that feature. This release is targeted for 12.2.0 inclusion. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Impossible to set date in 11.3.0?
It seems like all that is necessary is to add a test for a secured laptop to allow this patch to go upstream, right? (This approach looks very similar to what I did in OLPC build 603 or so.) --scott On Aug 25, 2012 7:08 PM, "Jerry Vonau" wrote: > On Sat, 2012-08-25 at 18:25 -0400, Walter Bender wrote: > > File a ticket and someone may jump in to tackle it. > > > > -walter > > > > see http://dev.laptop.org/ticket/11004 > > > > On Sat, Aug 25, 2012 at 3:24 PM, Martin Langhoff > > wrote: > > > On Sat, Aug 25, 2012 at 2:26 PM, C. Scott Ananian > wrote: > > >> Surely we can distinguish secured from unsecured laptops and allow > > >> unsecured laptops to set the date? > > > > > > Sure. Nobody's done the UI work for that, Sugar-side. > > > > > > - In all builds, hwclock is available from cli > > > - On 11.3.x and earler builds you can install the appropriate gnome > > > control panel. > > > - On 12.x.y builds, gnome control panels aren't so easy to make work, > > > 'cause they need clutter. > > > > > > Also, we should run ntp by default, or at least ntpdate on an NM hook. > > We do that in Australia builds, need nptdate to be added to the image, > setup /etc/sysconfig/ntpdate and the NM hook. > > # toggle setting the rtc > sed -i -e "s/SYNC_HWCLOCK=no/SYNC_HWCLOCK=yes/" /etc/sysconfig/ntpdate > > # call ntpdate when connected > cat << EOF > /etc/NetworkManager/dispatcher.d/10-ntpdate > #!/bin/sh > > if [ "\$2" = "up" ]; then > if [ ! -e /tmp/ntpdate ]; then > touch /tmp/ntpdate > /sbin/service ntpdate restart || : > fi > fi > EOF > chmod 755 /etc/NetworkManager/dispatcher.d/10-ntpdate > > Jerry > > > ___ > 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
