"bootmanger" For Zaurus

[CoreDump]

[...]
Now I need a simple howto for that ext2loop_rootfs.bin... unless you can supply a small one for testing to prove that this works on a poodle. I would be happy with a bootstrap.

I've uploaded a poodle ROM + cardfs and a poodle ext2loop here:
http://hentges.net/tmp/do_not_use/poodle/

Any feedback is welcome
Please note that this release is completly untested  

@JohnX:

I wouldn't worry about it. The only people likely to need an option like that are the people who are hacking up their own ROM image. It would be imppossible to chase down all the different options and script them in. I'd rather have a simple straight-forward script to hack on, than one that tried to do everything and became so complex that it was difficult to understand and modify.

Good point. I'll leave the current implementation as is is.

[Greg2]

I've uploaded a poodle ROM + cardfs and a poodle ext2loop here:
http://hentges.net/tmp/do_not_use/poodle/

Any feedback is welcome
Please note that this release is completly untested 

First of all I would like to thank you for all the work you've put into this, especially since you don't have a poodle to test it on.

Now for the bug report:

Before I flashed your 'poodle-image' I attempted to boot of my SD-card with your 'ext2loop-poodle' using your altboot I had installed previously in this thread. The bootmanager came up as normal and I selected [4] to boot from SD. The process started and failed at:

Code: [Select]

* * * Booting rootfs image * * *

ERROR: mount -o loop /media/card/boot-images/rootfs.bin /media/image failed!
/bin/sh: can't access tty; job control turned off
/media/card/boot-images #I had built an 'ext2-image' from my 'flash-image' earlier today and had the same results but I thought I would wait and try one of yours.

So it would appear that there is something different with the poodle that I missed.

I than installed your T2-RC3-DE, zImage-poodle.bin and cardfs-poodle from the “do not use” folder. For this I used the updater.sh from the 3.5.3 feed.
After the flash was completed (kernel and initrd.bin), I reset the unit as normal... but instead of your installer coming up to install the cardfs-poodle the altboot comes up first and stops at:

Code: [Select]

altboot v0.0.1

                [1] Normal boot
                [2] Single user mode
WARNING: /etc/altboot-menu not found
[ ]
WARNING: Using failsafe shell
/ #
So I need a way to call up your installer before the bootmanager?
Edit: I should explain that it never boots the first time to configure anything before the bootmanager.

Seriously, don't let this give you a headache... I will flash back to my working system for tonight.

Thanks


Greg

[JohnX]

Code: [Select]

* * * Booting rootfs image * * *

ERROR: mount -o loop /media/card/boot-images/rootfs.bin /media/image failed!
/bin/sh: can't access tty; job control turned off
/media/card/boot-images #
I don't think this is a poodle vs collie thing.  This is the same error I got when trying altboot for the first time from my OZ 3.5.3 install.  I think the version of mount that comes with OZ 3.5.3 doesn't understand the -o loop option.  If you feel comfortable hacking up the script a little you can replace the line that mounts the rootfs.bin file (in /etc/altboot-menu/15-bootSD) with one that first runs losetup to associate /dev/loop1 with the rootfs.bin file, then mount /dev/loop1 to /mnt/image.  I'll post more detailed instructions later...

Code: [Select]

altboot v0.0.1

               [1] Normal boot
               [2] Single user mode
WARNING: /etc/altboot-menu not found
[ ]
WARNING: Using failsafe shell
/ #
I have no idea about how the updater.sh works or what exactly happens when flashing a new ROM image onto a poodle...but it seems like something must have gone not entirely right, leaving you with /sbin/init still linked to /sbin/init.altboot.  Apparently /etc/altboot-menu got hosed during the flash though.  I would do exactly like you said and just do a complete flash to a known working system.

[CoreDump]

ERROR: mount -o loop /media/card/boot-images/rootfs.bin /media/image failed!
/bin/sh: can't access tty; job control turned off
/media/card/boot-images #

This might be the problem JohnX detected in the collie build. I've updated bootSD since then but the change didn't make it into the release. Interestignly this shouldn't happen in a hentges-style ROM as I use the "real" mount in these images.

altboot v0.0.1

              [1] Normal boot
              [2] Single user mode
WARNING: /etc/altboot-menu not found
[ ]
WARNING: Using failsafe shell
/ #

Ugh, yeah. This is a known busybox bug present in all current OZ snapshots. The fix is simple but wasn't commited into OE (a patch is going balistic). I manually fixed the collie build and now did the same for poodle.

I'm currently uploading a new initrd.bin and a new ex2loop image.
Please wait 2 hours after this post, the upload is going to take some time and I can't "babysit" it.

[Greg2]

I'm currently uploading a new initrd.bin and a new ex2loop image.

This image installed with only one problem and that's an easy fix... ipkg-link failed because there was no:

dest sd /media/card/

in ipkg.conf to link your cardfs.

I added it and ran ipkg-link and everything that I have checked so far is working but the keysounds and touchsounds, etc. Xmms works and the sound files are there... I believe this was a problem in another version iirc.

The bootmanager works and your oz-opie-ext2loop-poodle booted up and works perfect except for touchsounds and keysounds, etc.

I have to go now, but I will check out all the little things later tonight or tomorro.

Would you consider making your cardfs on a poodle install to /home... there is room (35840 kb), and it should work without much modification to your installer? The poodle /home is mtdblock3 and should install and ipkg-link about the same as /media/card?

Thanks

Greg

[CoreDump]

I'm currently uploading a new initrd.bin and a new ex2loop image.

This image installed with only one problem and that's an easy fix... ipkg-link failed because there was no:

dest sd /media/card/

in ipkg.conf to link your cardfs.

Hmm interesting. Are you sure that "dests" for SD and CF are configured in stock OZ ROMs? When I look at how OE handles the poodle, I'd think not. Which - of course - would be a bug, or maybe not?

I added it and ran ipkg-link and everything that I have checked so far is working but the keysounds and touchsounds, etc. Xmms works and the sound files are there... I believe this was a problem in another version iirc.

That indeed might be a problem in current snapshots. I'll see what I can find out.

The bootmanager works and your oz-opie-ext2loop-poodle booted up and works perfect except for touchsounds and keysounds, etc.

Great :-)

I have to go now, but I will check out all the little things later tonight or tomorro.

Would you consider making your cardfs on a poodle install to /home... there is room (35840 kb), and it should work without much modification to your installer? The poodle /home is mtdblock3 and should install and ipkg-link about the same as /media/card?

While that would be possible, it would fill up your "home" partition. A compressed cardfs image is about 20MB. I do not believe that this would be such a good thing, but we can try how it works out.

[Greg2]

Hmm interesting. Are you sure that "dests" for SD and CF are configured in stock OZ ROMs? When I look at how OE handles the poodle, I'd think not. Which - of course - would be a bug, or maybe not?

No it's not in the stock OZ-roms, but wouldn't it be needed in your version on the first boot for the installer to link your cardfs properly? Wasn't it (dest sd) already in your collie version?

Everything else on this image I've checked works. I can find no problems that we don't already have with the 3.5.3 (e.g. The on/off button start problem)

Would you consider making your cardfs on a poodle install to /home... there is room (35840 kb), and it should work without much modification to your installer? The poodle /home is mtdblock3 and should install and ipkg-link about the same as /media/card?

While that would be possible, it would fill up your "home" partition. A compressed cardfs image is about 20MB. I do not believe that this would be such a good thing, but we can try how it works out.

I normally always 'almost' fill up /home on my poodle before installing to my SD-card... the apps run a little faster there. With your new bootmanager installed it opens many possibilitys for that SD-card space. IMHO this would also be a very useful feature for the clamshell owners who have a large /home to use. (which I hear may soon be of interest to you)

Thanks again,

Greg

[CoreDump]

No it's not in the stock OZ-roms, but wouldn't it be needed in your version on the first boot for the installer to link your cardfs properly? Wasn't it (dest sd) already in your collie version?

Yes, the SD dest is needed. I was more asking if there could be a reason for the SD and CF dests to be excluded from the original ROMs. If there isn't one, we could change that for the next OZ release.
I've never seen or used a Poodle IRL so this question might sound stupid  
Is the missing SD and CF dest a bug or a feature of stock OZ ROMs?

Everything else on this image I've checked works. I can find no problems that we don't already have with the 3.5.3 (e.g. The on/off button start problem)

That's good to hear, and just prooves how flexible OpenEmbedded is. There were only very few
changes required to switch from Collie to Poodle  Way to go OE  

While that would be possible, it would fill up your "home" partition. A compressed cardfs image is about 20MB. I do not believe that this would be such a good thing, but we can try how it works out.

I normally always 'almost' fill up /home on my poodle before installing to my SD-card... the apps run a little faster there. With your new bootmanager installed it opens many possibilitys for that SD-card space.

Good point. I'll start hacking the installer today or tomorrow. Having a configurable cardfs destination is more elegant than a hard-coded path anyways  

IMHO this would also be a very useful feature for the clamshell owners who have a large /home to use. (which I hear may soon be of interest to you)

 

[Greg2]

Yes, the SD dest is needed. I was more asking if there could be a reason for the SD and CF dests to be excluded from the original ROMs. If there isn't one, we could change that for the next OZ release.
I've never seen or used a Poodle IRL so this question might sound stupid   
Is the missing SD and CF dest a bug or a feature of stock OZ ROMs?

I would have to call it a bug on a poodle. I can't find a reason for the SD, CF and /home to be excluded. It only comes with:

dest root /

This is what I use:

dest root /
dest home /home/
dest sd /media/card/

Why we are on the subject but o/t here... what is the purpose of the 'package' directory that so many users are using? (/media/card/packages/)

I'll start hacking the installer today or tomorrow. Having a configurable cardfs destination is more elegant than a hard-coded path anyways

Thanks, I was hoping you would think that!

Greg

[CoreDump]

I would have to call it a bug on a poodle. I can't find a reason for the SD, CF and /home to be excluded. It only comes with:

dest root /

This is what I use:

dest root /
dest home /home/
dest sd /media/card/

Fixed  in OE

[CoreDump]

I've just finished uploading a new version:
http://hentges.net/tmp/do_not_use/

It adds "dest" entries to ipkg.conf and cardfs can be installed onto every ipkg "dest" (SD / CF / home)
Please test

[Greg2]

I've just finished uploading a new version:
http://hentges.net/tmp/do_not_use/

Warning

Do not try to install the cardfs to /home with this poodle image!

I'll be back later to explain.

Greg

[CoreDump]

I've just finished uploading a new version:
http://hentges.net/tmp/do_not_use/

Warning

Do not try to install the cardfs to /home with this poodle image!

I'll be back later to explain.

Greg
[div align=\"right\"][a href=\"index.php?act=findpost&pid=82911\"][{POST_SNAPBACK}][/a][/div]

Guess it's a little big to large huh?

[Greg2]

Guess it's a little big to large huh?

Yes... just a wee bit.  

I've found some problems with your installer installing to /home.

When you select [3] for /home it seems to be ok, but then it insist on formatting your SD-card before the install... or it will not install the cardfs. When you say ok it formats mtdblock3 where /home is to ext2. This may or may not be a problem... although I would rather leave my mtdblock3 as jffs2. Then the install stops because there is no more room on /home... /home is full because an ext2 /home is smaller (holds less because jffs2 is compressed) then a jffs2 /home.

Now because of one or both of these problems when you reboot... mtdblock3 is gone! You still have a working system... but a very small one, hehe! (22528 kb)

Anyway I could find no way to fix mtdblock3 except for my 'first' NAND restore from a NAND file I made a long time ago. So I'm setting here looking at my Z with a sharp 'ROM' on it (it's the only NAND I had) but a smile on my face because mtdblock3 is back!

I'll return to OZ tomorrow... I'm tired and I might screw something else up.

I should note here that if there are any questions please ask... I was so amazed at what was happening that I took pics of the screen.

Is there a way to do this without formatting /home?

Thanks, and please don't give up on the poodle.

Greg

[CoreDump]

Guess it's a little big to large huh?

Yes... just a wee bit.  

I've found some problems with your installer installing to /home.

When you select [3] for /home it seems to be ok, but then it insist on formatting your SD-card before the install... or it will not install the cardfs. When you say ok it formats mtdblock3 where /home is to ext2. This may or may not be a problem... although I would rather leave my mtdblock3 as jffs2. Then the install stops because there is no more room on /home... /home is full because an ext2 /home is smaller (holds less because jffs2 is compressed) then a jffs2 /home.

Err. Now that's a nasty one. The installer never was intended to install into flash so it only checks for
an ext2 or ext3 filesystem on the target. If none of these is found it formats the target because I had all sorts of problems from people trying to install cardfs onto a VFAT filesystem  

I've fixed this problem and the filesystem check now aborts when it finds the target to be a /dev/mtdblock* device.

Now because of one or both of these problems when you reboot... mtdblock3 is gone! You still have a working system... but a very small one, hehe! (22528 kb)

 

Anyway I could find no way to fix mtdblock3 except for my 'first' NAND restore from a NAND file I made a long time ago. So I'm setting here looking at my Z with a sharp 'ROM' on it (it's the only NAND I had) but a smile on my face because mtdblock3 is back!

You may have gotten away with booting into init=/bin/sh and re-formatting the partition w/ jffs2.
This would be a major PITA though as jffs2 needs a hell of a lot of parameters.

I'll return to OZ tomorrow... I'm tired and I might screw something else up.

I should note here that if there are any questions please ask... I was so amazed at what was happening that I took pics of the screen.

Is there a way to do this without formatting /home?

Thanks, and please don't give up on the poodle.

Greg
[div align=\"right\"][a href=\"index.php?act=findpost&pid=82925\"][{POST_SNAPBACK}][/a][/div]

Fear not   I'm uploading new images as we speak, check back in 2 hours or so (can't babysit the upload ATM).

Sorry for that. This was a major f*uck up on my part  
If this would have been the "updater" partition as found on some newer models, the PDA would be toast    

I'll add a few more fail-safes to the installer so it won't ever format a mtdblock partition again.