All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] gfxpayload
Date: Sat, 16 May 2009 20:20:14 +0200	[thread overview]
Message-ID: <1242498014.3701.10.camel@fz.local> (raw)
In-Reply-To: <d7ead6de0905161101j4821dbb2l63d7126c082a0538@mail.gmail.com>

Am Samstag, den 16.05.2009, 20:01 +0200 schrieb Vladimir 'phcoder'
Serbinenko:
> Hello. Here is a long-discussed gfxpayload patch. To start linux in
> 1024x768 mode do:
> insmod vbe
> gfxmode=1024x768
> linux ...
> ...
> boot
> Multiple modes can be separated by either comma or semicolon. First
> mode can be "keep" which will make the system keep the current mode if
> accepted by kernel. Another special value is "text" which will put in
> text mode.
> Can someone check that vga= backward compatibility code interprets
> values correctly?
> With linux for a reason I don't know it results in black screen in
> qemu. But perhaps it's a problem with my kernel
> Now it's the same syntax for xnu too. Just remember that current xnu
> loader support 32-bit modes only

Just tried it in VMware. 
With set gfxmode=1024x768x24 and set gfxpayload=1024x768x24 and no vga=
option I just get the normal text mode
with set gfxpayload=keep it works
and also vga=0x317 works too.
-- 
Felix Zielcke




  reply	other threads:[~2009-05-16 18:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-16 18:01 [PATCH] gfxpayload Vladimir 'phcoder' Serbinenko
2009-05-16 18:20 ` Felix Zielcke [this message]
2009-05-17 12:35   ` Vladimir 'phcoder' Serbinenko
     [not found]     ` <d7ead6de0905170734u4a13d1ebl3f4686011eeef698@mail.gmail.com>
2009-05-17 20:36       ` Fwd: " Robert Millan
2009-05-18 15:09         ` Colin D Bennett
     [not found]         ` <d7ead6de0905300823u65ab7675h1c6e59b7d76f16be@mail.gmail.com>
2009-05-30 19:41           ` Fwd: " Robert Millan

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=1242498014.3701.10.camel@fz.local \
    --to=fzielcke@z-51.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.