OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: dansawyer on October 15, 2004, 04:31:07 pm
-
All,
I am trying to use the Z camera on 3.5.1. The package has been upgraded to the pakcage in upgrades.
The install create the sharpzdc links in /etc/pcmcia.
The camera icon appears on the Opie screen.
The card manager recognized the camera.
The install creates a modue in a /lib/modues/2.4.6... dir.
Should this be in the .18 dir??
Attempts to run the camera result in a short icon flash in the status bar but nothing happens.
Help? Do I need to force load the module? Should it load by itself?
What am I missing??
Dan
-
Sounds like you are using packages from wrong feeds. Look below:
mickey@gandalf:/tmp$ wget http://openzaurus.org/official/unstable/3.5.1/upgrades/sharp-camera-support_2.4.18-rmk7-pxa3-embedix-r1_arm.ipk .
mickey@gandalf:/tmp$ ipkgfiles sharp-camera-support_2.4.18-rmk7-pxa3-embedix-r1_arm.ipk
drwxr-xr-x root/root     0 2004-10-11 17:25:51 ./
drwxr-xr-x root/root     0 2004-10-11 17:25:51 ./etc/
drwxr-xr-x root/root     0 2004-10-11 17:25:51 ./etc/pcmcia/
drwxr-xr-x root/root     0 2004-10-11 17:25:51 ./etc/pcmcia/cis/
-rw-r--r-- root/root     61 2004-10-11 17:25:51 ./etc/pcmcia/cis/CE-AG06.dat
-rw-r--r-- root/root    282 2004-10-11 17:25:51 ./etc/pcmcia/sharpzdc.conf
-rwxr-xr-x root/root    752 2004-10-11 17:25:51 ./etc/pcmcia/sharpzdc
drwxr-xr-x root/root     0 2004-10-11 17:25:51 ./lib/
drwxr-xr-x root/root     0 2004-10-11 17:25:51 ./lib/modules/
drwxr-xr-x root/root     0 2004-10-11 17:25:51 ./lib/modules/2.4.18-rmk7-pxa3-embedix/
drwxr-xr-x root/root     0 2004-10-11 17:25:51 ./lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia/
-rw-r--r-- root/root   26564 2004-10-11 17:25:51 ./lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia/sharpzdc_cs.o
-
Thanks,
Those files are all there. I have two pkgs installed
sharp-camera-support version 2.4.18... from the upgrade feed (the file sizes match)
opie-camera from the release feed (version 1.0.1-r0)
That is all I have done except to insert the camera. It shows up as an unidentified cf card.
Thanks,
Dan
-
update -
It now recognizes the camera; however it does not work.
Dan
-
I'm sorry, but I can't tell you more than that I got it to work a couple of days ago on a fresh install after installing sharp-camera-support and opie-camera and rebooting. I'm afraid I can't help when I can't reproduce problems
-
One more try:
Attempting to run camera from the command line produces the following:
camera: error while loading shared libraries: libcamera.so.1: cannot open shared object file: No such file or directory
Should trying to run camera force the module to automaticly load??
I will remove the packages and reload them.
Thanks,
Dan
-
That fixed it. It now works.
-
Just removing and reloading worked? I had about the same experience you did. I installed the same packages (this is on an SL5600). The card manager recognizes the camera card. 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
Windrose
-
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
-
I don't have a 5600. Perhaps the low level sharpzdc.o module is different on the 5600. Someone with a 5600 w/ SharpROM should diff the modules and if so, sent us the correct one to openzaurus-devel@lists.sf.net
-
Someone with a 5600 w/ SharpROM should diff the modules and if so, sent us the correct one to openzaurus-devel@lists.sf.net.
I have that stuff, be happy to do it for you, 'cept I don't know how. Could you step-by-step me, or is it too complicated? Want an email to do it off-forum?
W
-
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.
-
Perhaps the low level sharpzdc.o module is different on the 5600. Someone with a 5600 w/ SharpROM should diff the modules and if so, sent us the correct one to openzaurus-devel@lists.sf.net
Just to ensure that I'm on something like the same page, we are talking about a module named
/lib/modules/<something something something>/sharpzdc.o
and not
/lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia/sharpzdc_cs.o
right? They're two different things?
Windrose
-
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.
-
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.
-
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.
-
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 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 (http://externe.net/zaurus/forum/viewtopic.php?t=273&view=next)
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:
#define JFFS2_NATIVE_ENDIANby
#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).
-
Close to topic:
What is the best, most stable viewer on 3.5.1? I can create images but cannot view them.
Dan
-
opie-eye from the upgrades feed.