i have regularly had the same problems: a direct install works (mostly...now...), but an update (i use console, zypper refresh; zypper update) may or may not complete successfully, but subsequent reboot mostly never succeeds; no clear indication why not. latest failed update attempt was with nemo-handset-armv7hl-n900-0.20120920.1.NEMO.2012-10-07.1-mmcblk0p.raw.bz2 (initial install works ok). i don't think those console msgs are directly related, but i haven't tried to recover dmesg to see what happened. to minimize frustration, i just do a clean install of a recent release; then select updates sparingly, if at all.
On Sun, Oct 21, 2012 at 9:12 PM, Chris Mailer <[email protected] > wrote: > Hello, I installed the Nemo October release on my N900 SDcard). > Booting via uboot works fine after installation. Once the device came > up, I noticed Nemo was really slow, even after reboot. I therefore > decided to check for updates, and after refreshing cache there were > 237 updates applicable. > I run the update until it said "finished". > I noticed most of the icons had changed, but the programs wouldn't > start any longer - and I decided to reboot the Phone. However, the > Phone seems to hang after reboot now, with messages like: "hci_h4p FW > error" and i2c omap controller timed out". > While I cut mount the Fat32 part of the MMC in Maemo that did but work > for the ext4-part. The Fat32 part looks ok, though. > Do I need to install the power kernel, or what can I do to resurrect > my Nemo-release? > Thank you in advance, > Chris > > >
