Description of problem: fglx proprietary video seg faults Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Use mcc to configure video server for ATI Radeon HD 6400 and later (radeon/fglrx) # lspcidrake | grep card Card:ATI Radeon HD 6400 and later (radeon/fglrx): Advanced Micro Devices, Inc. [AMD/ATI]|Oland PRO [Radeon R7 240/340] [DISPLAY_VGA] Workaround: set xorg vesa video driver. Reproducible: Steps to Reproduce:
Created attachment 7141 [details] dmesg snippet
Summary: fglx proprietary video seg faults => fglrx proprietary video seg faultsSource RPM: fglx => fglrx
Summary: fglrx proprietary video seg faults => fglrx proprietary video driver seg faults
Created attachment 7198 [details] dmesg snippet
Attachment 7141 is obsolete: 0 => 1
CC: (none) => tmbAssignee: bugsquad => anssi.hannula
Any chance of seeing if the amd-catalyst 15.201.1151-x86 release fixes my problem?
Not any point for now as current fglrx does not support kernel 4.4 (could probably be patched), and not xorg 1.18 (which needs changes bt Amd to the binary-only parts of fglrx), and is not really happy with gcc 5 either... :/ So we still have to wait for Amd
What is the status here? I upgraded this system online from mga5 a week ago, and it worked great. I kept updating and after a reboot a couple days ago it could not start X. I have to use the system so i use xorg vesa for now ( which is painful on a 2560x1600 screen... and yes i am am lunetic using cauldron on my workstation but i needed a programs that were conveniently packaged her and not on mga5 ;) ) ( also tried xorg ati and xorg amdgpu which failed, while i have no idea if they would have a chance. Any idea on a better workaround than the vesa (too low resolution for my taste ) Card: Barts PRO [Radeon HD 6850] # lspcidrake | grep card [root@svarten ~]# Card:ATI Radeon HD 6400 and later (radeon/fglrx): Advanced Micro Devices, Inc. [AMD/ATI]|Oland PRO [Radeon R7 240/340] [DISPLAY_VGA] I noted system only have mga5 versions of fglrx: - fglrx-control-center-15.302-1.mga5.nonfree.x86_64 - fglrx-kernel-4.1.15-desktop-2.mga5-15.302-1.mga5.nonfree.x86_64 - fglrx-kernel-desktop-latest-15.302-1.mga5.nonfree.x86_64 - fglrx-opencl-15.302-1.mga5.nonfree.x86_64 - x11-driver-video-fglrx-15.302-1.mga5.nonfree.x86_64 I wonder if the system was using them despite running mga6 kernel 4.6.0? To clear confusion i now uninstalled them. (i still keep latest mga5 kernel as a backup) I find no mga6 fglrx at all!? I fail to find where is a log of urpmi/drakrpm activities? IMO, this bug should be a release blocker
CC: (none) => fri
Created attachment 7843 [details] Xorg.0.log_failed-boot-default-proprietary Um, maybe there is another problem. From my Xorg.0.log : (EE) Screen 0 deleted because of no matching config section. (II) UnloadModule: "radeon" (EE) Device(s) detected, but none match those in the config file (but i can use vesa)
Small sidenotes: I read that amdgpu is not suitable for my GPU, interesting read https://www.reddit.com/r/Amd/comments/4gf9ev/thank_you_amd_for_your_open_source_linux_driver/ I also tried "HD4870 and earlier" as it was the only one in that series that do not need fglrx, but that fail too.
Created attachment 7844 [details] lspci-v_failed-boot-default-proprietary
Created attachment 7845 [details] lspcidrake-v_failed-boot-default-proprietary
Created attachment 7846 [details] journalctl-ab_failed-boot-default-proprietary.tar.gz
Update: since updated x11 and xorg ati today this system works with xorg ati free driver :) => my system is fully useable again (not using fglrx)
Now the proprietary ati driver works on this system :)
Status: NEW => RESOLVEDResolution: (none) => FIXED
you are not using any proprietary driver for amd/ati hw... There is no such driver available in cauldron, fglrx is not supporting either kernel or xorg server. So you are using the free radeon/ati drivers
Oh. Heh. Anyway good thing is that when selecting to use the default choice when configuring the graphics, the "ATI > Radeon HD 6400 and later (radeon/fglrx)" now results in a working system. What is the plan here, if any? Will proprietary driver be with us in the future, Or drakx11 changed to say that it really will use the free driver?