# Matlab + Intel graphics plotting bug again (Was: X screen configuration doesn't work) **URL:** \ **Category:** Bugs & Features\ **Tags:** linux, gpu\ **Created:** [November 20, 2023, 9:37am UTC](https://psychtoolbox.discourse.group/t/matlab-intel-graphics-plotting-bug-again-was-x-screen-configuration-doesnt-work/5177 "2023-11-20T09:37:08Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![Cemre](https://avatars.discourse-cdn.com/v4/letter/c/f475e1/32.png) [@Cemre](https://psychtoolbox.discourse.group/u/Cemre)\ **Post date:** [November 20, 2023, 9:37am UTC](https://psychtoolbox.discourse.group/t/matlab-intel-graphics-plotting-bug-again-was-x-screen-configuration-doesnt-work/5177/1 "2023-11-20T09:37:09Z")
Hello, PTB community! 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: ```auto 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 ]]] 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 ---
**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\ **Post date:** [November 20, 2023, 4:13pm UTC](https://psychtoolbox.discourse.group/t/matlab-intel-graphics-plotting-bug-again-was-x-screen-configuration-doesnt-work/5177/2 "2023-11-20T16:13:01Z")
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: > [@MATLAB starts with warning after Psychtoolbox installation](https://psychtoolbox.discourse.group/t/matlab-starts-with-warning-after-psychtoolbox-installation/4661/2): > > Background: This is a bug in the Matlab OpenGL hardware accelerated graphics and plotting system of all Matlab versions on Linux. I reported the problem to our Mathworks contact in the past, but the problem wasn’t resolved so far for more than a year. The bug triggers specifically on Intel graphics chips (and the just released Intel “Arc” discrete graphics cards) with the modern Intel iris graphics driver, e.g., as used on Ubuntu 20.04-LTS and later and similar modern distributions. The bug doe… **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: > [@Workaround for R2020b plotting brokeness on Linux with modern Intel graphics chips](https://psychtoolbox.discourse.group/t/workaround-for-r2020b-plotting-brokeness-on-linux-with-modern-intel-graphics-chips/3543): > > I just tested Matlab R2020b on Ubuntu 20.04-LTS with a modern Intel graphics chip that uses the “new” (well at least a year old by now) iris OpenGL graphics driver. While Psychtoolbox works perfectly as expected, Matlab itself spews some error messages, and plot()ing is broken. Apparently the Mathworks graphics team is just as bad at most basic graphics compatibility testing now as it was 3 years ago when plotting with AMD was broken for a very similar reason - History repeating, sad… Anyway, h… -mario ---
**Author:** ![Cemre](https://avatars.discourse-cdn.com/v4/letter/c/f475e1/32.png) [@Cemre](https://psychtoolbox.discourse.group/u/Cemre)\ **Post date:** [January 18, 2024, 8:38am UTC](https://psychtoolbox.discourse.group/t/matlab-intel-graphics-plotting-bug-again-was-x-screen-configuration-doesnt-work/5177/3 "2024-01-18T08:38:11Z")
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](https://psychtoolbox.discourse.group/t/amd-graphics-card/123/2) 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? ---
**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\ **Post date:** [January 25, 2024, 6:39pm UTC](https://psychtoolbox.discourse.group/t/matlab-intel-graphics-plotting-bug-again-was-x-screen-configuration-doesnt-work/5177/4 "2024-01-25T18:39:37Z")
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. ---
**Author:** ![Cemre](https://avatars.discourse-cdn.com/v4/letter/c/f475e1/32.png) [@Cemre](https://psychtoolbox.discourse.group/u/Cemre)\ **Post date:** [February 2, 2024, 8:05am UTC](https://psychtoolbox.discourse.group/t/matlab-intel-graphics-plotting-bug-again-was-x-screen-configuration-doesnt-work/5177/5 "2024-02-02T08:05:44Z")
Hi Mario, we might screw up our system but we couldn’t track it down. So, could you help us to dig up the issue and solve it? authentication token: 6YAFMXYD-2024229149:0b106911636f52ae4d0216a177fa346f59aaba817c1aefd9033901f84a19f980 ---
**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\ **Post date:** [February 2, 2024, 4:23pm UTC](https://psychtoolbox.discourse.group/t/matlab-intel-graphics-plotting-bug-again-was-x-screen-configuration-doesnt-work/5177/6 "2024-02-02T16:23:10Z")
Hi Cemre, validated - Up to 30 minutes of support. How was Psychtoolbox installed? If it was via NeuroDebian, did you run `PsychLinuxConfiguration` once after installation or update? What is the output (in a terminal) of: `ls -l /etc/X11/xorg.conf.d/` and of `ls -l /etc/X11/ | grep xorg` What is the output of `XOrgConfSelector` if you retry? -mario [15 out of 30 minutes paid support used] ---
**Author:** ![Cemre](https://avatars.discourse-cdn.com/v4/letter/c/f475e1/32.png) [@Cemre](https://psychtoolbox.discourse.group/u/Cemre)\ **Post date:** [February 7, 2024, 10:55am UTC](https://psychtoolbox.discourse.group/t/matlab-intel-graphics-plotting-bug-again-was-x-screen-configuration-doesnt-work/5177/7 "2024-02-07T10:55:57Z")
I followed the instructions for installation via NeuroDebian. I run PsychLinuxConfiguration as well. On terminal: ```auto 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: ```auto >> 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. Cemre ---
**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\ **Post date:** [February 7, 2024, 8:29pm UTC](https://psychtoolbox.discourse.group/t/matlab-intel-graphics-plotting-bug-again-was-x-screen-configuration-doesnt-work/5177/8 "2024-02-07T20:29:54Z")
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. When it asks about “Should i create or configure a X11 config directory that is writable for you?” you should answer y for yes. After that, XOrgConfSelector should be able to write files. You could download the new future XOrgConfSelector from here, for improved error reporting: [https://raw.githubusercontent.com/kleinerm/Psychtoolbox-3/master/Psychtoolbox/PsychHardware/XOrgConfSelector.m](https://raw.githubusercontent.com/kleinerm/Psychtoolbox-3/master/Psychtoolbox/PsychHardware/XOrgConfSelector.m) 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. [45 minutes out of 30 paid minutes used] ---
**Author:** ![Cemre](https://avatars.discourse-cdn.com/v4/letter/c/f475e1/32.png) [@Cemre](https://psychtoolbox.discourse.group/u/Cemre)\ **Post date:** [February 15, 2024, 2:48pm UTC](https://psychtoolbox.discourse.group/t/matlab-intel-graphics-plotting-bug-again-was-x-screen-configuration-doesnt-work/5177/9 "2024-02-15T14:48:18Z")
Thanks Mario, 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. ```auto 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. Cemre ---
**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\ **Post date:** [February 15, 2024, 4:47pm UTC](https://psychtoolbox.discourse.group/t/matlab-intel-graphics-plotting-bug-again-was-x-screen-configuration-doesnt-work/5177/10 "2024-02-15T16:47:31Z")
> [@Cemre](#): > > So, I logged in as allg\_admin this time. > > ```auto > 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. So this looks good now. Proper file and directory ownerships and permissions, new XOrgConfSelector not complaining. `PsychLinuxConfiguration` did the trick 🙂 . > [@](#): > > Should I delete something or reinstall everything? 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` > [@](#): > > 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. > > 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. 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`. 1. To get your display back, login to a text console (e.g., CTRL+ALT+F3). 2. 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. 3. `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? — 1. If you want to go AMD only, reboot the machine, check that things are working again, then reboot into the system EFI setup menu. 2. 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. 3. 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] ---
**Author:** ![Cemre](https://avatars.discourse-cdn.com/v4/letter/c/f475e1/32.png) [@Cemre](https://psychtoolbox.discourse.group/u/Cemre)\ **Post date:** [February 16, 2024, 10:09am UTC](https://psychtoolbox.discourse.group/t/matlab-intel-graphics-plotting-bug-again-was-x-screen-configuration-doesnt-work/5177/11 "2024-02-16T10:09:25Z")
Here are the contents of the files. I’ll continue with your suggestions, though. I’lll update when I’m done. `/etc/X11/xorg.conf.d/90-ptbxorg.conf` ![Screenshot from 2024-02-16 11-03-09](https://global.discourse-cdn.com/free1/uploads/psychtoolbox/original/1X/0fce049cdbb00f04afd7c342d7b4e58c78581241.png) `/home/username/.local/share/xorg/Xorg.0.log` > [41.210] > [X.Org](http://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](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](http://X.Org) ANSI C Emulation: 0.4 > [41.219] [X.Org](http://X.Org) Video Driver: 25.2 > [41.219] [X.Org](http://X.Org) XInput driver : 24.4 > [41.219] [X.Org](http://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](http://X.Org) Foundation” > [41.235] compiled for 1.21.1.4, module version = 1.0.0 > [41.235] ABI class: [X.Org](http://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](http://X.Org) Foundation” > [41.238] compiled for 1.21.1.4, module version = 22.0.0 > [41.239] Module class: [X.Org](http://X.Org) Video Driver > [41.239] ABI class: [X.Org](http://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](http://X.Org) Foundation” > [41.289] compiled for 1.21.1.4, module version = 1.0.1 > [41.289] ABI class: [X.Org](http://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](http://X.Org) Foundation” > [41.330] compiled for 1.21.1.4, module version = 1.0.1 > [41.330] ABI class: [X.Org](http://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) > … ---
**Author:** ![Cemre](https://avatars.discourse-cdn.com/v4/letter/c/f475e1/32.png) [@Cemre](https://psychtoolbox.discourse.group/u/Cemre)\ **Post date:** [February 16, 2024, 10:09am UTC](https://psychtoolbox.discourse.group/t/matlab-intel-graphics-plotting-bug-again-was-x-screen-configuration-doesnt-work/5177/12 "2024-02-16T10:09:41Z")
… > [41.376] (II) AMDGPU(1): Modeline "1920x1080"x99.9 235.50 1920 1968 2000 2080 1080 1083 1088 1133 +hsync -vsync (113.2 kHz e) > [41.376] (II) AMDGPU(1): Modeline "1920x1080"x84.9 198.50 1920 1968 2000 2080 1080 1083 1088 1124 +hsync -vsync (95.4 kHz e) > [41.376] (II) AMDGPU(1): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) > [41.376] (II) AMDGPU(1): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e) > [41.376] (II) AMDGPU(1): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e) > [41.376] (II) AMDGPU(1): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) > [41.376] (II) AMDGPU(1): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) > [41.376] (II) AMDGPU(1): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e) > [41.376] (II) AMDGPU(1): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e) > [41.376] (II) AMDGPU(1): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 -hsync +vsync (49.7 kHz e) > [41.376] (II) AMDGPU(1): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) > [41.376] (II) AMDGPU(1): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) > [41.376] (II) AMDGPU(1): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) > [41.376] (II) AMDGPU(1): Modeline "1280x720"x59.9 74.18 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) > [41.376] (II) AMDGPU(1): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) > [41.376] (II) AMDGPU(1): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) > [41.376] (II) AMDGPU(1): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) > [41.376] (II) AMDGPU(1): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) > [41.376] (II) AMDGPU(1): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) > [41.376] (II) AMDGPU(1): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) > [41.376] (II) AMDGPU(1): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) > [41.376] (II) AMDGPU(1): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) > [41.376] (II) AMDGPU(1): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) > [41.376] (II) AMDGPU(1): Modeline "720x480"x60.0 27.03 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) > [41.376] (II) AMDGPU(1): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) > [41.376] (II) AMDGPU(1): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) > [41.376] (II) AMDGPU(1): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) > [41.376] (II) AMDGPU(1): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) > [41.376] (II) AMDGPU(1): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) > [41.376] (II) AMDGPU(1): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) > [41.376] (II) AMDGPU(1): Output DisplayPort-2 connected > [41.376] (II) AMDGPU(1): Using exact sizes for initial modes > [41.376] (II) AMDGPU(1): Output DisplayPort-2 using initial mode 1920x1080 +0+0 > [41.376] (II) AMDGPU(1): mem size init: gart size :f4cc0000 vram size: s:fea50000 visible:102a9000 > [41.376] (==) AMDGPU(1): DPI set to (96, 96) > [41.376] (==) AMDGPU(1): Using gamma correction (1.0, 1.0, 1.0) > [41.376] (II) Loading sub module “ramdac” > [41.376] (II) LoadModule: “ramdac” > [41.376] (II) Module “ramdac” already built-in > [41.378] (II) UnloadModule: “amdgpu” > [41.378] (II) UnloadSubModule: “glamoregl” > [41.378] (II) Unloading glamoregl > [41.382] (II) AMDGPU(0): [DRI2] Setup complete > [41.382] (II) AMDGPU(0): [DRI2] DRI driver: radeonsi > [41.382] (II) AMDGPU(0): [DRI2] VDPAU driver: radeonsi > [41.382] (II) AMDGPU(0): Front buffer pitch: 7680 bytes > [41.383] (II) AMDGPU(0): SYNC extension fences enabled > [41.384] (II) AMDGPU(0): Present extension enabled > [41.384] (==) AMDGPU(0): DRI3 enabled > [41.384] (==) AMDGPU(0): Backing store enabled > [41.384] (II) AMDGPU(0): Direct rendering enabled > [41.438] (II) AMDGPU(0): Use GLAMOR acceleration. > [41.438] (II) AMDGPU(0): Acceleration enabled > [41.438] (==) AMDGPU(0): DPMS enabled > [41.438] (==) AMDGPU(0): Silken mouse enabled > [41.440] (II) AMDGPU(0): Set up textured video (glamor) > [41.451] (II) Initializing extension Generic Event Extension > [41.451] (II) Initializing extension SHAPE > [41.451] (II) Initializing extension MIT-SHM > [41.451] (II) Initializing extension XInputExtension > [41.452] (II) Initializing extension XTEST > [41.452] (II) Initializing extension BIG-REQUESTS > [41.452] (II) Initializing extension SYNC > [41.453] (II) Initializing extension XKEYBOARD > [41.453] (II) Initializing extension XC-MISC > [41.453] (II) Initializing extension SECURITY > [41.453] (II) Initializing extension XFIXES > [41.453] (II) Initializing extension RENDER > [41.453] (II) Initializing extension RANDR > [41.453] (II) Initializing extension COMPOSITE > [41.454] (II) Initializing extension DAMAGE > [41.454] (II) Initializing extension MIT-SCREEN-SAVER > [41.454] (II) Initializing extension DOUBLE-BUFFER > [41.454] (II) Initializing extension RECORD > [41.454] (II) Initializing extension DPMS > [41.454] (II) Initializing extension Present > [41.454] (II) Initializing extension DRI3 > [41.455] (II) Initializing extension X-Resource > [41.455] (II) Initializing extension XVideo > [41.455] (II) Initializing extension XVideo-MotionCompensation > [41.455] (II) Initializing extension SELinux > [41.455] (II) SELinux: Disabled on system > [41.455] (II) Initializing extension GLX > [41.469] (II) AIGLX: Loaded and initialized radeonsi > [41.470] (II) GLX: Initialized DRI2 GL provider for screen 0 > [41.470] (II) Initializing extension XFree86-VidModeExtension > [41.470] (II) Initializing extension XFree86-DGA > [41.470] (II) Initializing extension XFree86-DRI > [41.470] (II) Initializing extension DRI2 > [41.471] (II) AMDGPU(0): Setting screen physical size to 508 x 285 > [41.592] (II) config/udev: Adding input device Power Button (/dev/input/event1) > [41.592] (**) Power Button: Applying InputClass “libinput keyboard catchall” > [41.592] (II) LoadModule: “libinput” > [41.592] (II) Loading /usr/lib/xorg/modules/input/libinput\_drv.so > [41.597] (II) Module libinput: vendor=“[X.Org](http://X.Org) Foundation” > [41.597] compiled for 1.20.14, module version = 1.2.1 > [41.597] Module class: [X.Org](http://X.Org) XInput Driver > [41.597] ABI class: [X.Org](http://X.Org) XInput driver, version 24.1 > [41.597] (II) Using input driver ‘libinput’ for ‘Power Button’ > [41.599] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 30 paused 0 > [41.599] (**) Power Button: always reports core events > [41.599] (**) Option “Device” “/dev/input/event1” > [41.601] (II) event1 - Power Button: is tagged by udev as: Keyboard > [41.601] (II) event1 - Power Button: device is a keyboard > [41.602] (II) event1 - Power Button: device removed > [41.602] (**) Option “config\_info” “udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1” > [41.602] (II) XINPUT: Adding extended input device “Power Button” (type: KEYBOARD, id 6) > [41.602] (**) Option “xkb\_model” “pc105” > [41.602] (**) Option “xkb\_layout” “at” > [41.627] (II) event1 - Power Button: is tagged by udev as: Keyboard > [41.627] (II) event1 - Power Button: device is a keyboard > [41.628] (II) config/udev: Adding input device Video Bus (/dev/input/event13) > [41.628] (**) Video Bus: Applying InputClass “libinput keyboard catchall” > [41.628] (II) Using input driver ‘libinput’ for ‘Video Bus’ > [41.629] (II) systemd-logind: got fd for /dev/input/event13 13:77 fd 33 paused 0 > [41.629] (**) Video Bus: always reports core events > [41.629] (**) Option “Device” “/dev/input/event13” > [41.630] (II) event13 - Video Bus: is tagged by udev as: Keyboard > [41.631] (II) event13 - Video Bus: device is a keyboard > [41.631] (II) event13 - Video Bus: device removed > [41.631] (**) Option “config\_info” “udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input13/event13” > [41.631] (II) XINPUT: Adding extended input device “Video Bus” (type: KEYBOARD, id 7) > [41.631] (**) Option “xkb\_model” “pc105” > [41.631] (**) Option “xkb\_layout” “at” > [41.632] (II) event13 - Video Bus: is tagged by udev as: Keyboard > [41.632] (II) event13 - Video Bus: device is a keyboard > [41.633] (II) config/udev: Adding input device Power Button (/dev/input/event0) > [41.633] (**) Power Button: Applying InputClass “libinput keyboard catchall” > [41.633] (II) Using input driver ‘libinput’ for ‘Power Button’ > [41.634] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 34 paused 0 > [41.634] (**) Power Button: always reports core events > [41.634] (**) Option “Device” “/dev/input/event0” > [41.635] (II) event0 - Power Button: is tagged by udev as: Keyboard > [41.635] (II) event0 - Power Button: device is a keyboard > [41.635] (II) event0 - Power Button: device removed > [41.635] (**) Option “config\_info” “udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0” > [41.635] (II) XINPUT: Adding extended input device “Power Button” (type: KEYBOARD, id 8) > [41.635] (**) Option “xkb\_model” “pc105” > [41.635] (**) Option “xkb\_layout” “at” > [41.638] (II) event0 - Power Button: is tagged by udev as: Keyboard > [41.639] (II) event0 - Power Button: device is a keyboard > [41.640] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=8 (/dev/input/event10) > [41.640] (II) No input driver specified, ignoring this device. > [41.640] (II) This device may have been added with another device file. > [41.640] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=9 (/dev/input/event11) > [41.641] (II) No input driver specified, ignoring this device. > [41.641] (II) This device may have been added with another device file. > [41.641] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=10 (/dev/input/event12) > [41.641] (II) No input driver specified, ignoring this device. > [41.641] (II) This device may have been added with another device file. > [41.641] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=3 (/dev/input/event8) > [41.641] (II) No input driver specified, ignoring this device. > [41.642] (II) This device may have been added with another device file. > [41.643] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=7 (/dev/input/event9) > [41.643] (II) No input driver specified, ignoring this device. > [41.643] (II) This device may have been added with another device file. > [41.643] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=3 (/dev/input/event14) > [41.644] (II) No input driver specified, ignoring this device. > [41.644] (II) This device may have been added with another device file. > [41.644] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=7 (/dev/input/event15) > [41.644] (II) No input driver specified, ignoring this device. > [41.644] (II) This device may have been added with another device file. > [41.644] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=8 (/dev/input/event16) > [41.645] (II) No input driver specified, ignoring this device. > [41.645] (II) This device may have been added with another device file. > [41.646] (II) config/udev: Adding input device SteelSeries SteelSeries Apex M800 Keyboard (/dev/input/event3) > [41.646] (**) SteelSeries SteelSeries Apex M800 Keyboard: Applying InputClass “libinput keyboard catchall” > [41.646] (II) Using input driver ‘libinput’ for ‘SteelSeries SteelSeries Apex M800 Keyboard’ > [41.646] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 35 paused 0 > [41.646] (**) SteelSeries SteelSeries Apex M800 Keyboard: always reports core events > [41.646] (**) Option “Device” “/dev/input/event3” > [41.648] (II) event3 - SteelSeries SteelSeries Apex M800 Keyboard: is tagged by udev as: Keyboard > [41.648] (II) event3 - SteelSeries SteelSeries Apex M800 Keyboard: device is a keyboard > [41.649] (II) event3 - SteelSeries SteelSeries Apex M800 Keyboard: device removed > [41.649] (**) Option “config\_info” “udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10.1/3-10.1:1.1/0003:1038:1600.0003/input/input3/event3” > [41.649] (II) XINPUT: Adding extended input device “SteelSeries SteelSeries Apex M800 Keyboard” (type: KEYBOARD, id 9) > [41.649] (**) Option “xkb\_model” “pc105” > [41.649] (**) Option “xkb\_layout” “at” > [41.651] (II) event3 - SteelSeries SteelSeries Apex M800 Keyboard: is tagged by udev as: Keyboard > [41.651] (II) event3 - SteelSeries SteelSeries Apex M800 Keyboard: device is a keyboard > [41.652] (II) config/udev: Adding input device SteelSeries SteelSeries Apex M800 Keyboard Consumer Control (/dev/input/event4) > [41.652] (**) SteelSeries SteelSeries Apex M800 Keyboard Consumer Control: Applying InputClass “libinput keyboard catchall” > [41.652] (II) Using input driver ‘libinput’ for ‘SteelSeries SteelSeries Apex M800 Keyboard Consumer Control’ > [41.653] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 36 paused 0 > [41.653] (**) SteelSeries SteelSeries Apex M800 Keyboard Consumer Control: always reports core events > [41.653] (**) Option “Device” “/dev/input/event4” > [41.655] (II) event4 - SteelSeries SteelSeries Apex M800 Keyboard Consumer Control: is tagged by udev as: Keyboard > [41.655] (II) event4 - SteelSeries SteelSeries Apex M800 Keyboard Consumer Control: device is a keyboard > [41.655] (II) event4 - SteelSeries SteelSeries Apex M800 Keyboard Consumer Control: device removed > [41.655] (II) libinput: SteelSeries SteelSeries Apex M800 Keyboard Consumer Control: needs a virtual subdevice > [41.655] (**) Option “config\_info” “udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10.1/3-10.1:1.2/0003:1038:1600.0004/input/input4/event4” > [41.655] (II) XINPUT: Adding extended input device “SteelSeries SteelSeries Apex M800 Keyboard Consumer Control” (type: MOUSE, id 10) > [41.655] (**) Option “AccelerationScheme” “none” > [41.655] (**) SteelSeries SteelSeries Apex M800 Keyboard Consumer Control: (accel) selected scheme none/0 > [41.655] (**) SteelSeries SteelSeries Apex M800 Keyboard Consumer Control: (accel) acceleration factor: 2.000 > [41.655] (**) SteelSeries SteelSeries Apex M800 Keyboard Consumer Control: (accel) acceleration threshold: 4 > [41.657] (II) event4 - SteelSeries SteelSeries Apex M800 Keyboard Consumer Control: is tagged by udev as: Keyboard > [41.657] (II) event4 - SteelSeries SteelSeries Apex M800 Keyboard Consumer Control: device is a keyboard > [41.659] (II) config/udev: Adding input device SteelSeries SteelSeries Apex M800 Keyboard Mouse (/dev/input/event5) > [41.659] (**) SteelSeries SteelSeries Apex M800 Keyboard Mouse: Applying InputClass “libinput pointer catchall” > [41.659] (II) Using input driver ‘libinput’ for ‘SteelSeries SteelSeries Apex M800 Keyboard Mouse’ > [41.660] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 37 paused 0 > [41.660] (**) SteelSeries SteelSeries Apex M800 Keyboard Mouse: always reports core events > [41.660] (**) Option “Device” “/dev/input/event5” > [41.663] (II) event5 - SteelSeries SteelSeries Apex M800 Keyboard Mouse: is tagged by udev as: Mouse > [41.663] (II) event5 - SteelSeries SteelSeries Apex M800 Keyboard Mouse: device is a pointer > [41.663] (II) event5 - SteelSeries SteelSeries Apex M800 Keyboard Mouse: device removed > [41.663] (**) Option “config\_info” “udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10.1/3-10.1:1.2/0003:1038:1600.0004/input/input5/event5” > [41.663] (II) XINPUT: Adding extended input device “SteelSeries SteelSeries Apex M800 Keyboard Mouse” (type: MOUSE, id 11) > [41.663] (**) Option “AccelerationScheme” “none” > [41.663] (**) SteelSeries SteelSeries Apex M800 Keyboard Mouse: (accel) selected scheme none/0 > [41.663] (**) SteelSeries SteelSeries Apex M800 Keyboard Mouse: (accel) acceleration factor: 2.000 > [41.663] (**) SteelSeries SteelSeries Apex M800 Keyboard Mouse: (accel) acceleration threshold: 4 > [41.665] (II) event5 - SteelSeries SteelSeries Apex M800 Keyboard Mouse: is tagged by udev as: Mouse > [41.665] (II) event5 - SteelSeries SteelSeries Apex M800 Keyboard Mouse: device is a pointer > [41.667] (II) config/udev: Adding input device SteelSeries SteelSeries Apex M800 Keyboard Mouse (/dev/input/mouse1) > [41.667] (II) No input driver specified, ignoring this device. > [41.667] (II) This device may have been added with another device file. > [41.668] (II) config/udev: Adding input device SteelSeries SteelSeries Apex M800 Keyboard (/dev/input/event6) > [41.668] (**) SteelSeries SteelSeries Apex M800 Keyboard: Applying InputClass “libinput keyboard catchall” > [41.668] (II) Using input driver ‘libinput’ for ‘SteelSeries SteelSeries Apex M800 Keyboard’ > [41.669] (II) systemd-logind: got fd for /dev/input/event6 13:70 fd 38 paused 0 > [41.669] (**) SteelSeries SteelSeries Apex M800 Keyboard: always reports core events > [41.669] (**) Option “Device” “/dev/input/event6” > [41.670] (II) event6 - SteelSeries SteelSeries Apex M800 Keyboard: is tagged by udev as: Keyboard > [41.670] (II) event6 - SteelSeries SteelSeries Apex M800 Keyboard: device is a keyboard > [41.671] (II) event6 - SteelSeries SteelSeries Apex M800 Keyboard: device removed > [41.671] (**) Option “config\_info” “udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10.1/3-10.1:1.3/0003:1038:1600.0005/input/input6/event6” > [41.671] (II) XINPUT: Adding extended input device “SteelSeries SteelSeries Apex M800 Keyboard” (type: KEYBOARD, id 12) > [41.671] (**) Option “xkb\_model” “pc105” > [41.671] (**) Option “xkb\_layout” “at” > [41.673] (II) event6 - SteelSeries SteelSeries Apex M800 Keyboard: is tagged by udev as: Keyboard > [41.673] (II) event6 - SteelSeries SteelSeries Apex M800 Keyboard: device is a keyboard > [41.674] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event2) > [41.674] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass “libinput pointer catchall” > [41.674] (II) Using input driver ‘libinput’ for ‘Logitech USB-PS/2 Optical Mouse’ > [41.732] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 39 paused 0 > [41.732] (**) Logitech USB-PS/2 Optical Mouse: always reports core events > [41.732] (**) Option “Device” “/dev/input/event2” > [41.733] (II) event2 - Logitech USB-PS/2 Optical Mouse: is tagged by udev as: Mouse > [41.734] (II) event2 - Logitech USB-PS/2 Optical Mouse: device is a pointer > [41.734] (II) event2 - Logitech USB-PS/2 Optical Mouse: device removed > [41.734] (**) Option “config\_info” “udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/0003:046D:C044.0001/input/input2/event2” > [41.734] (II) XINPUT: Adding extended input device “Logitech USB-PS/2 Optical Mouse” (type: MOUSE, id 13) > [41.734] (**) Option “AccelerationScheme” “none” > [41.734] (**) Logitech USB-PS/2 Optical Mouse: (accel) selected scheme none/0 > [41.734] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000 > [41.734] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4 > [41.735] (II) event2 - Logitech USB-PS/2 Optical Mouse: is tagged by udev as: Mouse > [41.736] (II) event2 - Logitech USB-PS/2 Optical Mouse: device is a pointer > [41.737] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse0) > [41.737] (II) No input driver specified, ignoring this device. > [41.737] (II) This device may have been added with another device file. > [41.737] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event17) > [41.737] (II) No input driver specified, ignoring this device. > [41.737] (II) This device may have been added with another device file. > [41.738] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event18) > [41.738] (II) No input driver specified, ignoring this device. > [41.738] (II) This device may have been added with another device file. > [41.738] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event19) > [41.738] (II) No input driver specified, ignoring this device. > [41.738] (II) This device may have been added with another device file. > [41.739] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event20) > [41.739] (II) No input driver specified, ignoring this device. > [41.739] (II) This device may have been added with another device file. > [41.739] (II) config/udev: Adding input device Dell WMI hotkeys (/dev/input/event7) > [41.739] (**) Dell WMI hotkeys: Applying InputClass “libinput keyboard catchall” > [41.739] (II) Using input driver ‘libinput’ for ‘Dell WMI hotkeys’ > [41.740] (II) systemd-logind: got fd for /dev/input/event7 13:71 fd 40 paused 0 > [41.740] (**) Dell WMI hotkeys: always reports core events > [41.740] (**) Option “Device” “/dev/input/event7” > [41.742] (II) event7 - Dell WMI hotkeys: is tagged by udev as: Keyboard > [41.742] (II) event7 - Dell WMI hotkeys: device is a keyboard > [41.742] (II) event7 - Dell WMI hotkeys: device removed > [41.742] (**) Option “config\_info” “udev:/sys/devices/platform/PNP0C14:00/wmi\_bus/wmi\_bus-PNP0C14:00/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input7/event7” > [41.742] (II) XINPUT: Adding extended input device “Dell WMI hotkeys” (type: KEYBOARD, id 14) > [41.742] (**) Option “xkb\_model” “pc105” > [41.742] (**) Option “xkb\_layout” “at” > [41.743] (II) event7 - Dell WMI hotkeys: is tagged by udev as: Keyboard > [41.744] (II) event7 - Dell WMI hotkeys: device is a keyboard > [41.753] (**) SteelSeries SteelSeries Apex M800 Keyboard Consumer Control: Applying InputClass “libinput keyboard catchall” > [41.753] (II) Using input driver ‘libinput’ for ‘SteelSeries SteelSeries Apex M800 Keyboard Consumer Control’ > [41.753] (II) systemd-logind: returning pre-existing fd for /dev/input/event4 13:68 > [41.753] (**) SteelSeries SteelSeries Apex M800 Keyboard Consumer Control: always reports core events > [41.753] (**) Option “Device” “/dev/input/event4” > [41.753] (II) libinput: SteelSeries SteelSeries Apex M800 Keyboard Consumer Control: is a virtual subdevice > [41.753] (**) Option “config\_info” “udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10.1/3-10.1:1.2/0003:1038:1600.0004/input/input4/event4” > [41.753] (II) XINPUT: Adding extended input device “SteelSeries SteelSeries Apex M800 Keyboard Consumer Control” (type: KEYBOARD, id 15) > [41.753] (**) Option “xkb\_model” “pc105” > [41.753] (**) Option “xkb\_layout” “at” > [42.541] (II) AMDGPU(0): EDID vendor “ACI”, prod id 9380 > [42.542] (II) AMDGPU(0): Using EDID range info for horizontal sync > [42.542] (II) AMDGPU(0): Using EDID range info for vertical refresh > [42.542] (II) AMDGPU(0): Printing DDC gathered Modelines: > [42.542] (II) AMDGPU(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) > [42.542] (II) AMDGPU(0): Modeline "1920x1080"x0.0 198.50 1920 1968 2000 2080 1080 1083 1088 1124 +hsync -vsync (95.4 kHz e) > [42.542] (II) AMDGPU(0): Modeline "1920x1080"x0.0 235.50 1920 1968 2000 2080 1080 1083 1088 1133 +hsync -vsync (113.2 kHz e) > [42.542] (II) AMDGPU(0): Modeline "1920x1080"x0.0 285.50 1920 1968 2000 2080 1080 1083 1088 1144 +hsync -vsync (137.3 kHz e) > [42.542] (II) AMDGPU(0): Modeline "1920x1080"x0.0 325.08 1920 1944 1976 2056 1080 1083 1088 1098 +hsync +vsync (158.1 kHz e) > [42.542] (II) AMDGPU(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e) > [42.542] (II) AMDGPU(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) > [42.542] (II) AMDGPU(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) > [42.542] (II) AMDGPU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) > [42.542] (II) AMDGPU(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) > [42.542] (II) AMDGPU(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) > [42.542] (II) AMDGPU(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e) > [42.542] (II) AMDGPU(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) > [42.542] (II) AMDGPU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) > [42.542] (II) AMDGPU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) > [42.542] (II) AMDGPU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) > [42.542] (II) AMDGPU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) > [42.542] (II) AMDGPU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) > [42.542] (II) AMDGPU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) > [42.542] (II) AMDGPU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) > [42.542] (II) AMDGPU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) > [42.542] (II) AMDGPU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) > [42.542] (II) AMDGPU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) > [42.542] (II) AMDGPU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) > [42.542] (II) AMDGPU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) > [42.542] (II) AMDGPU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) > [42.542] (II) AMDGPU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) > [42.542] (II) AMDGPU(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e) > [42.542] (II) AMDGPU(0): Modeline "1280x800"x0.0 83.50 1280 1352 1480 1680 800 803 809 831 -hsync +vsync (49.7 kHz e) > [42.542] (II) AMDGPU(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e) > [42.542] (II) AMDGPU(0): Modeline "1680x1050"x0.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e) ---
**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\ **Post date:** [February 16, 2024, 4:54pm UTC](https://psychtoolbox.discourse.group/t/matlab-intel-graphics-plotting-bug-again-was-x-screen-configuration-doesnt-work/5177/13 "2024-02-16T16:54:43Z")
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.