OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: sashz on June 06, 2006, 02:49:14 am
-
http://mail.pdaxrom.org/node/102 (http://mail.pdaxrom.org/node/102)
-
quick work!
-
http://mail.pdaxrom.org/node/102 (http://mail.pdaxrom.org/node/102)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130000\"][{POST_SNAPBACK}][/a][/div]
Will the packages i compiled with the Beta4 Builder compatible with this Beta4 realease fot the CXXX?
-
oh s**t
I waited with my 860 hold in hand fo months, and today I read these awesome news... without my Z!!!!!!
You'll bring me to suicide
gonna flash and test in a few hours
thanks
-
http://mail.pdaxrom.org/node/102 (http://mail.pdaxrom.org/node/102)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130000\"][{POST_SNAPBACK}][/a][/div]
Will the packages i compiled with the Beta4 Builder compatible with this Beta4 realease fot the CXXX?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130007\"][{POST_SNAPBACK}][/a][/div]
yes!
-
http://mail.pdaxrom.org/node/102 (http://mail.pdaxrom.org/node/102)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130000\"][{POST_SNAPBACK}][/a][/div]
Will the packages i compiled with the Beta4 Builder compatible with this Beta4 realease fot the CXXX?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130007\"][{POST_SNAPBACK}][/a][/div]
yes!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130024\"][{POST_SNAPBACK}][/a][/div]
Ok, so i will go on with the GPE-Stuff.
BYEZ!
-
Great news,
but yet not for us c3000 owners I guess
Is there any way that i can contribute with my sl-c3000? I do linux sysadmin for a long time, I can edit scripts, do minor coding etc.
Any hope?
-
Great news,
but yet not for us c3000 owners I guess
Is there any way that i can contribute with my sl-c3000? I do linux sysadmin for a long time, I can edit scripts, do minor coding etc.
Any hope?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130029\"][{POST_SNAPBACK}][/a][/div]
i will test new bootloader it in one-two days
-
uh.. tried with 2 SD and a CF (standard FAT) but at C+D phase the leds are blinking...
I'm stuck there. I'll try to reformat the card and let you know.
EDIT
Running on a 860
-
uh.. tried with 2 SD and a CF (standard FAT) but at C+D phase the leds are blinking...
I'm stuck there. I'll try to reformat the card and let you know.
EDIT
Running on a 860
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130052\"][{POST_SNAPBACK}][/a][/div]
Yep, I had the same problem on my SL-C860. All md5sum values matched, and restoring my flash backup from the same CF card worked.
Dan
-
plz stop testing, i need check problem
-
I have a C760.
I have instaled the new bootloader sucesfully (no blinking leds), but I cannot bootup the emergency system. When I press ok and connect the power cable, the orange led blinks once and then nothing.
I have tried to wait more and less time before leave the ok button but the screen remains black.
I have tried with both a CF and a SD card with the same result (bootloader ok but no more).
-
so sashz, can I proceed woth installation on my 860, or should I wait?
-
uh.. tried with 2 SD and a CF (standard FAT) but at C+D phase the leds are blinking...
I'm stuck there. I'll try to reformat the card and let you know.
EDIT
Running on a 860
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130052\"][{POST_SNAPBACK}][/a][/div]
Same here, but I used vfat just like normal, formated in my camera.
Diesel1.
-
if it is any help, I had both lights on.... tried the routine a few times and it worked anyway. Might be because I was on a (low watt?) usb charge cable
-
I have a C760.
I have instaled the new bootloader sucesfully (no blinking leds), but I cannot bootup the emergency system. When I press ok and connect the power cable, the orange led blinks once and then nothing.
I have tried to wait more and less time before leave the ok button but the screen remains black.
I have tried with both a CF and a SD card with the same result (bootloader ok but no more).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130086\"][{POST_SNAPBACK}][/a][/div]
I have the same problem with my 7500.I know our great developer can solve it finnally .Looking forward to new release.
Thank you very much !
-
if it is any help, I had both lights on.... tried the routine a few times and it worked anyway. Might be because I was on a (low watt?) usb charge cable[div align=\"right\"][a href=\"index.php?act=findpost&pid=130145\"][{POST_SNAPBACK}][/a][/div]
I tried it first with my usb cable, then later with the power supply. Neither worked.
-
I have a C760.
I have instaled the new bootloader sucesfully (no blinking leds), but I cannot bootup the emergency system. When I press ok and connect the power cable, the orange led blinks once and then nothing.
I have tried to wait more and less time before leave the ok button but the screen remains black.
I have tried with both a CF and a SD card with the same result (bootloader ok but no more).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130086\"][{POST_SNAPBACK}][/a][/div]
I have the same problem with my 7500.I know our great developer can solve it finnally .Looking forward to new release.
Thnak you very much !
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130168\"][{POST_SNAPBACK}][/a][/div]
I'm also a 7500 owner, when shall I start to use it? Anyway, thanks sashz for the great work!
-
Plz try next way:
download u-boot zip archive again (i updated it),
prepare card with FAT16 partition, and formated with FAT 16 (mkfs.msdos -F 16 /dev/xxx )
Insert card in zaurus (only one must be inserted, if SD - no CF, if CF - no SD).
Run diagnostic menu (D+M),
Earse flash :
SERVICE 3/3 7. EXTRA MENU
[img]http://mail.pdaxrom.org/download/1.1.0beta4/Zaurus-7x0-860/07-06-06_1451.jpg\" border=\"0\" class=\"linked-image\" /]
EXTRA MENU 1.Zaurus Test
[img]http://mail.pdaxrom.org/download/1.1.0beta4/Zaurus-7x0-860/07-06-06_1452.jpg\" border=\"0\" class=\"linked-image\" /]
Extra MENU 2/4 10.NAND Flash Full Erase (press OK for erase)
[img]http://mail.pdaxrom.org/download/1.1.0beta4/Zaurus-7x0-860/07-06-06_1453.jpg\" border=\"0\" class=\"linked-image\" /]
As it finish, press Cancel until mail menu (SERVICE 1/3)
Select CF Update
[img]http://mail.pdaxrom.org/download/1.1.0beta4/Zaurus-7x0-860/07-06-06_1447.jpg\" border=\"0\" class=\"linked-image\" /]
you must see:
[img]http://mail.pdaxrom.org/download/1.1.0beta4/Zaurus-7x0-860/07-06-06_1439.jpg\" border=\"0\" class=\"linked-image\" /]
press OK for update flash:
[img]http://mail.pdaxrom.org/download/1.1.0beta4/Zaurus-7x0-860/07-06-06_1445.jpg\" border=\"0\" class=\"linked-image\" /]
as it finish, reboot it with OK pressed and install new system
-
I'll try this way: I was too scared to try "CF UPDATE".
Interestingly I found out that the test menu "CF CARD READ" reports almost everytime errors on a fresh formatted FAT card.
I did "CF CARD WRITE" and then the error disappears...it seems ONLY ONE BLOCK is defective and overwritten...
I tried with a couple of card and the block has different address.
I know for sure the cards are working (formatted on wifey's second Zaurus 860 Cacko)!
I understand doing full nand erase I wiped out the partition table, but this should not be related to the booting code...
P.S.
I didn't test the same options for SD/MMC but expect same results.
Ant
-
OK upto the CF Update step, this returns the following on my 860 :
CF Update
---Found orders---
Model Error!!
The last bit is shown in red. Do I have the wrong version of uboot?
-
...I have a SD card: what's MY procedure?
-
OK upto the CF Update step, this returns the following on my 860 :
CF Update
 ---Found orders---
Model Error!!
The last bit is shown in red. Do I have the wrong version of uboot?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130208\"][{POST_SNAPBACK}][/a][/div]
exactly the same here on SL-C860.
Is the problem limited to this model (Boxer)?
EDIT
I used: u-boot.bin 07-Jun-2006 13:42 128K
-
the same here... I thought the problem was I was using a SD instead of a CF
a bit of bricking never hurts
-
try with inserted battery.
I get report CF Update work with it (for me without battery too)
-
"model error" error still remains
-
OK upto the CF Update step, this returns the following on my 860 :
CF Update
---Found orders---
Model Error!!
The last bit is shown in red. Do I have the wrong version of uboot?[div align=\"right\"][a href=\"index.php?act=findpost&pid=130208\"][{POST_SNAPBACK}][/a][/div]
I followed the new instructions to the T. Same error for me.
-
For information my version of uboot.bin has a md5sum of :
737112abceda9878c90f87681779a10b
-
Hey guys! There's hope!
I was able to boot a new version of u-boot on a (so I tought) totally bricked C700! It gave me random errors on (Full) NAND erases, gave the symptoms ztep described. And now it was able to boot into emergency system two or three times. Try to download u-boot.bin again and try to Full NAND erase, CF Update, booting with OK multiple times. My one doesn't work well most of the time too... Maybe your flash is corrupted more/other places.
Anyway, I try to help with bugreports to Sashz! Good luck to you all!
Zumi
-
Does anyone know where do we download the updated uboot version? sashz, can you let us know the the md5 from your working version?
-
For me it works as far as the Emergency startup.
pdaXrom emergency system
==================
pdaXrom [Shepherd]
Loading /etc/sysconfig/keyboard/Shepherd/keymap.map
Processing /etc/profile... Done
-sh-3.00#
I've tried to manually start autoboot.sh in /mnt/cf but that results in a system freeze.
What's next, any ideas?
Update:
I've started the Emergency system WITHOUT the CF card inserted. This ends with the shell prompt. NOW I inserted the CF card. At this point the CF is recognized correctly, so I'm able to continue be entering the following command:
cd /mnt/cf
./autoboot.sh /mnt/cf
This continues the installation process, and reboots the system.
Works like a charm so far!
-
Cortez,
as far as I know after you have installed the new uboot loader and the emergency system a normal flash install should allow installation of the updated rom.
I assume the autoboot.sh is similar to the updater.sh for the previous boot loader (a binary file rather than an actual shell script).
So to update switch off (remove battery + charge cable) the reinsert battery and press 'on' while holding down the 'OK' button. This should start the installation.
Marc
-
Marc, thanks for your reply. See my update above
-
My mistake, just had a look and it is a normal shell script.
-
This situation reminds me of my old tries (no luck) to restore using these images:
http://pocketworkstation.org/files/recover/ (http://pocketworkstation.org/files/recover/)
Interestingly the image name for 860 is:
http://pocketworkstation.org/files/recover...not-working.zip (http://pocketworkstation.org/files/recover/c860-recover-probably-not-working.zip)
...some bits from http://pocketworkstation.org/files/recover...ash-recover.txt (http://pocketworkstation.org/files/recover/README-flash-recover.txt)
* Do a full reset. For the C700: Switch the battery lock switch (on the bottom)
to "unlock", and wait 5 seconds. On the C750 and C760, you also need to
remove the battery and the power supply.
* Insert the CF card into the handheld.
* Hold down the <C> and <D> keys simultaneously, and while holding them down
switch the battery lock switch back to "lock". On the C750 and C760,
re-insert the battery and reconnect the power supply. Release the keys.
* Both LEDs should switch on and stay continuously lit - this means the
flashing process is working. DO NOT disturb the handheld at this stage.
* After a minute or two, both lights will go off again. Power cycle the
handheld by switching the battery lock switch to "unlock" and back to "lock".
If the LEDs start flashing, an error has occured, and it has given up
the flash process in an unfinished state.
* Hold down the <OK> button (either one) and while holding it down press the
"On" button at the back of the handheld. You should get the japanese system
menu, and should be able to use it to restore the rest of the flash ROM.
...
-
I work for easy u-boot installation way now...
-
Hello
I suggest you add a nand backup - people will install that more easily.
Guylhem
-
I'm going OT but here an old post about bootloader and D+M and other exhotics combinations...
http://lists.arm.linux.org.uk/pipermail/li...rch/005118.html (http://lists.arm.linux.org.uk/pipermail/linux-arm/2003-March/005118.html)
-
Same Model Error!! as other 860 users... I also just get the blinky LEDs trying the C+D update method. Oh, how I wish I could try the yummyness of Beta4!
-
hello my friends, plz try next way for installation bootloader and system
Download new u-boot and install script:
http://mail.pdaxrom.org/download/1.1.0beta...rgi-current.zip (http://mail.pdaxrom.org/download/1.1.0beta4/Zaurus-7x0-860/pdaXrom-1.1.0beta4-Kathrin-u-boot-corgi-current.zip)
Extract all files (emergenc.img u-boot.bin updater.pro updater.sh) to CF or SD card which you used for install previous systems.
Download new system:
http://mail.pdaxrom.org/download/1.1.0beta...rgi-current.zip (http://mail.pdaxrom.org/download/1.1.0beta4/Zaurus-7x0-860/pdaXrom-1.1.0beta4-Kathrin-corgi-current.zip)
Extract files (autoboot.sh kernel.img rootfs.img) also on this card.
U-Boot installation with sharp installer
Insert card in device and run original Sharp updater system. It will install u-boot and emergency system. Later you will need not install u-boot again
As it finish, press and hold OK button during reboot for 10-15 sec. Emergency system will running and install new system.
-
I see Sashz uploaded new files some minutes ago...let's try later!
UPDATE:
Sashz,
I bricked the Zaurus with the latest u-boot version.
The image doesn't yet flash using D+C, but only using the updater.sh.
So I restored the 1.40JP full NAND image and rebooted OK+Pow button.
The flash was smooth, the last lines were "U-boot installed"...rebooting...
...and now the 860 is dotated of a beautiful deep BLACK screen...
******************************************************
The only responsive boot options appers to be D+C and D+Z.
No way to reenter D+M.
Pleas post a new image (or tell me how to full-nand erase the thing...)
Ant
-
It works!
Here is my brief log:
Reboot
Do a NAND backup!
Download
http://mail.pdaxrom.org/download/1.1.0beta...rgi-current.zip (http://mail.pdaxrom.org/download/1.1.0beta4/Zaurus-7x0-860/pdaXrom-1.1.0beta4-Kathrin-u-boot-corgi-current.zip)
&
http://mail.pdaxrom.org/download/1.1.0beta...rgi-current.zip (http://mail.pdaxrom.org/download/1.1.0beta4/Zaurus-7x0-860/pdaXrom-1.1.0beta4-Kathrin-corgi-current.zip)
per:
https://www.oesf.org/forums/index.php?showtopic=19809 (https://www.oesf.org/forums/index.php?showtopic=19809)
Extract them and put these files on the SD card:
emergenc.img
u-boot.bin
updater.pro
updater.sh
autoboot.sh
kernel.img
rootfs.img
Pull plug & battery for 10 seconds to reset.
Put in SD card.
Put in battery and plug in.
Hold down OK while turning on.
Option 4.
Then SD (or CF if that is what you have I guess).
Then Y.
It shoudl start "Writing " lots of numbers!
Whatch it, when it says it is done and going to reboot, then HOLD OK down until the "pdaXrom emergency system" comes up.
You should see it "Erasing ..." with percent
then "Writing data to block ..." with lots of numbers. (Green LED flashes as it writes too, but the scrolling numbers are just as useful to know something is happening.)
Then at some point it finishes and starts booting.
The green LED is now your "Flash access" light, kind of light a hard drive light on a desktop. So you can tell it is working when the green LED is either dimly lit or flashing. This is useful since things seem to take their time to boot up, and leave you at odd places with no output.
I am now at # prompt!! Cool.
EDIT: no flicker problem once it is fully booted.
Now to see if I can make everything work just like before. Hmm, if I want it to work like before, why did I upgrade?
-
>>Whatch it, when it says it is done and going to reboot
AARGH...in my case it didn't reboot ...I pulled the battery out after a while...
MY FAULT I ONLY HAD
emergenc.img
u-boot.bin
updater.pro
updater.sh
on the card. I downloaded the files BEFORE the Sash'z post came on the Newsgroup... (BTW the timing of the posts has something strange)
So, DON'T FORGET TO PUT
autoboot.sh
kernel.img
rootfs.img
on the same card, because they are required!
Now, let just see why the D+M menu refuses to appear on my BRICKED 860... isn't in the ROM?
Sashz, if u-boot is installed how can I boot the emergency kernel from the card?
-
EDIT: To make your Network card work see: https://www.oesf.org/forums/index.php?showt...ndpost&p=126615 (https://www.oesf.org/forums/index.php?showtopic=19301&view=findpost&p=126615)
Probably lots of other fixes we will need in that thread.
-
>>Whatch it, when it says it is done and going to reboot
AARGH...in my case it didn't reboot ...I pulled the battery out after a while...
MY FAULT I ONLY HAD
emergenc.img
u-boot.bin
updater.pro
updater.sh
on the card. I downloaded the files BEFORE the Sash'z post came on the Newsgroup... (BTW the timing of the posts has something strange)
So, DON'T FORGET TO PUT
autoboot.sh
kernel.img
rootfs.img
on the same card, because they are required!
Now, let just see why the D+M menu refuses to appear on my BRICKED 860... isn't in the ROM?
Sashz, if u-boot is installed how can I boot the emergency kernel from the card?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130544\"][{POST_SNAPBACK}][/a][/div]
unplug power adaptor, eject battery. Press and hold OK button and insert battery or power adaptor.
Hold button 10 sec, emergensy system will booting.
-
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 :
TERM=xterm-color
alsamixer
-
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 (https://www.oesf.org/forums/index.php?showtopic=11320&st=30&p=73169&#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!
-
>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
-
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.>
-
>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.
-
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.
-
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!
-
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!
-
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.
-
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.
-
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)
-
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 (https://www.oesf.org/forums/index.php?showtopic=19939&view=findpost&p=131089)
-
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/ (http://www.externe.net/zaurus/flash/)
-
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]
-
pdaXrom beta4 get this settings from /etc/sysconfig/zaurushw
QUESTIONS TO SASHZ REMOVED (OT)
-
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!
-
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] (http://index.php?act=findpost&pid=130603\")
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.
-
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
-
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.
-
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.
-
Ok, I finally got my c860 to work, just needed to get the nand restored.
PHEW!
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.
-
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.
-
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.
-
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
-
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 : (
-
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] (http://index.php?act=findpost&pid=131037\")
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.
-
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 (http://downloads.conics.net/pda/zaurus-sl-c700/service-menus/) may help.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=131039\")
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
-
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
-
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
-
prepare card with FAT16 partition, and formated with FAT 16 (mkfs.msdos -F 16 /dev/xxx )
I was formatting the CF card on the other Zaurus, running Cacko.
I did even run fdisk and set the partition ID to 4 (this old card is only 16MB).
The card SEEMS formatted FAT16 but fsck.msdos reveals FAT32.
Very odd...
-
I think that fsck.msdos and fsck.vfat are making a mistake!
Because when I format my 256MB SanDisk Ultra II with mkfs.vfat -F 32 my Zaurus can't find the sdk. But with a 16 bit allocation table, it works...
With fsck.vfat I have the same output on my laptop as you; with an USB-card reader.
-
http://mail.pdaxrom.org/node/102 (http://mail.pdaxrom.org/node/102)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130000\"][{POST_SNAPBACK}][/a][/div]
please!
could anybody do a link from the download section to this page???
because i never looked to this great forum before... i always went to the pdaxrom.org homepage and clicked download... and never checked more!
thanx.
pat.
-
i flashed the rom as here written in this post.
then i had the same problem as cortez. u-boot is booting the emergency system, but the autoboot.sh script didnt't find the cf card, so there was no flashing:
pdaXrom emergency system
==================
pdaXrom [Shepherd]
Loading /etc/sysconfig/keyboard/Shepherd/keymap.map
Processing /etc/profile... Done
-sh-3.00#
I've started the Emergency system WITHOUT the CF card inserted. This ends with the shell prompt. NOW I inserted the CF card. At this point the CF is recognized correctly, so I'm able to continue be entering the following command:
cd /mnt/cf
./autoboot.sh /mnt/cf
This continues the installation process, and reboots the system.
Works like a charm so far!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130228\"][{POST_SNAPBACK}][/a][/div]
i have corgi (c700) and made it the same as cortez... aaaand now it works : )
suuper great : ) thanx cortez.
-
Im having a problem with my linksys wcf12 wifi card. For some reason the orinoco and hostap drivers are being loaded for it and its not letting me set the SSID. I have tried changing the settings in /etc/pcmcia but it still loads both. Also is it possible to flash beta1 with the new bootloader.
-
I've installed u-boot and pdaxrom beta4, noticed a few things (appart from what other people have reported) and I have a few questions:
The suspend works correctly on the emergency image but not in the beta4 normal boot where instead I get a black screen with a blinkung cursor (full reset to recover from that and the system reboots automatically after that).
I've done further tracking on this issue. I started with the emerg image, mounted the jffs2 root image on /mnt/cf (mount -t jffs2 /dev/mtdblock2 /mnt/cf) and did a chroot on the freshly mounted filesystem, ran /etc/rc.d/rc.sysinit, started X (got an ugly twm and killed it CTRL ALT BACKSPACE straight away) now the suspend is not working too. So it appears that the problem is not kernel but something done in the init scripts or in X initialization.
The console in bothe emerg and non has I guess a buffer issue because when you edit any commands in history, if and only if the line has spaces, when you add new chars the other chars to the left of what you add get all messed up on video (but command is ok and if you recall it from history it appears ok untill you edit).
When you forget the sd in with the beta4 install stuff it's useless to allways go ahead with the autoboot.sh script so I added a few lines near the top:
#Ask befor installing
echo "Proceed with pdaxrom installation or boot to emergency system ?"
read ans
[ "$ans" != "y" ] && exit
This can prevent from uslessy reinstalling the images when you want to boot to emerg and you forgot the removable media containing the install stuff in.
The emergency image has a wierd 3 consecutive backlight off, backlight on every minute or so when the battery level falls below 33%. As the battery further discharges the anomaly becomes more persistent. Once you fall below 28% even more odd stuff occours (like nacklight dimming for a while and then going bright again all on it's own).
Now that I have a more flexible boot loader how can I use it to boot something from CF or SD (not just the emergency image) I mean potentially a test kernel and a test initrd on CF or SD ?
Is it possible to make u-boot load the 2.4.18 kernel on pdaxrom 1.1 beta1 ?
Do I need to prepare the kernel image for u-boot as described in the u-boot README ?
if so how can I overwrite just the root fs and homes (mtdblock2 and 3) so as to get the old non broken version on cxx0 hardware ?
Can I change parameters passed to kernel by u-boot so as to repartition the nand flash ?
I have downloaded the latest avalible sdk and u-boot (with also the patches), I've built the u-boot and ended up with a u-boot.bin 130592 while original is 130568. Is this because the src avalible differs from the last user by Sashz or is it a cross compile environment issue ?
I've been unable to mount via loop device ither the emergenc.img or the rootfs.img.
I've tried bothe on the Z and on a PC. The emerg image is in the u-boot format (or at least has a kernel at the start in that format) so it would be intresting to know how big it is to try extracting just the initrd. Whlat is really puzzeling me is the rootfs.img that is a standard jffs2 little endian ... I should be able to mount that even on my PC but this is what kernel says:
loop: loaded (max 8 devices)
JFFS2 version 2.2. (NAND) © 2001-2003 Red Hat, Inc.
Attempt to mount non-MTD device "/dev/loop0" as JFFS2
How can I mount that ?
Regards
David
-
Some issues:
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.
7. After exiting X, some keys like the "a" key do not work.
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.
Not complaining, just posting for inf, and looking for fixes. Thanks for the great work!
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=130603\")
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]
yes i 've got the same problems:-
3. AFTER settings -> Date and time python GUI, and save back, when rebooting from console command line, the date time stuff can be saved back again (maybe this is a clue on solving this?) ....
7. yes, but 'a' key reappears after you press 'Fn' key... and return to X by sequence 'st[Fn]artx'....
9. right mouse button effect can be proceed under x11vnc remote desktop condition, i.e. although [Fn] doesn't work in direct keyboard, right mouse effect can be procceed.....
10. battery, date .... yes.... it says "please define some commands" in a dialog box with an OK button.... even in RoxFiler as the windows manager.
i understand this is quite hard, but i really hope the [Fn] key can work back since this is quite crucial.....
-
Just flashed my C860 with Beta4 to see how it is like, etc. Been using RC12 previously to that and really pleased with pdaXrom.
Just like to thank clofland and cortez for their posting of how they got this beta4 working. Got me out of a pickle!
Was worried I'd bricked my C860 utterly, till I read and followed the advice they'd posted. So thanks
Now to see how beta4 shapes up
Kelly
-
just met a good Z player (badog) and he told me about the [Fn] disability resolution method in beta 4:-
originally in /etc/sysconfig/x11mousebutt, its content is something like that: -
hold_right_button 0
right_button 96
middle_button 97
power_button 117
then you can make its content to be :-
hold_right_button 0
right_button 69
middle_button 50
power_button 117
and then Ctrl-Alt-Bkspace quit X, startx again and you can use the [Fn] key as right mouse triggger again ...
i tried my kit and it seems running fine. enjoy yours....
-
Seems my Socket LP CF wifi card doesn't work with 1.1.0beta4?
Get:
pccard: PCMCIA card inserted into slot 0
pcmcia: registering new device pcmcia0.0
orinoco 0.15rc3
spectrum_cs 0.15rc3
spectrum_cs: cannot find firmware: symbol_sp24t_prim_fw
spectrum_cs: firmware download failed
eth0: failed to initialize firmware (err = -16)
spectrum_cs: register_netdev() failed
Any ideas? anyone else had this problem?
This card worked fine with RC12 and beta1.
Kelly
-
Gave beta3 a try and got exactly same error as with Beta4 on my C860.
I need wifi working, so have gone back to RC12 again (as I did a NAND Backup and have that all set up and working) for now.
Kelly
-
for beta4
unzip these 2 files to you CF or SD
# mkdir -p /usr/lib/hotplug/firmware
# cp *files* /usr/lib/hotplug/firmware
Insert card
for beta3
# cd /
# tar xvzf /*path/to*/orinoco_modules.tar.gz
Insert card... not it is a little bit more tricky getting the Lan/Wifi app to work under beta4
Let me know if you having any problems with it
Late
-
for beta4
unzip these 2 files to you CF or SD
# mkdir -p /usr/lib/hotplug/firmware
# cp *files* /usr/lib/hotplug/firmware
Insert card
for beta3
# cd /
# tar xvzf /*path/to*/orinoco_modules.tar.gz
Thanks for that Late,
I'll give it a try later, have restrored the RC12 NAND Backup for now.
Kelly
-
Just noticed that things got updated in http://mail.pdaxrom.org/download/1.1.0beta...us-7x0-860/new/ (http://mail.pdaxrom.org/download/1.1.0beta4/Zaurus-7x0-860/new/)
Is there anything specially updated or fixed not just for the previous 7x0-860 version but also for the Cxx00 one?
And for this in the blog:
U-Boot buttons during power-up:
[OK] - emergency system
[1] - pass to kernel: root=/dev/mmcblk0p1 (root filesystem on SD/MMC card)
[2] - pass to kernel: root=/dev/hda1 (root filesystem on CF, need special kernel)
[3] - pass to kernel: root=/dev/hdc1 (root filesystem on HD, need special kernel)
Just to play safe, is [3] the option for installing to internal flash (= HD)?
Anyhow thanks for your great effort again! Hope we can see the long-awaited Beta5 soon!
-
Just to play safe, is [3] the option for installing to internal flash (= HD)?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=137712\"][{POST_SNAPBACK}][/a][/div]
I read the instructions to mean that doing nothing (no options) installs to the internal flash on the 7** and 860. Anyone know if that's right? I'm also interested if anyone has tried this new beta4 and could report how usable it is compared to beta1. Is it the same as the beta4 for the 1000 or have any of the glitches noted there been fixed in this later version of beta4?
-
any new update for C1000?
-
Just noticed that things got updated in http://mail.pdaxrom.org/download/1.1.0beta...us-7x0-860/new/ (http://mail.pdaxrom.org/download/1.1.0beta4/Zaurus-7x0-860/new/)
Is there anything specially updated or fixed not just for the previous 7x0-860 version but also for the Cxx00 one?
And for this in the blog:
U-Boot buttons during power-up:
[OK] - emergency system
[1] - pass to kernel: root=/dev/mmcblk0p1 (root filesystem on SD/MMC card)
[2] - pass to kernel: root=/dev/hda1 (root filesystem on CF, need special kernel)
[3] - pass to kernel: root=/dev/hdc1 (root filesystem on HD, need special kernel)
Just to play safe, is [3] the option for installing to internal flash (= HD)?
Anyhow thanks for your great effort again! Hope we can see the long-awaited Beta5 soon!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=137712\"][{POST_SNAPBACK}][/a][/div]
I tried the new beta4 a little but some fatal errors still exist (on SL-7500C). My 7500 often power off suddenly without any cause. I guess the battery/charging function has some problem.
Once I managed to get into X and most functions are still the same.
Anyway, I'm interested in the multi-boot funtion of the new u-boot. Could I boot beta1 or Cacko from SD (Does the kernel have to be the same)? Can anybody post a guide of how this can be done?
-
sashz, is there any update in sl-c860 beta4?
I'd like a new stable release, I cannot use my zaurus anymore, and I don't want to leave pdaxrom family, since pdaxrom is the only rom that fits my needs
-
Sashz has released some new beta4 stuff:
http://mail.pdaxrom.org/node/107 (http://mail.pdaxrom.org/node/107)
Downloads avalible from:
http://mail.pdaxrom.org/download/1.1.0beta...us-7x0-860/new/ (http://mail.pdaxrom.org/download/1.1.0beta...us-7x0-860/new/)
Summery:
U-Boot buttons during power-up:
[OK] - emergency system
[1] - pass to kernel: root=/dev/mmcblk0p1 (root filesystem on SD/MMC card)
[2] - pass to kernel: root=/dev/hda1 (root filesystem on CF, need special kernel)
[3] - pass to kernel: root=/dev/hdc1 (root filesystem on HD, need special kernel)
Regards
David
-
thx for the hint. Have you tried this release?
-
Hi there,
have installed the new beta 4.
The battery problem still persists so cannot resume without reboot.
Anyone know how to slove the battery problem ?
BR,
Felix.
-
thx for the hint. Have you tried this release?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=138117\"][{POST_SNAPBACK}][/a][/div]
Very little testing so far on the rom but I've already widely used the new u-boot features.
I've recompiled it to make use of 2 and 3 to boot from mmcblk0p2 and mmcblk0p3
I have a modified emergency system booting from ext3 on mmcblk0p1 and I'm working to have the beta4 system booting from mmcblk0p2 so that I can modify it while still being able to boot unmodified version from onboard flash.
Since the freeze on suspend I thing is dew to something done during the rc5 level stuff I hope to be able to debug the exact origin.
I have in any case reproduced the problem on the emergency system:
boot to emerg,
halt
press "power on" button. This seqience produces the same blinking cursor that I see when I try to suspend (by pressing "power on" button on running system).
Regards
David
-
Not 100% relevent to this thread ... but since I mentioned above...
I think the freeze on suspend ia a problem bound to my pda:
I have avoided loading the whole sound module stack (as my c760 produces no sound). Doing this made the freeze on suspend problem dissapear.
I already noticed that when I enabled the sound widget the pda became inherently slow so generally I muted the sound anyway.
So I pretty sure that the problem is bound to my hardware.
Regards
David
-
Hi,
How can I install beta3 (initrd.bin updater.sh tools.tar)
using u-boot?
dd? nandwrite? or recycle sharp bootloader and... ?
I'd like to try beta3 after beta4 and u-boot.
---------------------
Report on beta4 impressions:
i've installed u-boot, having both leds (orange and green) flashing.
After that everything went ok.
beta4 misses cardctl, there was no audible sound, some progs behind the icons did not
worked (usb config...), vm menu went out of screen.
No backlight dim / zoom keys worked.
Button suspend is an eyeshot, resume is rather slow.
beta4 could not drove SysOn CF gps card.
Usb gadgets, like mouse, keyboard, netwk adapter worked well.
Internal keyboard worked, extnal usb keyboard failed some keys, eg. up arrow... (labtech ultra-flat).
z: SL-C3200, sd: 1g, 2g, mmc: 256m CF: 1g, worked all of them for u-boot intall.
O.
-
Ok, a transcript of a difficult day with my C860.
Following directions in this thread I put the 11 files (incuding md5sums, but I later discovered I was using files from July26, not the most recent ones) on my 256mb Lexar CF and started the process.
After installing Uboot, it failed to reboot (never finished going down).
Forcing the issue, I finally got it to boot to the Uboot emergency shell, and nothing. Around this time I realize the date disparity and download the newest files. mkfs.msdos and copy the files over again, still the same.
I poke around the emergency shell and get a segfault when it tries to access the CF. Ugly.
So I yank the 128mb CF from my camera, reformat, and try with that one. Nada.
Third time's the charm - I reformat my ext3 SD card (256mb /home) and put the files on it, and the emergency system recognizes and installs the new system.
Now, Uboot and the emergency system still have a problem, can't handle CF.
OK, I can boot the new system. And it seems to recognize my Socket WiFi, and my Ambicom WiFi, and my Billionton Bluetooth CF cards. (the toolbar applet has reasonably accurate names for them) But it's unable to work with any of them, and 'cardctl' cannot be found. (although eject from the toolbar applet works) Bluetooth gives me 'Can't get DUN info' trying to set up BT dialup. The LAN&WiFi tool keeps defaulting to profile 'none' even though I created one named 'wifi' successfully.
'control' and 'alt' keys, which input tool tells me are already mapped to 'calendar' and 'address' keys, are all hinky - they're clearly NOT mapped to those keys... And my up-arrow doesn't work in mc, but works in plain console? (ctrl and alt are broken both places)
1 - How do I reflash the Uboot to correct it's CF issues?
2 - During reformat of the internal flash, Uboot found a bad block around 72% through, and worked around it. How concerned should I be for longer-term survival of the internal flash?
3 - How do I get at least one of the wifi cards working? It seems that bluez isn't installed in the basic image, so I'm presuming that I need to pull the packages from feed for bluetooth. But what about cardctl??
4 - What about Ctrl, Alt, and Up? I've tried using mc's builtin key configurator, and it is unable to recognize when I press 'up', even though 'up' correctly cycles through the console history??
j
-
Hi,
How can I install beta3 (initrd.bin updater.sh tools.tar)
using u-boot?
dd? nandwrite? or recycle sharp bootloader and... ?
I'd like to try beta3 after beta4 and u-boot.
---------------------
Report on beta4 impressions:
i've installed u-boot, having both leds (orange and green) flashing.
After that everything went ok.
beta4 misses cardctl, there was no audible sound, some progs behind the icons did not
worked (usb config...), vm menu went out of screen.
No backlight dim / zoom keys worked.
Button suspend is an eyeshot, resume is rather slow.
beta4 could not drove SysOn CF gps card.
Usb gadgets, like mouse, keyboard, netwk adapter worked well.
Internal keyboard worked, extnal usb keyboard failed some keys, eg. up arrow... (labtech ultra-flat).
z: SL-C3200, sd: 1g, 2g, mmc: 256m CF: 1g, worked all of them for u-boot intall.
O.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=138588\")
I've suggested a reasonable attempt on how to use beta1 with uboot [a href=\"https://www.oesf.org/forums/index.php?showtopic=20401]here[/url] ... I guess you could do the same for beta3.
no cardctl in beta4 ... try pccardctl.
-
Hi all,
yes I wnat to try Beta4 with u-boot on my nice c860 but got terible dipressed (near to throw my c860 out of the window!) ... ok, not really ;-)
I tried everything to flash u-boot ... wrote some comments and threads ... btu I could not flash u-boot ... Beta 2 works well on my c860 and I am able to flash origial SHARP Rom and OZ with GPE, works fine but I want to have pdaXrom on it ...
NAND restore / backup works well to get back to my working Beta2 :-) but why am I not able to get u-boot working? CF / SD is well formated with FAT16 (tried it with or without partitioning)
trying to flash u-boot with this dammed D + C keys gives me only blinking green / yellow ...
Full Flash erase runs ok and Full Flash test says ok (no partition data found with other test - ok I think!)
try to use CF update from servicemenu ( D + M) says "Model error!" ... read some threads
No I'm very helpless ... I opened my c860 looking for the fuses to charge and power my Z. Looking for the connectors plug inside Z (thought there is a connecting problem, because sometimes my Z makes some problems - nothing!)
many many many THX to everybody who has a little hint foer me
Martin
-
OK, I'm giving up on Beta4 for now. I'm tired of fighting to get wifi and bluetooth working, (and losing) not to mention frustrated at keyboard snafus - like 'up' not working correctly, and 'a' (or for that matter, scrolling) not working on console after exiting X.
But the only NAND backup for the C860 I can find on my home network is the original Japanese Sharp rom.
And the downloads section at Conics.net is down for another week.
Where can I find a NAND backup that I can flash back onto my C860 (preferably a newer English one, ideally a Pdaxrom one), and how do I do that now with the Uboot deal, is it still the same?
j
-
a- check tisoft
b- just flash the japanese rom then upgrade to cacko?
c-do b but flash to pdaxrom beta3?
-
I say Option "c" :-)
Late
-
a- check tisoft
b- just flash the japanese rom then upgrade to cacko?
c-do b but flash to pdaxrom beta3?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=139075\"][{POST_SNAPBACK}][/a][/div]
a- Well, tisoft seems to have the same NAND as I have, plus one a year newer, with some German mods?
b- I don't want to go cacko or sharp, I want pdaxrom.
c- Seems there IS no 'beta3' for C860? All I can find are beta1 and beta4, then the old rc12 (which I was running before trying the beta4 deal)
So I guess I'll NAND restore back to the original japanese ROM, then install beta1. If I have continuing problems there then I'll go back to rc12. What burns me up is that I was careful to make NAND backups whenever I'd successfully gotten a new upgrade working, but now I can't find them.
j
-
why am I not able to get u-boot working? CF / SD is well formated with FAT16 (tried it with or without partitioning)
trying to flash u-boot with this dammed D + C keys gives me only blinking green / yellow ...
Give a try... don't get confused for blinking leds, 'cause I had been in the same situation.
But I got over with it.
Cookbook: (at least worked for me)
1., fat16 on any card
2., not significant if it is the whole card, or partitioned for 1 partition, eg: mkdosfs -F 16 /dev/sda or /dev/sda1
3. wait long while both leds are blinking (or simply on), so not only 20 secs...
4., and finally leds stop blinking, and you have u-boot installed.
For me on c3200.
-
Hi osage,
Thanks ... I tried it many times like you say :-) ... giving it a try for several minutes, but leds don't stop blinking ...
Do you have a more exact time like "more than 20 sec."?
Anybody have problems with FAT16 and msdos filesystem? especially with the upper-/lowercase of filenames ... I use KDE3.5.4 to mount, unzip and copy files?
What about mounting options filenames style (lowercase, Win95,WinNT,mixed) and UTF-8?
Maybe I have problems with that and Lowlevel updater will not recognize the file on my FAT16 media?!
THX
Martin
-
Hi osage,
Thanks ... I tried it many times like you say :-) ... giving it a try for several minutes, but leds don't stop blinking ...
Do you have a more exact time like "more than 20 sec."?
Anybody have problems with FAT16 and msdos filesystem? especially with the upper-/lowercase of filenames ... I use KDE3.5.4 to mount, unzip and copy files?
What about mounting options filenames style (lowercase, Win95,WinNT,mixed) and UTF-8?
Maybe I have problems with that and Lowlevel updater will not recognize the file on my FAT16 media?!
THX
Martin
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=139099\")
Hi martin did you format as in this post [a href=\"https://www.oesf.org/forums/index.php?showtopic=19809&st=67#]https://www.oesf.org/forums/index.php?showtopic=19809&st=68#[/url]?
Simon.
-
Hi diesel,
yes, that's what I did to prepare CF or SD Card :-) tried it with / without partitioning on /dev/sd? and /dev/sd?1 ... but no chance ...
Maybe someone could make a fresh installation on a c860 and post me a NAND backup? This works without problems on my c860! I could give some place on my server! Please PM me.
Yes I'm missing the donation link on the new website too.
THX
Martin
-
Hi,
I wonder why there are two threads about the same issue (Beta4)???
My Z is now running beta4 and I have the same problems that were already reported. Using the mentioned alsamixer I now have sound and the Fn-key works as right mouse button after I made the mentioned changes to /etc/sysconfig/x11mousebutts
The Ctrl and Alt keys still do not work at all any solution so far??
I found another strange thing: When I read a book using pdf-viewer and then turn my Z off and on again the pdf-viewer starts to turn pages like pressing (Fn-Up) and the only thing I could do is to kill xpdf.
I am not going back to my previous Beta1. Beta4 is just too nice
Short update:
I found another problem: After turning my Z back on when it was shut off for a longer time (e.g. over night) the SD and CF cards are not accessible any more. Any attempt to read from either one results in a green cpu panel (cpu stays busy) and the only solution is to kill the reading provess. I have not yet discovered how to make the cards work again without a reboot. Eject and reinserting the cards is not sufficent.
-
Hi,
I'm in a tricky situation with my 860 right now. Whenever I try to use C+D I get both LEDs flashing. Nothing else happens:( Also from D+M I cannot select 'CF Update' because it says: SD Update, ---Found orders---, followed by 'Model Error!!' displayed in red...
The only thing that works is doing a NAND restore. However even then I can not update my 860 to anything else because I can no longer get the Japanese Update menu (OK+power).
Is there a chance I can get that Japanese Update menu back?? I'm guessing that should solve my problems.
Thanks in advance
-
Okay, nevermind Luckily the japanese menu re-appeared after I did a NAND restore
Everything seems to install just fine now, fiew
-
The Ctrl and Alt keys still do not work at all any solution so far??
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=139628\")
Have you tried the two japanese keys right to the Fn key? They work for
me on my C860 (from [a href=\"http://openzaurus.org/wordpress/howto/c7x0-and-cxx00-26-kernel-information/]OpenZaurus c7×0 and cxx00 2.6 Kernel Information[/url])
-
Can anyone explain why I can boot into the emergency system but when I try to do anything it just freezes?
I have a c760.
I can change the directory to /mnt/cf but when I try to do this:
nandlogical /dev/mtd1 WRITE 0x0 0x20000 u-boot.bin
it just freezes. Actually, if I try to do anything (like `ls') it freezes.
I tried using that D-M method that sashz presents us (the one with all the pics) to no avail, i.e. it seemed to work, but then it just booted into the emerg system again and froze like before.
Any help?
Thanks.
dq
-
Can anyone explain why I can boot into the emergency system but when I try to do anything it just freezes?
I have a c760.
I can change the directory to /mnt/cf but when I try to do this:
nandlogical /dev/mtd1 WRITE 0x0 0x20000 u-boot.bin
it just freezes. Actually, if I try to do anything (like `ls') it freezes.
I tried using that D-M method that sashz presents us (the one with all the pics) to no avail, i.e. it seemed to work, but then it just booted into the emerg system again and froze like before.
Any help?
Thanks.
dq
[div align=\"right\"][a href=\"index.php?act=findpost&pid=140637\"][{POST_SNAPBACK}][/a][/div]
Hi,
on my C860 I had the same problem. I just removed the card when my Z was turned off and reinserted it after turning the Z back on. This was not ment to solve the problem, I did it just to check if it was the correct card, but it solved the problem
-
The Ctrl and Alt keys still do not work at all  any solution so far??
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=139628\")
Have you tried the two japanese keys right to the Fn key? They work for
me on my C860 (from [a href=\"http://openzaurus.org/wordpress/howto/c7x0-and-cxx00-26-kernel-information/]OpenZaurus c7×0 and cxx00 2.6 Kernel Information[/url])
[div align=\"right\"][a href=\"index.php?act=findpost&pid=140153\"][{POST_SNAPBACK}][/a][/div]
Thanks, that works
Does anyone know how to change this without the GUI, which doesn't seem to work? I find it difficult to hold both kanji keys and press left or right to switch desktops. With Calendar and Address as Ctrl and Alt this was quite easy.
Cheers, Jan