Messages

1

Angstrom & OpenZaurus / collie and kernel from 3.5.3 upgrades

« on: July 06, 2005, 03:27:56 pm »

Does your Z still crash after running

Code: [Select]

/etc/init.d/hotplug stop
and connecting / disconnecting USB?

Yes, it still did (crash, that is), however manually unloading the networking modules including usbdcore (one test where I only unloaded the two modules depending on it, but not this module itself produced the usual crash after the next suspend) before removing the Z from the cradle seems to do the trick (but I could only repeat the test twice due to lack of time), thanks for the hint. And yes, after putting the Z back in the cradle, the USB connection works again even after suspend/resume.

Your description of the Akita problems actually pretty well matches what I saw on my Collie the past few days...

Dan

2

Angstrom & OpenZaurus / collie and kernel from 3.5.3 upgrades

« on: July 05, 2005, 01:22:05 pm »

2- flash Hentges rom, and again the suspend problem, but not so frecuently, and now the clock don't reset, but keeps the time where it freezes. I just don't understand. Is there a procedure or configuration to avoid the problem? (its just software I presume).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86992\"][{POST_SNAPBACK}][/a][/div]

I also still saw some freezes (or mostly loss of keyboard use, in which case however even shutdown doesn't work properly anymore, so it really is more than that) with the June 30 kernel and Hentges rom (stock OZ 3.5.3 opie image didn't boot for me as reported by numerous others).

They seem to be network related. After I changed the network settings to not bring usbd0 up automatically, I am no longer seeing freezes while the Zaurus (a 5500G, incidentally) is outside the cradle - have been using it as calendar and etext reader for the past 5 days without needing to reboot even once finally (well until an hour ago when I put it in the cradle for the first time since then).

Putting it in the cradle or removing it from there still causes the known problems, though (but I also notice that the network appearantly reacts to usb dis-/reconnects regardless of what network settings were chosen). Perhaps this info will help a kernel hacker pin down the problem (some kernel/system call not reacting properly to a sudden change of network component availability?)...

Dan