> > Hmm. You seem to be right, on investigation (I'd missed the fact that > the 32-bit boot protocol skips a whole bunch of initialisation code), > but in that case I'm thoroughly confused about why setting it made any > difference at all in my tests. Back to the drawing board, I guess. > > (It's not actually quite true that vid_mode isn't used *at all* with the > 32-bit boot protocol; it's still saved for use with ACPI sleep.) > >> Does 0x0F04 really do something when used in combination with Linux' vesafb? > > It seems to be 16-bit boot protocol only. I withdraw this patch for the > time being as I'm obviously confused. If these numbers are still needed it needs to be uniform between gfxpayload=1024x768 or gfxpayload=keep + gfxmode=1024x768. Derive the number from video mode information if you really need it > > -- > Colin Watson [cjwat...@ubuntu.com] > > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/grub-devel >
-- Regards Vladimir 'phcoder' Serbinenko Personal git repository: http://repo.or.cz/w/grub2/phcoder.git _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
