I've been looking for a linux distribution with a recent kernel to try out a few things on my son's XO-1.

All XO distributions, official or otherwise, use the same OLPC kernels. ie 3.3 for XO-1 and XO-1.5, 3.5 for XO-4 and 3.0 for XO-1.75.
To that respect any recent XO-moded puppy included quirky have the same kernel._________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too

All XO distributions, official or otherwise, use the same OLPC kernels. ie 3.3 for XO-1 and XO-1.5, 3.5 for XO-4 and 3.0 for XO-1.75.
To that respect any recent XO-moded puppy included quirky have the same kernel.

Good. So that answers my first question (although I didn't have time to ask)! I thought some of the unofficial distributions didn't use the OLPC kernel, but now I know better. I guess there must be specific drivers compiled into this kernel.

I thought some of the unofficial distributions didn't use the OLPC kernel, but now I know better.

Some key changes in the OLPC kernel never made it into the official Linux kernel tree. So no other kernel will boot an XO.
The XO-puppy kernel is not exactly the same as the official (has some configuration changes) but is the same kernel source as the official.
If you need some modules that are not build in the current kernels, but they exist in the 3.3 source, let me know._________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too

As with the alpha version, you can also install FatDogArm in the internal XO card parallel to Fedora/Sugar and have a dual boot system that will boot to FD when the "O" game-key is pressed during power up.
To install in the internal flash storage, download the attached install_fd-b1_internally.sh.gz script in your XO, expand it, make it executable and run it as root, while you are connected to the internet.
If you do not have an internet connection in your XO just copy the scrip, fd-arm.sfs, and xo{175,4}-kernel.tar.gz in your XO and run the script.
NOTE:The script will not run if you already have an alternative boot option (/bootpart/boot/atl) in your XO

install_fd-b1_internally.sh.gz

Description

Script to install FatDogArm_beta1 in the internal storage of the XO-4 or XO-1.75, parllel to Fedora/Sugar.

Its been quite a while since I have used my xo-1 either with XO-pup or sugar. I think I will start trying to use them again. I know you have created many pups for the XO, and just wondered which you yourself use at the moment.

I know you have created many pups for the XO, and just wondered which you yourself use at the moment.

The original XOpup-2.2 s still in my XO-1's SDcard. I find it the most responsive and being based on Puppy Lucid 5.2.x is well stocked with apps. The browser choice is not very good but the hardware can hardly cope with the demands of modern browsers. You can still install Google Chrome though if you can tolerate the slow response.

On my XO-1.5, the SDcard has Precise-5.5_XO but Precise-5.6.1_XO is is probably better (too lazy to do all the customization again )
It is OK on the XO-1 too but noticeably slower. Go for it if Ubuntu 12.04 has apps that you need and do not exist in Ubuntu 10.4, or if for some reason (driver) you need the 3.3 kernel._________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too

I live in Argentina and I found a batch of old OLPC XO-1 B1 laptops (256mb RAM, batteries plain dead) and wondered if i could bring them back alive. I stumbled upon this thread and I was astonished of all your hard work on getting to work on Puppy. Big kudos all of you folks!

I managed to flash them from creepy old OpenFirmware builds to most recent one (q2f20) and boot into every puppy flavor i could find: XOPup, Precise, Racy, Slacko, etc (best so far Precise 5.6.1)

Fast forward: i'm stuck in trying to get Xorg to work. Tried with all posible "profiles" from xorgwizard but the best i could get is what depicted in the attached pic using "xorg.conf.t2"

B1 is a strange animal.
I would recommend to first downgrade the firmware to q2e18 or the last "official" for B1s version, q2c27. link
Then try to boot some official build to see which one will work. I would start with 8.2.1 then 11.3.0 and them maybe 13.2.1. link
After that and depending what is happening with the above, I would try with an older kernel pup (XOpup up to 5.5s) and see how it goes.

BTW which puppy version is the logs and picture from 5.6.1?

PS: Regarding official firmware and builds for B1s you can ask in the olpc devel list. Is still active and usually helpful._________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too

Hi
(Im a linux innocent and unfamiliar with terminal)
I have an XO 1.5 and have replaced the internal microSD with a larger one.
I want to install XOpup to it and use the External SD as storage.

Yet I can neither see the internal SD from XOpup on USB nor install to it as the option is given as unavailable in XOpup.

I guess I could remove the microSD and extract XOpup to it but I assume it will still not let me mount the internal drive etc

Up thread I read this but I dont quite understand "what and where needs to be put back"

Quote:

I'm not sure about this.
I have modified pup_event_frontend_d NOT to automount the internal SDcard of the XO-1.5, so users will not inadvertently messup with it.
This maybe affecting the boot process. Just put back the original and see.

Further, the MicroSD I have installed is a single etx2, is that going to be an issue?

Quote:

I do not know what you have in the internal SDcard but I think that the issue might be that you put the files in the big mmcblk0p2 partition?
OFW can not read this because is etx4. The boot* folders must go to the ext2 mmcblk0p1 but then the init must be instructed to look in another partition for the sfs. Confused

...or it could be the olpc.fth setup. The way it is now defines the internal SD as "PDEV1=mmcblk1p1", but without an external card the internal is "mmcblk0p1". Change line 106 of /boot/olpc.fth accordingly and see what happens. Actually this looks like the most likely reason since pup_event is not coming into play during init boot.
Anyway I would stay out of the internal SDcard/NAND as principle, but if people ask it can be done properly at the /boot/olpc.fth level.

Daedalum,
The original XOpup and the other puppies modified for the XOs are designed NOT to run from the internal SD and not even auto-mount it.
However, should not be difficult to install it in the internal SD. Just copy the files there and then you need to change the /boot/olpc.fth file a bit.
Changing 1 to 0 in line 117 as shown below, should do it

Quote:

" PDEV1=mmcblk0p1" \ Internal SD card

Be advised that I (or anyone else I know) never tested XOpup from the internal SDcard. So I really do not know if there are any issues.

To mount the internal SD card when booting XOpup form a USB/ExternalSD, open a window at the root of the file system press the "eye" to make visible the invisible files and then click on the ".intSD" folder. Should mount the internal SD card._________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum