next »

[newbie]

Forget the previous message regarding util-linux! Is correct but irrelevant to your problem!

Thank you! I was getting too embarassed to speak up and admit that things still don't work.

Having said that...er...things still don't quite work.

sfdisk works fine now (thanks again for the "su -"-advice). I've unmounted my sd card in the journal. I follow every single step in the directions, yet when it is time to execute the script, I get:

sh: UbInstall.sh: No such file or directory

Would it all be easier if I simply upgraded everything to the newest build/firmware? I am still running a pre-700 build because I'm worried about being unable to re-install all of my software (in the newer builds, I can't sugar-ize things like mplayer anymore, right?) and corrupting my sd-card.

I am insanely excited about the prospect of running hardy on my xo and feel like I'm almost there. Do you have any idea why the script isn't running?

[newbie]

Woo-Hoo! The script is running!

Maybe I misread your instructions? I tried it again, but this time put the "su -"-command at the beginning.

Great! Now I just have to wait (easier said than done)...

Still, the other question remains - does it make sense for me to update to Sugar-Build 711, or should I wait? I am curious about all this "power management" that people are talking about...

[mavrothal]

Still, the other question remains - does it make sense for me to update to Sugar-Build 711, or should I wait? I am curious about all this "power management" that people are talking about...

If you are happy with what you have I wouldn't bother at this time. In the coming few weeks the Update.2 (8.2.0) will come out that is much nicer  (from what I can see from joyrides).

My only worry about older builds would be the firmware that may have problems recognizing some SD cards (you get the error: the card didn't power up after 1 sec or something similar). If you do, you can try first to manually upgrade the firmware ( http://wiki.laptop.org/go/Manual_Firmware_Install ) and if this fails go for the update. I would still go for joyride2301 or whatever will be at the http://wiki.laptop.org/go/Friends_in_testing site

[newbie]

Great! My old build has served me fine so far, so I can wait a few more weeks...

UPDATE: Script works like a charm! I love having Hardy on my xo!

[MartijnR]

Great work!

Let's say I wanted it on a USB flash drive instead of a SD card (Simple for daddy: plug it in for Ubuntu, do not plug it in for daughters Sugar), how should the script need to be changed (not a Linx-pro here...)?

[mavrothal]

Let's say I wanted it on a USB flash drive instead of a SD card (Simple for daddy: plug it in for Ubuntu, do not plug it in for daughters Sugar), how should the script need to be changed (not a Linx-pro here...)?

The simplest thing is to change the olpc.fth file around so it will boot be default to Sugar and to the Ubuntu on the SD card if the "O" gamekey is pressed

Edit I AM back to my XO! This is NOT going to work. Forget it!

If you still want to use a USB  here is me best Guess ... I'm away from my XO so I can verify nothing of these even though it seems right...Try it at YOR...

FIRST plug in the USB stick that you are going to put Ubuntu on
THEN put the USB stick maned USB with the tar file and the script.
Open a terminal and type df. It should show the Ubuntu stick mounted on /dev/sda and the "USB" stick on /dev/sdb  If this is not exactly like that STOP and ignore whatever is below this point.

If it is, go in the Journal and Unmount the stick that you are going to put Ubuntu on  but leave the "USB" stick mounted. Then apply the script as described above, but now the script should look like that:
#
# script to install Teapot's Ubuntu8 in a USB stick
#
touch /etc/ohm/inhibit-suspend
/etc/init.d/haldaemon stop
umount /dev/sda
dd if=/dev/zero of=/dev/sda bs=4096 count=1
sfdisk /dev/sda << EOF
0,,83,*
EOF
mke2fs -j -L OLPCRoot /dev/sdap1
mkdir /media/OLPCRoot
mount /dev/sdap1 /media/OLPCRoot
cd /media/OLPCRoot
tar xvjf /media/USB/OLPCFiles-hardy-20080506.tar.bz2
cp -a /security .
cp -ia /boot/* boot/ </dev/null
cp -a /lib/modules/* lib/modules/
cp -a /lib/firmware/* lib/firmware/
cd /
umount /media/OLPCRoot
echo "All done!"
echo "Reboot your XO to start using Ubuntu"
echo "login with username:olpc password:olpcolpc"
exit 0

Again. This is NOT tested or verified at any level  Indeed
Worse case scenario messes up your stick and will need reformatting.

Let us know of problem/success.

Edit However, even if the installation works, you will not be able to run Ubuntu from the USB unless you modify the olpc.fth file in the /boot directory of the stick so it will look for boot in the USB stick instead of the SD card (as it is in its current form)! And I can not tell you that from memory..... If teapot or someone close to the XO sees that,  can  maybe help.

[Eddie Owens]

MartijnR, if you already have  Ubuntu functioning on an SD card, another option would be to add koolkat's multiboot olpc.fth to the SD card (topic=2375). 

Just messing around, I put Ubuntu on both an USB stick and SD card, and I have the multiboot olpc.fth on both.   And topic=1525 has a multiboot /etc/fstab you can use, uncommenting the appropriate lines for whether you are using SD or USB.

Using the multiboot  arrangement would of course require an individual to choose which device to boot from at startup, however this might not work well for younger users. 

[MartijnR]

Mavrothal, I've noticed! 

I am now trying to do it manual, step by step. Thanks for your try anyway. I'll keep you updated...

[mavrothal]

Mavrothal, I've noticed!  Cheesy

I am now trying to do it manual, step by step. Thanks for your try anyway. I'll keep you updated...

Good
The problem is that both sticks will be mounted on /dev/sda1. So is hard with the script (for me at least ) to distinguish which one will be formatted.
Manually, and one stick at a time  is easier. However, I am not sure if the "dd" command in the original teapot's instructions will work with the USB. Let us know.
Also if you manage, make sure that you change the "olpc.fth" file in the stick so will boot from the stick and not the (non-existing) SD card

[MartijnR]

I finally succeeded, folllowing teapots instructions http://olpcnews.com/forum/index.php?topic=2240.msg21169#msg21169, using the hardy-tarball.

The sticks mount as sda (1, 2, 3, etc,depending on the number of partitions) and sdb (1,2,3, etc). I did the partioning manually with fdisk,

I guess if you put the commands from the above message in a script and use sfdisk, it will probably work.

Sometimes after partioning a reboot is needed, that might mess up the script.

[mavrothal]

I finally succeeded, folllowing teapots instructions http://olpcnews.com/forum/index.php?topic=2240.msg21169#msg21169, using the hardy-tarball.

Well done! Maybe you can post some detailed instructions in that thread about the Stick partitioning at least

I did the partioning manually with fdisk,

The problem is fdisk is not script-frendly. That's why I used sfdisk

I guess if you put the commands from the above message in a script and use sfdisk, it will probably work.

By now you are certainly more qualified in this! If you remember your commands and the order (and reboot is not really mandatory), you just put them in the script.
For partitioning with sfdisk just use the same command but change the target device eg. put what ever you put to fdisk for partitioning.  Will be only one partition but that's fine.

[MartijnR]

Most (all...) of the information I did find in the thread I mentioned

The stick partioning works the same as with SD-cards I guess, except for (which Teapot also points out), that sometimes after partioning the old allocation table stays in the kernel (fdisk throws a warning). You have to reboot at that point otherwise you can't proceed. This would mess up a script that is running I guess......

By now you are certainly more qualified in this! If you remember your commands and the order (and reboot is not really mandatory), you just put them in the script.

Sorry, I ment this retorical, in no way I was ordering you to make the script! Only thing I don't know about the dd-command and about sfdisk..... Also the line in which the powersaving gets suspended didn't work, there was no such folder in my build (656).

[teapot]

mke2fs -j -L OLPCRoot /dev/sdap1

The names of devices for partitions on the USB drive are are /dev/sda1,  /dev/sda2, ... for the first device, /dev/sdb1, ... for the second device, etc., not /dev/sdap1 . Of course, since the original files are also on a USB drive, any automated script should at least discover which device is which. This is one of the reasons why I didn't post an automated installer scripts -- way too many possibilities for mis-identified devices and error conditions. With SD card one can be at least sure where the destination device is.

Once Ubuntu is installed on USB drive, the changes are only necessary in /boot/olpc.fth (disk: instead of sd: everywhere) and /etc/fstab (/dev/sda1 instead /dev/mmcblk0p1) (both files on USB disk, so when you edit them they will be relative to mount point of /dev/sda1 or /dev/sdb1 as it can be seen in the output of mount

Also the line in which the powersaving gets suspended didn't work, there was no such folder in my build (656).

If your configuration does not have /etc/ohm directory, then power management isn't enabled, so SD card won't get corrupted anyway. I still recommend to update the system on NAND before installing Ubuntu, so you'll get later version of kernel.

[mavrothal]

Of course, since the original files are also on a USB drive, any automated script should at least discover which device is which. This is one of the reasons why I didn't post an automated installer scripts -- way too many possibilities for mis-identified devices and error conditions.

Well... I tried it just the same...  http://olpcnews.com/forum/index.php?topic=2240.msg25065#msg25065
Just with plenty of details...