Bug 24724

Summary: VGACON AMDGPU modesetting conflict error message with normal boot, GUI works fine with recovery mode boot
Product: Mageia Reporter: Brian McNeil <bcm.alaska>
Component: RPM PackagesAssignee: Kernel and Drivers maintainers <kernel>
Status: NEW --- QA Contact:
Severity: major    
Priority: Normal CC: bulletfreak, marja11, tmb
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: x11-driver-video-amdgpu CVE:
Status comment:

Description Brian McNeil 2019-04-27 01:32:19 CEST
Description of problem:
No graphical mode when a normal boot is attempted, the boot ends with;[drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
If recovery mode is selected at boot, after ctrl-d to continue is input, everything works fine.

Version-Release number of selected component (if applicable):
This is a AMD RX 590 video card.

How reproducible:
Every time.

Steps to Reproduce:
1.A normal boot results in text mode only, startx will fail if attempted from a F2 login. The error message listed in the description will appear.
2. Recovery mode works everytime. Just use cntl-d to continue the boot.
3.

This was from a fresh cauldron install on new hardware. It has been this way awhile. I was away from my computer for about a month traveling, it was doing this before I left, and it's still doing it now after updating.
Comment 1 Thomas Backlund 2019-04-27 08:52:48 CEST
Is there a "nokmsboot" on the kernel command line ?
If so, remove that and try to boot again

CC: (none) => tmb

Comment 2 Brian McNeil 2019-04-27 15:47:25 CEST
Yes, there was "nokmsboot" and removing it did result in a successful boot. I'm not sure why nokmsboot would be there, as I understand from the errata that Mageia 7 won't be compatible with the AMD propitiatory driver anyway.
Marja Van Waes 2019-04-29 08:23:47 CEST

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

Comment 3 Brian McNeil 2019-04-30 00:05:54 CEST
The problem did not reappear after today's kernel upgrade reboot, so maybe the addition of nokmsboot was a one time problem.
Comment 4 Dusk Mourn 2019-12-22 12:37:13 CET
Confirming that this still happens with the amdgpu driver and the current latest kernel version of "5.4.5-desktop-1.mga8" when I boot into a fresh Cauldron install for the first time. Removing "nokmsboot" from the grub kernel line in /etc/default/grub fixes it as others have reported.

CC: (none) => bulletfreak