|
Reboot loop / apt-get upgrade / 20 Jun 2006 firmware
Hi,
After a look to forum, I solve my mistral-beta problem and add new repository to my list, after this I application list give 1 update: ok, no problem. But "apt-get install ssh" show me 19 applications to upgrade, apt-get upgrade propose to begin with 17 applications, I said yes and after a 3mn of download my 770 shutdown ... Now I'm in infinite boot loop mode with about 30s time usable ... Since I have enough time to copy a script from mmc card and start it, I do a ps -ef > /media/mmc1/result.txt this is result: PID Uid VmSize Stat Command 1 root 484 S init [2] 2 root SWN [ksoftirqd/0] 3 root SW [watchdog/0] 4 root SW< [events/0] 5 root SW< [khelper] 6 root SW< [kthread] 22 root SW< [kblockd/0] 36 root SW< [omap_uwire] 42 root SW< [khubd] 93 root SW [pdflush] 94 root DW [pdflush] 96 root SW< [aio/0] 95 root SW [kswapd0] 171 root SW< [cqueue/0] 172 root SW< [kseriod] 205 root SW [mtdblockd] 239 root SW< [krfcommd] 248 root SW [mmcqd] 278 root 540 R < dsme -d -l syslog -v 4 -p /usr/lib/dsme/libst 283 root 540 S dsme -d -l syslog -v 4 -p /usr/lib/dsme/libst 284 root 540 S dsme -d -l syslog -v 4 -p /usr/lib/dsme/libst 285 root 312 S /usr/bin/bme 333 root DWN [jffs2_gcd_mtd4] 352 root 416 S < /sbin/udevd --daemon 565 nobody 652 S < /usr/sbin/dnsmasq -k -i lo -a 127.0.0.1 -z 579 messageb 1320 S < /usr/bin/dbus-daemon --system 584 root 1492 S < /sbin/mce 588 messageb 1468 D /usr/lib/gconf2/gconfd-2 594 root 3248 S < /usr/bin/Xomap -mouse /dev/input/mouse0 -mous 618 user 236 S < /usr/sbin/temp-reaper 621 user 1128 S < /usr/bin/dbus-daemon --session 625 user 2628 S < /usr/lib/sapwood/sapwood-server 629 user 2068 S < /usr/bin/matchbox-window-manager -theme defau 640 root 1112 S /usr/sbin/dsp_dld -p --disable-restart -c /li 659 root 1128 S < /usr/sbin/hcid -n 661 root 492 S < /usr/sbin/sdpd -n 690 root 1016 S < /usr/bin/bme-dbus-proxy -N 707 root 1364 S /usr/bin/osso_hss 712 root 632 S /usr/bin/esd 733 root 1220 S < /usr/bin/btcond -l 751 root 1500 S < /usr/sbin/ke-recv 757 root 1288 S < /usr/sbin/wlancond 760 nobody 1056 S < /usr/bin/btpin -l 763 root 1484 S < /usr/sbin/icd 784 user 2112 S /usr/libexec/dbus-vfs-daemon 786 user 1844 S < /usr/bin/maemo-launcher --daemon --quiet 804 user 2112 S /usr/libexec/dbus-vfs-daemon 805 user 2112 S /usr/libexec/dbus-vfs-daemon 838 user 356 S < /usr/bin/maemo_af_desktop 839 user 8748 S < /usr/bin/maemo_af_desktop 845 user 356 S < /usr/bin/osso-connectivity-ui-conndlgs 846 user 4072 S < /usr/bin/osso-connectivity-ui-conndlgs 849 user 356 S /usr/bin/hildon-input-method 851 user 7132 S /usr/bin/osso-xterm 854 user 6172 S /usr/bin/hildon-input-method 857 user 600 S < /usr/bin/clipboard-manager 861 root 1384 S /usr/bin/ias 888 systemui 5040 S < /usr/bin/systemui 889 user 612 S gnome-pty-helper 892 user 708 S sh 893 user 7132 S /usr/bin/osso-xterm 894 user 7132 S /usr/bin/osso-xterm 912 root 1740 S /usr/bin/osso_alarm 919 root 68 S /usr/bin/retutime -s 920 user Z < [osso-media-serv] 921 user 528 S /bin/sh ./t 922 user 620 R ps -ef Is'it some kill I can do to stop the expected shutdown ? or someone can send me a script I can start to see mode deeply what arrive ... without any information, I will flash back to original final 2006, but it's also time to see what arrive ... Any idea ??? Thank you, Laurent. |
Hi,
Someone can post his own "ps -ef" result from a fresh booted 770 that I can compare ? (from 30 Jun 2006) Thanks, Laurent. |
1 Attachment(s)
I had just the same problem i couple of days ago...
I just reflashed the latest firmware to solve the problem. Thats the price to pay sometimes when living on the bleeding edge. :) |
Quote:
Thank you for your list, but that didn't help me, But I have very very big problem with reflash I didn't expect, solution was: export USB_DEVFS_PATH=/dev/bus/usb I see solution http://l3x.net/imwiki/Wiki.jsp?page=Main I will a make a post with better explanation. Good day, Laurent. |
I had this problem yesterday.
I believe it is the maemo-launcher update that causes the problem, mainly because it cannot upgrade properly (as the table reboots when it senses maemo-launcher not running). flash your 770 like so: $./flasher-2.0 --set-rd-flags=no-lifeguard-reset That will keep the 770 from rebooting when something critical has crashed or has been shut down for an upgrade. You can then use --clear-rd-flags=no-lifeguard-reset to put it back to normal, but I havent at this time. |
Now I have more information and I can reproduce my crash/reboot :(
- I flash with 30 June - add repository maemo-hackers.org/apt mistral main (to install xterm) - install xterm - activate R&D mode (to modify /usr/bin/gainroot) - disable R&D mode - add some repository - apt-get update - apt-get upgrade upgrade propose 14 update: I said Yes, system crash with libtelepathy install. this my repository list I copy from some post: (I don't remeber where) TAKE CARE OR YOU WILL CRASH YOUR SYSTEM, YOU HAVE BEEN WARNED !!! deb http://repository.maemo.org/contrib/ mistral free non-free deb http://repository.maemo.org/ mistral free non-free deb http://only.mawhrin.net/fbreader/maemo/ mistral user deb http://www.kernelconcepts.de/~fuchs/nokia770/ex_2006/ ./ deb http://www.mulliner.org/nokia770/repository/ maemo2 free deb http://maemo.org.br/platform/apt/ python python deb http://zeus.rm-fr.net/~skyhusker/maemo/ mistral user deb http://www.oakcourt.dyndns.org/maemo/ ./ Thank you for your tips hallgreng, I will make a new try with it and see if I can have libtelepathy version asap, Laurent. |
Please post me the output of
$dpkg -l | grep telepathy my output from a working tablet is as follows: Code:
# dpkg -l | grep telepathyI am beginning to wonder if I should apt-get from the command line at all any more. I am a hardcore Debian user, so I prefer to use apt command-line tools to do updates, but I have run into problems with maemo-launcher before, apparently libtelepathy (that was in the list of upgraded packages prior to my problems yesterday), and I needed to enable development flags in the firmware to fix them. I am not against doing heavy lifting, but the 770 is one of those devices that I like to "just work" and not have to fool around with it to do something. |
Next ...
This is my libtelepathy version before I try to upgrade:
Code:
home/user # dpkg -l | grep telepathyCode:
# apt-get updateCode:
/home/user # apt-get updateThis is update downloaded: Get:12 http://repository.maemo.org mistral/free libtelepathy 0.0.14-0osso1maemo1 [20.8kB] and still crash :( :( :( But reboot looks stable :) and telepathy is updated to: Code:
iiU libtelepathy 0.0.14-0osso1maemo1 Telepathy client libraryFinal: Code:
/ # apt-get upgradeNow system looks good now :) but I can't go out from R&D --set-rd-flags=no-lifeguard-reset mode cause reboot loop arrive :( :( :( hallgreng: did you test to go out from R&D to see what appends ? Cause it's not just an install point problem, it's stability system problem now I guess ... time for a bug report ? Good day, Laurent. |
Looks like your situation was the same as mine, I had apt asking about maemo-launcher during upgrade, though I opted to keep the original config file.
I did not disable R&D mode nor have i cleared the no-lifeguard-reset flag. I may do that tomorrow if necessary to test. I looked through dmesg and around the end of bootup and this is all that looks interesting: Code:
~ $ dmesg | grep -A 11 36.660and the DMA timeout. Does anyone have any knowledge of these two things? Due to the nature of the device, logs are sparce. dmesg is the best I can think of to gather information in this case... |
same issue here
I did the exact same steps.. got stuck in the reboot loop once I'd installed (and forced the rest of the install to finish). Popped the battery, rd mode to no lifeguard, and the reboot cycle goes away.. and returns again if I take out of R&D/no lifeguard.
I don't know if it's a symptom of R&D mode ( my understanding is that it doesn't cause any performace differences), or maybe I'm just imagining things.. but the overall system suddenly feels speedier since doing this minor upgrade. |
Well, I noticed today that I cannot play video or audio files any more, so I suppose the problem lies with the aic23 powering up and down.
I think that tomorrow I am going to go ahead and flash the official 2006 root directory onto my 770 and avoid using apt on the command line to upgrade... |
ditto on dead music/video
Quote:
I did the upgrade on telepathy and such as posted in the prior messages. This, of course, required using apt-get and fixing the install a few times (as other people noted). And now that I've mounted remote windows shares, I've noticed audio and video no longer works for me, either. I even did a 'shutdown -r now', and attempted to play a local audio/video before even making a network connection. Always get "unable to perform operation. try again". I'm wondering what exactly "broke" in updating those libraries. |
Quote:
Same for me, it's really annoying since i use my time to constantly repair my toy. That mean we can't use this device properly. That really sux ... |
Same things for me: no way to play Discovery internal video,
this is my dmesg | grep aic Code:
[ 22.237487] aic23 powering updmesg Code:
ialized vram=1048576 pixclock 21940 kHz hfreq 24.9 kHz vfreq 51.0 Hz- I flash back to original 30 June 2006, - install xterm with maemo-hackers.org/apt mistral main repository, - update manually libtelepathy only with dpkg -i ./libtelepathy_0.0.14-0osso1maemo1_armel.deb Now internal Discovery video is ok, reboot is stable without R&D, still powering up / powering down with aic like quoted in beginning, (dunno if it's important ...) result: libtelepathy alone is not the problem :( Good day, Laurent. |
Quote:
fresh flash: only install xterm, dmesg | grep aic Code:
[ 26.793823] aic23 powering upDo you know how to clear "no-lifeguard-reset flag" ? => go out from R&D: 770 reboot loop, go back to R&D: still reboot no-lifeguard-reset flag set: no reboot loop => I expect that to clear this flag: going out from R&D is enough ... but I don't find an express was to do this. Good day, Laurent. |
aic23 or something else?
I've noticed the powerup/down messages a lot in dmesg, even before I noticed a problem with the video / audio. And, that makes me wonder something else.. perhaps the audio/video was broken before this update. Maybe installing Gizmo managed to break it.
I know this is the price we pay for playing on the edge, but I dread the thought of reflashing at this point, and having to reinstall all the apps, all over again. I was cruising through dmesg -l output, and couldn't help but wonder if maybe something in the gstreamer* is what's been borked, even if -C doesn't report anything broken. |
Quote:
$./flasher-2.0 --clear-rd-flags=no-lifeguard-reset I think that today I will spend some time updating my personal 'make dirs, symlinks, and file edits the way i like them after a fresh install'-script and then flash back the official 06 root dir. Like BigBob said, this is really hurting my ability to use this device. On the bright side, at least it is easy to go back to a working state! =] |
Quote:
I've play several times to know which package cause the problem, After lots of test I see that: Nokia 770 in normal mode, fresh flash, only xterm, disable R&D, clear no-lifeguard-reset flag, dpkg -i gst-plugins-farsight_0.10.1-0osso2maemo1_armel.deb goes to reboot loop ... ok: I reinstall like before, go to 14 packages folders, remove gst-plugins and do a "dpkg -i *.deb" unexpected reboot, but looks stable after this, do it another time "dpkg -i *.deb" to finish previous install, no reboot, another dpkg -i *.deb" and ... reboot ! no logic for me ... But after reboot: no loop mode, great I think ... I go to gst-plugin to install it: dpkg request libstd :eek: (do you remember ? not supposed to be installed ???) ok ... but dpkg libstd request libgcc (supposely installed !) and to finish dpkg -i libgcc request to install gcc-3.4 :confused: After this 3 updates, I test to see result with reboot ... reboot loop mode come back :eek: (remember: without gst-plugins) ARGHHH ... it'enough for me ... I understood nothing :mad: :mad: :mad: I stop playing, my 770 is ok me like that ! Bad day :mad: Laurent. |
I have this same problem, would like a solution.
Two weeks ago I ssh'd into my 770 and did apt-get upgrade
After everything upgraded, I got a reboot loop. I asked on #maemo and disable the lifeguard reboot I didn't know that was the problem so I reflashed OS2006 today and did apt-get upgrade again... The moral of this story is, apt-get on the command line is not supported by Nokia. Sadly, I don't have time to reflash and reinstall everything again today. |
odd
I find this mostly baffling.
I understand how the application manager can do its own apt without killing stuff (just not showing these destructive packages and installing updates individually), but I dont understand WHY there are destructive packages in the stable repo! |
Just a guess here as I'm a Fedora guy. Maybe use update instead of upgrade.
In Fedora, yum update will check all installed apps for their latest stable version. yum upgrade, will upgrade your system to the next version like Core 4 to Core 5 or Core 5 to Core 6. Probably not what you intended. |
Because NOBODY is supposed to gain root permissions. Period. You need to use one a variety of hacks or exploits or R&D modes to do this, and it's simply assumed you know what you're doing at that point.
The primary problem is that attempting to upgrade a running application framework will fail, destroying the existing one, preventing any sort of bootup. In order to avoid this, it's necessary to use a serial console or apt-get over a non-running framework, such as updating one stored on an mmc chroot-ed in from one running on flash. It's not NOT showing destructive packages, it's ONLY showing packages explicitly vetted for end-user use. |
One of the packages with an upgrade in the repo (which is really designed for the SDK) is maemo-af-launcher. The lifeguard process on the device forces a reboot if this is killed.
It certainly needs a bit more sanity checking in its actions. |
Still, the problem is that even if you upgrade maemo-launcher via ssh with the lifeguard reboot turned off, once you disable developer mode and re-enable the lifeguard reset, the tablet is in a reboot loop again.
I googled to find the list of applications that were watchdogged by dsme, but I could not figure out what is prompting dsme to do the reboot. I think I'll just give up on this and switch back to the OS2006 and install applications only via the appmanager. |
SSH and RD-mode required to solve problem
I got my 770 rebooting always when I tried to install new programs. It's because dpkg tried to reconfigure maemo-launcher -program. If you try to install anything, package-management software will restart maemo-launcher service. And it will always reboot your 770 unless you are on R&D and no-lifeguard-reset -mode.
I had sshd running on my 770 (can't install it if your 770 is already on bad phase) beforehand. Then I changed mode: Code:
$ ./flasher-2.0 --enable-rd-mode --set-rd-flags=no-lifeguard-resetCode:
# dpkg --reconfigure -aFinally apt-get started maemo-launcher again but graphical UI didn't show up. So I run reboot -command. Finally it's time to disable RD mode: Code:
$ ./flasher-2.0 --disable-rd-mode --clear-rd-flags=no-lifeguard-resetBR, HenriP |
Re: Reboot loop / apr-get upgrade / 20 Jun 2006 firmware
@Tobler: your post was precious - I was kept in a similar reboot loop with a borked apt - after updating a number of packages with apt-get. Entering R&D mode and disabling lifeguard allowed me to recover apt.
|
| All times are GMT. The time now is 10:53. |
vBulletin® Version 3.8.8