C860 USB Not detecting

[Bundabrg]

Hi All,

I've just bought myself a Sharp C860. Apart from the transformer deciding to fry itself (even with a universal adapter), I'm fairly excited to start playing around with this and finally retire my old Palm M500.

Things that may be relevant
OS is Windows XP SP 1
PDA is Zaurus SL-C860
I'm in Australia


My skill level
I'm fluent in Linux. I'm fluent in Windows. As an administrator, developer and user.

Short Description of Problem
My problem is that I simply cannot get the USB drivers to work.
Windows always says that it is an "Unknown Device".
Doing an "Update Driver", and browsing to the original Japanese CD \usbdriver\network, windows says that it "could not find a better match".

Longer Description
 - First thing I did whe I got this was install the C860 OpenZaurus from CF. No problems here.

 - Plugged in the Zaurus to USB port. It came up as unknown device.

 - Downloaded "qtopiadesktop-1.7.0.exe" and installed it.

 - Downloaded 5500v310U.zip, and ran "Pcsoft\setup.exe". Let it go all the way through. I pulled it the C860 off the usbport when it asked me to. Rebooted.

 - Plugged in PDA. It still comes up with Unknown Driver.

 - Brought up hardware manager->usb->unknown driver and selected "Update Driver". Gave it location on the original japanese CD of "usbdriver\network". It didn't like it (Couldn't find a better match apparently). Also tried the usbdriver with the 5500v310U.zip file, but I suspect this is different?

 - Totally uninstalled 5500v310U, qtopiadestop 1.7.0, and ran the slUninstall from the 5500v310U usbdriver folder a few times. Then only put back on 5500v310U, rebooted, and re-put back on the original japanese usbdriver. Same result.



I'm running out of ideas! I'm getting a CF Wireless card, but I still want to be able to sync over usb. I can't find any docs on the net for C760 or C860 that seem to address this problem.

 - Bundabrg

[Bundabrg]

After some playing around I finally got this working.

Fix was as follows: -

  - Power off the C860. I used Settings->Shutdown->Shutdown.

(This has the side effect that it suddenly was impossible to turn the device back on. I've heard that this is apparently a bug? When plugging in the USB cable in this 'shutdown' state, the windows box still came up with unknown device, so the pda was STILL on!)

  - Remove the battery. Wait till windows decides that it can no longer see it (The unknown device disappears).

  - Put battery in, and turn pda on. During boot, windows will suddenly find ... <gasp> a SL 7200 (or something like that, I forget exactly).

I had to do the above twice, before it got everything (IE, it detected some SL stuff, and then an Unknown Device, and redoing it, got it to detect everything).

Now I just need to figure out why the unit keeps resetting to 1970 on a restart.

Bundabrg

[omega]

The network drivers you need are somewhere on this website. search for c8x60  ... i think it's in the files sections, but there are definitely posts about this.

[Stubear]

You don't mention what ROM and version you are using on the C860.

The USB drivers you want are available here.

Make sure that the Zaurus is set to USB network mode using PC-link (qtsamba) on the setting tab.

I've had trouble with using extension cables with the Zaurus to connect to XP (no problem with linux and same cable however). If I don't use the origial cable byitself I can't get XP to recognise the zaurus - remove extensino cable and zaurus is recognised.

To force windows to use the new drivers remove them from Device Manager and also remove the .inf files from the hidden INF folder in windows/system32 (or it might just be in windows - sorry cant remember)

Then reboot and after windows starts up plug the Z in and power it on.

Note: If you try to change usb modes while the cable is plugged into the PC and the Z is powered on you will get an error message.

Stu

[Bundabrg]

Ok, further update: -

Keywords: C860 Cx60 C760 (Google really returns little about the C860)

ROM versions I've tried is both the OZ 3.3.5 and 3.3.6-pre1. (I was using 3.3.6-pre1 when I posted my first query).

In all instances, I have the following problem: -
  - Date always resets back to the beginning of the epoch (1/1/1970). This even when I manually issue a "date -s" AND issue a "hwclock -w". This also when I don't load opie and open a console before it starts. And even when I open the console and manually issue 'hwlock -s' it is 1970 (in fact, just issuing hwclock before a boot shows the correct hardware time, and doing straight after a boot shows the beginning of the epoch).

Not tested on 3.3.5, but done on 3.3.6-pre1, my original problem: -
  - If I drop to a console before opie starts (during that press enter else in 5 seconds opie starts phase), I can plug in my XP pc OR my linux laptop and both recognize the device.
  - If I plug it in after opie starts (OR unplug it and then plug it back in if I plugged it in during the 'safe' phase), then windows detects it as an unknown device, and my laptops usbnet comes up with a -110 error with usbnet, something about the card not accepting address 8, then not accepting address 9 etc...


Sooooooooo, flashed on the pdaXrom. Now date works, and network appears to work. Actually fairly impressed with running X11, through now its less PDA and more computer (I'm of two minds there, since it doesn't do some stuff nearly as well as Opie, but is now very extendible).

[Edit: Removed network corruption error report. Was actually the fact one feed used 'ar' and the other used 'tgz' format files... gah ]

In reply to: Stubear
 - Thanks for the USBDriver link. I'll try it out later.
 - With my original problem, even erasing the inf files (yes its the inf folder btw), AND doing a search for all sz* files and removing them still caused windows to auto-detect as an unknown device. One day I'll reinstall OZ and step through till I find the point it does this.



Anyway, its definately a nifty device and I'm now going to install Opie on top of the pdaXrom.

Bundabrg

[lareya]

You said:
Anyway, its definately a nifty device and I'm now going to install Opie on top of the pdaXrom.

Can you do that? Hmmm?    

Lareya

[lardman]

@lareya:

I'm now going to install Opie on top of the pdaXrom.

Can you do that? Hmmm?

I'm afraid not; not unless you recompile the Opie apps to use X11 rather than the framebuffer. I'm pretty sure this is possible, but not sure how to do it.

@Bundabrg:

In all instances, I have the following problem: -
- Date always resets back to the beginning of the epoch (1/1/1970). This even when I manually issue a "date -s" AND issue a "hwclock -w". This also when I don't load opie and open a console before it starts. And even when I open the console and manually issue 'hwlock -s' it is 1970 (in fact, just issuing hwclock before a boot shows the correct hardware time, and doing straight after a boot shows the beginning of the epoch).

This is a standard C machine problem (iirc). I assume that pdaXrom records the date and time before rebooting and then updates it after the reboot; obviously OZ doesn't do this (yet).

Not tested on 3.3.5, but done on 3.3.6-pre1, my original problem: -
- If I drop to a console before opie starts (during that press enter else in 5 seconds opie starts phase), I can plug in my XP pc OR my linux laptop and both recognize the device.
- If I plug it in after opie starts (OR unplug it and then plug it back in if I plugged it in during the 'safe' phase), then windows detects it as an unknown device, and my laptops usbnet comes up with a -110 error with usbnet, something about the card not accepting address 8, then not accepting address 9 etc...

Yes I've noticed this too. It's presumably a hotplug issue and can be solved quite easily by insmoding the net_fd.o module after Opie has re-started (and I assume a more permanent fix is to downgrade hotplug as it says in the readme?).


Si

[Bundabrg]

Lardman:

I'm afraid not; not unless you recompile the Opie apps to use X11 rather than the framebuffer. I'm pretty sure this is possible, but not sure how to do it.

Hmm, I've not looked closely at it yet, but wouldn't it be possible to still run it under the framebuffer. What I was thinking is to basically use the pdaXrom setup (IE, boot scripts, kernel etc..) and the opie software on top of that. I wasn't thinking of running this under X.

In essence I'm just creating an OZ but using the pdaXrom kernel and initrd images. I guess I'd remove X11 for space reasons.

Does Opie require the kernel to have a patch to support it? Or does it just use the normal framebuffer. If so I can't see why this wouldn't be a fairly trivial exercise.

However, if your other answers help me then it would be faster to start with OZ and fix it the other way.

Lardman:

This is a standard C machine problem (iirc). I assume that pdaXrom records the date and time before rebooting and then updates it after the reboot; obviously OZ doesn't do this (yet).

Does this mean there is NO hardware clock for these devices (or perhaps I should say no battery backed hardware clock?) If that is all that the problem is I'll write a script to save the time. I was thinking of doing this anyway, but I thought it was a workaround.

Lardman:

Yes I've noticed this too. It's presumably a hotplug issue and can be solved quite easily by insmoding the net_fd.o module after Opie has re-started (and I assume a more permanent fix is to downgrade hotplug as it says in the readme?).

Thanks for this. I'll try it out.

[lardman]

In essence I'm just creating an OZ but using the pdaXrom kernel and initrd images. I guess I'd remove X11 for space reasons.

I'd be tempted to go the other way, using the OZ base system and put X11 on top of it (or just using the OZ as is). OZ has a far better version of ipkg and a later version of libc to boot.


Si

[Bundabrg]

I'm inclined to agree. I've been having quite a few probs with pdaXrom's ipks and the various feeds, mainly to do with the shell vs binary versions and libc etc... I've seen your other posts so I know you've been through all that <g>.

Actually, I've settled on RC3 pdaXrom and am quite happy with it (Finally resolved the whole issue of whether to use as a PDA or PC replacement).
Anyway, this is all off topic.
Bundabrg

[shula]

i have the same problem on windows 98 SE.
tried all kinds of drivers,
complete uninstall, etc.
nothing. just "unknown device".
i can't and won't install 2nd os, since it's not my computer.

so i bought a SD card reader.  
it's not that convinient to transfer the sd here and there (and probably not that healthy either), but it works.


EDIT:
 i tried again:

since the last time i tried, i installed USB2 drivers (for my SD card reader), so *probably* they fixed up some of the win98-usb mess.

what i did today was:
erased all relevant registry entries: look for slz
erased all relevant files from all over the windows dir.
rebooted,
connected,
pointed the driver to the files (mentioned above by stubear)
temporarily neutralized the internal firewall (just in case)
and VOILA! at last.

FYI: i'm working with pscp (command line) and winSCP (gui) to transfer files, PuTTY as telnet+ssh client.