> > Richard Pickler wrote: > > The second time, I was installing some packages I built myself, and it > > crashed, which I could not recover from. (this one I'll take the blame > > for). > > Why should you take the blame? This is a consumer oriented device and > software installation is promoted as a user feature - it should not brick > the device, period! Heh, well, I'm building some of my own packages (raw file utilities) and was working on getting vpn setup and really messed up the installation of some things. At some point in the near future, I have some software projects I want to work on for this device, and I'm just starting the process of getting some low level things I want to build off of. What actually happened though - did the device end up in a reboot loop? The reboot loop described in that bug is exactly what I'm running into. It never makes it to the progress bar running across the bottom of the screen, which I assume to mean it is running through the init.d scripts. You may need to provide more details, but quite a few people are > experiencing reboot loops for no apparent reason, check > https://maemo.org/bugzilla/show_bug.cgi?id=999 for more details. Unfortunately, I can't really provide any more details as I'm usually installing things and setting up other things, etc. Any one thing that I do could be the culprit. I usually don't notice it has crashed for a day or two after I've done something to the device. My gut instinct is telling me that there's a bug in the jffs file system they're using (it is jffs right?). Seeing how it can come from many different programs, I'm curious if it's just corrupting the file system somewhere which then makes the thing unbootable. This is just armchair developer speculation. Rich -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.maemo.org/pipermail/maemo-users/attachments/20070212/709d850f/attachment.htm
