Messages

1

Sharp ROMs / Watapon ROM

« on: March 25, 2005, 10:28:36 am »

I found that kopi needs to have another package to get the Sharp DTM to work.  The executable that it tries to use is called "db2file", but I couldn't find it anywhere on the net.  I did however find that there is a package called "zdbat" that you can install and then rename zdbat as db2file and the calendar sync then works.

You can get zdbat from:

http://tbox.jpn.org/wiki/linuzau/wiki.cgi?zdbat

This appears to be web page from Japan, but there are download links near to bottom.  Alternatively, you can do a google search for zdbat.

Once you install the package, you'll need to get a shell on the Zaurus, cd to /home/QtPalmtop/bin, and run "ln -s zdbat db2file".

I still haven't figured out how to get anything other than the Calendar sync'ed with Windows and Outlook yet.

Of course now you have to sync with the PC and then you have to tell KO/PI to sync with DTM.  Too bad we couldn't get back to a one step process.  At the moment, the greatly improved KO/PI interface over the builtin calendar justifies the extra work...

   -David

Thanks Chaos for all your work on this ROM! 

I have installed 1.6 but am having trouble syncing with the KDE PIM.  From the PC everything looks great, and the sync seems to work, says items are sent,  but on the Zaurus, nothing shows up in Ko/Pi or or KA/Pi.  I try to use the sync to Sharp DTM in Ko/Pi, but that seems to do nothing.

Am I doing something wrong?  Anyone else having the same results?

Thanks!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=71479\"][{POST_SNAPBACK}][/a][/div]

2

Angstrom & OpenZaurus / TEW-222CF locks OZ 3.5.1

« on: September 27, 2004, 09:50:37 am »

I hadn't though of that.  I think there might be problems though.  The version of the wireless exentions in the Sharp modules is pretty old, and I think they use a different set of libraries too.  The original modules for the socket cards wouldn't let you use any of the wirless sniffers.  Next time I flash my 5600 with OZ 3.5.1 I'll give that a try and see what happens just in case.

    -David

3

Angstrom & OpenZaurus / OZ 3.5.1, 5600 Socket CF WLAN and Sync

« on: September 27, 2004, 09:43:08 am »

SSH works through the USB advanced networking option once the usb0 interface is configured with a static IP address on the 5600.   The Wireless card definately does not work out of the "box" so to speak.  Sync'ing with Intellisync on Windows doesn't seem to work either.   Those are the major issues that I have found.  The OS itself does appear to work, unfortunately for me the wireless card issue and the sync'ing issue are two things that I need to work before I can switch over myself.

   -David

4

Angstrom & OpenZaurus / TEW-222CF locks OZ 3.5.1

« on: September 24, 2004, 01:04:22 pm »

Just wanted to add that this seems to be a very simular problem documented in a thread I created:

https://www.oesf.org/forums/inde...?showtopic=7037

It's a different card, but it still uses the hermes and orinico modules.   When I try to start up networking on the card, I get the same lockup.

I made several pleas, but I haven't gotten any useful or helpful responses.   Unfortunately, there doesn't appear to be any developers on the OE/OZ project has an SL-5600 to test these things out with.  The fact that it boots up and runs at all it is amazing testomony to their skills.

My next steps are to see if I can get one of my home Linux system setup to do the OE build and then focus on those kernel modules.   I have modules from 2.4.18 that works with my wireless card as well as the source, so I'm hoping that a source code comparision will turn up where the fault is.

   -David

5

Angstrom & OpenZaurus / OZ 3.5.1, 5600 Socket CF WLAN and Sync

« on: September 21, 2004, 10:31:14 pm »

Sorry, forgot to mention in the original post that that all these issues are with SL5600's OPIE image.  When I started the GPE image was not available (and may still not be available - I haven't checked).  It sounds like the OPIE image for the SL5500 has some major differences with the SL5600.

I may have to try to download the OE buildsystem and see what I can tell from that.  Are there any current developer's out there that might be able to answer the question about the differences between the OPIE images?  Thanks.

6

Angstrom & OpenZaurus / OZ 3.5.1, 5600 Socket CF WLAN and Sync

« on: September 21, 2004, 12:33:06 pm »

Hello all,

First off I wanted to thank the OZ team for their continuing work on support the Zaurus even after Sharp seems to have let the PDA just slide.  

I've been playing with OZ 3.5.1 on the SL5600 for a couple of hours and I've found a couple of issues.  These may not be unique to the SL5600, but since this is the only model that I have, I can't verify if it effects any of the other models.

First, I have a Socket LowPower CF WLAN card that uses the spectrum_cs, orinoco, and ther hermes modules.  While this card has worked on the Sharp ROM perfectly fine, it fails with the following messages:

Code: [Select]

orinoco.c 0.13e (David Gibson and others)
spectrum_cs.c 0.4.2 (Pavel Roskin and others)
hermes @ IO 0xf6000000: hermes_read_ltv(): rid  (0xfd20) does not match type (0x0021)
hermes @ IO 0xf6000000: Truncating LTV record from 129544 to 8 bytes. (rid=0xfd20, len=0xfd05)
eth0: Station identity 0002:0001:2259:6b4a
eth0: Looks like a Lucent/Agere firmware version 8793.27466
eth0: Ad-hoc demo mode supported
eth0: IEEE standard IBSS ad-hoc mode supported
eth0: WEP supported, 104-bit key
hermes @ IO 0xf6000000: hermes_read_ltv(): rid  (0xfc01) does not match type (0x3c00)
hermes @ IO 0xf6000000: Truncating LTV record from 129030 to 6 bytes. (rid=0xfc01, len=0xfc04)
eth0: MAC address F2:D3:01:00:59:22
hermes @ IO 0xf6000000: hermes_read_ltv(): rid  (0xfc0e) does not match type (0x7200)
hermes @ IO 0xf6000000: Truncating LTV record from 129058 to 34 bytes. (rid=0xfc0e, len=0xfc12)
eth0: Station name "m  I"
hermes @ IO 0xf6000000: hermes_read_ltv(): rid  (0xfd10) does not match type (0x72ff)
hermes @ IO 0xf6000000: Truncating LTV record from 129538 to 2 bytes. (rid=0xfd10, len=0xfd02)
hermes @ IO 0xf6000000: hermes_read_ltv(): rid  (0xfc06) does not match type (0x72ff)
hermes @ IO 0xf6000000: Truncating LTV record from 129022 to 2 bytes. (rid=0xfc06, len=0xfc00)
hermes @ IO 0xf6000000: hermes_read_ltv(): rid  (0xfc83) does not match type (0x722b)
hermes @ IO 0xf6000000: Truncating LTV record from 129026 to 2 bytes. (rid=0xfc83, len=0xfc02)
hermes @ IO 0xf6000000: hermes_read_ltv(): rid  (0xfc25) does not match type (0x722b)
hermes @ IO 0xf6000000: Truncating LTV record from 129022 to 2 bytes. (rid=0xfc25, len=0xfc00)
hermes @ IO 0xf6000000: hermes_read_ltv(): rid  (0xfc0c) does not match type (0x7264)
hermes @ IO 0xf6000000: Truncating LTV record from 129026 to 2 bytes. (rid=0xfc0c, len=0xfc02)
hermes @ IO 0xf6000000: hermes_read_ltv(): rid  (0xfc0d) does not match type (0x7264)
hermes @ IO 0xf6000000: Truncating LTV record from 129026 to 2 bytes. (rid=0xfc0d, len=0xfc02)
eth0: ready
eth0: index 0x01: Vcc 3.3, irq 39, io 0xf6000000-0xf6000047
The overall effect is that while a "eth0" device seems to get created, it is not functional at all.  Any attempt to configure the wireless settings causes the Sl5600 to lockup hard -- not even a kernel panic message.

I was hopping that someone might recognize these messages and know if there is some module configuration option to resolve this issue.


I've also noted simular bugs others have already seen on the SL5600.  One in particular that isn't good is that the Intellisync does not work between Windows and OZ3.5.1.  This is even after setting up the USB network configuration correctly in Windows (XP) and on the Zaurus.  I'm able to successfully SSH to the Zaurus and confirm that network connectivity is not the problem.   When ever the the Intellisync software is run, it cannot connect.   I've tried the Qtopia desktop as well and it cannot connect either.

Does anyone know what the connection method is for the syncing software?  The last I knew, I thought that the Sharp ROM did a samba share to the /root/Application or /home/root/Application directories to make the sync work with the PC.  I've been looking at the configuration on the SL5600 and I can't find anything that provides a network share of any kind.

Those are the two major issues with OZ 3.5.1 that I have found so far.  There are a couple of little issues:

 - Enabling screen clicks or key clicks does not produce any sound on SL5600
 - Last graphic line of the display does not appear to drawn properly
 - The Document Tab does not seem to actually do anything

Anyhow, I'll probably have switch back to the Kompany ROM image while I wait to see if anyone has any suggestions.  I will also happily reinstall OZ 3.5.1 or something new to try any suggested fixes to help out the OZ team.  

Thanks again all!