Re: lfs 12.3-rc1: 10.4. Using GRUB to Set Up the Boot Process

On 22.02.25 07:07, Bruce Dubbs ([email protected] via lfs-support Mailing List) wrote:
> On 2/21/25 11:20 PM, Hans Meier ([email protected] via lfs-support Mailing List) wrote:
>> Hello,
>>
>> In '10.4.4. Creating the GRUB Configuration File' a new configuration
>> parameter has been added: set gfxpayload=1024x768x32
>>
>> Using qemu on the final image results in a black screen unfortunately.
>> Without this parameter everything works fine.
>>
>> qemu-system-x86_64 -m 800 -drive file=image.img
>>
>> Was there any particular reason adding this parameter end of October 2024?
> 
> It's in the command explanations.
> 
> The set gfxpayload=1024x768x32 command sets the
> resolution and color depth of the VESA framebuffer to be passed to the
> kernel.  It's necessary for the kernel SimpleDRM driver to use the
> VESA framebuffer.  You can use a different resolution or color depth
> value which better suits for your monitor.
> 
> You do not have qemu set up to support this.  You can try passing
> -vga std to qemu or just remove the gfxpayload line.
> 
> Also see https://www.gnu.org/software/grub/manual/grub/html_node/gfxpayload.html
> 
>   -- Bruce
> 
> 
> 

The link above says among others (emphasis mine):

"Depending on your kernel, your distribution, your graphics card,
 and the ***phase of the moon***, note that using this option may cause
 GNU/Linux to ***suffer*** from various display problems, particularly
 during the early part of the boot sequence. If you have problems,
 set this variable to ‘text’ and GRUB will tell Linux to boot in
 normal text mode."


I am not sure whether such a parameter belongs to LFS.


Regards,
  Hans

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-support
Unsubscribe: See the above information page