Bug 17585

Summary: kernel update corrupts /etc/default/grub when Nvidia driver used
Product: Mageia Reporter: T ex78 <jTrex>
Component: RPM PackagesAssignee: Kernel and Drivers maintainers <kernel>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: anaselli, mageiatools, marja11, thierry.vignaud, zen25000
Version: 5   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: drakxtools, bootloader-utils CVE:
Status comment:
Attachments: Syslog entries for jan 21 updates

Description T ex78 2016-01-23 09:22:33 CET 
Description of problem:

Recently installed Nvidia driver for video card :
NVIDIA GeForce 8100 to GeForce 415: NVIDIA Corporation|GT200 [GeForce GTX 260] [DISPLAY_VGA] (vendor:10de device:05e2 subv:10de subd:0585) (rev: a1)
Compiz activated too.
This configuration needs "nokmsboot" kernel parameter to boot, so I added a line
GRUB_CMDLINE_LINUX_DEFAULT=" nokmsboot splash=verbose vga=795" to /etc/default/grub, and ran grub2.mkconfig.
Works well, "nokmsboot" appears in /boot/grub2/grub.cfg, and computer boots without problems.

But when a kernel update occurs, next boot fails with a message saying something like (sorry, didn't write the exact message) :
"Video driver modified, reboot or continue"
Rebooting gives nothing more
Continuing finally boots, but staying in command line. Manual xorg start fails.

Checking /boot/grub2/grub.cfg shows my GRUB_CMDLINE_LINUX_DEFAULT parameters disappeared from linux entries.
Manually adding "nokmsboot" allows to boot without error.

In fact, /etc/default/grub file seems recreated during update, and my GRUB_CMDLINE_LINUX_DEFAULT line disappeared (but I changed GRUB_TIMEOUT to 30 too, and this has been kept ? )

My original /etc/default/grub :

GRUB_TERMINAL_OUTPUT=gfxterm
GRUB_DISABLE_RECOVERY=false
GRUB_ENABLE_CRYPTODISK=y
GRUB_DISABLE_SUBMENU=n
GRUB_GFXMODE=1024x768x32
GRUB_DISABLE_OS_PROBER=true
GRUB_GFXPAYLOAD_LINUX=text
GRUB_DISTRIBUTOR=Mageia
GRUB_TIMEOUT=30
GRUB_THEME=/boot/grub2/themes/maggy/theme.txt
GRUB_CMDLINE_LINUX_DEFAULT=" nokmsboot splash=verbose vga=795

After kernel update :

GRUB_DISABLE_OS_PROBER=true
GRUB_ENABLE_CRYPTODISK=y
GRUB_DISABLE_SUBMENU=n
GRUB_THEME=/boot/grub2/themes/maggy/theme.txt
GRUB_DISABLE_RECOVERY=false
GRUB_GFXPAYLOAD_LINUX=text
GRUB_GFXMODE=1024x768x32
GRUB_TERMINAL_OUTPUT=gfxterm
GRUB_TIMEOUT=30
GRUB_DISTRIBUTOR=Mageia

This happened at least 2 times, last on jan 21.

Version-Release number of selected component (if applicable):


How reproducible:
Depends if kernel updates occurs

Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 T ex78 2016-01-23 09:26:36 CET 
Created attachment 7375 [details]
Syslog entries for jan 21 updates
Thierry Vignaud 2016-01-23 21:51:51 CET

CC: (none) => thierry.vignaud, zen25000

Comment 2 Barry Jackson 2016-01-24 01:38:47 CET 
Your original line seems to be missing a closing " - unless that was just a bad copy/paste?

GRUB_CMDLINE_LINUX_DEFAULT=" nokmsboot splash=verbose vga=795
Comment 3 T ex78 2016-01-24 07:57:31 CET 
Your're right : it's a copy/paste error, closing " is present.
Anyway, removing it fails :
# grub2-mkconfig
/etc/default/grub: ligne 11: caractère de fin de fichier (EOF) prématuré lors de la recherche du « " » correspondant
( 'premature EOF char when searching matching « " »' )
Marja Van Waes 2016-02-14 11:42:40 CET

CC: (none) => marja11
Assignee: bugsquad => tmb

Comment 4 Marja Van Waes 2016-08-26 11:43:04 CEST 
Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.

Assignee: tmb => kernel

Comment 5 Thierry Vignaud 2016-08-26 11:51:00 CEST 
This one has been fixed in cauldron (future mga6) where grub2 support has been enhanced quite a lot.

Source RPM: kernel-desktop-4.1.15-2.mga5-1-1.mga5.x86_64 ; nvidia340-kernel-4.1.15-desktop-2.mga5-340.93-5.mga5.nonfree.x86_64 => drakxtools, bootloader-utils

Comment 6 Marja Van Waes 2016-08-26 12:21:47 CEST 
Thx, Thierry :-)

@ Angelo

CC'ing mageiatools group ml, but you're not a member of that list, yet https://ml.mageia.org/l/review/mageiatools
So CC'ing you, too, in case work on manaboot already started.

CC: (none) => anaselli, mageiatools

Comment 7 Marja Van Waes 2018-04-28 22:03:34 CEST 
Hi T ex78,

Thank you for having taken the needed time to report this issue!

We regret if this issue didn't get fixed in Mageia 5.

Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, but non-security bugs have no chance of still getting fixed.

I understand from comment #5 that this issue doesn't exist in Mageia 6, so closing this report.

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