Re: UEFI Boot with Grub-Experimental

["Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>]

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

On 06/30/2010 07:10 PM, stephen@hyarros.com wrote:
> Hi,
>
> Thanks for the response.
>
> After trying terminal_output, the computer screen would simply go black
> and the machine would hang (the numlock key would not respond) after the
> terminal_output gfx command was executed; this would happen regardless
> of whether or not set gfxmode was called before.  
>   
It's "terminal_output gfxterm", not just "gfx". There may have been bug
in the past thast specifying incorrect terminal lead to bad consequences.
Also be sure not to load efi_uga.
> I also have just tried the efi_video_info patch; the system reports:
>
> GOP info:
> List of video modes:
> 0: 1024 x 768, bitonly, scan line 1024
> Current mode: 0
>
> Do i need to pass this information on to the kernel somehow?
>
> Thanks.
>
> On Wed, 30 Jun 2010 10:40:31 +0100, Colin Watson <cjwatson@ubuntu.com>
> wrote:
>   
>> On Wed, Jun 30, 2010 at 01:54:36AM -0700, stephen@hyarros.com wrote:
>>     
>>> After having no luck using the grub-efi-amd64 package in ubuntu, or the
>>> grub trunk, I've started trying to compile my own grub and getting it to
>>> boot on a new Intel motherboard which supports EFI.  I've not been able
>>> to get any output yet from the acutal linux kernel; usually the system
>>> will simply hang after the boot menu option is selected, or the 'boot'
>>> command is issued from the grub command line.
>>>
>>> Currently the farthest I've gotten is using the grub command line and
>>> typing in the following commands:
>>>
>>> insmod efi_gop # no impact on result
>>> insmod ext2
>>> insmod part_gpt
>>>
>>> set root=(hd0,gpt3)
>>> fakeroot # optional, no impact on result
>>>       
>> I guess that should be 'fakebios'.
>>
>>     
>>> error: no suitable mode found
>>>       
>> After 'insmod efi_gop', could you try 'insmod gfxterm' and then
>> 'terminal_output gfxterm', and see what happens?  Before the
>> terminal_output command, you can also use 'set gfxmode=MODE' (e.g. 'set
>> gfxmode=1024x768') to change its mode selection.  gfxterm can help
>> matters here, as that way you have a working video mode that the kernel
>> can be told to inherit, rather than having to probe its own.
>>
>> Unfortunately right now it's hard to get debugging information on EFI
>> video modes.  Since you're building your own GRUB anyway, though, you
>> could try this patch against trunk:
>>
>>   http://people.canonical.com/~cjwatson/tmp/grub-efivideoinfo.patch
>>
>> That will give you an 'efi_video_info' command, which should dump out
>> the available GOP modes, and might be useful to get a slightly better
>> idea of what's going on.
>>
>>     
>>> booting however
>>> _
>>>
>>> And then nothing else happens.
>>>       
>> It's possible that the kernel may have booted successfully, but that you
>> simply don't have a working console.  It would be useful to try pinging
>> the machine to test that.
>>
>>     
>>> I've also tried newreloc, but I don't think this has anything to do with
>>> relocations.
>>>       
>> Agreed.
>>     
>
> _______________________________________________
> 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 --]