Bug 22339 - The 4.14.10 kernel requires radeon.cik_support=0 admgpu.cik_support=1 on the kernel command line for amdgpu.
Summary: The 4.14.10 kernel requires radeon.cik_support=0 admgpu.cik_support=1 on the ...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-07 03:38 CET by Alan Richter
Modified: 2020-08-14 16:17 CEST (History)
3 users (show)

See Also:
Source RPM: drakx-kbd-mouse-x11-1.23-1.mga6
CVE:
Status comment:


Attachments

Description Alan Richter 2018-01-07 03:38:11 CET
Description of problem:
Xorg will not start if amdgpu is selected in XFdrake for the Xserver with the 4.1.4.10 kernel.

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


How reproducible:
Always with the 4.14.10 kernel.

Steps to Reproduce:
1. Start XFdrake.
2. Select amdgpu for X-server.
3. reboot

If radeon.cik_support=0 admgpu.cik_support=1 is specified on the kernel command line, amdgpu comes up fine. 

Perhaps something to this effect should be added to the kernel command line when selecting radeon or amdgpu for AMD GPUs in XFdrake.
Comment 1 Charles Edwards 2018-01-07 05:09:08 CET
This is the same bug as https://bugs.mageia.org/show_bug.cgi?id=22284.
Different chips but with the same issue.

It can|will affect certain amd gpu.

cik (Sea Island Rx 200 series)
ci  (Southern Island HD 7000 series)

The radeon driver is the default for these cards.
For the amdgpu driver to be used appends Must be added to prevent the radeonfb
driver from being loaded and to instruct that the amdgpufb driver be used.

CC: (none) => cae

Marja Van Waes 2018-01-07 06:52:00 CET

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

Comment 2 Alan Richter 2018-01-07 18:09:05 CET
Thanks for the information, I should put something on the wiki instead of bothering the bugsquad.  Thanks for the response.  

Great job everyone.
Comment 3 Aurelien Oudelet 2020-08-14 16:17:41 CEST
This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

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


Note You need to log in before you can comment on or make changes to this bug.