Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

"If the code and the comments disagree, then both are probably wrong." -- Norm Schryer


computers / alt.os.linux.mageia / update-grub2 boot menu and stuff

SubjectAuthor
* update-grub2 boot menu and stufffaeychild
+* Re: update-grub2 boot menu and stuffBit Twister
|`* Re: update-grub2 boot menu and stufffaeychild
| `* Re: update-grub2 boot menu and stuffBit Twister
|  +* Re: update-grub2 boot menu and stufffaeychild
|  |`* Re: update-grub2 boot menu and stuffBit Twister
|  | `* Re: update-grub2 boot menu and stufffaeychild
|  |  +* Re: update-grub2 boot menu and stuffWilliam Unruh
|  |  |`- Re: update-grub2 boot menu and stufffaeychild
|  |  `* Re: update-grub2 boot menu and stuffBit Twister
|  |   `* Re: update-grub2 boot menu and stufffaeychild
|  |    `* Re: update-grub2 boot menu and stuffBit Twister
|  |     `* Re: update-grub2 boot menu and stufffaeychild
|  |      `* Re: update-grub2 boot menu and stuffBit Twister
|  |       +- Re: update-grub2 boot menu and stufffaeychild
|  |       `* Re: update-grub2 boot menu and stufffaeychild
|  |        `* Re: update-grub2 boot menu and stuffBit Twister
|  |         `* Re: update-grub2 boot menu and stufffaeychild
|  |          `* Re: update-grub2 boot menu and stuffBit Twister
|  |           `* Re: update-grub2 boot menu and stufffaeychild
|  |            +- Re: update-grub2 boot menu and stufffaeychild
|  |            `* Re: update-grub2 boot menu and stufffaeychild
|  |             `* Re: update-grub2 boot menu and stuffAragorn
|  |              `- Re: update-grub2 boot menu and stufffaeychild
|  `* Re: update-grub2 boot menu and stuffDoug Laidlaw
|   `* Re: update-grub2 boot menu and stufffaeychild
|    `- Re: update-grub2 boot menu and stuffBit Twister
`* Re: update-grub2 boot menu and stuffDavid W. Hodgins
 +* Re: update-grub2 boot menu and stuffBit Twister
 |`- Re: update-grub2 boot menu and stuffDavid W. Hodgins
 `- Re: update-grub2 boot menu and stufffaeychild

Pages:12
update-grub2 boot menu and stuff

<s7fe2m$c7q$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3609&group=alt.os.linux.mageia#3609

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: faeych...@nomail.afraid.org (faeychild)
Newsgroups: alt.os.linux.mageia
Subject: update-grub2 boot menu and stuff
Date: Wed, 12 May 2021 12:21:01 +1000
Organization: A noiseless patient Spider
Lines: 86
Message-ID: <s7fe2m$c7q$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 12 May 2021 02:21:10 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="64bd445fb934e62a6083ed578a6ecab7";
logging-data="12538"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18kglR9XWuMysco0AfG12Gp/6HmEXrQv6I="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
Thunderbird/78.10.0
Cancel-Lock: sha1:ArOo93z0hY0Kay+b49K2PgNWPM8=
Content-Language: en-US
X-Mozilla-News-Host: snews://news.motzarella.org:563
 by: faeychild - Wed, 12 May 2021 02:21 UTC

I find there to be some inconsistencies with the results of
"update-grub2"

I have run update-grub2 several times but the response is not what I
expected. update-grub2 when run does produce output indicative of files
being accessed.

Generating grub configuration file ...
Found theme: /boot/grub2/themes/maggy/theme.txt
Found linux image: /boot/vmlinuz-5.10.33-desktop-1.mga8
Found initrd image: /boot/initrd-5.10.33-desktop-1.mga8.img
Found linux image: /boot/vmlinuz-5.10.16-desktop-1.mga8
Found initrd image: /boot/initrd-5.10.16-desktop-1.mga8.img
Found linux image: /boot/vmlinuz-desktop
Found initrd image: /boot/initrd-desktop.img
Found Mageia 8 (8) on /dev/nvme0n1p2
---------------etc-----------------

I have the systemrescuecd installed in a separate partition and the menu
entry is in /etc/grub.d

ls -l /etc/grub.d/25*
-rwxrwxr-x 1 root root 504 Sep 9 2019 /etc/grub.d/25_sysresccd*

The entry shows up in /boot/grub2/grub.cfg

### END /etc/grub.d/20_ppc_terminfo ###

### BEGIN /etc/grub.d/25_sysresccd ###

menuentry "SystemRescueCd (isoloop)" {
load_video
insmod gzio
insmod part_gpt
insmod part_msdos
insmod ext2
search --no-floppy --label boot --set=root
loopback loop /systemrescuecd.iso
echo 'Loading kernel ...'
linux (loop)/sysresccd/boot/x86_64/vmlinuz img_label=boot
img_loop=/systemrescuecd.iso archisobasedir=sysresccd copytoram setkmap=us
echo 'Loading initramfs ...'
initrd (loop)/sysresccd/boot/x86_64/sysresccd.img
} ### END /etc/grub.d/25_sysresccd ###

I also have the higher res vga entry in /etc/default/grub

GRUB_DISTRIBUTOR=Mageia
GRUB_ENABLE_CRYPTODISK=y

GRUB_GFXMODE=1920x1080x32

GRUB_GFXPAYLOAD_LINUX=auto

But curiously the systemrescuecd entry does not show in the boot menu
and the boot messages (text) is still in low res vga eg: large full
screen.
\ I have had these effects come and go when booting different partitions -
MGA 6 MGA 7 MGA 8-

I have gained them and then lost them again

I am still considering installing just Mageia 6 and Mageia 8 so the
situation isn't critical. It's one of ancillary consideration that crop
up when messing around

And I can't understand what the inconstancy is. I suspect that I am
missing something

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

Re: update-grub2 boot menu and stuff

<slrns9mi2s.1gqec.BitTwister@wb.home.test>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3610&group=alt.os.linux.mageia#3610

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: BitTwis...@mouse-potato.com (Bit Twister)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Tue, 11 May 2021 22:15:39 -0500
Organization: A noiseless patient Spider
Lines: 42
Message-ID: <slrns9mi2s.1gqec.BitTwister@wb.home.test>
References: <s7fe2m$c7q$1@dont-email.me>
Injection-Info: reader02.eternal-september.org; posting-host="66f08e801c9c2a3c706ce3128b3951af";
logging-data="6722"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+MEbjA3kiGH3irVyBwJfVkXinTi6pupVc="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:C8aTNlWC/hqbEteLMSsZDmJoQ9Q=
 by: Bit Twister - Wed, 12 May 2021 03:15 UTC

On Wed, 12 May 2021 12:21:01 +1000, faeychild wrote:
>
>
> I find there to be some inconsistencies with the results of
> "update-grub2"
>

>
> But curiously the systemrescuecd entry does not show in the boot menu
> and the boot messages (text) is still in low res vga eg: large full
> screen.
> \
> I have had these effects come and go when booting different partitions -
> MGA 6 MGA 7 MGA 8-
>
> I have gained them and then lost them again
>
> I am still considering installing just Mageia 6 and Mageia 8 so the
> situation isn't critical. It's one of ancillary consideration that crop
> up when messing around
>
> And I can't understand what the inconstancy is. I suspect that I am
> missing something

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.

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.

If I install another OS/release, its update-grub2 and grub2-install
overwrites my "Production" boot. I then have to boot the Production
install and run update-grub2 and grub2-install to pickup the new
install and restored my "Production" boot setup.

Re: update-grub2 boot menu and stuff

<op.029lfug4a3w0dxdave@hodgins.homeip.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3612&group=alt.os.linux.mageia#3612

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: dwhodg...@nomail.afraid.org (David W. Hodgins)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Wed, 12 May 2021 01:27:20 -0400
Organization: A noiseless patient Spider
Lines: 13
Message-ID: <op.029lfug4a3w0dxdave@hodgins.homeip.net>
References: <s7fe2m$c7q$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
Content-Transfer-Encoding: 8bit
Injection-Info: reader02.eternal-september.org; posting-host="fab3e005e34d291a619312714f3c896d";
logging-data="14657"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX195WxM6dPXfbWOIqZN2/2vFP2NgaOyLsQ0="
User-Agent: Opera Mail/12.16 (Linux)
Cancel-Lock: sha1:u+TxtbrdNsmdl2hbrPVrFJ9Qc40=
 by: David W. Hodgins - Wed, 12 May 2021 05:27 UTC

On Tue, 11 May 2021 22:21:01 -0400, faeychild <faeychild@nomail.afraid.org> wrote:
> I have the systemrescuecd installed in a separate partition and the menu
> entry is in /etc/grub.d
> And I can't understand what the inconstancy is. I suspect that I am
> missing something

Is the partition with the systemrescuecd always mounted when update-grub is run?

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.

Re: update-grub2 boot menu and stuff

<slrns9ni9p.1ode4.BitTwister@wb.home.test>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3613&group=alt.os.linux.mageia#3613

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: BitTwis...@mouse-potato.com (Bit Twister)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Wed, 12 May 2021 07:25:17 -0500
Organization: A noiseless patient Spider
Lines: 15
Message-ID: <slrns9ni9p.1ode4.BitTwister@wb.home.test>
References: <s7fe2m$c7q$1@dont-email.me>
<op.029lfug4a3w0dxdave@hodgins.homeip.net>
Injection-Info: reader02.eternal-september.org; posting-host="66f08e801c9c2a3c706ce3128b3951af";
logging-data="21496"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/8FmtHaI+VnbREGduNrlGE2s5e+3olv70="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:wbM5jrC2mYhiSaHRTdCrbZnaSUE=
 by: Bit Twister - Wed, 12 May 2021 12:25 UTC

On Wed, 12 May 2021 01:27:20 -0400, David W. Hodgins wrote:
> On Tue, 11 May 2021 22:21:01 -0400, faeychild <faeychild@nomail.afraid.org> wrote:
>> I have the systemrescuecd installed in a separate partition and the menu
>> entry is in /etc/grub.d
>> And I can't understand what the inconstancy is. I suspect that I am
>> missing something
>
> Is the partition with the systemrescuecd always mounted when update-grub is run?

I am curious as to why that would matter.

update-grub looks through the partition table, mounts unmounted partitions
then looks for OS images to boot. That partition umount is what causes
update-grub to take a long time to complete.

Re: update-grub2 boot menu and stuff

<op.03apb3zfa3w0dxdave@hodgins.homeip.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3616&group=alt.os.linux.mageia#3616

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: dwhodg...@nomail.afraid.org (David W. Hodgins)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Wed, 12 May 2021 15:49:05 -0400
Organization: A noiseless patient Spider
Lines: 29
Message-ID: <op.03apb3zfa3w0dxdave@hodgins.homeip.net>
References: <s7fe2m$c7q$1@dont-email.me>
<op.029lfug4a3w0dxdave@hodgins.homeip.net>
<slrns9ni9p.1ode4.BitTwister@wb.home.test>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
Content-Transfer-Encoding: 8bit
Injection-Info: reader02.eternal-september.org; posting-host="9e14b6094f6c6f31b51829a380230278";
logging-data="19963"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18ATNjs0Oeo8dh8UUKSy1GZTIFhKqEo3pU="
User-Agent: Opera Mail/12.16 (Linux)
Cancel-Lock: sha1:DYHeGOUBbe/zX2GZBWOtn/TFT1I=
 by: David W. Hodgins - Wed, 12 May 2021 19:49 UTC

On Wed, 12 May 2021 08:25:17 -0400, Bit Twister <BitTwister@mouse-potato.com> wrote:

> On Wed, 12 May 2021 01:27:20 -0400, David W. Hodgins wrote:
>> On Tue, 11 May 2021 22:21:01 -0400, faeychild <faeychild@nomail.afraid.org> wrote:
>>> I have the systemrescuecd installed in a separate partition and the menu
>>> entry is in /etc/grub.d
>>> And I can't understand what the inconstancy is. I suspect that I am
>>> missing something
>>
>> Is the partition with the systemrescuecd always mounted when update-grub is run?
>
> I am curious as to why that would matter.
>
> update-grub looks through the partition table, mounts unmounted partitions
> then looks for OS images to boot. That partition umount is what causes
> update-grub to take a long time to complete.

I'd forgotten that it will mount the partitions as I normally disable the scan
for other installs. I now keep one install per drive and use the bios boot
drive selection to pick the install to boot.

On my uefi systems I now use refind to select the install, except when I have
to test grub2-efi.

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.

Re: update-grub2 boot menu and stuff

<s7hftj$jr2$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3618&group=alt.os.linux.mageia#3618

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: faeych...@nomail.afraid.org (faeychild)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Thu, 13 May 2021 07:04:50 +1000
Organization: A noiseless patient Spider
Lines: 20
Message-ID: <s7hftj$jr2$1@dont-email.me>
References: <s7fe2m$c7q$1@dont-email.me>
<op.029lfug4a3w0dxdave@hodgins.homeip.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 12 May 2021 21:04:51 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="64bd445fb934e62a6083ed578a6ecab7";
logging-data="20322"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX191zPCcIgfUG7Uw4682BbQGeqOYhBMmVWE="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
Thunderbird/78.10.0
Cancel-Lock: sha1:m7SZ+mtoTdRk7/4FpxheyxQoXSA=
In-Reply-To: <op.029lfug4a3w0dxdave@hodgins.homeip.net>
Content-Language: en-US
 by: faeychild - Wed, 12 May 2021 21:04 UTC

On 12/5/21 3:27 pm, David W. Hodgins wrote:
> On Tue, 11 May 2021 22:21:01 -0400, faeychild
> <faeychild@nomail.afraid.org> wrote:
>> I have the systemrescuecd installed in a separate partition and the menu
>> entry is in /etc/grub.d
>> And I can't understand what the inconstancy is. I suspect that I am
>> missing something
>
> Is the partition with the systemrescuecd always mounted when update-grub
> is run?
>

No "boot_iso" isn't mounted. I'll try that next

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

Re: update-grub2 boot menu and stuff

<s7hgtu$aqs$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3620&group=alt.os.linux.mageia#3620

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: faeych...@nomail.afraid.org (faeychild)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Thu, 13 May 2021 07:22:03 +1000
Organization: A noiseless patient Spider
Lines: 40
Message-ID: <s7hgtu$aqs$1@dont-email.me>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 12 May 2021 21:22:06 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="64bd445fb934e62a6083ed578a6ecab7";
logging-data="11100"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18MnoAExDhOmSguBAi7UR8ZkJvTI5AxfBU="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
Thunderbird/78.10.0
Cancel-Lock: sha1:OoSOc/ouF+v98cR7BC3NrcNaq2A=
In-Reply-To: <slrns9mi2s.1gqec.BitTwister@wb.home.test>
Content-Language: en-US
 by: faeychild - Wed, 12 May 2021 21:22 UTC

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

/default/grub is basic template, it seems
>
> 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
I will put in grub.d later today, see what happens

Running update-grub2 from Mageia 8 does not pick up the resolution
change nor the systemrescue entry. It seems to be impervious to modification

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-7-x86_64-DVD.iso

Re: update-grub2 boot menu and stuff

<slrns9olkm.1ppqm.BitTwister@wb.home.test>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3623&group=alt.os.linux.mageia#3623

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: BitTwis...@mouse-potato.com (Bit Twister)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Wed, 12 May 2021 17:28:37 -0500
Organization: A noiseless patient Spider
Lines: 55
Message-ID: <slrns9olkm.1ppqm.BitTwister@wb.home.test>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test> <s7hgtu$aqs$1@dont-email.me>
Injection-Info: reader02.eternal-september.org; posting-host="4b45ff8289593a43c7a339cd6b953292";
logging-data="21928"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19h5Qz1VuQblWjwRs0Eo5Hxsx44xRbhSAM="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:7r8Ej0ErzJpYKmTwbF+UE1Y9Mik=
 by: Bit Twister - Wed, 12 May 2021 22:28 UTC

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

Re: update-grub2 boot menu and stuff

<s7ip37$jv4$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3631&group=alt.os.linux.mageia#3631

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: faeych...@nomail.afraid.org (faeychild)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Thu, 13 May 2021 18:47:32 +1000
Organization: A noiseless patient Spider
Lines: 108
Message-ID: <s7ip37$jv4$1@dont-email.me>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test> <s7hgtu$aqs$1@dont-email.me>
<slrns9olkm.1ppqm.BitTwister@wb.home.test>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 13 May 2021 08:47:35 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="de03e9f3c446cc8b424ae0efdd5a3a45";
logging-data="20452"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/hE2r503wMbqGo3wHEqlQGNFeAkGStPew="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
Thunderbird/78.10.0
Cancel-Lock: sha1:gNGLaHf8aVSznKQES+Sx4C6IWss=
In-Reply-To: <slrns9olkm.1ppqm.BitTwister@wb.home.test>
Content-Language: en-US
X-Mozilla-News-Host: news://news.motzarella.org
 by: faeychild - Thu, 13 May 2021 08:47 UTC

On 13/5/21 8:28 am, Bit Twister wrote:

>
> 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
>

I have booted Mageia 8

cat /etc/issue
Mageia release 8 (Official) for x86_64
Kernel 5.10.33-desktop-1.mga8 on an 8-processor x86_64 / \l

[root@unimatrix ~]# cat /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="nokmsboot noiswmd
resume=UUID=0f26b0d8-adf7-45cf-a963-cc5d89c1a8e4 audit=0 vga=791"
GRUB_DEFAULT=saved
GRUB_DISABLE_OS_PROBER=false
GRUB_DISABLE_RECOVERY=false
GRUB_DISABLE_SUBMENU=n
GRUB_DISTRIBUTOR=Mageia
GRUB_ENABLE_CRYPTODISK=y
GRUB_GFXMODE=1920x1080x24
GRUB_GFXPAYLOAD_LINUX=auto
GRUB_SAVEDEFAULT=true
GRUB_TERMINAL_OUTPUT=gfxterm
GRUB_THEME=/boot/grub2/themes/maggy/theme.txt
GRUB_TIMEOUT=10

ls -la /etc/grub.d/
total 108
drwxr-xr-x 2 root root 4096 May 13 17:07 ./
drwxr-xr-x 124 root root 12288 May 13 18:21 ../
-rwxr-xr-x 1 root root 9346 Feb 17 22:43 00_header*
-rwxr-xr-x 1 root root 236 Feb 17 22:43 01_users*
-rwxr-xr-x 1 root root 835 Feb 17 22:43 08_fallback_counting*
-rwxr-xr-x 1 root root 11771 Feb 17 22:43 10_linux*
-rwxr-xr-x 1 root root 833 Feb 17 22:43 10_reset_boot_success*
-rwxr-xr-x 1 root root 892 Feb 17 22:43 12_menu_auto_hide*
-rwxr-xr-x 1 root root 410 Feb 17 22:43 14_menu_show_once*
-rwxr-xr-x 1 root root 12285 Feb 17 22:43 20_linux_xen*
-rwxr-xr-x 1 root root 2562 Feb 17 22:43 20_ppc_terminfo*
-rwxrwxr-x 1 root root 504 Sep 9 2019 25_sysresccd*
-rwxr-xr-x 1 root root 10673 Feb 17 22:43 30_os-prober*
-rwxr-xr-x 1 root root 1415 Feb 17 22:43 30_uefi-firmware*
-rwxr-xr-x 1 root root 218 Feb 17 22:43 40_custom*
-rwxr-xr-x 1 root root 220 Feb 17 22:43 41_custom*
-rw-r--r-- 1 root root 483 Feb 17 22:43 README

update-grub2
Generating grub configuration file ...
Found theme: /boot/grub2/themes/maggy/theme.txt
Found linux image: /boot/vmlinuz-5.10.33-desktop-1.mga8
Found initrd image: /boot/initrd-5.10.33-desktop-1.mga8.img
Found linux image: /boot/vmlinuz-5.10.16-desktop-1.mga8
Found initrd image: /boot/initrd-5.10.16-desktop-1.mga8.img
Found linux image: /boot/vmlinuz-desktop
Found initrd image: /boot/initrd-desktop.img
Found Mageia 8 (8) on /dev/nvme0n1p2
Found Mageia 6 (6) on /dev/nvme0n1p7
Adding boot menu entry for EFI firmware configuration
done

grub2-install
Installing for x86_64-efi platform.
Installation finished. No error reported.

I rebooted and let the boot fall through unhindered. I did not change
the partition selection- just to be clear on that

The outcome

systemrescuecd is listed in the boot menu

A little win there :-)

Unfortunately the boot text and the kernel boot messages are still large
font

The same release did reboot

cat /etc/issue
Mageia release 8 (Official) for x86_64
Kernel 5.10.33-desktop-1.mga8 on an 8-processor x86_64 / \l

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-7-x86_64-DVD.iso

Re: update-grub2 boot menu and stuff

<slrns9q2pf.21s7b.BitTwister@wb.home.test>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3632&group=alt.os.linux.mageia#3632

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: BitTwis...@mouse-potato.com (Bit Twister)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Thu, 13 May 2021 06:19:09 -0500
Organization: A noiseless patient Spider
Lines: 75
Message-ID: <slrns9q2pf.21s7b.BitTwister@wb.home.test>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test> <s7hgtu$aqs$1@dont-email.me>
<slrns9olkm.1ppqm.BitTwister@wb.home.test> <s7ip37$jv4$1@dont-email.me>
Injection-Info: reader02.eternal-september.org; posting-host="4b45ff8289593a43c7a339cd6b953292";
logging-data="2570"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19NUxFWQeDkhTKgRYlrF+Suzh0FyZ34TgM="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:7FSBzXto9naIMwOsYIuj++4p2qM=
 by: Bit Twister - Thu, 13 May 2021 11:19 UTC

On Thu, 13 May 2021 18:47:32 +1000, faeychild wrote:
> On 13/5/21 8:28 am, Bit Twister wrote:
>
>>
>> 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
>>
>
>
>
> I have booted Mageia 8
>
>
> cat /etc/issue
> Mageia release 8 (Official) for x86_64
> Kernel 5.10.33-desktop-1.mga8 on an 8-processor x86_64 / \l
>
> [root@unimatrix ~]# cat /etc/default/grub

> GRUB_GFXMODE=1920x1080x24

On one of your boots you indicated small font instead of the
current large font. You would need to copy those from that boot's
/etc/default/grub into this boot's /etc/default/grub
and run update-grub2. I will guess there is no requirement to
run grub2-install

********** WARNING *************
The warranty and liability expired as you read this message.
If the following breaks your system, it's yours and you keep both pieces.

To set small font boot info/menu I have
$ grep GRUB_GF /etc/default/grub
GRUB_GFXMODE=1280x1024x32
GRUB_GFXPAYLOAD_LINUX=1280x1024x32

guessing that you need to change x24 to x32 since your
monitor/display is much better than mine.

#**********************************************************
#* You damn sure better have a bootable systenrescue media.
#**********************************************************

dinking with GFXMODE/GRUB_GFXPAYLOAD_LINUX might cause grub2
to abort and leave you with no means of booting anything.

In this kind of situation you would boot the install cd in the
Rescue mode to reinstall the bootloader, pick the old release
That will get a grub menu. You boot the old install, run update-grub
to pick up the new release. Now you can boot the new release and
dink with /etc/default/grub, update-grub, grub-install and try again.

Having a standalone bootable systenrescue media would allow you
to back out your changes that are broke in the event you completely
mess up both old and new install.

The bad news is I do not have the commands to chroot the install
and do the grub update/install.

> grub2-install

I am impressed because I thought grub2-install required where the
bootloader was to be installed.

> Installing for x86_64-efi platform.
> Installation finished. No error reported.

Ok, guessing an efi bootloader does not require you to enter
a location.

Re: update-grub2 boot menu and stuff

<s7kc0p$ndc$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3644&group=alt.os.linux.mageia#3644

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: faeych...@nomail.afraid.org (faeychild)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Fri, 14 May 2021 09:16:32 +1000
Organization: A noiseless patient Spider
Lines: 130
Message-ID: <s7kc0p$ndc$1@dont-email.me>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test> <s7hgtu$aqs$1@dont-email.me>
<slrns9olkm.1ppqm.BitTwister@wb.home.test> <s7ip37$jv4$1@dont-email.me>
<slrns9q2pf.21s7b.BitTwister@wb.home.test>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 13 May 2021 23:16:41 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="87e21b80e8047e5707d5ea14529254a1";
logging-data="23980"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+ZmU0MqGBt+uInn6yv6ThnpNXMFOmuzpA="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
Thunderbird/78.10.0
Cancel-Lock: sha1:bctJqjVsmKAoOHNmZM8jD5cw3Zo=
In-Reply-To: <slrns9q2pf.21s7b.BitTwister@wb.home.test>
Content-Language: en-US
 by: faeychild - Thu, 13 May 2021 23:16 UTC

On 13/5/21 9:19 pm, Bit Twister wrote:

>>
>> I have booted Mageia 8
>>
>>
>> cat /etc/issue
>> Mageia release 8 (Official) for x86_64
>> Kernel 5.10.33-desktop-1.mga8 on an 8-processor x86_64 / \l
>>
>> [root@unimatrix ~]# cat /etc/default/grub
>
>> GRUB_GFXMODE=1920x1080x24
>
> On one of your boots you indicated small font instead of the
> current large font. You would need to copy those from that boot's
> /etc/default/grub into this boot's /etc/default/grub
> and run update-grub2. I will guess there is no requirement to
> run grub2-install
>
> ********** WARNING *************
> The warranty and liability expired as you read this message.
> If the following breaks your system, it's yours and you keep both pieces.
>
>
> To set small font boot info/menu I have
> $ grep GRUB_GF /etc/default/grub
> GRUB_GFXMODE=1280x1024x32

This was all that it used to need to switch to the high res font and now
it doesn't work

> GRUB_GFXPAYLOAD_LINUX=1280x1024x32
>
> guessing that you need to change x24 to x32 since your
> monitor/display is much better than mine.

It can be 24 or 32 depending on the installation and that Nvidia driver.

It is not satisfactory

>
> #**********************************************************
> #* You damn sure better have a bootable systenrescue media.
> #**********************************************************
>
> dinking with GFXMODE/GRUB_GFXPAYLOAD_LINUX might cause grub2
> to abort and leave you with no means of booting anything.

gfxpayload never used to be involved in this palaver

>
> In this kind of situation you would boot the install cd in the
> Rescue mode to reinstall the bootloader, pick the old release
> That will get a grub menu. You boot the old install, run update-grub
> to pick up the new release. Now you can boot the new release and
> dink with /etc/default/grub, update-grub, grub-install and try again.
>
> Having a standalone bootable systenrescue media would allow you
> to back out your changes that are broke in the event you completely
> mess up both old and new install.
>
> The bad news is I do not have the commands to chroot the install
> and do the grub update/install.
>

The current systemrescue partition does not work. Once it starts up it
complains of not being able to find its own files. This is an old
problem which I think you solved long ago with linking.
I have forgotten what I did

So I think installing systemrescue on a stick, while not as elegant,
is much easier.

I have never actually used a rescue disk. My understanding was that you
run the rescue. Use fdisk to ID the partition. then mount it and cd into
the mount point and away you go. But reinstalling bootloaders and
chrooting is out of my pay grade

The other view is the with the reinstalling taking only a few minutes,
is it worth the time dinking about with rescue disk.

Or as you have said Rsync your last backup onto the offending partition
and away you go. It makes far more sense to do it that way

So why haven't I Why dont I ??

>
>
>> grub2-install
>
> I am impressed because I thought grub2-install required where the
> bootloader was to be installed.
>
>> Installing for x86_64-efi platform.
>> Installation finished. No error reported.
>
> Ok, guessing an efi bootloader does not require you to enter
> a location.
>

The arrangement is very erratic currently

I have the printer and scanner running on MGA6.

I have them running on the test MGA8 partition

I can't get xsane to run on production MGA8

And along with the the 640x480 size boot font, it's been a
glaring at the monitor and WTF time. :-)

All this could be some interaction with all the grub defaults and
grub.d's on all the partitions. Maybe update-grub is lost down the
rabbit hole because I remember seeing the systemrescue entry in grub.cfg
on the partition I was booting but it would not show on the boot menu.

I could go crazy, reformat everything and install one only

Still
I'll download the new sysrescue iso and rustle up a stick

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

Re: update-grub2 boot menu and stuff

<s7kii8$p0h$3@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3650&group=alt.os.linux.mageia#3650

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: unr...@invalid.ca (William Unruh)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Fri, 14 May 2021 01:08:24 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 14
Message-ID: <s7kii8$p0h$3@dont-email.me>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test> <s7hgtu$aqs$1@dont-email.me>
<slrns9olkm.1ppqm.BitTwister@wb.home.test> <s7ip37$jv4$1@dont-email.me>
<slrns9q2pf.21s7b.BitTwister@wb.home.test> <s7kc0p$ndc$1@dont-email.me>
Injection-Date: Fri, 14 May 2021 01:08:24 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="683cc75c752413a672b84a97210f39e2";
logging-data="25617"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18S0f8qoz5ffPC07JaUBpsI"
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:y2rMWNflxWYbfZi2O98jk5YIY9I=
 by: William Unruh - Fri, 14 May 2021 01:08 UTC

On 2021-05-13, faeychild <faeychild@nomail.afraid.org> wrote:
>
> The arrangement is very erratic currently
>
> I have the printer and scanner running on MGA6.
>
> I have them running on the test MGA8 partition
>
> I can't get xsane to run on production MGA8

xsane does run on my Mga8. It keeps finding my Logitech webcam as its
choice for the xsane device, but does give my Epson 1660 as an option,
so it works.

Re: update-grub2 boot menu and stuff

<s7kkvq$kur$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3651&group=alt.os.linux.mageia#3651

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: faeych...@nomail.afraid.org (faeychild)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Fri, 14 May 2021 11:49:40 +1000
Organization: A noiseless patient Spider
Lines: 27
Message-ID: <s7kkvq$kur$1@dont-email.me>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test> <s7hgtu$aqs$1@dont-email.me>
<slrns9olkm.1ppqm.BitTwister@wb.home.test> <s7ip37$jv4$1@dont-email.me>
<slrns9q2pf.21s7b.BitTwister@wb.home.test> <s7kc0p$ndc$1@dont-email.me>
<s7kii8$p0h$3@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 14 May 2021 01:49:46 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="87e21b80e8047e5707d5ea14529254a1";
logging-data="21467"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+bR21TgFtcVyS238QZ4XAzr8g9+9/+L4E="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
Thunderbird/78.10.0
Cancel-Lock: sha1:MnlFU8olYFGDoUiJ0a+H3DW5gys=
In-Reply-To: <s7kii8$p0h$3@dont-email.me>
Content-Language: en-US
 by: faeychild - Fri, 14 May 2021 01:49 UTC

On 14/5/21 11:08 am, William Unruh wrote:

>
> xsane does run on my Mga8. It keeps finding my Logitech webcam as its
> choice for the xsane device, but does give my Epson 1660 as an option,
> so it works.
>

scanner was installed under MCC (experimental procedure) and since then
it has failed to operate and reinstalling xsane does not work.
I suspect that the original install (MCC) left something nasty behind
that trashes the xsane installtion.

I could use "find" and remove every mention of "scan" which would also
take out he scanner drivers and it becomes a shadow chase.

Whereas a simple backup of essential files and reinstall may solve
everything

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-7-x86_64-DVD.iso

Re: update-grub2 boot menu and stuff

<slrns9rpho.239r1.BitTwister@wb.home.test>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3652&group=alt.os.linux.mageia#3652

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: BitTwis...@mouse-potato.com (Bit Twister)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Thu, 13 May 2021 21:53:39 -0500
Organization: A noiseless patient Spider
Lines: 135
Message-ID: <slrns9rpho.239r1.BitTwister@wb.home.test>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test> <s7hgtu$aqs$1@dont-email.me>
<slrns9olkm.1ppqm.BitTwister@wb.home.test> <s7ip37$jv4$1@dont-email.me>
<slrns9q2pf.21s7b.BitTwister@wb.home.test> <s7kc0p$ndc$1@dont-email.me>
Injection-Info: reader02.eternal-september.org; posting-host="a72e18840b12bb3c946a8872ee2ed651";
logging-data="28050"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19O84coj0QGahv7Twr/Lkkj1Kpo8znQDFg="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:/bJLGAbi6J8BMWzt081ntTxoFos=
 by: Bit Twister - Fri, 14 May 2021 02:53 UTC

On Fri, 14 May 2021 09:16:32 +1000, faeychild wrote:
> On 13/5/21 9:19 pm, Bit Twister wrote:
>

>>
>> To set small font boot info/menu I have
>> $ grep GRUB_GF /etc/default/grub
>> GRUB_GFXMODE=1280x1024x32
>
> This was all that it used to need to switch to the high res font and now
> it doesn't work

I understand, I have both because I want to to see boot
messages in a small font let alone the menu.

>>
>> guessing that you need to change x24 to x32 since your
>> monitor/display is much better than mine.
>
> It can be 24 or 32 depending on the installation and that Nvidia driver.

Ah so I see says the blind man. I am going to guess you have
picked a video setting that requires the Nvidia driver but
it is not installed yet.

You will need to start the grub boot, hit Esc key and have grub
dump resolution values it will use.

>
> It is not satisfactory

Snippet from my brain book follows:

[bittwister@wb work]$ uh grub

_grub_command_video_monitor_ grub> vbeinfo
_grub_command_video_monitor_ grub> set gfxpayload=1680x1050

Been awhile since I been in grub command line. I think bottom
of screen indicates Ctl+x to continue.
>
>> GRUB_GFXPAYLOAD_LINUX=1280x1024x32

>>
>> dinking with GFXMODE/GRUB_GFXPAYLOAD_LINUX might cause grub2
>> to abort and leave you with no means of booting anything.
>
> gfxpayload never used to be involved in this palaver

But if your boot hangs you might want small font for the
boot messages

>>
>
> The current systemrescue partition does not work. Once it starts up it
> complains of not being able to find its own files. This is an old
> problem which I think you solved long ago with linking.
> I have forgotten what I did

That is why you put the changes/commands in a script to
run after install, or you keep an admin diary with
who, what, when, where what was before/after was done.
My guess is I mounted the iso on loop back, and used lsblk to
get the label name for the link used in the grub staza.
Current values of
# mount_iso systemrescue-8.03-amd64.iso

# lsblk -o NAME,TYPE,FSTYPE,MOUNTPOINT,SIZE,FSAVAIL,FSUSED,LABEL,PARTLABEL /dev/loop0
NAME TYPE FSTYPE MOUNTPOINT SIZE FSAVAIL FSUSED LABEL PARTLABEL
loop0 loop iso9660 /iso 717M 0 717M RESCUE803
>
> So I think installing systemrescue on a stick, while not as elegant,
> is much easier.
>
> I have never actually used a rescue disk. My understanding was that you
> run the rescue. Use fdisk to ID the partition. then mount it and cd into
> the mount point and away you go. But reinstalling bootloaders and
> chrooting is out of my pay grade
>
> The other view is the with the reinstalling taking only a few minutes,
> is it worth the time dinking about with rescue disk.

I can recommend having a hard copy of the system partition
information. Currently I have saved the output of

# blkid -s device -s LABEL -s TYPE -s PARTLABEL | sort -V
and
# gdisk -l /dev/sda

>
> The arrangement is very erratic currently
>
> I have the printer and scanner running on MGA6.
>
> I have them running on the test MGA8 partition
>
> I can't get xsane to run on production MGA8

Grub should have no impact on xsane.

>
> And along with the the 640x480 size boot font, it's been a
> glaring at the monitor and WTF time. :-)
>
> All this could be some interaction with all the grub defaults and
> grub.d's on all the partitions. Maybe update-grub is lost down the
> rabbit hole because I remember seeing the systemrescue entry in grub.cfg
> on the partition I was booting but it would not show on the boot menu.
>
> I could go crazy, reformat everything and install one only

I see no change in using that methodology.
I has to be some problem in the setup.
We have been in this conversation in another thread where I
indicated what I did for setting up my scanner/printer.

> Still
> I'll download the new sysrescue iso and rustle up a stick

Ok, in the mean time, make a hard copy of your setup.
Boot the Classic Iso dvd. Use the Rescue option and just look
at how it works.

At the which partition to use, you may have to hit the
power/reset button to get loose from the rescue mode
of the Classic DVD.

Re: update-grub2 boot menu and stuff

<s7l0ji$61a$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3653&group=alt.os.linux.mageia#3653

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: faeych...@nomail.afraid.org (faeychild)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Fri, 14 May 2021 15:07:53 +1000
Organization: A noiseless patient Spider
Lines: 147
Message-ID: <s7l0ji$61a$1@dont-email.me>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test> <s7hgtu$aqs$1@dont-email.me>
<slrns9olkm.1ppqm.BitTwister@wb.home.test> <s7ip37$jv4$1@dont-email.me>
<slrns9q2pf.21s7b.BitTwister@wb.home.test> <s7kc0p$ndc$1@dont-email.me>
<slrns9rpho.239r1.BitTwister@wb.home.test>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 14 May 2021 05:08:02 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="87e21b80e8047e5707d5ea14529254a1";
logging-data="6186"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18e5Ch6b1MHCswO7GZLPoq0peNV9k/JhU0="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
Thunderbird/78.10.0
Cancel-Lock: sha1:v/d51w7mptMiaWq/8MBiSzlG8eM=
In-Reply-To: <slrns9rpho.239r1.BitTwister@wb.home.test>
Content-Language: en-US
 by: faeychild - Fri, 14 May 2021 05:07 UTC

On 14/5/21 12:53 pm, Bit Twister wrote:
> On Fri, 14 May 2021 09:16:32 +1000, faeychild wrote:
>> On 13/5/21 9:19 pm, Bit Twister wrote:
>>
>
>>>
>>> To set small font boot info/menu I have
>>> $ grep GRUB_GF /etc/default/grub
>>> GRUB_GFXMODE=1280x1024x32
>>
>> This was all that it used to need to switch to the high res font and now
>> it doesn't work
>
> I understand, I have both because I want to to see boot
> messages in a small font let alone the menu.

I agree. And that is how it used to be - for me. I didn't change
GRUB_GFXPAYLOAD_LINUX and I still had the boot menu and messages in
small font.

But with several installation partitions and running "update-grub" run
from then individually reset the font size to the point where I can't
change it. although each of the /etc/default/grubs has GFXMODE set to
the same high res. Running update-grub does not pick it up

I could give GRUB_GFXPAYLOAD_LINUX a try

The current "grub.cfg" entry says

if loadfont $font ; then
set gfxmode=1920x1080x24
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_AU
insmod gettext
fi

but then ignores it.

>
>>>
>>> guessing that you need to change x24 to x32 since your
>>> monitor/display is much better than mine.
>>
>> It can be 24 or 32 depending on the installation and that Nvidia driver.
>
>
> Ah so I see says the blind man. I am going to guess you have
> picked a video setting that requires the Nvidia driver but
> it is not installed yet.

No No To clarify. When I run the post configuration the graphic option
in defaulted to "monitor custom" and "resolution automatic".

My monitor model is not listed so I stick with plug and play. I have
tried the other options. :-(

And for resolution I select 1920x1080. There is only a choice for 24 bits.

After some time - months. I have found the monitor to be relisted as LG
Flatscreen and the colour set to 32 bit.

I "blamed" this on kernel and video driver upgrades because it certainly
wasn't me.

>
> You will need to start the grub boot, hit Esc key and have grub
> dump resolution values it will use.
>
>

>>
>> I have the printer and scanner running on MGA6.
>>
>> I have them running on the test MGA8 partition
>>
>> I can't get xsane to run on production MGA8
>
> Grub should have no impact on xsane.

Agreed

>
>>
>> And along with the the 640x480 size boot font, it's been a
>> glaring at the monitor and WTF time. :-)
>>
>> All this could be some interaction with all the grub defaults and
>> grub.d's on all the partitions. Maybe update-grub is lost down the
>> rabbit hole because I remember seeing the systemrescue entry in grub.cfg
>> on the partition I was booting but it would not show on the boot menu.
>>
>> I could go crazy, reformat everything and install one only
>
> I see no change in using that methodology.
> I has to be some problem in the setup.

Most definitely!

> We have been in this conversation in another thread where I
> indicated what I did for setting up my scanner/printer.

I have scanner working in mageia 8 test version

I have no scanner in mageia 8 production version

The only difference is, that in mageia production I attempted to install
the scanner from MCC. This did not work. And now attempting to run xsane
also fails. I don't know how to back out of the MCC scanner install. I
suspect some conflict with this and xsane
>
>
>
>> Still
>> I'll download the new sysrescue iso and rustle up a stick
>
>
> Ok, in the mean time, make a hard copy of your setup.
> Boot the Classic Iso dvd. Use the Rescue option and just look
> at how it works.
>
> At the which partition to use, you may have to hit the
> power/reset button to get loose from the rescue mode
> of the Classic DVD.
>

I don't have Classic CD but I tried from the stick, essentially the same
thing.

And it works well. It's quite intuitive. I mounted the partition had a
look through /etc and /boot. There should be no problem. I hope I never
have to use it :-)

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-7-x86_64-DVD.iso

Re: update-grub2 boot menu and stuff

<slrns9scb4.247v9.BitTwister@wb.home.test>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3654&group=alt.os.linux.mageia#3654

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: BitTwis...@mouse-potato.com (Bit Twister)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Fri, 14 May 2021 03:14:20 -0500
Organization: A noiseless patient Spider
Lines: 32
Message-ID: <slrns9scb4.247v9.BitTwister@wb.home.test>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test> <s7hgtu$aqs$1@dont-email.me>
<slrns9olkm.1ppqm.BitTwister@wb.home.test> <s7ip37$jv4$1@dont-email.me>
<slrns9q2pf.21s7b.BitTwister@wb.home.test> <s7kc0p$ndc$1@dont-email.me>
<slrns9rpho.239r1.BitTwister@wb.home.test> <s7l0ji$61a$1@dont-email.me>
Injection-Info: reader02.eternal-september.org; posting-host="a72e18840b12bb3c946a8872ee2ed651";
logging-data="13613"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18jVEMvZaJe9ApBk09LLmM4z+D5K9azG5A="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:YNN4Ilo+7LuKUhjfKBovcj6GacE=
 by: Bit Twister - Fri, 14 May 2021 08:14 UTC

On Fri, 14 May 2021 15:07:53 +1000, faeychild wrote:
> On 14/5/21 12:53 pm, Bit Twister wrote:

The Classic iso is the big dvd iso. not one of the live iso.

The monitor resolutions you see after boot are the ones the
Nvidia driver can use based on information pulled from your monitor.

You need to pick a value from the grub command line command vbeinfo

My hindbrain made me finally remember that the /etc/grub.d/ sysresccd
grub script did not use the downloaded iso name. Glancing at
my grub rescue script I see
loopback loop /systemrescuecd.iso
and looking in the directory where systemrescuecd iso is stored
I see
# ls -l systemrescue*
-rw-r--r-- 1 browser browser 751828992 May 12 17:03 systemrescue-8.03-amd64.iso
lrwxrwxrwx 1 root document 27 May 12 17:05 systemrescuecd.iso -> systemrescue-8.03-amd64.iso

That is the link that is needed by my grub.d script.

For burning the rescue cd to a usb thumb drive you need to use the
instructions from the https://www.system-rescue.org/Download/ page's
Installation on a USB stick or internal disk.
Clicking the USB stickslink gets you to
https://www.system-rescue.org/Installing-SystemRescue-on-a-USB-memory-stick/

Checking my faeychild file I notice I do not have what Mageia iso
was used in your Mageia 8 install. The Classic DVD Iso is Mageia-8-x86_64.iso
and is the one with the Rescue mode.

Re: update-grub2 boot menu and stuff

<s7lss3$q45$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3661&group=alt.os.linux.mageia#3661

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: faeych...@nomail.afraid.org (faeychild)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Fri, 14 May 2021 23:10:18 +1000
Organization: A noiseless patient Spider
Lines: 56
Message-ID: <s7lss3$q45$1@dont-email.me>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test> <s7hgtu$aqs$1@dont-email.me>
<slrns9olkm.1ppqm.BitTwister@wb.home.test> <s7ip37$jv4$1@dont-email.me>
<slrns9q2pf.21s7b.BitTwister@wb.home.test> <s7kc0p$ndc$1@dont-email.me>
<slrns9rpho.239r1.BitTwister@wb.home.test> <s7l0ji$61a$1@dont-email.me>
<slrns9scb4.247v9.BitTwister@wb.home.test>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 14 May 2021 13:10:27 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="87e21b80e8047e5707d5ea14529254a1";
logging-data="26757"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19a8NFVapNz/RFBEUJYIx5ebsrxtUgfyQw="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
Thunderbird/78.10.0
Cancel-Lock: sha1:K6zk71a7y32xFFYv/1bRZcmrUio=
In-Reply-To: <slrns9scb4.247v9.BitTwister@wb.home.test>
Content-Language: en-US
 by: faeychild - Fri, 14 May 2021 13:10 UTC

On 14/5/21 6:14 pm, Bit Twister wrote:
> On Fri, 14 May 2021 15:07:53 +1000, faeychild wrote:
>> On 14/5/21 12:53 pm, Bit Twister wrote:
>
> The Classic iso is the big dvd iso. not one of the live iso.
>
> The monitor resolutions you see after boot are the ones the
> Nvidia driver can use based on information pulled from your monitor.
>
> You need to pick a value from the grub command line command vbeinfo
>
> My hindbrain made me finally remember that the /etc/grub.d/ sysresccd
> grub script did not use the downloaded iso name. Glancing at
> my grub rescue script I see
> loopback loop /systemrescuecd.iso
> and looking in the directory where systemrescuecd iso is stored
> I see
> # ls -l systemrescue*
> -rw-r--r-- 1 browser browser 751828992 May 12 17:03 systemrescue-8.03-amd64.iso
> lrwxrwxrwx 1 root document 27 May 12 17:05 systemrescuecd.iso -> systemrescue-8.03-amd64.iso
>
> That is the link that is needed by my grub.d script.

That was it. As Max would say "The old shortened name trick"

>
> For burning the rescue cd to a usb thumb drive you need to use the
> instructions from the https://www.system-rescue.org/Download/ page's
> Installation on a USB stick or internal disk.
> Clicking the USB stickslink gets you to
> https://www.system-rescue.org/Installing-SystemRescue-on-a-USB-memory-stick/

I'm unaware of that one. I used isodumper to install sysrescuecd on
the USB stick

>
> Checking my faeychild file I notice I do not have what Mageia iso
> was used in your Mageia 8 install. The Classic DVD Iso is Mageia-8-x86_64.iso
> and is the one with the Rescue mode.
>

You are correct. I didn't notice the typo in the signature. It should
read "installed via Mageia-8-x86_64-DVD.iso"

Isodumper was used to copy the Mageia 8 dvd iso to a stick also

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

Re: update-grub2 boot menu and stuff

<slrns9t2a7.2br9d.BitTwister@wb.home.test>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3662&group=alt.os.linux.mageia#3662

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: BitTwis...@mouse-potato.com (Bit Twister)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Fri, 14 May 2021 09:29:27 -0500
Organization: A noiseless patient Spider
Lines: 23
Message-ID: <slrns9t2a7.2br9d.BitTwister@wb.home.test>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test> <s7hgtu$aqs$1@dont-email.me>
<slrns9olkm.1ppqm.BitTwister@wb.home.test> <s7ip37$jv4$1@dont-email.me>
<slrns9q2pf.21s7b.BitTwister@wb.home.test> <s7kc0p$ndc$1@dont-email.me>
<slrns9rpho.239r1.BitTwister@wb.home.test> <s7l0ji$61a$1@dont-email.me>
<slrns9scb4.247v9.BitTwister@wb.home.test> <s7lss3$q45$1@dont-email.me>
Injection-Info: reader02.eternal-september.org; posting-host="a72e18840b12bb3c946a8872ee2ed651";
logging-data="8302"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/0Fr0EasbmUog82wIGubhvGfsMVXTcbUo="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:Lm+YOWjT9Gyeeq/s8usH8jVoGKY=
 by: Bit Twister - Fri, 14 May 2021 14:29 UTC

On Fri, 14 May 2021 23:10:18 +1000, faeychild wrote:
> On 14/5/21 6:14 pm, Bit Twister wrote:

>>
>> For burning the rescue cd to a usb thumb drive you need to use the
>> instructions from the https://www.system-rescue.org/Download/ page's
>> Installation on a USB stick or internal disk.
>> Clicking the USB stickslink gets you to
>> https://www.system-rescue.org/Installing-SystemRescue-on-a-USB-memory-stick/
>
> I'm unaware of that one. I used isodumper to install sysrescuecd on
> the USB stick

What is really important is, does it boot and work on your system.

By the way, geany is an ASCII editor on the iso.

>
> You are correct. I didn't notice the typo in the signature. It should
> read "installed via Mageia-8-x86_64-DVD.iso"

And is still there on your reply. :)

Re: update-grub2 boot menu and stuff

<s7n072$kge$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3664&group=alt.os.linux.mageia#3664

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: faeych...@nomail.afraid.org (faeychild)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Sat, 15 May 2021 09:13:35 +1000
Organization: A noiseless patient Spider
Lines: 19
Message-ID: <s7n072$kge$1@dont-email.me>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test> <s7hgtu$aqs$1@dont-email.me>
<slrns9olkm.1ppqm.BitTwister@wb.home.test> <s7ip37$jv4$1@dont-email.me>
<slrns9q2pf.21s7b.BitTwister@wb.home.test> <s7kc0p$ndc$1@dont-email.me>
<slrns9rpho.239r1.BitTwister@wb.home.test> <s7l0ji$61a$1@dont-email.me>
<slrns9scb4.247v9.BitTwister@wb.home.test> <s7lss3$q45$1@dont-email.me>
<slrns9t2a7.2br9d.BitTwister@wb.home.test>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 14 May 2021 23:13:38 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="45db38cd233b052f96d576bb673671a8";
logging-data="21006"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18mY18Y9bFKiEtAPo8J53gBormyH1VkP8g="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
Thunderbird/78.10.0
Cancel-Lock: sha1:DXSlqYukn59n5dOh7W9XTF/cgrQ=
In-Reply-To: <slrns9t2a7.2br9d.BitTwister@wb.home.test>
Content-Language: en-US
 by: faeychild - Fri, 14 May 2021 23:13 UTC

On 15/5/21 12:29 am, Bit Twister wrote:
> On Fri, 14 May 2021 23:10:18 +1000, faeychild wrote:

>> You are correct. I didn't notice the typo in the signature. It should
>> read "installed via Mageia-8-x86_64-DVD.iso"
>
> And is still there on your reply. :)
>

Mea Culpa

I have your updated bash_profile .signature script around. I hope.

--
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

Re: update-grub2 boot menu and stuff

<s7nr9v$dl3$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3673&group=alt.os.linux.mageia#3673

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: faeych...@nomail.afraid.org (faeychild)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Sat, 15 May 2021 16:55:56 +1000
Organization: A noiseless patient Spider
Lines: 38
Message-ID: <s7nr9v$dl3$1@dont-email.me>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test> <s7hgtu$aqs$1@dont-email.me>
<slrns9olkm.1ppqm.BitTwister@wb.home.test> <s7ip37$jv4$1@dont-email.me>
<slrns9q2pf.21s7b.BitTwister@wb.home.test> <s7kc0p$ndc$1@dont-email.me>
<slrns9rpho.239r1.BitTwister@wb.home.test> <s7l0ji$61a$1@dont-email.me>
<slrns9scb4.247v9.BitTwister@wb.home.test> <s7lss3$q45$1@dont-email.me>
<slrns9t2a7.2br9d.BitTwister@wb.home.test>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sat, 15 May 2021 06:55:59 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="45db38cd233b052f96d576bb673671a8";
logging-data="13987"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18jegQYGSZMux3ZplupK27HOqM5yzxBs20="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
Thunderbird/78.10.0
Cancel-Lock: sha1:hVI6vBl1X7jC3vboRlDl34L/lII=
In-Reply-To: <slrns9t2a7.2br9d.BitTwister@wb.home.test>
Content-Language: en-US
X-Mozilla-News-Host: news://news.motzarella.org
 by: faeychild - Sat, 15 May 2021 06:55 UTC

On 15/5/21 12:29 am, Bit Twister wrote:

FWIW Bits

I changed both entries GFXMODE and GFXPAYLOAD in /etc/default/grub to
reflect the smaller text font for the boot menu and the kernel messages

GRUB_CMDLINE_LINUX_DEFAULT="nokmsboot noiswmd
resume=UUID=0f26b0d8-adf7-45cf-a963-cc5d89c1a8e4 audit=0 vga=791"
GRUB_DEFAULT=saved
GRUB_DISABLE_OS_PROBER=false
GRUB_DISABLE_RECOVERY=false
GRUB_DISABLE_SUBMENU=n
GRUB_DISTRIBUTOR=Mageia
GRUB_ENABLE_CRYPTODISK=y

GRUB_GFXMODE=1920x1080x32
GRUB_GFXPAYLOAD_LINUX=1920x1080x32

GRUB_SAVEDEFAULT=true
GRUB_TERMINAL_OUTPUT=gfxterm
GRUB_THEME=/boot/grub2/themes/maggy/theme.txt
GRUB_TIMEOUT=10

then ran update-gru2 and rebooted
and the text is still large 640x480 type

So.... Clearly the font size is influenced somewhere else.

He He You've gotta love stuff, Bits

--
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

Re: update-grub2 boot menu and stuff

<slrns9usmj.59j.BitTwister@wb.home.test>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3674&group=alt.os.linux.mageia#3674

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: BitTwis...@mouse-potato.com (Bit Twister)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Sat, 15 May 2021 02:05:55 -0500
Organization: A noiseless patient Spider
Lines: 40
Message-ID: <slrns9usmj.59j.BitTwister@wb.home.test>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test> <s7hgtu$aqs$1@dont-email.me>
<slrns9olkm.1ppqm.BitTwister@wb.home.test> <s7ip37$jv4$1@dont-email.me>
<slrns9q2pf.21s7b.BitTwister@wb.home.test> <s7kc0p$ndc$1@dont-email.me>
<slrns9rpho.239r1.BitTwister@wb.home.test> <s7l0ji$61a$1@dont-email.me>
<slrns9scb4.247v9.BitTwister@wb.home.test> <s7lss3$q45$1@dont-email.me>
<slrns9t2a7.2br9d.BitTwister@wb.home.test> <s7nr9v$dl3$1@dont-email.me>
Injection-Info: reader02.eternal-september.org; posting-host="0e8c0c363e26ccf93f1c17e7919fb7d3";
logging-data="10540"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+15gVOGMS2BmOYOvISxytCXv3DVKPuk54="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:Z5LFd28B7nZoMdMXC3T7hw8xBIY=
 by: Bit Twister - Sat, 15 May 2021 07:05 UTC

On Sat, 15 May 2021 16:55:56 +1000, faeychild wrote:
> On 15/5/21 12:29 am, Bit Twister wrote:
>
> FWIW Bits
>
> I changed both entries GFXMODE and GFXPAYLOAD in /etc/default/grub to
> reflect the smaller text font for the boot menu and the kernel messages
>
>
> GRUB_CMDLINE_LINUX_DEFAULT="nokmsboot noiswmd
> resume=UUID=0f26b0d8-adf7-45cf-a963-cc5d89c1a8e4 audit=0 vga=791"
> GRUB_DEFAULT=saved
> GRUB_DISABLE_OS_PROBER=false
> GRUB_DISABLE_RECOVERY=false
> GRUB_DISABLE_SUBMENU=n
> GRUB_DISTRIBUTOR=Mageia
> GRUB_ENABLE_CRYPTODISK=y
>
> GRUB_GFXMODE=1920x1080x32
> GRUB_GFXPAYLOAD_LINUX=1920x1080x32
>
> GRUB_SAVEDEFAULT=true
> GRUB_TERMINAL_OUTPUT=gfxterm
> GRUB_THEME=/boot/grub2/themes/maggy/theme.txt
> GRUB_TIMEOUT=10
>
> then ran update-gru2 and rebooted
> and the text is still large 640x480 type
>
> So.... Clearly the font size is influenced somewhere else.
>
> He He You've gotta love stuff, Bits

One more time. I believe what you are seeing is if grub can not get
the indicated/desired resolution so t will default to 640x480.

You have to use values given by the grub vbeinfo command.

Ignore that you can get more values after you log in.

Re: update-grub2 boot menu and stuff

<s7ph3q$4oi$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3692&group=alt.os.linux.mageia#3692

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: faeych...@nomail.afraid.org (faeychild)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Sun, 16 May 2021 08:14:16 +1000
Organization: A noiseless patient Spider
Lines: 37
Message-ID: <s7ph3q$4oi$1@dont-email.me>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test> <s7hgtu$aqs$1@dont-email.me>
<slrns9olkm.1ppqm.BitTwister@wb.home.test> <s7ip37$jv4$1@dont-email.me>
<slrns9q2pf.21s7b.BitTwister@wb.home.test> <s7kc0p$ndc$1@dont-email.me>
<slrns9rpho.239r1.BitTwister@wb.home.test> <s7l0ji$61a$1@dont-email.me>
<slrns9scb4.247v9.BitTwister@wb.home.test> <s7lss3$q45$1@dont-email.me>
<slrns9t2a7.2br9d.BitTwister@wb.home.test> <s7nr9v$dl3$1@dont-email.me>
<slrns9usmj.59j.BitTwister@wb.home.test>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sat, 15 May 2021 22:14:18 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="640cd0a5277a367a5f157c7f6cf3018a";
logging-data="4882"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18hTeuVJ6mtnctMLonbi1OmorlVJ6IUeq4="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
Thunderbird/78.10.0
Cancel-Lock: sha1:QDcbvkUxwBtEBFYY3vdcrmJZdyM=
In-Reply-To: <slrns9usmj.59j.BitTwister@wb.home.test>
Content-Language: en-US
X-Mozilla-News-Host: news://news.motzarella.org
 by: faeychild - Sat, 15 May 2021 22:14 UTC

On 15/5/21 5:05 pm, Bit Twister wrote:

> One more time. I believe what you are seeing is if grub can not get
> the indicated/desired resolution so t will default to 640x480.
>
> You have to use values given by the grub vbeinfo command.
>
> Ignore that you can get more values after you log in.
>

From the grub command line

vbeinfo does nothing

videoinfo produces

Adapter EFI GOP driver
640 x 480 x 32
800 x 600 32
1024 x 768 x 32
1280 x 1024 x 32
1920 x 1080 x 32

So I changed both GFXMODE and GFXPAYLOAD to 1280x1024x32
and ran update-grub2.

I now have smaller text, still spread across the monitor because the
kerning is large.

--
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

Re: update-grub2 boot menu and stuff

<slrnsa0k02.dbi.BitTwister@wb.home.test>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3693&group=alt.os.linux.mageia#3693

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: BitTwis...@mouse-potato.com (Bit Twister)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Sat, 15 May 2021 17:49:38 -0500
Organization: A noiseless patient Spider
Lines: 27
Message-ID: <slrnsa0k02.dbi.BitTwister@wb.home.test>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test> <s7hgtu$aqs$1@dont-email.me>
<slrns9olkm.1ppqm.BitTwister@wb.home.test> <s7ip37$jv4$1@dont-email.me>
<slrns9q2pf.21s7b.BitTwister@wb.home.test> <s7kc0p$ndc$1@dont-email.me>
<slrns9rpho.239r1.BitTwister@wb.home.test> <s7l0ji$61a$1@dont-email.me>
<slrns9scb4.247v9.BitTwister@wb.home.test> <s7lss3$q45$1@dont-email.me>
<slrns9t2a7.2br9d.BitTwister@wb.home.test> <s7nr9v$dl3$1@dont-email.me>
<slrns9usmj.59j.BitTwister@wb.home.test> <s7ph3q$4oi$1@dont-email.me>
Injection-Info: reader02.eternal-september.org; posting-host="748e97ba7a986e8f2d4997d1744191f0";
logging-data="13188"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/4+2w7JeeooC/qrf+j3c6WF52WeFcCOj8="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:u0+/xiuFE58afLs19xG+9SCA/BM=
 by: Bit Twister - Sat, 15 May 2021 22:49 UTC

On Sun, 16 May 2021 08:14:16 +1000, faeychild wrote:

>
> From the grub command line
>
> vbeinfo does nothing
>
> videoinfo produces

Thank you for the feedback. I had not done the command in years.

>
> Adapter EFI GOP driver
> 640 x 480 x 32
> 800 x 600 32
> 1024 x 768 x 32
> 1280 x 1024 x 32
> 1920 x 1080 x 32
>
> So I changed both GFXMODE and GFXPAYLOAD to 1280x1024x32
> and ran update-grub2.
>
> I now have smaller text, still spread across the monitor because the
> kerning is large.

I would have tried the 1920x1080x32 in that case.

Re: update-grub2 boot menu and stuff

<s7pkod$oub$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3694&group=alt.os.linux.mageia#3694

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: faeych...@nomail.afraid.org (faeychild)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Sun, 16 May 2021 09:16:24 +1000
Organization: A noiseless patient Spider
Lines: 20
Message-ID: <s7pkod$oub$1@dont-email.me>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test> <s7hgtu$aqs$1@dont-email.me>
<slrns9olkm.1ppqm.BitTwister@wb.home.test> <s7ip37$jv4$1@dont-email.me>
<slrns9q2pf.21s7b.BitTwister@wb.home.test> <s7kc0p$ndc$1@dont-email.me>
<slrns9rpho.239r1.BitTwister@wb.home.test> <s7l0ji$61a$1@dont-email.me>
<slrns9scb4.247v9.BitTwister@wb.home.test> <s7lss3$q45$1@dont-email.me>
<slrns9t2a7.2br9d.BitTwister@wb.home.test> <s7nr9v$dl3$1@dont-email.me>
<slrns9usmj.59j.BitTwister@wb.home.test> <s7ph3q$4oi$1@dont-email.me>
<slrnsa0k02.dbi.BitTwister@wb.home.test>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sat, 15 May 2021 23:16:29 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="640cd0a5277a367a5f157c7f6cf3018a";
logging-data="25547"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19Sw6a482IeqW+7l6UASb/uWcmJfF5T1xs="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
Thunderbird/78.10.0
Cancel-Lock: sha1:/9i+BULW9ovxh1jlpzKu/PhdxQk=
In-Reply-To: <slrnsa0k02.dbi.BitTwister@wb.home.test>
Content-Language: en-US
 by: faeychild - Sat, 15 May 2021 23:16 UTC

On 16/5/21 8:49 am, Bit Twister wrote:

>>
>> So I changed both GFXMODE and GFXPAYLOAD to 1280x1024x32
>> and ran update-grub2.
>>
>> I now have smaller text, still spread across the monitor because the
>> kerning is large.
>
> 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
--
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

Re: update-grub2 boot menu and stuff

<s7poos$e84$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=3695&group=alt.os.linux.mageia#3695

 copy link   Newsgroups: alt.os.linux.mageia
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: faeych...@nomail.afraid.org (faeychild)
Newsgroups: alt.os.linux.mageia
Subject: Re: update-grub2 boot menu and stuff
Date: Sun, 16 May 2021 10:25:00 +1000
Organization: A noiseless patient Spider
Lines: 27
Message-ID: <s7poos$e84$1@dont-email.me>
References: <s7fe2m$c7q$1@dont-email.me>
<slrns9mi2s.1gqec.BitTwister@wb.home.test> <s7hgtu$aqs$1@dont-email.me>
<slrns9olkm.1ppqm.BitTwister@wb.home.test> <s7ip37$jv4$1@dont-email.me>
<slrns9q2pf.21s7b.BitTwister@wb.home.test> <s7kc0p$ndc$1@dont-email.me>
<slrns9rpho.239r1.BitTwister@wb.home.test> <s7l0ji$61a$1@dont-email.me>
<slrns9scb4.247v9.BitTwister@wb.home.test> <s7lss3$q45$1@dont-email.me>
<slrns9t2a7.2br9d.BitTwister@wb.home.test> <s7nr9v$dl3$1@dont-email.me>
<slrns9usmj.59j.BitTwister@wb.home.test> <s7ph3q$4oi$1@dont-email.me>
<slrnsa0k02.dbi.BitTwister@wb.home.test> <s7pkod$oub$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 16 May 2021 00:25:01 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="640cd0a5277a367a5f157c7f6cf3018a";
logging-data="14596"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+CZmf1IRcLq3945ZIETJGl6JYrfNQT3Bs="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
Thunderbird/78.10.0
Cancel-Lock: sha1:ihCXluop3MfS2LHn3hPYWg4cpig=
In-Reply-To: <s7pkod$oub$1@dont-email.me>
Content-Language: en-US
 by: faeychild - Sun, 16 May 2021 00:25 UTC

On 16/5/21 9:16 am, faeychild wrote:
> On 16/5/21 8:49 am, Bit Twister wrote:
>
>>>
>>>    So I changed both GFXMODE and  GFXPAYLOAD to 1280x1024x32
>>> and ran update-grub2.
>>>
>>> I now have smaller text, still spread across the monitor because the
>>> kerning is large.
>>
>> 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

This guy struck the same effect 8 years ago

https://askubuntu.com/questions/206967/why-isnt-grub2-using-custom-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

Pages:12
server_pubkey.txt

rocksolid light 0.9.7
clearnet tor