<div dir="ltr">On Mon, Jul 28, 2008 at 6:38 PM, casaubon <span dir="ltr"><<a href="mailto:jputhoff@wisc.edu">jputhoff@wisc.edu</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Hi, all.<br>
<br>
I went to pick up my FR to make a call earlier, and the screen locker<br>
responded *really, really* slowly. Desktop was equally slow in response. I<br>
powered down (gracefully, it seemed to me) using the power settings menu,<br>
but the device refuses to boot again (it can't get past the mokologo<br>
splash).</blockquote></div><br>I'm in a similar situation, though I haven't tried anything in u-boot. This happened when I opkg updated the system tonight from a 20080722 image (which appears to be the most recent available image on the buildhost). I've had this problem after updating both ASU and 2007.2 images. Also, I received the following error on each rootfs while opkg updating:<br>
<br>[snip]<br>Configuring kernel<br>update-alternatives: Linking //boot/uImage to uImage-2.6.24<br>Configuring kernel-2.6.24<br>Configuring kernel-image-2.6.24<br>Upgrading Kernel in Flash<br>DO NOT stop this process<br>Erasing 128 Kibyte @ 7e0000 -- 98 % complete.<br>
open input file: No such file or directory<br>[snip]<br><br>My guess is opkg isn't updating the kernel properly.<br><br>-- <br>Dylan<br><br>Type faster. Use Dvorak:<br><a href="http://dvzine.org">http://dvzine.org</a><br>
</div>