Pdaxrom 1.1.0beta 4 And New Bootloader

[Dima202]

It's so great that Beta 4 came out )))
This is really great since it is before I left!
Thanks a lot, I will wait a week untill most noticible bugs are worked out
-Also I am so busy that I won't have time, would love to beta test

Thanks a lot guys, 4 gig sd support is awesome too!

[kenya]

Some issues:
1. After I exit X back to the command prompt, sometimes the screen is locked, and all of my typing just scrolls in one line at the bottom.

2. Menu in X goes off of the bottom of the screen in landscape mode. no way to see the lower selections.

3. Time does not survive a reboot. In the old versions, the curren time was saved and then restored on reboot, so I lost seconds, hours or days if left ina drawer. Now it goes back to 1970.

4. Note during bootup: "can't synthesize pci hotplug events"

5. No "cardctl" program. How do I eject/insert a card "from the command line"?

6. Stylus sometimes "hangs" when tapping on something. It presses the button, but stays "down" rather than coming back up.

7. After exiting X, some keys like the "a" key do not work.

8. I use "modprobe g_ether" to get USB networking working (on 760), but when I run "startx" it shuts that down and I have to start it again

9. Keyboard in X: Menu key soes not work, FN 3 and FN 4 does not dim/brighten the screen.

10. Tapping on battery, clock, or CPU meter does not do anything. Older ROM's gave info, and sometimes link to a related program.

11. I think filesystems should mount "noatime" to spare flash writes.

Not complaining, just posting for inf, and looking for fixes. Thanks for the great work!
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

Hi clofland! It's a nice testing report!  

I report that there is not "hwclock" command in beta4.
Checked beta4 for Cxxxx, this command seems to be in "util-linux."
So I rebuild util-linux with hwclock using pdaXrom-builder.
hwclock works fine, but after rebooting, returned to 1970/01/01.

If you want to replace util-linux right now, you can download it from my web.
[a href=\"http://comomo.shacknet.nu/plone/files/pdaxrom/1-1-0beta4/util-linux_2.12_armv5tel.ipk/download]http://comomo.shacknet.nu/plone/files/pdax...el.ipk/download[/url]
Sorry, this web in Japanese.

sashz, thanks for your good job.
Could you update util-linux sys-config, including hwclock?

And, sashz, does Zaurus need both APM and ACPI support?
It's just a question because I don't know about them well.

[scoutme]

I put every file on my SD, hard-rebooted with OK pressed and emergency system has been installed.
Then I got the emergency system by pressing OK for 10 seconds after replacing battery and/or reinserting ac. Beta4 has been installed

Now I HAVE a working BETA4 on my sl-c860


I notice:
fonts in menu and panel are way too big, but I don't know how to reduce'em (look'n'feel doesn't work)
menu sections are not well placed (they are half out the screen)
sometimes programs seem to hang; but they continue regularly if you input something (e.g.: move the jog)

these beta seem less stable than old RC. Am I wrong?
no hwclock problem here, anyway.

EDIT!!!!!


my fault, I didn't test enough
1) hwclock problem present, as expectable
2) shadowing screen while in vertical mode (not in landscape)
3) apps hanging confirmed. Seems an interface problem... like if "release event" of touchscreen remains appended to a cue that you have to flush by pushing new input events. Bread for your teeth, Sash

[clofland]

It looks like some NAND addresses are overlapping with this version of u-boot, thus NO D+M!

Quick RESCUE if you want go back and restore a NAND image of the Zaurus (pre u-boot status):

1) put a copy of SYSTC860.DBK (for the 860) on the CF/SD
2) EDIT autoboot.sh in this ugly way and copy it on the CF/SD:

#!/bin/sh

PATH=/bin:/sbin:/usr/bin:/usr/sbin

echo $1

LOC=$1

for file in $LOC/systc860.dbk $LOC/SYSTC860.DBK; do
    if [ -e $file ]; then
   echo "Backup $file"
   nandlogical /dev/mtd1 WRITE 0x00000000 0x000DBFFF $file
   break
    fi
    file=""
done

reboot
##############

3) unplug power, pull battery out.
4) insert the CF/SD
5) press OK and plug in the power AC connector
6) let the kernel boot and execute autoboot.sh
7) ignore the errors...

Et voilà, D+M menus are back!!! You can do NAND FULL ERASE and NAND RESTORE in the easy way!

POST EDITED: this flash interval should suffice to reach the D+M menu again (Mainte + Parameter Area + NAND Diag)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130622\"][{POST_SNAPBACK}][/a][/div]

SUCCESS!  Thanks. That did the trick. Back to trusty Beta3.   Sashz has spoiled me with all of these "Betas" that work so well, that I just couldn't keep using Beta4.

NOTE: Now my screen flickers in X under Beta3 (after a full NAND restore), while it did NOT flicker before. That seems very odd. What could have changed that could have survived a NAND restore? I think there are fixes for this, so I will go search the forum, but I thought it was odd that I never had ths problem before now.

[diesel1]

I cannot get my c860 working, Only thing that seems to show is service menu(D+M).
Can any one give me a pointer to get it going?

Thanks, Diesel1.

[diesel1]

Ok, I finally got my c860 to work, just needed to get the nand restored.

PHEW!

Diesel1.

[patsch]

It looks like some NAND addresses are overlapping with this version of u-boot, thus NO D+M!

Quick RESCUE if you want go back and restore a NAND image of the Zaurus (pre u-boot status):
1) put a copy of SYSTC860.DBK (for the 860) on the CF/SD
....

I think, that I have tried everything, what was discussed in this topic, but my zaurus (corgi) doesn't wake up after an updating crash to beta4 : (

he is still flashing his led, after I try to make some first aid : (
why is he blinking???
only because of an cf error??
but he is also blinking without cf or sd - only battery or dc!?!
what can I do?? I can not start a kernel with "OK" and also no "D" and "M" possiblity!!
thanks,
patsch.

[diesel1]

It looks like some NAND addresses are overlapping with this version of u-boot, thus NO D+M!

Quick RESCUE if you want go back and restore a NAND image of the Zaurus (pre u-boot status):
1) put a copy of SYSTC860.DBK (for the 860) on the CF/SD
....

I think, that I have tried everything, what was discussed in this topic, but my zaurus (corgi) doesn't wake up after an updating crash to beta4 : (

he is still flashing his led, after I try to make some first aid : (
why is he blinking???
only because of an cf error??
but he is also blinking without cf or sd - only battery or dc!?!
what can I do?? I can not start a kernel with "OK" and also no "D" and "M" possiblity!!
thanks,
patsch.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130990\"][{POST_SNAPBACK}][/a][/div]

Try to format your card as so..

prepare card with FAT16 partition, and formated with FAT 16 (mkfs.msdos -F 16 /dev/xxx )

I had some issues with card filesystems.

Diesel1.

[rmrfchik]

It looks like some NAND addresses are overlapping with this version of u-boot, thus NO D+M!

Quick RESCUE if you want go back and restore a NAND image of the Zaurus (pre u-boot status):
1) put a copy of SYSTC860.DBK (for the 860) on the CF/SD
....

I think, that I have tried everything, what was discussed in this topic, but my zaurus (corgi) doesn't wake up after an updating crash to beta4 : (

he is still flashing his led, after I try to make some first aid : (
why is he blinking???
only because of an cf error??
but he is also blinking without cf or sd - only battery or dc!?!
what can I do?? I can not start a kernel with "OK" and also no "D" and "M" possiblity!!
thanks,
patsch.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130990\"][{POST_SNAPBACK}][/a][/div]

Don't panic. Do you have a towel?
Ok, after erasing NAND, your zaurus will always blink the LEDs until you load it with ROM.
To revive the pet, format card, put SYSTC860.DBK on it, insert card into zaurus, go to D+M menu, choose Test ComapctFlash (or similar, do not remeber the exact item). If it pass correctly, try to Restore NAND.
Report here.

[scoutme]

did you try keeping pressed for more than 10 seconds the OK button while inserting battery and AC?
Thi is the procedure to start emergency system

[patsch]

yes I tried this many times...
but when I'm inserting the battery, the green LED is already blinking... also with open battery lock. when I close the lock and put the AC, the yellow LED begins to blink : (

[diesel1]

yes I tried this many times...
but when I'm inserting the battery, the green LED is already blinking... also with open battery lock. when I close the lock and put the AC, the yellow LED begins to blink : (
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

This is exactly the behaviour my c860 was showing.

Did you format the sd/cf card with mkfs.msdos -F 16 /dev/xxx ?
Then press and hold D + M, while holding keys insert power lead, now you should have service menu.

The info at [a href=\"http://downloads.conics.net/pda/zaurus-sl-c700/service-menus/]Conics[/url] may  help.

Diesel1.

[patsch]

Did you format the sd/cf card with mkfs.msdos -F 16 /dev/xxx ?
Then press and hold D + M, while holding keys insert power lead, now you should have service menu.

I saw it a bit to late : ( But yes. It was exectly the problem : ) Thanks anyway  

The info at Conics may  help.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

That's a suuper great archive : ) It's a bit pity that there isn't a md5sum. But very great.
I opend yesterday a new [a href=\"https://www.oesf.org/forums/index.php?showtopic=19939&st=0&p=131126&#entry131126]post.[/url]
so TriSoft showd me a Voodoo Key Combination : ) With it you can start a rescue copy of the diagnostic mode: "FN"+"D"+"M"
Thanx for anything again  

[Bundabrg]

I rather think the fuzzyness some of you are experiencing are because the NAND Erase erases COM and PHASE settings. I can't remember off hand which were important (theres a sticky on the pdaxrom forum about it) but if its wrong you'll get some 'shadows' etc..

(Edit) Oh, I see that autoboot.sh restores the settings? Or am I wrong there?

 - Bundabrg

[ant]

pdaXrom beta4 get this settings from /etc/sysconfig/zaurushw

OK guys,
after a good sleep I see the things clearer:

the Nand Full Erase does indeed cause annoyances:

Some Values are lost (Params):

'Tablet', 'COM' and 'Phase' are '---'.
 'Battery Voltage Adj' is empty
...


I think we should look at the 176 kb parameters area (overwritten updating to  pdaxrom).

Now I'm investigating about the file mversion.bin 16k...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130638\"][{POST_SNAPBACK}][/a][/div]

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

Would a gentle 760/860 user post /etc/sysconfig/zaurushw ?

TIA