Thread: Diagnosing a reboot loop?
View Single Post
notnarb is offline notnarb
2010-05-11 , 09:09
Posts: 109 | Thanked: 56 times | Joined on Apr 2009
#4
Originally Posted by maacruz View Post
Check first the free space in the root partition, if it is full, that could be the cause.
Sadly, no, that's not the case

Syslog might show why it thinks it needs to reboot. If you don't have it installed you may be able to install it by booting the working version, chrooting into the reboot-looping one and installing it manually with apt-get (see http://maemo.org/development/tools/diablo/ for installation details). While you're in the chroot you may want to try uninstalling autoscan to see if it makes a difference.

See also http://wiki.maemo.org/Troubleshooting_boot_issues
As much as I hate asking these generic "help!!" questions with any sort of frequency, couldn't get any of that to work.

Autoscan is apparently not installed on my tablet (according to apt-get), trying to start syslog results in something along the lines of
Code:
hurp-derp /proc not mounted (success?)
and both of my linux installs don't want to connect via telnet (sporadic disconnections on my laptop - got to bash like.. once - what a tease, and the device is outright ignored on desktop's virtualized Fedora installation)

So a fix to any of those (or some other way to diagnose / fix this) would be swell

TLDR: Syslog's man page is confusing, how am I supposed to use it?