Description of problem: On a fresh install of Mageia 6 sta1 I found that X would not start, the EE lines in /var/log/Xorg.0.log are as follows: Version-Release number of selected component (if applicable): [ 21.084] (II) [KMS] Kernel modesetting enabled. [ 21.084] (II) RADEON(0): Creating default Display subsection in Screen section "screen1" for depth/fbbpp 24/32 [ 21.084] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32 [ 21.084] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) [ 21.084] (==) RADEON(0): Default visual is TrueColor [ 21.085] (==) RADEON(0): RGB weight 888 [ 21.085] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC) [ 21.085] (--) RADEON(0): Chipset: "KAVERI" (ChipID = 0x130f) [ 21.165] (EE) RADEON(0): [drm] Failed to open DRM device for pci:0000:00:01.0: No such file or directory [ 21.165] (EE) RADEON(0): Kernel modesetting setup failed [ 21.165] (II) UnloadModule: "radeon" [ 21.165] (EE) Screen(s) found, but none have a usable configuration. [ 21.165] (EE) Fatal server error: [ 21.165] (EE) no screens found(EE) [ 21.165] (EE) How reproducible: Try to configure X via XFdrake as well as Xorg -configure Steps to Reproduce: 1. XFdrake 2. Select Radeon HD 6400 and later (radeon/fglrx) 3. Hit OK, then reboot. Xorg does not start. Xorg works fine on Mageia 5 as well as the Cauldron ISO prior to sta1. Kaveri is an AMD A10-7850K processor.
CC: (none) => marja11Component: Release (media or process) => RPM PackagesAssignee: bugsquad => thierry.vignaud
CC: (none) => tmb
Please attach (not paste) the whole log instead of jsut an extract. Also what's the output of the following command? lspcidrake -v|egrep 'card:|VGA'
Keywords: (none) => NEEDINFO
Created attachment 8252 [details] Output from Xorg failing to start with Kaveri amdgpu driver.
Entire Xorg.0.log attached. Output from lspcidrake -v|egrep 'card:|VGA' Card:ATI Radeon HD 6400 and later (radeon/fglrx): Advanced Micro Devices, Inc. [AMD/ATI]|Kaveri [Radeon R7 Graphics] [DISPLAY_VGA] (vendor:1002 device:130f subv:1462 subd:7721) Thanks Thierry.
Attachment 8252 mime type: text/x-log => text/plain
So the real issue is that ldetect-list lists the wrong driver (radeon instead of amdgpu)
Source RPM: x11-driver-video-amdgpu-1.1.0-4.mga6.src.rpm => ldetect-lst
Why are you trying to use the amdgpu driver for that card? You need to use the ati driver. See https://www.x.org/wiki/RadeonFeature/ (polaris support has been added in amdgpu for Rx 480)
I'm working with MGA6 sta1, and at this level of things, AMDGPU is the correct driver: AMDGPU is the name given to the AMD GPU LLVM back-end (formerly known as the R600 LLVM back-end) as well as a new DRM kernel driver for supporting newer hardware. The AMDGPU kernel driver is used by both the open-source Gallium3D user-space driver and the new (closed-source) Catalyst driver in user-space on Linux systems. The ATI driver works great with MGA 5. I don't know if AMDGPU is new to MGA6 sta1 but I suspect it is.
It actually fails with 'ati'... (see above logs)
(In reply to Alan Richter from comment #6) > I'm working with MGA6 sta1, and at this level of things, AMDGPU is the > correct driver: > > AMDGPU is the name given to the AMD GPU LLVM back-end (formerly known as the > R600 LLVM back-end) as well as a new DRM kernel driver for supporting newer > hardware. The AMDGPU kernel driver is used by both the open-source Gallium3D > user-space driver and the new (closed-source) Catalyst driver in user-space > on Linux systems. > > The ATI driver works great with MGA 5. I don't know if AMDGPU is new to > MGA6 sta1 but I suspect it is. It must be new. This system was done from an earlier Mga6 iso. At that time was using a nvidia card but have, of 2 weeks ago, switched to an Radeon card. Card:ATI Radeon HD 6400 and later (radeon/fglrx): Advanced Micro Devices, Inc. [AMD/ATI]|Hawaii XT / Grenada XT [Radeon R9 290X/390X] [DISPLAY_VGA] (vendor:1002 device:67b0 subv:1682 subd:9290) Using the ati driver with EXA acceleration.
CC: (none) => cae
Actually 0x1002 0x130f is not supported by amdgpu
Summary: Xorg will not start with Mageia 6 sta1 using amdgpu => Xorg will not start with Mageia 6 sta1 using atiSource RPM: ldetect-lst => x11-driver-video-ati
(In reply to Thierry Vignaud from comment #9) > Actually 0x1002 0x130f is not supported by amdgpu So this video device, and possibly the entire line of Kaveri processors will not be supported by Mageia/Xorg? Do I need to bring up this topic on freedesktop.org?
No, it just means it's covered by the radeon driver, not the amdgpu one. CIK Support (Sea Islands: Kaveri, Bonaire, Hawaii, Kabini, Mullins) in amdgpu is still flagged experimental so I haven't enabled it in current kernel. But I think I'll enable the experimental support so people have it as an option if radeon driver fails...
amdgpu CIK support enabled in kernel-4.7.0-2.mga6
Great, I'll keep an eye on my repositories for that kernel. Thank you Thomas.
Created attachment 8301 [details] Output from Xorg -configure The meat of this attachment is: amdgpu_device_initialize: DRM version is 2.45.0 but this driver is only compatible with 3.x.x.
Created attachment 8302 [details] Xorg.0.log from Xorg -configure.
It looks like the amdgpu module is looking for 3.x.x drm instead of 2.x.x.
I ran into that error also. But if run lsmod |grep amd you'll find that both the the radeon driver is also being loaded which is what causes X to fail. You need to blacklist radeon. I tried doing so in /etc/modprobe.d/ and etc/modprobe.conf but that did not work for me. What did work was adding this in the kernel appends radeon.modeset=0 rd.driver.blacklist=radeon Also, amdgpu module is not being auto-loaded You need to modprobe amdgpu before trying to start X, or you can do as I and add amdgpu to /etc/modprobe.preload to force it to be loaded.
Created attachment 8305 [details] Xorg.0.log
I successfully blacklisted radeon, then ran XFdrake who thought that radeon was the best selection. Well since radeon was blacklisted it didnt' work so I specified amdgpu which didn't work either . Xorg.0.log attached. Wow, this one is a poser!
Run XFdrake and set the driver as amdgpu Under Options set it NOT to auto start X (Boots to init 3) Re-start the system. At init 3 login as user and su- to root run # lsmod |grep amdgpu This is what you want to see: [root@BuildBot ~]# lsmod |grep amdgpu amdgpu 1359872 7 i2c_algo_bit 16384 1 amdgpu drm_kms_helper 143360 1 amdgpu ttm 98304 1 amdgpu drm 360448 12 ttm,drm_kms_helper,amdgpu 1) If you have any listing for radeon then it is not being blacklisted. 2) If amdgpu is not listed then then it is not being auto-loaded If Only #2 is true you can modprobe amdgpu && service dm start which should now work
Jolly good, it worked! I'd love to be able to come up with X auto-started automatically but this is good enough for now. At least I get to play with Mageia 6 and amdgpu! I saw all that lovely tessellation in the Unigine Heaven demo with the Mesa amdgpu driver; very exciting Thank you for your help, I appreciate your knowledge and patience .
Add it to /etc/modprobe.preload Here's mine [root@BuildBot ~]# cat /etc/modprobe.preload # /etc/modprobe.preload: kernel modules to load at boot time. # # This file should contain the names of kernel modules that are # to be loaded at boot time, one per line. Comments begin with # a `#', and everything on the line after them are ignored. # this file is for module-init-tools (kernel 2.5 and above) ONLY # for old kernel use /etc/modules xpad amdgpu That will force the module to be loaded during boot. You can then set X to auto-start or even for auto-login.
Got the latest Cauldron updates tonight, the kernel line no longer has the blacklist option and Xorg started up fine with the amdgpu driver. Unless there is a reason not to, this bug can be closed resolved. Thank you all for your help.
(In reply to Alan Richter from comment #23) > > Unless there is a reason not to, this bug can be closed resolved. > Thanks for the feedback :-) Closing (the report can be opened again if someone thinks the issue did not get fixed)
Status: NEW => RESOLVEDResolution: (none) => FIXED