Re: No framebuffer available until amdgpu driver is loaded

[Jorge Fernandez Monteagudo]

Hi Paul! Sorry, I've done a lot of tests with different configuration but I've attached a coreboot.log and the CBFS from my last coreboot with this problem.
> What board with what graphics device is it?

I'm testing and AMD bettong board on coreboot-4.10. The graphic card is integrated in the SOC.
> Do you run the VGA Option ROM? Without it, you won’t get any output until
> a proper driver sets up the device to my knowledge.

Yes, I see a graphic mode set in coreboot and the next lines in coreboot log, but no framebuffer once the linux kernel is run. Maybe I have to close this console somehow...

VBE: Getting information about VESA mode 4122                                                                                                                                                    
VBE: resolution:  800x600@32                                                                                                                                                                     
VBE: framebuffer: e0000000                                                                                                                                                                       
VBE: Setting VESA mode 4122

Thanks!
Jorge

No framebuffer available until amdgpu driver is loaded

[Paul Menzel]

[Your MUA (mailer) does not set the *References* header field, thus
breaking threading.]

Dear Jorge,

On 2019-11-12 15:34, Jorge Fernandez Monteagudo wrote:
> Sorry, I've done a lot of tests with different configuration
> but I've attached a coreboot.log and the CBFS from my last coreboot 
> with this problem.

Thank you.
> > What board with what graphics device is it?
>
> I'm testing and AMD bettong board on coreboot-4.10. The graphic card
> is integrated in the SOC.
> > Do you run the VGA Option ROM? Without it, you won’t get any output until
> > a proper driver sets up the device to my knowledge.
>
> Yes, I see a graphic mode set in coreboot and the next lines in
> coreboot log, but no framebuffer once the linux kernel is run.

I do not understand that sentence. Do you see anything at all on
the monitor before Linux starts? If so, what payload? But judging
from the payload size, you are using the Linux kernel payload.
> Maybe I have to close this console somehow...
>
> VBE: Getting information about VESA mode 4122
> VBE: resolution:  800x600@32
> VBE: framebuffer: e0000000
> VBE: Setting VESA mode 4122

SeaBIOS is recommended to run VGA Option ROMs. As another data
point, please disable Option ROM loading in coreboot, and use
SeaBIOS to run it, and load your Linux payload from SeaBIOS [1].

Kind regards,

Paul

[1]: https://www.coreboot.org/SeaBIOS#Adding_payloads