[systemd-devel] systemd fails to boot OLPC XO-1.5

[Gustavo Sverzut Barbieri]

On Sat, May 7, 2011 at 5:13 PM, Daniel Drake <dsd at laptop.org> wrote:
> Hi,
>
> Just built a Fedora rawhide-based image for the XO-1.5 laptop,
> including systemd v26.
>
> This is not "pure Fedora", it doesn't use the comps system/base
> groups, so may be missing important things. No plymouth or selinux,
> for example. We also use a custom kernel instead of Fedora's. So
> perhaps I'm asking for trouble from the start.

There is no problem with different setups, in Gentoo we allow
different use flags to cope with that. In your case, you better
disable some things like:

[    6.965615] <30>systemd[1]: systemd 26 running in system mode.
(+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; fedora)

likely you do not need AUDIT, SELINUX, SYSVINIT or LIBCRYPTSETUP?
Disable those at ./configure phase. (note: sysvinit is to
automatically start /etc/init.d scripts in legacy mode, if you have
control to convert all your scripts, disable that).

Then read the log, it already points you at errors:

     /etc/mtab is not a symlink or not pointing to /proc/self/mounts.
This is not supported anymore. Please make sure to replace this file
by a symlink to avoid incorrect or misleading mount(8) output.

Thus rm -f /etc/mtab; ln -s /proc/self/mounts /etc/mtab

     systemd[1]: systemd-readahead-collect[1014]: Failed to create
fanotify object: Function not implemented

compile your kernel with FANOTIFY if you wish to run readahead. Or
disable this service.

     Failed to initialize automounter: No such file or directory

This one is a big thing. Compile your kernel with autofs support. You
don't need any userspace program, but you need this in the kernel so
systemd works.

You better check you have the following set in your kernel config:
    CONFIG_AUTOFS4_FS=y
    CONFIG_CGROUPS=y
    CONFIG_DEVTMPFS=y

then try again.


> Either way, the system doesn't boot. It gets to the point where it
> starts udev (with various error messages along the way) and from that
> point things move very slowly, error by error.
>
> I captured full logs over serial console, you can view them here:
> http://dev.laptop.org/~dsd/20110507/systemd-boot.txt
>
> Is there anything obviously wrong with this setup? Where would you
> start on debugging this, and how? Happy to dive into the code.

lots of kernel stuff missing. Likely it's just about that :-)




-- 
Gustavo Sverzut Barbieri
http://profusion.mobi embedded systems
--------------------------------------
MSN: barbieri at gmail.com
Skype: gsbarbieri
Mobile: +55 (19) 9225-2202