systemd issue preventing upgrade

[duckunix]

Hello, all. As discussed in #17 and #18, we cannot move to a newer version of systemd with the current kernel (3.4.0). And, now, I am hitting an error when trying to update my box:

don@pixie:~> uname -a
Linux pixie.home.duckland.org 3.4.0-ARCH #1 SMP Sun May 25 18:58:05 MDT 2014 armv7l GNU/Linux
don@pixie:~> sudo pacman -Suyy
:: Synchronizing package databases...
 core                            208.7 KiB   221K/s 00:01 [------------------------------] 100%
 extra                             2.3 MiB   805K/s 00:03 [------------------------------] 100%
 community                         2.8 MiB  1201K/s 00:02 [------------------------------] 100%
 alarm                            99.3 KiB  2.16M/s 00:00 [------------------------------] 100%
 aur                              62.7 KiB  2.04M/s 00:00 [------------------------------] 100%
 archlinuxfr                       6.6 KiB  0.00B/s 00:00 [------------------------------] 100%
:: Starting full system upgrade...
warning: systemd: ignoring package upgrade (212-3 => 222-1)
resolving dependencies...
looking for conflicting packages...

Packages (9) colord-1.2.9-3  gvfs-1.24.1-2  libgudev-230-1  libnm-glib-1.0.4-1
             libsystemd-222-1  networkmanager-1.0.4-1  systemd-sysvcompat-222-1
             udisks2-2.1.6-1  upower-0.99.3-1

Total Installed Size:  49.63 MiB
Net Upgrade Size:       1.39 MiB

:: Proceed with installation? [Y/n] y
(9/9) checking keys in keyring                            [------------------------------] 100%
(9/9) checking package integrity                          [------------------------------] 100%
(9/9) loading package files                               [------------------------------] 100%
(9/9) checking for file conflicts                         [------------------------------] 100%
error: failed to commit transaction (conflicting files)
libgudev: /usr/include/gudev-1.0/gudev/gudev.h exists in filesystem
libgudev: /usr/include/gudev-1.0/gudev/gudevclient.h exists in filesystem
libgudev: /usr/include/gudev-1.0/gudev/gudevdevice.h exists in filesystem
libgudev: /usr/include/gudev-1.0/gudev/gudevenumerator.h exists in filesystem
libgudev: /usr/include/gudev-1.0/gudev/gudevenums.h exists in filesystem
libgudev: /usr/include/gudev-1.0/gudev/gudevenumtypes.h exists in filesystem
libgudev: /usr/include/gudev-1.0/gudev/gudevtypes.h exists in filesystem
libgudev: /usr/lib/girepository-1.0/GUdev-1.0.typelib exists in filesystem
libgudev: /usr/lib/pkgconfig/gudev-1.0.pc exists in filesystem
libgudev: /usr/share/gir-1.0/GUdev-1.0.gir exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/GUdevClient.html exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/GUdevDevice.html exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/GUdevEnumerator.html exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/annotation-glossary.html exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/api-index-deprecated.html exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/api-index-full.html exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/gudev-hierarchy.html exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/gudev.devhelp2 exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/home.png exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/index.html exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/index.sgml exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/ix02.html exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/left-insensitive.png exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/left.png exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/ref-API.html exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/right-insensitive.png exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/right.png exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/style.css exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/up-insensitive.png exists in filesystem
libgudev: /usr/share/gtk-doc/html/gudev/up.png exists in filesystem
Errors occurred, no packages were upgraded.

Any thoughts on what to do next? Ideally, if there exists a newer kernel, I would love to go to that.

Thanks!

d

[wamserma]

Oh well, because of this I just updated to systemd 224-1 and after a reboot I just get black screen ... should have read before. Anyway: Is there a way to at least get a shell or sth to do the rollback?
I have installed to eMMC and I cannot boot brom USB as my chromebook tells me it is disabled when pressing Ctrl-U.
If I had an image of the eMMC I would not hesitate to reinstall ChromeOS, start the process all over again an then dd the image back, but because of #47 this is not the case.
So, any ideas of reviving the system?

[omgmog]

If you had SSH enabled you might be able to SSH in from another machine, other than that you've got no choice but to reinstall Chrome OS and start over.

The annoying thing is that right now the installer isn't working because ALARM no-longer seems to maintain the Exynos image that we were using. (#48)

If you do decide to reinstall, and want to try making the necessary modification to the script to use the ARMv7 image, feedback on that issue would be cool!

[wamserma]

SSH does not help without a network connection. Is there any way to revive the thing or at least access the eMMC? I have copies of most of the data, but there are a few longer text files that i'd love to recover before wiping the eMMC (I'd be willing to open the case for that if that helps).

For further reference: I got "org.freedesktop.systemd1 timed out" when entering reboot, so I did an reboot -f and now am stuck with the unusable system. Any key combination I could try to stop systemd from getting into action and drop to a minimal system, hoping to get a shell?

I read about the Exynos-Image being no longer available, but actually I gave the systemd-update a shot, being quite confident I could do a pacman -U to an older version if issues arise. Regarding this image: It also seems to have disappeared from any mirrors. Have you tried contacting the ALARM-Team directly? The must be an archive around somewhere. It could also still reside on an USB stick used to install ARM on the Chromebook...

[omgmog]

I think depending on ALARM as we are is going to just continue to be problematic, so in the long term I'd rather move towards building an image from scratch.

I'll ask on the forum anyway, though the mods are pretty unsupportive of installation methods by third-parties.

I realise this doesn't help you right now though...

[wamserma]

Well, in case I have to reinstall, that might help. But right now I am just looking for a way to get some files from my home before I wipe.

[omgmog]

@wamserma see my comment on #48, I think the "peach" image is the new name for the "chromebook" image, so if you need to reinstall you can modify the installer script to use that.

[wamserma]

Maybe will try that, but not until I know that my data is definitely lost...

Is there a way to edit the kernel boot-parameters at startup? Or some way to re-enable USB booting?

[omgmog]

You might be able to boot to u-boot (hold space while booting I think) and manually boot the USB stick, chroot in to the EMMC install and downgrade systemd.

But without a Chromebook at hand, and having not touched my Chromebook in a little while, I can't begin to explain how you would do that.

Here might be a good start: https://www.chromium.org/chromium-os/u-boot-porting-guide/using-nv-u-boot-on-the-samsung-arm-chromebook

[wamserma]

The problem ist you have to be real fast hitting space after pressing Ctrl+D and I have not yet managed this...