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:
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!