Hi!
I'm trying to build a custom x86 image.
The image provided from the OpenWRT site, shows the grub menu, kernel is booting, then there is no video output anymore.
When I try to boot my own custom image, it doesn't even show the grub menu. (Intel System)
On my Desktop machine the image boots fine. (AMD System)
My normal chore for flashing OpenWRT in x86-64 (From Windows) are :
Dump Ubuntu 21.10 iso into a USB drive by using RUFUS on windows
Extract for example openwrt-x86-64-generic-ext4-combined-efi.img.gz archive into only openwrt-x86-64-generic-ext4-combined-efi.img with WINRAR
Copy openwrt-x86-64-generic-ext4-combined-efi.img into another USB drive
Boot into Ubuntu 21.10 live usb, and choose "Try Ubuntu"
Open the GPARTED from the ubuntu live USB, & delete all of the partition on the target disk (mine is /dev/nvme0n1)
Plug-in another USB drive that has openwrt-x86-64-generic-ext4-combined-efi.img on it, open the corresponding partition which has it with the file explorer in the Ubuntu live USB, on the file manager right click and choose "Open Terminal"
Type in for example "sudo dd if=openwrt-x86-64-generic-ext4-combined-efi.img of=/dev/nvme0n1" , wait for around 3-5 minutes until dd is done.
Remove all of the usb drive and reboot.
So probably you dd/flashed the .gz (compressed gzip archive file) without being extracted/gunzip first
Optional :
You can also use the gparted from the Ubuntu Live USB to resize the partition size to use biggest possible value.
No, the usb sticks are only for one for live ubuntu 21.10 and another one to store the openwrt-x86-64-generic-ext4-combined-efi.img file which containing the OpenWRT image itself.
Be aware to understand carefully the partition when using dd, don't flash/gparted the wrong drive/partitions.
It will end up a openwrt-21.02.2-x86-64-generic-ext4-combined-efi.img file, copy this file into second usb stick.
The idea of using Ubuntu live USB is to use the gparted/dd tools, much easier for me if it's in GUI, feel free to use debian/distro cli/console anyway.
I got it booting from USB.
But it has the same problem as the official image.
There is some console output, then reboot after a short time.
I guess some kind of kernel panic?
I tried different boot options to stop the automatic reboot but I can't get this working.
So I used my phone cam to capture the log.
Text is quite fuzzy and lines are overlapping because they are scrolling so fast.
It is something about:
comm: swapper Not tainted (which is a generic error message when something is screwed?)
Is this a system with multiple CPU chips not just multiple cores in a single chip? That is what the IBM note is about. Also the chips would have to be not identical stepping revision versions.
If it has a standard bus-attached serial port (not a USB adapter) it should send out the whole boot log on the serial port.
Hi!
It only has one single CPU.
I searched for comm: swapper Not tainted online and the IBM article popped up.
But it seems like the "not tainted" message is related to many things.
Unfortunately I don't have a serial console on this device.
PFsense, OPNsense, etc all boot fine.
The image also boots fine on my AMD system.
So it must be something INTEL related that it doesn't boot?
I know you said you tried to film the failing boot sequence, but the text's to fast for the phone.
Did you try filming in slow motion mode ? It'll get you more frames/sec but at lower res.
might want to create a separate thread in the developer forum
but the answer might be to use musl, but I haven't been down that road, trying to avoid self made images
if you're using the official image, it'll resize the partition back to the original size, but if you're
creating your own images, you might put in a different size - MyBook Live Duo 21.02.2 / rootfs size - #10 by takimata