Hi,

What you are describing there seems to be a manifestation of a known bug:
during the upgrade process, X itself is upgraded and the X server is
killed. But since the terminal runs on an X server too, it also gets
killed, preventing any further progress of the upgrade too.

See this page:
https://wiki.merproject.org/wiki/Nemo/Updating
The "known issues" and "updating via command like" chapters are what you're
looking for.

Cheers,
Timur


On Sat, Oct 27, 2012 at 4:18 PM, Chris Mailer <[email protected]>wrote:

> Hello,
>
> I played a bit more with the phone and eventually ssh'ed into the phone to
> check the log file for XDM.
> This is what is says:
> [   280.961] (EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device
> [   280.992] (EE) PreInit returned 8 for "TSC2005 touchscreen"
>
> Obviously, something is going wrong with the X-window configuration, but I
> couldn't find any .rpmsave or .rpmnew files which would explain this
> behavior, nor wasn't I able to find a solution through google.
> Since this behaviour is reproduceable (recent N900 meego relase on sd
> card, zypper refresh, zypper update) I hardly doubt I'm the only one
> running into trouble and I would really be happy if anyone could point me
> to a solution.
> Thanks,
>
>  Chris
>
>
>
> On Tue, Oct 23, 2012 at 8:29 PM, letters.random13 <
> [email protected]> wrote:
>
>> 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
>>>
>>>
>>>
>>
>

Reply via email to