Re: Upgrade to PR 1.2 gone wrong
Alejandro López listas@googlemail.com writes: operation). When the moment for the reboot came, the problems started: my N900 would start booting never asking for the security code, and when starting to show the desktop, it would reboot; and the loop started again. It was impossible to power it off except by removing the battery. I had the same experience, with the reboot loop at the same point, after doing apt-get dist-upgrade (which I did because the app manager was telling me I needed to use the proprietary Windows Nokia software suite). I ended up flashing it, and restoring my settings/apps from backup, and it seems to be working fine now. -- -John Sullivan -http://wjsullivan.net -GPG Key: AE8600B6 ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Upgrade to PR 1.2 gone wrong
Hi, ext John Sullivan wrote: Alejandro López listas@googlemail.com writes: operation). When the moment for the reboot came, the problems started: my N900 would start booting never asking for the security code, and when starting to show the desktop, it would reboot; and the loop started again. It was impossible to power it off except by removing the battery. I had the same experience, with the reboot loop at the same point, after doing apt-get dist-upgrade (which I did because the app manager was telling me I needed to use the proprietary Windows Nokia software suite). Did you have any packages installed which stupidly declare exact version dependencies to other packages? For example several of the games in Extras seem to be declaring exact version dependency to SGX driver. Which of course causes a conflict on SSU which contains a new improved SGX driver. IMHO packages with exact version dependencies to anything that doesn't come from the same source package should just be rejected from Extras. Could somebody looking after Extras fix this so that we don't get such bad packages at least for PR1.2? I ended up flashing it, and restoring my settings/apps from backup, and it seems to be working fine now. - Eero ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Upgrade to PR 1.2 gone wrong
On Thursday 27 May 2010 08:24:30 Eero Tamminen wrote: IMHO packages with exact version dependencies to anything that doesn't come from the same source package should just be rejected from Extras. Possibly. It is certainly worth discussing, on the -developers list. Could somebody looking after Extras fix this so that we don't get such bad packages at least for PR1.2? In the meantime, as you understand what is going on, could you please log a bug report? Clearly the SSU needs to handle this case and not get into a reboot loop! Graham ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Upgrade to PR 1.2 gone wrong
Hi all, To be sure that upgrading to PR 1.2 was quite simple and avoid any possible issue, I waited 24 never-ending hours for the SSU. Today the upgrade package appeared in the application manager, so I made a backup and fully charged the battery in preparation for the installation. I installed the upgrade and it went horribly wrong. During the upgrade I happened to read a message that disappeared quite quickly stating that some operation had failed, but then the upgrade went on (nothing in this world would make me stop the operation). When the moment for the reboot came, the problems started: my N900 would start booting never asking for the security code, and when starting to show the desktop, it would reboot; and the loop started again. It was impossible to power it off except by removing the battery. So I decided to flash the image manually in the old-fashion way. After several USB problems (which disappeared when I blacklisted the cdc-phonet module in my PC - Thanks to the maemo wiki!), I succeeded to flash the device. Now all my applications and most of the configurations are gone, so I'm getting ready to restore the backup I did just before starting. I wonder what could have caused the initial upgrade to go that wrong. Any ideas? I have nothing modified in my device. Alejandro. ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
