I have some issues with my setup. I have a Linux PC and I needed to reinstall everything due to a graphic cards issue (I don’t know what happened but the PC started refusing to turn on.). I have 2 monitors connected to the PC and I tried to configure X screens with XOrgConfiguraionCreator and then selected my config with XOrgConfigurationSelector. I had no error but when I restarted the PC, both monitors were active, and this error showed when I launched MATLAB:
com.jogamp.opengl.GLException: X11GLXDrawableFactory - Could not initialize shared resources for X11GraphicsDevice[type .x11, connection :0, unitID 0, handle 0x0, owner false, ResourceToolkitLock[obj 0x1e237daf, isOwner false, <18e1ad01, 7d19a277>[count 0, qsz 0, owner <NULL>]]]
at jogamp.opengl.x11.glx.X11GLXDrawableFactory$SharedResourceImplementation.createSharedResource(X11GLXDrawableFactory.java:326)
at jogamp.opengl.SharedResourceRunner.run(SharedResourceRunner.java:297)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
at jogamp.opengl.GLContextImpl.makeCurrent(GLContextImpl.java:688)
at jogamp.opengl.GLContextImpl.makeCurrent(GLContextImpl.java:580)
at jogamp.opengl.x11.glx.X11GLXDrawableFactory$SharedResourceImplementation.createSharedResource(X11GLXDrawableFactory.java:297)
... 2 more
I couldn’t find a solution to this. This seems a bit advanced for me but I can do my best with some guidance.
I am using MATLAB R2022b on Ubuntu 22.04. I installed PTB as recommended on the website. I reconfigured MATLAB (sudo dpkg-reconfigure matlab-support) and I installed low-latency kernel as well.
Looking forward to your reply!
Cemre Yilmaz (identified as she/her) #X11#XOrgConfiguration#XScreen
This is a Matlab bug on Linux + Intel graphics chips, often reported to Mathworks, never fixed by them. It doesn’t affect Psychtoolbox at all, just plotting in Matlab.
Diagnosis and ok solution see:
Update with a possibly better solution on recent Matlab:
What also worked for me on Ubuntu 20.04.6-LTS, Intel graphics, Mesa 21.2.6, with Matlab R2023b is the following older approach at fixing it:
Thanks Mario! It helped with the OpenGL issue.
I still have a problem with XOrgConf. Although I can create an config file and select it without any error message on matlab, it doesn’t apply it after logout/login - even after restart. It is a similar issue with this: AMD graphics card - #2 by mariokleiner
I ran sudo dpkg-reconfigure matlab-support on terminal and it changed only GCC library names. uname -r reports 6.5.0-14-generic. There is no PTB output about XOrgConf. Do you have further suggestions?
It works on any supported system, unless you screwed up or do/did something unsupported or your system is odd. In any case, this is a case for paid support if our standard tips and instructions don’t work.
I followed the instructions for installation via NeuroDebian. I run PsychLinuxConfiguration as well.
On terminal:
user:~$ ls -l /etc/X11/xorg.conf.d/
total 4
-rw-rw-r-- 1 allg_admin allg_admin 931 Jän 17 11:27 90-ptbxorg.conf
user:~$ ls -l /etc/X11/ | grep xorg
drwxrwxr-x 2 allg_admin allg_admin 4096 Feb 7 11:49 xorg.conf.d
drwxr-xr-x 2 root root 4096 Jän 17 11:02 xorg.conf.d.old
On matlab:
>> XOrgConfSelector
You can choose from the following X11 configuration files:
1) 90-ptbconfig_1_xscreens_1_outputs_modesetting.conf
2) 90-ptbconfig_2_xscreens_2_outputs_modesetting.conf
3) 90-ptbconfig_single_xscreen_amdgpu.conf
Which one should i use? (Choose 0 for remove the current active file): 2
Copied the xorg.conf file into the X11 config folder under:
/etc/X11/xorg.conf.d/90-ptbxorg.conf
Troubleshooting tip in case of emergency:
In case something goes seriously wrong and you end up with a non-functioning GUI,
you can always press(*) 'CTRL+ALT+F3', which provides you with a text console. Then login
there, run octave or matlab from the text console and call XOrgConfSelector to remove
the troublesome config file. Or type this: rm /etc/X11/xorg.conf.d/90-ptbxorg.conf
(*)Apple computer users may need to press 'FN+CTRL+ALT+F3' instead of CTRL+ALT+F3
Now please logout and login again for the new configuration to take effect.
I was stuck on login screen when I tried logging in after logout. And I have two active monitors after restart. The stimulus monitor is still on and PTB uses two monitors as one screen.
Ok, so the access permissions and ownerships of the directory /etc/X11/xorg.conf.d/ are wrong for some very weird reason (do you have some administrator administrating that machine who does weird stuff?), and would only allow the user “allg_admin” to update the config file, ie. for your username “user” XOrgConfSelector would fail. It unfortunately fails silently though, as error reporting is insufficient in current PTB’s. I’ve improved it for the next upcoming PTB 3.0.19.8 release.
PsychLinuxConfiguration however, as of the current NeuroDebian releases (PsychtoolboxVersion reports 3.0.19.7.dfsg as version) , should be able to detect and fix permission/ownership issues by itself. Your user must also be added to the “psychtoolbox” Unix user group. If you type id in a terminal, the output should list “psychtoolbox” somewhere.
Can you rerun PsychLinuxConfiguration again? Then logout + login.
When it asks about adding users to the psychtoolbox user group, you should enter user as the name to add.
I guess your started off on that machine with an Intel graphics chip and then upgraded to an AMD gpu, and due to the silent failure XOrgConfSelector, there’s still an unsuitable file for the old Intel chip installed, leading to failure.
For reference, ls -l /etc/X11 | grep xorg should normally look similar to this - the word psychtoolbox and drwxrwsr-x being key: drwxrwsr-x 2 root psychtoolbox 4096 Feb 2 17:28 xorg.conf.d
id should contain the word psychtoolbox as well in its output.
The lab was too busy, I could find a time slot today. You’re right, we started with an Intel graphic card and switched to an AMD, and it shows “Mesa Intel® HD Graphics 4400 (HSW GT2) / AMD® Radeon pro wx 320…” as graphic info, I didn’t noticed that before. Should I delete something or reinstall everything?
So, I logged in as allg_admin this time.
allg_admin@14-PF062:~$ ls -l /etc/X11/xorg.conf.d/
total 4
-rw-rw-r-- 1 allg_admin psychtoolbox 958 Feb 15 15:34 90-ptbxorg.conf
allg_admin@14-PF062:~$ ls -l /etc/X11/ | grep xorg
drwxrwsr-x 2 root psychtoolbox 4096 Feb 15 15:34 xorg.conf.d
drwxr-xr-x 2 root root 4096 Jän 17 11:02 xorg.conf.d.old
drwxrwsr-x 2 allg_admin psychtoolbox 4096 Feb 7 11:49 xorg.conf.d_old
Then, I downloaded the new version of XOrgConfSelector, and created a new X screen configuration, and selected it. I didn’t get any error message again. After login/logout, the monitor on which I selected to show matlab GNU is not detected anymore. I restarted the computer and it gets signal at the beginning and shows Dell logo. After login, it is completely dark and it says “no signal”. Also XOrgConfCreator detects only one monitor.
So this looks good now. Proper file and directory ownerships and permissions, new XOrgConfSelector not complaining. PsychLinuxConfiguration did the trick .
You can delete the old xorg.conf.d folders inside /etc/X11, e.g., on a terminal:
sudo rm -rf /etc/X11/xorg.conf.d*old
That 2nd graphics card could be the reason, if it is still active an has not been disabled in the EFI firmware settings when installing the new AMD card. Are any display monitors still plugged into the output port of the Intel card? Or are all monitors plugged into the AMD?
On Linux, as the only operating system, you can effectively use two graphics cards for vision science if you really want and need it. If you have a hybrid graphics laptop, Linux might be even the only way to make it usable at all for vision science. And if you want two graphics cards just for regular desktop use without need for precisely controlled visual stimulation timing, it usually just works plug & play.
But if you want to use both graphics cards for visual stimulation, and you want precise visual stimulation timing and control, it requires extra manual setup. And if you want to use a multi-x-screen setup, you’ll have to create the xorg.conf files yourself, as XOrgConfCreator in general can not deal with it - too many weird variations of hardware out there - and will create potentially broken config files. The whole story and instructions in help HybridGraphics.
But if this is a regular desktop PC computer, I’d assume you probably would not want to use the old Intel gpu at all for typical bread and butter use cases, and the best course of action would be to simply disable the Intel or Onboard graphics in the EFI firmware settings and then start over with XOrgConfCreator.
To get your display back, login to a text console (e.g., CTRL+ALT+F3).
Make a backup of the XOrg log file and post it. E.g., for the user “username” that was logged in when things went south, the file /home/username/.local/share/xorg/Xorg.0.log would be the right one.
rm /etc/X11/xorg.conf.d/90-ptbxorg.conf or run XOrgConfSelector selecting 0 for removing the file - same thing. But first make a backup of the file and post its content here.
— Maybe post those files here first to double check? —
If you want to go AMD only, reboot the machine, check that things are working again, then reboot into the system EFI setup menu.
Somewhere in the many sub-menus there must be a setting that allows to disable the internal graphics (sometimes called iGPU). You’d want “discrete graphics only” or “external graphics” or “dGPU” or some wording like that. Save. Reboot.
Now you’d have an AMD only machine, with all monitors connected to the AMD, and XOrgConfCreator and XOrgConfSelector could do their jobs again in this simplified case.
Please respond quickly, technically the paid for support time has already been used up twice so we need to resolve this quickly or further payments would be needed.
-mario
[60 minutes out of 30 paid minutes used - Paid support exhausted]
[ 41.210] X.Org X Server 1.21.1.4
X Protocol Version 11, Revision 0
[ 41.210] Current Operating System: Linux 14-PF062 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64
[ 41.210] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic root=UUID=3382ea19-901a-4900-a3a6-1e88b7caa382 ro quiet splash vt.handoff=7
[ 41.210] xorg-server 2:21.1.4-2ubuntu1.7~22.04.8 (For technical support please see http://www.ubuntu.com/support)
[ 41.210] Current version of pixman: 0.40.0
[ 41.210] Markers: (–) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 41.210] (==) Log file: “/home/allg_admin/.local/share/xorg/Xorg.0.log”, Time: Fri Feb 16 10:48:46 2024
[ 41.213] (==) Using config directory: “/etc/X11/xorg.conf.d”
[ 41.213] (==) Using system config directory “/usr/share/X11/xorg.conf.d”
[ 41.218] (==) ServerLayout “PTB-Hydra”
[ 41.218] () |–>Screen “Screen0” (0)
[ 41.218] () | |–>Monitor “VGA-1-1”
[ 41.219] () | |–>Device “Card0”
[ 41.219] () |–>Screen “Screen1” (1)
[ 41.219] () | |–>Monitor “DisplayPort-2”
[ 41.219] () | |–>Device “Card1”
[ 41.219] () Option “AutoAddGPU” “false”
[ 41.219] (==) Automatically adding devices
[ 41.219] (==) Automatically enabling devices
[ 41.219] (**) Not automatically adding GPU devices
[ 41.219] (==) Automatically binding GPU devices
[ 41.219] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 41.219] (WW) The directory “/usr/share/fonts/X11/cyrillic” does not exist.
[ 41.219] Entry deleted from font path.
[ 41.219] (WW) The directory “/usr/share/fonts/X11/100dpi/” does not exist.
[ 41.219] Entry deleted from font path.
[ 41.219] (WW) The directory “/usr/share/fonts/X11/75dpi/” does not exist.
[ 41.219] Entry deleted from font path.
[ 41.219] (WW) The directory “/usr/share/fonts/X11/100dpi” does not exist.
[ 41.219] Entry deleted from font path.
[ 41.219] (WW) The directory “/usr/share/fonts/X11/75dpi” does not exist.
[ 41.219] Entry deleted from font path.
[ 41.219] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
built-ins
[ 41.219] (==) ModulePath set to “/usr/lib/xorg/modules”
[ 41.219] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 41.219] (II) Loader magic: 0x55eee92ce020
[ 41.219] (II) Module ABI versions:
[ 41.219] X.Org ANSI C Emulation: 0.4
[ 41.219] X.Org Video Driver: 25.2
[ 41.219] X.Org XInput driver : 24.4
[ 41.219] X.Org Server Extension : 10.0
[ 41.220] (++) using VT number 2
[ 41.221] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_32
[ 41.223] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 41.223] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card1
[ 41.224] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 14 paused 0
[ 41.224] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 41.224] (II) Platform probe for /sys/devices/pci0000:00/0000:00:02.0/drm/card0
[ 41.225] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 15 paused 0
[ 41.228] (–) PCI: (0@0:2:0) 8086:041e:1028:0612 rev 6, Mem @ 0xf7800000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x???/131072
[ 41.228] (–) PCI:*(1@0:0:0) 1002:6981:1002:0b0d rev 16, Mem @ 0xe0000000/268435456, 0xf0000000/2097152, 0xf7d00000/262144, I/O @ 0x0000e000/256, BIOS @ 0x???/131072
[ 41.228] (II) LoadModule: “glx”
[ 41.230] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 41.235] (II) Module glx: vendor=“X.Org Foundation”
[ 41.235] compiled for 1.21.1.4, module version = 1.0.0
[ 41.235] ABI class: X.Org Server Extension, version 10.0
[ 41.235] (II) LoadModule: “amdgpu”
[ 41.236] (II) Loading /usr/lib/xorg/modules/drivers/amdgpu_drv.so
[ 41.238] (II) Module amdgpu: vendor=“X.Org Foundation”
[ 41.238] compiled for 1.21.1.4, module version = 22.0.0
[ 41.239] Module class: X.Org Video Driver
[ 41.239] ABI class: X.Org Video Driver, version 25.2
[ 41.239] (II) AMDGPU: Driver for AMD Radeon:
All GPUs supported by the amdgpu kernel driver
[ 41.239] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 41.239] (II) AMDGPU(0): Creating default Display subsection in Screen section
“Screen0” for depth/fbbpp 24/32
[ 41.239] (==) AMDGPU(0): Depth 24, (–) framebuffer bpp 32
[ 41.239] (II) AMDGPU(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[ 41.239] (==) AMDGPU(0): Default visual is TrueColor
[ 41.239] () AMDGPU(0): Option “ZaphodHeads” “VGA-1-1”
[ 41.239] (==) AMDGPU(0): RGB weight 888
[ 41.239] (II) AMDGPU(0): Using 8 bits per RGB (8 bit DAC)
[ 41.239] (–) AMDGPU(0): Chipset: “AMD Radeon Pro WX 3200 Series” (ChipID = 0x6981)
[ 41.239] (II) Loading sub module “fb”
[ 41.239] (II) LoadModule: “fb”
[ 41.240] (II) Module “fb” already built-in
[ 41.240] (II) Loading sub module “dri2”
[ 41.240] (II) LoadModule: “dri2”
[ 41.240] (II) Module “dri2” already built-in
[ 41.282] (II) Loading sub module “glamoregl”
[ 41.282] (II) LoadModule: “glamoregl”
[ 41.282] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[ 41.289] (II) Module glamoregl: vendor=“X.Org Foundation”
[ 41.289] compiled for 1.21.1.4, module version = 1.0.1
[ 41.289] ABI class: X.Org ANSI C Emulation, version 0.4
[ 41.303] (II) AMDGPU(0): glamor X acceleration enabled on AMD Radeon Pro WX 3200 Series (polaris12, LLVM 15.0.7, DRM 3.54, 6.5.0-17-generic)
[ 41.303] (II) AMDGPU(0): glamor detected, initialising EGL layer.
[ 41.303] (==) AMDGPU(0): TearFree property default: auto
[ 41.303] (==) AMDGPU(0): VariableRefresh: disabled
[ 41.303] (==) AMDGPU(0): AsyncFlipSecondaries: disabled
[ 41.303] (II) AMDGPU(0): KMS Pageflipping: enabled
[ 41.320] (WW) AMDGPU(0): No outputs definitely connected, trying again…
[ 41.320] (WW) AMDGPU(0): Unable to find connected outputs - setting 1024x768 initial framebuffer
[ 41.320] (II) AMDGPU(0): mem size init: gart size :f4cc0000 vram size: s:fea50000 visible:102a9000
[ 41.320] (==) AMDGPU(0): DPI set to (96, 96)
[ 41.320] (==) AMDGPU(0): Using gamma correction (1.0, 1.0, 1.0)
[ 41.320] (II) Loading sub module “ramdac”
[ 41.320] (II) LoadModule: “ramdac”
[ 41.320] (II) Module “ramdac” already built-in
[ 41.320] (EE) AMDGPU(0): No modes.
[ 41.320] (II) AMDGPU(1): Creating default Display subsection in Screen section
“Screen1” for depth/fbbpp 24/32
[ 41.320] (==) AMDGPU(1): Depth 24, (–) framebuffer bpp 32
[ 41.320] (II) AMDGPU(1): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[ 41.320] (==) AMDGPU(1): Default visual is TrueColor
[ 41.320] () AMDGPU(1): Option “ZaphodHeads” “DisplayPort-2”
[ 41.320] (==) AMDGPU(1): RGB weight 888
[ 41.320] (II) AMDGPU(1): Using 8 bits per RGB (8 bit DAC)
[ 41.320] (–) AMDGPU(1): Chipset: “AMD Radeon Pro WX 3200 Series” (ChipID = 0x6981)
[ 41.320] (II) Loading sub module “fb”
[ 41.320] (II) LoadModule: “fb”
[ 41.320] (II) Module “fb” already built-in
[ 41.320] (II) Loading sub module “dri2”
[ 41.320] (II) LoadModule: “dri2”
[ 41.320] (II) Module “dri2” already built-in
[ 41.330] (II) Loading sub module “glamoregl”
[ 41.330] (II) LoadModule: “glamoregl”
[ 41.330] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[ 41.330] (II) Module glamoregl: vendor=“X.Org Foundation”
[ 41.330] compiled for 1.21.1.4, module version = 1.0.1
[ 41.330] ABI class: X.Org ANSI C Emulation, version 0.4
[ 41.342] (II) AMDGPU(1): glamor X acceleration enabled on AMD Radeon Pro WX 3200 Series (polaris12, LLVM 15.0.7, DRM 3.54, 6.5.0-17-generic)
[ 41.342] (II) AMDGPU(1): glamor detected, initialising EGL layer.
[ 41.342] (==) AMDGPU(1): TearFree property default: auto
[ 41.342] (==) AMDGPU(1): VariableRefresh: disabled
[ 41.342] (==) AMDGPU(1): AsyncFlipSecondaries: disabled
[ 41.342] (II) AMDGPU(1): KMS Pageflipping: enabled
[ 41.358] (II) AMDGPU(1): Output DisplayPort-2 using monitor section DisplayPort-2
[ 41.374] (II) AMDGPU(1): EDID for output DisplayPort-2
[ 41.375] (II) AMDGPU(1): Manufacturer: ACI Model: 24a4 Serial#: 16843009
[ 41.375] (II) AMDGPU(1): Year: 2014 Week: 26
[ 41.375] (II) AMDGPU(1): EDID Version: 1.4
[ 41.375] (II) AMDGPU(1): Digital Display Input
[ 41.375] (II) AMDGPU(1): 8 bits per channel
[ 41.375] (II) AMDGPU(1): Digital interface is DisplayPort
[ 41.375] (II) AMDGPU(1): Max Image Size [cm]: horiz.: 53 vert.: 30
[ 41.375] (II) AMDGPU(1): Gamma: 2.20
[ 41.375] (II) AMDGPU(1): DPMS capabilities: Off
[ 41.375] (II) AMDGPU(1): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 YCrCb 4:2:2
[ 41.375] (II) AMDGPU(1): First detailed timing is preferred mode
[ 41.375] (II) AMDGPU(1): Preferred mode is native pixel format and refresh rate
[ 41.375] (II) AMDGPU(1): redX: 0.650 redY: 0.329 greenX: 0.331 greenY: 0.622
[ 41.375] (II) AMDGPU(1): blueX: 0.151 blueY: 0.053 whiteX: 0.313 whiteY: 0.329
[ 41.375] (II) AMDGPU(1): Supported established timings:
[ 41.375] (II) AMDGPU(1): 720x400@70Hz
[ 41.375] (II) AMDGPU(1): 640x480@60Hz
[ 41.375] (II) AMDGPU(1): 640x480@67Hz
[ 41.375] (II) AMDGPU(1): 640x480@75Hz
[ 41.375] (II) AMDGPU(1): 800x600@56Hz
[ 41.375] (II) AMDGPU(1): 800x600@60Hz
[ 41.375] (II) AMDGPU(1): 800x600@72Hz
[ 41.375] (II) AMDGPU(1): 800x600@75Hz
[ 41.375] (II) AMDGPU(1): 832x624@75Hz
[ 41.375] (II) AMDGPU(1): 1024x768@60Hz
[ 41.375] (II) AMDGPU(1): 1024x768@70Hz
[ 41.375] (II) AMDGPU(1): 1024x768@75Hz
[ 41.375] (II) AMDGPU(1): 1280x1024@75Hz
[ 41.375] (II) AMDGPU(1): Manufacturer’s mask: 0
[ 41.375] (II) AMDGPU(1): Supported standard timings:
[ 41.375] (II) AMDGPU(1): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
[ 41.375] (II) AMDGPU(1): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 41.375] (II) AMDGPU(1): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
[ 41.375] (II) AMDGPU(1): #3: hsize: 1280 vsize 720 refresh: 60 vid: 49281
[ 41.375] (II) AMDGPU(1): #4: hsize: 1280 vsize 800 refresh: 60 vid: 129
[ 41.375] (II) AMDGPU(1): #5: hsize: 1440 vsize 900 refresh: 60 vid: 149
[ 41.375] (II) AMDGPU(1): #6: hsize: 1680 vsize 1050 refresh: 60 vid: 179
[ 41.375] (II) AMDGPU(1): Supported detailed timing:
[ 41.375] (II) AMDGPU(1): clock: 148.5 MHz Image Size: 531 x 299 mm
[ 41.375] (II) AMDGPU(1): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 41.375] (II) AMDGPU(1): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
[ 41.375] (II) AMDGPU(1): Ranges: V min: 50 V max: 150 Hz, H min: 30 H max: 160 kHz, PixClock max 335 MHz
[ 41.375] (II) AMDGPU(1): Monitor name: VG248
[ 41.375] (II) AMDGPU(1): Serial No: E6LMQS099813
[ 41.375] (II) AMDGPU(1): Supported detailed timing:
[ 41.375] (II) AMDGPU(1): clock: 148.5 MHz Image Size: 531 x 299 mm
[ 41.375] (II) AMDGPU(1): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 41.375] (II) AMDGPU(1): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
[ 41.375] (II) AMDGPU(1): Supported detailed timing:
[ 41.375] (II) AMDGPU(1): clock: 198.5 MHz Image Size: 531 x 299 mm
[ 41.375] (II) AMDGPU(1): h_active: 1920 h_sync: 1968 h_sync_end 2000 h_blank_end 2080 h_border: 0
[ 41.375] (II) AMDGPU(1): v_active: 1080 v_sync: 1083 v_sync_end 1088 v_blanking: 1124 v_border: 0
[ 41.375] (II) AMDGPU(1): Supported detailed timing:
[ 41.375] (II) AMDGPU(1): clock: 235.5 MHz Image Size: 531 x 299 mm
[ 41.375] (II) AMDGPU(1): h_active: 1920 h_sync: 1968 h_sync_end 2000 h_blank_end 2080 h_border: 0
[ 41.375] (II) AMDGPU(1): v_active: 1080 v_sync: 1083 v_sync_end 1088 v_blanking: 1133 v_border: 0
[ 41.375] (II) AMDGPU(1): Supported detailed timing:
[ 41.375] (II) AMDGPU(1): clock: 285.5 MHz Image Size: 531 x 299 mm
[ 41.375] (II) AMDGPU(1): h_active: 1920 h_sync: 1968 h_sync_end 2000 h_blank_end 2080 h_border: 0
[ 41.375] (II) AMDGPU(1): v_active: 1080 v_sync: 1083 v_sync_end 1088 v_blanking: 1144 v_border: 0
[ 41.375] (II) AMDGPU(1): Supported detailed timing:
[ 41.375] (II) AMDGPU(1): clock: 325.1 MHz Image Size: 531 x 299 mm
[ 41.375] (II) AMDGPU(1): h_active: 1920 h_sync: 1944 h_sync_end 1976 h_blank_end 2056 h_border: 0
[ 41.375] (II) AMDGPU(1): v_active: 1080 v_sync: 1083 v_sync_end 1088 v_blanking: 1098 v_border: 0
[ 41.375] (II) AMDGPU(1): Number of EDID sections to follow: 1
[ 41.375] (II) AMDGPU(1): EDID (in hex):
[ 41.375] (II) AMDGPU(1): 00ffffffffffff000469a42401010101
[ 41.375] (II) AMDGPU(1): 1a180104a5351e783a9de5a654549f26
[ 41.375] (II) AMDGPU(1): 0d5054b7ef00714f8180814081c08100
[ 41.375] (II) AMDGPU(1): 9500b3000101023a801871382d40582c
[ 41.375] (II) AMDGPU(1): 4500132b2100001e000000fd0032961e
[ 41.375] (II) AMDGPU(1): a021000a202020202020000000fc0056
[ 41.375] (II) AMDGPU(1): 473234380a20202020202020000000ff
[ 41.375] (II) AMDGPU(1): 0045364c4d51533039393831330a01b3
[ 41.375] (II) AMDGPU(1): 020318f14b900504030201111213141f
[ 41.375] (II) AMDGPU(1): 2309070783010000023a801871382d40
[ 41.375] (II) AMDGPU(1): 582c4500132b2100001e8a4d80a07038
[ 41.375] (II) AMDGPU(1): 2c4030203500132b2100001afe5b80a0
[ 41.375] (II) AMDGPU(1): 7038354030203500132b2100001a866f
[ 41.375] (II) AMDGPU(1): 80a07038404030203500132b2100001a
[ 41.375] (II) AMDGPU(1): fc7e80887038124018203500132b2100
[ 41.375] (II) AMDGPU(1): 001e0000000000000000000000000073
[ 41.375] (II) AMDGPU(1): Printing probed modes for output DisplayPort-2
[ 41.375] (II) AMDGPU(1): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[ 41.375] (II) AMDGPU(1): Modeline "1920x1080"x144.0 325.08 1920 1944 1976 2056 1080 1083 1088 1098 +hsync +vsync (158.1 kHz e)
[ 41.375] (II) AMDGPU(1): Modeline "1920x1080"x120.0 285.50 1920 1968 2000 2080 1080 1083 1088 1144 +hsync -vsync (137.3 kHz e)
…
That log output - and 90-ptb.xorg.conf generated based on it - looks like your first monitor for Screen 0 and the desktop GUI is plugged into the video output of the Intel onboard graphics chip instead of the AMD. As the XOrgConfCreator generated config file does not allow for use of the Intel chip, AMD only, your experimenter display would be dead.
So maybe simply plugging both monitors into the AMD, then running XOrgConfCreator again, might do the trick already. Or disabling the Intel chip in the EFI firmware settings as I said before.
.