Author Topic: Pdaxrom 1.1.0beta 4 And New Bootloader (Read 104058 times)

sashz · « **Reply #45 on:** June 09, 2006, 11:40:43 am »

Quote

Having the ROM installed, first issue was that my CF LAN card was not working. No IP.
Made a profile called LAN
then hit OK, closing that, and then from a terminal run these commands:

/bin/ln -s /etc/sysconfig/netconfig/LAN.conf /etc/sysconfig/netconfig/eth0.conf
ifup eth0 &

create profile with name eth0
We will rewrite this utils soon

Also GUI mixer not fixed yet, use console alsamixer :

Code: [Select]

TERM=xterm-color
alsamixer

clofland · « **Reply #46 on:** June 09, 2006, 12:39:35 pm »

USB Networking working!!! Cool.

Here is what I did, let me know if it doesn't work for you:

get linux.inf.txt from here https://www.oesf.org/forums/index.php?showt...169&#entry73169

Put it in a directory on your windoze box and rename it to just linux.inf

from a terminal run:
modprobe g_ether

Plug the Z's USB into your Windoze box.

When windows asks for a driver, tell it to look in the directory where you put linux.inf

Let it do its thing and finish. (Windows may ask to reboot, but I did NOT let it, and it works now.)

Go into the properties and give it an IP. (Use ifconfg on your Z to see what the IP on the Z is and put it in the same subnet, I use 192.168.129.200 on my windoze box)

Works great!

ant · « **Reply #47 on:** June 09, 2006, 01:12:33 pm »

>unplug power adaptor, eject battery. Press and hold OK button and insert battery or power adaptor.
>Hold button 10 sec, emergensy system will booting.

OK, i inserted the card with the kernels and rescued the Z.

Now I can confirm u-boot on SL-C860, though the D+C flashing way not yet working (MODEL ID mismatch somewhere?).

THX Sashz

Ant

scoutme · « **Reply #48 on:** June 09, 2006, 01:47:59 pm »

incredible... every release only when I'm away from both my pc and zaurus

gonna flash when back home

thanks Sash

<O.T.> while the release was broken I could try OZ/GPE... nice ROM. Not my ROM (PDAXROM is my rom), but a lot of usefull ideas. we should take some.
I mean, it's sorta KDE-GNOME comparison. KDE and OZ/GPE are much more integrated and functional as-is, but less customizable. GNOME and pdaXrom look less specific, but easy to customize and extend with thousand apps.
As I prefer GNOME on my box, I prefer pdaXrom on my Z, but that GPE/OZ rom is full of apps I's like to have...sketchpad, vocalnotes, to-do, easyinput... ok stop here
</O.T.>

rmrfchik · « **Reply #49 on:** June 09, 2006, 01:55:27 pm »

Quote

>unplug power adaptor, eject battery. Press and hold OK button and insert battery or power adaptor.
>Hold button 10 sec, emergensy system will booting.

OK, i inserted the card with the kernels and rescued the Z.

Now I can confirm u-boot on SL-C860, though the D+C flashing way not yet working (MODEL ID mismatch somewhere?).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130563\"][{POST_SNAPBACK}][/a][/div]

Do not use D+C method. Use usual way to reflash -- Power+OK, 4, SD|CF, Y.

rmrfchik · « **Reply #50 on:** June 09, 2006, 02:30:05 pm »

Funny keymap in this beta4. After startx/exit, the following keys doesn't work "a", UP.
Jog "right" works as "tab".

Also, after power off I can't power on . Black screen. Hmm.

clofland · « **Reply #51 on:** June 09, 2006, 04:31:51 pm »

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!

clofland · « **Reply #52 on:** June 09, 2006, 05:05:33 pm »

Additional:

12. Socket Bluetooh card does not work. Didn't have time to research, but it worked "out of the box" on Beta3.

13. No sound. The volume control applet will not move up when I try to slide it.

That is about all. Time to NAND restore back to Beta 3 now so I can use my Z.

Great work. I look forward to testing the next Beta! I'm still amazed at how functional Beta3 is!

clofland · « **Reply #53 on:** June 09, 2006, 05:36:05 pm »

Ugh, now I can't get into the NAND menu.

Suspend
Flip battery switch toward back
Hold down D+M
Flip battery witch toward front
Nothing.

Any ideas? It is like the "suspend" mode that the new kernel uses does not allow the Z to do its thing. Or maybe I am just doing it wrong? That is how I made my NAND backup of Beta3.

Thanks for any ideas.

rmrfchik · « **Reply #54 on:** June 09, 2006, 06:31:13 pm »

Quote

Ugh, now I can't get into the NAND menu.

Suspend
Flip battery switch toward back
Hold down D+M
Flip battery witch toward front
Nothing.
Thanks for any ideas.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130610\"][{POST_SNAPBACK}][/a][/div]

Try to use cord, not battery. This works for me.

ant · « **Reply #55 on:** June 09, 2006, 06:39:16 pm »

Quote

Quote
Ugh, now I can't get into the NAND menu.

Suspend
Flip battery switch toward back
Hold down D+M
Flip battery witch toward front
Nothing.
Thanks for any ideas.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130610\"][{POST_SNAPBACK}][/a][/div]
Try to use cord, not battery. This works for me.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130614\"][{POST_SNAPBACK}][/a][/div]

Sorry but it seems the DM menu is "lost".

Impossible, we know it is on the ROM, but....instead of DM menu you see "Boot PROM Filesystem"

Basically we cannot flash/erase anything with any key combination...

Hope Sashz will solve the D+C flash problem (wrong model)

ant · « **Reply #56 on:** June 09, 2006, 08:35:00 pm »

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)

**************************************************
EDITED AGAIN 2006, June 15th: the D+M menu are not lost!
**************************************************
Thanks to M. Stephan (Trisoft) for revealing a new key combination (do they disassemble PROMS overnight? Sleepless Germans... ;-)

https://www.oesf.org/forums/index.php?showt...ndpost&p=131089

ant · « **Reply #57 on:** June 10, 2006, 05:41:41 am »

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

P.S. thanks Guylhelm for the pics http://www.externe.net/zaurus/flash/

sashz · « **Reply #58 on:** June 10, 2006, 05:44:43 am »

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

Quote

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]

ant · « **Reply #59 on:** June 10, 2006, 05:56:04 am »

Quote

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

QUESTIONS TO SASHZ REMOVED (OT)

News:

Author Topic: Pdaxrom 1.1.0beta 4 And New Bootloader (Read 104058 times)