grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: LiveCD bootloader
Date: Thu, 09 Sep 2010 08:51:51 +0200	[thread overview]
Message-ID: <4C888407.6050405@gmail.com> (raw)
In-Reply-To: <AANLkTi=uzvp9aTapNfG4O_3a-bY3Gx8ws6fzc2QjUch=@mail.gmail.com>

On 09/09/10 03:33, Brendan Trotter wrote:
> Hi,
>
> On Thu, Sep 9, 2010 at 8:30 AM, Teresa e Junior<teresaejunior@gmail.com>  wrote:
>    
>> What do you mean with that? Let us suppose, I set:
>>
>> GRUB_GFXMODE=1280x800,1024x768,640x480
>>
>> and if the hardware supports the first, it will use the first, and so
>> forth?
>>      
> Not all of my previous assumptions were obsolete (and this time I
> checked the source code for GRUB2 to make sure).
>
> If the video card and software supports the first video mode then GRUB
> will use the first video mode; regardless of whether or not the
> monitor itself supports the video mode.
>    
GRUB uses VBE on real hardware (I have some intelfb code but it's not 
functional yet), in this case it's VBE responsibility to verify monitor 
capabilities. Even having EDID without knowing the card characteristics 
you can't really check it since card itself may perform 
post-transformations like stretching or splitting the image among monitors.
> This means that: for the monitors I have here; for the newest 3 (LCD)
> monitors you'll get 1280x800 and it will work fine (although probably
> a little blurry due to not using the native resolution of any of the
> monitor's); for the largest CRT you'll probably get a squashed image
> that might still be readable (within the monitors maximum frequency,
> but unsupported aspect ratio); for the next CRT you'll get a black
> screen with an error message from the on screen display; for the next
> 2 CRTs you'll get an unreadable (flickering/rolling) mess; and for the
> last monitor (a very old CRT) you'll probably cause permanent damage.
>
>
> Cheers,
>
> Brendan
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>    


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



  reply	other threads:[~2010-09-10  6:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08  2:42 LiveCD bootloader Teresa e Junior
2010-09-08  5:09 ` Brendan Trotter
2010-09-08  5:24   ` Brendan Trotter
2010-09-08  8:34     ` Robert Millan
2010-09-08 22:47     ` Teresa e Junior
2010-09-08 22:52       ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-08 23:00         ` Teresa e Junior
2010-09-08 23:29           ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-08 23:46             ` Teresa e Junior
2010-09-09  1:33           ` Brendan Trotter
2010-09-09  6:51             ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-09-08  8:36 ` Robert Millan
2010-09-08 22:46   ` Teresa e Junior
2010-09-09  7:53     ` future of grub commands setup and install ? Treutwein Bernhard
2010-09-09 12:14       ` Robert Millan
2010-09-10  6:28         ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-10  6:38         ` Treutwein Bernhard
2010-09-08 15:28 ` LiveCD bootloader Andreas Born
2010-09-08 15:46   ` Colin Watson
2010-09-08 16:31     ` GRUB2 fails when booting from CD Andreas Born
2010-09-26 20:22       ` Andreas Born
2010-09-27 15:17         ` Phillip Susi
     [not found]           ` <4CA1FEF0.4000209@googlemail.com>
     [not found]             ` <4CA215C9.9060000@cfl.rr.com>
     [not found]               ` <4CA219B9.3020209@googlemail.com>
     [not found]                 ` <4CA22FC6.9000701@cfl.rr.com>
2010-09-28 20:19                   ` Andreas Born
2010-12-25 20:45       ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-12-27 12:30         ` Andreas Born
2011-01-04 14:45           ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-08 22:48   ` LiveCD bootloader Teresa e Junior
  -- strict thread matches above, loose matches on Subject: below --
2010-09-09 10:34 Tom Davies
2010-09-15  1:21 ` Teresa e Junior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C888407.6050405@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).