#1 2025-05-12 06:10:54

WizardofCOR

Member

Registered: 2023-07-28

Posts: 9

arandr alternative?

Greetings, all.

I'm doing an install on a workstation w/2x Dark Matter curved 49" monitors that natively run at 5120x1440, connected to an nVidia RTX4060 via Display Port.
Unfortunately, arandr only detects and labels one out of the two monitors as "default", and the only resolution option is 1024x768.

On my Boron laptop, I see multiple different connection types and potential resolutions - not so on the workstation.

Boron was to replace Mint on said workstation, and Mint had provided auto-detection and orientation configurations - I was hoping for similar out-of-the-box functionality from Boron.
I've searched and checked the other posts here (and elsewhere) offering potential guidance on CLI scripting that should normally allow resolution and configuration alterations, but all CLI change attempts fail on this machine, as it cannot accurately discern monitor labels or connections, even after installing nVidia drivers.

Is there an alternative to arandr for Boron?  Preferably something with a GUI that can auto-detect resolutions and allow manipulative configurations similar to what Mint/Ubuntu uses?
I'm really hoping to use Boron on this workstation.
Thanks for any tips!

---

Just a dude playing a dude, disguised as another dude...

Döbbie03

Resident Metalhead

From: New Zealand

Registered: 2015-09-29

Posts: 3,870

Re: arandr alternative?

What is the output of xrandr in a terminal? Does that pick up the resolution you expect?

---

"All we are is dust in the wind, dude"
                                       - Theodore "Ted" Logan
"Led Zeppelin didn't write tunes that everybody liked, they left that to the Bee Gees."
                                       - Wayne Campbell

WizardofCOR

Member

Registered: 2023-07-28

Posts: 9

Re: arandr alternative?

Hey, thanks for responding Resident Metalhead!

Running xrandr from a terminal, I see the following:

xrandr: Failed to get size of gamma for output default
screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
      1024x768           76.00*

Edited:

I'm starting to think it may have something to do with ACPI errors and nVidia drivers - just a guess.
Seeing these kinds of errors during bootup:

ACPI error aborting method _sb pci0...
ACPI BIOS Error (bug) : Could not resolve symb01 [\_sb.pci0...
and
[Failed] Failed to start nvidia-persistenced.service - NVidia Persistence Daemon

Perhaps ironically, I was just looking at a Mint forum post:
https://forums.linuxmint.com/viewtopic. … b&start=20

where they mentioned manually creating a xorg.conf file.
So I'll hazard a guess that the arandr result may be a symptom of a larger, more fundamental issue between ACPI, UEFI and nVidia drivers on this box.

Lots of potential variables to troubleshoot, wish me luck!

Last edited by WizardofCOR (2025-05-12 07:36:46)

---

Just a dude playing a dude, disguised as another dude...

Head_on_a_Stick

Member

From: London

Registered: 2015-09-29

Posts: 9,093

Website

Re: arandr alternative?

Looks like you're running the VESA drivers, check with

lspci -knn -d ::03xx

I don't support NVIDIA though, sorry.

---

Para todos todo, para nosotros nada

Döbbie03

Resident Metalhead

From: New Zealand

Registered: 2015-09-29

Posts: 3,870

Re: arandr alternative?

Hey, thanks for responding Resident Metalhead!

Running xrandr from a terminal, I see the following:

xrandr: Failed to get size of gamma for output default
screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
      1024x768           76.00*

Edited:

I'm starting to think it may have something to do with ACPI errors and nVidia drivers - just a guess.
Seeing these kinds of errors during bootup:

ACPI error aborting method _sb pci0...
ACPI BIOS Error (bug) : Could not resolve symb01 [\_sb.pci0...
and
[Failed] Failed to start nvidia-persistenced.service - NVidia Persistence Daemon

Perhaps ironically, I was just looking at a Mint forum post:
https://forums.linuxmint.com/viewtopic. … b&start=20

where they mentioned manually creating a xorg.conf file.
So I'll hazard a guess that the arandr result may be a symptom of a larger, more fundamental issue between ACPI, UEFI and nVidia drivers on this box.

Lots of potential variables to troubleshoot, wish me luck!

Good luck indeed.  I too struggle with Nvidia so unfortunately I will be of little help here.

Also check out the Arch Wiki page which may be of assistance.

https://wiki.archlinux.org/title/Xrandr#

---

"All we are is dust in the wind, dude"
                                       - Theodore "Ted" Logan
"Led Zeppelin didn't write tunes that everybody liked, they left that to the Bee Gees."
                                       - Wayne Campbell