"bootmanger" For Zaurus

[Greg2]

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

Thanks, I'll check that out later tonight. I have a more important problem in my basement with a water leak from my very old plumbing to check first.

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.

Don't worry about it, we caught it before that happened... that's why it's called testing!

Greg

[Greg2]

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

Thanks, I'll check that out later tonight.

Your installer now works perfect on the poodle for an install to /home. After the install I have available 8924 kb on /root and 6912 kb on /home.

I can find no problems except the sound problem with touch and keys that was present in the last image, but I see that this is from the same snapshot date. Has anyone else experienced this problem with that snapshot?

Anyway, thanks again for the bootmanager, and taking the time to build this poodle-image with an installer that installs to /home... or the other dest you've added!

I don't suppose you would be willing to bitbake one of those PXA255 kernels with the cache errata disabled as an option for this deluxe poodle-image? I know of the controversy about this... but many of us have had absolutely no problems using it.

Thanks

Greg

[CoreDump]

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

Thanks, I'll check that out later tonight.

Your installer now works perfect on the poodle for an install to /home. After the install I have available 8924 kb on /root and 6912 kb on /home.

Very nice.

I can find no problems except the sound problem with touch and keys that was present in the last image, but I see that this is from the same snapshot date. Has anyone else experienced this problem with that snapshot?

"Touch" sounds work perfectly fine on my collie. Does normal sound work for you? (ie: playing an mp3 or wav file)

Anyway, thanks again for the bootmanager, and taking the time to build this poodle-image with an installer that installs to /home... or the other dest you've added!

You're welcome  
I could hardly believe it that ipkg destinations were missing for poodle and no one complained about it heh.

I don't suppose you would be willing to bitbake one of those PXA255 kernels with the cache errata disabled as an option for this deluxe poodle-image? I know of the controversy about this... but many of us have had absolutely no problems using it.

Hmm shouldn't be much of a problem. I'll ask around how to build such a kernel. However, the problem is that this kernel will cause problems. I'd rather not ship a ROM with it but adding it as an option might not be a bad idea.

If I'd ship it as the default, people would be posting about the "broken" ROM when all that was broken is their CPU heh.

You have to keep in mind that a lot of Poodle users have no clue about the underlying system or their PDA's broken hardware. The people "in the know" avoided the 5600 like the plaque when it was released  

They probably bought a Collie - which was indeed the better choice. Just look how bad the Poodle support is in OZ  . I mean sheesh, no ipkg destinations. That takes like, um, 2 minutes to fix  
IIRC, not a single OZ dev owns a Poodle.

[CoreDump]

I've just uploaded another kernel with CONFIG_XSCALE_CACHE_ERRATA unset:
http://hentges.net/tmp/do_not_use/poodle/kernel/

No guarantees on stability though

[Greg2]

"Touch" sounds work perfectly fine on my collie. Does normal sound work for you? (ie: playing an mp3 or wav file)

Yes... sorry, I thought you understood that. XMMS plays mp3s, oggs 'and' the wav files in /opt/QtPalmtop/sounds/ through the internal speaker or earbuds without any problems. I've read about this problem before on the poodle and or collie with an earlier version but I can't seem to find it now... or remember where I read it. I will however keep looking.

I could hardly believe it that ipkg destinations were missing for poodle and no one complained about it heh.

That's as much my fault as anyone... I will report more bugs to the proper place.

I don't suppose you would be willing to bitbake one of those PXA255 kernels with the cache errata disabled as an option for this deluxe poodle-image? I know of the controversy about this... but many of us have had absolutely no problems using it.

Hmm shouldn't be much of a problem. I'll ask around how to build such a kernel. However, the problem is that this kernel will cause problems. I'd rather not ship a ROM with it but adding it as an option might not be a bad idea.

If I'd ship it as the default, people would be posting about the "broken" ROM when all that was broken is their CPU heh.

You have to keep in mind that a lot of Poodle users have no clue about the underlying system or their PDA's broken hardware. The people "in the know" avoided the 5600 like the plaque when it was released  

I agree with you completely. I would never suggest that it be the default kernel.

Thanks

Greg

[Greg2]

I've just uploaded another kernel with CONFIG_XSCALE_CACHE_ERRATA unset:
http://hentges.net/tmp/do_not_use/poodle/kernel/

No guarantees on stability though
[div align=\"right\"][a href=\"index.php?act=findpost&pid=83199\"][{POST_SNAPBACK}][/a][/div]

Thanks, I will try that out tonight.

Greg

[Greg2]

I've just uploaded another kernel with CONFIG_XSCALE_CACHE_ERRATA unset:
http://hentges.net/tmp/do_not_use/poodle/kernel/

No guarantees on stability though
[div align=\"right\"][a href=\"index.php?act=findpost&pid=83199\"][{POST_SNAPBACK}][/a][/div]

Thanks, I will try that out tonight.

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

The -fast-kernel works 'very' well!

You would have to have one of these poodles in your hand to appreciate the difference it makes. It improves even the little things like the balls moving across the BilliardZ table... they move smoothly now. (I think they may even roll a bit farther... heh)

Anyway, everything that did work still works. My SMC2642W card and my AmbiCom EZjack modem are detected and work fine. Hell, if I could just get my touch and key sounds working... my Poodle would be a Porsche!

It's also good to see the calculator dropdown box dropping down with options in this snapshot like it used to in Familiar 7.2! ( I can't remember if it did in OZ 3.3.6)

With all of the posting about the rboot and dual-boot and running both Opie and GPE at the same time in this forum, and on the mailing list... it's hard to believe that there are no more users posting in this thread?

Thanks for all you've done with these 'images' (rw-roms).  

Greg

[Sniffer]

Ill give this a try once im at home, by the sounds of it I will be very pleased.

[CoreDump]

The -fast-kernel works 'very' well!

You would have to have one of these poodles in your hand to appreciate the difference it makes. It improves even the little things like the balls moving across the BilliardZ table... they move smoothly now. (I think they may even roll a bit farther... heh)

Anyway, everything that did work still works. My SMC2642W card and my AmbiCom EZjack modem are detected and work fine. Hell, if I could just get my touch and key sounds working... my Poodle would be a Porsche!

It's also good to see the calculator dropdown box dropping down with options in this snapshot like it used to in Familiar 7.2! ( I can't remember if it did in OZ 3.3.6)

That's good to hear  

With all of the posting about the rboot and dual-boot and running both Opie and GPE at the same time in this forum, and on the mailing list... it's hard to believe that there are no more users posting in this thread?

Yeah, well. I guess you have to try "multi"-boot to really appreciate it  
It is unbelievable that I could live w/o it for so long. In the past, I had to flash every time I made a
change to the image - just to make sure it would work on the first boot after flashing automatically.

This is now over. Most of the time I'm building ext2 images now and boot off of SD. And having a way
to init into /bin/sh is a real life saver from time to time. This is way cool  

However, there is a problem with obtaining correctly built boot-images for the clam-shells.
Maybe if I upload new opie  / GPE snapshots for C7x0 someone will take the time to port the boot-manager to the clamshells running kernel 2.6.

This is a thing i cannot possibly do on my own. You've got to own such a device to make it work.
Basic instructions on how to mount the SD and CF card after init=/bin/sh would be enough to edit the script.

Thanks for all you've done with these 'images' (rw-roms).  

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

You are very welcome

[TimW]

I'm currently using Daniel Steen's rboot scripts for dual booting (I've got an Opie and a GPE image on SD). What are the differences/similarities (advantages/disadvantages) between what you are doing here and the rboot stuff?

[CoreDump]

I'm currently using Daniel Steen's rboot scripts for dual booting (I've got an Opie and a GPE image on SD). What are the differences/similarities (advantages/disadvantages) between what you are doing here and the rboot stuff?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=83347\"][{POST_SNAPBACK}][/a][/div]

The principle of operation is exactly the same for altboot and rboot (what does the "r" stand for btw?):
- Mount an external medium
- pivot_root into it
- call /sbin/init.

So any image that works with altboot will work with rboot and the other way around  

I didn't play with rboot a lot so I really am the wrong person to comment on its advantages or disadvantages, however the current features of altboot are:

- Written with multi-device support in mind.
- Available in OE (so it will most likely appear in the official feeds for OZ 3.5.4+)
- Due to the first two points, it could be ported to any PDA supported by OE  (iPAQ, Simpads, etc)
- Can boot ext2 filesystem "images" (ie: loop-images) and a real filesystem on the card
  You can even copy more than one image onto the card and you'll be presented a list to choose
  the one to boot (OPIE / GPE dual-boot anyone?). And there's no need to edit any config files  
- Can boot from SD and CF
- Can boot into init=/bin/sh
- Can do all sorts of nice things by writing small shell scripts which are placed into /etc/altboot-menu
  The scripts will appear in the boot menu. Having external scripts is very useful as you can't possibly
  break altboot in a way that you need the re-flash your device. Only your script will break, but altboot
  will still work just fine.
- Installation is as easy as it gets: ipkg install altboot   (just don't install it to SD or CF heh that will render your Z unbootable)

[TimW]

The principle of operation is exactly the same for altboot and rboot (what does the "r" stand for btw?):

No idea  

It sounds like overall they are pretty similar once installed so having got rboot working I'll be sticking with it. However, for the next OZ release I'll definitely give altboot a go as installation sounds so much easier, plus there seems to be some extra flexibility once it is installed.

If you need any further testing on an SL5000D though, I'm happy to give altboot a go on my "spare" device. I generally keep a Sharp compatible ROM on there for testing SharpROM releases of opie-reader so I can spare it for a test.

[CoreDump]

The principle of operation is exactly the same for altboot and rboot (what does the "r" stand for btw?):

No idea  

 

[...]
If you need any further testing on an SL5000D though, I'm happy to give altboot a go on my "spare" device. I generally keep a Sharp compatible ROM on there for testing SharpROM releases of opie-reader so I can spare it for a test.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=83383\"][{POST_SNAPBACK}][/a][/div]

Thanks for the offer!
It would be interesting to know if the script would work correctly in a Sharp ROM. If you could check that, it would be great   No hurry though. Booting an OZ image is bound to fail due to the kernel but basic functionality should be there.

[TimW]

I did a quick check using your ipk on my Sharp based ROM (actually Cacko with "root on sd" so very little chance of it working any way I would expect) but fell foul of the change in ipk format. I can retest using (IIRC) ipkg-new or by repacking the ipk, OTOH I can reflash this device at any time (my OZ device is my main one) so what would be your preference I test:

another OZ test on an SL5000D,
or on old Sharp ROM (there is no SL5000 version of the current ROM),
or one of the ROMs which is nominally Sharp compatible (Cacko, tkc, etc),
or one of the latter with home on SD (probably a silly idea but you may know better),
or something else?

[CoreDump]

I did a quick check using your ipk on my Sharp based ROM (actually Cacko with "root on sd" so very little chance of it working any way I would expect) but fell foul of the change in ipk format. I can retest using (IIRC) ipkg-new or by repacking the ipk, OTOH I can reflash this device at any time (my OZ device is my main one) so what would be your preference I test:

another OZ test on an SL5000D,
or on old Sharp ROM (there is no SL5000 version of the current ROM),
or one of the ROMs which is nominally Sharp compatible (Cacko, tkc, etc),
or one of the latter with home on SD (probably a silly idea but you may know better),
or something else?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=83563\"][{POST_SNAPBACK}][/a][/div]

Home on SD might still work (hentges ROMs w/ home on SD work just fine heh) but it depends on its implementation.

It would be great if you could test the script on a stock Sharp ROM, though