On Sun, May 03, 2009 at 09:18:02AM -0400, Isaac Dupree wrote: > Robert Millan wrote: > > > > > Some > > > > > kernels may not support VESA modes at all. > > > > > > > > I don't think this is applicable; all modern versions of Linux include > > > > vesa modesetting in its 16-bit entry code, and older versions are > > > > already detected by the new loader (user is prompted to use linux16). > > > > > > I can disable CONFIG_FB, and then the screen remains blank until X > > > starts. It's entirely possible that some distros don't enable CONFIG_FB > > > to save memory, and I don't always enable it in the kernels I configure > > > myself. > > > > Makes sense for official GRUB. > > > > However, I'd still like to add a macro check that can be enabled on distros > > that ship Linux builds with CONFIG_FB and want to enable seamless mode > > transition (this will be the case for e.g. Debian). > > Can we have GRUB2 not be distro-dependent,
We aren't talking about making GRUB distro-dependant, only about what is the default behaviour when user didn't specify any. Official GRUB, as discussed, will default to text mode. I don't see why downstream distributors would need to do the same, since it's so easy to override in case a user needs that. -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
