http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c2 Timo Jyrinki changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |timo.jyrinki@gmail.com --- Comment #2 from Timo Jyrinki --- Created attachment 677518 --> http://bugzilla.suse.com/attachment.cgi?id=677518&action=edit result from test iso 1 It just hangs in there. With kvm /dev/sdb on another machine I can see it correctly gives resolution list. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c4 Timo Jyrinki changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(timo.jyrinki@gmai | |l.com) | --- Comment #4 from Timo Jyrinki --- Right, yes it does react to Esc, I can get the boot: menu with the harddisk/linux/upgrade etc options. So it's not hanged. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c6 --- Comment #6 from Steffen Winterfeldt --- Created attachment 677583 --> http://bugzilla.suse.com/attachment.cgi?id=677583&action=edit test iso 2: show active vbe mode and try to use it Please test this one. Ideally it shows the current mode and then lets you continue. Anything can happen, but I'd like at least to know the mode number. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c7 --- Comment #7 from Timo Jyrinki --- Created attachment 677602 --> http://bugzilla.suse.com/attachment.cgi?id=677602&action=edit result from test iso 2 No graphics still. (but under kvm I got the graphical menu instead of text one) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c9 Timo Jyrinki changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(timo.jyrinki@gmai | |l.com) | --- Comment #9 from Timo Jyrinki --- Created attachment 677609 --> http://bugzilla.suse.com/attachment.cgi?id=677609&action=edit result from test iso 3 We've some modes. The native resolution of Acer Chromebook R11 (Braswell 14nm CPU) is 1366x768. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c11 --- Comment #11 from Timo Jyrinki --- With test iso 4, blank black screen after the "Press a key to continue..." prompt after the modes are displayed as in the previous image attachement. Keypresses don't seem have a visual effect. (On kvm /dev/sdb, 320x200 graphical output) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c13 --- Comment #13 from Timo Jyrinki --- With test iso 5 still just blank black screen after seeing the text "Initializing gfx code...". -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c15 --- Comment #15 from Timo Jyrinki --- Created attachment 677776 --> http://bugzilla.suse.com/attachment.cgi?id=677776&action=edit result from test iso 6 We have image! Sorry for bad colors, they are normal red/green/blue for all the blocks. The text is ip 26d: 2010b0a9.4 (ie the '1' is what's barely visible under green color in the photo) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c17 --- Comment #17 from Timo Jyrinki --- Nothing seems to happen when I press Esc, the screen stasys as is. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c19 --- Comment #19 from Steffen Winterfeldt --- I'm on vacation next week and won't respond during that time. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c21 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snwint@suse.com Flags| |needinfo?(snwint@suse.com) --- Comment #21 from Steffen Winterfeldt --- Created attachment 680084 --> http://bugzilla.suse.com/attachment.cgi?id=680084&action=edit 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 as before + some lines crossing the screen + a small rectangle in the middle. When you press ESC there, you reach another debug point and the text 'Test' should be printed at the top of the screen. Do any of these things show up? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c23 --- Comment #23 from Steffen Winterfeldt --- 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 that can be trivially adjusted - it seems that the graphics card can only be accessed via framebuffer; but gfxboot uses the old method via 64k windows mapped at 0xa0000 for drawing; I've added a patch that changes this (see link below) - and which works at least on some test machines - it still doesn't work here; the patch seems to be ok because you can (a) draw directly by using the framebuffer pointer and do memory writes (the dots you see with the test isos) and (b) the debug window is visible (it's drawn using standard internal routines) - my suspicion atm is that _reading_ from the framebuffer causes problems: it's done implicitly internally at a number of places and can't be avoided (design decision from the old times where free memory was scarce); also, maybe strange mtrr settings are an issue I've put the current state into the chrome_fb branch (there's some translation update that slipped into it which can be ignored). When you build the 'test_fb' theme, you basically get test iso 7. https://github.com/openSUSE/gfxboot/tree/chrome_fb -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c25 Patrick Rudolph changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |siro@das-labor.org --- Comment #25 from Patrick Rudolph --- gfxboot doesn't support 24bpp or 32bpp. The only mode that is supported by coreboot's native graphics initialization is 32bpp. As the graphics initialization is done by coreboot, the pixel format can't be changed in (Sea)VGABIOS. I'm working on supporting multiple resolutions, but the main problem persists. There will be only one advertised pixel format ever. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c27 --- Comment #27 from Patrick Rudolph --- You are right. I got confused looking at the code: pixel_bits db 0 ; pixel size (8 or 16) color_bits db 0 ; color bits (8, 15 or 16) This should be fixed. SeaVGABios advertises 24bpp as the panel does support 24bpp, even though the VBE format should be 32bpp. I'll send a fix to SeaBIOS. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c29 --- Comment #29 from Steffen Winterfeldt ---

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 ?

Good point. It isn't. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c31 --- Comment #31 from Steffen Winterfeldt ---

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?

Yes, I've done this in the branch mentioned in comment 23. The patch basically simulates the 64k window thing by moving 64k segment selectors across the framebuffer. -- You are receiving this mail because: You are on the CC list for the bug.

From Timo's reports it seems it gets the framebuffer address right: the code in

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c33 --- Comment #33 from Steffen Winterfeldt --- 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. themes/test_fb/test_fb.bc that draws directly by writing bytes into the fb and creates the diagonal pixel pattern seemed to work. But then it gets wrong. I don't have an idea so far, why. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c35 --- Comment #35 from Steffen Winterfeldt --- 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 are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c37 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(siro@das-labor.or | |g) --- Comment #37 from Steffen Winterfeldt --- 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 are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980570 http://bugzilla.suse.com/show_bug.cgi?id=980570#c39 --- Comment #39 from Patrick Rudolph --- My framebuffer fixes are part SeaBIOS 1.11.0 stable. -- You are receiving this mail because: You are on the CC list for the bug.