Jiaxun Yang

Ah I see, so CSMWrap will not prepare data structure which passes framebuffer information to SeaVGABIOS when it's using external vgarom. I think it's desired behaviour, what's your use case...

This is actually modesetting issue I mentioned in #3.

> But why CSMWrap not use legacy VBIOS from iGPU? > > PCIe AMD6450 - legacy AMD VBIOS is used iGPU - SeaVGABIOS from CSMWrap is used In this case...

I have no idea about how to obtain VBIOS blob in UEFI... Maybe it's exposed by some protocol instead of PciIo...

> May be, that this is the problem with all graphiks in csmwrap. > > [@FlyGoat](https://github.com/FlyGoat) Is there a possibility, that **SeaBios** looks always for an **legacy VGA Option Rom**...

@ghostplant It really depends. We have a couple of fallback options, but none of them are working all the time.

@ghostplant Yes in most cases. I can't give a universal answer because there are simply too much platform specific issues spanning from hardware to ACPI.

@Gelip I actually have another project to deal with this issue. Just run this in efi shell before CSMWrap. https://github.com/FlyGoat/vgaarb-efi

@Gelip Nah we are not using stdvga variant of SeaVGABIOS, we are using a special build designed for coreboot. stdvga SeaVGABIOS requires BOCHS DISPI VBE extension, which does not exist...

@Gelip I would recommend you not to do so. Maybe it's easier just to build the project...