Messages

16

Debian / Gpe On Debian?

« on: July 29, 2008, 07:46:37 am »

About the battery: I find my battery dies quickly with Debian as well. I am using yonggun's andromeda image.
I have two suppositions:
- we need to make lower the backlight level, which is easy in X but I don't know how to do it in console.
- maybe by default the cpu is overclocked.

Anyone knowing more about this?

17

Debian / [new] Kernel 2.6.24.4 With Cpufreq

« on: July 23, 2008, 12:37:42 am »

Hi 2or0, thanks for your help every time.
Could you provide a lirc module?
I would like to control my tv with my zaurus

Thanks in advance

18

Debian / I Want It Compiled !

« on: July 19, 2008, 04:26:28 am »

I would love to run qt4 embedded on debian, directly on linuxfb.

-> Request Qt4.4 build with -embedded arm and linuxfb as graphics driver.

Thank you!

19

Debian / [new] Kernel 2.6.24.4 With Cpufreq

« on: July 17, 2008, 10:06:24 pm »

Thank you very much!!!

20

Debian / Dualbooting/multiplebooting With Kexec!

« on: July 15, 2008, 09:25:58 pm »

OK, I found the way to go! Thanks Pelrun for the hint!! Only the boot params needed to be changed, so it was rather easy.

Since this topic is rather long I started a new one. Feel free to move it back here if necessary:

Kexec how-to really working: : see https://www.oesf.org/forum/index.php?showtopic=25983

21

Debian / Kexec From Debian To Sharprom, Really Working How-to!

« on: July 15, 2008, 09:22:21 pm »

Hello, I was frustrated about not being able to kexec successfully into sharprom, but frustration is over!!
Following Pelrun's hint that the NAND partition layout had to be hardcoded, I recompiled eviljazz's kernel passing the necessary argument to the kernel, and now using this kernel for kexec the dreaded: "unable to open initial console" is GONE!!"

How-to


1. On your Z
Boot into the sharprom using your usual kernel, check the file /var/log/dmesg and find the line which contains this:
mtdparts=sharpsl-nand:7168k@0k(smf),44032k@7168k(root),-(home) jffs2_orphaned_inodes=delete EQUIPMENT=5 LOGOLAND=1 DEFYEAR=2008 LOGO=1 LAUNCH=q
(Your values for sharpsl-nand may vary, and this is why you need to build your own kernel)

2. On your linux Desktop:
- download eviljazz's toolchain http://katastrophos.net/zaurus/kernels/com...1.09.05.tar.bz2
- download eviljazz's kernel tarball http://katastrophos.net/zaurus/kernels/cur....20-v55.tar.bz2

- Follow the instructions in the kernel tarball's README, but after executing "make oldconfig", do "make menuconfig".
In there, go to General Setup, and scroll down until you find the place to edit kernel arguments. By default, they should be: "console=ttyS0 root=/dev/mtdblock2"
Select that, and add the line you have noted on your Z earlier, so that the boot param becomes:
console=ttyS0 root=/dev/mtdblock2 mtdparts=sharpsl-nand:7168k@0k(smf),44032k@7168k(root),-(home) jffs2_orphaned_inodes=delete EQUIPMENT=5 LOGOLAND=1 DEFYEAR=2008 LOGO=1 LAUNCH=q
(Again, with your values for sharpsl-nand)

Go on with "make dep" and "make zImage", the resulting zImage will work for kexecing to sharprom!

22

Debian / Dualbooting/multiplebooting With Kexec!

« on: July 15, 2008, 03:36:54 am »

@Pelrun

Could you explain this in more detail please?
I would be happy to build a kexec-ready sharprom kernel. I tried before but didn't know where/what to alter.

Thanks in advance.


Matthis

23

Debian / Graphics Acceleration And Xrandr

« on: June 28, 2008, 10:35:53 am »

Hi, I am using yonggun's andromeda image with his 2.6.24 kernel.

I noticed that scrolling and moving windows around is much smoother in portrait mode compared to landscape mode...

Would there be a way to keep the graphic acceleration in landscape mode?


I know this is quite vague, but would be happy to know more about what's happening there..

Thanks!

24

Ubuntu / Ubuntu Mid Edition

« on: June 26, 2008, 07:59:07 pm »

Capn_Fish: I'll build it for Debian, if that's any consolation.

Yes Please!!!!!!!!!!

25

Linux Issues / Setup Dev On Sl-c1000 Kernel 2.4.20 Cacko 1.23 Howto

« on: June 23, 2008, 08:08:21 pm »

http://www.users.on.net/~hluc/myZaurus/

Look for zgcc on the page!

26

Sharp ROMs / Lirc On Tetsu/eviljazz Kernel (2.4.20)

« on: June 19, 2008, 07:18:24 am »

Same errors for 0.8.3  

27

Sharp ROMs / Lirc On Tetsu/eviljazz Kernel (2.4.20)

« on: June 18, 2008, 10:37:27 am »

Dear Capn_Fish,

Thank you for your reply.
Yes I did post from where the errors started ... no such thing as ***.h missing or any other helpful hint.

(Maybe I need to disable something in ./configure?)


PS: I tried with lirc version 0.6.6 (which has apparently been succesfully build for 2.4.18), but got the same errors.

28

Sharp ROMs / Lirc On Tetsu/eviljazz Kernel (2.4.20)

« on: June 18, 2008, 07:58:01 am »

As far as I know we don't have a working lirc module for 2.4.20 on the Sharp/Cacko ROM.

I tried to build Lirc 0.8.2

1.  ./configure --host=i686 arm=arm-gnu-linux --with-kerneldir=/home/mat/Desktop/zaurus-kernel-2.4.20-v55/linux/ --prefix=/home/mat/Desktop/lirc-arm/ --with-driver=sa1100

2. make ends with these errors...

[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']lirc_sir.c:139: `IRQ_Ser2ICP' undeclared here (not in a function)
lirc_sir.c: In function `on':
lirc_sir.c:242: `PPSR' undeclared (first use in this function)
lirc_sir.c:242: (Each undeclared identifier is reported only once
lirc_sir.c:242: for each function it appears in.)
lirc_sir.c:242: `PPC_TXD2' undeclared (first use in this function)
lirc_sir.c: In function `off':
lirc_sir.c:247: `PPSR' undeclared (first use in this function)
lirc_sir.c:247: `PPC_TXD2' undeclared (first use in this function)
lirc_sir.c: In function `lirc_write':
lirc_sir.c:362: `Ser2UTCR3' undeclared (first use in this function)
lirc_sir.c:383: `Ser2UTSR0' undeclared (first use in this function)
lirc_sir.c:383: `UTSR0_RID' undeclared (first use in this function)
lirc_sir.c:383: `UTSR0_RBB' undeclared (first use in this function)
lirc_sir.c:383: `UTSR0_REB' undeclared (first use in this function)
lirc_sir.c:385: `UTCR3_RXE' undeclared (first use in this function)
lirc_sir.c:385: `UTCR3_RIE' undeclared (first use in this function)
lirc_sir.c: In function `sir_interrupt':
lirc_sir.c:624: `Ser2UTSR0' undeclared (first use in this function)
lirc_sir.c:629: `UTSR0_EIF' undeclared (first use in this function)
lirc_sir.c:635: `Ser2UTSR1' undeclared (first use in this function)
lirc_sir.c:637: `UTSR1_FRE' undeclared (first use in this function)
lirc_sir.c:639: `UTSR1_ROR' undeclared (first use in this function)
lirc_sir.c:641: `UTSR1_PRE' undeclared (first use in this function)
lirc_sir.c:645: `Ser2UTDR' undeclared (first use in this function)
lirc_sir.c:650: `UTSR0_RFS' undeclared (first use in this function)
lirc_sir.c:650: `UTSR0_RID' undeclared (first use in this function)
lirc_sir.c:663: `UTSR1_RNE' undeclared (first use in this function)
lirc_sir.c:675: `UTSR0_TFS' undeclared (first use in this function)
lirc_sir.c:683: `UTSR0_RBB' undeclared (first use in this function)
lirc_sir.c:683: `UTSR0_REB' undeclared (first use in this function)
lirc_sir.c:616: warning: `data' might be used uninitialized in this function
lirc_sir.c: In function `init_hardware':
lirc_sir.c:875: `Ser2HSCR0' undeclared (first use in this function)
lirc_sir.c:877: `Ser2UTCR0' undeclared (first use in this function)
lirc_sir.c:878: `Ser2UTCR1' undeclared (first use in this function)
lirc_sir.c:879: `Ser2UTCR2' undeclared (first use in this function)
lirc_sir.c:880: `Ser2UTCR3' undeclared (first use in this function)
lirc_sir.c:881: `Ser2UTCR4' undeclared (first use in this function)
lirc_sir.c:883: `Ser2UTDR' undeclared (first use in this function)
lirc_sir.c:884: `Ser2UTSR0' undeclared (first use in this function)
lirc_sir.c:885: `Ser2UTSR1' undeclared (first use in this function)
lirc_sir.c:889: `PPDR' undeclared (first use in this function)
lirc_sir.c:889: `PPC_TXD2' undeclared (first use in this function)
lirc_sir.c:890: `PSDR' undeclared (first use in this function)
lirc_sir.c:898: `HSCR0_HSSP' undeclared (first use in this function)
lirc_sir.c:901: `UTSR0_RID' undeclared (first use in this function)
lirc_sir.c:901: `UTSR0_RBB' undeclared (first use in this function)
lirc_sir.c:901: `UTSR0_REB' undeclared (first use in this function)
lirc_sir.c:904: `UTCR0_1StpBit' undeclared (first use in this function)
lirc_sir.c:904: `UTCR0_7BitData' undeclared (first use in this function)
lirc_sir.c:909: `UTCR4_HPSIR' undeclared (first use in this function)
lirc_sir.c:909: `UTCR4_Z1_6us' undeclared (first use in this function)
lirc_sir.c:912: `UTCR3_RXE' undeclared (first use in this function)
lirc_sir.c:912: `UTCR3_RIE' undeclared (first use in this function)
lirc_sir.c: In function `drop_hardware':
lirc_sir.c:1015: `Ser2UTCR3' undeclared (first use in this function)
lirc_sir.c:1017: `Ser2UTCR0' undeclared (first use in this function)
lirc_sir.c:1018: `Ser2UTCR1' undeclared (first use in this function)
lirc_sir.c:1019: `Ser2UTCR2' undeclared (first use in this function)
lirc_sir.c:1020: `Ser2UTCR4' undeclared (first use in this function)
lirc_sir.c:1023: `Ser2HSCR0' undeclared (first use in this function)
make[5]: *** [lirc_sir.o] Error 1
[/div]

What do I need to get it to compile? Thanks for any help.

29

Debian / Customized New Rootfs

« on: June 17, 2008, 11:27:25 am »

I installed it to hda1

30

General Discussion / Qemu Zaurus Emulation, With Cacko/sharp Rom

« on: June 14, 2008, 11:00:44 pm »

The latest version of Qemu (0.9.1) adds support for Xscale emulation and specific zaurus emulation.

I have used this successfully for roms which do not use nand, like debian.

But I would love to get sharp-rom going under emulation.
Here are the steps needed to get going, from what I have gathered up until now.

1. Get sharp/cacko kernel
http://tetsu.homelinux.org/zaurus/kernel/v...-v18j-C3200.bin  (this is for 3200 --> terrier in qemu)

2. From the emergency menu of your zaurus, do a full NAND backup (I get a SYST320.DBK) file. (I have an sl-c3200)

3. extract the necessary bit from this backup file: use this script: http://web.mita.keio.ac.jp/~mh070504/nand-ripper.sh

As explained in the script, you may have to modify two parameters:

[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']YOU MAY NEED TO ADJUST THE TWO PARAMETERS BELOW.

Run the indicated commands on the zaurus to find your values.  It is unlikely
that ROMFS needs changing - I think this is fixed in the firmware at 7Mb,
i.e., 7 x 8 = 56 128kb blocks.  ROOTFS on the other hand will depend on how
you have divided up the remaining 121Mb between the root and user partitions.

EOC

ROMFS=56        # Use 'wc -c </dev/mtdblock1' and divide result by 128x1024.
ROOTFS=344      # Use 'df' to find the 1k-blocks for /dev/root and divide by 128.[/div]

Then run the script like this: ./nand-ripper.sh ripped_nand all SYST320.DBK

4. Get going with qemu:

qemu-system-arm -M terrier -kernerl sharp_kernel.bin -mtdblock ripped_nand -portrait


THIS FAILS AT THIS POINT: the kernel complains endlessly about reading nand error.
I suppose the script to rip has to be adjusted or something.

Anyone knowledgeable in this area?? Thanks! I think this is quite an exciting project.