> Yes, it completely skips modesetting. > >> What if the same mode is passed as a value? Does linux redoes the >> modesetting? > > Yes, which permits it to display text since now it's set up a linear > framebuffer. Why can't linux use linear framebuffer for its framebuffer console? > >> If 0x0F04 works ok I would prefer to always pass it when kernel is >> booted in graphical mode. VESA mode numbers are an artifact and when >> grub2 has its own graphical drivers it won't correspond to anything. > > It's not the best solution; it's just closer than what's there right > now. The problem with 0x0F04 is that the kernel doesn't know how to > display text until it brings up its own framebuffer, and we need to > figure out how to tell vesafb to come up early so that the kernel can > display text if necessary. At the moment it seems that (a) either 0x0F04 > or a VESA mode number is appropriate if GRUB is booting in graphical > mode; (b) kernel work is needed to do better; (c) as such it is probably > not appropriate for GRUB to boot Linux in graphical mode by default just > yet. > > -- > 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
