Messages

1

Angstrom & OpenZaurus / Pxa255 Kernel + Wi-fi Cf

« on: May 08, 2005, 10:52:42 am »

I don't see how rebuilding the modules should change anything. the xscale cache errata code is some arm asm bits contained in the startup and sleep/resume. Enabling or disabling this has no effect on the module code.

I'm not a kernel guru, but I'm sure the kernel size changes with the Cache Errata disabled, so some of the symbols the modules might want to call are certainly displaced, thus you have to recompile them, does it make sense ?

I'm pretty sure the System.map changes, so maybe the only thing needed is a valid System.map somewhere (and a depmod or sth like that) ?

Anayway, I recompiled the modules and I don't have the oops when plugin the USB connector, which lead me to think I was right, but this is maybe just a coincidence. I can't confirm anything about wifi as I don't have such cards.

2

Angstrom & OpenZaurus / Pxa255 Kernel + Wi-fi Cf

« on: May 06, 2005, 05:41:20 pm »

Nobody, as I suspected 
[div align=\"right\"][a href=\"index.php?act=findpost&pid=78517\"][{POST_SNAPBACK}][/a][/div]

If it works with the standard oz kernel, then I suspect you'll have to recompile the modules and not only the kernel.

Your best bet is to install OpenEmbedded, change the config and rebuild the kernel (this is a quite easy step to do) or to convince someone to build the modules for you.

3

Angstrom & OpenZaurus / Greate We Can Change To Terminal, But How ...

« on: December 09, 2004, 02:09:21 pm »

Greate we can change to Terminal mode (like CTRL+ALT+F1 on PC), but how to back to Opie/GPE GUI? We dont have this keys on Z!

use chvt.

4

Angstrom & OpenZaurus / OZ 3.5.1 how to beam ?

« on: November 09, 2004, 04:44:06 pm »

install openobex-apps

it seems openobex-apps is not part of the OZ feed ?
There is only libopenobex...
Can I build it with OE (I don't have the environment at home to verify).

On a side note, it seems to lack lirc-modules too.

Thanks,

Brice

5

Angstrom & OpenZaurus / OZ 3.5.1 how to beam ?

« on: November 08, 2004, 05:48:27 pm »

After a week of running OZ3.5.1 (and several flashing operations), I'm very pleased :-)
Almost everything works (sometimes with some fiddling, hence the 'unstable' status).
I was jsut wondering how to activate IR beam ?
The IR applet does not seem to do anything on my SL-5600.
Do I need a special app/module ?
Then after that, is there any option to beam a file or contact in OPIE ?

Thanks,
Brice

6

Angstrom & OpenZaurus / OZ3.5.1 Kernel question

« on: November 08, 2004, 05:08:23 pm »

masterzen, sorry, I don't know if it works with a 5600, I have a 5500. But if you find out, well, let us know

Unfortunately it does not seem to work.
It produces an initrd, the initrd can be flashed, but the kernel won't boot...

7

Angstrom & OpenZaurus / OZ3.5.1 Kernel question

« on: November 08, 2004, 09:01:24 am »

Basically just don't put an initrd.bin file (the filesystem) on the CF/SD card and proceed as normal with just the zImage.bin (kernel) and installer.sh.

Edit: The kernel should be named zImage (without the .bin) for the 5600.

Si

The upgrade went fine, but unfortunately, when booting the OZ kernel has panic'ed with something like:
VFS: can't find rootfs...
Analysis of the previous message showed that the kernel seems to partition the MTD while booting after an upgrade (maybe because the size of the kernel changed ?).
I have to look to the kernel's code...

8

Angstrom & OpenZaurus / opie camera on 3.5.1 ??

« on: November 04, 2004, 10:02:09 am »

I grabbed the module from the original Sharp initrd.bin (it was quite complicated to do, especially since my host is a linux/ppc computer), and the modules are different.

On a bit of a tangent, are the instructions for how to uncompress/mount/whatever an initrd.bin image on one's desktop computer available anywhere? Most the links I managed to find by various google queries don't exist anymore.

Windrose

I've found that howto:
How to read/modify initrd.bin

There are a few gotchas:

• your host must be running linux, I didn't find anything for other OS.
  
• you might have to strip the 16 first bytes of the file (at least for sharp rom) as they seem to have some version header at the beginning of the file.
  
• host endian-ness:
  jffs2 image are not endiannes friendly, so if your computer have not the same endianness as the jffs2 image, you won't be able to mount it.
  You have to modify the endianness of the jffs2 module by editing fs/jffs2/nodelist.h and change the following line:
  
  Code: [Select]
  #define JFFS2_NATIVE_ENDIANby
  
  Code: [Select]
  #define JFFS2_BIG_ENDIANand recompile the module.
  
• block & erase size:
  You need to check the /proc/mtd pseudo file on your zaurus and note the numbers for the root block of the MTD.
  Then divide by 1024 and give those numbers when loading the mtdram module (as explained in the second post of the above url).

9

Angstrom & OpenZaurus / Opie for left-hander ?

« on: November 04, 2004, 05:45:29 am »

Hi all,

I'm a left-hander, and have (thus) some problem to move the thumb of the windows' scrollbar with my left hand under opie while reading what's in the window at the same time. Using my right hand to use the stylus is not an option without a complete brain format.

I can't find anything about this on google or on the opie site, so if there are some poweruser there that can think about a solution or a magical setting somewhere...

Thanks,
Brice

10

Angstrom & OpenZaurus / opie camera on 3.5.1 ??

« on: November 04, 2004, 05:17:07 am »

Very good. Please send the 5600 module to me @ mickeyl@handhelds.org
C7x0 folks might also send me their module, since it probably doesn't work there either.

OK,

I'll do that as soon as I come back home.
Unfortunately it seems Opie-camera does not handle quite well the resulting images, as the saved jpgs  look fine only with the native resolution (320x240).
All other settings results in screwed images.

11

Angstrom & OpenZaurus / opie camera on 3.5.1 ??

« on: November 03, 2004, 04:45:39 pm »

Copy the module to your Zaurus, launch a console a do a 'diff <oldModule> <newModule>'. Then tell us the results. If they're different, we need to add the 5600 camera module to OE.

I grabbed the module from the original Sharp initrd.bin (it was quite complicated to do, especially since my host is a linux/ppc computer), and the modules are different.

I then overwrited the OZ modules with the sharp's one, and guess what, opie-camera is now working fine.
So I think you'll have to add a specific module for the 5600.

12

Angstrom & OpenZaurus / OZ3.5.1 Kernel question

« on: November 02, 2004, 05:23:19 pm »

Uhh, yeah, now THAT's a sad thing... You can download it at http://www.pipsfrank.de/public_files/ozone.tar.gz .

Many thanks,

Do you know if this version works with a SL-5600 ?
The author admits in the README that he never tested on this zaurus.

Thanks,

Brice

13

Angstrom & OpenZaurus / opie camera on 3.5.1 ??

« on: November 02, 2004, 05:14:19 pm »

The camera app on the first run after a reboot inflicts a a SIGSEGV. After that occasion it announces that it can't detect the card, and if run from the command line you get:

OGlobal::creating global configuration instance.
OConfig::0Config()
Opie-Camera: Creating ZCameraO::_instance
Opie-Camera: ERROR: Can't open camera driver: Device or resource busy

I also have a SL-5600, and have the same problem.

The module (sharpzdc_cs) produces an oops in the kernel. Then it remains 'used' and you can't unload it (only a reboot can help). (try dmesg to see what I mean).

From what I understood (I'm still looking for a complete ksymoops, mine borrowed from debian-arm seems to work but with a few gotchas), the driver crashes in WaitCapture.

I think there might be a bad interaction between the kernel and this closed source kernel.

Did someone tried the sharp camera package ?
Anyone succeeded in using the Camera on a SL-5600 and OZ3.5.1 ?

Thanks,
Brice

14

Angstrom & OpenZaurus / OZ3.5.1 Kernel question

« on: November 02, 2004, 02:22:48 pm »

There was a bug in 'opie-camera' that is fixed in the 'upgrades' feed. (This name changed, it is the alternate feed and contains fixes)

It seems I have the last version (opie-camera from feed and sharp-camera-support from upgrades).
Maybe I should build the package from oe as there might be a new version ?

15

Angstrom & OpenZaurus / OZ3.5.1 Kernel question

« on: November 02, 2004, 02:20:07 pm »

Basically just don't put an initrd.bin file (the filesystem) on the CF/SD card and proceed as normal with just the zImage.bin (kernel) and installer.sh.

After decoding and reading the OZ updater.sh, it seems that if you don't provide the initrd.bin file, your MTD root partition won't be erased.
I'll try that (but I'd prefer to find the ozone script first )