Re: [Testing] 11.3.0 release candidate 3 (build 882) released
On Sat, Oct 22, 2011 at 5:06 AM, Gary Martin garycmar...@googlemail.com wrote: I just wondered if this XO-1 backlight power saving issue has made it onto anyone else's radar, or if I should be setting some special trac flag/keyword? Seems a shame to regress on a basic XO-1 power saving feature. https://dev.laptop.org/ticket/11304 Thanks for drawing our attention to this. This was disabled by Martin in http://dev.laptop.org/git/projects/olpc-utils/commit/?id=78cda69a7e9b41d331426d266bde45d261729047 Martin, can you explain why this change was extended to XO-1? Thanks, Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] 11.3.0 release candidate 3 (build 882) released
My thinking was along the lines of Paul's in his comment in #11304:
consistently disable DPMS/blanking/etc from X hooks, and let powerd
consistently control it, across all platforms.
Is it a powerd bug that it doesn't DTRT on XO-1? Or maybe there's a
limitation on XO-1 (maybe the kernel we ship doesn't expose the right
controls to powerd...) and it makes sense to rely on DPMS there...
In any case, I didn't do it with any special knowledge of XO-1 specifics. I
was just trying to make code and behaviour consistent across hw platforms.
Which may well been a naive move.
cheers,
m
{ Martin Langhoff - one laptop per child }
On Oct 25, 2011 3:38 PM, Daniel Drake d...@laptop.org wrote:
On Sat, Oct 22, 2011 at 5:06 AM, Gary Martin garycmar...@googlemail.com
wrote:
I just wondered if this XO-1 backlight power saving issue has made it
onto anyone else's radar, or if I should be setting some special trac
flag/keyword? Seems a shame to regress on a basic XO-1 power saving feature.
https://dev.laptop.org/ticket/11304
Thanks for drawing our attention to this.
This was disabled by Martin in
http://dev.laptop.org/git/projects/olpc-utils/commit/?id=78cda69a7e9b41d331426d266bde45d261729047
Martin, can you explain why this change was extended to XO-1?
Thanks,
Daniel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: [Testing] 11.3.0 release candidate 3 (build 882) released
On Tue, Oct 25, 2011 at 6:54 PM, Martin Langhoff mar...@laptop.org wrote: My thinking was along the lines of Paul's in his comment in #11304: consistently disable DPMS/blanking/etc from X hooks, and let powerd consistently control it, across all platforms. Is it a powerd bug that it doesn't DTRT on XO-1? Or maybe there's a limitation on XO-1 (maybe the kernel we ship doesn't expose the right controls to powerd...) and it makes sense to rely on DPMS there... In any case, I didn't do it with any special knowledge of XO-1 specifics. I was just trying to make code and behaviour consistent across hw platforms. Which may well been a naive move. The only specifics I know of is that originally the geode Xorg driver had code to control the DCON in the DPMS hooks. When the question came back up for the XO 1.5 I suggested removing the DPMS out of the question all together and just handle everything through powerd. My preference was to limit the moving pieces a bit, with the downside being custom distros would have to adopt powerd or fend for themselves. I think as a platform this decision is working well and we should keep it consistent across the different models. -Jon ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] 11.3.0 release candidate 3 (build 882) released
On Fri, Oct 21, 2011 at 10:43:13PM -0700, rihowa...@gmail.com wrote: 155a68922bc7e3fea323d400eaf3e99a u:\q2e48.rom Thanks, that is the correct md5sum. q2e46 is the OFW currently installed on this XO-1 Thanks. That version may not report exceptions that occur during USB operations. That version may also not properly read files on certain ext2 filesystems. If the file cannot be fully read, the length that is read is compared against the expected length, and if they are unequal then you get Image file is the wrong length. This is safer than using the shorter than expected data as is. So I tried flash u:\q2e48.rom again after running the md5sum.fth and this time the OFW flash worked Good. It seems the problem you had was temporary, and it was likely to be related to either the USB drive, or the filesystem that is on the drive. If you would like to explore further, you may wish to try exercising md5sum on various USB drives, filesystems, and files. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] 11.3.0 release candidate 3 (build 882) released
Hi Daniel, On 21 Oct 2011, at 19:53, Daniel Drake wrote: Hi, We're pleased to announce our third release candidate of our new 11.3.0 software release. Information and installation instructions can be found here: http://wiki.laptop.org/go/Release_notes/11.3.0 Quick links for those who know which files need to be grabbed and save to USB disks: http://download.laptop.org/xo-1/os/candidate/882/ I just wondered if this XO-1 backlight power saving issue has made it onto anyone else's radar, or if I should be setting some special trac flag/keyword? Seems a shame to regress on a basic XO-1 power saving feature. https://dev.laptop.org/ticket/11304 Regards, --Gary http://download.laptop.org/xo-1.5/os/candidate/882/ http://download.laptop.org/xo-1.75/os/candidate/882/ 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. Our scheduled release date is November 1st. 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 few weeks before release, including: XO-1.75 Sound does not work in many activities (ticket #11296). There is no suspend/resume support yet. There is slight mouse cursor visual corruption in Sugar, and the mouse cursor in GNOME appears odd, but is otherwise functional. Sometimes, part of the screen may not redraw correctly, such as Sugar's neighborhood view after dismissing the wireless security dialog (ticket #11273) XO-1 users: we have identified a bug in the firmware releases shipped during 11.3.0 development and in earlier 11.3.0 release candidates. Affected versions are Q2E46 and Q2E47. You can check which version you are running in the Sugar 'Settings' dialog. Unfortunately, a bug in the firmware update code means that these firmware versions will not automatically upgrade to newer versions. We have fixed this in Q2E48 (included in 11.3.0 build 882 onwards), but existing users of Q2E46 and Q2E47 will need to update manually. Sorry about that. The procedure is outlined here: http://dev.laptop.org/ticket/11336#comment:8 Ask for help on these lists if needed. Users of 11.2.0 and previous (who will be running older firmware releases such as Q2E45) are not affected, and XO-1.5 and XO-1.75 users are similarly unaffected. Changes since build 881: The Sugar intro screen now shows the correct mouse cursor. The Sugar About my computer dialog now shows firmware versions on the XO-1.75 as it does on other laptop models. A XO-1.75 graphics drawing problem has been solved: closing the wireless key dialog no longer leaves an unpainted region on the screen. The camera now works in Scratch on XO-1.75. Wikipedia should no longer crash on XO-1.75 and will use less network bandwidth when online on all laptop models (previously we were downloading and rendering huge images, now we use thumbnails as we should!) Record no longer crashes on XO-1 when recording audio/video. A XO-1 keyboard problem was fixed causing some XO-1 models to have non-functional special keys (e.g. the frame key) An issue preventing XO-1 firmware upgrades was fixed, but affected users will need to manually update the firmware just this once. A trivial bug fix was applied to further reduce the window where the system may decide to suspend while connecting to a network. XO-1.75 now sends kernel log messages over serial console in secure mode. A XO-1.75 firmware update also reduces the popping at the start/end of the bootup jingle. 8GB disk images are now produced for XO-1.75. Closed tickets: #11332 Record activity dying while recording on SIGILL on XO-1 #10712 wrong cursor on welcome screen #11232 Sugar About my Computer dialog does not show 1.75 firmware/wireless firmware versions #11315 XO 1.75 secure mode gets ttyS0 console instead of ttyS2 #11335 Specialized Sugar keys on XO-1 Keyboard not working after battery pull #11336 Q2E46 does not automatically pick up new firmware builds. #11318 Ad-hoc network is not brought back after idle suspend/resume #11319 Scratch looks for wrong libv4l2.so file #11280 Drawing issue in neighborhood view #11295 insufficient resources for operation in wikipedia ___ Testing mailing list test...@lists.laptop.org http://lists.laptop.org/listinfo/testing ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] 11.3.0 release candidate 3 (build 882) released
On Oct 21, 2011, at 11:53 AM, Daniel Drake wrote: XO-1 users: we have identified a bug in the firmware releases shipped during 11.3.0 development and in earlier 11.3.0 release candidates. Affected versions are Q2E46 and Q2E47. You can check which version you are running in the Sugar 'Settings' dialog. Unfortunately, a bug in the firmware update code means that these firmware versions will not automatically upgrade to newer versions. We have fixed this in Q2E48 (included in 11.3.0 build 882 onwards), but existing users of Q2E46 and Q2E47 will need to update manually. Sorry about that. The procedure is outlined here: http://dev.laptop.org/ticket/11336#comment:8 Ask for help on these lists if needed. Users of 11.2.0 and previous (who will be running older firmware releases such as Q2E45) are not affected, and XO-1.5 and XO-1.75 users are similarly unaffected. If I download the file from http://dev.laptop.org/pub/firmware/q2e48/q2e48.rom and on an unlocked XO1 use the OFW command flash u:\q2e48.rom I get : Reading u:\q2e48.rom Image file is the wrong length ok By the way the file size is 1,048,576 bytes ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] 11.3.0 release candidate 3 (build 882) released
On Fri, Oct 21, 2011 at 10:21:20PM -0700, rihowa...@gmail.com wrote: If I download the file from http://dev.laptop.org/pub/firmware/q2e48/q2e48.rom and on an unlocked XO1 use the OFW command flash u:\q2e48.rom I get : Reading u:\q2e48.rom Image file is the wrong length ok I've checked, and I don't get that. By the way the file size is 1,048,576 bytes Thanks. That's the right size. Please check the md5sum of the file as read by OpenFirmware from your USB drive. This will help me to isolate the cause to either OpenFirmware, the XO-1, or your USB drive. To make this check, please create a text file md5sum.fth on the USB drive containing these lines: -- cut here -- : md5sumsafe-parse-word 2dup $read-file abort Read error 2dup $md5digest1 2swap free-mem push-hex bounds ?do i c@ # u# u# u# type loop pop-base . 2swap type type ; md5sum u:\q2e48.rom -- cut here -- Then insert the USB drive, get to the ok prompt, and type fl u:\md5sum.fth Then tell me what is displayed. Please also tell me what version of OpenFirmware is on the XO-1 at the moment. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] 11.3.0 release candidate 3 (build 882) released
On Oct 21, 2011, at 10:32 PM, James Cameron wrote: On Fri, Oct 21, 2011 at 10:21:20PM -0700, rihowa...@gmail.com wrote: If I download the file from http://dev.laptop.org/pub/firmware/q2e48/q2e48.rom and on an unlocked XO1 use the OFW command flash u:\q2e48.rom I get : Reading u:\q2e48.rom Image file is the wrong length ok I've checked, and I don't get that. By the way the file size is 1,048,576 bytes Thanks. That's the right size. Please check the md5sum of the file as read by OpenFirmware from your USB drive. This will help me to isolate the cause to either OpenFirmware, the XO-1, or your USB drive. To make this check, please create a text file md5sum.fth on the USB drive containing these lines: -- cut here -- : md5sumsafe-parse-word 2dup $read-file abort Read error 2dup $md5digest1 2swap free-mem push-hex bounds ?do i c@ # u# u# u# type loop pop-base . 2swap type type ; md5sum u:\q2e48.rom -- cut here -- Then insert the USB drive, get to the ok prompt, and type fl u:\md5sum.fth Then tell me what is displayed. 155a68922bc7e3fea323d400eaf3e99a u:\q2e48.rom ok Please also tell me what version of OpenFirmware is on the XO-1 at the moment. q2e46 is the OFW currently installed on this XO-1 -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] 11.3.0 release candidate 3 (build 882) released
On Oct 21, 2011, at 10:43 PM, rihowa...@gmail.com wrote: On Oct 21, 2011, at 10:32 PM, James Cameron wrote: On Fri, Oct 21, 2011 at 10:21:20PM -0700, rihowa...@gmail.com wrote: If I download the file from http://dev.laptop.org/pub/firmware/q2e48/q2e48.rom and on an unlocked XO1 use the OFW command flash u:\q2e48.rom I get : Reading u:\q2e48.rom Image file is the wrong length ok I've checked, and I don't get that. By the way the file size is 1,048,576 bytes Thanks. That's the right size. Please check the md5sum of the file as read by OpenFirmware from your USB drive. This will help me to isolate the cause to either OpenFirmware, the XO-1, or your USB drive. To make this check, please create a text file md5sum.fth on the USB drive containing these lines: -- cut here -- : md5sumsafe-parse-word 2dup $read-file abort Read error 2dup $md5digest1 2swap free-mem push-hex bounds ?do i c@ # u# u# u# type loop pop-base . 2swap type type ; md5sum u:\q2e48.rom -- cut here -- Then insert the USB drive, get to the ok prompt, and type fl u:\md5sum.fth Then tell me what is displayed. 155a68922bc7e3fea323d400eaf3e99a u:\q2e48.rom ok Please also tell me what version of OpenFirmware is on the XO-1 at the moment. q2e46 is the OFW currently installed on this XO-1 -- James Cameron http://quozl.linux.org.au/ So I tried flash u:\q2e48.rom again after running the md5sum.fth and this time the OFW flash worked ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
