Puppylinux for the OLPC laptops: XOpup

For talk and support relating specifically to Puppy derivatives
Message
Author
User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

XOpup-2.2.RC has been released

#151 Post by mavrothal »

Just updated XOpup to XOpup-2.2.RC (xopup-204).

There is the usual updates, additions, bugfixes etc (see changelog for details), but the most noticeable for the user, is the addition of the Frisbee network manager.

To install XOpup-2.2.RC download XOpup-2.2.RC.tar.gz expand it at the root of any USB or SDcard and boot. But first please do see the build Announcement.

To update from a previous xopup-20x build, just expand the tarball at the root of the USB/SDcard that you run XOpup from.

If you do an update instead of a clean/new install, Frisbee may have difficulties connecting immediately after the update.
Reboot after the version update and then use Frisbee for the first time.
Alternatively, before you update to version 204, install the Frisbee_XO-2.pet (in the previous page) that will properly reset your settings, and then update and enjoy.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

New power management

#152 Post by mavrothal »

One of the missing features in XOpup power management was to properly detect external mice and keyboards and not dim/blank/sleep while they were used.

Not anymore :D

Thanks to the new olpc-kbdshim-19 from the OLPC folks (pgf) and a lot of messing around with it, XOpup can now "see" the use of external mice/keyboards and act accordingly.

Just download and install the attached kbdshim_udev_19-1.pet, reboot and you are set!

Work in all XOpups from 2.0 onwards.

Note: Since OLPC power management, powers down the USB ports when in suspend, the XOpup will not auto-suspend on prolonged user inactivity when an external mouse/keyboard is attached.
Will dim and blank OK, though.
Will also suspend fine when the lid is closed or the power button is pressed.
Attachments
kbdshim_udev_19-1.pet
proper detection of external mice and keyboards of the XOpup power management
(12.95 KiB) Downloaded 369 times
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

XOpup-2.2 Release

#153 Post by mavrothal »

Almost 2 years to the date after my Puppylinux-on-XO saga started, 1 year after the first XOpup build was released and 15 builds latter :shock: ...
XOpup-2.2 is out.

Image

XOpup-2.2 integrates updates from (the terminated ? :( ) Puppylinux 5.2.x series, Woof/Wary development, latest OLPC software, various pets and some stuff unique to XOpup.

From faster boot and peripherals-aware power management, to friendly network manager and customization scripts, XOpup has come a long way from the original build. Now looks like a useful OS for the aging XO-1 and the (soon to be replaced by XO-1.75) XO-1.5.

Using the extended Lucid-puppy pet repository and the Ubuntu 10.04 LTS packages, has the ability to carry the XO-1 to the end of its useful life and provide a viable alternative to XO-1.5

Unless major issues are found, I doubt that will be another XOpup build.
I'll try of course to support XOpup the best I can.
It was a fun and educating process for me.

But do not despair, 01micko is developing Slackware Puppy, a Puppylinux 5.3 candidate, and said more than once that he is planning to make it available for the XO too.
So let's give him a hand :wink:
Last edited by mavrothal on Sun 21 Aug 2011, 07:59, edited 2 times in total.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#154 Post by 01micko »

Slacko has a zdrv, which should make things a little easier to separate :)

As soon as final is released (late September), I'll be back playing in Xo land.. SlaXO land.. :lol:

Let me know mavrothal if you think the video drivers need to be updated. (you can get the versions by looking at "Packages-puppy-slacko-official" on the puppy servers.)

Cheers
Puppy Linux Blog - contact me for access

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#155 Post by mavrothal »

01micko wrote: Let me know mavrothal if you think the video drivers need to be updated. (you can get the versions by looking at "Packages-puppy-slacko-official" on the puppy servers.)
Cheers
I'm not sure which version of geode_drv Slacko is using but anything above 2.11.9 is OK for the XO-1. Slackware 13.37 is using 2.11.10 so I assume is the same for slacko, Should be OK.
The XO-1.5 though needs the chrome driver to be compiled from source, since is not upstreamed to Xorg AFAIK.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#156 Post by mavrothal »

mavrothal wrote: The XO-1.5 though needs the chrome driver to be compiled from source
I compiled it in Slacko 4991 (after downloading a couple of dev packages). No issues. :D

Now we need to know if it works...

Anyone with a VIA7 CPU, VX855/VX875 chipset running Slacko?
Attached, just in case... :wink:
Attachments
chrome-driver_slacko.tar.gz
(183.55 KiB) Downloaded 340 times
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

Did you say "SlaXO"?

#157 Post by mavrothal »

mavrothal wrote: Anyone with a VIA7 CPU, VX855/VX875 chipset running Slacko?
Well... I have one :D :D :D

Image

This is with the XOpup-2.2 kernel/intrd (though the init script is the original), the chrome driver posted above and the XOpup's xorg.conf.
Adding udev 165 from official slackware, olpc-kbdshim-udev, powerd, olpc-brightnes, olpc-volume, olpc-rotate and the wireless firmware, the XOpup's battery monitor, and rc.local and a small addition in rc.sysint, is in perfect working order :D
It does need a rotation aware window manager though :lol:
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#158 Post by 01micko »

Remarkable! :D

So what works and what doesn't? Did the zdrv make transforming any easier? Did you get my latest Pupdial from Slacko thread? I'm working on an NLS version with gettext...oh and openbox/fbpanel from ppm mostly works..

:) :D :lol: :twisted:
Puppy Linux Blog - contact me for access

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#159 Post by mavrothal »

01micko wrote:So what works and what doesn't?
At the end, EVERYTHING WORKS, including power management.
Starting with the original slacko4991, failed totally to pass OFW screen and get to console. Is VIA enabled in the kernel config?

Adding the XOpup kernel got me to startx which failed because the xorgwizard does not even offer the XO resolution (1200x900). Though I'm not sure would have worked even if it was there.

Adding the chome driver, the xorg.conf and `modprobe mousedev' got me to a functional desktop with sound.

Adding the wireless firmware (it is present compressed in the zrdv) got me network.
Did the zdrv make transforming any easier?
No. But the "problem" is that the XOpup initrd.gz has the entire kernel and modules (since it has only the XO-specific ones). So does not need anything else.
At some point I might rework the XOpup initrd with just the needed modules and then move the rest to zdrv of the sfs
Did you get my latest Pupdial from Slacko thread?

Not yet
I'm working on an NLS version with gettext
Aaa ha! Thinking globally I see :D
openbox/fbpanel from ppm mostly works
Not really, but enough to verify that rotation works. :)
It needs fbpanel configuration and an fbpanel-aware fixmenus to be OK.
And some how it managed to mess-up the JWM tray with no Startup tray applications running. I guessed it did something to .xinitrc. I'll have to check.

On different note, I have all the changes and additions (except the kernel) in a tarball. Is only ~850kb (too big for posting) and most of it is udev-165. We could do without it, using the kbdshim-udev from post above in this page and the rc.local from xopup-204, but I think is better to follow "upstreams" as much as possible. Minimizes hacking, facilitates maintainability and can be easier woofyfied :wink:
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#160 Post by 01micko »

Ok, this is great!

Anything you can think of that can make things easier for olpc in general Slacko development? (BTW, I enabled what I thought would be ok, considering olpc in the kernel, knowing it was doomed anyway! [patches are probably needed])
I wrote:Did you get my latest Pupdial from Slacko thread? I'm working on an NLS version with gettext..
mavrothal wrote:Not yet. Aaa ha! Thinking globally I see :D
Yes! Actually started a Spanish trans from my feeble knowledge of Spanish and google translate :lol:

Note that all the necessary stuff for openbox/fbpanel (fixmenus etc) is available; DaveS and myself are onto making a package :wink: I'm also interested in Iguleder's work with Window Maker, reckon's he has his own fixmenus and all, of course more investigation needed. I just think openbox/fbpanel is too slow. Maybe pekwm/tint2? (fixmenus exists :wink: thanks to Musher0)

Early days .. will be fun!

Cheers
Puppy Linux Blog - contact me for access

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#161 Post by mavrothal »

01micko wrote: Early days .. will be fun!
Indeed! :lol:

I already uploaded in datafilehostSlaXOfy.tar.bz2 - NO GO
Expand it at the root of the squashfs-root and your puppy is good for the XOs (provided the right kernel of course)
It has the XO-1.5 driver and xorg.conf for the XO-1 and XO-1.5, power management and keyboard recognition, udev and some modifications in puppy scripts plus rc.local.
Actually it should work for any puppy provided it has a geode driver and that the (truncated) Slackware udev-165 is not going to give any problems.

Latter And since we are up to it,... I also uploaded make_initrds.tar.bz2 that will build the XO-1/XO-1.5 intrd/vmlinuz (based on the xopup-205 kernels) out of any puppy's initrd.gz. - NO GO
Just copy the original initrd.gz into the folder and run the build.sh script.
So when beta2 is coming out? :lol:

PS see 2 posts below
Last edited by mavrothal on Mon 22 Aug 2011, 05:34, edited 2 times in total.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#162 Post by 01micko »

mavrothal wrote:So when beta2 is coming out?
This week some time.

What I can do is do a specialised woof build for SlaXO, with the prefix and everything in place, also add in scripts which are compat with the main repo. Do you have a browser preference? I can build in any browser, however I prefer not to build in Chrome browsers as they need extray nss/nspr libs from seamonkey, a bit too bloated too. Opera needs them too but isn't so large.

Also, can you point me to specialised pets so they can be included?

Later.. actually I can just pet the SlaXOfy.tar.bz2 file and that should cover it for now, and I can specify in woof to not build all the unnecessary Xorg drivers and other stuff.
Puppy Linux Blog - contact me for access

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#163 Post by mavrothal »

01micko wrote: What I can do is do a specialised woof build for SlaXO, with the prefix and everything in place, also add in scripts which are compat with the main repo.
Hold on a bit
Actually the make_initrds has the kernels mixed up and the wrong olpc.fth (too late last night :oops: )
The SlaXOfy is mostly OK (just needs a couple of additions) but when I tested on the XO-1 took 2 minutes !!! to do the `udevadm settle' step in rc.sysinit. In XOpup takes about 5 secs. So I have to look over the slackware udev to see what the issue might be .

Give me a couple of days
Do you have a browser preference?
Actually I was delighted to see that Seamonkey 2.3 works in XO-1! Previous2.x versions failed (is XOpup). So Seamonkey it is!

Another thought... maybe we need a new thread for SlaXO?....
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#164 Post by 01micko »

Just a quick play.. no boot though..

Code: Select all

#!/bin/sh

# Make Puppy initrds for the OLPC XO-1 and XO-1.5

#set -x

CWD=`pwd` #just for standards
CORRECTDIR=`echo $CWD | grep make_initrds`

if [ "$CORRECTDIR" = "" ] ; then
	echo "please run the script from within the \"make_initrds\" directory"
	exit 0
fi

if [ ! -f $CWD/initrd.gz ] ; then 
	echo "please copy the puppy initrd.gz into the \"make_initrds\" directory"
 	exit 0
fi



for DIR in XO*

do VER="`echo $DIR|sed -e 's%^XO%%' -e 's%kernel$%%'`"
 case $VER in
  1)VERDIR=10
    XO=XO1 ;;
  1.5)VERDIR=15 
     XO=XO1.5 ;;
  *)echo "not supported" && break && exit 0 ;;
 esac
 
[ -f $CWD/boot${VERDIR}/initrd.* ] && rm -f $CWD/boot${VERDIR}/initrd.*

echo "Making the $XO initrd.gz"

cd $CWD/initramfs

gunzip -c ../initrd.gz | cpio -i
sync
rm -rf lib/modules/*
cp -aR ../$DIR/* .
sync
find . -print | cpio -H newc -o | gzip -9 > ../boot${VERDIR}/initrd.gz
sync

rm -rf $CWD/initramfs/* 
echo "find kernel and initrd in the $DIR diectory"
done

cd $CWD

echo " Done! "
#echo "find kernels and initrds in the \"boot10\" and \"boot15\" folders"
exit 0
Puppy Linux Blog - contact me for access

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

XOfy

#165 Post by mavrothal »

01micko wrote:Just a quick play.. no boot though..
Looks good to me 8)
Though, before seeing this I had already uploaded XOfy.tar.gz (md5sum: 2403e5eb9cd49d6c745231b02ecce5c6) that has both the corrected kernels and the files and a mini howto that I hope you will script :wink:
I left the full udev out, aiming for a more generic version* and udev can be woofed-in from the distro package list or just installed afterwards.
Some looking into udev solved the loooong module loading process.
Hopefully Barry will include my little suggestion into the next woof (upstreaming :wink: ) and make things a bit simpler.

* Tried it with slack and lupu-258. Actually in lupu worked even without the full udev. Something to look at...
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

SlaXO booting

#166 Post by 01micko »

Hi mavrothal

Nice!

Typing from SlaXO now!

Very painless to set up, remarkable indeed!

There is a bug in the init script where XO can't boot from mmcb1kp1 (internal SD card).. but that should be easy to fix. I am booting from usb stick no problem. I'll report to Barry.

So far, I got 2 barks at a sane volume, Cam works in gnome-mplayer.. sorry no screenshot as mplayer is notorious for not showing in mtpaint captures... woops, just went to blacksceen, something with power management, just hit power button to recover.

I will test ffmpeg (on the XO-1.5 atm) and the equalizer see if they work...YES! pequalizer works perfect! You can save a preset for XO's tinny speakers too, makes an improvement

I'll script up your little tutorial

Cheers!

Later.... Ok, tried on XO-1, same usb stick install with save file from XO-1.5. Naturally had to run xorgwizard and alsa was messed but fixed easily. The equalizer works there too, so does the Cam. Seamonkey is a bit like treacle but stable. I might compile Dillo with a view for using in XO-1, it's very light and will be swift on the limited hardware.

Start a new thread I think, as I said, early days for SlaXO
Attachments
SlaXO-1.png
XO-1
(160.61 KiB) Downloaded 1178 times
SlaXO.png
XO-1.5
(78.89 KiB) Downloaded 1243 times
Puppy Linux Blog - contact me for access

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

Re: SlaXO booting

#167 Post by mavrothal »

01micko wrote:
There is a bug in the init script where XO can't boot from mmcb1kp1 (internal SD card).. but that should be easy to fix. I am booting from usb stick no problem. I'll report to Barry.
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.

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. :?

...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.
woops, just went to blacksceen, something with power management, just hit power button to recover.
Yes, if you do not have the full udev installed the user activity monitoring daemon (kbdshim-udev) is not working.
Later.... Ok, tried on XO-1, same usb stick install with save file from XO-1.5. Naturally had to run xorgwizard and alsa was messed but fixed easily
.
Actually, you do not need to do that. Just delete xorg.conf and reboot or copy the included /etc/X11/xorg.conf.XO-1 to xorg.conf and startx :)
I guess this could be automated in the rc.local where the xorg.conf selection is done but I did not think that many "normal" users will do that, and X takes too long to load as it is already.
Start a new thread I think, as I said, early days for SlaXO
Me?...

Actually, I was thinking to try XO-drake*. Is the only rpm-based puppy spin and then maybe jump to Fed(ora)-X(O) :lol: to be closer to base. Combining the 3 upstreams woof, OLPC and Fedora will make the project just a packaging issue :wink:

* Yep, XO-drake works :D . Some hiccups but mostly OK

Come on. There are no puppy-fedora lovers? :P (though I would stay out of F14+)
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

even faster

#168 Post by mavrothal »

If you want to cut another 3-6 seconds from the XOpup-2.2 (xopup-205) boot time install the attached init-1.pet.

Do not install in earlier versions
Attachments
init-1.pet
rc.sysinit for XOpup-2.2
(5.18 KiB) Downloaded 843 times
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#169 Post by 01micko »

Latest Wary .. 8) more later

Ok, here it is....

create_xo_puppy-0.1.tar.bz2 9752K

4269fc10c76b51b127f772c5d33c32b1 create_xo_puppy-0.1.tar.bz2


Fully automated building of a bootable Puppy on the XO hardware

Code: Select all

./create_xo_puppy -i /initrd/mnt/dev_save/wary-5.1.3.2.iso
That built me an almost sane Wary.. of course you need the exact path to an iso on your machine! Only works in Puppy. It works ok on XO-1 but the chrome driver is no good on the XO-1.5.

I tested with an earlier spup aka slacko and no problem.

Have fun! :lol:
Attachments
waryXO.png
(131.91 KiB) Downloaded 1101 times
Puppy Linux Blog - contact me for access

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#170 Post by mavrothal »

01micko wrote: create_xo_puppy-0.1.tar.bz2 9752K

4269fc10c76b51b127f772c5d33c32b1 create_xo_puppy-0.1.tar.bz2


Fully automated building of a bootable Puppy on the XO hardware
Man... This is WAY cool :lol:

I'll tested latter but looks good on paper. :!:

The chrome driver must be compiled agains the puppy's xserver, but I already have the ubuntu and compiling for wary, drake, Dpup etc (hopefully) should not be a problem.
Unless of course if you want to script it from an included source 8) with a (modified) src2pet, hoping that the devx will have all the dependencies :wink:
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

Post Reply