All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Completely disable graphics support in grub2 x86_64-efi
Date: Thu, 26 Aug 2010 10:30:01 +0200	[thread overview]
Message-ID: <4C762609.303@gmail.com> (raw)
In-Reply-To: <AANLkTin7Ri_3-QqDv7xtp0f_1s_S2geA7xdjr9HcMbAq@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3252 bytes --]

On 08/26/2010 10:02 AM, KESHAV P.R. wrote:
> On Wed, Aug 25, 2010 at 17:43, KESHAV P.R. <skodabenz@gmail.com> wrote:
>   
>> 2010/8/25 Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>:
>>     
>>> Were you testing inside qemu? If so then mainline version has used
>>> video_cirrus module which wasn't propagated into newreloc until I
>>> resynced it recently
>>>       
>> No, I was not testing in qemu or VirtualBox (or any virtual machine).
>> I tried it in real hardware. My GPU is ATI Mobility Radeon HD 3450
>> with 256 MB Graphics RAM, 1280x800 native resolution of my Dell Studio
>> 1537 laptop. Should I use newreloc or experimental branch?
>>
>> Maybe I will try newreloc separately and come back to you.
>>
>>     
> I tried the newreloc branch
> https://code.launchpad.net/~skodabenz/grub/grub2-branch-newreloc but I
> found no difference in fuctionality between experimental and newreloc
> in case of x86_64-efi (I do not know about i386-efi). "newreloc"
> solves the problem of initramfs not being loaded properly and leading
> to kernel panic that currently occurs with mainline, but the graphics
> problem in experimental also occurs with newreloc, I think this
> problem is due to efigfx branch.
efigfx was merged into mainline quite some time ago
>  Is there any command which makes
> grub2 stop trying to load a graphics/video mode and instead fallback
> to efi simple text protocol?
efi simple text protocol was never used for this. Moreover it's not
usable by OS (you can read spec for details, part boot and runtime
protocols)
>  Please include the way mainline handles
> the issue, as a fallback option in efigfx, in case no graphics/video
> mode is found.
>   
I don't understand what happens in your case. According to you
"videotest" doesn't work (can you confirm?) and according to code GRUB
in neither branch tries to detect any other way of configure graphics on
EFI. I have a theory that for some reason Linux uses vga_text normally.
It's possible to have this behaviour with patch at the end of this
e-mail. But that patch can't be incorporated because there is no way to
actualy check the availability of vga_text on EFI and on EFI as a
firmware it's usualy not. EFI is pretty loosy firmware and is definitely
not what I recommend. I recognize that in some cases you have to use EFI
(if your hardware is shipped with it) but in case of DUET, it's
specifically searching for trouble.
Additionaly DUET is labeled as being for test purposes only and not for
regular use.
=== modified file 'grub-core/loader/i386/linux.c'
--- grub-core/loader/i386/linux.c       2010-04-21 17:13:45 +0000
+++ grub-core/loader/i386/linux.c       2010-08-26 08:20:20 +0000
@@ -638,7 +638,7 @@
     }
   else
     {
-#if defined (GRUB_MACHINE_PCBIOS) || defined (GRUB_MACHINE_COREBOOT) ||
defined (GRUB_MACHINE_QEMU)
+#if 1
       params->have_vga = GRUB_VIDEO_LINUX_TYPE_TEXT;
       params->video_mode = 0x3;
 #else


> Regards.
>
> Keshav
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>   


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



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

  reply	other threads:[~2010-08-26  8:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-24 14:11 Completely disable graphics support in grub2 x86_64-efi KESHAV P.R.
2010-08-25  1:30 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-08-25  6:44   ` KESHAV P.R.
2010-08-25  9:44     ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-08-25 12:13       ` KESHAV P.R.
2010-08-26  8:02         ` KESHAV P.R.
2010-08-26  8:30           ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-08-26 10:04             ` KESHAV P.R.
2010-08-26 10:26               ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-08-26 11:25                 ` KESHAV P.R.
2010-08-26 11:47                   ` Vladimir 'phcoder' Serbinenko
2010-08-26 12:02                     ` KESHAV P.R.
2010-08-26 12:26                       ` Vladimir 'phcoder' Serbinenko
     [not found]                         ` <AANLkTi=MYggKu3svrGPxCSdRqvmXEPaGS8qW8baSEOVu@mail.gmail.com>
2010-09-08 12:53                           ` KESHAV P.R.
  -- strict thread matches above, loose matches on Subject: below --
2010-08-21 14:56 KESHAV P.R.

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=4C762609.303@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 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.