Arch Linux

toude

Member

Registered: 2026-01-11

Posts: 2

[SOLVED] Incorrect display settings: name, resolution, missing display

Hello,

This is my first post on these forums and while I have read the rules and guidelines feel free to correct me if I happen to apply them incorrectly.

I run a Windows 11/Arch Linux dual-boot on my machine. Two weeks ago, after rebooting from Windows to Arch I was met with an incorrect interface. I did not update my system the last boot I did on Arch, though I have updated my system since.

To go into more details out of my two monitors only one is now detected, and at 1024x768 instead of 2560x1440. This is also the only resolution now available. What's more `xrandr` now shows the display as `None-1` instead of `DP-1` as was previously the case (both my monitors are identical and plugged in via displayport). Full output below:

Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
None-1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm   1024x768      60.00*+

I have an Nvidia GTX1080 graphics card, onto which my monitors are plugged. I use the legacy `nvidia-580xx` Nvidia drivers as recommended on the wiki. Although I have tried the newer open drivers, which did not solve my issue and changed nothing I noticed regarding it.

I have tried adding a new mode and enabling for my `None-1` display through xrandr as described in this procedure. It failed.
Tried:

xrandr --newmode "2560x1440_60.00"  312.25  2560 2752 3024 3488  1440 1443 1448 1493 -hsync +vsync
xrandr --addmode None-1 "2560x1440_60.00"
xrandr --output None-1 --mode "2560x1440_60.00"

Got:

xrandr: Configure crtc 0 failed

Which just confused me further as I don't know what this is (unless it's cathode tubes but I don't see the link).

I also retrieved the EDID binary for my monitors on my working Windows install with the same hardware and tried to force it as described on the wiki. I failed again, though I only tried setting the EDID after boot. I did not understand how to access the kernel command line yet after all.

I should also mention I'm using the X server and the Qtile WM. My `Xorg.0.log` can be found on this pastebin and the output from `journalctl -b`

If you need anything else feel free to ask ! Good day to you, whenever you may read this

Last edited by toude (Yesterday 14:52:30)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 72,057

Re: [SOLVED] Incorrect display settings: name, resolution, missing display

I use the legacy `nvidia-580xx` Nvidia drivers as recommended

Nope.

You're running on the simpledrm software emulation because you're trying to run a pascal chip w/ nvidia-open

janv. 11 23:53:03 s0lst1ce-desktop kernel: NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:1b80)
                                           NVRM: installed in this system is not supported by open
                                           NVRM: nvidia.ko because it does not include the required GPU
                                           NVRM: System Processor (GSP).
                                           NVRM: Please see the 'Open Linux Kernel Modules' and 'GSP
                                           NVRM: Firmware' sections in the driver README, available on
                                           NVRM: the Linux graphics driver download page at
                                           NVRM: www.nvidia.com.

https://archlinux.org/news/nvidia-590-d … l-modules/

pacman -Qs 'kernel|nvidia'
dkms status

I run a Windows 11/Arch Linux dual-boot on my machine.

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

toude

Member

Registered: 2026-01-11

Posts: 2

Re: [SOLVED] Incorrect display settings: name, resolution, missing display

Hello Seth, thanks for your quick reply.

Thanks for pointing out my mistake regarding the drivers, I seem to have forgotten to revert to the 58xx. Doing this and disabling fast boot did the trick, thanks !