Generate Scarthgap genericx86-64 machine booting pcbios

Generate Scarthgap genericx86-64 machine booting pcbios

[Sebastian]

[-- Attachment #1: Type: text/plain, Size: 983 bytes --]

Hi community,

I've looked around how to get the example meta-yocto-bsp running on genericx86-64. By creating the default image it spits out the efi version which boots up quick and fine. In my target application I have to support the non efi world too. So I tried to switch by feeding the appended wks file to create the pcbios version:

part /boot --source bootimg-pcbios --ondisk sda --label msdos --active --align 1024 --use-uuid
part / --source rootfs --ondisk sda --fstype=ext4 --label platform --align 1024 --use-uuid
part swap --ondisk sda --size 44 --label swap1 --fstype=swap
bootloader --ptable gpt --timeout=5 --append="rootfstype=ext4 console=tty0"

Problem is: it stops by Kernel panic - not syncing: Invalid configuration from end user prevents continuing
Hardware name: Deault string Default string/Default string, BIOS 5.13 01/18/2024

Unfortunately there is not more I can read.

Can anyone explain me where I missed a step?

Regards,

Sebastian

[-- Attachment #2: Type: text/html, Size: 1467 bytes --]

Re: Generate Scarthgap genericx86-64 machine booting pcbios

[Sebastian]

[-- Attachment #1: Type: text/plain, Size: 451 bytes --]

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.

Regards,

Sebastian

[-- Attachment #2: Type: text/html, Size: 39090 bytes --]

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

[Paul Gortmaker]

[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.

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

[Alexander Kanavin]

TBH, I would try one of the MACHINEs in meta-intel. Genericx86-64
lacks many important pieces.

Alex

On Thu, 26 Jun 2025 at 10:06, Sebastian via lists.yoctoproject.org
<sebastian.krahl=lacon.de@lists.yoctoproject.org> wrote:
>
> I've tried the approach with the camera as there is no way of getting the serial port to the target. Also the footage is from my old PC as the VGA-Link from the target is to slow to display something useful on the screen. I'm testing with an USB-Stick as boot media but also tested via SATA drive so I would exclude a missing driver as a root cause.
>
> I hope somebody can find the relevant message in the boot log.
>
> Regards,
>
> Sebastian
>
> The following attachments were removed because the message exceeded 15MB. Attachments are automatically removed for messages larger than 15MB to ensure delivery.
>
> VID_20250626_093819466.mp4: https://lists.yoctoproject.org/g/poky/sattachment/3945602771410806765/254200256/0/78547d21db49a8a9eaa6d2d722eaac8ca2588636b026f89f9f5056ecc07132ea
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#13682): https://lists.yoctoproject.org/g/poky/message/13682
> Mute This Topic: https://lists.yoctoproject.org/mt/113825829/1686489
> Group Owner: poky+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/poky/unsub [alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>