Bug 30546

Summary:	grub config
Product:	Mageia	Reporter:	Mészáros Csaba <csablak>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	Normal	CC:	csablak, fri, mageiatools, thierry.vignaud
Version:	8	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Mészáros Csaba 2022-06-14 10:54:45 CEST

Hi guys!
I set things up in /etc/default/grub for myself, but a new kernel update smoothly overwrote the comments and made the file executable for some reason.
I call this a mistake. 
Is there anything you can do about it? Anyway, I have a couple of files that get executable rights, even though you don't need them.
Just look in the /etc/sysconfig folder. Although there are also files whose role is already questionable.
Is there anyone reviewing these?

Regards: Csaba

oops. and here it comes to mind. I tried the c command in the grub launcher. So I was in a grub shell.
Interestingly, the ls command lists the partitions (hd0), (hd0, msdos6), etc. it also wrote gpt partitions as msdos, but if I wanted to list the contents of (hd0, msdos6), it was written as an unknown file system. ????

Mészáros Csaba 2022-06-14 10:55:02 CEST

CC: (none) => csablak

Comment 1 Morgan Leijström 2022-06-15 09:54:39 CEST

CC people who knows this best.

CC: (none) => fri, mageiatools

Comment 2 Thierry Vignaud 2022-06-15 16:18:19 CEST

What did you change in /etc/default/grub and what was removed by the kernel update?

CC: (none) => thierry.vignaud
Keywords: (none) => NEEDINFO

Comment 3 Mészáros Csaba 2022-06-15 17:16:54 CEST

In the end nothing changed that was sharp, but since I just experimented a bit to get the framebuffer to pick up the right resolution, I added a # sign to some of the entries to try these out and see what it does.

For example:
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
# GRUB_GFXMODE=1920x1080-32
GRUB_GFXMODE=auto

Of these, only the last entry remains.

Comment 4 Thierry Vignaud 2022-06-15 21:52:48 CEST

It's "normal" for the comments to disapear the way we update the config file.
Does the uncommented "GRUB_GFXMODE=auto" disappeared or only your comments?
If only the comments you can workaround this just by adding:
"GRUB_GFXMODE_backup=1920x1080-32"

Comment 5 Lewis Smith 2022-12-13 21:17:35 CET

(In reply to Thierry Vignaud from comment #4)
> It's "normal" for the comments to disapear the way we update the config file.
> Does the uncommented "GRUB_GFXMODE=auto" disappeared or only your comments?
(In reply to Mészáros Csaba from comment #3)
> For example:
> # The resolution used on graphical terminal
> # note that you can use only modes which your graphic card supports via VBE
> # you can see them in real GRUB with the command 'videoinfo'
> # GRUB_GFXMODE=1920x1080-32
> GRUB_GFXMODE=auto
> 
> Of these, only the last entry remains.
I think answers tv's question. Moreover, his suggestion:
> If only the comments you can workaround this just by adding:
> "GRUB_GFXMODE_backup=1920x1080-32"
offers an elegant catch-all.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME