[Buildroot] Problems with generating an x86 Image

[Buildroot] Problems with generating an x86 Image

[Lukas Hecht]

Hi there,

i'm having problems with generating an x86 image for an industrial pc
based on an AMD Embedded G-Series APU which runs perfectly fine using
Ubuntu.

Here's what i did, using Buildroot 2020.02.10:


make pc_x86_64_bios_defconfig

make menuconfig changes:

Filesystem Image: 250M size

iso image

initial ram filesystem

Networking applications - wireless-regdb (to get rid of an regdb error
while booting)

make


dd disk.img to USB drive, and then copy bzImage to /boot on the USB drive.

Boot my target system with clonezilla to console, and then dd the usb
drive to /dev/sda


When i reboot and remove the usb drive, grub starts and selects
"buildroot" after 5 seconds, and then the boot starts but i don't get to
the console. It stops with:


Welcome to Buildroot

buildroot login: scsi 0:0:0:0: Direct-Access Generic Ultra HS-COMBO 1.98
PQ: 0 ANSI : 0

sd 0:0:0:0 [sda] Attached SCSI removable disk

random: fast init done

random: crng init done (coming up after some minutes)


And there it just stops, with a blinking cursor. Can anyone point me to
what i am doing wrong?

If not, is there an easy way to access and save the console output that
comes up before these last lines to get a better understanding of what
is happening?

Thanks a lot!

Lukas

[Buildroot] Problems with generating an x86 Image

[Thomas De Schampheleire]

Hello,


El mi?, 3 mar 2021 a las 16:48, Lukas Hecht (<mixolydisch@gmx.de>) escribi?:
>
> Hi there,
>
> i'm having problems with generating an x86 image for an industrial pc
> based on an AMD Embedded G-Series APU which runs perfectly fine using
> Ubuntu.
>
> Here's what i did, using Buildroot 2020.02.10:
>
>
> make pc_x86_64_bios_defconfig
>
> make menuconfig changes:
>
> Filesystem Image: 250M size
>
> iso image
>
> initial ram filesystem
>
> Networking applications - wireless-regdb (to get rid of an regdb error
> while booting)
>
> make
>
>
> dd disk.img to USB drive, and then copy bzImage to /boot on the USB drive.
>
> Boot my target system with clonezilla to console, and then dd the usb
> drive to /dev/sda
>
>
> When i reboot and remove the usb drive, grub starts and selects
> "buildroot" after 5 seconds, and then the boot starts but i don't get to
> the console. It stops with:
>
>
> Welcome to Buildroot
>
> buildroot login: scsi 0:0:0:0: Direct-Access Generic Ultra HS-COMBO 1.98
> PQ: 0 ANSI : 0
>
> sd 0:0:0:0 [sda] Attached SCSI removable disk
>
> random: fast init done
>
> random: crng init done (coming up after some minutes)
>
>
> And there it just stops, with a blinking cursor. Can anyone point me to
> what i am doing wrong?
>
> If not, is there an easy way to access and save the console output that
> comes up before these last lines to get a better understanding of what
> is happening?

While I don't have experience specifically with using Buildroot for PC
images, this symptom gives me the impression that the 'getty', which
is supposed to give you a login prompt, is not going to the terminal
you are looking at.

Based on the boot output, do you agree that the system 'seems' booted,
but you are just missing the login prompt?

Have a look at /etc/inittab , based on the defconfig you started from,
the getty is supposed to be assigned to 'tty1'.
Did you change anything in this regard?
Do you have something specific on this hardware with respect to tty /
serial line?

Best regards,
Thomas

[Buildroot] Problems with generating an x86 Image

[Lukas Hecht]

Hi Thomas,

maybe this idea could lead in the right direction. The process takes
about 12 seconds from leaving grub till stopping to boot, which sounds
about right to me for such a basic system.

I did not change anything on the getty, etc/inittab shows:
tty1::respawn:/sbin/getty -L tty1 0 vt100 # GENERIC_SERIAL

My hardware has three serial ports but i don't know any more details
about these at the moment.

Is there an easy way (like with booting a live ubuntu) to find out if
tty1 is the right one?

Thanks a lot,
Lukas


Am 03.03.2021 um 16:56 schrieb Thomas De Schampheleire:
> While I don't have experience specifically with using Buildroot for PC
> images, this symptom gives me the impression that the 'getty', which
> is supposed to give you a login prompt, is not going to the terminal
> you are looking at.
>
> Based on the boot output, do you agree that the system 'seems' booted,
> but you are just missing the login prompt?
>
> Have a look at /etc/inittab , based on the defconfig you started from,
> the getty is supposed to be assigned to 'tty1'.
> Did you change anything in this regard?
> Do you have something specific on this hardware with respect to tty /
> serial line?
>
> Best regards,
> Thomas

[Buildroot] Problems with generating an x86 Image

[Thomas De Schampheleire]

Hi Lukas,

On Wed, Mar 3, 2021, 17:16 Lukas Hecht <mixolydisch@gmx.de> wrote:

> Hi Thomas,
>
> maybe this idea could lead in the right direction. The process takes
> about 12 seconds from leaving grub till stopping to boot, which sounds
> about right to me for such a basic system.
>
> I did not change anything on the getty, etc/inittab shows:
> tty1::respawn:/sbin/getty -L tty1 0 vt100 # GENERIC_SERIAL
>
> My hardware has three serial ports but i don't know any more details
> about these at the moment.
>

Is it really a serial port? In that case I would expect ttyS0, ttyS1, ...
instead of tty0, tty1, ...

Also the baud rate will normally need to be specified.

Have a look at the corresponding option under the System menu in menuconfig.



> Is there an easy way (like with booting a live ubuntu) to find out if
> tty1 is the right one?
>

A basic approach is to open a getty on all tty's, by adding multiple getty
lines in /etc/inittab, each time for a different tty.

Best regards
Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20210303/85ea6fc0/attachment.html>