<apalos>
sjg1: and I assume you are testing with 64 bits?
<apalos>
does kvm play a role? Or it hangs in any case?
<sjg1>
Yes, 64-bit, no kvm, since kvm on x86 still has trouble with option ROMs
<sjg1>
apalos: I'm not sure how to debug booting the Ubuntu installer, since just taking out 'quiet' doesn't seem to do anything
<apalos>
sjg1: when the kernel boots, the first thing it does is launch the EFI-stub
<apalos>
that uses some EFI services, e.g EFI_RNG to setup ASLR, measure the initrd we load etc etc
<apalos>
and setups up the entry point for the kernel proper
<apalos>
What I assume is happening, is it crashes on get_memory_map, but I'll have a look either today or tomorrow
<apalos>
do you have early console enabled?
<apalos>
IIRC earlycon=efifb prints some useful stuff
<sjg1>
apalos: Oh OK, thanks. Yes it shows some stuff on the screen, but it disappears before I can read all of it
<Sout_>
time for the more modern of take of using phone picture to show a kernel panic. video record it at 60 fps :P
flokli has quit [Ping timeout: 252 seconds]
warpme has joined #u-boot
flokli has joined #u-boot
dsimic has quit [Ping timeout: 244 seconds]
guest35 has quit [Quit: Client closed]
dsimic has joined #u-boot
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #u-boot
<apalos>
sjg1: do you have buildman on an executable path in your PC?
<apalos>
Because that scripts assumes that
<apalos>
q
<apalos>
but there are no distro packages with it
<apalos>
also if I cnage the buildman path for a local u-boot dir, ./tools/buildman/buildman -w -o /tmp/b/qemu-x86_64 --board qemu-x86_64 -I exits with an error 100
goliath has quit [Quit: SIGSEGV]
persmule has joined #u-boot
<sjg1>
apalos: Yes I have buildman on the path...
<sjg1>
apalos: I wonder if you have toolchains installed? buildman --list-toolchains
Lightsword has quit [Read error: Connection reset by peer]
Lightsword_ has joined #u-boot
Lightsword_ is now known as Lightsword
Jones42_ has quit [Ping timeout: 248 seconds]
Forest2 has joined #u-boot
<Forest2>
Is there a way to modify uefi variables, like you can with efibootmgr, in u-boot? Trying to get something booted but have no experience with arm boot stuff.
<marex>
xypron: ^
<marex>
apalos: ^
<xypron>
Forest2: You can use the eficonfig and efidebug commands to edit boot options.
<xypron>
For generic variables 'setenv -e', 'printenv -e'.
<Forest2>
Thank you! I got it booting but it requires typing out a long line of commands to boot
<Forest2>
xypron: Is there an easy or recommended way to automate this to have it boot automatically? It is just loading the device tree, kernel, then setting the environment options with setenv, finally booting with bootefi
<xypron>
Ubuntu just loads GRUB and GRUB manages kernel, initrd, devicetree. Debian uses package flash-kernel to create a boot script. Suse IIRC uses GRUB.
<xypron>
If GRUB is /EFI/BOOT/BOOTAA64.EFI U-Boot wiil load it from ESP without any manually set UEFI boot variable.