Messages

1

Zaurus - pdaXrom / Pdaxii13 On C3100

« on: January 08, 2007, 03:33:49 pm »

Iusing the c3000 kernel I got some error about not finding rootfs I think it was.

Yes it was the problem I remained stucked for a long time
Exactly the first problem was pdaxrom3 beta + pdaxii13 files complained about
"init" problem as it was described some time ago.

As I understand Meanie had worked to correct this for non-3000  machines by changes in initrd stuff and recently he had changed updater.sh to version 24 that did not ignore SL3200 -
I remember that this time it really started flashing the NAND with kernel 2.4.20-bin
but then it complained about the nonexistant NAND and no rootfs (as you mention)

Meanie explained this by the kernel hardcoded size of NAND as he put the 3000 kernel on pdaxii13 stable and tmp distro.

maybe I am wrong but I think everything was corrected by replacing the correct kernel (3100/3200 from pdaxrom3 beta distro in the root of SD.
So it probably would work from the scratch (Sharp, cacko)  using that replaced kernel AND updater 0.24 (which realy started flashing).

Alternative solution as taken by me is to use updater 0.23 (that ignores the real kernel flashing)
having already flashed the 3200/3100 kernel from previous pdaxrom  beta3 installator.
(I could not find updater 0.24 anymore and I have ereased it from SD already)


I do not think partitioning scheme plays any role - in fact it requires only the one partition large enough to host the uncompressed hdimage_full stuff.

I wouldn't have thought different partitioning would've made a difference (would it? Did you have your drive partitioned for Cacko/Sharp when you installed beta3?

 Have I got to partition my MD that way first?) as when I installed beta3 my MD was partitioned ready for pdaXii13 already but the b3 installer didn't seem to have any problem with that.

yes no problem I have flashed about 5 times pdaxii13 and pdaxrom3 beta having the partitions intact since first experiments with first hdimage_full (somewhere about 11 December)

To summarize I think that for the future installation recipe there should be prepared 3 sets of files
(for 3000/3100/3200 separately)
pdaxii13+hdimage-full.tgz 5.2 + kernel for appropriate model (from pdaxrom beta3) renamed to zImage-2.4.20.bin + updater v 0.24 !!

and people probably could start directly flashing pdaxii13 after sharp immediately

But its my feeling only - someone should test it

2

Zaurus - pdaXrom / Pdaxii13 On C3100

« on: January 08, 2007, 01:39:50 pm »

My install howerver was different.  I did a standard pdaXrom Beta3 install first.  Then used the old updater.sh from http://www.tyrannozaurus.com/feed/pdaXii13/files/updater.sh and did a standard install using the 5.2 full package, no file replacements.

I was able to install finally (after unsuccessful trials since Christmas) pdaxii13 on my 3200.
Exactly as shown above
1)reflashed pdaxrom3 beta (with kernel for 3200)
2)replaced the files for pdaxii13 on SD root
3) started flashing (OK+power) - japan menu 4, Y, Y to get installer of pdaxii13
4) partitioned microdrive to 3 partitions as recommended by Meanie
5) used option marked as flashing pdaxii13 - (but it takes only short time as it does not flash kernel -   using updater.sh 0.23  - BTW the version 0.24 is not available anymore neither on  alpha page (pdaXii13/tmp) nor on stable (pdaXii13/files)
6) installed hdimage_all.tgz using next installer option
7) rebooted

after LONG time it started X and system was there !

I have used release 5.2 alpha that was at  http://www.tyrannozaurus.com/feed/pdaXii13/tmp/

For me do work Fn keys (*..) , zoom (japan key left from - and 1,2)...
Most applications started well (but I did not have time to test every applications in detail)
SD card 2GB works from scratch (it did not work on pdax3 beta) - so the new SD driver is directly in pdaxii13

I did not test Planex wifi yet...


What I miss most is mc (Midnight commander)

3

Zaurus - pdaXrom / Pdaxrom For C3000 (based On Beta1/beta3)

« on: December 04, 2006, 11:19:22 pm »

Hi ajnstajn,

congrats on your new Z. however, your post is really confusing this thread as this thread is about pdaXrom for C3000 and you are mixing several distros.

Sorry if it sounds confusing but I intended to install the C3000 distro on 3200 (you said it should work in theory and some people asked about it on 3100 so I tried it. As I was stucked  in #prompt without reaction (after flashing pdaxiirom ) I had to reflash to pdaXrom beta3 while having the disks partitioned with hdimage-full contents.

4

Zaurus - pdaXrom / Pdaxrom For C3000 (based On Beta1/beta3)

« on: December 04, 2006, 10:12:11 pm »

still working on improving pdaXii13-full

...


the SL-C3200/SL-C3100 has not been tested but in theory should work once the bugs have been ironed out. you will need to provide the error messages you see when you boot to diagnose this.

Hi all !

I am the new owner of 3200 for about a week and after some bad experience with basic pdaXrom beta3 (over the original Sharp rom - suspend problems ... complete crash of system could not turn it on ... several times reflashing to original SHARp and to beta3 ..) I decided to test pdaxiirom with state about 1 December

Parititioining HDD as recommended by Meanie  (swap 256MB, hdd1 1.5GB the hdd3 being the rest )
uncompressing of hdimage-full was OK. But after the final reboot the system did not come up
It stopped at the prompt like # (root)
but the console did not accept commands - I could write anything and erase it but it did not activate any commands ..

After some trials to understand what have happened I gave up and reflashed again beta3
but with new partitions from pdaxiirom. System came up well and it started to run some ipkg-link task (and running microdrive) at the start.

All applications as gnumeric, abiword gqview ,,,, all worked . The suspend is reliable etc ...

So it is very good. But today i tried to instal pdaxqtrom cramfs files and after runing install the startx does not work and a lot of applicatiions during the start complain about some shared libraries problems..)
I had to remove /opt/QTPalmtop/lib/X11/xinit/xserverrc and replaced xinitrc  by xinitrc.obenbox to get it running again.

probably the pdaxiirom structure is not compatible with the pdaxqtrom ...

To be honest I am still very confused about all the stuff in OESF forums, pdaxrom customization pages xqt etc ...  Although I am experienced Linux user, I have to learn a lot about the Z - moreover I did not follow 2.4 kernels for a long time - now running Debian Sarge on 2.6.16 on most my machines in work .

The same confusion concerns the magic procedured with removing batery, unpluging and mainly pressing reset button when all power sources are disconnected  -why ?
Most procedures to getting flash menu (described elsewhere) do not work on my 3200.
The only reliabkle is to remove batery and power, swithing the batery swith on (without batery) and presing D+B or D+M while pluging power supply. It does not work with batery in...
I am not able to go to Hlash menu (power+OK) immediately but only by booting (D+ and holding OK while rebooting from the command in Pdaxrom  - it worked only in SHARP rom even with battery without power plug.
So is it anything  changed in the boot loader between SHARP and pdaXrom ?

I feel there is a lot of magic behind the stuff mentioned in different places here and on various zaurus pages -
It serves exact research what happens during the booting process, what is called from flash menu exactly, when different keypresses are read (even with dark screen) etc ...
The battery switch is strange too - is seems to be just some kind of "jumper" read during certain phase of booting - e.g I have to switch it on (like to close battery cover - but I do not put battery and cover..) and after the systems prompts for root account I can switch off , put battery in and close again and nothing happens, at the other cases - like having X runing- the switching off causes the system to some suspend state ...)

 


I need some time to check everything once more and starting from the SHARP rom again before I can reliably report bugs here, though.


Anyway  good piece of work Meanie and others !