Hello and thank you for any help in advance:
I am working with Yocto/poky for the first time. I am able to successfully
build the `core-image-base` for the `beaglebone` machine using the following
layers:
- meta-arm: origin/kirkstone (c39bb4ce3b60b73d35c5fb06af012432e70d6b38)
- "meta-arm-toolchain" layer
- "meta-arm" layer
- meta-ti: origin/kirkstone (7e1a048bc0f116842a6076cd284d80dc0eae01f8)
- "meta-ti-bsp" layer
- poky: origin/kirkstone (d6b8790370500b99ca11f0d8a05c39b661ab2ba6)
- "meta" layer
- "meta-poky" layer
I did not modify any layers, the layers have been added successfully to
BBLAYERS, and I am simply adding MACHINE ?= "beaglebone" and IMAGE_FSTYPES +=
"wic" to my local.conf.
However, after flashing (sudo dd if=$IMAGE of=$DEVICE status=progress
conv=fsync) the generated .wic image, there is a kernel panic due to invalid an
PARTUUID:
[ 5.458363] VFS: PARTUUID= is invalid.
[ 5.458363] Expected PARTUUID=<valid-uuid-id>[/PARTNROFF=%d]
[ 5.468094] Disabling rootwait; root= is invalid.
[ 5.473129] VFS: Cannot open root device "PARTUUID=" or unknown-block(0,0):
error -6
[ 5.481011] Please append a correct "root=" boot option; here are the
available partitions:
[ 5.489480] b300 3735552 mmcblk1
[ 5.489488] driver: mmcblk
[ 5.496351] b301 3731456 mmcblk1p1 d0be457f-01
[ 5.496356]
[ 5.503209] 0b3:00300 61798400 mmcblk0
[ 5.503215] driver: mmcblk
[ 5.510078] 0b3:00301 131072 mmcblk0p1 e9fc2e52-01
[ 5.510083]
[ 5.516943] 0b3:00302 267378 mmcblk0p2 e9fc2e52-02
[ 5.516948]
[ 5.523795] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
[ 5.532120] ---[ end Kernel panic - not syncing: VFS: Unable to mount root
fs on unknown-block(0,0) ]---
I see that the generated extlinux/extlinux.conf file sets
"root=PARTUUID=${uuid}". I thought this variable was to be replaced when
preparing the wic image, but I also validated that $uuid is unset in the u-boot
environment.
I am able to get around this issue if I hardcode my PARTUUID
(root=PARTUUID=<blkid PARTUUID of my root partition>) in the extlinux.conf.
This may be a naive question, but is this expected - is it standard practice to
set the correct root=PARTUUID=${uuid} after the extlinux.conf is generated? I
am assuming not, but I have not been able to find a workaround without patching
meta-ti/meta-ti-bsp/conf/machine/include/ti33x.inc (UBOOT_EXTLINUX_ROOT =
"root=/dev/mmcblk0p2") or hardcoding my PARTUUID.
Any direction is appreciated, and again, I thank you in advance for any
replies.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16879):
https://lists.yoctoproject.org/g/meta-ti/message/16879
Mute This Topic: https://lists.yoctoproject.org/mt/100830887/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
