[geekmaster]

Since charging my DX, I did a factory reset and reinstalled KUAL and stuff. It all worked. I did a hard reset because I was running my "newtrix" demo (one of my unpublished KUAL extensions) on it (very slow on DX) and I was impatient to do something else on my DX. On reboot, KUAL failed. I understand how rebooting gives a bad date until you set it or turn radio on, but why did trying to start KUAL before fixing the date cause a persistent timestamp error? I will try to get usbnet working without KUAL and fix it from there.

Which reminds me, I installed usbnet on a K3 (3G) yesterday, and tweaking it from KUAL, I can only telnet in (even resetting to default usbnet settings in KUAL). The K3 rejects all incoming SSH connections on USB. I also looked at the usbnet config and it looks sane. I am puzzled because SSH works on a K3 (wifi-only) that I installed on recently. Any hints so I can spendy time on pursuits other than fighting usbnet battles?

Problems like this make me feel like a noob...

EDIT: A difference is that this DX had wifi on long enough to get the dreaded "not a test kindle" document installed on it by amazon, and I had to reinstall MKK, so it is running the latest firmware, whereas the K3 is running whatever firmware version Kubrick put on it. If something new from amazon causes (some) kindles to go insane if you try to launch an app with a reset date (ca. 1970), perhaps we need a "force-sane-date" startup script, that sets the date to the newest of "current date / newest timestamp in /usr/var" or something...

EDIT2: Meh... nevermind. I just wimped out and did another factory reset. I will reinstall everything from scratch (again!). But this time I will remember that a factory reset enabled the radio, and I will turn it off BEFORE installing stuff (but after the date is correct). If this date problem bit me after a firmware update, it might bite others too, so maybe we do want a "force-sane-date" startup script as mentioned in my previous EDIT above. ;(