next »

[mavrothal]

Just to point out that all three new background are included in the built and can be easily set by Menu>Desktop>Desktop Settings>Nathan Wallpaper Setter.
Connection wise, there is a visual guide in the "Docs" folder that should make it easy.

BTW in case the correct time is not maintained through reboots, comment out line 42 in /etc/rc.d/rc.local and move the invisible /root/.settime file to /root/Startup/

[mavrothal]

Till XOpup-2.0 arrives I thought to release a small xopup-200 update with a couple of additions and fixes.
xopup_200_update-1.pet has a new resizable user interface for PPM and fixes the PPM-configure layout. Also includes an addition to quickpet that now directly downloads the xopup_devx_200.sfs. Finally fixes the time-change-after-reboots issue on the XO-1 (pls report on this one).

[eric76]

(...)

Going on with XOpup development (...) we have reached Release Candidate status for XOpup-2.

The main changes compared to XOpup-1.0 are:
 (...)

To install download the XOpup-2.RC.tar.gz (md5sum: 2ea3773984a0dafd1736e13f0666e52d), expand it at the root of an ext2/ext3/vfat formatted USB or SDcard and boot your unlocked XO-1 or XO-1.5.

PS: Minipoll
Which of the 3 wallpapers you think should go in the XOpup-2 "final"?

• 1
• 2
• 3

Hey Mavrothal, first, thanks a lot for this!

i extracted the RC to sd, and boot up:
it says: "xopup-200.sfs not found. Dropping out to intitial-ramdisk console..."
but the file is in the root of the card..

also i couldn't find the lupu-511.sfs file anywhere (that is mentioned in your first post). Don't know if thats needed anymore.


so Thanks a lot in advance,
and i go with WP no1 (e.g. NewWallpaper3, the one with the trampolin), its by far the cutest imo!

greetings,
Eric

[mavrothal]

i extracted the RC to sd, and boot up:
it says: "xopup-200.sfs not found. Dropping out to intitial-ramdisk console..."
but the file is in the root of the card..

Sometimes cards can be "funny" on the XO-1.
Pls try a USB stick.
Alternatively try to see if XOpup-1 will work OK (the new kernel does do some strange tricks with some hardware-see few posts above). If this is OK you could use the (included) 2.6.31 kernel (More on than if needed)

also i couldn't find the lupu-511.sfs file anywhere (that is mentioned in your first post). Don't know if thats needed anymore.

No it is not.

Thanks for the "vote"

[eric76]

Sometimes cards can be "funny" on the XO-1.
Pls try a USB stick.
Alternatively try to see if XOpup-1 will work OK (the new kernel does do some strange tricks with some hardware-see few posts above). If this is OK you could use the (included) 2.6.31 kernel (More on than if needed)

thanks for the quick help!

now i put V 1.0 on the card, same thing, but that it says lupu-511.sfs is missing.
Unfortunately im not much into linux and don't know for sure which one the kernel file is.

I would need your OS on the card, it is much more comfortable. However i put it into an usb stick adapter, but it didn't work out with either of both versions.

I may have to mention im using the latest Stable Release 10.1.3 (16th january) from wiki.laptop.org and the card is formated with a Swap Partition, then ext3. (but since it boots up and gives a lot of messages i guess thats not the problem...)

looking forward to hear from you!
boot up looks really fast, so im very eager to lay my hands on the puppy

[mavrothal]

now i put V 1.0 on the card, same thing, but that it says lupu-511.sfs is missing.
Unfortunately im not much into linux and don't know for sure which one the kernel file is.

I would say that the problem is the card itself.
What else is in the card? What was used for before? Is this a fresh partitioning? With Parted/fdisk/other utility?

However i put it into an usb stick adapter, but it didn't work out with either of both versions.

If it is the same card we are talking about, moving it to an adapter is not going to change things.

I may have to mention im using the latest Stable Release 10.1.3 (16th january) from wiki.laptop.org and the card is formated with a Swap Partition, then ext3. (but since it boots up and gives a lot of messages i guess thats not the problem...)

Is 10.1.3 on the same card?
What _exactly_ do you mean by "Swap Partition, then ext3"
Can you boot in Sugar with the card in (press the 'O' kame key during power up) and post the output of:

Code:

fdisk -l /dev/mmcblk0

(this is the letter "el" not the number "one")

[eric76]

Hi Mavrothal,

please excuse my late reply, and thank you very much for your help. I forgot to mention there's a fat partition after the ext 3, the table looks like this:

        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1               1          62      497983+   5  Extended
/dev/mmcblk0p2   *          63        1058     8000370   83  Linux
/dev/mmcblk0p3            1059        1953     7189087+   b  W95 FAT32
/dev/mmcblk0p5               1          62      497952   82  Linux swap / Solaris

i made it with cfdisk on the XO Laptop.

I've read a guide at
http://wiki.laptop.org/go/User:NeoAmsterdam/Installing_build_8.0.2_to_a_bootable_SD_card
which uses the whole card for the system, but i thought it might come in more handy to be easily able to switch files with MS Windows, now and then!

[mavrothal]

Eric
You partition table looks strange.
Your first partition is an extended one and within it you have your swap partition.
I can not see anything like that in the link that you reference.

I would recommend to repartition your card using a GUI tool as Gparted in linux or Acronis disk director (not free)  in Windows. Or just follow the formating instructions included in the Docs folder of the XOpup download (but this is to make it only one partition).

Make sure that XOpup files are in the first partition.

You do not need the boot flag for the XO. The OFW does not read it and does not care really.

[eric76]

okay thanks!! i will give it a try the next days and update you!

[eric76]

I would recommend to repartition your card using a GUI tool as Gparted in linux or Acronis disk director (not free)  in Windows. Or just follow the formating instructions included in the Docs folder of the XOpup download (but this is to make it only one partition).

Make sure that XOpup files are in the first partition.

okay, i tried it with gparted and as you said, puppy now on sdc1.

  Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1         535     4297356   83  Linux
/dev/sdc2             536         600      522112+  82  Linux swap / Solaris
/dev/sdc3             601        1953    10867972+   b  W95 FAT32

but it still gets the same failure:

"xopup-200.sfs not found. Dropping out to intitial-ramdisk console...
/bin/sh: can't access tty; job control turned off"
...

I tried it with bootflag / on off which didn't make a difference (as you said). ext4 i wanted to try as well, but didn't work at all.

P.S.: i've tried it on an usb stick now as well, and it works great there. By what i've seen so far i am very impressed. thank you very much for this!
I hope you can fix the sdcard issue, because it would be much more comfortable that way! (with the fat partition for file switching)

[mavrothal]

I'm assuming that the card is mounted on an adapter (otherwise it should show as /dev/mmcblk0, not /dev/sdc)
That there are no USB or SDcard when you mount you puppy card (from the slot or the adapter)
That this is a fresh install and there are no other files on the card except  the XOpup files.
And finally that you have firmware q2e45 (It should have been updated if you ever booted up 10.1.3 while the power adapter was plugged and the battery > 50%)

If the above is true, I can only think 2 things.
That this 8GB card does not play well with the XO (have you booted any other OS on the XO with this very card?) or
that the presence of both the etx3 and vfat partitions on the same card somehow "confuses" puppy.
This should not be happening but I have never tested it so I can not be 100%. A simple test for that is just to use gparted and erase the vfat partition leaving the space empty and see if it makes a difference (you an recreate your vfat partition later).

Frankly I think is the card itself (what brand/class is it?) and maybe what has been through
All these partitions tools are made for HD, and cards are quite different
When I repartition a card I make sure that the start and end points are the same with the factory settings and the partition boundaries align with erase blocks if possible.

Try another card

[eric76]

I'm assuming that
(...)
Try another card

All your assumptions are correct, except that it's a 16gb card.
I've been running teapots' Ubuntu Intrepid on it before that which worked quite fine (but using the whole card)

I made another gparted try on my linux machine (thats why it says /dev/sdb...), deleting all tables and making one big ext3 partition. (I didn't read through your whole link yet, maybe i will the next days - so much text - btw, i discovered this "[Mitch says: actually, OFW will use the partition that is marked bootable, and if there isn't one, it will use the first partition]" there)

And once again the same error... :/

It will take me some days to get another card (which is quite frustrating, cause the one was expensive enough). Maybe i'll give the original Sugar a try on it before that. But would have liked the encryption feature. Btw. what are you using for "strong encryption"?

[mavrothal]

But would have liked the encryption feature. Btw. what are you using for "strong encryption"?

Never use it.
It really brings XO-1 to its knees particularly in boot/save/shutdown

Mitch says: actually, OFW will use the partition that is marked bootable, and if there isn't one, it will use the first partition

XOpup uses by default the first partition of the device.
/boot/olpc.fth defines sda1 or mmcblk0p1 (USB or Card) as the boot partition, exactly because puppylinux has problems with some cards and sticks to find them.

BTW what the command "probepart_init -k" gives when it says that can not find the puppy files?
Do you see your partitions in the list?

[mavrothal]

This is the second release candidate build of XOpup-2 (xopup-201).



As the picture suggests it supports screen rotation for both the XO-1 and the XO-1.5
Also hinted in the picture is the inclusion of the rotation-aware, Openbox/Fbpanel as the default window manager.
Another handy addition is the inclusion of shinobar's "fsf_load on the fly" utility that I think is extremely useful, particularly for a limited resources machine like the XO-1.

Openbox is much more user friendly and feature-full than JWM and thus a bit slower. You can switch back and forth between the 2 WM with the new switch desktop utility (in the Desktop sub-menu)

Rotation in implemented either with the rotation button or with the new, rotate screen, menu entry (in the Desktop sub-menu).
90 or 270 degrees rotation has a  bug in the touchpad rotation. The cursor freezes and to revive it you must have a(ny) keyboard key pressed. Even a dead key like the "journal" or the "double rectangle" key. An external USB mouse is OK though.
I find it is still usable as a book reader since in this mode you do/can not use the touchpad anyway.

Download and install XOpup-2.RC2.tar.gz (md5sum: a75e3c00dfbe3f4fb6cbed8143a6b577).
If you already using xopup-200 should/will auto-update your installation so you can keep the same savefile.

As usually please check the announcement for more info and the change log for a more detailed list of changes and functions.

Have fun and please report any issues so we can get to XOpup-2 "final"

[Zelenogorets]

mavrothal,

RC2 was my first attempt to install XOpup on my XO-1. I had previously updated to firmware Q2E45 and the XO software release 10.1.3, to avoid encountering any trouble from that area.

I made use of a 4 GB SD card, which now has (in rough numbers) a 3.75 GB ext3 partition and a 0.25 GB swap partition.

The initial boot into XOpup went well, except that it was unable to recognize the built-in wireless networking device. After rebooting for the first time back into Sugar, for confirmation that eth0 would still be recognized there (and it was), I rebooted into XOpup; that time around, eth0 was recognized, and has worked well since then under XOpup.

On discovering that Midori (its default browser) doesn’t support https-schemed URLs, I downloaded and installed the Firefox 3.6.13 pet. On running it for the first time, it gave notification that the included Flash plugin was out of date; I then went to the Adobe site to download the latest Flash plugin for Linux (in the .tar.gz package, since I didn’t know which packaging systems XOpup supported). After installation of the latest Flash plugin, I then tried visiting two sites which my daughter enjoys, but which are unusable under both Sugar and GNOME on her XO-1. The innerstaru.com site is still unusable under XOpup, but the webkinz.com site is now usable with XOpup!

When I told her about that, she immediately expressed interest in using her XO-1 to visit the Webkinz site; so, I shut down my XO-1, put my SD card in her XO-1, and tried starting up XOpup on hers. However, her eth0 device was not recognized under XOpup. (She also has firmware Q2E45 and software release 10.1.3 on her XO-1.) I then shut hers down, put the SD card back in mine, and found that my eth0 was still recognized in XOpup.

Since then, I have downloaded and installed the xopup_devx_201.sfs file to allow XOpup development.

This particular series of events left me with the following questions/comments; I hope that you’ll be able to answer the questions.

• Is it typical for eth0/wlan0 (whichever is the preferred name under XOpup) to be completely unrecognized on the initial boot? I’m glad that it was recognized under the second boot-up, but if it is typical to not be recognized initially, I wouldn’t have bothered with an initial series of a dozen or so auto-probes during the first boot-up to find the interface that I thought would have been recognized initially.

• I’ve noticed that when XOpup boots up, its ext3 journal needs recovery each time. Does the ext3 filesystem not get cleanly closed when XOpup is shut down or rebooted? (The ext3 filesystem is apparently closed cleanly when unmounted under Sugar, since the recovery message doesn’t appear on an XOpup boot which directly follows a Sugar shutdown.)

• The initial boot into XOpup showed a discrepancy in the timezone between the software and the hardware. Once I had set the hardware’s timezone to be UTC, set the software’s timezone to its proper local setting, and adjusted the software clock to match the hardware clock, everything was straightened out.

• When time synchronization is set up for autostarting, should the window with the Autostart/Remove Autostart/Close buttons appear each time? (I would have thought that the window would only appear once, when setting up the autostart, and silently autostart on subsequent boots.)

• Should my SD card be usable as-is on any other XO-1 with the same firmware installed? I was surprised that networking wasn’t available on my daughter’s XO-1 even though it was available on mine, both before and after her boot of XOpup. (Our Internet access is provided by the same wireless router.) For example, is there anything under XOpup that might tie networking access to a particular eth0’s MAC address?

• My daughter’s preferred wallpaper is the one with the trampoline.

• Much to my surprise, I found that vi (or a clone such as vim) was not part of XOpup — not even as part of the developer’s SFS. (I have no idea what “busybox” is, which is what /bin/vi is linked to — but if there’s anything that it isn’t, it isn’t a vi clone!) As a result, the first pet which I’d sought after was a vi work-alike. I eventually found a link to an out-of-date version of vim, but its hosting website didn’t provide a straightforward download link, so I decided to compile an up-to-date version of vim under XOpup. I now have vim 7.3.107 running locally; what would it take to make this into a pet for XOpup?

• I was also surprised to find that the man program under XOpup is a link to a “pman” script, which starts Midori to show online documentation — and to add insult to injury, Midori on starting up under pman complains that libaspell.so.15 is unavailable (“cannot open shared object file: No such file or directory”). Looking at the source of /usr/bin/pman, it notes that the real man program should be under /usr/local/bin; however, under XOpup, the man program isn’t there. I also found that there are only a handful of man pages in the /usr/share/man hierarchy. Is there a pet available that contains /usr/local/bin/man and the various hierarchies of man pages?

Finally, I’ll add my voice to the chorus of people here who are thanking you for making XOpup available. Thank you!

(Edited to add a couple of points which escaped my mind the first time around.)