Bug 24156 - AMD Radeon R5 does not boot properly with Live media of 7beta2
Summary: AMD Radeon R5 does not boot properly with Live media of 7beta2
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords: 7beta2
Depends on:
Blocks:
 
Reported: 2019-01-08 19:13 CET by Dick Gevers
Modified: 2019-02-18 09:29 CET (History)
5 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Dick Gevers 2019-01-08 19:13:49 CET
Description of problem:

Laptop HP with AMD Radeon R5.

Live media (64 bits) show boot media but after entering an option nothing seems to happen anymore.

If I remove "splash quiet" I see many many boot messages for a second but
thereafter the screen is black and stays that way...

I tried adding the blacklist parameters: rd.driver.blacklist=radeon 
rd.driver.blacklist=amdgpu and indeed I got a lot further !

I now get all the boot messages and see after 5 to 10 minutes that network
is active. With tty2 I can login as live and see X is not running.

With XFdrake I did not manage to get a working setup; each time it is:
"error (EE) Fatal server error"

Bug report after discussion with MartinW on QA ML
Comment 1 Dick Gevers 2019-01-08 19:15:07 CET
With 6.1 and 7beta1 this did not happen.

Keywords: (none) => 7beta2
CC: (none) => mageia

Marja Van Waes 2019-01-09 08:22:06 CET

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

Comment 2 Martin Whitaker 2019-01-09 09:49:57 CET
I think this is a kernel driver regression.

Assignee: isobuild => kernel
Component: Release (media or process) => RPM Packages

Comment 3 Lewis Smith 2019-01-11 11:03:03 CET
Mageia7 beta2 Gnome Live from USB.
Real EFI hardware with AMD Radeon HD7310 graphics (which apparently does not now require non-free driver). Boot menu results:
- Boot Live all free: worked.
- Boot Live with non-free: started, showed occasional splash screens, then stuck on a blank screen.
- Install all free: worked
- Install non-free: started, showed occasional splash screens, then stuck on a blank screen.

CC: (none) => lewyssmith

Comment 4 Martin Whitaker 2019-01-13 00:58:55 CET
@Lewis, there is no proprietary driver for AMD graphics. The "non-free" menu items add the nokmsboot kernel boot option, which is needed for the nvidia drivers to work, but prevents the free radeon driver from working.
Comment 5 Thomas Backlund 2019-01-13 11:11:53 CET
I think we should alter the menu to state "nonfree nvidia" to avoid confusion.

If we ever package up the nonfree amd driver stack again we can re-visit the issue... but that wont happend for Mga7

CC: (none) => tmb

Comment 6 Martin Whitaker 2019-01-13 14:17:42 CET
(In reply to Thomas Backlund from comment #5)
> I think we should alter the menu to state "nonfree nvidia" to avoid
> confusion.

Yes, I'd been thinking that. The only reason I hadn't already is that it's more work for the translators.
Comment 7 Lewis Smith 2019-01-14 21:35:10 CET
(In reply to Martin Whitaker from comment #4)
> @Lewis, there is no proprietary driver for AMD graphics. The "non-free" menu
> items add the nokmsboot kernel boot option, which is needed for the nvidia
> drivers to work, but prevents the free radeon driver from working.
Is there a problem here? Should 'nokmsboot' kernel boot option queer other things which do not need it?
As a naive user, I always took the boot menu non-free drivers option to be system-wide, not just re video for booting. So Thomas' suggestion 'the menu to state "nonfree nvidia" to avoid confusion' is sound. Accept for the future, not M7.
Comment 8 Dick Gevers 2019-02-18 09:29:30 CET
Okay for me in round3, closing

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


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