News for hackers. Stuff that matters.
Re:Boycott systemd by klaasvakie on Thursday April 24, 2014 @07:11AM (#7639412)
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)"?

Re:Boycott systemd by cnvogel on Thursday April 24, 2014 @07:38AM (#7639540)
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

[2] Phytec PhyFlex i.MX6 http://www.phytec.de/de/produkte/system-on-modules/produktde...

Re:Boycott systemd by cnvogel on Thursday April 24, 2014 @09:47AM (#7640219)
### 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.

Re:Boycott systemd by cnvogel on Friday April 25, 2014 @04:06PM (#7648744)
I was missing one config option from the README, now it works!