On 16/5/21 9:16 am, faeychild wrote:

>>
>> I would have tried the 1920x1080x32 in that case.
>>
>
> That was the res I was running just before the 1280x1024 change over.
>
> I try 1920 again later when I can reboot

After having rebooted several times, Bits it is entirely possible that
resolution was never 1920x1080. The current 1280x1024 is starting to
look more and more normal.

Maybe it never was 1920x1080 and I have been gas lighting myself and it
never will achieve the maximum resolution

The assumption made was that the old small text was the maximum
resolution

..
--
faeychild
Running plasmashell 5.20.4 on 5.10.33-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso

On 16.05.2021 at 13:57, faeychild scribbled:

> On 16/5/21 9:16 am, faeychild wrote:
>
> >>
> >> I would have tried the 1920x1080x32 in that case.
> >>
> >
> > That was the res I was running just before the 1280x1024 change
> > over.
> >
> > I try 1920 again later when I can reboot
>
> After having rebooted several times, Bits it is entirely possible
> that resolution was never 1920x1080. The current 1280x1024 is
> starting to look more and more normal.
>
> Maybe it never was 1920x1080 and I have been gas lighting myself and
> it never will achieve the maximum resolution
>
> The assumption made was that the old small text was the maximum
> resolution

Okay, as you guys probably already know by now, I'm not running Mageia
here. Instead, I'm running the KDE Plasma edition of Manjaro Stable,
and have been doing so quite happily for over two years now.

But at some point last year, there was an update to GRUB which also
caused me trouble, and in several ways. For instance, instead of
having the Manjaro-themed GFX menu, I got the stock text-mode GRUB boot
menu. After tinkering with /etc/default/grub, I was able to correct
that. The updated GRUB had the line...

GRUB_GFXMODE=auto

.... in it, but I found that this no longer gave me the correct screen
resolution — my monitor is 1920 x 1080. So I changed that to...

GRUB_GFXMODE=1920x1080x32
GRUB_GFXPAYLOAD_LINUX=keep

.... and ran...

$ sudo update-grub

.... and ever since then, I've got an even higher screen resolution in
the boot menu than I originally had when I installed Manjaro, leading
me to suspect that the "auto" setting would have picked something like
1600 x 900 instead of 1920 x 1080.

Now, this machine here has an MSI motherboard with an Intel i5-8400
six-core processor — no hyperthreading — and the GPU is just the
well-known and quite standardized onboard Intel UHD 630 unit, which
uses the in-kernel i915 driver.

But apparently — and this is my bottom line — even with well-known and
standardized hardware, GRUB should not be left to its own devices in
determining the ideal screen resolution. Best is to set the resolution
manually and be done with it.

Just my 2 Eurocents, at today's exchange rate.

> --
> faeychild
> Running plasmashell 5.20.4 on 5.10.33-desktop-1.mga8 kernel.
> Mageia release 8 (Official) for x86_64 installed via
> Mageia-8-x86_64-DVD.iso

Thy signature delimiter is b0rk3n, little Hobbit. It should be "dash
dash space newline". ;)

--
With respect,
= Aragorn

On 16/5/21 2:58 pm, Aragorn wrote:

>
> ... in it, but I found that this no longer gave me the correct screen
> resolution — my monitor is 1920 x 1080. So I changed that to...
>
> GRUB_GFXMODE=1920x1080x32
> GRUB_GFXPAYLOAD_LINUX=keep
>
> ... and ran...
>
> $ sudo update-grub
>
> ... and ever since then, I've got an even higher screen resolution in
> the boot menu than I originally had when I installed Manjaro, leading
> me to suspect that the "auto" setting would have picked something like
> 1600 x 900 instead of 1920 x 1080.

This morning I experimented a little more.

Following your method with GFXPAYLOAD_LINUX=keep

First I changed the GFXMODE 1280, 1024 and booted.
then changed it to 1920, 1080 and booted.

superficial the text looks almost identical

except that the lower resolution stretches the text across the screen a
bit further.

But I am glad to have the neater smaller text back in the boot menu and
the kernel messages

Regards

--
faeychild
Running plasmashell 5.20.4 on 5.10.33-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso

On 13/5/21 8:28 am, Bit Twister wrote:
> On Thu, 13 May 2021 07:22:03 +1000, faeychild wrote:
>> On 12/5/21 1:15 pm, Bit Twister wrote:
>>
>>>
>>> Unless you are making changes or system hardware is intermittent
>>> your update-grub2 should be consistent.
>>>
>>> If you are booting different installs and running update-grub2
>>> then I would expect different results because /etc/default/grub and
>>> /etc/grub.d/* do not contain the same contents.
>>
>> Ummm Yes grub.d contains add on modules if I understand it
>
> All install will have grub.d modules.
> If you want the same selections in grub.cfg then /etc/default/grub
> and /etc/grub.d/ then all installs would need the same contents.
>
> Note I am not talking about your sysrescye install since I have
> never done that. I just download the iso and boot it.
>
>>
>> /default/grub is basic template, it seems
>
> Each distribution decides its contents.
>
>
>
>>>
>>> I do not boot UEFI. I boot cms/legacy os. As a result I pick an install
>>> to be the "Production" boot. As a result that is the booted install where
>>> I run update-grub2 then grub2-install.
>>
>> I haven't run grub2-install.
>>
>>
>> I did run update-grub2 from the Mageia 6 partition and it picked up the
>> resolution change. The sysemrscuecd entry though doesn't exist in Mageai 6
>>
>>
>> Running update-grub2 from Mageia 8 does not pick up the resolution
>> change nor the systemrescue entry. It seems to be impervious to modification
>
> update-grub2 will only generate whatever is in /etc/default/grub and
> whatever scripts are in /etc/grub.d.
>
>> I will put in grub.d later today, see what happens
>
> update-grub2 will only create a /boot/grub2/grub.cfg for the booted
> install. It will not change what /boot/grub2/grub.cfg was/is chosen for
> boot selection.
>
> Boot mga8. Make make your /etc/default/grub and etc/grub.d changes
> in the mga8 install. Run update-grub2 to create /boot/grub2/grub.cfg
> you then have to run install-grub to have it boot using the mga8
> /boot/grub2/grub.cfg
>
If the installed version of grub.cfg came from another OS, you MUST run
grub2-install and update-grub2. If the only change is a kernel upgrade
in a guest OS, update-grub2 alone is sufficient. /etc/default/grub
starts with the modules, etc. which would be on the command line in a
machine with only one OS, including ones like nokmsboot. You can edit
that line if needed.

On 18/5/21 8:36 am, Doug Laidlaw wrote:

>>
> If the installed version of grub.cfg came from another OS, you MUST run
> grub2-install and update-grub2.

Is the order important??
I assume install before update would be the order

--
faeychild
Running plasmashell 5.20.4 on 5.10.33-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso

On Tue, 18 May 2021 15:41:01 +1000, faeychild wrote:
> On 18/5/21 8:36 am, Doug Laidlaw wrote:
>
>>>
>> If the installed version of grub.cfg came from another OS, you MUST run
>> grub2-install and update-grub2.
>
> Is the order important??

I would expect you would want to run update-grub2 first to make sure
it does create a valid /boot/grub2/grub.cfg before doing the
grub2-install to point to grub.cfg.

At least I would.