A Clean, Fresh, Configured Eabi Rootfs Tarball

[zaurier]

I have still problems connecting wireless via WPA-TKIP. I installed wpa_supplicant and got it running but no success (wap_cli shows a pingpong between "accociated with..." and "CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys")... Before i go in details my first question: Is anybody out there, who get this tarball installation running with wireless WPA connection?

thanks zuaurier

[ZDevil]

autoboot.sh (posted in this topic ) don't work..
i have write in u-boot emergency shell:

nandlogical /dev/mtd1 WRITE 0x5a0000 0x160000 /mnt/card/kernel.img

I didn't have any problem using the attached script.    The command you used is already in the autoboot.sh (notice the autoboot.sh for debian is different from the one for pdaXrom)   Or is it only me?

[zecrazytux]

Hoy all

As I explained on my blog: http://www.zecrazytux.net/GNU-Linux/Zaurus...x-on-the-Zaurus I got busy for a time... And i did'nt succeed to get clicks working.
I did'nt noticed that a younggun kernel existed for c1000 zauriis.
Lots of thanks for your work zdevil ! it works perfectly !

[jpmatrix]

Hoy all

As I explained on my blog: http://www.zecrazytux.net/GNU-Linux/Zaurus...x-on-the-Zaurus I got busy for a time... And i did'nt succeed to get clicks working.
I did'nt noticed that a younggun kernel existed for c1000 zauriis.
Lots of thanks for your work zdevil ! it works perfectly !

blog bookmarked
il fait beau à Troyes ?

[zogs]

autoboot.sh (posted in this topic ) don't work..
i have write in u-boot emergency shell:

nandlogical /dev/mtd1 WRITE 0x5a0000 0x160000 /mnt/card/kernel.img

I didn't have any problem using the attached script.    The command you used is already in the autoboot.sh (notice the autoboot.sh for debian is different from the one for pdaXrom)   Or is it only me?

scenario:

pdaXrom emergency system
==================
pdaXrom [Borzoi]
Loading /etc/sysconfig/keyboard/Borzoi/keymap.map
Bootscript /mnt/card/autoboot.sh, go...
: command not foundsh : line 2:
: command not foundsh : line 4:
: command not foundsh : line 6:
Proceed with debian installation or boot to emergency system? [y/n]
: command not foundsh : line 8:
y
' : not a valid identfierne 9: read: 'ans
: command not foundsh : line 10:
'mnt/card/autoboot.sh: line 19: syntax error near unexpected token 'do
'mnt/card/autoboot.sh: line 19: 'for file in $LOC/kernel.img $LOC/KERNEL.IMG; do

Processing /etc/profile... Done

-sh-3.08# cd /mnt/card
-sh-3.08# sh autoboot.sh
[command not foundsh..etc etc repeat]

-sh-3.08# ./autoboot.sh
-s: ./autoboot.sh: /bin/sh^M: bad interpreter: No such file or directory
-sh-3.08# vi autoboot.sh

o my god !!  ^M on end of every line
delete all ^M from autoboot.sh and :wq

restart with u-boot emrgency for kernel installation and it work fine
the problem is the format of autoboot.sh  sorry

[zaurier]

WPA connection still not working (I use the Ambicom WL1100C-CF card with my c1000). Before I try another 1000 configuration examples with wpa_supplicant.conf and network configuration files my question: Is anybody out there, who actually succeeded in WPA-connecting with this eabi-tarball-installation?

zaurier

[scottlfa]

I have found that things that aren't Z specific can be found in alot of the debian forums if that helps.   Its where I have had to go to get a number of configuration options.

[zaurier]

I have found that things that aren't Z specific can be found in alot of the debian forums if that helps.   Its where I have had to go to get a number of configuration options.

I know that and of course I searched the (debian) forums for configuration problems/options and tried REALLY a lot... But none of the tips and configuration-samples helped/worked. I ask in this forum because my AMBICOMcard worked with all other ROMs I have installed so far. I just want to know whether somebody succeeded with THIS eabi-tarball-installation to make sure its "only" (my) configuration problem and it is possible to get the card working with THIS INSTALLATION and WPA encryption...  

thanks zaurier

[LinuxGadget]

Before i go in details my first question: Is anybody out there, who get this tarball installation running with wireless WPA connection?

thanks zuaurier

Ok, maybe it's about time to go in details?  

[malik]

hello,

can someone please help:

* i want to use zdevils instructions to install debian on my z and went
into problems with uboot
* i read a thread of capn_fish what to do if something goes wrong while
installing uboot, but nothing helped.
* meanwhile i was able to install uboot using
pdaXrom-1.1.0r198-Kathrin-akita-uboot.zip coming from a fresh sharprom
(trisoft nand)/(fresh)cackorom installation, but after that i cant reboot
the zaurus using the on/off button and i cant get into the desired emergency
mode. nothing happens, cant get into the japanese mode or do c+d+reset to
install the kernel. sometimes even (fn+)d+m didnt worked, no headaches yet:-)
* i guess the installation order is alright. do i need to prepare the rootfs
on sd as the first step? i guess no...

my hope was to keep the cackorom in the flash and to use it (with kexec
from angstrom).

[Chero]

hello,

can someone please help:

* i want to use zdevils instructions to install debian on my z and went
into problems with uboot
* i read a thread of capn_fish what to do if something goes wrong while
installing uboot, but nothing helped.
* meanwhile i was able to install uboot using
pdaXrom-1.1.0r198-Kathrin-akita-uboot.zip coming from a fresh sharprom
(trisoft nand)/(fresh)cackorom installation, but after that i cant reboot
the zaurus using the on/off button and i cant get into the desired emergency
mode. nothing happens, cant get into the japanese mode or do c+d+reset to
install the kernel. sometimes even (fn+)d+m didnt worked, no headaches yet:-)
* i guess the installation order is alright. do i need to prepare the rootfs
on sd as the first step? i guess no...

my hope was to keep the cackorom in the flash and to use it (with kexec
from angstrom).

Forget about Cacko on flash when you want to use uboot and debian : they use different kernels.

(To make sure uboot is working : flash pdaXrom r198 following the instructions.
If you can boot it, uboot is ok.)
Do you need to prepare the rootfs : yes.
What else do you need to to : flash the kernel (actually, if you can flash the kernel uboot is ok)
Then : just reboot.

About installing uboot, flashing the kernel :
uboot is very picky about sd-cards and how they are formatted/partitioned. I always use a card with 2 partitions where the first one is fat-formatted and I always succeed. Before I used this card I used a card with 1 partition (a new one !) and never got it working.

Good luck,
Chero.

[scottlfa]

I agree with Chero, if you have PdaXrom 198 running uboot is fine, flashing it is easy from there.  I am thinking that it won't be a happy marriage if you try to run cacko and u-boot.   So far I have only successfully got a dual boot setup out of Angstrom & Debian.

I too use a dual partitioned card, fat on first and ext3 on the larger second partition (lesson learned while messing with the C1k and debian).

[malik]

thanx for the quick answers. it is possible to run angstrom from hd and cacko
from nand using kexec. does the necessity of uboot kill this kind of scenario for
yongun/debian and cacko? i mean booting to a debian console, executing kexec
from the angstrom feed... maybe uboot changes the nand flash in such a way that
this becomes impossible.

[malik]

partitioning the cards and flashing r198 is not needed. bad news for me: kexec executes
the cacko kernel ripped from tools.tar, but the kernel hangs while booting. the preinstalled
nand image seems to be disturbed by uboot and/or the yonggun kernel. maybe i will try
it from a clean cacko or sharprom install...

[malik]

1) uboot installation from cf card and japanese menu: works now for me
but only when the sd card isnt inserted (not uboot specific)
2) rebooting works fine after installing the yongun kernel, i.e. using
reset or a reboot from console. before its a really headache, the zaurus
seems not to react on anything or arbitrarily concerning wakeups/reboots or
d+m stuff. can someone confirm this behaviour?
3) script didnt worked for me, executed the nandlogical command by hand
4) some progress with kexec and a fresh cacko installation, getting a lot
of error messages and warnings, but now i can see the cacko screen, starting
linux and qtopia... the story ends here:-)