Topics

1

C1000/3x00 Hardware / C1000 - Hw Pb With Touch Screen

« on: February 28, 2010, 10:30:04 am »

Hello,
I've some troublshooting with my C1000. When I use the point to press in the screen, the action isn't recognized.

In "DEBUG MODE", there is  3 pages and in the page 3, the choice 7, there is "7. Extra Menu".
In "Extra menu" -> "1 Zaurus Test" -> "7. H Display". This option presents the character "H" or "h" on all the screen. When a place is touched, the screen commute between "H" and "h". This test is OK.

But, under Cacko, PdaXrom, the action isn't recognized. Isn't possible to make a new sceen's setup, where you press in the 4 coins of the screen.

Could you help me, to solve my problem ? A zaurus without touchscreen is too sad

Thanks a lot.

Randy

2

Zaurus - pdaXrom / Build Pdaxrom, Cross-compile : Some Evolution ? (don't Shout Me Please)

« on: February 22, 2009, 11:33:46 am »

Hi,
Fisrt, I must give some explications. I 'd looked at the www.pdaxrom.rom for several months without see anything chanching. And I'm using the Cacko to synchronise Outlook with the Zaurus for a while. I've forgotten to watch the forum ... sorry.

Now, I would come back to PdaXrom and use the cross-compilation. My second aim is to prepare an environment for this event : Solution Linux (Paris).

I'd looked at : PdaXrom Development, OESF Wiki Cross-Compilation and Beginner's Cross Compile Question.


My question is : What's the BEST way to build the environment ?

I'm waiting yours advices.


Thanks.

3

Zaurus - pdaXrom / Problem With Inodes At The Boot Time. [solved]

« on: September 18, 2006, 10:42:38 am »

Hello,

I'm running a Beta3 on a SL-C1000. At the boot time I have

Cramfs: wrong magic
FAT: bogus logical sector size 381
Inode #1666 was a directory with children - removong those too...
Inode #2442 was a directory with children - removong those too...
Inode #2464 was a directory with children - removong those too...
Inode #2468 was a directory with children - removong those too...
Inode #11343 was a directory with children - removong those too...

If there is no CF or SD, it's the same thing.
The NAND is good : Menu Service (D+M).
I've tried

# tune2fs -c 2 -C 3 /dev/mtdblock3
tune2fs 1.34 (25-Jul-2003)
tune2fs: Bad magic number in super-block while trying to open /dev/mtdblock3
Couldn't find valid filesystem superblock.
#

When I make a "mount" :

rootfs on / type rootfs (rw)
/dev/root on / type jffs2 (rw)
/proc on /proc type proc (rw)
none on /dev type tmpfs (rw)
/dev/mtdblock3 on /home type jffs2 (rw,noatime)
none on /dev/pts type devpts (rw)
/dev/mtdblock3 on /mnt/user type jffs2 (rw,noatime)
/dev/mmcda1 on /mnt/card type ext2 (rw)
/dev/hda1 on /mnt/cf type vfat (rw,noatime)
/dev/hda2 on /mnt/cf2 type ext2 (rw,nosuid,nodev)

I've also tried a Backup/Restore (D+M) : no modification. The backup reproduce the problem (the filesystem keep the bug)  : it's a  normal situation because de NAND has no default, only the filesystem.

How to obtain a normal filesystem ?

Thanks for your help.

Randy11