I think it's all in Tumbleweed meanwhile, closing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530530
Title:
Installer doesn't show up on some Chromebooks: "Error setting up
gfxboot"
To
Thanks a lot!
Then, AIUI, the only thing left is to recognize the video mode as 32bit even
though it's advertised as 24bit, right? Can we do that by adding up the
rgb+reserved bits and use this if the sum is > than bits_per_pixel?
--
You received this bug notification because you are a member
Patrick, if you could try out
https://github.com/openSUSE/gfxboot/pull/26
this would be great. There should be everything in place now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530530
Title:
I don't see any reason why the code in the chrome_fb branch shouldn't
work. It does, for example, work in qemu as running './gfxtest -t
test_fb' shows.
>From Timo's reports it seems it gets the framebuffer address right: the code in
themes/test_fb/test_fb.bc that draws directly by writing bytes
> Looking at the code is seems that relocation is required
You're right; after reading up the vbe specs again, 'relocation' means
mapping different regions into the window. So yes, it's required and the
code is correct.
> Would it be possible to add VBE2 and linear framebuffer support to
gfxboot supports 32bit but not 24bit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530530
Title:
Installer doesn't show up on some Chromebooks: "Error setting up
gfxboot"
To manage
> SeaVGABios advertises 24bpp as the panel does support 24bpp, even though the
> VBE format should be 32bpp. I'll send a fix to SeaBIOS.
Uhm, is there a way to detect this situation? Like, add at least the color mask
bits up to 32?
> Is the attribute VBE_WINDOW_ATTRIBUTE_RELOCATABLE required ?
I'm currently out of ideas and it will be tricky to make progress
without such a device at my desk. :-(
Issues I've seen:
- the video bios knows only one video mode with an unusual resolution;
the standard gfxboot script doesn't expect this (and doesn't provide a
theme in this resolution), but
Created attachment 680084
test iso 7: try to draw something
I've prepared a new test image. It shows at startup on a text screen the
internal memory layout. Please attach the numbers (or screenshot).
Then, it will draw a bit. On the first debug screen, you should see the
dots all over the screen
