Bug 11078

Summary:	does not boot on NUC
Product:	[Yocto Project Subprojects] IoT Reference OS Kit	Reporter:	Patrick Ohly <patrick.ohly>
Component:	intel-iot-refkit-platform-support	Assignee:	Mikko Ylinen <mikko.ylinen>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Medium	CC:	matti-pekka.sivosuo
Version:	unspecified
Target Milestone:	2.3 M3
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Patrick Ohly 2017-02-18 12:17:55 UTC

When trying recent IoT Refkit on a NUC, booting failed with "rootfs '' not found". Yes, the device name was empty. Debugging this further by editing meta/recipes-core/initrdscripts/initramfs-framework/init (because APPEND_append = " shell-debug init_fatal_sh" had no effect) showed that the reason was that /proc/cmdline was empty, i.e. the root=PARTUUID... was not passed to the kernel.

I've not been able to determine why that is. I suspected the RMC patch for systemd-boot, but reverting that in meta-intel didn't change anything.

I wanted to use the NUC for demoing Refkit at ELC, but I'm running out of time for that and probably will give up.

Comment 1 Mikko Ylinen 2017-02-19 14:59:19 UTC

This is unlikely RMC related because the stub patch only appends to the built-in cmdline.

Try commenting out the block that sets cmdline from LoadOptions (in stub.c).

Comment 2 Mikko Ylinen 2017-02-21 08:56:13 UTC

(In reply to comment #1)

> Try commenting out the block that sets cmdline from LoadOptions (in stub.c).

https://github.com/systemd/systemd/issues/4903

Comment 3 Mikko Ylinen 2017-02-28 15:30:54 UTC

Submitted to meta-intel:
https://lists.yoctoproject.org/pipermail/meta-intel/2017-February/004626.html

Comment 4 Mikko Ylinen 2017-03-30 10:59:57 UTC

The version of meta-intel with the fix is now integrated.