On Thursday 24 July 2008, Maarten Wisse wrote: > It went into suspend. But it did not return. Then, upon a hard reboot and > return to the environment I had created earlier, I did it again, and it > returned. > But after a couple of seconds, screen clicks do no longer respond and the > whole system becomes locked up.
:( > Unfortunately, after a hard reboot the log is lost because it is linked to > ram. I think you might be able to output the log to the serial port, that may allow you to see what is going on. > What might be the reason for this? I'm out of clues. Familiar had the same > problem. I'm doing nothing special, the device seems indeed to be a h2200 > (after hard reboot, the very first screen, with the HP thing on it and the > progress bar, has 1.10 at the bottom right corner). Interesting, I think perhaps you have a different bootloader to me. I presume you are not using LAB? It is strange that you got the same problem with Familiar as well. Cheers, Paul _______________________________________________ Angstrom-distro-users mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
