All of lore.kernel.org
 help / color / mirror / Atom feed
From: "KESHAV P.R." <skodabenz@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Completely disable graphics support in grub2 x86_64-efi
Date: Wed, 25 Aug 2010 12:14:19 +0530	[thread overview]
Message-ID: <AANLkTi=ojV6b2ed6_CGvHaCbQrkaz9DR2Kc=J38Wgbzc@mail.gmail.com> (raw)
In-Reply-To: <4C747249.4080205@gmail.com>

2010/8/25 Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>:
> On 08/24/2010 04:11 PM, KESHAV P.R. wrote:
>> I am getting these errors when grub.efi is started but before the menu
>> comes up :-
>>
>>
>> error: no such device found
>> (3 times)
>> error: no suitable mode found
>> error: no video mode activated
>>
>>
>> using this config :-
>>
>>
>> insmod efi_gop
>> insmod efi_uga
>> insmod font
>>
>>
> Did you try keeping just efi_uga? This is what was previously hardcoded

efi_uga has no effect. efi_gop shows proper menu colors but no
background image and no kernel boot messages while booting.

>> if loadfont ${prefix}/unifont.pf2
>> then
>>    insmod gfxterm
>>    set gfxmode="1280x800x32,1024x768x32,800x600x32,640x480x32,1280x800,1024x768,800x600,640x480"
>>
> Have you tried gfxmode="auto" ?

no video mode activated error still comes. No change.

I talked to Tianocore guys about this and they told me that EDK1 DUET
(based on UEFI 2.1) does not include BiosVideo support. EDK2 DuetPkg
supports it and I tested DuetPkg X64 (UEFI 2.3) and the background
image came up properly and the kernel boot messages were displayed.
For people who are using old UEIF firmware (based on EDK1) are out of
luck. How come the bzr main trunk's grub.efi shows boot messages even
with the old firmware?

>
>>    set gfxpayload=keep
>>    terminal_output gfxterm
>>
>>    set color_normal=light-blue/black
>>    set color_highlight=light-cyan/blue
>>
>>    insmod png
>>    background_image ${prefix}/archlinux.png
>> fi
>>
>> insmod part_gpt
>> insmod fat
>> insmod ext2
>>
>> set timeout=5
>> set default=0
>>
>> search --file --set=arch64 --no-floppy /vmlinuz26
>>
>> set _kernel_flags="nomodeset add_efi_memmap"
>> set _rootfstype="ext4"
>>
>> menuentry "Arch Linux 2.6.35.3-ARCH" {
>> linux (${arch64})/vmlinuz26
>> root=/dev/disk/by-uuid/0cc6e472-7f98-42ff-b7f3-309b641377ad
>> rootfstype=${_rootfstype} ro ${_kernel_flags}
>> initrd (${arch64})/kernel26.img
>> }
>>
>> menuentry  "Arch Linux 2.6.35.3-ARCH Fallback" {
>> linux (${arch64})/vmlinuz26
>> root=/dev/disk/by-uuid/0cc6e472-7f98-42ff-b7f3-309b641377ad
>> rootfstype=${_rootfstype} ro ${_kernel_flags}
>> initrd (${arch64})/kernel26-fallback.img
>> }
>>
>>
>> The menu colors come up properly but no background image is shown.
>> While booting no kernel boot messages are displayed.
>>
>> Without the gfx related lines (config file starting from "insmod part_gpt" ),
>>
>> (before menu)
>> error: no such device found
>> (3 times)
>>
>> (while booting)
>> error: no suitable mode found
>> Booting however
>>
>> No menu color change and no kernel boot messages. I am using 64-bit
>> UEFI 2.1 firmware (Tianocore EDK1 DUET UEFI64). How do I resolve this?
>> I want to see the kernel boot messages and be able to boot into
>> terminal (runlevel or init 3), not particular about grub2 menu colors
>> or background image. Thanks in advance.
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> http://lists.gnu.org/mailman/listinfo/grub-devel
>>
>>
>
>
> --
> Regards
> Vladimir 'φ-coder/phcoder' Serbinenko
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>


  reply	other threads:[~2010-08-25  6:44 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. [this message]
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
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='AANLkTi=ojV6b2ed6_CGvHaCbQrkaz9DR2Kc=J38Wgbzc@mail.gmail.com' \
    --to=skodabenz@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.