On Tue, Dec 31, 2013 at 04:11:39PM -0500, Tim Moody wrote: > I reset my xo to q2f12 > > on my osbuilder vm: > > I created a localrepo with olpc-firmware-q2-f19-1.unsigned.noarch.rpm > > and added the last line to my .ini > > [repos] > fedora_arch=i386 > olpc_frozen_1=0,koji.dist-f17-i686 > olpc_frozen_2=0,koji.dist-f17-i686-updates-12.1.0 > olpc_frozen_3=1,local.12.1.0 > olpc_frozen_4=1,local.12.1.0-xo1 > add_excludes_to=koji.dist-f17-i686,koji.dist-f17-i686-updates-12.1.0 > custom_repo_1=1,xo1-fw,file:///root/osbuilder/localrepo/ > > after running olpc-os-builder > > /var/tmp/olpc-os-builder/output/21004xx0.packages.txt shows > > olpc-firmware-q2-f19-1.unsigned.noarch > > but if I copy-nand 21004xx0.img > > I still have q2f12 > > what am I missing?
During boot there was no file nand:\boot\bootfw.zip and so the firmware did not upgrade. For secure laptops this is handled by the firmware, for unsecure laptops this is handled by /boot/olpc.fth See http://wiki.laptop.org/go/Upgrading_firmware#How_it_Works The signing module in olpc-os-builder has a step for signing the firmware. See: http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/signing/preimage.40.sign-firmware.sh?h=v5.0 As you are not using deployment keys, you should instead craft a customisation that copies the signed firmware file from our server into your build: http://wiki.laptop.org/go/Upgrading_firmware http://dev.laptop.org/pub/firmware/q2f19/bootfw.zip Don't forget, you can use deployment keys without enabling security on the laptops. But having to use our bootfw.zip doesn't seem like a good enough reason to embark upon that. Being able to use the four game key method to install may be a justification. -- James Cameron http://quozl.linux.org.au/ _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
