Page 1 of 1

nvidia-settings, can't change my screen resolution.

Posted: Mon May 02, 2022 6:29 pm
by pete67
Hi there,

I installed MX_21.1 KDE (Plasma) and made the nvidia-installation offered by the MX-Tools.
The Manual says "For Nvidia cards you can install the package nvidia-settings, which provides you with a
graphics tool which allows you to change the settings as root with the command nvidia-settings command.
So I opened a termial and typed "sudo nvida-setting" because in the graphical program there is no Option to change the Screenresolution! But the terminal gave me this message:

Code: Select all

tuxpete@mxlinux:~
$ sudo nvidia-settings
[sudo] Passwort für tuxpete: 

(nvidia-settings:4381): GLib-GObject-CRITICAL **: 00:01:05.540: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
tuxpete@mxlinux:~
$ 
Can someone help me with this problem?

Thanks in advice.

Regards,
pete 67

Re: nvidia-settings, can't change my screen resolution.

Posted: Mon May 02, 2022 7:53 pm
by Stevo
Are you using a laptop with hybrid graphics?

It's best that you run "Quick System Info" from the menu, and then just paste the information that it put into the clipboard automatically into a reply here. Then we'll have some technical info.

Re: nvidia-settings, can't change my screen resolution.

Posted: Mon May 02, 2022 8:12 pm
by pete67
Additional here my Hardware. I run a Samsung curved Monitor (Samsung C49HG9x)

This one
https://www.samsung.com/de/monitors/gam ... 840-x-1080

It has a resolution of 3840x1080 and runs in landscape format with a refresh rate of 144Hz. But MX only offers me 1024x768 and a refresh rate of 76hz. In Win11 and in Ubuntu 20.04, which I kicked to install MX managed 3840x1080 with a refresh rate of 144Hz.

Code: Select all

[code]
System:
  Kernel: 5.10.0-14-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-amd64 
  root=UUID=<filter> ro quiet 
  nomodeset splash 
  Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
  Distro: MX-21.1_KDE_x64 Wildflower April 9  2022 
  base: Debian GNU/Linux 11 (bullseye) 
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME Z370-P v: Rev X.0x 
  serial: <filter> UEFI: American Megatrends v: 2401 
  date: 07/15/2019 
CPU:
  Info: 6-Core model: Intel Core i5-8600K bits: 64 type: MCP 
  arch: Kaby Lake note: check family: 6 model-id: 9E (158) 
  stepping: A (10) microcode: EC cache: L2: 9 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 
  bogomips: 43200 
  Speed: 1085 MHz min/max: 800/4300 MHz Core speeds (MHz): 
  1: 1085 2: 1549 3: 1075 4: 1617 5: 2212 6: 1253 
  Vulnerabilities: Type: itlb_multihit 
  status: KVM: VMX unsupported 
  Type: l1tf mitigation: PTE Inversion 
  Type: mds mitigation: Clear CPU buffers; SMT disabled 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass mitigation: Speculative Store Bypass 
  disabled via prctl and seccomp 
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and 
  __user pointer sanitization 
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, 
  IBRS_FW, STIBP: disabled, RSB filling 
  Type: srbds mitigation: Microcode 
  Type: tsx_async_abort 
  mitigation: Clear CPU buffers; SMT disabled 
Graphics:
  Device-1: NVIDIA TU116 [GeForce GTX 1660 Ti] vendor: ASUSTeK 
  driver: nvidia v: 510.47.03 bus-ID: 01:00.0 chip-ID: 10de:2182 
  class-ID: 0300 
  Device-2: Logitech Webcam C270 type: USB 
  driver: snd-usb-audio,uvcvideo bus-ID: 5-2.1:4 
  chip-ID: 046d:0825 class-ID: 0102 serial: <filter> 
  Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: 
  loaded: nvidia note: n/a (using device driver) unloaded: fbdev 
  display-ID: :0 screens: 1 
  Screen-1: 0 s-res: 1024x768 s-dpi: 96 
  s-size: 271x203mm (10.7x8.0") s-diag: 339mm (13.3") 
  Monitor-1: default res: 1024x768 hz: 76 
  OpenGL: renderer: llvmpipe (LLVM 12.0.1 256 bits) 
  v: 4.5 Mesa 21.2.5 compat-v: 3.1 direct render: Yes 
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 
  chip-ID: 8086:a2f0 class-ID: 0403 
  Device-2: NVIDIA TU116 High Definition Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus-ID: 01:00.1 
  chip-ID: 10de:1aeb class-ID: 0403 
  Device-3: Logitech Webcam C270 type: USB 
  driver: snd-usb-audio,uvcvideo bus-ID: 5-2.1:4 
  chip-ID: 046d:0825 class-ID: 0102 serial: <filter> 
  Sound Server-1: ALSA v: k5.10.0-14-amd64 running: yes 
  Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel 
  port: d000 bus-ID: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
RAID:
  Hardware-1: Silicon Image SiI 3132 Serial ATA Raid II Controller driver: sata_sil24 v: kernel port: c000 bus-ID: 05:00.0 
  chip-ID: 1095.3132 rev: 01 class-ID: 0104 
Drives:
  Local Storage: total: 3.47 TiB used: 9.76 GiB (0.3%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda maj-min: 8:0 type: USB vendor: Toshiba 
  model: MK3252GSX size: 298.09 GiB block-size: physical: 4096 B 
  logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> 
  rev: 8101 scheme: MBR 
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung 
  model: SSD 860 EVO 1TB size: 931.51 GiB block-size: 
  physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD 
  serial: <filter> rev: 3B6Q scheme: GPT 
  ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung model: HD103UJ 
  size: 931.51 GiB block-size: physical: 512 B logical: 512 B 
  speed: 3.0 Gb/s type: N/A serial: <filter> rev: 1118 
  scheme: GPT 
  ID-4: /dev/sdd maj-min: 8:48 vendor: Samsung model: HD103UJ 
  size: 931.51 GiB block-size: physical: 512 B logical: 512 B 
  speed: 3.0 Gb/s type: N/A serial: <filter> rev: 1118 
  scheme: MBR 
  ID-5: /dev/sdj maj-min: 8:144 type: USB vendor: Western Digital 
  model: WD5000AAKS-22A7B0 size: 465.76 GiB block-size: 
  physical: 512 B logical: 512 B type: N/A serial: <filter> 
  scheme: MBR 
  SMART Message: Unknown USB bridge. Flash drive/Unsupported 
  enclosure? 
Partition:
  ID-1: / raw-size: 36.93 GiB size: 36.05 GiB (97.62%) 
  used: 9.33 GiB (25.9%) fs: ext4 dev: /dev/sdb2 maj-min: 8:18 
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) 
  used: 275 KiB (0.1%) fs: vfat dev: /dev/sdb1 maj-min: 8:17 
  ID-3: /home raw-size: 886.33 GiB size: 871.34 GiB (98.31%) 
  used: 440.1 MiB (0.0%) fs: ext4 dev: /dev/sdb4 maj-min: 8:20 
Swap:
  Kernel: swappiness: 15 (default 60) 
  cache-pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) 
  priority: -2 dev: /dev/sdb3 maj-min: 8:19 
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C 
  Fan Speeds (RPM): N/A 
Repos:
  Packages: note: see --pkg apt: 2463 lib: 1386 flatpak: 0 
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
  1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://deb.debian.org/debian bullseye main contrib non-free
  2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
  1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list 
  1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye main non-free
  2: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye ahs
Info:
  Processes: 275 Uptime: 2m wakeups: 1 Memory: 31.3 GiB 
  used: 1.75 GiB (5.6%) Init: SysVinit v: 2.96 runlevel: 5 
  default: 5 tool: systemctl Compilers: gcc: 10.2.1 alt: 10 
  Shell: Bash v: 5.1.4 
  running-in: quick-system-info-mx inxi: 3.3.06 
Boot Mode: UEFI
[/code]

Re: nvidia-settings, can't change my screen resolution.

Posted: Tue May 03, 2022 3:33 am
by pete67
@Stevo,
Are you using a laptop with hybrid graphics?
No Stevo, I run a Desktop-System.

Kind Regards,
pete67

Re: nvidia-settings, can't change my screen resolution.

Posted: Tue May 03, 2022 8:48 am
by Huckleberry Finn
You have nomodeset in boot parameters. Remove it from "MX Boot Options" - "Kernel Parameters" box , Apply.

Also :

Code: Select all

sudo rm /etc/X11/xorg.conf
Reboot.

P.S. It may say: "no such file or folder" , no harm.

Re: nvidia-settings, can't change my screen resolution.

Posted: Tue May 03, 2022 3:49 pm
by pete67
@Huckleberry Finn, thanx my friend. It worked. Nvidias driver took over command. It has now the proper resolution of 3840x1080 and runs in landscape format with a refresh rate of 144Hz as it should.

The Nvidia setting program offers to save the x-config to /ect/X11/xorg.conf and the preview shows the nvidia-settings. Can I save it?

Re: nvidia-settings, can't change my screen resolution.

Posted: Tue May 03, 2022 3:52 pm
by pete67
Here the actual Systeminfo:

Code: Select all

System:
  Kernel: 5.10.0-14-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-amd64 
  root=UUID=<filter> ro 
  Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
  Distro: MX-21.1_KDE_x64 Wildflower April 9  2022 
  base: Debian GNU/Linux 11 (bullseye) 
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME Z370-P v: Rev X.0x 
  serial: <filter> UEFI: American Megatrends v: 2401 date: 07/15/2019 
CPU:
  Info: 6-Core model: Intel Core i5-8600K bits: 64 type: MCP 
  arch: Kaby Lake note: check family: 6 model-id: 9E (158) 
  stepping: A (10) microcode: EC cache: L2: 9 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 
  bogomips: 43200 
  Speed: 800 MHz min/max: 800/4300 MHz Core speeds (MHz): 1: 800 2: 800 
  3: 800 4: 800 5: 800 6: 800 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported 
  Type: l1tf mitigation: PTE Inversion 
  Type: mds mitigation: Clear CPU buffers; SMT disabled 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, 
  STIBP: disabled, RSB filling 
  Type: srbds mitigation: Microcode 
  Type: tsx_async_abort mitigation: Clear CPU buffers; SMT disabled 
Graphics:
  Device-1: NVIDIA TU116 [GeForce GTX 1660 Ti] vendor: ASUSTeK 
  driver: nvidia v: 510.47.03 bus-ID: 01:00.0 chip-ID: 10de:2182 
  class-ID: 0300 
  Device-2: Logitech Webcam C270 type: USB 
  driver: snd-usb-audio,uvcvideo bus-ID: 5-2.1:4 chip-ID: 046d:0825 
  class-ID: 0102 serial: <filter> 
  Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: 
  loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv 
  display-ID: :0 screens: 1 
  Screen-1: 0 s-res: 3840x1080 s-dpi: 81 s-size: 1204x343mm (47.4x13.5") 
  s-diag: 1252mm (49.3") 
  Monitor-1: DP-2 res: 3840x1080 hz: 144 dpi: 82 
  size: 1196x336mm (47.1x13.2") diag: 1242mm (48.9") 
  OpenGL: renderer: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 
  v: 4.6.0 NVIDIA 510.47.03 direct render: Yes 
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a2f0 
  class-ID: 0403 
  Device-2: NVIDIA TU116 High Definition Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus-ID: 01:00.1 chip-ID: 10de:1aeb 
  class-ID: 0403 
  Device-3: Logitech Webcam C270 type: USB 
  driver: snd-usb-audio,uvcvideo bus-ID: 5-2.1:4 chip-ID: 046d:0825 
  class-ID: 0102 serial: <filter> 
  Sound Server-1: ALSA v: k5.10.0-14-amd64 running: yes 
  Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel port: d000 
  bus-ID: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
RAID:
  Hardware-1: Silicon Image SiI 3132 Serial ATA Raid II Controller 
  driver: sata_sil24 v: kernel port: c000 bus-ID: 05:00.0 
  chip-ID: 1095.3132 rev: 01 class-ID: 0104 
Drives:
  Local Storage: total: 3.47 TiB used: 9.85 GiB (0.3%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB 
  size: 931.51 GiB block-size: physical: 512 B logical: 512 B 
  speed: 6.0 Gb/s type: SSD serial: <filter> rev: 3B6Q scheme: GPT 
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: HD103UJ 
  size: 931.51 GiB block-size: physical: 512 B logical: 512 B 
  speed: 3.0 Gb/s type: N/A serial: <filter> rev: 1118 scheme: GPT 
  ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung model: HD103UJ 
  size: 931.51 GiB block-size: physical: 512 B logical: 512 B 
  speed: 3.0 Gb/s type: N/A serial: <filter> rev: 1118 scheme: MBR 
  ID-4: /dev/sdd maj-min: 8:48 type: USB vendor: Toshiba 
  model: MK3252GSX size: 298.09 GiB block-size: physical: 4096 B 
  logical: 512 B type: N/A serial: <filter> rev: 8101 scheme: MBR 
  ID-5: /dev/sdj maj-min: 8:144 type: USB vendor: Western Digital 
  model: WD5000AAKS-22A7B0 size: 465.76 GiB block-size: physical: 512 B 
  logical: 512 B type: N/A serial: <filter> scheme: MBR 
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
Partition:
  ID-1: / raw-size: 36.93 GiB size: 36.05 GiB (97.62%) 
  used: 9.34 GiB (25.9%) fs: ext4 dev: /dev/sda2 maj-min: 8:2 
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) 
  used: 275 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1 
  ID-3: /home raw-size: 886.33 GiB size: 871.34 GiB (98.31%) 
  used: 524.3 MiB (0.1%) fs: ext4 dev: /dev/sda4 maj-min: 8:4 
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) 
  priority: -2 dev: /dev/sda3 maj-min: 8:3 
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 38 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 29% 
Repos:
  Packages: note: see --pkg apt: 2463 lib: 1386 flatpak: 0 
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
  1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://deb.debian.org/debian bullseye main contrib non-free
  2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
  1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list 
  1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye main non-free
  2: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bullseye ahs
Info:
  Processes: 245 Uptime: 13m wakeups: 1 Memory: 31.3 GiB 
  used: 2.12 GiB (6.8%) Init: SysVinit v: 2.96 runlevel: 5 default: 5 
  tool: systemctl Compilers: gcc: 10.2.1 alt: 10 Shell: bash 
  default: Bash v: 5.1.4 running-in: quick-system-info-mx inxi: 3.3.06 
Boot Mode: UEFI
[/code]

Re: nvidia-settings, can't change my screen resolution.

Posted: Tue May 03, 2022 4:23 pm
by Huckleberry Finn
:number1:
pete67 wrote: Tue May 03, 2022 3:49 pmThe Nvidia setting program offers to save the x-config to /ect/X11/xorg.conf and the preview shows the nvidia-settings. Can I save it?
Yep. The reason we suggest to delete it (as above) is many times (mostly when generated automatically) it causes conflicts (also obsolete) and sometimes causes even black screen when rebooting after Nvidia Driver Installation...

So, just save it, and in case it causes any issues, you can again remove or just rename it to ...conf.old and it'll become passive.

In case you feel it's solved (as the starter of the thread) :

Re: nvidia-settings, can't change my screen resolution.  [Solved]

Posted: Wed May 04, 2022 5:01 am
by pete67
@Huckleberry Finn, ah okay. So I will save it and make a duplicate to save it under xorg.conf.old so that I can jump back.
Anyway I will make a snapshot with that MX-Tool of the entire now proper running system! :happy:

Re: nvidia-settings, can't change my screen resolution.

Posted: Wed May 04, 2022 5:50 am
by Huckleberry Finn
Good idea :)

Just take note: Since you have Nvidia driver installed, when booting with your snapshot iso , you need to add

Code: Select all

xorg=nvidia
in boot parameters.

(Otherwise there'll be just a black screen with a blinking cursor and you'll wonder what happened again :) )

(You know: press E on Grub , type it after ... quiet splash blahblah then press F10 to go on boot )

Re: nvidia-settings, can't change my screen resolution.

Posted: Thu May 05, 2022 9:11 am
by pete67
@Huckleberry Finn
hello my friend. I added "xorg=nvidia" under the boot parameters in my german MX-Boot-Options und "Kernel-Parameter". I hope that's what you mean with "boot parameters".

I wanted to save my In "Nvidia X-Server-Einstellungen" my setting to save and tried it via the button "Save to X Configuration File" where it would save
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 510.47.03

Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "Module"
Load "dbe"
Load "extmod"
Load "type1"
Load "freetype"
Load "glx"
EndSection

Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Samsung C49HG9x"
HorizSync 30.0 - 170.0
VertRefresh 50.0 - 144.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "NVIDIA GeForce GTX 1660 Ti"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "DFP-4"
Option "metamodes" "nvidia-auto-select +0+0"
Option "SLI" "Off"
Option "MultiGPU" "Off"
Option "BaseMosaic" "off"
SubSection "Display"
Depth 24
EndSubSection
EndSection
But when I want to save it a message pops up which says "Unable to open X config file '/etc/S11/xorg.conf' for writing."

I think I must get root-rights first to save that file but I don't know how to get them. Do I have to boot as root that I can save the settings or how can I do that to save the X Configuration file via the graphic too Nvidia Settings with root rights?

Re: nvidia-settings, can't change my screen resolution.

Posted: Thu May 05, 2022 9:21 am
by Huckleberry Finn
pete67 wrote: Thu May 05, 2022 9:11 am... added "xorg=nvidia" under the boot parameters in my german MX-Boot-Options und "Kernel-Parameter"...
No, that one is for the installed system, you don't need it now. That was just, when you create a snapshot iso, then write it on a usb and try to boot with that.. only then type it on welcome screen (press E ) ...

Re: nvidia-settings, can't change my screen resolution.

Posted: Thu May 05, 2022 9:27 am
by Huckleberry Finn
You can do it manually for now, rather than logging in as root :

Code: Select all

sudo -E geany /etc/X11/xorg.conf
Then copy-paste these, save, close, reboot.

Code: Select all

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 510.47.03

Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "Module"
Load "dbe"
Load "extmod"
Load "type1"
Load "freetype"
Load "glx"
EndSection

Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Samsung C49HG9x"
HorizSync 30.0 - 170.0
VertRefresh 50.0 - 144.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "NVIDIA GeForce GTX 1660 Ti"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "DFP-4"
Option "metamodes" "nvidia-auto-select +0+0"
Option "SLI" "Off"
Option "MultiGPU" "Off"
Option "BaseMosaic" "off"
SubSection "Display"
Depth 24
EndSubSection
EndSection
P.S. You can replace geany with your favorite text editor, or whatever is installed , or just sudo nano /etc/X11/xorg.conf )

Re: nvidia-settings, can't change my screen resolution.

Posted: Sat May 07, 2022 9:34 am
by pete67
Hi @Huckleberry Finn , I've done as you wrote but when I want to save the file it says the following:
"/ect/X11/xorg.conf" E212: Datei kann nicht zum Schreiben geöffnet werden" In English "....File cannot be opened for writing"

So I used
sudo nano /etc/X11/xorg.conf
as you suggested put the code in the file saved it and that works. Wonder why vim wasn't able to save it!?

Re: nvidia-settings, can't change my screen resolution.

Posted: Sat May 07, 2022 10:03 am
by Huckleberry Finn
pete67 wrote: Sat May 07, 2022 9:34 am... but when I want to save the file it says the following:
"/ect/X11/xorg.conf" E212: Datei kann nicht zum Schreiben geöffnet werden" In English "....File cannot be opened for writing"...
Cause there's no such directory /ect/... (if it was not just a typo when posting here) :)

Re: nvidia-settings, can't change my screen resolution.

Posted: Sat May 07, 2022 2:38 pm
by Huckleberry Finn
Meanwhile, it's ok on your installed system. But having such a file may cause such an issue: When you take a snapshot and write your iso , then need to boot (your live medium) on another pc which's non-Nvidia, then it may cause black screen / boot problems. Cause this one tells it directly to use nvidia driver for xorg:

Section "Device"
Identifier "Device0"
Driver "nvidia"

... So, it may be good to rename that file to ..old (or move to somewhere or delete) before running MX Snapshot (for your iso be bootable on all machines, no matter Intel, Amd ... )

Re: nvidia-settings, can't change my screen resolution.

Posted: Mon May 09, 2022 4:51 am
by pete67
Hi, @Huckleberry Finn , meanwhile I could save the setting under /etc/X11/xorg.conf and above I can save changes in the file directly out of the graphical program. As the permissions lies by the user root this is a miracle for me, but I works, without mistakes to save this file.

Meanwhile I made a snapshot and let the lines for booting with all kinds of graphic cards uncommented. So I think when I boot it into the live mode it will select the driver for the built-in graphic card or uses the default xorg driver or not? Am I right or is this a false assumption?

Re: nvidia-settings, can't change my screen resolution.

Posted: Mon May 09, 2022 4:59 am
by pete67
@Huckleberry Finn BTW: I used
sudo nano /etc/X11/xorg.conf
and added the coding into it and saved it. Why isn't Vim able to save that file as nano does?

Re: nvidia-settings, can't change my screen resolution.

Posted: Mon May 09, 2022 5:45 am
by Huckleberry Finn
... Shortly, when there's no such file or such lines (like the official iso) , it just selects the required driver automatically according to that machine (hardware) : amdgpu, radeon, nouveau, intel, modesetting etc.

But such a file forces it to use "that" driver . That's why many times it causes black screens or resolution issues or no brightness controls etc. Cause sometimes it is:

Driver "vesa"

or

Driver "fbdev"

and the user is unaware of that, then asks why they can't change resolution, brightness etc.. (Cause the real / appropriate driver is not loaded due to that).

Also, that's why the suggestion is to add on live session xorg=nvidia (which will be temporary; just for that boot)
... cause if you make it permanent (like in your xorg file) then it'll be ok for that pc (you won't even need to type such a thing).. But on another pc it will still try to use Nvidia driver (the wrong one) when that machine has an Amd or Intel card .
_________________________

As for Vim : As above, have you tried with the correct path? (you had a typo as /ect/ )

Re: nvidia-settings, can't change my screen resolution.

Posted: Mon May 09, 2022 6:01 am
by pete67
Well for other people I will create a full live Stick with the MX-Tool "MX Live USB Erzeugung (MX Live USB Generation) and I think this will not have the nvidia driver per default, or do I go wrong again with this suggestion?

On the other hand, in mentioned tool one can refer to a freshly downloaded iso, right?

Re: nvidia-settings, can't change my screen resolution.

Posted: Mon May 09, 2022 6:30 am
by Huckleberry Finn
That one ( "MX Live Usb Maker" ) is just to write an iso to a usb (to prepare a bootable usb stick).

So, you can use either an official iso,
or first create a snapshot of your current system ("your own iso" with "MX Snapshot" ) and choose "Resetting Accounts" at second step:

Re: nvidia-settings, can't change my screen resolution.

Posted: Mon May 09, 2022 7:05 am
by pete67
Well, I used a downloaded and proved iso without the snapshot of my own system so that others can install the clean version of MX on their machines doesn't matter what hardware is installed on their Machines.

As I created a snapshot of my system I can create with that tool a live stick, especially for me and my machine. Will do that in the next few days.

So for that moment this thread can really be marked as solved and can maybe be helpful for others with similar problems. :popcorn: