Kernel Panic with 10.3.5 and AJZaurusUSB 0.2.5

[dhns]

Hi all,
I have experienced that the USB connection through AJZaurusUSB 0.2.5 is no longer working on my TiBook after upgrading to MacOS X 10.3.5, the security fix and iSync 1.5 yesterday.

The symptoms are:
* Zaurus (SL5500G) connectivity is broken as soon as Updater is installed and Mac is not rebooted
* after Reboot I coud no longer contact the Zaurus (neither ping, nor ssh, nor SMB)
* after looking at the Network system prefs I got the message that there is a new Ethernet interface that must be configured
* after configuring (assigning in an IP address) and activating there is still no connectivity
!! when taking the Zaurus from the docking station I get a Kernel Panic (the first after one year!)
!! this is systematic even during reboot. As soon as the boot progress window says that the IP services are running, unplugging the Zaurus crashes the kernel

I have informed the Author of AJZaurusUSB. I will also take a look myself into the sources and the kernel panic log if I can find anything.

Did anybody else observe the same issues?

-- hns

[Chaos]

Just upgraded to 10.3.5 last night. I'll try it later today...

[dhns]

So, I was able to narrow it down a little more.

1. deinstalling AJZaurusUSB => still panic
2. reboot => still panic
3. deinstall en2, en3 through Network settings => NO PANIC!
4. plug in the Zaurus again => Network Settings has a popup that a new interface en2 is found => no panic!
5. configure the new interface with a manual IP address => AGAIN PANIC!

My current working Hypothesis:
Apple has brought with one of the updates of last week something similar to AJZaurusUSB - an Ethernet over USB bridge. And it is not prepared to work with the Zaurus.

So, the issue is NOT AJZaurusUSB but some (new) driver by Apple (part of iSync for the Palm?). If this turns out to be true, I think we should all push Apple to officially support he Zaurus and fix the bug asap.

So the next steps (tomorrow) will be
1. check which module becomes loaded/active (kextstat) when plugging in the Zaurus
2. look into the latest Software Update receipts to find which one has installed which .kext

-- hns

[Chaos]

So the next steps (tomorrow) will be
1. check which module becomes loaded/active (kextstat) when plugging in the Zaurus
2. look into the latest Software Update receipts to fins which one has installed which .kext

And of course once we have this figured out, why not just trash (or move out of the way) the module and work from there? Theoretically removing one module shouldn't bring OSX crashing down... And if you don't have a Palm or anything, it shouldn't be a big deal.