next »

[mavrothal]

hey im runnin ubuntu 8.10 on my XO ryt now  [...  ...] i also read all the threads but couldnt find a proper way of installing it ...so if any1 can tell me how to install it in a easy way like the installation of ubuntu ...  

The legendary Teapot's Ubuntu is using the entire unmodified official os767/802 /boot and /security folders. Thus for the OFW is an "official" build   Hopefully, he is going to do that again with the os852 and Lucid/Maverick ...
This can not be done for XOpup because it requires a modified kernel that /boot/fs.zip will see as "unofficial".... and no, I do not have OLPC's cryptographic keys...
(However Tinycore might....   )

But look at the bright site, Uruguayan XOs can boot any official builds

Now regarding instructions, Let me try again...
Get a USB stick. Format it as an ext2/ext3 partitions. Detailed  instructions for that are (as mentioned in the announce post)  HERE.
Then just " tar xvzf XOpup-v4.tar.gz" (also indicated at the above link).

You can also use Teapot's original instructions up to "tar xvjf /media/...." and replace with the path (location) of the XOpup-v4.tar.gz

It shouldn't boot on a locked XO, but if you somehow manage, please let us know

[Rao]

hey im runnin ubuntu 8.10 on my XO ryt now  [...  ...] i also read all the threads but couldnt find a proper way of installing it ...so if any1 can tell me how to install it in a easy way like the installation of ubuntu ...  

The legendary Teapot's Ubuntu is using the entire unmodified official os767/802 /boot and /security folders. Thus for the OFW is an "official" build  Hopefully, he is going to do that again with the os852 and Lucid/Maverick ...
This can not be done for XOpup because it requires a modified kernel that /boot/fs.zip will see as "unofficial".... and no, I do not have OLPC's cryptographic keys...
(However Tinycore might....   )

But look at the bright site, Uruguayan XOs can boot any official builds

Now regarding instructions, Let me try again...
Get a USB stick. Format it as an ext2/ext3 partitions. Detailed  instructions for that are (as mentioned in the announce post)  HERE.
Then just " tar xvzf XOpup-v4.tar.gz" (also indicated at the above link).

You can also use Teapot's original instructions up to "tar xvjf /media/...." and replace with the path (location) of the XOpup-v4.tar.gz

It shouldn't boot on a locked XO, but if you somehow manage, please let us know

I am afraid the installations instructions are still not clear (at least to me).  What I am confused about is,

1.  In your first post in this thread you said,  
    ********
To install download XOpup-v4.tar.gz, extract it by "tar xvzf XOpup-v4.tar.gz", or copy the boot folder (see "Attention" below), vmlinuz, initrd.gz and lupu-510.sfs, at the root of an etx2/3 formatted USB stick or SDcard 500MB or bigger (so you'll have at least 128MB saving space and maybe add 250MB  swap), and boot.
***************

From this and from the write-up at http://ftp.cc.uoc.gr/mirrors/linux/XOpup/Docs/Formatting_Instructions.html I conclude that the XOpup is to be (extracted) installed onto a USB or SD card.   Is that right?

If so, why copy the boot folder,  vmlinuz, initrd.gz and lupu-510.sfs (to) at the root of ext2/ext3 formatted USB stick or SD card (this is from your instructions above)?

2. Or do you mean that the folder and files have to be copied to the RAM on the XO-1?

thanks,

Rao

[mavrothal]

Hmmm, you are right.
This is because the tar tar file can be extracted anyware (Windown, Mac, linux) and the contents of it transfered into the USB/SDcard or extracted directly into the USB/SDcard. But I can see how this can generate confusion.

So either extract directly into the USB/SDcard or extract anywhere and transfer the vmlinuz, initrd.gz and lupu-510.sfs as well as the appropriate boot folder to the USB/card.

The notes about about boot folders and olpc.fth verssions apply in both cases. The "move" in the case that you extract directly into the USB/SDcard means really "rename", which is done in linux by the "mv" command ...
(The upcoming XO-1/XO-1.5 version of XOpup greatly simplifies the boot folder/olpc.fth issues but till then...)

[awaistoor]

hey mavrothal ... well i have installed puppy wid ur early instructions n everythn is working good execpt for 2 things:
1. i can connect to my DSL through wirless router but web i start browsin anythin it says dat "couldnt resolve host" ... but i can enter my router setting throught ping
2. mousepad is not workin properly .. 1 min it works fine n very next min its not workin ...
 so can u help me in these probs ...
   and btw thanx for ur help

[awaistoor]

hey im runnin ubuntu 8.10 on my XO ryt now  [...  ...] i also read all the threads but couldnt find a proper way of installing it ...so if any1 can tell me how to install it in a easy way like the installation of ubuntu ...  

The legendary Teapot's Ubuntu is using the entire unmodified official os767/802 /boot and /security folders. Thus for the OFW is an "official" build  Hopefully, he is going to do that again with the os852 and Lucid/Maverick ...
This can not be done for XOpup because it requires a modified kernel that /boot/fs.zip will see as "unofficial".... and no, I do not have OLPC's cryptographic keys...
(However Tinycore might....   )

But look at the bright site, Uruguayan XOs can boot any official builds

Now regarding instructions, Let me try again...
Get a USB stick. Format it as an ext2/ext3 partitions. Detailed  instructions for that are (as mentioned in the announce post)  HERE.
Then just " tar xvzf XOpup-v4.tar.gz" (also indicated at the above link).

You can also use Teapot's original instructions up to "tar xvjf /media/...." and replace with the path (location) of the XOpup-v4.tar.gz

It shouldn't boot on a locked XO, but if you somehow manage, please let us know

I am afraid the installations instructions are still not clear (at least to me).  What I am confused about is,

1.  In your first post in this thread you said,  
    ********
To install download XOpup-v4.tar.gz, extract it by "tar xvzf XOpup-v4.tar.gz", or copy the boot folder (see "Attention" below), vmlinuz, initrd.gz and lupu-510.sfs, at the root of an etx2/3 formatted USB stick or SDcard 500MB or bigger (so you'll have at least 128MB saving space and maybe add 250MB  swap), and boot.
***************

From this and from the write-up at http://ftp.cc.uoc.gr/mirrors/linux/XOpup/Docs/Formatting_Instructions.html I conclude that the XOpup is to be (extracted) installed onto a USB or SD card.   Is that right?

If so, why copy the boot folder,  vmlinuz, initrd.gz and lupu-510.sfs (to) at the root of ext2/ext3 formatted USB stick or SD card (this is from your instructions above)?

2. Or do you mean that the folder and files have to be copied to the RAM on the XO-1?

thanks,

Rao

hey rao ...
lemme tell u this that this work is not that difficult as it seems ...
if u have installed any other  OS on ur olpc (let say Ubuntu 8.04 or 8.10) then just download the XOpup file and extract tar file as mavrothal said ... den rename both boot folders name as mavrothal told us .... den just copy those files to ur root directory (file system directory) .. apparently it will not let u copy as ur not the root user ... open terminal n copy dose files with sudo command or become rootuser n den use copy command ... [i hope u know the commands] wen the files r copied .. just restart ur XO n ull find a Puppy linux workin in ur XO ...
hope u now understand

[Rao]

Thanks for the prompt reply but I still have a problem!

I have OS852 running on my XO-1.  I created a ext3 partition (with no boot flag) and a swap partition on my Sandisk USB stick. Next, I extracted the .gz file as instructed into the ext3 partition (ls -l /media/XOpup shows the mentioned files).

Now, as I understand, I don't have to copy any files to the XO-1 (from the USB stick) and I don't have to do any rename/mv since I am using a USB stick.

Is that right?

If it is, I have a problem.  When I boot the XO with the USB stick plugged in what comes up is Sugar.  I tried booting again after setting the boot flag for the ext3 partition but that didn't help.

Please set me straight!

Are you aware of James Cameron's work on Ubuntu 10.x for XO-1 (only terminal interface!) and XO-1.5 (with browser interface, I believe).  I looked into it some but it was too much for me.

thanks,

Rao

Hmmm, you are right.
This is because the tar tar file can be extracted anyware (Windown, Mac, linux) and the contents of it transfered into the USB/SDcard or extracted directly into the USB/SDcard. But I can see how this can generate confusion.

So either extract directly into the USB/SDcard or extract anywhere and transfer the vmlinuz, initrd.gz and lupu-510.sfs as well as the appropriate boot folder to the USB/card.

The notes about about boot folders and olpc.fth verssions apply in both cases. The "move" in the case that you extract directly into the USB/SDcard means really "rename", which is done in linux by the "mv" command ...
(The upcoming XO-1/XO-1.5 version of XOpup greatly simplifies the boot folder/olpc.fth issues but till then...)

[awaistoor]

hey rao .. the prob is dat u r using USB stick ... there r just 2 ways boot in XO laptops ... 1 by built in n the other is through SD Cards ... so u have to us a SD Card n do all those things that u have done with USB ... ur Puppy linux will work den hopefully

TOOR

[Rao]

A while ago I used a USB stick to boot into Teapot's Ubuntu (Hardy and Intrepid) but these days I use SD card for that.    I will use that SD card (I have only one SD card) to try the PuppyLinux.  But my understanding from Mavrothal's post is that  either can be used except for renaming for SD card.

thanks,

Rao

hey rao .. the prob is dat u r using USB stick ... there r just 2 ways boot in XO laptops ... 1 by built in n the other is through SD Cards ... so u have to us a SD Card n do all those things that u have done with USB ... ur Puppy linux will work den hopefully

TOOR

[awaistoor]

A while ago I used a USB stick to boot into Teapot's Ubuntu (Hardy and Intrepid) but these days I use SD card for that.    I will use that SD card (I have only one SD card) to try the PuppyLinux.  But my understanding from Mavrothal's post is that  either can be used except for renaming for SD card.

thanks,

Rao

dude dont rename ur SD card .. n dont even rename the folders ... just format that SD card in ext3 n copy dost files n folders in it n den boot from it

[mavrothal]

Rao is there anything else in your USB stick?
In its standard configuration there is no way the XOpup-v4 to boot sugar, because its olpc.fth does not "see" the internal NAND at all. (unless you press the "O" game key... )  The only way for this to happen is
a) the stick is not "visible" by the XO at all
b) it is not in the first partition (eg you have first the swap partition and then the ext3)
c) the boot folder is not at the root of the stick
d) the file is corrupt (check md5sum)
e) You used XOpup-v3. There the files are enclosed in the XOpup-v3 folder and if extracted at the root of the stick then the boot folder is in the XOpup folder-> no boot from USB
f) voodoo  

[mavrothal]

awaistoor,
are you saying you booted XOpup in a locked XO-1

[Rao]

Rao is there anything else in your USB stick?
In its standard configuration there is no way the XOpup-v4 to boot sugar, because its olpc.fth does not "see" the internal NAND at all. The only way for this to happen is
a) the stick is not "visible" by the XO at all
b) it is not in the first partition (eg you have first the swap partition and then the ext3)
c) the boot folder is not at the root of the stick
d) the file is corrupt (check md5sum)
e) You used XOpup-v3. There the files are enclosed in the XOpup-v3 folder and if extracted at the root of the stick then the boot folder is in the XOpup folder-> no boot from USB
f) voodoo  

The md5sum's match as you can see below.

a44343e6e1e1e6a2a56c26bc498cd05f
a44343e6e1e1e6a2a56c26bc498cd05f
--------------------------

I did download the v4 version.
------------------------------------------
The files in the root director (of the USB) stick are shown below by the ls -l command,

root@klpsr-desktop:~# ls -l /media/XOpup/
total 112604
drwxr-xr-x 2  500  500      4096 2010-08-27 10:39 boot
drwxr-xr-x 2  500  500      4096 2010-08-27 10:39 boot_sd
-rw-rw-r-- 1  500  500      7483 2010-09-05 17:26 changelog.txt
-rw-rw-r-- 1  500  500      2929 2010-08-27 10:08 Formatting_Instructions.txt
-rw-r--r-- 1  500  500   3487144 2010-08-13 20:04 initrd.gz
drwx------ 2 root root     16384 2010-09-17 10:06 lost+found
-rw-r--r-- 1  500  500 109690880 2010-09-05 18:07 lupu-510.sfs
-rw-r--r-- 1  500  500       133 2010-09-05 18:10 md5sums.txt
-rw-r--r-- 1  500  500   1950000 2010-07-17 06:25 vmlinuz
-rw-rw-r-- 1  500  500      5543 2010-09-05 12:14 XOpup-v4.html

--------------------------------------------
The USB stick is visible to  OS852. The command ls -l shows the same files as above.
-------------------


gparted shows the following

Partition    FileSystem MountPoint          Label        Size       Used          Unused  Flags
/dev/sdb1 ext2            /media/XOpup       XOpup     1.65GiB 157.69MiB 1.5GiB  boot

/dev/sdb2 linux-swap                    LXSWAP    258.86MiB  

------------------------------




But what I found out is that with OS852 installed I can't get the OK prompt (to try boot u:\boot\olpc.fth or dir commands) repeatedly pressing ESC while powering up.  That doesn't seem to be right but I don't know if that has anything to do with the problem at hand.


---------------

So XOpuppy should work with a USB stick also, is that right?

Anyway,  is the boot flag supposed to set for  the partition?  It didn't make any difference with my problem.

thanks,

Rao

[awaistoor]

awaistoor,
are you saying you booted XOpup in a locked XO-1

wat do u mean by LOCKED XO-1?? 

[Rao]

awaistoor,
are you saying you booted XOpup in a locked XO-1

wat do u mean by LOCKED XO-1?? 

I believe that means that to run any OS other than  official/signed from OLPC, one has to obtain developer key (a file) from OLPC and place it in the directory /security.   Also, at the OK prompt which you get by repeatedly pressing  the ESC key (top left) when powering up the XO one has to run the command disable-security.

That is my understanding.

[mavrothal]

Rao,
I'm using XOpup almost exclusively from a stick.
Everything looks OK in your stick but just in case also try "ls -al" to check for any hidden files.
I assumed that your firmware is q2e45 right? (check the sugar "settings-> about my XO")
Try to power-up with the "check" gamekey pressed to bypass pretty boot and see what OFW says. Is it really reading the "u:\boot\olpc.fth"?
Finally remove any SDcard if install (though souldn't make a difference)

The fact you do not get to the OFW prompt is very suspicious....

In its standard configuration there is no way the XOpup-v4 to boot sugar, because its olpc.fth does not "see" the internal NAND at all.

This is wrong! in the standard XOpup-v4 configuration if you have the "O" game key pressed the XO will boot from the NAND if you run an F11 build (like os852) but should not give the "pretty boot" with the dot animation. Just the running console.