OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: davidhewing 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:
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!
-
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.
and
- Enabling screen clicks or key clicks does not produce any sound on SL5600
are the same on SL5500 with GPE.
Does anyone know if there is a way to especially get the sync problem to work?
Thx!
Franky G
-
Update!
Flashing SL5500 with OZ 3.5.1's OPIE (yes, OPIE not GPE!) image file, sync and sound does work. Only hassle is that "Intellisync syncronises to /home/root/Application/ rather than /root/Application/" as described in OzReleaseNotes (http://www.openembedded.org/oe_wiki/index.php/OzReleaseNotes).
Copying PIM data files manually from "/home/root/Applications/" to "/root/Applications/" is a workaround, although this is pretty annoying for everyday use...
Frank
-
you can symlink /home/root/ to /root/ for sync working
-
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.
-
you can symlink /home/root/ to /root/ for sync working
Thanks Hrw, I guessed that
Frank
-
So is OZ 3.5.1 working on the 5600 or not? In the original post above, there is mention of the Socket Low Power WLAN (the same card I have) not working. But then right after that, the poster mentions that they can SSH.
I really want to know if OZ 3.5.1 will work on a 5600 with that same card (or ANY card for that matter). So far, I'm seeing conflicting/confusing reports. I've already tried it and I had that same problem with the interface not working and locking up the Z, so back to 3.3.6 for me for now. I want to know what I did wrong though; I REALLY liked 3.5.1. Please advise.
Stetson
-
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
-
I have no idea about that error - the same card works fine on 5500. I'm afraid you have to debug that one yourself, since the 5600 situation in the OZ team hasn't change - there is still no one who has one, so, testing is quite... uhm... limited
-
Can you direct us to some dummies guide for testing and cross compiling?
-
could someone post a link to how to set up the usb networking between windows and the zaurus. in particular the 5600
-
Hi guys. I just flashed OZ onto my 5600 for the first time tonight, and i'd have to say i'm pretty impressed. But i'm having the same USB issue as well. I set up usbd0 to use 192.168.129.201 and its running.
When i go to start/stop and go to advanced interface info, i see that its set for broadcast on 192.168.129.255, and i can actually ping that address. but i can't ssh to it or connect with samba
Does OZ even have a default smb server running? I'm a little new to the distro, but i like it a lot. My problem now is that i just can't ACCESS anything. Thanks!
PS: anyone know how to restore an old backup from a zauros rom to get back JUST my data? thanks
-
Does OZ even have a default smb server running?
No.
PS: anyone know how to restore an old backup from a zauros rom to get back JUST my data?
I think the backup file is a tar file, rename and extract.
but i can't ssh to it
It seems that dropbear is a bit fussy about its clients. Openssh and putty both work on windows for ssh, openssh works for scp (for file transfer), but putty doesn't. I think openssh works for all on Linux.
Si
-
ok,. but i couldn't ping it either. And i've read a bunch of posts about how others could not get usb working exactly correctly.
Does it not respond to ping?
i'm also having trouble with my cf card, is there no automount for that? if not is there a way to get that working? thanks, sorry for the basic questions, like i said, its my first flash
-
Ping should work.
What is your desktop machine running?
Si
-
I'm using Os X 10.3.5 and can talk to the zaurus fine with a Sharp Rom, including Zynergy and Default Sharp Rom
-
I'm having the same issue. I have a script that I setup when using the stock rom to connect, now I can't ping with oz 3.5.1. I would like to transfer stuff over to it, and add more packages, Is there anyway I can connect to it? I'm running gentoo with kernel 2.6.7
-
I had the issue until I flashed the kernel. I don't know how I missed it the first time, but make sure it is zImage and not zimage. Now I'm pinging scping and trying to get the thing setup the way I like.
-
thats EXACTLY what happened to me last night, it kept naming it zimage and i never got the new kernel. Once i fixed that, i wsa GOOOOD to go!! I've been going at it ever since. OZ ROCKS!
-
I think I said this someplace else too....
My sl5600 (pxa 250 - no noted cache probs when bug fix is off on other roms , thank you,) works really well with opie oz 3.5.1 (gpe too but the apps aren't there) EXCEPT that in opie I can use my wifi, but no cf memory devices. any cf flash or drive crashes and locks the Z. return from suspend with wifi also locks it. Help? This is way beyond me.
blink:
adf
-
Do you have the opie-wirelessapplet installed? Try removing it, reboot, and see if that improves things.
-
Mickeyl,
Are you saying that by removing that app, it could possibly fix the issue of the Z locking up?
Stetson
-
Yes, that would seem like an accurate interpretation of my message.