Re: 10.1.3 image and Firmware q2e42
Excerpts from James Cameron's message of Wed Feb 16 23:06:38 +0100 2011: [Q2E42] - SMBIOS setup, (effect unknown, there was no test case), FWIW, this is likely to be the cause of your (i.e. Daniels) keyboard trouble. You will need to add setup-smbios (without the quotes) as the first line of olpc-fth-boot-me in olpc.fth. Newer versions of OFW do this outside of olpc.fth. Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 10.1.3 image and Firmware q2e42
On Wed, Feb 16, 2011 at 8:18 PM, Martin Langhoff martin.langh...@gmail.comwrote: On Wed, Feb 16, 2011 at 5:06 PM, James Cameron qu...@laptop.org wrote: If you based your image on OLPC OS 10.1.3 then after installation the firmware will be automatically upgraded to Q2E45, so you should test with Q2E45. Daniel - James is right here. Just include /boot/bootfw.zip in your image (os-builder will do the right thing if you provide the unsigned bootfw rpm and follow the signing procedures). For some bad experiences that we had in the past, the decision is not allow users to update the firmware. Just our technical team (and maybe volunteers) will do it. I know that we could include the firmware updating process in our software image release. I am pretty sure that all the bad experiences that support this decision are related to an old firmware version. I suppose that a good way to ensure that users could update the firmware without problems is make a pilot. But we don't have enough time now, maybe for the next firmware release. Right after install, each boot will check if there is battery+external power, and if those 2 conditions are met, will upgrade OFW. About your keyboard issues -- things have changed a bit from 8.2.x to 10.1.x in how we manage the keyboard. Can you tell us what you're trying to do (perhaps in a separate email thread), and we'll find a good way to do it. cheers, 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 -- Ing. Daniel Castelo Plan Ceibal - Área Técnica Avda. Italia 6201 Montevideo - Uruguay. Tel.: 2 601 57 73 Interno 2228 E-mail : dcast...@plan.ceibal.edu.uy ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 10.1.3 image and Firmware q2e42
Our idea is that just our technical stuff (and maybe volunteers with certain knowledge) could update the firmware. But this process will take us at least two or three months. So, we want to release our new software version trying to make it compatible with both firmware version Q2E41 and Q2E45. You have mentioned some bugs that could affect us: * #9100 (machines hanging during boot) * EC firmware which fixes issues with resuming from suspend from the touchpad * bugs in selftest diagnostics * others that could affect OFW's ability to install new releases We couldn't reproduce the bug #9100, and maybe we could accept the price of the other bugs that you have mentioned. However we have another problem in the keyboard mapping: the user couldn't use certain special keys, for example the frame key. I know that in the past the keyboard mapping configuration has changed from setolpckeys utility to HAL. The workaround that we found is the use of setolpckeys in our F11 image. If we copy /etc/udev/rules.d/96-olpc-keyboard.rules and /usr/sbin/setolpckeys all the key combination work. My question is, the use of setolpckeys in our F11 build could be dangerous or incompatible with the keyboard mapping based on HAL? Regards, Daniel. On Tue, Feb 1, 2011 at 6:02 PM, Paul Fox p...@laptop.org wrote: daniel wrote: Hi! We are using a software image based on dextrose, I know that the official OLPC software image is different, but for this question I think that is the same. We want to install dextrose (suppose 10.1.3 image) with the firmware q2e42. What do you think? This is possible or we will have problems with this combination of firmware and software image? you can read the release notes for the firmware releases between q2e42 and q2e45 here: http://wiki.laptop.org/go/OLPC_Firmware_q2e45 http://wiki.laptop.org/go/OLPC_Firmware_q2e44 http://wiki.laptop.org/go/OLPC_Firmware_q2e43 i'm sure the release will run. but q2e45 in particular contains a fix for machines hanging during boot (d.l.o #9100) as well as EC firmware which fixes issues with resuming from suspend from the touchpad. you can also see that q2e43 fixed very many bugs -- many of them are related to the selftest diagnostics, but others could affect OFW's ability to install new releases. we don't issue new firmware lightly, and of course we recommend that deployments always use the latest firmware. paul Regards, Daniel. -- Forwarded message -- From: Daniel Castelo dcast...@plan.ceibal.edu.uy Date: Tue, Feb 1, 2011 at 4:25 PM Subject: Dextrose and Firmware q2e42 To: dextr...@lists.sugarlabs.org We have delivered dextrose 1.0 for our XO 1.5 machines, we want to release this version to XO 1.0 one's, but based on some bad experiences that we had in the past we aren't allowed to update the firmware (problems with some machines that remained broken after the process). The question is, if we have the firmware q2e42 installed, will dextrose (version 1) run properly in this machines? After a first test ( ten minutes one) seem that works, but I suppose that we could have some problems if we don't update the firmware to the last version. Thanks Daniel -- Ing. Daniel Castelo Plan Ceibal - Área Técnica Avda. Italia 6201 Montevideo - Uruguay. Tel.: 2 601 57 73 Interno 2228 E-mail : dcast...@plan.ceibal.edu.uy part 2 text/plain 129 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org -- Ing. Daniel Castelo Plan Ceibal - Área Técnica Avda. Italia 6201 Montevideo - Uruguay. Tel.: 2 601 57 73 Interno 2228 E-mail : dcast...@plan.ceibal.edu.uy ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 10.1.3 image and Firmware q2e42
G'day, I'm puzzled. If you based your image on OLPC OS 10.1.3 then after installation the firmware will be automatically upgraded to Q2E45, so you should test with Q2E45. If you based your image on Dextrose os439dx, the same thing should occur, since it contains Q2E45 firmware. If it does not occur because of not being signed, you can sign the firmware, during image build, with your deployment keys. (This is assuming you have deployment keys in your secured laptop population). Are you intending to prevent the firmware update that Dextrose normally performs? For OLPC OS 10.1.3, it was tested with Q2E45, and so we don't really know how it will go wrong with Q2E41. For Dextrose, I imagine the same testing limitation was imposed. I think you've found at least one way it goes wrong; the keyboard mapping. You should review the full list of changes since Q2E41 to fully evaluate them. Paul didn't mention some that concern me: Q2E42 - key delegation, (you can ignore this if you do not use key delegation), - SMBIOS setup, (effect unknown, there was no test case), - nbclone to secure XO, (you can ignore this if you do not use nbclone), - many problems with ext2 filesystem access, (you can ignore this if you do not plan to deploy operating system images using ext2 filesystems), - many problems with USB access, (you can ignore this if you do not plan to deploy operating system images on USB drives), Q2E43 - free cluster tracking in FAT filesystem driver, (you can ignore this if you do not plan to capture data using firmware scripts that will write to USB or SD with FAT filesystems), - compatibility with USB keyboards, (you can ignore this if USB keyboards won't be connected at the time the laptop is turned from off to on). #9100 you may not be able to reproduce with your test laptops, but may reproduce on your deployed laptops. We don't have a firm idea of the probability distribution, but my estimate is somewhere between 5% and 20% of a population may be affected, depending on manufacturing variations. You might control for this risk by monitoring failures and applying firmware updates only to affected laptops. (The problem is caused by the new kernel relying on the contents of memory which is not initialised by the BIOS). On Wed, Feb 16, 2011 at 04:15:37PM -0200, Daniel Castelo wrote: My question is, the use of setolpckeys in our F11 build could be dangerous or incompatible with the keyboard mapping based on HAL? I'm not sure. I think you should test it. Paul may have a response. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 10.1.3 image and Firmware q2e42
On Wed, Feb 16, 2011 at 5:06 PM, James Cameron qu...@laptop.org wrote: If you based your image on OLPC OS 10.1.3 then after installation the firmware will be automatically upgraded to Q2E45, so you should test with Q2E45. Daniel - James is right here. Just include /boot/bootfw.zip in your image (os-builder will do the right thing if you provide the unsigned bootfw rpm and follow the signing procedures). Right after install, each boot will check if there is battery+external power, and if those 2 conditions are met, will upgrade OFW. About your keyboard issues -- things have changed a bit from 8.2.x to 10.1.x in how we manage the keyboard. Can you tell us what you're trying to do (perhaps in a separate email thread), and we'll find a good way to do it. cheers, 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: 10.1.3 image and Firmware q2e42
daniel wrote: Hi! We are using a software image based on dextrose, I know that the official OLPC software image is different, but for this question I think that is the same. We want to install dextrose (suppose 10.1.3 image) with the firmware q2e42. What do you think? This is possible or we will have problems with this combination of firmware and software image? you can read the release notes for the firmware releases between q2e42 and q2e45 here: http://wiki.laptop.org/go/OLPC_Firmware_q2e45 http://wiki.laptop.org/go/OLPC_Firmware_q2e44 http://wiki.laptop.org/go/OLPC_Firmware_q2e43 i'm sure the release will run. but q2e45 in particular contains a fix for machines hanging during boot (d.l.o #9100) as well as EC firmware which fixes issues with resuming from suspend from the touchpad. you can also see that q2e43 fixed very many bugs -- many of them are related to the selftest diagnostics, but others could affect OFW's ability to install new releases. we don't issue new firmware lightly, and of course we recommend that deployments always use the latest firmware. paul Regards, Daniel. -- Forwarded message -- From: Daniel Castelo dcast...@plan.ceibal.edu.uy Date: Tue, Feb 1, 2011 at 4:25 PM Subject: Dextrose and Firmware q2e42 To: dextr...@lists.sugarlabs.org We have delivered dextrose 1.0 for our XO 1.5 machines, we want to release this version to XO 1.0 one's, but based on some bad experiences that we had in the past we aren't allowed to update the firmware (problems with some machines that remained broken after the process). The question is, if we have the firmware q2e42 installed, will dextrose (version 1) run properly in this machines? After a first test ( ten minutes one) seem that works, but I suppose that we could have some problems if we don't update the firmware to the last version. Thanks Daniel -- Ing. Daniel Castelo Plan Ceibal - Área Técnica Avda. Italia 6201 Montevideo - Uruguay. Tel.: 2 601 57 73 Interno 2228 E-mail : dcast...@plan.ceibal.edu.uy part 2 text/plain 129 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
