Re: [poky] Generate Scarthgap genericx86-64 machine booting pcbios

[Paul Gortmaker <paulg@kernel.org>]

[Re: [poky] Generate Scarthgap genericx86-64 machine booting pcbios] On 25/06/2025 (Wed 22:58) Sebastian via lists.yoctoproject.org wrote:

> After a suggestion from Paul I was not able to scroll through the boot log on
> the target machine.
>  
> But then I moved to virtualbox. In the virtual environment the system comes up
> with no issue. Except:
> Output is from /var/log/dmesg and blkid....
>  
> Why it is booting in vbox I don't know but why are the labels that different? I
> try to change the UUID in the syslinux.cfg and give it a try but it does not
> change anything.

If you can't get a serial port on your target that allows you to capture
and scroll the boot log, you can just film the boot on your phone and
review it there.  Yeah I know it is rather klunky, but hopefully you'll
only be doing it once.  Then you can compare real hardware with
virtualbox and see how partition detection and boot args differ.

Paul.
--

> Regards,
>  
> Sebastian

>> That message is basically telling you that whatever partition you
>> specified in your boot args to the kernel - like "root=/dev/sda1" or
>> whatever, does not exist in the list of partitions discovered by the
>> kernel at boot.   So you'll need to scroll up earlier in your boot log
>> and look what *was* discovered and what *was* in the bootargs, and figure
>> out the discrepancy.
>> 
>> For the record, the "Invalid configuration..." part of that message is a
>> Yocto addition, because the default message of "not syncing" doesn't mean
>> much of anything to people who aren't using Linux on a regular basis.