Bug 28217

Summary: Unable to boot into system after updates and reboot as the display driver had changed
Product: Mageia Reporter: ian trump <chrisv11c>
Component: RPM PackagesAssignee: Kernel and Drivers maintainers <kernel>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: Normal CC: chrisv11c, ouaurelien, tmb
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description ian trump 2021-01-25 14:15:27 CET
Description of problem:

After installing major updates the system hangs while trying to reboot and told the display driver has changed.

 The system then refuses to go any further or even give a choice to select the correct driver. I have re-installed the O/S but have not done the updates.I have re -installed the O/S three times, once on a different hard drive and the same problem happens after the reboot from the updates.

It would appear the display driver has been changed because the correct drivers have not been included after the system updates. 

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

The Graphic card used is a Sapphire Tri-X R9 280X

Before the updates the display driver in the hardware section read: Module: ‎Card:ATI Radeon HD 6400 and later (radeon/fglrx)

Ater the updates and before rebooting the message read: Module : Card:ATI Volcanic Islands and later (amdgpu/fglrx)

How reproducible:
Tried on a different hard drive. Same problem.

Steps to Reproduce:
1.
2.
3.
ian trump 2021-01-25 14:15:37 CET

CC: (none) => chrisv11c

Comment 1 Aurelien Oudelet 2021-01-25 14:19:55 CET
Sorry for this kind of troubles.

Can you provide here the output of
$ lspcidrake -v | grep VGA

Mine returns for example:
Card:NVIDIA GeForce 635 series and later: NVIDIA Corporation|TU116 [GeForce GTX 1660 Ti] [DISPLAY_VGA] (vendor:10de device:2182 subv:1458 subd:3fc3) (rev: a1)

CC: (none) => ouaurelien

Comment 2 ian trump 2021-01-25 15:35:38 CET
I believe this is the information you require. 

Card:ATI Radeon HD 6400 and later (radeon/fglrx): Advanced Micro Devices, Inc. [AMD/ATI]|Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [DISPLAY_VGA] (vendor:1002 device:6798 subv:174b subd:3001)

I also use another Linux O/S, PClinux I have just had some major updates and the same has happened when I rebooted the O/S.
 I re-installed that that O/S and performed the their updates again but this I time went into their control center before rebooting (which is similar to mageia control center) and noticed after the update the display card had also been changed to the ATI Volcanic Islands and later (amdgpu/fglrx).

I then changed it back to the ATI Radeon HD 6400 and later (radeon/fglrx)
as it should be and rebooted the O/S. The O/S appeared to be configuring the display card on boot up then it did the same as before and refused to go any further.

This would be a problem for other linux O/S as well and not just mageia.
Comment 3 Aurelien Oudelet 2021-01-25 15:45:18 CET
Well,

Assigning to Kernel and Drivers maintainers.

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

Comment 4 Thomas Backlund 2021-01-25 17:39:59 CET
Yeah, I'm reverting the switch to amdgpu for now as it breaks working setups.

Will revisit that for mga9 if we can handle it better then
Comment 5 ian trump 2021-01-25 18:36:58 CET
I have had this problem happen to both Mageia and PClinux, so there must be a problem with a configuration file that effects both systems.

As far as I can see the updates I have recently performed through Mageia and PClinux makes it impossible to boot into either O/S and has broken both of them.

Until a fix is found I do not know what part of the updates is responsible for this problem so I can not update. 

I am not sure what you mean by reverting back to amdgpu for now?.

Please advise. Thank you.
Comment 6 Thomas Backlund 2021-01-25 21:35:34 CET
it was not reverting to amdgpu

it was reverting the earlier change from radeon to amdgpu

so when ldetect-lst 0.6.23 lands it should configure your gpu back to radeon
Comment 7 ian trump 2021-01-26 01:33:37 CET
Have re-installed the O/S and updated with ldetect-lst 0.6.23 and everything is good.

Have done the same with PClinux and that also appears to be OK now.

Thank you for your help and resolving the problem.

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