Hello Walt, Friday, January 4, 2008, 3:02:16 PM, you wrote:
> Will I never learn? > In four years experience with alternative Zaurus ROMs - as a user, not > a developer - I have never had "ipkg upgrade" work! Last night was no > exception. > My C3200 was flashed with the gpe image, 2007.11RC2.2. It has been > working well generally, but has been giving trouble with standby mode, > nothing consistent enough to do a bug report; sometimes the keyboards > are "dead" when it's asking for the password, sometimes the wi-fi > refuses to start up (even after eject/insert the card and ifup) and I > need to do a reset, so I decided once again to try "ipkg update" and > "ipkg upgrade". I actually went through the process three times, > until "ipkg upgrade" said there was nothing to do, and then re-booted. Well, such description doesn't help at all. ipkg has an option "-noaction" for dry-run mode. "ipkg upgrade" should always be performed with it first, the output should be reviewed carefully, "know your packages" is the motto - if it's true for desktop (well, especially for server) distros, why it should be different? It's not "ipkg upgrade" what breaks your install, it's specific package what does. Either way, let me guess, and be true, that kernel upgrade broke it. And this is going to continue until device maintainers won't part with their favorite sandboxes and won't come together to solve kernel upgrade problem consistently for all devices. > The first attempt, with "shutdown -r now" resulted in an unstoppable > (and unreadable) scrolling screen of messages, so I did a reset. > Now I am stuck at the login screen with unresponsive keyboards > (physical and on-screen). Before I give up and re-flash, is there any > way I can interrupt the boot process early so I can get logged in? > I'm not sure what that will gain me, except maybe another try at "ipkg > upgrade" but it's something to try. Walls of developers' sandboxes should have scribblings on that, along the lines that you should run new version's updater script but flash *only* kernel, or use rescue bootloader for that at all. Don't listen to me, I don't have Z, make sure you found those, ahem, instructions. > Any other suggestions are welcome, and if there are any files I can > submit to Bugzilla, tell me what to do! > Walt -- Best regards, Paul mailto:[EMAIL PROTECTED] _______________________________________________ Angstrom-distro-users mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
