| View previous topic :: View next topic |
| Author |
Message |
ICannotStandXorg
n00b
Joined: 02 Jun 2016
Posts: 9
|
 Posted: Thu Jun 02, 2016 1:23 am Post subject: [SOLVED] X server refusing to start. |
 |
|
Hello.
I'm having trouble with KMS and getting X server to start. Here is my full Xorg.0.log:
| Code: |
X.Org X Server 1.18.3
Release Date: 2016-04-04
[ 991.958] X Protocol Version 11, Revision 0
[ 991.958] Build Operating System: Linux 4.6.0-gentoo x86_64 Gentoo
[ 991.958] Current Operating System: Linux loane 4.6.0-gentoo #1 SMP Wed Jun 1 17:48:33 MDT 2016 x86_64
[ 991.959] Kernel command line: BOOT_IMAGE=/boot/kernel-genkernel-x86_64-4.6.0-gentoo root=UUID=cd40f33e-e0dc-444d-9fdc-1b884e2e5019 ro
[ 991.959] Build Date: 01 June 2016 04:13:00PM
[ 991.959]
[ 991.959] Current version of pixman: 0.34.0
[ 991.960] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 991.960] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 991.961] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jun 1 18:59:57 2016
[ 991.961] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 991.961] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 991.961] (==) No Layout section. Using the first Screen section.
[ 991.961] (==) No screen section available. Using defaults.
[ 991.961] (**) |-->Screen "Default Screen Section" (0)
[ 991.961] (**) | |-->Monitor "<default monitor>"
[ 991.961] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 991.961] (**) | |-->Device "AMD"
[ 991.961] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 991.961] (==) Automatically adding devices
[ 991.961] (==) Automatically enabling devices
[ 991.961] (==) Automatically adding GPU devices
[ 991.961] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 991.961] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 991.961] (==) ModulePath set to "/usr/lib64/xorg/modules"
[ 991.961] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 991.961] (II) Loader magic: 0x812c40
[ 991.961] (II) Module ABI versions:
[ 991.961] X.Org ANSI C Emulation: 0.4
[ 991.961] X.Org Video Driver: 20.0
[ 991.961] X.Org XInput driver : 22.1
[ 991.961] X.Org Server Extension : 9.0
[ 991.962] (--) PCI:*(0:1:0:0) 1002:6939:1458:22b6 rev 241, Mem @ 0xe0000000/268435456, 0xf0000000/2097152, 0xf7e00000/262144, I/O @ 0x0000e000/256, BIOS @ 0x????????/131072
[ 991.962] (II) LoadModule: "glx"
[ 991.962] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[ 991.962] (II) Module glx: vendor="X.Org Foundation"
[ 991.962] compiled for 1.18.3, module version = 1.0.0
[ 991.962] ABI class: X.Org Server Extension, version 9.0
[ 991.962] (==) AIGLX enabled
[ 991.962] (II) LoadModule: "amdgpu"
[ 991.963] (II) Loading /usr/lib64/xorg/modules/drivers/amdgpu_drv.so
[ 991.963] (II) Module amdgpu: vendor="X.Org Foundation"
[ 991.963] compiled for 1.18.3, module version = 1.1.0
[ 991.963] Module class: X.Org Video Driver
[ 991.963] ABI class: X.Org Video Driver, version 20.0
[ 991.963] (II) AMDGPU: Driver for AMD Radeon chipsets: BONAIRE, BONAIRE, BONAIRE,
BONAIRE, BONAIRE, BONAIRE, BONAIRE, BONAIRE, BONAIRE, KABINI, KABINI,
KABINI, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI,
KABINI, KABINI, KABINI, KABINI, KABINI, KABINI, KAVERI, KAVERI,
KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
KAVERI, KAVERI, KAVERI, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII,
HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, TOPAZ, TOPAZ,
TOPAZ, TOPAZ, TOPAZ, TONGA, TONGA, TONGA, TONGA, TONGA, TONGA, TONGA,
TONGA, TONGA, CARRIZO, CARRIZO, CARRIZO, CARRIZO, CARRIZO, FIJI,
STONEY, POLARIS11, POLARIS11, POLARIS11, POLARIS11, POLARIS11,
POLARIS11, POLARIS10, POLARIS10
[ 991.963] (--) using VT number 7
[ 991.967] (II) [KMS] drm report modesetting isn't supported.
[ 991.967] (EE) Screen 0 deleted because of no matching config section.
[ 991.967] (II) UnloadModule: "amdgpu"
[ 991.967] (EE) Device(s) detected, but none match those in the config file.
[ 991.967] (EE)
Fatal server error:
[ 991.967] (EE) no screens found(EE)
[ 991.967] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 991.967] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 991.967] (EE)
[ 991.969] (EE) Server terminated with error (1). Closing log file.
|
I have seen many different reports of the modesetting not being support error, however all of them are very old and are using the Radeon driver, where I'm using amdgpu. I have seen answers of enabling
| Code: |
<M> ATI Radeon
[*] Enable modesetting on radeon by default - NEW DRIVER (NEW)
|
in menuconfig, however it simply is not there anymore, and there isn't the option under the AMDGPU section either. I simply cannot find any real modern documentation on why KMS will not work with amdgpu for me, everything says it's "enabled by default". If you need anything else please ask me.
Thanks for your time.
Last edited by ICannotStandXorg on Thu Jun 02, 2016 5:59 am; edited 1 time in total |
|
| Back to top |
|
 |
The Doctor
Moderator
Joined: 27 Jul 2010
Posts: 2678
|
| Posted: Thu Jun 02, 2016 1:54 am Post subject: |
|
|
Welcome to Gentoo!
There are several likely causes to explore here. First, note that the amdgpu module is being loaded but can't be used so this is unlikely to be kernel related. Xorg simply can't use the module which implies that the firmware might be missing. This should be provided by either sys-firmware/amdgpu-ucode or sys-kernel/linux-firmware according to taste.
It is important to note that either amdgpu must be built as a module or the firmware must be built into the kernel. Again, this is according to taste.
Second, there is the options in make.conf. You should have VIDEO_CARDS="amdgpu radeonsi" to instruct portage to build support for your driver.If you need to add that line, run emerge --ask --changed-use --deep @world to install the missing packages.
_________________
First things first, but not necessarily in that order.
Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box. |
|
| Back to top |
|
|
ICannotStandXorg
n00b
Joined: 02 Jun 2016
Posts: 9
|
| Posted: Thu Jun 02, 2016 1:59 am Post subject: |
|
|
| The Doctor wrote: |
There are several likely causes to explore here. First, note that the amdgpu module is being loaded but can't be used so this is unlikely to be kernel related. Xorg simply can't use the module which implies that the firmware might be missing. This should be provided by either sys-firmware/amdgpu-ucode or sys-kernel/linux-firmware according to taste.
|
I have installed linux-firmware.
| The Doctor wrote: |
It is important to note that either amdgpu must be built as a module or the firmware must be built into the kernel. Again, this is according to taste.
|
In /lib/firmware/amdgpu there appears to be all of the necessary .bin for my Tonga video card.
| The Doctor wrote: |
Second, there is the options in make.conf. You should have VIDEO_CARDS="amdgpu radeonsi" to instruct portage to build support for your driver.If you need to add that line, run emerge --ask --changed-use --deep @world to install the missing packages. |
Yup, I've had that line in make.conf. |
|
| Back to top |
|
|
The Doctor
Moderator
Joined: 27 Jul 2010
Posts: 2678
|
| Posted: Thu Jun 02, 2016 4:12 am Post subject: |
|
|
Which kernel version and xorg version are you using? Are you trying to use the stable or unstable branch?
A little googling shows problems with kernels before 4.5.1.
_________________
First things first, but not necessarily in that order.
Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box. |
|
| Back to top |
|
|
ICannotStandXorg
n00b
Joined: 02 Jun 2016
Posts: 9
|
| Posted: Thu Jun 02, 2016 4:17 am Post subject: |
|
|
| The Doctor wrote: | Which kernel version and xorg version are you using? Are you trying to use the stable or unstable branch?
A little googling shows problems with kernels before 4.5.1. |
X server 1.18.3.
Kernel 4.6.0. |
|
| Back to top |
|
|
The Doctor
Moderator
Joined: 27 Jul 2010
Posts: 2678
|
| Posted: Thu Jun 02, 2016 4:19 am Post subject: |
|
|
Can you pastebin your kernel .config?
_________________
First things first, but not necessarily in that order.
Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box. |
|
| Back to top |
|
|
ICannotStandXorg
n00b
Joined: 02 Jun 2016
Posts: 9
|
|
| Back to top |
|
|
The Doctor
Moderator
Joined: 27 Jul 2010
Posts: 2678
|
| Posted: Thu Jun 02, 2016 4:43 am Post subject: |
|
|
| Code: | CONFIG_DRM_AMDGPU=y
# CONFIG_FIRMWARE_IN_KERNEL is not set |
Here is the problem. You either need to amdgpu to be a module or build it's firmware into the kernel.
Your simplest and solution will be to use menuconfig (never manually edit the kernel .conf) to set AMDGPU to module and rebuild your kernel. As it is the card cannot load the firmware so naturally it isn't working.
_________________
First things first, but not necessarily in that order.
Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box. |
|
| Back to top |
|
|
ICannotStandXorg
n00b
Joined: 02 Jun 2016
Posts: 9
|
| Posted: Thu Jun 02, 2016 5:58 am Post subject: |
|
|
| The Doctor wrote: | | Code: | CONFIG_DRM_AMDGPU=y
# CONFIG_FIRMWARE_IN_KERNEL is not set |
Here is the problem. You either need to amdgpu to be a module or build it's firmware into the kernel.
Your simplest and solution will be to use menuconfig (never manually edit the kernel .conf) to set AMDGPU to module and rebuild your kernel. As it is the card cannot load the firmware so naturally it isn't working. |
Aha! Thank you very much, it worked.  |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
