You are not logged in.

#1 2018-11-22 14:17:29

koreankiwitea
Member
Registered: 2018-02-12
Posts: 48

[Solved] difficculty in setting up 144hz monitor.

Firstly, sorry if you have seen this post before. I asked on reddit and on irc for help. Wondering if anyone out there can advise me further.

Current setup:

i5-6600k
Nvidia GTX1070
16gb ddr3
asus z170-e motherboard
Benq EX3203R connected directly from the Graphics card to the monitor using DP.

I can get the high refresh rate to work in Windows 10. BUT, full '144hz' didn't work just by setting 'nvidia control panel' or windows display setting. Even though it was detected, the monitor wouldn't reproduce 144hz (the in-monitor setting correctly detected it was indeed receiving 144hz as well, but it clearly was running at sub-60hz even...) The Windows-side solution was to manually create an 'unsupported' resolution setting and bump the refresh rate down to '143hz'. The in-monitor detects it is now receiving 143hz, and it now correctly reproduces the high refresh rate glory.

After going through arch wiki, I tried many solutions and wasn't able to get it to work last night. I manually edited Xorg.conf to be anywhere between 140-143.91 (as reported by xrandr), didn't work. I tried adding modes in xrandr, but the nvidia's "BadMatch" issue occurs. And even if it wasn't, manually doing

xrandr --output DP-0 --mode 2560x1440 --rate 143

Doesn't help either. Interestingly, testing from the range of 140~145 all results in '144hz' being reported in the in-monitor setting.

the output of cvt 2560 1440 I noticed that the pixel clock was reported to have some super high value like ~800 something. But when I run:

nvidia-xconfig --query-gpu-info

the maximum pixel clock rate reports something around ~600. I'm wondering if this has something to do with the issue? or it might be completely unrelated. If I bump the resolution down to 1920x1080 (1080p), the high refreshrate (144hz reported) does indeed work. I'm not sure how to proceed from here. I tried to follow 'exporting edid from windows' but the archwiki's external link is broken so lost my leads from there (because the wiki says I need *.bin file when other online guides exports a *.txt file)

Can you guys help me investigate this? What steps can I take next?

Thank you!

xrandr output supported modes if anyone cares!

$ xrandr
Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 32767 x 32767
DVI-D-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 698mm x 393mm
   2560x1440     59.95*+ 144.00 
   3840x2160     59.94    29.97    25.00    23.98 
   2560x1080    119.88   100.00    59.94 
   1920x1080    143.85   119.93   119.88   100.00    99.90    60.00    59.94    50.00    29.97    25.00    23.98 
   1680x1050     59.95 
   1600x900      60.00 
   1280x1024     75.02    60.02 
   1280x800      59.81 
   1280x720      60.00    59.94    50.00 
   1024x768      75.03    60.00 
   800x600       75.00    60.32 
   720x576       50.00 
   720x480       59.94 
   640x480       75.00    59.94    59.93 
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)

Last edited by koreankiwitea (2018-11-25 16:36:21)


very n00b.

Offline

#2 2018-11-22 19:45:46

seth
Member
Registered: 2012-09-03
Posts: 19,806

Re: [Solved] difficculty in setting up 144hz monitor.

See "NoMaxPClkCheck" in /usr/share/doc/nvidia/README but you're still driving the HW out of spec.

Online

#3 2018-11-22 20:00:22

koreankiwitea
Member
Registered: 2018-02-12
Posts: 48

Re: [Solved] difficculty in setting up 144hz monitor.

seth wrote:

See "NoMaxPClkCheck" in /usr/share/doc/nvidia/README but you're still driving the HW out of spec.

[  1264.252] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): Internal DisplayPort
[  1264.252] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): DFP is not internal to notebook
[  1264.252] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3) Name Aliases:
[  1264.252] (--) NVIDIA(GPU-0):   DFP
[  1264.252] (--) NVIDIA(GPU-0):   DFP-3
[  1264.252] (--) NVIDIA(GPU-0):   DPY-3
[  1264.252] (--) NVIDIA(GPU-0):   DP-0
[  1264.252] (--) NVIDIA(GPU-0):   DPY-EDID-7f4f7068-5959-2042-10e7-fdfbb9453ec3
[  1264.252] (--) NVIDIA(GPU-0):   DP-0
[  1264.252] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): 1440.0 MHz maximum pixel clock
[  1264.252] (--) NVIDIA(GPU-0):
[  1264.252] (--) NVIDIA(GPU-0): --- EDID for BenQ EX3203R (DP-0) ---
[  1264.252] (--) NVIDIA(GPU-0): EDID Version                 : 1.4
[  1264.252] (--) NVIDIA(GPU-0): Manufacturer                 : BNQ
[  1264.252] (--) NVIDIA(GPU-0): Monitor Name                 : BenQ EX3203R
[  1264.252] (--) NVIDIA(GPU-0): Product ID                   : 0x7f66
[  1264.252] (--) NVIDIA(GPU-0): 32-bit Serial Number         : 0x00005445
[  1264.252] (--) NVIDIA(GPU-0): Serial Number String         : R5J00087019
[  1264.252] (--) NVIDIA(GPU-0): Manufacture Date             : 2018, week 21
[  1264.252] (--) NVIDIA(GPU-0): DPMS Capabilities            : Active Off
[  1264.252] (--) NVIDIA(GPU-0): Input Type                   : Digital
[  1264.252] (--) NVIDIA(GPU-0): Prefer first detailed timing : Yes
[  1264.252] (--) NVIDIA(GPU-0): Supports Continuous Frequency: Yes
[  1264.252] (--) NVIDIA(GPU-0): EDID 1.4 YCbCr 422 support   : Yes
[  1264.252] (--) NVIDIA(GPU-0): EDID 1.4 YCbCr 444 support   : Yes
[  1264.252] (--) NVIDIA(GPU-0): Maximum Image Size           : 700 mm x 390 mm
[  1264.252] (--) NVIDIA(GPU-0): Valid HSync Range            : 222.0 kHz - 222.0 kHz
[  1264.252] (--) NVIDIA(GPU-0): Valid VRefresh Range         : 24.0 Hz - 144.0 Hz
[  1264.252] (--) NVIDIA(GPU-0): EDID maximum pixel clock     : 600.0 MHz
[  1264.252] (--) NVIDIA(GPU-0): CEA-861 extension block #    : 0
[  1264.252] (--) NVIDIA(GPU-0):

The monitor input's max pixel clock is 1440Mhz. The monitor itself's max pixel clock is 600.0MHz as reported here in the Edid.
As the post specifies, the monitor's 144hz actually works fine under Windows so I don't think I'm driving the HW out of spec. All are supposed to work here as far as I can work out.


very n00b.

Offline

#4 2018-11-22 20:07:54

seth
Member
Registered: 2012-09-03
Posts: 19,806

Re: [Solved] difficculty in setting up 144hz monitor.

The monitor itself's max pixel clock is 600.0MHz as reported here in the Edid.

Yes, and if you're driving it at 800MHz, that's outside the monitors spec. It could oc. be a bug in the EDID, but there's no clear evidence for that?

Online

#5 2018-11-22 20:10:48

koreankiwitea
Member
Registered: 2018-02-12
Posts: 48

Re: [Solved] difficculty in setting up 144hz monitor.

seth wrote:

The monitor itself's max pixel clock is 600.0MHz as reported here in the Edid.

Yes, and if you're driving it at 800MHz, that's outside the monitors spec. It could oc. be a bug in the EDID, but there's no clear evidence for that?


Huh, you're absolutely right. That's strange. Can you advise me how to investigate this? I might try going into windows and see the EDID there just to check. Because this thing does work on that.


very n00b.

Offline

#6 2018-11-23 08:36:36

seth
Member
Registered: 2012-09-03
Posts: 19,806

Re: [Solved] difficculty in setting up 144hz monitor.

Afaiu you had to "manually create an 'unsupported' resolution" on windows?
Where do the 144Hz in the xrandr output stem from? Autodetected or did you add that modeline by hand?
The EDID is provided by the monitor HW (oc. could still be an interpretation bug on linux, but I doubt that)
Does the tech sheet of the monitor advertise that frequency at that resolution? (Does it list official pixelclock values?)
Overdriving does not necessarily insta-fail, but *could* lead to overheating and long term damage.

Online

#7 2018-11-23 17:04:44

koreankiwitea
Member
Registered: 2018-02-12
Posts: 48

Re: [Solved] difficculty in setting up 144hz monitor.

seth wrote:

Afaiu you had to "manually create an 'unsupported' resolution" on windows?
Where do the 144Hz in the xrandr output stem from? Autodetected or did you add that modeline by hand?
The EDID is provided by the monitor HW (oc. could still be an interpretation bug on linux, but I doubt that)
Does the tech sheet of the monitor advertise that frequency at that resolution? (Does it list official pixelclock values?)
Overdriving does not necessarily insta-fail, but *could* lead to overheating and long term damage.

it was an autodetect. The monitor definitely supports 144Hz. The thing is, if I just set up 144hz on nvidia control panel (Windows), it doesn't work. I need to manually create a profile on windows and bump the refresh rate down to 143Hz. Then it works perfectly. Not sure how to achieve that on linux however.


very n00b.

Offline

#8 2018-11-23 17:07:50

seth
Member
Registered: 2012-09-03
Posts: 19,806

Re: [Solved] difficculty in setting up 144hz monitor.

You can write a 143Hz modeline and select that: https://wiki.archlinux.org/index.php/Xr … esolutions
If it was 120Hz I'd tell you to try a reduced blanking modeline, but it has to be n*60Hz for that to work.

Online

#9 2018-11-23 17:11:18

koreankiwitea
Member
Registered: 2018-02-12
Posts: 48

Re: [Solved] difficculty in setting up 144hz monitor.

seth wrote:

You can write a 143Hz modeline and select that: https://wiki.archlinux.org/index.php/Xr … esolutions
If it was 120Hz I'd tell you to try a reduced blanking modeline, but it has to be n*60Hz for that to work.

The problem is, Nvidia's dev forum says to avoid xrandr and nvidia actively blocks users from setting modes that they don't like. It's absolutely horrendous. XRandR addmode reseults in 'BadMatch' Error which is mostly only shown on Nvidia from blocking unwanted mode. This is why when I set modeline on Xorg, it reverts me back to nvidia-auto-config.


very n00b.

Offline

#10 2018-11-23 17:37:40

seth
Member
Registered: 2012-09-03
Posts: 19,806

Re: [Solved] difficculty in setting up 144hz monitor.

Who in that forum said that? Aaron or some random dude?
nvidia implements the randr protocol, did you add the "NoMaxPClkCheck" option?

Online

#11 2018-11-25 10:25:53

koreankiwitea
Member
Registered: 2018-02-12
Posts: 48

Re: [Solved] difficculty in setting up 144hz monitor.

seth wrote:

Who in that forum said that? Aaron or some random dude?
nvidia implements the randr protocol, did you add the "NoMaxPClkCheck" option?


Hi Seth, Thank you so much for still trying to help me out smile
It's puzzling indeed.

https://devtalk.nvidia.com/default/topi … 00-failed/

Here's the devtalk where nvidia dev (Wayne) says they block non supported modes. and Yes I have NoMaxPClkCheck option enabled, and is visible on the logs.
I'm now trying to see if there is a way to edit my edid manually. Is there a risk of breaking my monitor is I inevitably f* it up?

Thank you


very n00b.

Offline

#12 2018-11-25 12:51:22

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 9,028

Re: [Solved] difficculty in setting up 144hz monitor.

That devtalk topic is about the Tegra X1, a system on a chip with an ARM cpu, northbridge, southbridge, gpu .

On such a system it may make sense to block unsupported modes.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
Did you use the guided installer ? If yes, I can't help you.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#13 2018-11-25 13:05:13

koreankiwitea
Member
Registered: 2018-02-12
Posts: 48

Re: [Solved] difficculty in setting up 144hz monitor.

Lone_Wolf wrote:

That devtalk topic is about the Tegra X1, a system on a chip with an ARM cpu, northbridge, southbridge, gpu .

On such a system it may make sense to block unsupported modes.

Aha. Thank you for the clarification. I'm not sure if external links are allowed, but here's an imgur link to the windows' nvidia that is working. (https://imgur.com/a/HUsjxfN).

On reddit one of the members of the arch's subreddit pointed out to me that xrandr actually just uses the closest mode to the one that I've explicitly configured to.

i.e, if I:

  xrandr --output --mode 2560x1440 --rate 143

Then, because the closest 'legitimate' mode is 144hz, it will just select that as opposed to 143hz. As you can see on Windows' configuration, I need that to be down to 143hz.

Xrandr doesn't work, xorg's configuration also doesn't seem to give me any difference.


very n00b.

Offline

#14 2018-11-25 13:48:24

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 9,028

Re: [Solved] difficculty in setting up 144hz monitor.

The set refresh rate is only input to get suitable timings, we need to know the exact timings.


The screenshot indicates windows sets hsync to 213.07 KHz and the Pixel Clock to 579.5504 MHz.
I've tried to get cvt to achieve similar values with 2560x1440 , but failed sofar.

$ cvt 2560 1440 136.6
# 2560x1440 136.51 Hz (CVT) hsync: 213.10 kHz; pclk: 763.75 MHz
Modeline "2560x1440_136.60"  763.75  2560 2792 3072 3584  1440 1443 1448 1561 -hsync +vsync
$

$ cvt 2560 1440 106.5
# 2560x1440 106.47 Hz (CVT) hsync: 163.22 kHz; pclk: 579.75 MHz
Modeline "2560x1440_106.50"  579.75  2560 2776 3056 3552  1440 1443 1448 1533 -hsync +vsync
$

First one has the same Hsync but higher pixel clock, 2nd one has similar pixel clock but much lower Hsymc.

We need some windows tool that can get the values we need directly from the hardware.


edit

wiki links to http://www.x.org/wiki/FAQVideoModes#Obt … PowerStrip .
PowerStrip is a shareware program from entech taiwan, but they seem to have stopped developing it.

I have found another download link (from a site i do trust) though :
https://www.majorgeeks.com/files/detail … strip.html

Try running that.

Last edited by Lone_Wolf (2018-11-25 14:02:27)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
Did you use the guided installer ? If yes, I can't help you.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#15 2018-11-25 14:45:55

seth
Member
Registered: 2012-09-03
Posts: 19,806

Re: [Solved] difficculty in setting up 144hz monitor.

From the screenshot: shortened H & V totals and reversed H polarity to get the dotclock down.
I will point out again that consulting the monitors specs and check whether it *really* advertises 2560x1440@144Hz and not just "up to" stuff would be a really great idea here.

Online

#16 2018-11-25 14:59:35

koreankiwitea
Member
Registered: 2018-02-12
Posts: 48

Re: [Solved] difficculty in setting up 144hz monitor.

seth wrote:

From the screenshot: shortened H & V totals and reversed H polarity to get the dotclock down.
I will point out again that consulting the monitors specs and check whether it *really* advertises 2560x1440@144Hz and not just "up to" stuff would be a really great idea here.

The monitor's spec is found here (https://www.benq.com/en/monitor/video-e … tions.html). Not sure what you mean by 'up to' since it can be driven to 2560x1440@144hz.

I can see the totals, but what about the three preceding values? What do you mean by shortened? and reversed H polarity, I'm assuming I need to flip positive to negative?

Lone_Wolf wrote:

The set refresh rate is only input to get suitable timings, we need to know the exact timings.

The screenshot indicates windows sets hsync to 213.07 KHz and the Pixel Clock to 579.5504 MHz.
I've tried to get cvt to achieve similar values with 2560x1440 , but failed sofar.

$ cvt 2560 1440 136.6
# 2560x1440 136.51 Hz (CVT) hsync: 213.10 kHz; pclk: 763.75 MHz
Modeline "2560x1440_136.60"  763.75  2560 2792 3072 3584  1440 1443 1448 1561 -hsync +vsync
$

$ cvt 2560 1440 106.5
# 2560x1440 106.47 Hz (CVT) hsync: 163.22 kHz; pclk: 579.75 MHz
Modeline "2560x1440_106.50"  579.75  2560 2776 3056 3552  1440 1443 1448 1533 -hsync +vsync
$

First one has the same Hsync but higher pixel clock, 2nd one has similar pixel clock but much lower Hsymc.

We need some windows tool that can get the values we need directly from the hardware.

edit

wiki links to http://www.x.org/wiki/FAQVideoModes#Obt … PowerStrip .
PowerStrip is a shareware program from entech taiwan, but they seem to have stopped developing it.

I have found another download link (from a site i do trust) though :
https://www.majorgeeks.com/files/detail … strip.html

Try running that.

Hi, the tool that you provided doesn't allow me to go 'advanced monitor profile' as suggested on the website. But the same company that made that tool also provides more passive monitor assessment tool, and I was able to acquire a modeline that I think is being used on Windows.

Detailed timing #1..... 2560x1440p at 144Hz (16:9)
  Modeline............. "2560x1440" 583.600 2560 2568 2600 2720 1440 1465 1473 1490 +hsync +vsync

Applying this to Xorg.conf was interesting. It bumped my resolution all the way up to 4k (not native to monitor) for some reason. It's a similar tool, but as you can see it doesn't actually show me the timing value that you were looking for. I'll keep digging, THank you for the input.


very n00b.

Offline

#17 2018-11-25 15:07:27

seth
Member
Registered: 2012-09-03
Posts: 19,806

Re: [Solved] difficculty in setting up 144hz monitor.

The website doesn't provide an actual table of supported combinations (aslo notice that it says "Resolution (max.)")
That's not a tech spec but a commercial - did you get some paperwork w/ the monitor (or a PDF, at least stuff that is more elaborate than a dozen lines)?
The mere fact that no matter the OS you've to make this kind of an effort to get it at 2560x1440@144 is a VERY strong indicator that this is not a supported setup.

By shortened I mean the values are smaller than usual (cutting down eg. the vblank interval, provoking tearing)

Online

#18 2018-11-25 15:15:42

koreankiwitea
Member
Registered: 2018-02-12
Posts: 48

Re: [Solved] difficculty in setting up 144hz monitor.

seth wrote:

The website doesn't provide an actual table of supported combinations (aslo notice that it says "Resolution (max.)")
That's not a tech spec but a commercial - did you get some paperwork w/ the monitor (or a PDF, at least stuff that is more elaborate than a dozen lines)?
The mere fact that no matter the OS you've to make this kind of an effort to get it at 2560x1440@144 is a VERY strong indicator that this is not a supported setup.

By shortened I mean the values are smaller than usual (cutting down eg. the vblank interval, provoking tearing)

I understand. I called BenQ support team when I got the thing too because it should really be a plug and play kind of thing rather than have the pain to go through the settings myself.

This link(https://www.benq.com/en-us/support/downloads-faq/products/monitor/ex3203r/manual.html) has the pdf that came with the product. under 'Resolution File', it shows in more detail what the thing can do. As far as I can tell, DP supports 144Hz at 2560x1400 on 8 bit 4:4:4.


very n00b.

Offline

#19 2018-11-25 15:45:34

seth
Member
Registered: 2012-09-03
Posts: 19,806

Re: [Solved] difficculty in setting up 144hz monitor.

That's more like it ;-)
And yes, looks legit, but we'll still have to remain below 600MHz and that's only ever possible w/ reduced blanking.
Try

# 2560x1440 @ 144.000 Hz Reduced Blank (CVT) field rate 144.000 Hz; hsync: 222.192 kHz; pclk: 586.59 MHz
Modeline "2560x1440_144.00_rb2"  586.59  2560 2568 2600 2640  1440 1529 1537 1543 +hsync -vsync

This is 2560x1440@144 w/ reduced blanking, generated by cvt12, https://aur.archlinux.org/packages/cvt12-git/

Online

#20 2018-11-25 16:03:38

koreankiwitea
Member
Registered: 2018-02-12
Posts: 48

Re: [Solved] difficculty in setting up 144hz monitor.

seth wrote:

That's more like it ;-)
And yes, looks legit, but we'll still have to remain below 600MHz and that's only ever possible w/ reduced blanking.
Try

# 2560x1440 @ 144.000 Hz Reduced Blank (CVT) field rate 144.000 Hz; hsync: 222.192 kHz; pclk: 586.59 MHz
Modeline "2560x1440_144.00_rb2"  586.59  2560 2568 2600 2640  1440 1529 1537 1543 +hsync -vsync

This is 2560x1440@144 w/ reduced blanking, generated by cvt12, https://aur.archlinux.org/packages/cvt12-git/

Thank you for the confirmation! still no luck however. Here's the Xorg log if you're interested. I can see that the mode has been validated, but I'm still not getting the high refresh rate. Can you maybe generate a cvt for 2560x1440@143 like I did for Windows?
Also, just a practical question that came about while working on this, We don't exactly specify what refresh rate the Xorg has to display in 'modeline'. If i'm understanding correctly, the "" value is just a name for the mode. How does it work out what refresh rate it needs to display at?

EDIT: sorry I got the cvt12-git and worked out how to use it. I'll update after testing with 143Hz. Thank you!

ps/ not sure what the 'primary gpu is not used' warning flag is, as far as I can tell it's fine?

[  2733.885] (--) Log file renamed from "/var/log/Xorg.pid-7835.log" to "/var/log/Xorg.0.log"
[  2733.885] 
X.Org X Server 1.20.3
X Protocol Version 11, Revision 0
[  2733.885] Build Operating System: Linux Arch Linux
[  2733.885] Current Operating System: Linux archMachine 4.19.2-arch1-1-ARCH #1 SMP PREEMPT Tue Nov 13 21:16:19 UTC 2018 x86_64
[  2733.885] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=e2b2f91e-cd48-4b11-9f49-79562b2ff885 rw quiet
[  2733.885] Build Date: 25 October 2018  04:42:32PM
[  2733.885]  
[  2733.885] Current version of pixman: 0.34.0
[  2733.885] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[  2733.885] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  2733.885] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Nov 25 17:56:24 2018
[  2733.885] (==) Using config file: "/etc/X11/xorg.conf"
[  2733.885] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  2733.885] (==) ServerLayout "Layout0"
[  2733.885] (**) |-->Screen "Screen0" (0)
[  2733.885] (**) |   |-->Monitor "Monitor0"
[  2733.886] (**) |   |-->Device "Device0"
[  2733.886] (**) |-->Input Device "Keyboard0"
[  2733.886] (**) |-->Input Device "Mouse0"
[  2733.886] (**) Option "Xinerama" "0"
[  2733.886] (==) Automatically adding devices
[  2733.886] (==) Automatically enabling devices
[  2733.886] (==) Automatically adding GPU devices
[  2733.886] (==) Automatically binding GPU devices
[  2733.886] (==) Max clients allowed: 256, resource mask: 0x1fffff
[  2733.886] (WW) The directory "/usr/share/fonts/misc" does not exist.
[  2733.886] 	Entry deleted from font path.
[  2733.886] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[  2733.886] 	Entry deleted from font path.
[  2733.886] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[  2733.886] 	Entry deleted from font path.
[  2733.886] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[  2733.886] 	Entry deleted from font path.
[  2733.886] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[  2733.886] 	Entry deleted from font path.
[  2733.886] (==) FontPath set to:
	/usr/share/fonts/TTF
[  2733.886] (==) ModulePath set to "/usr/lib/xorg/modules"
[  2733.886] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[  2733.886] (WW) Disabling Keyboard0
[  2733.886] (WW) Disabling Mouse0
[  2733.886] (II) Module ABI versions:
[  2733.886] 	X.Org ANSI C Emulation: 0.4
[  2733.886] 	X.Org Video Driver: 24.0
[  2733.886] 	X.Org XInput driver : 24.1
[  2733.886] 	X.Org Server Extension : 10.0
[  2733.886] (++) using VT number 1

[  2733.886] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[  2733.886] (II) xfree86: Adding drm device (/dev/dri/card0)
[  2733.887] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules"
[  2733.887] (**) OutputClass "nvidia" setting /dev/dri/card0 as PrimaryGPU
[  2733.887] (--) PCI:*(1@0:0:0) 10de:1b81:1043:8599 rev 161, Mem @ 0xde000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[  2733.887] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[  2733.887] (II) LoadModule: "glx"
[  2733.887] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  2733.888] (II) Module glx: vendor="X.Org Foundation"
[  2733.888] 	compiled for 1.20.3, module version = 1.0.0
[  2733.888] 	ABI class: X.Org Server Extension, version 10.0
[  2733.888] (II) LoadModule: "nvidia"
[  2733.888] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[  2733.888] (II) Module nvidia: vendor="NVIDIA Corporation"
[  2733.888] 	compiled for 4.0.2, module version = 1.0.0
[  2733.888] 	Module class: X.Org Video Driver
[  2733.888] (II) NVIDIA dlloader X Driver  415.18  Thu Nov 15 21:40:36 CST 2018
[  2733.888] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[  2733.890] (II) Loading sub module "fb"
[  2733.890] (II) LoadModule: "fb"
[  2733.890] (II) Loading /usr/lib/xorg/modules/libfb.so
[  2733.890] (II) Module fb: vendor="X.Org Foundation"
[  2733.890] 	compiled for 1.20.3, module version = 1.0.0
[  2733.890] 	ABI class: X.Org ANSI C Emulation, version 0.4
[  2733.890] (II) Loading sub module "wfb"
[  2733.890] (II) LoadModule: "wfb"
[  2733.890] (II) Loading /usr/lib/xorg/modules/libwfb.so
[  2733.890] (II) Module wfb: vendor="X.Org Foundation"
[  2733.890] 	compiled for 1.20.3, module version = 1.0.0
[  2733.890] 	ABI class: X.Org ANSI C Emulation, version 0.4
[  2733.890] (II) Loading sub module "ramdac"
[  2733.890] (II) LoadModule: "ramdac"
[  2733.890] (II) Module "ramdac" already built-in
[  2733.890] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[  2733.890] (==) NVIDIA(0): RGB weight 888
[  2733.890] (==) NVIDIA(0): Default visual is TrueColor
[  2733.890] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[  2733.891] (II) Applying OutputClass "nvidia" options to /dev/dri/card0
[  2733.891] (**) NVIDIA(0): Option "Stereo" "0"
[  2733.891] (**) NVIDIA(0): Option "UseEdidFreqs" "FALSE"
[  2733.891] (**) NVIDIA(0): Option "nvidiaXineramaInfoOrder" "DFP-3"
[  2733.891] (**) NVIDIA(0): Option "SLI" "Off"
[  2733.891] (**) NVIDIA(0): Option "MultiGPU" "Off"
[  2733.891] (**) NVIDIA(0): Option "ModeValidation" "AllowNonEdidModes, NoEdidMaxPClkCheck, NoMaxPClkCheck"
[  2733.891] (**) NVIDIA(0): Option "BaseMosaic" "off"
[  2733.891] (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration"
[  2733.891] (**) NVIDIA(0): Stereo disabled by request
[  2733.891] (**) NVIDIA(0): NVIDIA SLI disabled.
[  2733.891] (**) NVIDIA(0): NVIDIA Multi-GPU disabled.
[  2733.891] (**) NVIDIA(0): Enabling 2D acceleration
[  2733.891] (II) Loading sub module "glxserver_nvidia"
[  2733.891] (II) LoadModule: "glxserver_nvidia"
[  2733.891] (II) Loading /usr/lib/nvidia/xorg/libglxserver_nvidia.so
[  2733.894] (II) Module glxserver_nvidia: vendor="NVIDIA Corporation"
[  2733.894] 	compiled for 4.0.2, module version = 1.0.0
[  2733.894] 	Module class: X.Org Server Extension
[  2733.894] (II) NVIDIA GLX Module  415.18  Thu Nov 15 21:39:03 CST 2018
[  2734.196] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0
[  2734.196] (--) NVIDIA(0):     DFP-0
[  2734.196] (--) NVIDIA(0):     DFP-1
[  2734.196] (--) NVIDIA(0):     DFP-2
[  2734.196] (--) NVIDIA(0):     DFP-3 (boot)
[  2734.196] (--) NVIDIA(0):     DFP-4
[  2734.196] (--) NVIDIA(0):     DFP-5
[  2734.196] (--) NVIDIA(0):     DFP-6
[  2734.197] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 1070 (GP104-A) at PCI:1:0:0 (GPU-0)
[  2734.197] (--) NVIDIA(0): Memory: 8388608 kBytes
[  2734.197] (--) NVIDIA(0): VideoBIOS: 86.04.1e.00.21
[  2734.197] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[  2734.197] (--) NVIDIA(GPU-0): DFP-0: disconnected
[  2734.197] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[  2734.197] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[  2734.197] (--) NVIDIA(GPU-0): 
[  2734.198] (--) NVIDIA(GPU-0): DFP-1: disconnected
[  2734.198] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[  2734.198] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[  2734.198] (--) NVIDIA(GPU-0): 
[  2734.198] (--) NVIDIA(GPU-0): DFP-2: disconnected
[  2734.198] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[  2734.198] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[  2734.198] (--) NVIDIA(GPU-0): 
[  2734.198] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): connected
[  2734.198] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): Internal DisplayPort
[  2734.198] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): 1440.0 MHz maximum pixel clock
[  2734.198] (--) NVIDIA(GPU-0): 
[  2734.201] (--) NVIDIA(GPU-0): DFP-4: disconnected
[  2734.201] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[  2734.201] (--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
[  2734.201] (--) NVIDIA(GPU-0): 
[  2734.201] (--) NVIDIA(GPU-0): DFP-5: disconnected
[  2734.201] (--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort
[  2734.201] (--) NVIDIA(GPU-0): DFP-5: 1440.0 MHz maximum pixel clock
[  2734.201] (--) NVIDIA(GPU-0): 
[  2734.202] (--) NVIDIA(GPU-0): DFP-6: disconnected
[  2734.202] (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
[  2734.202] (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[  2734.202] (--) NVIDIA(GPU-0): 
[  2734.202] (**) NVIDIA(GPU-0): Mode Validation Overrides for BenQ EX3203R (DFP-3):
[  2734.202] (**) NVIDIA(GPU-0):     NoMaxPClkCheck
[  2734.202] (**) NVIDIA(GPU-0):     NoEdidMaxPClkCheck
[  2734.202] (**) NVIDIA(GPU-0):     AllowNonEdidModes
[  2734.224] (II) NVIDIA(0): Validated MetaModes:
[  2734.224] (II) NVIDIA(0):     "DFP-3:2560x1440_144.00_rb2"
[  2734.224] (II) NVIDIA(0): Virtual screen size determined to be 2560 x 1440
[  2734.252] (--) NVIDIA(0): DPI set to (92, 93); computed from "UseEdidDpi" X config
[  2734.252] (--) NVIDIA(0):     option
[  2734.253] (II) NVIDIA: Using 24576.00 MB of virtual memory for indirect memory
[  2734.253] (II) NVIDIA:     access.
[  2734.255] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[  2734.255] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[  2734.255] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[  2734.255] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[  2734.255] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[  2734.255] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[  2734.255] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[  2734.255] (II) NVIDIA(0):     Config Options in the README.
[  2734.267] (II) NVIDIA(0): Setting mode "DFP-3:2560x1440_144.00_rb2"
[  2734.394] (==) NVIDIA(0): Disabling shared memory pixmaps
[  2734.394] (==) NVIDIA(0): Backing store enabled
[  2734.394] (==) NVIDIA(0): Silken mouse disabled
[  2734.394] (**) NVIDIA(0): DPMS enabled
[  2734.394] (WW) NVIDIA(0): Option "PrimaryGPU" is not used
[  2734.394] (II) Loading sub module "dri2"
[  2734.394] (II) LoadModule: "dri2"
[  2734.394] (II) Module "dri2" already built-in
[  2734.394] (II) NVIDIA(0): [DRI2] Setup complete
[  2734.394] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[  2734.395] (II) Initializing extension Generic Event Extension
[  2734.395] (II) Initializing extension SHAPE
[  2734.395] (II) Initializing extension MIT-SHM
[  2734.395] (II) Initializing extension XInputExtension
[  2734.395] (II) Initializing extension XTEST
[  2734.395] (II) Initializing extension BIG-REQUESTS
[  2734.395] (II) Initializing extension SYNC
[  2734.395] (II) Initializing extension XKEYBOARD
[  2734.395] (II) Initializing extension XC-MISC
[  2734.395] (II) Initializing extension SECURITY
[  2734.395] (II) Initializing extension XFIXES
[  2734.395] (II) Initializing extension RENDER
[  2734.395] (II) Initializing extension RANDR
[  2734.395] (II) Initializing extension COMPOSITE
[  2734.395] (II) Initializing extension DAMAGE
[  2734.396] (II) Initializing extension MIT-SCREEN-SAVER
[  2734.396] (II) Initializing extension DOUBLE-BUFFER
[  2734.396] (II) Initializing extension RECORD
[  2734.396] (II) Initializing extension DPMS
[  2734.396] (II) Initializing extension Present
[  2734.396] (II) Initializing extension DRI3
[  2734.396] (II) Initializing extension X-Resource
[  2734.396] (II) Initializing extension XVideo
[  2734.396] (II) Initializing extension XVideo-MotionCompensation
[  2734.396] (II) Initializing extension GLX
[  2734.396] (II) Initializing extension GLX
[  2734.396] (II) Indirect GLX disabled.
[  2734.396] (II) GLX: Another vendor is already registered for screen 0
[  2734.396] (II) Initializing extension XFree86-VidModeExtension
[  2734.396] (II) Initializing extension XFree86-DGA
[  2734.396] (II) Initializing extension XFree86-DRI
[  2734.396] (II) Initializing extension DRI2
[  2734.396] (II) Initializing extension NV-GLX
[  2734.396] (II) Initializing extension NV-CONTROL
[  2734.396] (II) Initializing extension XINERAMA
[  2734.417] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[  2734.417] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[  2734.417] (II) LoadModule: "libinput"
[  2734.417] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[  2734.418] (II) Module libinput: vendor="X.Org Foundation"
[  2734.418] 	compiled for 1.20.1, module version = 0.28.1
[  2734.418] 	Module class: X.Org XInput Driver
[  2734.418] 	ABI class: X.Org XInput driver, version 24.1
[  2734.418] (II) Using input driver 'libinput' for 'Power Button'
[  2734.418] (**) Power Button: always reports core events
[  2734.418] (**) Option "Device" "/dev/input/event2"
[  2734.418] (**) Option "_source" "server/udev"
[  2734.419] (II) event2  - Power Button: is tagged by udev as: Keyboard
[  2734.419] (II) event2  - Power Button: device is a keyboard
[  2734.419] (II) event2  - Power Button: device removed
[  2734.444] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[  2734.444] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[  2734.444] (II) event2  - Power Button: is tagged by udev as: Keyboard
[  2734.444] (II) event2  - Power Button: device is a keyboard
[  2734.444] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[  2734.444] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[  2734.444] (II) Using input driver 'libinput' for 'Power Button'
[  2734.444] (**) Power Button: always reports core events
[  2734.444] (**) Option "Device" "/dev/input/event1"
[  2734.444] (**) Option "_source" "server/udev"
[  2734.444] (II) event1  - Power Button: is tagged by udev as: Keyboard
[  2734.444] (II) event1  - Power Button: device is a keyboard
[  2734.444] (II) event1  - Power Button: device removed
[  2734.467] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
[  2734.467] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[  2734.467] (II) event1  - Power Button: is tagged by udev as: Keyboard
[  2734.467] (II) event1  - Power Button: device is a keyboard
[  2734.467] (II) config/udev: Adding input device Sleep Button (/dev/input/event0)
[  2734.468] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[  2734.468] (II) Using input driver 'libinput' for 'Sleep Button'
[  2734.468] (**) Sleep Button: always reports core events
[  2734.468] (**) Option "Device" "/dev/input/event0"
[  2734.468] (**) Option "_source" "server/udev"
[  2734.468] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[  2734.468] (II) event0  - Sleep Button: device is a keyboard
[  2734.468] (II) event0  - Sleep Button: device removed
[  2734.497] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0/event0"
[  2734.497] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[  2734.498] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[  2734.498] (II) event0  - Sleep Button: device is a keyboard
[  2734.499] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event21)
[  2734.499] (II) No input driver specified, ignoring this device.
[  2734.499] (II) This device may have been added with another device file.
[  2734.499] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event22)
[  2734.499] (II) No input driver specified, ignoring this device.
[  2734.499] (II) This device may have been added with another device file.
[  2734.500] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event23)
[  2734.500] (II) No input driver specified, ignoring this device.
[  2734.500] (II) This device may have been added with another device file.
[  2734.500] (II) config/udev: Add[  2733.885] (--) Log file renamed from "/var/log/Xorg.pid-7835.log" to "/var/log/Xorg.0.log"
[  2733.885] 
X.Org X Server 1.20.3
X Protocol Version 11, Revision 0
[  2733.885] Build Operating System: Linux Arch Linux
[  2733.885] Current Operating System: Linux archMachine 4.19.2-arch1-1-ARCH #1 SMP PREEMPT Tue Nov 13 21:16:19 UTC 2018 x86_64
[  2733.885] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=e2b2f91e-cd48-4b11-9f49-79562b2ff885 rw quiet
[  2733.885] Build Date: 25 October 2018  04:42:32PM
[  2733.885]  
[  2733.885] Current version of pixman: 0.34.0
[  2733.885] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[  2733.885] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  2733.885] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Nov 25 17:56:24 2018
[  2733.885] (==) Using config file: "/etc/X11/xorg.conf"
[  2733.885] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  2733.885] (==) ServerLayout "Layout0"
[  2733.885] (**) |-->Screen "Screen0" (0)
[  2733.885] (**) |   |-->Monitor "Monitor0"
[  2733.886] (**) |   |-->Device "Device0"
[  2733.886] (**) |-->Input Device "Keyboard0"
[  2733.886] (**) |-->Input Device "Mouse0"
[  2733.886] (**) Option "Xinerama" "0"
[  2733.886] (==) Automatically adding devices
[  2733.886] (==) Automatically enabling devices
[  2733.886] (==) Automatically adding GPU devices
[  2733.886] (==) Automatically binding GPU devices
[  2733.886] (==) Max clients allowed: 256, resource mask: 0x1fffff
[  2733.886] (WW) The directory "/usr/share/fonts/misc" does not exist.
[  2733.886] 	Entry deleted from font path.
[  2733.886] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[  2733.886] 	Entry deleted from font path.
[  2733.886] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[  2733.886] 	Entry deleted from font path.
[  2733.886] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[  2733.886] 	Entry deleted from font path.
[  2733.886] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[  2733.886] 	Entry deleted from font path.
[  2733.886] (==) FontPath set to:
	/usr/share/fonts/TTF
[  2733.886] (==) ModulePath set to "/usr/lib/xorg/modules"
[  2733.886] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[  2733.886] (WW) Disabling Keyboard0
[  2733.886] (WW) Disabling Mouse0
[  2733.886] (II) Module ABI versions:
[  2733.886] 	X.Org ANSI C Emulation: 0.4
[  2733.886] 	X.Org Video Driver: 24.0
[  2733.886] 	X.Org XInput driver : 24.1
[  2733.886] 	X.Org Server Extension : 10.0
[  2733.886] (++) using VT number 1

[  2733.886] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[  2733.886] (II) xfree86: Adding drm device (/dev/dri/card0)
[  2733.887] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules"
[  2733.887] (**) OutputClass "nvidia" setting /dev/dri/card0 as PrimaryGPU
[  2733.887] (--) PCI:*(1@0:0:0) 10de:1b81:1043:8599 rev 161, Mem @ 0xde000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[  2733.887] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[  2733.887] (II) LoadModule: "glx"
[  2733.887] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  2733.888] (II) Module glx: vendor="X.Org Foundation"
[  2733.888] 	compiled for 1.20.3, module version = 1.0.0
[  2733.888] 	ABI class: X.Org Server Extension, version 10.0
[  2733.888] (II) LoadModule: "nvidia"
[  2733.888] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[  2733.888] (II) Module nvidia: vendor="NVIDIA Corporation"
[  2733.888] 	compiled for 4.0.2, module version = 1.0.0
[  2733.888] 	Module class: X.Org Video Driver
[  2733.888] (II) NVIDIA dlloader X Driver  415.18  Thu Nov 15 21:40:36 CST 2018
[  2733.888] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[  2733.890] (II) Loading sub module "fb"
[  2733.890] (II) LoadModule: "fb"
[  2733.890] (II) Loading /usr/lib/xorg/modules/libfb.so
[  2733.890] (II) Module fb: vendor="X.Org Foundation"
[  2733.890] 	compiled for 1.20.3, module version = 1.0.0
[  2733.890] 	ABI class: X.Org ANSI C Emulation, version 0.4
[  2733.890] (II) Loading sub module "wfb"
[  2733.890] (II) LoadModule: "wfb"
[  2733.890] (II) Loading /usr/lib/xorg/modules/libwfb.so
[  2733.890] (II) Module wfb: vendor="X.Org Foundation"
[  2733.890] 	compiled for 1.20.3, module version = 1.0.0
[  2733.890] 	ABI class: X.Org ANSI C Emulation, version 0.4
[  2733.890] (II) Loading sub module "ramdac"
[  2733.890] (II) LoadModule: "ramdac"
[  2733.890] (II) Module "ramdac" already built-in
[  2733.890] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[  2733.890] (==) NVIDIA(0): RGB weight 888
[  2733.890] (==) NVIDIA(0): Default visual is TrueColor
[  2733.890] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[  2733.891] (II) Applying OutputClass "nvidia" options to /dev/dri/card0
[  2733.891] (**) NVIDIA(0): Option "Stereo" "0"
[  2733.891] (**) NVIDIA(0): Option "UseEdidFreqs" "FALSE"
[  2733.891] (**) NVIDIA(0): Option "nvidiaXineramaInfoOrder" "DFP-3"
[  2733.891] (**) NVIDIA(0): Option "SLI" "Off"
[  2733.891] (**) NVIDIA(0): Option "MultiGPU" "Off"
[  2733.891] (**) NVIDIA(0): Option "ModeValidation" "AllowNonEdidModes, NoEdidMaxPClkCheck, NoMaxPClkCheck"
[  2733.891] (**) NVIDIA(0): Option "BaseMosaic" "off"
[  2733.891] (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration"
[  2733.891] (**) NVIDIA(0): Stereo disabled by request
[  2733.891] (**) NVIDIA(0): NVIDIA SLI disabled.
[  2733.891] (**) NVIDIA(0): NVIDIA Multi-GPU disabled.
[  2733.891] (**) NVIDIA(0): Enabling 2D acceleration
[  2733.891] (II) Loading sub module "glxserver_nvidia"
[  2733.891] (II) LoadModule: "glxserver_nvidia"
[  2733.891] (II) Loading /usr/lib/nvidia/xorg/libglxserver_nvidia.so
[  2733.894] (II) Module glxserver_nvidia: vendor="NVIDIA Corporation"
[  2733.894] 	compiled for 4.0.2, module version = 1.0.0
[  2733.894] 	Module class: X.Org Server Extension
[  2733.894] (II) NVIDIA GLX Module  415.18  Thu Nov 15 21:39:03 CST 2018
[  2734.196] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0
[  2734.196] (--) NVIDIA(0):     DFP-0
[  2734.196] (--) NVIDIA(0):     DFP-1
[  2734.196] (--) NVIDIA(0):     DFP-2
[  2734.196] (--) NVIDIA(0):     DFP-3 (boot)
[  2734.196] (--) NVIDIA(0):     DFP-4
[  2734.196] (--) NVIDIA(0):     DFP-5
[  2734.196] (--) NVIDIA(0):     DFP-6
[  2734.197] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 1070 (GP104-A) at PCI:1:0:0 (GPU-0)
[  2734.197] (--) NVIDIA(0): Memory: 8388608 kBytes
[  2734.197] (--) NVIDIA(0): VideoBIOS: 86.04.1e.00.21
[  2734.197] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[  2734.197] (--) NVIDIA(GPU-0): DFP-0: disconnected
[  2734.197] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[  2734.197] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[  2734.197] (--) NVIDIA(GPU-0): 
[  2734.198] (--) NVIDIA(GPU-0): DFP-1: disconnected
[  2734.198] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[  2734.198] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[  2734.198] (--) NVIDIA(GPU-0): 
[  2734.198] (--) NVIDIA(GPU-0): DFP-2: disconnected
[  2734.198] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[  2734.198] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[  2734.198] (--) NVIDIA(GPU-0): 
[  2734.198] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): connected
[  2734.198] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): Internal DisplayPort
[  2734.198] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): 1440.0 MHz maximum pixel clock
[  2734.198] (--) NVIDIA(GPU-0): 
[  2734.201] (--) NVIDIA(GPU-0): DFP-4: disconnected
[  2734.201] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[  2734.201] (--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
[  2734.201] (--) NVIDIA(GPU-0): 
[  2734.201] (--) NVIDIA(GPU-0): DFP-5: disconnected
[  2734.201] (--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort
[  2734.201] (--) NVIDIA(GPU-0): DFP-5: 1440.0 MHz maximum pixel clock
[  2734.201] (--) NVIDIA(GPU-0): 
[  2734.202] (--) NVIDIA(GPU-0): DFP-6: disconnected
[  2734.202] (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
[  2734.202] (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[  2734.202] (--) NVIDIA(GPU-0): 
[  2734.202] (**) NVIDIA(GPU-0): Mode Validation Overrides for BenQ EX3203R (DFP-3):
[  2734.202] (**) NVIDIA(GPU-0):     NoMaxPClkCheck
[  2734.202] (**) NVIDIA(GPU-0):     NoEdidMaxPClkCheck
[  2734.202] (**) NVIDIA(GPU-0):     AllowNonEdidModes
[  2734.224] (II) NVIDIA(0): Validated MetaModes:
[  2734.224] (II) NVIDIA(0):     "DFP-3:2560x1440_144.00_rb2"
[  2734.224] (II) NVIDIA(0): Virtual screen size determined to be 2560 x 1440
[  2734.252] (--) NVIDIA(0): DPI set to (92, 93); computed from "UseEdidDpi" X config
[  2734.252] (--) NVIDIA(0):     option
[  2734.253] (II) NVIDIA: Using 24576.00 MB of virtual memory for indirect memory
[  2734.253] (II) NVIDIA:     access.
[  2734.255] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[  2734.255] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[  2734.255] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[  2734.255] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[  2734.255] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[  2734.255] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[  2734.255] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[  2734.255] (II) NVIDIA(0):     Config Options in the README.
[  2734.267] (II) NVIDIA(0): Setting mode "DFP-3:2560x1440_144.00_rb2"
[  2734.394] (==) NVIDIA(0): Disabling shared memory pixmaps
[  2734.394] (==) NVIDIA(0): Backing store enabled
[  2734.394] (==) NVIDIA(0): Silken mouse disabled
[  2734.394] (**) NVIDIA(0): DPMS enabled
[  2734.394] (WW) NVIDIA(0): Option "PrimaryGPU" is not used
[  2734.394] (II) Loading sub module "dri2"
[  2734.394] (II) LoadModule: "dri2"
[  2734.394] (II) Module "dri2" already built-in
[  2734.394] (II) NVIDIA(0): [DRI2] Setup complete
[  2734.394] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[  2734.395] (II) Initializing extension Generic Event Extension
[  2734.395] (II) Initializing extension SHAPE
[  2734.395] (II) Initializing extension MIT-SHM
[  2734.395] (II) Initializing extension XInputExtension
[  2734.395] (II) Initializing extension XTEST
[  2734.395] (II) Initializing extension BIG-REQUESTS
[  2734.395] (II) Initializing extension SYNC
[  2734.395] (II) Initializing extension XKEYBOARD
[  2734.395] (II) Initializing extension XC-MISC
[  2734.395] (II) Initializing extension SECURITY
[  2734.395] (II) Initializing extension XFIXES
[  2734.395] (II) Initializing extension RENDER
[  2734.395] (II) Initializing extension RANDR
[  2734.395] (II) Initializing extension COMPOSITE
[  2734.395] (II) Initializing extension DAMAGE
[  2734.396] (II) Initializing extension MIT-SCREEN-SAVER
[  2734.396] (II) Initializing extension DOUBLE-BUFFER
[  2734.396] (II) Initializing extension RECORD
[  2734.396] (II) Initializing extension DPMS
[  2734.396] (II) Initializing extension Present
[  2734.396] (II) Initializing extension DRI3
[  2734.396] (II) Initializing extension X-Resource
[  2734.396] (II) Initializing extension XVideo
[  2734.396] (II) Initializing extension XVideo-MotionCompensation
[  2734.396] (II) Initializing extension GLX
[  2734.396] (II) Initializing extension GLX
[  2734.396] (II) Indirect GLX disabled.
[  2734.396] (II) GLX: Another vendor is already registered for screen 0
[  2734.396] (II) Initializing extension XFree86-VidModeExtension
[  2734.396] (II) Initializing extension XFree86-DGA
[  2734.396] (II) Initializing extension XFree86-DRI
[  2734.396] (II) Initializing extension DRI2
[  2734.396] (II) Initializing extension NV-GLX
[  2734.396] (II) Initializing extension NV-CONTROL
[  2734.396] (II) Initializing extension XINERAMA
[  2734.417] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[  2734.417] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[  2734.417] (II) LoadModule: "libinput"
[  2734.417] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[  2734.418] (II) Module libinput: vendor="X.Org Foundation"
[  2734.418] 	compiled for 1.20.1, module version = 0.28.1
[  2734.418] 	Module class: X.Org XInput Driver
[  2734.418] 	ABI class: X.Org XInput driver, version 24.1
[  2734.418] (II) Using input driver 'libinput' for 'Power Button'
[  2734.418] (**) Power Button: always reports core events
[  2734.418] (**) Option "Device" "/dev/input/event2"
[  2734.418] (**) Option "_source" "server/udev"
[  2734.419] (II) event2  - Power Button: is tagged by udev as: Keyboard
[  2734.419] (II) event2  - Power Button: device is a keyboard
[  2734.419] (II) event2  - Power Button: device removed
[  2734.444] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[  2734.444] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[  2734.444] (II) event2  - Power Button: is tagged by udev as: Keyboard
[  2734.444] (II) event2  - Power Button: device is a keyboard
[  2734.444] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[  2734.444] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[  2734.444] (II) Using input driver 'libinput' for 'Power Button'
[  2734.444] (**) Power Button: always reports core events
[  2734.444] (**) Option "Device" "/dev/input/event1"
[  2734.444] (**) Option "_source" "server/udev"
[  2734.444] (II) event1  - Power Button: is tagged by udev as: Keyboard
[  2734.444] (II) event1  - Power Button: device is a keyboard
[  2734.444] (II) event1  - Power Button: device removed
[  2734.467] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
[  2734.467] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[  2734.467] (II) event1  - Power Button: is tagged by udev as: Keyboard
[  2734.467] (II) event1  - Power Button: device is a keyboard
[  2734.467] (II) config/udev: Adding input device Sleep Button (/dev/input/event0)
[  2734.468] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[  2734.468] (II) Using input driver 'libinput' for 'Sleep Button'
[  2734.468] (**) Sleep Button: always reports core events
[  2734.468] (**) Option "Device" "/dev/input/event0"
[  2734.468] (**) Option "_source" "server/udev"
[  2734.468] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[  2734.468] (II) event0  - Sleep Button: device is a keyboard
[  2734.468] (II) event0  - Sleep Button: device removed
[  2734.497] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0/event0"
[  2734.497] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[  2734.498] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[  2734.498] (II) event0  - Sleep Button: device is a keyboard
[  2734.499] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event21)
[  2734.499] (II) No input driver specified, ignoring this device.
[  2734.499] (II) This device may have been added with another device file.
[  2734.499] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event22)
[  2734.499] (II) No input driver specified, ignoring this device.
[  2734.499] (II) This device may have been added with another device file.
[  2734.500] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event23)
[  2734.500] (II) No input driver specified, ignoring this device.
[  2734.500] (II) This device may have been added with another device file.
[  2734.500] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event24)
[  2734.500] (II) No input driver specified, ignoring this device.
[  2734.500] (II) This device may have been added with another device file.
[  2734.501] (II) config/udev: Adding input device ROCCAT ROCCAT Kova (/dev/input/event9)
[  2734.501] (II) No input driver specified, ignoring this device.
[  2734.501] (II) This device may have been added with another device file.
[  2734.503] (II) config/udev: Adding input device ROCCAT ROCCAT Kova Mouse (/dev/input/event7)
[  2734.503] (**) ROCCAT ROCCAT Kova Mouse: Applying InputClass "libinput pointer catchall"
[  2734.503] (II) Using input driver 'libinput' for 'ROCCAT ROCCAT Kova Mouse'
[  2734.503] (**) ROCCAT ROCCAT Kova Mouse: always reports core events
[  2734.503] (**) Option "Device" "/dev/input/event7"
[  2734.503] (**) Option "_source" "server/udev"
[  2734.505] (II) event7  - ROCCAT ROCCAT Kova Mouse: is tagged by udev as: Mouse
[  2734.505] (II) event7  - ROCCAT ROCCAT Kova Mouse: device is a pointer
[  2734.505] (II) event7  - ROCCAT ROCCAT Kova Mouse: device removed
[  2734.563] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:1E7D:2CEF.0004/input/input8/event7"
[  2734.563] (II) XINPUT: Adding extended input device "ROCCAT ROCCAT Kova Mouse" (type: MOUSE, id 9)
[  2734.564] (**) Option "AccelerationScheme" "none"
[  2734.564] (**) ROCCAT ROCCAT Kova Mouse: (accel) selected scheme none/0
[  2734.564] (**) ROCCAT ROCCAT Kova Mouse: (accel) acceleration factor: 2.000
[  2734.564] (**) ROCCAT ROCCAT Kova Mouse: (accel) acceleration threshold: 4
[  2734.566] (II) event7  - ROCCAT ROCCAT Kova Mouse: is tagged by udev as: Mouse
[  2734.566] (II) event7  - ROCCAT ROCCAT Kova Mouse: device is a pointer
[  2734.568] (II) config/udev: Adding input device ROCCAT ROCCAT Kova Mouse (/dev/input/mouse1)
[  2734.568] (II) No input driver specified, ignoring this device.
[  2734.568] (II) This device may have been added with another device file.
[  2734.569] (II) config/udev: Adding input device ROCCAT ROCCAT Kova Consumer Control (/dev/input/event8)
[  2734.569] (**) ROCCAT ROCCAT Kova Consumer Control: Applying InputClass "libinput keyboard catchall"
[  2734.569] (II) Using input driver 'libinput' for 'ROCCAT ROCCAT Kova Consumer Control'
[  2734.570] (**) ROCCAT ROCCAT Kova Consumer Control: always reports core events
[  2734.570] (**) Option "Device" "/dev/input/event8"
[  2734.570] (**) Option "_source" "server/udev"
[  2734.572] (II) event8  - ROCCAT ROCCAT Kova Consumer Control: is tagged by udev as: Keyboard
[  2734.572] (II) event8  - ROCCAT ROCCAT Kova Consumer Control: device is a keyboard
[  2734.572] (II) event8  - ROCCAT ROCCAT Kova Consumer Control: device removed
[  2734.587] (II) libinput: ROCCAT ROCCAT Kova Consumer Control: needs a virtual subdevice
[  2734.587] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:1E7D:2CEF.0004/input/input9/event8"
[  2734.587] (II) XINPUT: Adding extended input device "ROCCAT ROCCAT Kova Consumer Control" (type: MOUSE, id 10)
[  2734.587] (**) Option "AccelerationScheme" "none"
[  2734.587] (**) ROCCAT ROCCAT Kova Consumer Control: (accel) selected scheme none/0
[  2734.587] (**) ROCCAT ROCCAT Kova Consumer Control: (accel) acceleration factor: 2.000
[  2734.587] (**) ROCCAT ROCCAT Kova Consumer Control: (accel) acceleration threshold: 4
[  2734.590] (II) event8  - ROCCAT ROCCAT Kova Consumer Control: is tagged by udev as: Keyboard
[  2734.590] (II) event8  - ROCCAT ROCCAT Kova Consumer Control: device is a keyboard
[  2734.591] (II) config/udev: Adding input device ROCCAT ROCCAT Kova (/dev/input/event10)
[  2734.591] (**) ROCCAT ROCCAT Kova: Applying InputClass "libinput keyboard catchall"
[  2734.591] (II) Using input driver 'libinput' for 'ROCCAT ROCCAT Kova'
[  2734.591] (**) ROCCAT ROCCAT Kova: always reports core events
[  2734.591] (**) Option "Device" "/dev/input/event10"
[  2734.592] (**) Option "_source" "server/udev"
[  2734.594] (II) event10 - ROCCAT ROCCAT Kova: is tagged by udev as: Keyboard
[  2734.594] (II) event10 - ROCCAT ROCCAT Kova: device is a keyboard
[  2734.594] (II) event10 - ROCCAT ROCCAT Kova: device removed
[  2734.657] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:1E7D:2CEF.0005/input/input11/event10"
[  2734.657] (II) XINPUT: Adding extended input device "ROCCAT ROCCAT Kova" (type: KEYBOARD, id 11)
[  2734.660] (II) event10 - ROCCAT ROCCAT Kova: is tagged by udev as: Keyboard
[  2734.660] (II) event10 - ROCCAT ROCCAT Kova: device is a keyboard
[  2734.661] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event3)
[  2734.661] (**) Logitech USB Receiver: Applying InputClass "libinput keyboard catchall"
[  2734.662] (II) Using input driver 'libinput' for 'Logitech USB Receiver'
[  2734.662] (**) Logitech USB Receiver: always reports core events
[  2734.662] (**) Option "Device" "/dev/input/event3"
[  2734.662] (**) Option "_source" "server/udev"
[  2734.664] (II) event3  - Logitech USB Receiver: is tagged by udev as: Keyboard
[  2734.664] (II) event3  - Logitech USB Receiver: device is a keyboard
[  2734.664] (II) event3  - Logitech USB Receiver: device removed
[  2734.697] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:046D:C53D.0001/input/input3/event3"
[  2734.697] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 12)
[  2734.700] (II) event3  - Logitech USB Receiver: is tagged by udev as: Keyboard
[  2734.700] (II) event3  - Logitech USB Receiver: device is a keyboard
[  2734.701] (II) config/udev: Adding input device Logitech USB Receiver Mouse (/dev/input/event4)
[  2734.701] (**) Logitech USB Receiver Mouse: Applying InputClass "libinput pointer catchall"
[  2734.701] (II) Using input driver 'libinput' for 'Logitech USB Receiver Mouse'
[  2734.702] (**) Logitech USB Receiver Mouse: always reports core events
[  2734.702] (**) Option "Device" "/dev/input/event4"
[  2734.702] (**) Option "_source" "server/udev"
[  2734.704] (II) event4  - Logitech USB Receiver Mouse: is tagged by udev as: Mouse
[  2734.704] (II) event4  - Logitech USB Receiver Mouse: device is a pointer
[  2734.704] (II) event4  - Logitech USB Receiver Mouse: device removed
[  2734.763] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C53D.0002/input/input4/event4"
[  2734.763] (II) XINPUT: Adding extended input device "Logitech USB Receiver Mouse" (type: MOUSE, id 13)
[  2734.764] (**) Option "AccelerationScheme" "none"
[  2734.764] (**) Logitech USB Receiver Mouse: (accel) selected scheme none/0
[  2734.764] (**) Logitech USB Receiver Mouse: (accel) acceleration factor: 2.000
[  2734.764] (**) Logitech USB Receiver Mouse: (accel) acceleration threshold: 4
[  2734.766] (II) event4  - Logitech USB Receiver Mouse: is tagged by udev as: Mouse
[  2734.766] (II) event4  - Logitech USB Receiver Mouse: device is a pointer
[  2734.768] (II) config/udev: Adding input device Logitech USB Receiver Mouse (/dev/input/mouse0)
[  2734.768] (II) No input driver specified, ignoring this device.
[  2734.768] (II) This device may have been added with another device file.
[  2734.769] (II) config/udev: Adding input device Logitech USB Receiver Consumer Control (/dev/input/event5)
[  2734.769] (**) Logitech USB Receiver Consumer Control: Applying InputClass "libinput keyboard catchall"
[  2734.769] (II) Using input driver 'libinput' for 'Logitech USB Receiver Consumer Control'
[  2734.770] (**) Logitech USB Receiver Consumer Control: always reports core events
[  2734.770] (**) Option "Device" "/dev/input/event5"
[  2734.770] (**) Option "_source" "server/udev"
[  2734.772] (II) event5  - Logitech USB Receiver Consumer Control: is tagged by udev as: Keyboard
[  2734.772] (II) event5  - Logitech USB Receiver Consumer Control: device is a keyboard
[  2734.772] (II) event5  - Logitech USB Receiver Consumer Control: device removed
[  2734.787] (II) libinput: Logitech USB Receiver Consumer Control: needs a virtual subdevice
[  2734.787] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C53D.0002/input/input5/event5"
[  2734.787] (II) XINPUT: Adding extended input device "Logitech USB Receiver Consumer Control" (type: MOUSE, id 14)
[  2734.787] (**) Option "AccelerationScheme" "none"
[  2734.787] (**) Logitech USB Receiver Consumer Control: (accel) selected scheme none/0
[  2734.787] (**) Logitech USB Receiver Consumer Control: (accel) acceleration factor: 2.000
[  2734.787] (**) Logitech USB Receiver Consumer Control: (accel) acceleration threshold: 4
[  2734.790] (II) event5  - Logitech USB Receiver Consumer Control: is tagged by udev as: Keyboard
[  2734.790] (II) event5  - Logitech USB Receiver Consumer Control: device is a keyboard
[  2734.791] (II) config/udev: Adding input device Logitech USB Receiver System Control (/dev/input/event6)
[  2734.791] (**) Logitech USB Receiver System Control: Applying InputClass "libinput keyboard catchall"
[  2734.791] (II) Using input driver 'libinput' for 'Logitech USB Receiver System Control'
[  2734.791] (**) Logitech USB Receiver System Control: always reports core events
[  2734.791] (**) Option "Device" "/dev/input/event6"
[  2734.792] (**) Option "_source" "server/udev"
[  2734.794] (II) event6  - Logitech USB Receiver System Control: is tagged by udev as: Keyboard
[  2734.794] (II) event6  - Logitech USB Receiver System Control: device is a keyboard
[  2734.794] (II) event6  - Logitech USB Receiver System Control: device removed
[  2734.830] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C53D.0002/input/input6/event6"
[  2734.830] (II) XINPUT: Adding extended input device "Logitech USB Receiver System Control" (type: KEYBOARD, id 15)
[  2734.833] (II) event6  - Logitech USB Receiver System Control: is tagged by udev as: Keyboard
[  2734.833] (II) event6  - Logitech USB Receiver System Control: device is a keyboard
[  2734.834] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event12)
[  2734.834] (II) No input driver specified, ignoring this device.
[  2734.834] (II) This device may have been added with another device file.
[  2734.835] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event13)
[  2734.835] (II) No input driver specified, ignoring this device.
[  2734.835] (II) This device may have been added with another device file.
[  2734.836] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event14)
[  2734.836] (II) No input driver specified, ignoring this device.
[  2734.836] (II) This device may have been added with another device file.
[  2734.836] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event15)
[  2734.836] (II) No input driver specified, ignoring this device.
[  2734.836] (II) This device may have been added with another device file.
[  2734.837] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event16)
[  2734.837] (II) No input driver specified, ignoring this device.
[  2734.837] (II) This device may have been added with another device file.
[  2734.838] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event17)
[  2734.838] (II) No input driver specified, ignoring this device.
[  2734.838] (II) This device may have been added with another device file.
[  2734.839] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event18)
[  2734.839] (II) No input driver specified, ignoring this device.
[  2734.839] (II) This device may have been added with another device file.
[  2734.840] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event19)
[  2734.840] (II) No input driver specified, ignoring this device.
[  2734.840] (II) This device may have been added with another device file.
[  2734.840] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event20)
[  2734.841] (**) Eee PC WMI hotkeys: Applying InputClass "libinput keyboard catchall"
[  2734.841] (II) Using input driver 'libinput' for 'Eee PC WMI hotkeys'
[  2734.841] (**) Eee PC WMI hotkeys: always reports core events
[  2734.841] (**) Option "Device" "/dev/input/event20"
[  2734.841] (**) Option "_source" "server/udev"
[  2734.842] (II) event20 - Eee PC WMI hotkeys: is tagged by udev as: Keyboard
[  2734.842] (II) event20 - Eee PC WMI hotkeys: device is a keyboard
[  2734.842] (II) event20 - Eee PC WMI hotkeys: device removed
[  2734.883] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input21/event20"
[  2734.883] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 16)
[  2734.885] (II) event20 - Eee PC WMI hotkeys: is tagged by udev as: Keyboard
[  2734.885] (II) event20 - Eee PC WMI hotkeys: device is a keyboard
[  2734.886] (II) config/udev: Adding input device PC Speaker (/dev/input/event11)
[  2734.886] (II) No input driver specified, ignoring this device.
[  2734.886] (II) This device may have been added with another device file.
[  2734.895] (**) ROCCAT ROCCAT Kova Consumer Control: Applying InputClass "libinput keyboard catchall"
[  2734.895] (II) Using input driver 'libinput' for 'ROCCAT ROCCAT Kova Consumer Control'
[  2734.895] (**) ROCCAT ROCCAT Kova Consumer Control: always reports core events
[  2734.895] (**) Option "Device" "/dev/input/event8"
[  2734.895] (**) Option "_source" "_driver/libinput"
[  2734.895] (II) libinput: ROCCAT ROCCAT Kova Consumer Control: is a virtual subdevice
[  2734.896] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:1E7D:2CEF.0004/input/input9/event8"
[  2734.896] (II) XINPUT: Adding extended input device "ROCCAT ROCCAT Kova Consumer Control" (type: KEYBOARD, id 17)
[  2734.896] (**) Logitech USB Receiver Consumer Control: Applying InputClass "libinput keyboard catchall"
[  2734.896] (II) Using input driver 'libinput' for 'Logitech USB Receiver Consumer Control'
[  2734.896] (**) Logitech USB Receiver Consumer Control: always reports core events
[  2734.896] (**) Option "Device" "/dev/input/event5"
[  2734.896] (**) Option "_source" "_driver/libinput"
[  2734.896] (II) libinput: Logitech USB Receiver Consumer Control: is a virtual subdevice
[  2734.896] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C53D.0002/input/input5/event5"
[  2734.896] (II) XINPUT: Adding extended input device "Logitech USB Receiver Consumer Control" (type: KEYBOARD, id 18)
[  2734.898] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): connected
[  2734.898] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): Internal DisplayPort
[  2734.898] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): 1440.0 MHz maximum pixel clock
[  2734.898] (--) NVIDIA(GPU-0): 
[  2740.011] (--) NVIDIA(GPU-0): DFP-0: disconnected
[  2740.011] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[  2740.011] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[  2740.011] (--) NVIDIA(GPU-0): 
[  2740.011] (--) NVIDIA(GPU-0): DFP-1: disconnected
[  2740.011] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[  2740.011] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[  2740.011] (--) NVIDIA(GPU-0): 
[  2740.011] (--) NVIDIA(GPU-0): DFP-2: disconnected
[  2740.011] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[  2740.011] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[  2740.011] (--) NVIDIA(GPU-0): 
[  2740.011] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): connected
[  2740.011] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): Internal DisplayPort
[  2740.011] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): 1440.0 MHz maximum pixel clock
[  2740.011] (--) NVIDIA(GPU-0): 
[  2740.020] (--) NVIDIA(GPU-0): DFP-4: disconnected
[  2740.020] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[  2740.020] (--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
[  2740.020] (--) NVIDIA(GPU-0): 
[  2740.020] (--) NVIDIA(GPU-0): DFP-5: disconnected
[  2740.020] (--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort
[  2740.020] (--) NVIDIA(GPU-0): DFP-5: 1440.0 MHz maximum pixel clock
[  2740.020] (--) NVIDIA(GPU-0): 
[  2740.020] (--) NVIDIA(GPU-0): DFP-6: disconnected
[  2740.020] (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
[  2740.020] (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[  2740.020] (--) NVIDIA(GPU-0): 
[  2740.062] (II) NVIDIA(0): Setting mode "DP-0: 2560x1440_144_0 @2560x1440 +0+0 {ViewPortIn=2560x1440, ViewPortOut=2560x1440+0+0}"
[  2740.293] (--) NVIDIA(GPU-0): DFP-0: disconnected
[  2740.293] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[  2740.293] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[  2740.293] (--) NVIDIA(GPU-0): 
[  2740.293] (--) NVIDIA(GPU-0): DFP-1: disconnected
[  2740.293] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[  2740.293] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[  2740.293] (--) NVIDIA(GPU-0): 
[  2740.293] (--) NVIDIA(GPU-0): DFP-2: disconnected
[  2740.293] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[  2740.293] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[  2740.293] (--) NVIDIA(GPU-0): 
[  2740.293] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): connected
[  2740.293] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): Internal DisplayPort
[  2740.293] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): 1440.0 MHz maximum pixel clock
[  2740.293] (--) NVIDIA(GPU-0): 
[  2740.297] (--) NVIDIA(GPU-0): DFP-4: disconnected
[  2740.297] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[  2740.297] (--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
[  2740.297] (--) NVIDIA(GPU-0): 
[  2740.297] (--) NVIDIA(GPU-0): DFP-5: disconnected
[  2740.297] (--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort
[  2740.297] (--) NVIDIA(GPU-0): DFP-5: 1440.0 MHz maximum pixel clock
[  2740.297] (--) NVIDIA(GPU-0): 
[  2740.297] (--) NVIDIA(GPU-0): DFP-6: disconnected
[  2740.297] (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
[  2740.297] (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[  2740.297] (--) NVIDIA(GPU-0): 
[  2747.566] (--) NVIDIA(GPU-0): DFP-0: disconnected
[  2747.566] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[  2747.566] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[  2747.566] (--) NVIDIA(GPU-0): 
[  2747.566] (--) NVIDIA(GPU-0): DFP-1: disconnected
[  2747.566] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[  2747.566] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[  2747.566] (--) NVIDIA(GPU-0): 
[  2747.566] (--) NVIDIA(GPU-0): DFP-2: disconnected
[  2747.566] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[  2747.566] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[  2747.566] (--) NVIDIA(GPU-0): 
[  2747.566] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): connected
[  2747.566] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): Internal DisplayPort
[  2747.566] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): 1440.0 MHz maximum pixel clock
[  2747.566] (--) NVIDIA(GPU-0): 
[  2747.570] (--) NVIDIA(GPU-0): DFP-4: disconnected
[  2747.570] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[  2747.570] (--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
[  2747.570] (--) NVIDIA(GPU-0): 
[  2747.570] (--) NVIDIA(GPU-0): DFP-5: disconnected
[  2747.570] (--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort
[  2747.570] (--) NVIDIA(GPU-0): DFP-5: 1440.0 MHz maximum pixel clock
[  2747.570] (--) NVIDIA(GPU-0): 
[  2747.570] (--) NVIDIA(GPU-0): DFP-6: disconnected
[  2747.570] (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
[  2747.570] (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[  2747.570] (--) NVIDIA(GPU-0): 
ing input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event24)
[  2734.500] (II) No input driver specified, ignoring this device.
[  2734.500] (II) This device may have been added with another device file.
[  2734.501] (II) config/udev: Adding input device ROCCAT ROCCAT Kova (/dev/input/event9)
[  2734.501] (II) No input driver specified, ignoring this device.
[  2734.501] (II) This device may have been added with another device file.
[  2734.503] (II) config/udev: Adding input device ROCCAT ROCCAT Kova Mouse (/dev/input/event7)
[  2734.503] (**) ROCCAT ROCCAT Kova Mouse: Applying InputClass "libinput pointer catchall"
[  2734.503] (II) Using input driver 'libinput' for 'ROCCAT ROCCAT Kova Mouse'
[  2734.503] (**) ROCCAT ROCCAT Kova Mouse: always reports core events
[  2734.503] (**) Option "Device" "/dev/input/event7"
[  2734.503] (**) Option "_source" "server/udev"
[  2734.505] (II) event7  - ROCCAT ROCCAT Kova Mouse: is tagged by udev as: Mouse
[  2734.505] (II) event7  - ROCCAT ROCCAT Kova Mouse: device is a pointer
[  2734.505] (II) event7  - ROCCAT ROCCAT Kova Mouse: device removed
[  2734.563] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:1E7D:2CEF.0004/input/input8/event7"
[  2734.563] (II) XINPUT: Adding extended input device "ROCCAT ROCCAT Kova Mouse" (type: MOUSE, id 9)
[  2734.564] (**) Option "AccelerationScheme" "none"
[  2734.564] (**) ROCCAT ROCCAT Kova Mouse: (accel) selected scheme none/0
[  2734.564] (**) ROCCAT ROCCAT Kova Mouse: (accel) acceleration factor: 2.000
[  2734.564] (**) ROCCAT ROCCAT Kova Mouse: (accel) acceleration threshold: 4
[  2734.566] (II) event7  - ROCCAT ROCCAT Kova Mouse: is tagged by udev as: Mouse
[  2734.566] (II) event7  - ROCCAT ROCCAT Kova Mouse: device is a pointer
[  2734.568] (II) config/udev: Adding input device ROCCAT ROCCAT Kova Mouse (/dev/input/mouse1)
[  2734.568] (II) No input driver specified, ignoring this device.
[  2734.568] (II) This device may have been added with another device file.
[  2734.569] (II) config/udev: Adding input device ROCCAT ROCCAT Kova Consumer Control (/dev/input/event8)
[  2734.569] (**) ROCCAT ROCCAT Kova Consumer Control: Applying InputClass "libinput keyboard catchall"
[  2734.569] (II) Using input driver 'libinput' for 'ROCCAT ROCCAT Kova Consumer Control'
[  2734.570] (**) ROCCAT ROCCAT Kova Consumer Control: always reports core events
[  2734.570] (**) Option "Device" "/dev/input/event8"
[  2734.570] (**) Option "_source" "server/udev"
[  2734.572] (II) event8  - ROCCAT ROCCAT Kova Consumer Control: is tagged by udev as: Keyboard
[  2734.572] (II) event8  - ROCCAT ROCCAT Kova Consumer Control: device is a keyboard
[  2734.572] (II) event8  - ROCCAT ROCCAT Kova Consumer Control: device removed
[  2734.587] (II) libinput: ROCCAT ROCCAT Kova Consumer Control: needs a virtual subdevice
[  2734.587] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:1E7D:2CEF.0004/input/input9/event8"
[  2734.587] (II) XINPUT: Adding extended input device "ROCCAT ROCCAT Kova Consumer Control" (type: MOUSE, id 10)
[  2734.587] (**) Option "AccelerationScheme" "none"
[  2734.587] (**) ROCCAT ROCCAT Kova Consumer Control: (accel) selected scheme none/0
[  2734.587] (**) ROCCAT ROCCAT Kova Consumer Control: (accel) acceleration factor: 2.000
[  2734.587] (**) ROCCAT ROCCAT Kova Consumer Control: (accel) acceleration threshold: 4
[  2734.590] (II) event8  - ROCCAT ROCCAT Kova Consumer Control: is tagged by udev as: Keyboard
[  2734.590] (II) event8  - ROCCAT ROCCAT Kova Consumer Control: device is a keyboard
[  2734.591] (II) config/udev: Adding input device ROCCAT ROCCAT Kova (/dev/input/event10)
[  2734.591] (**) ROCCAT ROCCAT Kova: Applying InputClass "libinput keyboard catchall"
[  2734.591] (II) Using input driver 'libinput' for 'ROCCAT ROCCAT Kova'
[  2734.591] (**) ROCCAT ROCCAT Kova: always reports core events
[  2734.591] (**) Option "Device" "/dev/input/event10"
[  2734.592] (**) Option "_source" "server/udev"
[  2734.594] (II) event10 - ROCCAT ROCCAT Kova: is tagged by udev as: Keyboard
[  2734.594] (II) event10 - ROCCAT ROCCAT Kova: device is a keyboard
[  2734.594] (II) event10 - ROCCAT ROCCAT Kova: device removed
[  2734.657] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:1E7D:2CEF.0005/input/input11/event10"
[  2734.657] (II) XINPUT: Adding extended input device "ROCCAT ROCCAT Kova" (type: KEYBOARD, id 11)
[  2734.660] (II) event10 - ROCCAT ROCCAT Kova: is tagged by udev as: Keyboard
[  2734.660] (II) event10 - ROCCAT ROCCAT Kova: device is a keyboard
[  2734.661] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event3)
[  2734.661] (**) Logitech USB Receiver: Applying InputClass "libinput keyboard catchall"
[  2734.662] (II) Using input driver 'libinput' for 'Logitech USB Receiver'
[  2734.662] (**) Logitech USB Receiver: always reports core events
[  2734.662] (**) Option "Device" "/dev/input/event3"
[  2734.662] (**) Option "_source" "server/udev"
[  2734.664] (II) event3  - Logitech USB Receiver: is tagged by udev as: Keyboard
[  2734.664] (II) event3  - Logitech USB Receiver: device is a keyboard
[  2734.664] (II) event3  - Logitech USB Receiver: device removed
[  2734.697] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:046D:C53D.0001/input/input3/event3"
[  2734.697] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 12)
[  2734.700] (II) event3  - Logitech USB Receiver: is tagged by udev as: Keyboard
[  2734.700] (II) event3  - Logitech USB Receiver: device is a keyboard
[  2734.701] (II) config/udev: Adding input device Logitech USB Receiver Mouse (/dev/input/event4)
[  2734.701] (**) Logitech USB Receiver Mouse: Applying InputClass "libinput pointer catchall"
[  2734.701] (II) Using input driver 'libinput' for 'Logitech USB Receiver Mouse'
[  2734.702] (**) Logitech USB Receiver Mouse: always reports core events
[  2734.702] (**) Option "Device" "/dev/input/event4"
[  2734.702] (**) Option "_source" "server/udev"
[  2734.704] (II) event4  - Logitech USB Receiver Mouse: is tagged by udev as: Mouse
[  2734.704] (II) event4  - Logitech USB Receiver Mouse: device is a pointer
[  2734.704] (II) event4  - Logitech USB Receiver Mouse: device removed
[  2734.763] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C53D.0002/input/input4/event4"
[  2734.763] (II) XINPUT: Adding extended input device "Logitech USB Receiver Mouse" (type: MOUSE, id 13)
[  2734.764] (**) Option "AccelerationScheme" "none"
[  2734.764] (**) Logitech USB Receiver Mouse: (accel) selected scheme none/0
[  2734.764] (**) Logitech USB Receiver Mouse: (accel) acceleration factor: 2.000
[  2734.764] (**) Logitech USB Receiver Mouse: (accel) acceleration threshold: 4
[  2734.766] (II) event4  - Logitech USB Receiver Mouse: is tagged by udev as: Mouse
[  2734.766] (II) event4  - Logitech USB Receiver Mouse: device is a pointer
[  2734.768] (II) config/udev: Adding input device Logitech USB Receiver Mouse (/dev/input/mouse0)
[  2734.768] (II) No input driver specified, ignoring this device.
[  2734.768] (II) This device may have been added with another device file.
[  2734.769] (II) config/udev: Adding input device Logitech USB Receiver Consumer Control (/dev/input/event5)
[  2734.769] (**) Logitech USB Receiver Consumer Control: Applying InputClass "libinput keyboard catchall"
[  2734.769] (II) Using input driver 'libinput' for 'Logitech USB Receiver Consumer Control'
[  2734.770] (**) Logitech USB Receiver Consumer Control: always reports core events
[  2734.770] (**) Option "Device" "/dev/input/event5"
[  2734.770] (**) Option "_source" "server/udev"
[  2734.772] (II) event5  - Logitech USB Receiver Consumer Control: is tagged by udev as: Keyboard
[  2734.772] (II) event5  - Logitech USB Receiver Consumer Control: device is a keyboard
[  2734.772] (II) event5  - Logitech USB Receiver Consumer Control: device removed
[  2734.787] (II) libinput: Logitech USB Receiver Consumer Control: needs a virtual subdevice
[  2734.787] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C53D.0002/input/input5/event5"
[  2734.787] (II) XINPUT: Adding extended input device "Logitech USB Receiver Consumer Control" (type: MOUSE, id 14)
[  2734.787] (**) Option "AccelerationScheme" "none"
[  2734.787] (**) Logitech USB Receiver Consumer Control: (accel) selected scheme none/0
[  2734.787] (**) Logitech USB Receiver Consumer Control: (accel) acceleration factor: 2.000
[  2734.787] (**) Logitech USB Receiver Consumer Control: (accel) acceleration threshold: 4
[  2734.790] (II) event5  - Logitech USB Receiver Consumer Control: is tagged by udev as: Keyboard
[  2734.790] (II) event5  - Logitech USB Receiver Consumer Control: device is a keyboard
[  2734.791] (II) config/udev: Adding input device Logitech USB Receiver System Control (/dev/input/event6)
[  2734.791] (**) Logitech USB Receiver System Control: Applying InputClass "libinput keyboard catchall"
[  2734.791] (II) Using input driver 'libinput' for 'Logitech USB Receiver System Control'
[  2734.791] (**) Logitech USB Receiver System Control: always reports core events
[  2734.791] (**) Option "Device" "/dev/input/event6"
[  2734.792] (**) Option "_source" "server/udev"
[  2734.794] (II) event6  - Logitech USB Receiver System Control: is tagged by udev as: Keyboard
[  2734.794] (II) event6  - Logitech USB Receiver System Control: device is a keyboard
[  2734.794] (II) event6  - Logitech USB Receiver System Control: device removed
[  2734.830] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C53D.0002/input/input6/event6"
[  2734.830] (II) XINPUT: Adding extended input device "Logitech USB Receiver System Control" (type: KEYBOARD, id 15)
[  2734.833] (II) event6  - Logitech USB Receiver System Control: is tagged by udev as: Keyboard
[  2734.833] (II) event6  - Logitech USB Receiver System Control: device is a keyboard
[  2734.834] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event12)
[  2734.834] (II) No input driver specified, ignoring this device.
[  2734.834] (II) This device may have been added with another device file.
[  2734.835] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event13)
[  2734.835] (II) No input driver specified, ignoring this device.
[  2734.835] (II) This device may have been added with another device file.
[  2734.836] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event14)
[  2734.836] (II) No input driver specified, ignoring this device.
[  2734.836] (II) This device may have been added with another device file.
[  2734.836] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event15)
[  2734.836] (II) No input driver specified, ignoring this device.
[  2734.836] (II) This device may have been added with another device file.
[  2734.837] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event16)
[  2734.837] (II) No input driver specified, ignoring this device.
[  2734.837] (II) This device may have been added with another device file.
[  2734.838] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event17)
[  2734.838] (II) No input driver specified, ignoring this device.
[  2734.838] (II) This device may have been added with another device file.
[  2734.839] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event18)
[  2734.839] (II) No input driver specified, ignoring this device.
[  2734.839] (II) This device may have been added with another device file.
[  2734.840] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event19)
[  2734.840] (II) No input driver specified, ignoring this device.
[  2734.840] (II) This device may have been added with another device file.
[  2734.840] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event20)
[  2734.841] (**) Eee PC WMI hotkeys: Applying InputClass "libinput keyboard catchall"
[  2734.841] (II) Using input driver 'libinput' for 'Eee PC WMI hotkeys'
[  2734.841] (**) Eee PC WMI hotkeys: always reports core events
[  2734.841] (**) Option "Device" "/dev/input/event20"
[  2734.841] (**) Option "_source" "server/udev"
[  2734.842] (II) event20 - Eee PC WMI hotkeys: is tagged by udev as: Keyboard
[  2734.842] (II) event20 - Eee PC WMI hotkeys: device is a keyboard
[  2734.842] (II) event20 - Eee PC WMI hotkeys: device removed
[  2734.883] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input21/event20"
[  2734.883] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 16)
[  2734.885] (II) event20 - Eee PC WMI hotkeys: is tagged by udev as: Keyboard
[  2734.885] (II) event20 - Eee PC WMI hotkeys: device is a keyboard
[  2734.886] (II) config/udev: Adding input device PC Speaker (/dev/input/event11)
[  2734.886] (II) No input driver specified, ignoring this device.
[  2734.886] (II) This device may have been added with another device file.
[  2734.895] (**) ROCCAT ROCCAT Kova Consumer Control: Applying InputClass "libinput keyboard catchall"
[  2734.895] (II) Using input driver 'libinput' for 'ROCCAT ROCCAT Kova Consumer Control'
[  2734.895] (**) ROCCAT ROCCAT Kova Consumer Control: always reports core events
[  2734.895] (**) Option "Device" "/dev/input/event8"
[  2734.895] (**) Option "_source" "_driver/libinput"
[  2734.895] (II) libinput: ROCCAT ROCCAT Kova Consumer Control: is a virtual subdevice
[  2734.896] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:1E7D:2CEF.0004/input/input9/event8"
[  2734.896] (II) XINPUT: Adding extended input device "ROCCAT ROCCAT Kova Consumer Control" (type: KEYBOARD, id 17)
[  2734.896] (**) Logitech USB Receiver Consumer Control: Applying InputClass "libinput keyboard catchall"
[  2734.896] (II) Using input driver 'libinput' for 'Logitech USB Receiver Consumer Control'
[  2734.896] (**) Logitech USB Receiver Consumer Control: always reports core events
[  2734.896] (**) Option "Device" "/dev/input/event5"
[  2734.896] (**) Option "_source" "_driver/libinput"
[  2734.896] (II) libinput: Logitech USB Receiver Consumer Control: is a virtual subdevice
[  2734.896] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C53D.0002/input/input5/event5"
[  2734.896] (II) XINPUT: Adding extended input device "Logitech USB Receiver Consumer Control" (type: KEYBOARD, id 18)
[  2734.898] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): connected
[  2734.898] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): Internal DisplayPort
[  2734.898] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): 1440.0 MHz maximum pixel clock
[  2734.898] (--) NVIDIA(GPU-0): 
[  2740.011] (--) NVIDIA(GPU-0): DFP-0: disconnected
[  2740.011] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[  2740.011] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[  2740.011] (--) NVIDIA(GPU-0): 
[  2740.011] (--) NVIDIA(GPU-0): DFP-1: disconnected
[  2740.011] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[  2740.011] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[  2740.011] (--) NVIDIA(GPU-0): 
[  2740.011] (--) NVIDIA(GPU-0): DFP-2: disconnected
[  2740.011] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[  2740.011] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[  2740.011] (--) NVIDIA(GPU-0): 
[  2740.011] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): connected
[  2740.011] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): Internal DisplayPort
[  2740.011] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): 1440.0 MHz maximum pixel clock
[  2740.011] (--) NVIDIA(GPU-0): 
[  2740.020] (--) NVIDIA(GPU-0): DFP-4: disconnected
[  2740.020] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[  2740.020] (--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
[  2740.020] (--) NVIDIA(GPU-0): 
[  2740.020] (--) NVIDIA(GPU-0): DFP-5: disconnected
[  2740.020] (--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort
[  2740.020] (--) NVIDIA(GPU-0): DFP-5: 1440.0 MHz maximum pixel clock
[  2740.020] (--) NVIDIA(GPU-0): 
[  2740.020] (--) NVIDIA(GPU-0): DFP-6: disconnected
[  2740.020] (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
[  2740.020] (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[  2740.020] (--) NVIDIA(GPU-0): 
[  2740.062] (II) NVIDIA(0): Setting mode "DP-0: 2560x1440_144_0 @2560x1440 +0+0 {ViewPortIn=2560x1440, ViewPortOut=2560x1440+0+0}"
[  2740.293] (--) NVIDIA(GPU-0): DFP-0: disconnected
[  2740.293] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[  2740.293] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[  2740.293] (--) NVIDIA(GPU-0): 
[  2740.293] (--) NVIDIA(GPU-0): DFP-1: disconnected
[  2740.293] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[  2740.293] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[  2740.293] (--) NVIDIA(GPU-0): 
[  2740.293] (--) NVIDIA(GPU-0): DFP-2: disconnected
[  2740.293] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[  2740.293] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[  2740.293] (--) NVIDIA(GPU-0): 
[  2740.293] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): connected
[  2740.293] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): Internal DisplayPort
[  2740.293] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): 1440.0 MHz maximum pixel clock
[  2740.293] (--) NVIDIA(GPU-0): 
[  2740.297] (--) NVIDIA(GPU-0): DFP-4: disconnected
[  2740.297] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[  2740.297] (--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
[  2740.297] (--) NVIDIA(GPU-0): 
[  2740.297] (--) NVIDIA(GPU-0): DFP-5: disconnected
[  2740.297] (--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort
[  2740.297] (--) NVIDIA(GPU-0): DFP-5: 1440.0 MHz maximum pixel clock
[  2740.297] (--) NVIDIA(GPU-0): 
[  2740.297] (--) NVIDIA(GPU-0): DFP-6: disconnected
[  2740.297] (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
[  2740.297] (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[  2740.297] (--) NVIDIA(GPU-0): 
[  2747.566] (--) NVIDIA(GPU-0): DFP-0: disconnected
[  2747.566] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[  2747.566] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[  2747.566] (--) NVIDIA(GPU-0): 
[  2747.566] (--) NVIDIA(GPU-0): DFP-1: disconnected
[  2747.566] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[  2747.566] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[  2747.566] (--) NVIDIA(GPU-0): 
[  2747.566] (--) NVIDIA(GPU-0): DFP-2: disconnected
[  2747.566] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[  2747.566] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[  2747.566] (--) NVIDIA(GPU-0): 
[  2747.566] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): connected
[  2747.566] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): Internal DisplayPort
[  2747.566] (--) NVIDIA(GPU-0): BenQ EX3203R (DFP-3): 1440.0 MHz maximum pixel clock
[  2747.566] (--) NVIDIA(GPU-0): 
[  2747.570] (--) NVIDIA(GPU-0): DFP-4: disconnected
[  2747.570] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[  2747.570] (--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
[  2747.570] (--) NVIDIA(GPU-0): 
[  2747.570] (--) NVIDIA(GPU-0): DFP-5: disconnected
[  2747.570] (--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort
[  2747.570] (--) NVIDIA(GPU-0): DFP-5: 1440.0 MHz maximum pixel clock
[  2747.570] (--) NVIDIA(GPU-0): 
[  2747.570] (--) NVIDIA(GPU-0): DFP-6: disconnected
[  2747.570] (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
[  2747.570] (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[  2747.570] (--) NVIDIA(GPU-0): 

Last edited by koreankiwitea (2018-11-25 16:06:41)


very n00b.

Offline

#21 2018-11-25 16:14:33

koreankiwitea
Member
Registered: 2018-02-12
Posts: 48

Re: [Solved] difficculty in setting up 144hz monitor.

seth wrote:

That's more like it ;-)
And yes, looks legit, but we'll still have to remain below 600MHz and that's only ever possible w/ reduced blanking.
Try

# 2560x1440 @ 144.000 Hz Reduced Blank (CVT) field rate 144.000 Hz; hsync: 222.192 kHz; pclk: 586.59 MHz
Modeline "2560x1440_144.00_rb2"  586.59  2560 2568 2600 2640  1440 1529 1537 1543 +hsync -vsync

This is 2560x1440@144 w/ reduced blanking, generated by cvt12, https://aur.archlinux.org/packages/cvt12-git/


OOooooooh my goodness. It works. when i tried:

$cvt12 2560 1440 143 -b
# 2560x1440 @ 143.000 Hz Reduced Blank (CVT) field rate 143.000 Hz; hsync: 220.506 kHz; pclk: 582.14 MHz
Modeline "2560x1440_143.00_rb2"  582.14  2560 2568 2600 2640  1440 1528 1536 1542 +hsync -vsync

and restarted x, I could tell in the SDDM immediately it worked. Log in to KDE, it didn't for some reason. I when to system settings and on KDE it was still on 144hz. More importantly, I now had an option to change that to 143Hz. VOILA. Monitor is also correctly reporting that now i'm inputting 143Hz. WOW.

Thank you so much Seth and all others for helping me get through this! What a wonderful moment, and I definitely learned a lot. Still don't quite understand how modeline works out the refresh rate, though! smile

Solved!


very n00b.

Offline

#22 2018-11-25 16:26:44

seth
Member
Registered: 2012-09-03
Posts: 19,806

Re: [Solved] difficculty in setting up 144hz monitor.

Cool.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

The 143Hz thing, the lacking modeline from the monitor, the double-positive polarity on windows - all that still smells weird, though.

The frequency is btw. implicit, primarily the ratio of dotclock/total amount of pixels (but the other values come to play as well)

Online

#23 2018-11-25 16:39:30

koreankiwitea
Member
Registered: 2018-02-12
Posts: 48

Re: [Solved] difficculty in setting up 144hz monitor.

seth wrote:

Cool.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

The 143Hz thing, the lacking modeline from the monitor, the double-positive polarity on windows - all that still smells weird, though.

The frequency is btw. implicit, primarily the ratio of dotclock/total amount of pixels (but the other values come to play as well)

Of course, marked. Thank you again for the help, I can now not touch Xorg.conf and this will enormously increase my quality of life!

Yes I agree it's a little sketchy, but the support dude insists that monitor is a 'passive' device and that it should be all okay - and that my GPU might be underpowered... hmmm.

Also, wow, I thought frequency is something that I had to 'set'. So When I was doing manual '143hz' on nvidia on Windows, it wasn't me 'setting' a 143hz, but rather nvidia control panel working out similar steps to what i've just gone through to hit close to '143hz'? Fascinating.

Marked as Solved!!


very n00b.

Offline

#24 2020-09-17 11:11:14

solskog
Member
Registered: 2020-09-05
Posts: 255

Re: [Solved] difficculty in setting up 144hz monitor.

sorry, wrong post.

Last edited by solskog (2020-09-17 11:17:07)

Offline

#25 2020-09-17 11:21:24

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 12,526

Re: [Solved] difficculty in setting up 144hz monitor.

Closing, to prevent other accidental bumps.

Offline

Board footer

Powered by FluxBB