[Bug 1530530]
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 manage notifications about this bug go to: https://bugs.launchpad.net/gfxboot-theme-ubuntu/+bug/1530530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530530]
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 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 notifications about this bug go to: https://bugs.launchpad.net/gfxboot-theme-ubuntu/+bug/1530530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530530]
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: Installer doesn't show up on some Chromebooks: "Error setting up gfxboot" To manage notifications about this bug go to: https://bugs.launchpad.net/gfxboot-theme-ubuntu/+bug/1530530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530530]
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 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 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 notifications about this bug go to: https://bugs.launchpad.net/gfxboot-theme-ubuntu/+bug/1530530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530530]
> 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 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 notifications about this bug go to: https://bugs.launchpad.net/gfxboot-theme-ubuntu/+bug/1530530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530530]
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 notifications about this bug go to: https://bugs.launchpad.net/gfxboot-theme-ubuntu/+bug/1530530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530530]
> 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 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 notifications about this bug go to: https://bugs.launchpad.net/gfxboot-theme-ubuntu/+bug/1530530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530530]
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 0xa 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 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 Chromebook To manage notifications about this bug go to: https://bugs.launchpad.net/gfxboot-theme-ubuntu/+bug/1530530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530530]
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 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 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 Chromebook To manage notifications about this bug go to: https://bugs.launchpad.net/gfxboot-theme-ubuntu/+bug/1530530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
