4 ms·

In my experiece, upgrading the kernel to a newer one is not a problem. What can happen, though, is that an upgrade of userspace will suddenly require a kernel-f

by cnvogel 13y ago

In my experiece, upgrading the kernel to a newer one is not a problem. What can happen, though, is that an upgrade of userspace will suddenly require a kernel-feature not present, if you run an ancient board-support-package with a 3.0-kernel or so in 2014! (happened to me with a BSP for a Freescale i.MX6). So, if you have archlinux tracking the latest and greatest systemd, uptrading userland can make your machine no longer bring up everything (completely). But in my case the kernel is from 2011...

klaasvakie 13y ago
I have an i.MX5 BSP with a 2.6.xx era kernel :( Can you give an example of the "no longer bring up everything (completely)"?
- cnvogel 13y ago
  After putting a current arch-linux rootfs[1] on the box[2], it seems to come up, just network and console seems to be misconfigured, but this, I think, I had to fix the last time also. So: indeed the current systemd seems to work on a iMX6 running a 3.0 kernel. [1] ArchLinuxARM-imx6-latest.tar.gz from http://archlinuxarm.org/developers/downloads http://archlinuxarm.org/developers/downloads [2] Phytec PhyFlex i.MX6 http://www.phytec.de/de/produkte/system-on-modules/produktdetails/p/phyflex-imx-6-3.html http://www.phytec.de/de/produkte/system-on-modules/produktde...
  - cnvogel 13y ago
    ### addendum ### Recent systemd doesn't seem to realize that ethernet and the serial console device are actually there, it's waiting for dev-ttymxc3.device and sys-subsystem-net-devices-eth0.device ... but both are statically compiled in. So there is some issue with kernel 3.0.x.
    - cnvogel 13y ago
      I was missing one config option from the README, now it works!
zokier 13y ago
systemd README claims compatibility with 3.0 kernel: http://cgit.freedesktop.org/systemd/systemd/tree/README#n39 http://cgit.freedesktop.org/systemd/systemd/tree/README#n39
makomk 13y ago
Upgrading the kernel to a newer one isn't generally a problem, but the changes to cgroups that the systemd and kernel devs are planning to make in the future are not going to be backwards compatible with old userland code.

by cnvogel 13y ago

klaasvakie 13y ago

I have an i.MX5 BSP with a 2.6.xx era kernel :( Can you give an example of the "no longer bring up everything (completely)"?

cnvogel 13y ago
After putting a current arch-linux rootfs[1] on the box[2], it seems to come up, just network and console seems to be misconfigured, but this, I think, I had to fix the last time also. So: indeed the current systemd seems to work on a iMX6 running a 3.0 kernel. [1] ArchLinuxARM-imx6-latest.tar.gz from http://archlinuxarm.org/developers/downloads http://archlinuxarm.org/developers/downloads [2] Phytec PhyFlex i.MX6 http://www.phytec.de/de/produkte/system-on-modules/produktdetails/p/phyflex-imx-6-3.html http://www.phytec.de/de/produkte/system-on-modules/produktde...
- cnvogel 13y ago
  ### addendum ### Recent systemd doesn't seem to realize that ethernet and the serial console device are actually there, it's waiting for dev-ttymxc3.device and sys-subsystem-net-devices-eth0.device ... but both are statically compiled in. So there is some issue with kernel 3.0.x.
  - cnvogel 13y ago
    I was missing one config option from the README, now it works!

zokier 13y ago

systemd README claims compatibility with 3.0 kernel: http://cgit.freedesktop.org/systemd/systemd/tree/README#n39 http://cgit.freedesktop.org/systemd/systemd/tree/README#n39

makomk 13y ago

Upgrading the kernel to a newer one isn't generally a problem, but the changes to cgroups that the systemd and kernel devs are planning to make in the future are not going to be backwards compatible with old userland code.