Reboot loop

[gostt]

I have been running into this issue since I got my 770 and was just curious if there was a common cause? The only software I installed was GAIM, the cpu status bar monitor, the weather applet and minimo.

Any ideas on what might be causing this? I eliminated additional software last night and it was working fine. Brought it into work this morning and it was stuck in a reboot loop when I powered on. I am currently reflashing it using the nokia software.

Is there anything I should avoid or be on the lookout for that might cause this issue?

[SeRi@lDiE]

I have been running into this issue since I got my 770 and was just curious if there was a common cause? The only software I installed was GAIM, the cpu status bar monitor, the weather applet and minimo.

Any ideas on what might be causing this? I eliminated additional software last night and it was working fine. Brought it into work this morning and it was stuck in a reboot loop when I powered on. I am currently reflashing it using the nokia software.

Is there anything I should avoid or be on the lookout for that might cause this issue?


The weather applet is your problem.
The wather applet is known to cause reboot loops.

Try OMWeather Instead.

[gostt]

Thanks SeRi@lDiE. It was pretty frustrating to think it was working and have it start looping on me again after a few hours. I'll take a look at OMWeather now.

[SeRi@lDiE]

I installed the weather applet a few month ago and it was doing the reboot loop....
I uninstalled it and it stop the reboot loop... Than looking for a update I found this note on the Maemo Weather Wip...


Serious bug: mweather home applet very often causes the desktop process to crash during boot time, causing a reboot loop. Every now and then it boots successfully. (FWIW I tried to cause successfull boots by e.g. plugging in the USB cable or by repeatedly pressing random hardware keys; I'm not sure if these had any effect). Booting until after the desktop crashes, then pluging in the charging cable, "powering off" (which actually just suspends the 770) and powering back on may caused the applet crash not to take down the whole desktop which will allow you to uninstall it.

[gostt]

I saw that note as well after you let me know about the problem. The loop wasn't happening consistently for me (I'd get several good boots before going into the loop) so I didn't suspect the weather applet and was uninstalling all sorts of apps instead.

Thanks again for the tip :)

[qole]

Any known applets / programs that can cause the reboot loop in OS2008?

My status bar makes it 80% of the way across before the blue light of death starts flashing and the tablet reboots.

Thankfully, the hosed OS2008 is on a MMC partition, so I can chroot into the bad OS and apt-get remove until I figure out what I did.

EDIT: Is there anything I can "apt-get install --reinstall" that will put my desktop settings back to "normal"?

[qole]

I found out what the problem was. Somehow my /usr/share/alsa/alsa.conf file got messed up; it was replaced with a script to run another application. I copied a "good" version back over the messed up one, and the desktop booted.

Sorry to bother you all.

[josiahg777]

Hey, guys, I'm really sorry for bringing up an old thread, but I've got the same problem as Qole...

My N810 won't boot from the mmc... the loading bar gets to about 60% then the blue light flashes and it dies back to the Nokia symbol and dumps me back in the bootmenu.

I can boot into the flash and I can chroot into the OS... So my question is then: How can I diagnose the problem and find out what to edit/delete/uninstall/whatever to save my OS partition?

Thanks in advance for any help :) Man, what a time for everything to go down the tubes :/

[qole]

For me, I had to think to myself, "what was I doing during my last session?" and then I looked at all of the files that I had modified. I found the problem in a very unlikely place, so look at all of the config files you edited, files you copied, etc.

[josiahg777]

Hmm... that's just the thing... I hadn't done anything... except remove the battery for a second, but I can't imagine that would hurt the device (the device was already off)

I had opened the process controller in the system panel but I hadn't disabled anything (to my knowledge) And that was the last thing I did prior to a shutdown... I had also installed Python again in an attempt to get rid of the stupid gconf error which is not going away (if anyone has info on that, I'd be very thankful as well :P and yes I did try installing youamp)

Hmm... when I chroot into my mmcOS I run the following:


$ root
# mount /dev/mmcblk0p2 /mnt/mmc22
# chroot /mnt/mmc22


However, I can't run any gui programs... Is there any way I can launch a gui program from this chroot? (this probably requires starting the sapwood/hildondesktop server huh?) or barring that is there a way to access the control panel through the command line?

Also, if it's helpful this is what I get when I run ls /etc/init.d/ :


af-base-apps
af-services
af-startup
alarmd
bluez-utils
brightness-permission
btcond
dbus
dnsmasq
dsp-init
esd
fb-progress.sh
fuse
glibc.sh
gpsdriver
hal
hildon-application-manager
hildon-desktop
hulda
icd2
ke-recv
libgpsbt
local.sh
maemo-launcher
mce
mediaplayer-daemon
metalayer-crawler0
minireboot
minishutdown
multimediad
myfile.txt
networking
obexsrv
osso-applet-display
osso-ipv6
osso-systemui
osso-systemui-early
product-code
python-launcher
rc
rcS
sbrshd
ssh
supllistenerd
tablet-browser-daemon
ttyusb0
wide-dhcpv6-client
wlancond
x-server
zzinitdone


Am I missing anything crucial here?

[josiahg777]

Okay, never mind, I'm an idiot!

touch /etc/no_lg_reboots worked :)

So now I can boot to it... now to figure out what I did to screw things up :P

EDIT: Okay, so I realized I had accidentally disabled "hal" :/ Wow, I'm kinda dumb sometimes :P My apologies for wasting people's time

Thank you qole for your help!

[qole]

Gotta love a thread that has lots of "Ok, I'm an idiot, sorry for wasting your time" ;-)

[fanoush]

$ root
# mount /dev/mmcblk0p2 /mnt/mmc22
# chroot /mnt/mmc22


However, I can't run any gui programs... Is there any way I can launch a gui program from this chroot? (this probably requires starting the sapwood/hildondesktop server huh?) or barring that is there a way to access the control panel through the command line?


You can run most stuff from chroot if you mount also /proc and /sys and /tmp with -o bind


$ root
# mount /dev/mmcblk0p2 /mnt/mmc22
# mount -n -t proc proc /mnt/mmc22/proc
# mount -n -t sysfs sysfs /mnt/mmc22/sys
# mount -n -o bind /mnt/initfs/tmp /mnt/mmc22/tmp
# chroot /mnt/mmc22

And maybe also other stuff, see 'grep mount /etc/init.d/rsS' for inspiration.

For more troubleshooting see also tips in http://www.internettablettalk.com/forums/showthread.php?t=16056

[qole]

I hear there's a fairly complete chroot script floating around that does a pretty good job of mounting all those things. Can't think of exactly what thread it's in, though. ;)

[sellier]

I am also suffering from a n810 endless reboot.

If I enable R&D mode and set no-lifeguard-reset it boots up into the full GUI.

I checked "Control Panel -> Services" and everything is checked.

Can anyone advise me on how to check whats crashing? /var/log is empty so I'm not sure where the crash logs are.

Thanks

[xandor]

I, too, have this plague (with my N800)!
I reflashed to Diablo, and after undoing Lifeguard, it booted after several attempts. Before the no LG, the bar would go across a third of the way, then reappear near the far end (weird) and hang!

I had to reboot after a couple of days due to the browser not launching due to "insufficient memory"(!)
Now it won't boot at all; typically the blue bar makes it across the bottom screen all the way, then the loop recurs after a total of 45 seconds.

I will reflash to 2007,(and reset no LG) but I still did experience looping under it as well (just not as persistently).

At this point I'm wondering if it's a h/w problem. I'm tempted to re-watch that video of an N800 being dismantled, and just going in and re-heating soldering joints in case there's a disturbed/cold one somewhere (I'm only half-joking here). It's out of warranty now, anyway. I wonder if there's such a thing as a "lower level" re-flashing (akin to earlier hard drives).

This device is providing no end of frustration! At the same time, I do like it when it's working!

[xandor]

(1/2 hour later):
Well, I reflashed back to OS 2007 with the no LF on the command line, and it actually booted up first try!
Perhaps Diablo is a little more...fussy?

Meanwhile, I'll see if I can get by for a good while without having to reboot.