Wanted: Helpers to test the 8.1.1 bugfix release candidate

   
   
   
   
   

I've been happily running the cutting edge "faster" builds over the last couple of days to see how the most recent improvements, especially when it comes to the re-design of the Sugar UI, are coming along (more on this topic soon). At the same time OLPC is also very busy working on the 8.1.1 (build 708) bugfix release. Among other things power-management has received some more attention, security has been improved and the pen tablet (stylus mode) can now be used to move the cursor.

Windows_XP_BSOD_s.png
Help avoid this!

In order to facilitate widespread testing of this release candidate OLPC has made a signed version of it available, therefore allowing everyone, not just people with a developer key, to thoroughly test this build. In an e-mail to the developer's mailing-list Michael Stone wrote:

Next, PLEASE SHOUT if you experience a regression in connectivity from 65x to 70x. (We've got another G1G1 visible on the horizon and we'd really like to know about connectivity problems as soon as you can tell us.) If you wish to help perform this testing (or to verify the fixes for specific issues), please record your results at http://wiki.laptop.org/go/OLPC_SW-ECO_5

Especially when it comes to connectivity OLPC can't possibly test and evaluate all the routers and firmware versions out there, an in-house approach is simply not that scalable. So tapping the community as a testing resource allows OLPC to gain a much broader understanding of potential issues which can then be addressed. Finding these issues in advance has a direct impact on all XO users, regardless whether it's a G1G1 donor in North America or a child in Peru.

See Michael's e-mail, read the 8.1.1 release notes and record your results here to contribute to OLPC and help all of us using an XO by testing this build!

Related Entries

7 Comments

Can't do it. Bug 6532 (SD Card Corruption: partition table gets corrupted on ext3-formatted SD cards on suspend/resume) is a deal breaker as far as I'm concerned. It seems foolish to install any upgrade that knowingly corrupts memory.

"Can't do it. Bug 6532 (SD Card Corruption: partition table gets corrupted on ext3-formatted SD cards on suspend/resume) is a deal breaker as far as I'm concerned. It seems foolish to install any upgrade that knowingly corrupts memory."

You can disable power management to keep SD card from being corrupted -- all other functionality should be safe to upgrade.

How long should this update take? I started it about 2 1/2 hours ago and it is still at:

- Performing full rsync.

The light at (o) is flashing sporadically.

I left it for 4 hours on the 'performing full rsync' line, then exited the activity. Now su isn't working ('permission denied'). Any suggestions?

I am giving up and doing a full install of the release candidate from a USB stick.

First, thanks for responding to my request for help testing the release candidate.

Colin, concerning slow rsyncs: it seems that Scott tried moving the updates server from a powerful VM onto an XO with attached storage. Unfortunately, the XO isn't powerful enough to keep up with all your concurrent rsyncs. We'll flip it back tomorrow as soon as I get access to the DNS entries.

Frankie, try logging in as root on the Linux virtual terminal and check the permission on /bin/su. (See http://dev.laptop.org/ticket/7158 for details.)

Thanks very much, and sorry for any inconvenience!

I have to agree that Bug 6532 is a major problem.. I noticed they are starting to tackle it finally, but I am still a bit stunned there is a hardware problem like this left.

Does 8.1.1 have "airplane mode" yet? I am excited to try out the new Sugar interface. I'll see what I can do. Thank you Michael for making this available.

Close