Getting Crazy With Os X / Sl5500 In Usb-cradle!

[elwood151]

I nearly got everything working to sync my Zaurus SL-5500 (Sharp ROM 3.13 + Cacko Kernel Patch) with my Apple PowerBook G4 12", but there is one annoying problem:

When I put the PowerBook and/or the Zaurus to sleep, I'm not able to reestablish the USB/TCP-IP connection afterwards - no more ping in any direction!

The PowerBook is running OS 10.3.9, the Cradle is connected to one of the internal USB-ports (no hub!). The PowerBook is connected to my DSL-WLAN-router via Airport.

The PB has IP 192.168.129.1, the Z has *.201

If I try to shut down Airport and plug out/in the Z again, but it doesn't change anything,
the system log says and there is no pinging possible:


AirPort:  Link DOWN
org_lucidcake_driver_AJZaurusUSB:        0        1 Enumerating configurations ...
org_lucidcake_driver_AJZaurusUSB:        0        0   Config found
org_lucidcake_driver_AJZaurusUSB:        0        0     Interface found
org_lucidcake_driver_AJZaurusUSB:        9        4       bLength, bDescriptorType
org_lucidcake_driver_AJZaurusUSB:        0        0       bInterfaceNumber, bAlternateSetting
org_lucidcake_driver_AJZaurusUSB:        0        0       bNumEndpoints
org_lucidcake_driver_AJZaurusUSB:        2        6       bInterfaceClass, bInterfaceSubClass
org_lucidcake_driver_AJZaurusUSB:        0        5       bInterfaceProtocol, iInterface
org_lucidcake_driver_AJZaurusUSB:        1        0     Interface found
org_lucidcake_driver_AJZaurusUSB:        9        4       bLength, bDescriptorType
org_lucidcake_driver_AJZaurusUSB:        1        0       bInterfaceNumber, bAlternateSetting
org_lucidcake_driver_AJZaurusUSB:        0        0       bNumEndpoints
org_lucidcake_driver_AJZaurusUSB:        a        0       bInterfaceClass, bInterfaceSubClass
org_lucidcake_driver_AJZaurusUSB:        0        6       bInterfaceProtocol, iInterface
org_lucidcake_driver_AJZaurusUSB:        2        0     Interface found
org_lucidcake_driver_AJZaurusUSB:        9        4       bLength, bDescriptorType
org_lucidcake_driver_AJZaurusUSB:        1        1       bInterfaceNumber, bAlternateSetting
org_lucidcake_driver_AJZaurusUSB:        2        0       bNumEndpoints
org_lucidcake_driver_AJZaurusUSB:        a        0       bInterfaceClass, bInterfaceSubClass
org_lucidcake_driver_AJZaurusUSB:        0        7       bInterfaceProtocol, iInterface
org_lucidcake_driver_AJZaurusUSB:        2        6 org_lucidcake_driver_AJZaurusUSB::initDevice - Interface class and sub class
       0        0 AppleUSBCDCECMControl: probe - provider doesn't want us to match
       0        0 AppleUSBCDCECMData: probe - provider doesn't want us to match
       0        0 AppleUSBCDCWMCData: probe - provider doesn't want us to match
       0        0 AppleUSBCDCACMData: probe - provider doesn't want us to match
org_lucidcake_driver_AJZaurusUSB:        0        0 org_lucidcake_driver_AJZaurusUSB::createNetworkInterface - attachInterface failed
org_lucidcake_driver_AJZaurusUSB:        0        0 org_lucidcake_driver_AJZaurusUSB::configureDevice - createNetworkInterface failed
org_lucidcake_driver_AJZaurusUSB:        0        0 org_lucidcake_driver_AJZaurusUSB::start - failed
       0        0 AppleUSBCDCECMControl: probe - provider doesn't want us to match
       0        0 AppleUSBCDCECMData: probe - provider doesn't want us to match
       0        0 AppleUSBCDCWMCData: probe - provider doesn't want us to match
       0        0 AppleUSBCDCACMData: probe - provider doesn't want us to match


After a restart of the PowerBook, it works again (till the next sleep phase), but this is not really fun, because at (nearly) each shutdown/restart/logoff of the PowerBook a Kernel Panic occurs, which seems to be caused by problems with Apple's internal USB drivers.. :-(
I contacted Andreas, the author of the Z-USB-driver, but so far he didn't find a solution for the Kernel-Panic-problem.  

Can anyone tell me how to reactivate the USB/TCP-IP connection after sleep without restarting the Powerbook?
Any terminal hack is welcome!

Best regards

Martin

[dhns]

When I put the PowerBook and/or the Zaurus to sleep, I'm not able to reestablish the USB/TCP-IP connection afterwards - no more ping in any direction!

fun, because at (nearly) each shutdown/restart/logoff of the PowerBook a Kernel Panic occurs, which seems to be caused by problems with Apple's internal USB drivers.. :-(

Similar issues are known but I did not have them such severe (except when 10.3.5 was introduced - see below). Usually, I just need to switch off the Zaurus for one or two seconds and switch on again and the connections resume.

Every 10 attempts it still hangs and then, the trick with Airport off/on works.

Every 100 or so, it does not resume (and the driver name changes to "nil" in the network settings) and needs the Powerbook to reboot.

There was a real driver conflict with MacOS X 10.3.5 which was solved by the 0.28 driver. This resulted in a kernel panic.

I have nevers had installed 10.3.9 so I don't know if there is a new conflict.

And finally, although I have compiled myself a 0.30 version (http://www.dsitri.de/wiki.php?page=AJZaurusUSB) on Tiger&Xcode there have been reports that the 0.28 driver also works on Tiger.

So, I think your 10.3.9 system has a special conflict resulting in that kernel panic.

Regarding the hanging itself, I have had discussions with Andreas and it is probably a "feature rather than a bug". The outgoing packet queue is being stalled if the USB interface goes down because the Z sleeps. And depending on what is going on (e.g. ping or ssh), the outgoing queue fills up to its limit. This stalls the sending process (ping). And there seems to be no wakeup mechanism that detects that the Z is awaking.

I have some ideas how to improve the driver on that and will do that in the next days.

-- hns

[elwood151]

Hi hns,

thanks for your "just in time" answer.

I would be glad if those driver problems could be solved - I don't plan to switch to OS 10.4 right now, so I will need to get along with 10.3.9 and my Z.

Would it make sense to install Version 0.3 with OS 10.3.9 or is it sure that this won't work?

Best regards

Martin

[lpetroni]

I nearly got everything working to sync my Zaurus SL-5500 (Sharp ROM 3.13 + Cacko Kernel Patch) with my Apple PowerBook G4 12", but there is one annoying problem:

When I put the PowerBook and/or the Zaurus to sleep, I'm not able to reestablish the USB/TCP-IP connection afterwards - no more ping in any direction!

The PowerBook is running OS 10.3.9, the Cradle is connected to one of the internal USB-ports (no hub!). The PowerBook is connected to my DSL-WLAN-router via Airport.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=83914\"][{POST_SNAPBACK}][/a][/div]

Hi Martin,

I've the same configuration as you but I've not connected my Z to my PowerBook yet. I'm waiting the arrival of a card reader that I bought to be able to  flash the newer Sharp ROM v3.13). I believe I will do the flash procedure this week.

I will follow this thread and post my results here too.

lpetroni

[dhns]

Would it make sense to install Version 0.3 with OS 10.3.9 or is it sure that this won't work?

Unfortunately, it is sure it does not work on 10.3.x
It needs an additional kernel library that is only available on 10.4.

So, what you could try to do is to go back to 10.3.8 (which might be a lot of work - install 10.3.5 or whatever you have on CD and then manually upgrade...) or try to reinstall the driver.

By the way, things will become worse for x86 based Macs next year - kernel extensions are not compatible and can not be translated by Rosetta. So the driver will have to be split into two different versions --- next year which is plenty of time!

-- hns

[freizugheit]

I am currently an SL-5600 Zaurus user.

Whenever I have connection problem with my Mac, I reinitialize the network conneciton by activating the PC Link utilities, selecting "USB-IO  (Debault) " option undder Connection and quitting  the application.

Actiavte the PC Link utilities one more time, select "USB-TCP/IP(Advanced)" option undder Connection and quit the application.

I hope the above will help.

[elwood151]

I am currently an SL-5600 Zaurus user.

Whenever I have connection problem with my Mac, I reinitialize the network conneciton by activating the PC Link utilities, selecting "USB-IO  (Debault) " option undder Connection and quitting  the application.

Actiavte the PC Link utilities one more time, select "USB-TCP/IP(Advanced)" option undder Connection and quit the application.

I hope the above will help.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=84004\"][{POST_SNAPBACK}][/a][/div]

Hi freizugheit,

thanks for your hint - unfortunately it doesn't work for me.

It only changes the behaviour of the Zaurus from absolutely no reaction while pinging it to:

ping: sendto: Host is down
ping: wrote 192.168.129.201 64 chars, ret=-1

:-(

Martin

[dhns]

ping: sendto: Host is down
ping: wrote 192.168.129.201 64 chars, ret=-1

The host down means that the routing is no longer active (and there is no alternative path). Usually, if I switch on Airport it times out - if not the host down comes.

Did you try to switch off the Z for approx. 2 seconds and switch on again - while being in the cradle? This might reset the USB controller of the Z. Plugging and replugging the Z is not the same procedure.

And one more hint: you can encounter the strange situation that an existing ping or ssh in a Terminal window hangs - while a newly opened window where you issue a new ping or ssh works. And the latter even might "restart" the previously hanging other ping and ssh commands.

-- hns

[elwood151]

ping: sendto: Host is down
ping: wrote 192.168.129.201 64 chars, ret=-1

The host down means that the routing is no longer active (and there is no alternative path). Usually, if I switch on Airport it times out - if not the host down comes.

Did you try to switch off the Z for approx. 2 seconds and switch on again - while being in the cradle? This might reset the USB controller of the Z. Plugging and replugging the Z is not the same procedure.
-- hns
[div align=\"right\"][a href=\"index.php?act=findpost&pid=84169\"][{POST_SNAPBACK}][/a][/div]

Dear hns,

thanks for your hints - unfortunately, none of them does help. :-(

That's what I did:

I came home, woke up the PowerBook from its sleep, put the Z in the cradle, turned the Z on.

I hear some harddisk spinning on the PowerBook, but no reaction concerning the TCP/IP connection (en2 "inaktiv").

I switched off the Z, waited some seconds, switched it on again.
No reaction.

I switched Airport off, tried the same procedure (Z off/wait/on) - no success. :-(

Neither opening another terminal window for pinging nor even quitting the terminal app and reopening it made it possible to ping the Z. :-(

Any other ideas?

Best regards

Martin

[dhns]

I hear some harddisk spinning on the PowerBook, but no reaction concerning the TCP/IP connection (en2 "inaktiv").

I switched off the Z, waited some seconds, switched it on again.
No reaction.

I switched Airport off, tried the same procedure (Z off/wait/on) - no success. :-(

Hm,
does the console log say anything at that instant of time?

-- hns

[elwood151]

Hm,
does the console log say anything at that instant of time?

-- hns
[div align=\"right\"][a href=\"index.php?act=findpost&pid=84569\"][{POST_SNAPBACK}][/a][/div]

no.

[dhns]

Hm,
does the console log say anything at that instant of time?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=84569\"][{POST_SNAPBACK}][/a][/div]

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

Hm,
that is really strange since the driver should say that it becomes initialized.
Just an idea: could be the cable broken or a bad contact in the cradle?
Another idea: do you have any other USB drivers/devices installed - where one might conflict?

-- hns

[elwood151]

Hm,
that is really strange since the driver should say that it becomes initialized.
Just an idea: could be the cable broken or a bad contact in the cradle?
Another idea: do you have any other USB drivers/devices installed - where one might conflict?

-- hns
[div align=\"right\"][a href=\"index.php?act=findpost&pid=84630\"][{POST_SNAPBACK}][/a][/div]

Hi hns,

yeah, strange it is.
the cable could be broken, but my Zaurus is nearly new and I did not use it often yet.
However (at least I believe it is like that and I'll try it out), when I do not touch the Z at all and restart the PowerBook, the connection works again, so in my opinion at contact problem can't be the reason, but I'll try it out.

Concerning conflicting USB drivers:
I'm using the following USB components:
- mouse Logitech Notebook mouse optical plus+
  -> Logitech Control Center installed
- scanner Canon LiDE 30 (driver installed)
- USB stick/ Yedata USB floppy drive
  -> no extra driver necessary

I could try to create a new user, copy the network prefs from my account and leave out all those drivers (if they are not installed in the System Library, which I fear might be the case..)

Would there be any other way to have a look at the USB "action" while plugging in?

Best regards

Martin

[elwood151]

Just an idea: could be the cable broken or a bad contact in the cradle?

I don't think so.
1) I just plugged the cradle USB connector in the PB and switched on the Z.
The PB has its IP *.129.1 assigned, but no ping possible.

2) I restarted the PowerBook (without touching the Z, the cable, the cradle or anything),
OS X crashes (like each time when I restart),
et voilà: I can ping the Z again, no problem, as long as nobody goes to sleep or is disconnected....

Martin

[dhns]

Would there be any other way to have a look at the USB "action" while plugging in?

One is to open the Console and look for messages in other logs: console.log and system.log

Another idea: after rebooting after the kernel panic, there should be a panic.log stored as /Library/Logs/panic.log It should describe what caused the kernel panic - and if it is really related to the Zaurus driver.

And one more idea:
Start the System Profiler. Open the USB infos. There should be an entry for your Zaurus (in one of the USB bus entries - there is one for each port). It should appear/disappear when you plug/unplug the Zaurus and press Apple-R (refresh). This is sort of an USB diagnosis (independent of the AJZaurusUSB driver).

-- hns