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

ant · « **Reply #75 on:** June 15, 2006, 10:52:59 am »

Quote

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

patsch · « **Reply #76 on:** June 15, 2006, 12:46:45 pm »

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.

patsch · « **Reply #77 on:** June 18, 2006, 12:57:11 pm »

Quote

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.

patsch · « **Reply #78 on:** June 18, 2006, 05:13:31 pm »

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:

Quote

Code: [Select]
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:

Code: [Select]
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.

VoiDeR · « **Reply #79 on:** June 28, 2006, 04:00:40 pm »

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.

louigi600 · « **Reply #80 on:** July 07, 2006, 06:18:18 am »

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

dinorex · « **Reply #81 on:** July 31, 2006, 04:35:14 am »

Quote

Quote
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]

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

kellyharding · « **Reply #82 on:** August 04, 2006, 04:41:27 pm »

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

dinorex · « **Reply #83 on:** August 05, 2006, 03:16:23 pm »

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

Code: [Select]

hold_right_button 0
right_button 96
middle_button 97
power_button 117

then you can make its content to be :-

Code: [Select]

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

kellyharding · « **Reply #84 on:** August 05, 2006, 05:27:39 pm »

Seems my Socket LP CF wifi card doesn't work with 1.1.0beta4?

Get:

Code: [Select]

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

kellyharding · « **Reply #85 on:** August 05, 2006, 07:05:57 pm »

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

InSearchOf · « **Reply #86 on:** August 05, 2006, 07:41:08 pm »

for beta4

unzip these 2 files to you CF or SD

Code: [Select]

# mkdir -p /usr/lib/hotplug/firmware
# cp *files* /usr/lib/hotplug/firmware

Insert card

for beta3

Code: [Select]

# 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

kellyharding · « **Reply #87 on:** August 06, 2006, 03:59:57 am »

Quote

for beta4

unzip these 2 files to you CF or SD

Code: [Select]
# mkdir -p /usr/lib/hotplug/firmware # cp *files* /usr/lib/hotplug/firmware
Insert card

for beta3

Code: [Select]
# 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

ZDevil · « **Reply #88 on:** August 07, 2006, 04:30:25 pm »

Just noticed that things got updated in http://mail.pdaxrom.org/download/1.1.0beta...us-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:

Quote

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!

stbrock · « **Reply #89 on:** August 07, 2006, 08:15:49 pm »

Quote

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?

News:

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