maemo.org - Talk - Diagnosing a reboot loop?

maemo.org - Talk (https://talk.maemo.org/index.php)

- OS2008 / Maemo 4 / Chinook - Diablo (https://talk.maemo.org/forumdisplay.php?f=29)

- - Diagnosing a reboot loop? (https://talk.maemo.org/showthread.php?t=52273)

Diagnosing a reboot loop?

After installing autoscan, my n810 has decided to enter a reboot loop. All hope is not lost because I have a dualboot setup, so I can log in to my now unmaintained maemo partition and possibly right whatever wrong I may have done.

Since my last reboot, I have updated fennec from yesterday's nightly build to today's, and installed autoscan (which asks that you reboot, which started this whole mess), and as far as I know, that's all. I installed autoscan by copying the deb from the above link, scp-ing it on to my n810, then running it from the file manager.

Possible other causes: installing the community SSU 2-3 reboots ago (this was either my first or second successful boot since installing the SSU - can't remember which).

So what can I do to get on the right track towards fixing this?

Re: Diagnosing a reboot loop?

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

Re: Diagnosing a reboot loop?

Check first the free space in the root partition, if it is full, that could be the cause.

Re: Diagnosing a reboot loop?

Quote:

Originally Posted by maacruz (Post 652316)

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

Quote:

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? :p