The thing we learned the hard way, is that on some hardware, you cannot set up the graphics twice unless you do a reset in the middle and that is difficult and sometimes impossible.
For one distro we did, webboot, we would always kexec another linux. We found that, if we wanted graphics in the first linux with x11, we could make the kexec of the final linux with x11 work with qemu, and not with hardware; or with hardware, but not with qemu. It was a mess. The fix in the end is never enable graphics until the last linux boots. Just a data point, not sure that helps. I can say the coreboot graphics init worked on many chromebooks. But Intel fought it tooth and nail, so I also know it did not work in all. On Mon, Nov 24, 2025 at 17:39 <[email protected]> wrote: > I’m not running linux here. only 9front. > Booting from linux USB sticks works without any issues. > > > Using the image seabios_x200_4mb_libgfxinit_txtmode.rom: > With igfx: > - I get a screen glitch (like on photo i sent), but the cursor is drawn. > However, I can't move it. > With vesa: > - It says there's no framebuffer (don’t remember the exact error) and > continues in terminal mode. > > Using seabios_x200_4mb_libgfxinit_corebootfb.rom: > When I boot directly with SeaBIOS, it shows at startup: > bootfile=/amd64/9pc64 > boot > …and then it just freezes. > > When I boot through U-Boot, everything works fine, even with VESA. > > *9fans <https://9fans.topicbox.com/latest>* / 9fans / see discussions > <https://9fans.topicbox.com/groups/9fans> + participants > <https://9fans.topicbox.com/groups/9fans/members> + delivery options > <https://9fans.topicbox.com/groups/9fans/subscription> Permalink > <https://9fans.topicbox.com/groups/9fans/T82d344ab9bb6e428-M0e33dfcd2d1441a9ee971805> > ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T82d344ab9bb6e428-M48a65e9da36db6e2c520436a Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
