Bug 17018 - X not starting with kernel 4.2 when fglrx installed
Summary: X not starting with kernel 4.2 when fglrx installed
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-25 23:06 CET by Nikita Krupenko
Modified: 2022-05-01 19:25 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Boot with fglrx (173.08 KB, text/plain)
2015-10-26 12:42 CET, Nikita Krupenko 		Details
Boot with fglrx removed (164.96 KB, text/plain)
2015-10-26 12:42 CET, Nikita Krupenko 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Nikita Krupenko 2015-10-25 23:06:13 CET 
Description of problem:
I have laptop with AMD A8-5557M APU (Radeon HD 8550G) and discrete videocard Radeon HD 8750M.
With kerel 4.2 X cannot start. After several minutes I see pseudo-graphical drakx window with massage, that I have module incompatible with driver. This is with "ati" driver in xorg.conf. With fglrx, I haven't even seen this window, X not starts too.
Kernel 4.1 works fine with ati driver.
It started too boot when I removed all fglrx packages from my system.

Kernel 4.2 has new AMDGPU driver. May be it is not yet supported in Mageia?

Also, when I boot with 4.2 kernel, I see this error message:

radeon 0000:01:00.0: VCE init error (-110).


Reproducible: 

Steps to Reproduce:
Comment 1 Marja Van Waes 2015-10-26 09:29:24 CET 
(In reply to Nikita Krupenko from comment #0)
> 
> Also, when I boot with 4.2 kernel, I see this error message:
> 
> radeon 0000:01:00.0: VCE init error (-110).
> 

That sounds like you always see that error message, and not only when boot fails, correct?

Please do (as root) something like
  journalctl --since="2015-10-25" --until="2015-10-26" > journalctl.txt

to grab the logs from when you tried to boot the 4.2 kernel with the fglrx packages still installed + your first boot without them, and attach 
  journalctl.txt 
to this report

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

Comment 2 Nikita Krupenko 2015-10-26 12:42:21 CET 
Created attachment 7168 [details]
Boot with fglrx

Yes, I see VCE error on 4.2 in all configurations.
Comment 3 Nikita Krupenko 2015-10-26 12:42:53 CET 
Created attachment 7169 [details]
Boot with fglrx removed
Comment 4 Morgan Leijström 2016-05-24 10:34:08 CEST 
Removing NEEDINFO as requested info was provided.

Nikita: any updates on this issue?

FYI fglrx is not yet in shape on cauldron, Bug 16980

Keywords: NEEDINFO => (none)
CC: (none) => fri

Comment 5 Nikita Krupenko 2016-05-24 13:50:02 CEST 
Right now I have no fglrx and most of the time I use open-source drivers, so I can't say, if it works.

I think, more serious problem with kernel is bug 18322.
Comment 6 Marja Van Waes 2016-08-26 12:48:55 CEST 
Mass-reassigning all bugs with "kernel" in the summary that are still assigned to tmb (or wrongly assigned to someone with "tmb" in his e-mail address) to the kernel packagers group, but without adding "kernel" to the SRPM field.

Please reassign if needed, or add kernel to the SRPM field if this is correct.

Assignee: tmb => kernel

Comment 7 sturmvogel 2022-05-01 19:25:15 CEST 
Last time we shipped fglrx was with Mageia 5.

Closing OLD.

Resolution: (none) => OLD
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.