From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1M0DRI-00005k-A6 for mharc-grub-devel@gnu.org; Sat, 02 May 2009 07:31:28 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M0DRF-0008Uw-Ao for grub-devel@gnu.org; Sat, 02 May 2009 07:31:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M0DR9-0008T0-G8 for grub-devel@gnu.org; Sat, 02 May 2009 07:31:24 -0400 Received: from [199.232.76.173] (port=50823 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M0DR8-0008Sl-Qd for grub-devel@gnu.org; Sat, 02 May 2009 07:31:19 -0400 Received: from aybabtu.com ([69.60.117.155]:33708) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M0DR8-0006n7-5L for grub-devel@gnu.org; Sat, 02 May 2009 07:31:18 -0400 Received: from [192.168.10.10] (helo=thorin) by aybabtu.com with esmtp (Exim 4.69) (envelope-from ) id 1M0DDr-0001ar-Q5 for grub-devel@gnu.org; Sat, 02 May 2009 13:17:36 +0200 Received: from rmh by thorin with local (Exim 4.69) (envelope-from ) id 1M0DR4-0007OA-TR for grub-devel@gnu.org; Sat, 02 May 2009 13:31:14 +0200 Date: Sat, 2 May 2009 13:31:14 +0200 From: Robert Millan To: The development of GRUB 2 Message-ID: <20090502113114.GA28362@thorin> References: <1239032043.8986.27.camel@mj> <20090413141657.GE12170@thorin> <20090413144558.GA22165@thorin> <1239637296.3549.9.camel@mj> <20090413190546.GB24072@thorin> <1239664820.13208.50.camel@mj> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1239664820.13208.50.camel@mj> Organization: free as in freedom X-Message-Flag: Worried about Outlook viruses? Switch to Thunderbird! www.mozilla.com/thunderbird X-Debbugs-No-Ack: true User-Agent: Mutt/1.5.18 (2008-05-17) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Subject: Re: [PATCH] Video mode fixes in linux loader X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 May 2009 11:31:25 -0000 On Mon, Apr 13, 2009 at 07:20:20PM -0400, Pavel Roskin wrote: > > We could detect this situation by checking video= parameter, and setting > > text mode if intelfb is found. But then again do we want to prevent > > future versions of intelfb from gracefuly transitioning from vesa mode > > without screen glitch? > > No, that would be bad. It's even possible that intelfb would work > correctly in other configurations. The laptop has resolution 1440x900 > that doesn't match any VESA mode. Alright. > > > 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). > > > "vga=ask" is not a warning now. It causes "error: You need to load the > > > kernel first", apparently from initrd. In other words, the "linux" > > > command fails and there is no visible warning. > > > > Sounds like my error code is wrong, but we could turn it into a warning > > like you suggested. > > I was editing the command line from the menu, so I could not see the > message. Waiting for input is a fair game for an option that implies > waiting for input. Spot on. Will do 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."