(Warning about dual boot failure) |
m (→Can't self install on XO: minor grammar) |
||
Line 43: | Line 43: | ||
# yum install isomd5sum squashfs-tools | # yum install isomd5sum squashfs-tools | ||
Which I did. This did not resolve the 'No such File' errors. Probing deeper in the script | Which I did. This did not resolve the 'No such File' errors. Probing deeper in the script, it seems to be failing on trying to mount a squashfs image. I loaded the squashfs-tools, but I suspect that the real issue is that the XO doesn't have squashfs support compiled in. | ||
So the bottom line is that you can't uses an XO to self install this image. | So the bottom line is that you can't uses an XO to self install this image. |
Revision as of 22:05, 8 November 2008
Can't self install on XO
I recently purchase a Sandisk SD card to try to do the Fedora 10 installation on my XO. I could not follow the installation instructions as I have an older SD card reader that will not recognize the 4Gb SDHC card.
So, I tried to do a self installation procedure on the XO. I copied the F10 live image to a USB stick, and inserted it and the SD card in thee XO. I downloaded the live iso script and attempted to run it. This failed with lots of 'no such file or directory' errors. The 'already set up' error is because this log was a second attempt, so that I could capture the log. Log follows:
bash-3.2# bash livecd-iso-to-disk.sh --xo --overlay-size-mb 320 --swap-size-mb 256 /media/PNY4/Fedora-10-Snap3-i686-Live/F10-Snap3-i686-Live.iso /dev/mmcblk0p1 Verifying image... livecd-iso-to-disk.sh: line 304: checkisomd5: command not found Are you SURE you want to continue? Press Enter to continue or ctrl-c to abort y Already set up as live image. Deleting old OS in fifteen seconds... Copying live image to USB stick mount: unknown filesystem type 'squashfs' cp: cannot stat `/media/cdtmp.1T1vVo/LiveOS/ext3fs.img': No such file or directory Cleaning up to exit... umount: /media/cdtmp.1T1vVo: not mounted umount: /media/cdtmp.1T1vVo: not mounted cp: cannot stat `/media/cdtmp.1T1vVo/isolinux/*': No such file or directory Updating boot config file sed: can't read /media/usbdev.CifSx0/syslinux/isolinux.cfg: No such file or directory Initializing persistent overlay file dd: opening `/media/usbdev.CifSx0/LiveOS/overlay-SAN4fedora-4911-BF89': No such file or directory sed: can't read /media/usbdev.CifSx0/syslinux/isolinux.cfg: No such file or directory sed: can't read /media/usbdev.CifSx0/syslinux/isolinux.cfg: No such file or directory Initializing swap file dd: opening `/media/usbdev.CifSx0/LiveOS/swap.img': No such file or directory /media/usbdev.CifSx0/LiveOS/swap.img: No such file or directory Setting up /boot/olpc.fth file egrep: /media/usbdev.CifSx0/syslinux/isolinux.cfg: No such file or directory Installing boot loader mv: cannot stat `/media/usbdev.CifSx0/syslinux/isolinux.cfg': No such file or directory umount: /media/cdtmp.1T1vVo: not mounted umount: /media/usbdev.CifSx0: not mounted USB stick set up as live image!
User:jlaska - suggested to
- yum install isomd5sum squashfs-tools
Which I did. This did not resolve the 'No such File' errors. Probing deeper in the script, it seems to be failing on trying to mount a squashfs image. I loaded the squashfs-tools, but I suspect that the real issue is that the XO doesn't have squashfs support compiled in.
So the bottom line is that you can't uses an XO to self install this image. Rmyers7 21:40, 8 November 2008 (UTC) rmyers7 at mindspring dot com
Is anybody successfully using the Nov 4th build?
I have successfully loaded and use the Snap3 build. I installed the Preview build and the XO does not complete the boot. The comet freezes near the bottom of the screen during its second revolution after going slower and slower. The sunspot animation continues, but the machine never gets any farther. Rmyers7 21:49, 8 November 2008 (UTC)
Warning about dual boot failure
After interrupting the boot process with the escape key, so that I could boot into Sugar (boot nand:\boot\olpc.fth) rather than the F10 test, the XO refuses to boot into F10 on subsequent boot attempts. It gets as far as the boot message on the XO power up screen, but never proceeds into the Fedora boot process screen. I suspect that this is a manifestation of 461808. I suspect that something in the normal XO boot or operation is corrupting the F10 initrd. So for right now it looks like if you want to use your XO for F10 and Sugar, you need to remove the F10 card, and not boot to Sugar with it in. IMO, this is not a good long term situation, as discussion in the OLPC community suggests that the SD slot does not stand up to mishandling, and unnecessary insertion/removal cycles are to be avoided. Rmyers7 22:04, 8 November 2008 (UTC)