Hello SUSE! I just installed oS for the first time comming from Ubuntu and I love it, up until I installed the Nvidia driver through YasT. I followed the procedure in the documentation but when I rebooted I noticed my desktop environment had been scaled up in size. Icons, windows, test, menus everything is bloated. I went to display settings and it says that it is set to 1920x1080 which is my native res. Upon looking at the systemd journals it seems to suggest that perhaps the noveau driver has taken over my video card (GTX 970). I tried blacklisting noveau but that didn’t help. When I go to my hardware detector in YasT it says that my graphics card is currently using the Nvidia drivers. I am lost on what to do next. Has anyone else had this problem:question:
Okay so opening up the NVIDIA server settings and running an auto-detect of my displays seemed to work. Im using KDE and that just seemed to do the trick. I haven’t a clue why. But if anyone else has this problem try doing that… Thanks anyway!!!
Okay I’m sorry about this. But the problem is back but this time I noticed a pattern. It only happens when I have my smaller display on at boot. And when my smaller display is my primary. Its not that much smaller so it definitely should not be this bloated. Also I noticed that I didn’t really specify what DE I’m using. I am using KDE plasma 5. I’m sorry again for the dragging on of this post but I thought the problem was solved. Has anyone else had this problem with duel different sized monitors? Thanks in advanced!!
Also here is my systemd journal with everything nvidia grepped its a lot of text but I think it seems to point to the noveau driver as the culprit, however I have tried to disable it using the blacklisting technique with no luck.
May 23 14:03:11 linux-wg1g kernel: nouveau 0000:01:00.0: Direct firmware load for nvidia/gm204/fecs_inst.bin failed with error -2
May 23 14:18:47 linux-wg1g kernel: nvidia: loading out-of-tree module taints kernel.
May 23 14:18:47 linux-wg1g kernel: nvidia: module license 'NVIDIA' taints kernel.
May 23 14:18:47 linux-wg1g kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 247
NVRM: nouveau, rivafb, nvidiafb or rivatv
May 23 14:18:47 linux-wg1g kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 247
May 23 14:18:47 linux-wg1g kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 247
NVRM: nouveau, rivafb, nvidiafb or rivatv
May 23 14:18:47 linux-wg1g kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 247
May 23 14:18:48 linux-wg1g kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 247
NVRM: nouveau, rivafb, nvidiafb or rivatv
May 23 14:18:48 linux-wg1g kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 247
May 23 14:18:48 linux-wg1g kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 247
NVRM: nouveau, rivafb, nvidiafb or rivatv
May 23 14:18:48 linux-wg1g kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 247
May 23 14:18:48 linux-wg1g kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 247
NVRM: nouveau, rivafb, nvidiafb or rivatv
May 23 14:18:48 linux-wg1g kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 247
May 23 14:18:48 linux-wg1g kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 247
NVRM: nouveau, rivafb, nvidiafb or rivatv
May 23 14:18:48 linux-wg1g kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 247
May 23 14:19:21 linux-wg1g kernel: nvidia_modeset: loading out-of-tree module taints kernel.
May 23 14:19:21 linux-wg1g kernel: nvidia_modeset: module license 'NVIDIA' taints kernel.
May 23 14:19:21 linux-wg1g kernel: nvidia_modeset: Unknown symbol nvidia_register_module (err 0)
May 23 14:19:21 linux-wg1g kernel: nvidia_modeset: Unknown symbol nvidia_get_rm_ops (err 0)
May 23 14:19:21 linux-wg1g kernel: nvidia_modeset: Unknown symbol nvidia_unregister_module (err 0)
May 23 14:19:33 linux-wg1g kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 247
May 23 14:19:34 linux-wg1g kernel: nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 246
May 23 14:19:34 linux-wg1g kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 375.66 Mon May 1 14:33:30 PDT 2017
May 23 14:19:34 linux-wg1g kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
May 23 14:20:01 linux-wg1g kernel: nvidia-modeset: Allocated GPU:0 (GPU-389601bb-7a1f-6c19-129a-372e76c98315) @ PCI:0000:01:00.0
May 23 14:24:43 linux-wg1g kernel: nvidia-modeset: Freed GPU:0 (GPU-389601bb-7a1f-6c19-129a-372e76c98315) @ PCI:0000:01:00.0
May 23 14:24:45 linux-wg1g kernel: nvidia-modeset: Allocated GPU:0 (GPU-389601bb-7a1f-6c19-129a-372e76c98315) @ PCI:0000:01:00.0
May 23 14:24:47 linux-wg1g kernel: nvidia-modeset: Freed GPU:0 (GPU-389601bb-7a1f-6c19-129a-372e76c98315) @ PCI:0000:01:00.0
May 23 14:25:09 linux-wg1g kernel: nvidia_modeset: loading out-of-tree module taints kernel.
May 23 14:25:09 linux-wg1g kernel: nvidia_modeset: module license 'NVIDIA' taints kernel.
May 23 14:25:09 linux-wg1g kernel: nvidia_modeset: Unknown symbol nvidia_register_module (err 0)
May 23 14:25:09 linux-wg1g kernel: nvidia_modeset: Unknown symbol nvidia_get_rm_ops (err 0)
May 23 14:25:09 linux-wg1g kernel: nvidia_modeset: Unknown symbol nvidia_unregister_module (err 0)
May 23 14:25:21 linux-wg1g kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 247
May 23 14:25:22 linux-wg1g kernel: nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 246
May 23 14:25:22 linux-wg1g kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 375.66 Mon May 1 14:33:30 PDT 2017
May 23 14:25:22 linux-wg1g kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
May 23 14:25:50 linux-wg1g kernel: nvidia-modeset: Allocated GPU:0 (GPU-389601bb-7a1f-6c19-129a-372e76c98315) @ PCI:0000:01:00.0
May 23 14:44:15 linux-wg1g kernel: nvidia-modeset: Freed GPU:0 (GPU-389601bb-7a1f-6c19-129a-372e76c98315) @ PCI:0000:01:00.0
May 23 14:44:17 linux-wg1g kernel: nvidia-modeset: Allocated GPU:0 (GPU-389601bb-7a1f-6c19-129a-372e76c98315) @ PCI:0000:01:00.0
May 23 14:44:18 linux-wg1g kernel: nvidia-modeset: Freed GPU:0 (GPU-389601bb-7a1f-6c19-129a-372e76c98315) @ PCI:0000:01:00.0
May 23 14:44:46 linux-wg1g kernel: nvidia_modeset: loading out-of-tree module taints kernel.
May 23 14:44:46 linux-wg1g kernel: nvidia_modeset: module license 'NVIDIA' taints kernel.
May 23 14:44:46 linux-wg1g kernel: nvidia_modeset: Unknown symbol nvidia_register_module (err 0)
May 23 14:44:46 linux-wg1g kernel: nvidia_modeset: Unknown symbol nvidia_get_rm_ops (err 0)
May 23 14:44:46 linux-wg1g kernel: nvidia_modeset: Unknown symbol nvidia_unregister_module (err 0)
May 23 14:44:58 linux-wg1g kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 247
May 23 14:45:02 linux-wg1g kernel: nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 246
May 23 14:45:02 linux-wg1g kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 375.66 Mon May 1 14:33:30 PDT 2017
May 23 14:45:02 linux-wg1g kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
May 23 14:45:27 linux-wg1g kernel: nvidia-modeset: Allocated GPU:0 (GPU-389601bb-7a1f-6c19-129a-372e76c98315) @ PCI:0000:01:00.0
May 23 14:49:49 linux-wg1g kernel: nvidia-modeset: Freed GPU:0 (GPU-389601bb-7a1f-6c19-129a-372e76c98315) @ PCI:0000:01:00.0
May 23 14:49:51 linux-wg1g kernel: nvidia-modeset: Allocated GPU:0 (GPU-389601bb-7a1f-6c19-129a-372e76c98315) @ PCI:0000:01:00.0
May 23 14:49:52 linux-wg1g kernel: nvidia-modeset: Freed GPU:0 (GPU-389601bb-7a1f-6c19-129a-372e76c98315) @ PCI:0000:01:00.0
May 23 14:50:19 linux-wg1g kernel: nvidia: loading out-of-tree module taints kernel.
May 23 14:50:19 linux-wg1g kernel: nvidia: module license 'NVIDIA' taints kernel.
May 23 14:50:19 linux-wg1g kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 248
May 23 14:50:19 linux-wg1g kernel: nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 247
May 23 14:50:19 linux-wg1g kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 375.66 Mon May 1 14:33:30 PDT 2017
May 23 14:50:19 linux-wg1g kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
How did you install the nvidia driver ? When I installed it I found an opensuse page that suggested different ways of doing it. One in particular didn’t look like a good idea to me (yast update) so I followed the method that suggested clicking community repo’s in yast repo’s and adding the nvidia site. Then installed the driver via yast software management. There are several drivers and for me the correct one to use had an 04 on the end. Searching for nvidia here also brings up some open gl libs which can also be installed.
dmesg should show something like this. I also have a warning about vga text mode.
dmesg | grep nvidia
1.876289] nvidia: loading out-of-tree module taints kernel.
1.876293] nvidia: module license 'NVIDIA' taints kernel.
1.884844] nvidia-nvlink: Nvlink Core is being initialized, major device number 248
1.889100] nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 247
1.947205] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 375.66 Mon May 1 14:33:30 PDT 2017
1.947787] [drm] [nvidia-drm] [GPU ID 0x00000500] Loading driver
48.044928] nvidia-modeset: Allocated GPU:0 (GPU-3e4b29b0-1bb6-ec1c-c665-d96a75d956e7) @ PCI:0000:05:00.0
5516.991296] nvidia-modeset: Freed GPU:0 (GPU-3e4b29b0-1bb6-ec1c-c665-d96a75d956e7) @ PCI:0000:05:00.0
5517.649577] nvidia-modeset: Allocated GPU:0 (GPU-3e4b29b0-1bb6-ec1c-c665-d96a75d956e7) @ PCI:0000:05:00.0
I’m wondering if you have installed the wrong driver. The 04 version is ok with cards from something like at least 6 or 7 years ago.
Problem though - the nvidia repo was down yesterday hopefully just for maintenance work. Another site that offers them is opensuse community. I also usually use that site for codecs rather than pacman. Once installed and working you should be able to add the open gl bits and pieces via sofware management. I am assuming those come from the usual repo’s.
When you do get it working you may find VLC has problems if you use it. Uninstall plus clean up, enable the pacman repo briefly, search vlc and install the beta V3 version. I had a nvidia driver update recently though so this may not be needed any more.
John
I installed the driver by adding the nvidia repo from the community repos in YasT and then going to the software management i clicked “extras” then “install all matching recommended packages”. Then i went to hardware info to verify the changes and sure enough its using the nvidia drivers.
Here is what dmesg gave me. my GPU is an MSI nvidia 970. So you think that the 04 driver is too old? I’m pretty sure I have 04 installed…
p nvidia
1.712729] nvidia: loading out-of-tree module taints kernel.
1.712736] nvidia: module license 'NVIDIA' taints kernel.
1.722536] nvidia-nvlink: Nvlink Core is being initialized, major device number 248
1.725042] nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 247
1.748462] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 375.66 Mon May 1 14:33:30 PDT 2017
1.749025] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
43.786239] nvidia-modeset: Allocated GPU:0 (GPU-389601bb-7a1f-6c19-129a-372e76c98315) @ PCI:0000:01:00.0
Good question. I’m not sure any one knows. I installed it initially on an older card and fitted a 1050ti a couple of weeks ago and 04 still functions correctly.
As I read the numbers on the drivers the 04 is the most recent one and suspect that the others are older and may have to be used on certain cards. So on that basis it’s best to install 04.
I didn’t install the way that you did. I tried yast’s update way but didn’t like the look of what it was going to do. It should have just indicated nvidia and related updates. I did it the way I usually do. It’s pretty simple.
Just add the repo for the driver to yast’s repo list. Then go to yasts software management and search nvidia. Then select the driver and any other files that are associated with the driver. The descriptions and names make it pretty clear which ones to install. It might be worth you doing the same search and seeing if anything is available but not installed.
However the repo seems to be dead at the moment. My refreshes aren’t telling me that but the links to it come up not found in a browser. From the version number this is the 04 driver and supports my 1050ti and your 970 so the 04 is the correct one to use. I believe it usually is.
http://www.nvidia.co.uk/download/driverResults.aspx/118428/en-uk
How to install the driver from that link. Not sure.
John
However the repo seems to be dead at the moment. My refreshes aren’t telling me that but the links to it come up not found in a browser.
Changed by Nvidia… You can not open it by Browser anymore.
Please post:
/sbin/lspci -nnk | grep -EiA3 'vga|display|3d'
uname -a
zypper se -si kernel-default nvidia
zypper lr -d
Please use Code-Tags for the Output.
Okay the output of lspci:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3160]
Kernel driver in use: nvidia
Kernel modules: nouveau, nvidia_drm, nvidia
The output for uname:
Linux linux-wg1g 4.4.62-18.6-default #1 SMP Fri Apr 21 16:14:48 UTC 2017 (84f9824) x86_64 x86_64 x86_64 GNU/Linux
Output for zypper se:
kernel-default nvidia
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
--+---------------------------+---------+-----------------------+--------+------------------------
i | kernel-default | package | 4.4.62-18.6.1 | x86_64 | Main Update Repository
i | kernel-default-devel | package | 4.4.62-18.6.1 | x86_64 | Main Update Repository
i | nvidia-computeG04 | package | 375.66-22.1 | x86_64 | nVidia Graphics Drivers
i | nvidia-gfxG04-kmp-default | package | 375.66_k4.4.27_2-22.1 | x86_64 | nVidia Graphics Drivers
i | nvidia-glG04 | package | 375.66-22.1 | x86_64 | nVidia Graphics Drivers
i | x11-video-nvidiaG04 | package | 375.66-22.1 | x86_64 | nVidia Graphics Drivers
Output for zypper lr:
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+-------------------------------------+--------------------------------------------------------+---------+-----------+---------+----------+--------+------------------------------------------------------------------------------+--------
1 | download.nvidia.com-leap | nVidia Graphics Drivers | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.nvidia.com/opensuse/leap/42.2 |
2 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/leap/42.2/repo/non-oss/ |
3 | download.opensuse.org-non-oss_1 | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/42.2/non-oss/ |
4 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/leap/42.2/repo/oss/ |
5 | download.opensuse.org-oss_1 | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/42.2/oss |
6 | games | games | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/games/openSUSE_Leap_42.2/ |
7 | google-chrome | google-chrome | Yes | (r ) Yes | Yes | 99 | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64 |
8 | home_adra | adra's Home Project (openSUSE_Leap_42.2) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/home:/adra/openSUSE_Leap_42.2/ |
9 | home_regataos | Regata OS Home Project (openSUSE_Leap_42.2) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/home:/regataos/openSUSE_Leap_42.2/ |
10 | http-download.opensuse.org-03400002 | Emulators | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/Emulators/openSUSE_Leap_42.2/ |
11 | http-download.opensuse.org-14c96ad5 | home:Krysanto | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/home:/Krysanto/openSUSE_Leap_42.2/ |
12 | http-download.opensuse.org-1eda8052 | openSUSE:Leap:42.2:Update | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/ports/update/leap/42.2/ |
13 | http-download.opensuse.org-246955d6 | home:xenonpk | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/home:/xenonpk/openSUSE_Leap_42.2/ |
14 | http-download.opensuse.org-9bfff39f | home:wsxy162 | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/home:/wsxy162/openSUSE_Leap_42.2/ |
15 | http-download.opensuse.org-ad93ab8f | home:awissu | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/home:/awissu/openSUSE_Leap_42.2/ |
16 | http-download.opensuse.org-c71c2f7b | home:dnh | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/home:/dnh/openSUSE_Leap_42.2/ |
17 | openSUSE-42.2-0 | openSUSE-42.2-0 | No | ---- | ---- | 99 | yast2 | hd:///?device=/dev/disk/by-id/scsi-1SanDiskUltra-part2 |
18 | packman | packman | Yes | (r ) Yes | Yes | 99 | rpm-md | http://packman.inode.at/suse/openSUSE_Leap_42.2 |
19 | packman.inode.at-suse | Packman Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://packman.inode.at/suse/openSUSE_Leap_42.2/ |
20 | repo-debug | openSUSE-Leap-42.2-Debug | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/42.2/repo/oss/ |
21 | repo-debug-non-oss | openSUSE-Leap-42.2-Debug-Non-Oss | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/42.2/repo/non-oss/ |
22 | repo-debug-update | openSUSE-Leap-42.2-Update-Debug | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/update/leap/42.2/oss/ |
23 | repo-debug-update-non-oss | openSUSE-Leap-42.2-Update-Debug-Non-Oss | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/update/leap/42.2/non-oss/ |
24 | repo-source | openSUSE-Leap-42.2-Source | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/42.2/repo/oss/ |
25 | repo-source-non-oss | openSUSE-Leap-42.2-Source-Non-Oss | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/42.2/repo/non-oss/ |
26 | utilities | all the small tools for the shell (openSUSE_Leap_42.2) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/utilities/openSUSE_Leap_42.2/ |
I also notice if I have my small display powered off when i boot, the graphics are fine, and when I switch my larger display off or to another source the smaller display stays normal. Wierd…
Maybe try to boot with the conflicting Display and see, what /var/log/Xorg.0.log is saying?
That’s some repo list. Might be the cause of your problems. Personally I only have the default repo’s enable and keep some disabled but most of the time when I install an unsupported package from the software search I use the option to tell yast to use the repo but not retain it. If for some reason it stops working or I think it may have been upgraded I just use the search again and do the same thing.
:shame:I have been known to be naughty in this respect at times but usually do get round to deleting some of the kept ones. I should know better because in the past I have found myself with a mix of library files from different development routes that can not work together. This can even happen if packman remains enabled. All that need to remain enabled and refreshed are these - except various file systems, yast needs that to switch to running without swap.
zypper lr
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh
---+-------------------------------------+-----------------------------------+---------+-----------+--------
1 | Perl_Development | Perl Development | No | ---- | ----
2 | Varrious_files_systems | Varrious files systems | Yes | (r ) Yes | Yes
3 | download.nvidia.com-leap | nVidia Graphics Drivers | Yes | (r ) Yes | Yes
4 | http-download.opensuse.org-178b527f | openSUSE:Leap:42.2:Ports | No | ---- | ----
5 | http-download.opensuse.org-7b61e500 | multimedia:photo ######## Fotoxx | No | ---- | ----
6 | http-download.opensuse.org-87633179 | home:rawtherapee ############ | No | ---- | ----
7 | openSUSE-42.2-0 | openSUSE-42.2-0 | No | ---- | ----
8 | packman.inode.at-suse | Packman Repository | No | ---- | ----
9 | repo-non-oss | openSUSE-Leap-42.2-Non-Oss | Yes | (r ) Yes | Yes
10 | repo-oss | openSUSE-Leap-42.2-Oss | Yes | (r ) Yes | Yes
11 | repo-source | openSUSE-Leap-42.2-Source | No | ---- | ----
12 | repo-update | openSUSE-Leap-42.2-Update | Yes | (r ) Yes | Yes
13 | repo-update-non-oss | openSUSE-Leap-42.2-Update-Non-Oss | Yes | (r ) Yes | Yes
John
I’m not sure if I understand your issue corectly
is the resolution at startup bigger then you’d want it to be?
during startup nvidia uses the system (root’s) display settings
I had an issue on an older tft monitor I had setup at a smaller resolution but during boot it was at maximum which drove me nuts
the solution was to run the nvidia-settings utility as root and save the settings to /etc/X11/xorg.conf
you can manually edit /etc/X11/xorg.conf and set the preferred resolution but using nvidia’s configuration is much easyer
I suspect or have been assuming the OP means that the graphics / icons on the display are too big - a kde setting but on my set up the size of the icons can be changed but the spacing remains the same so for different screen sizes and resolution something some where must change that aspect.
I somehow doubt he really means the environment.
xorg.conf ? No signs of it on my kde set up. I’ve been trying to figure out how x is involved with the monitor for other reasons and no luck at all. There is an xorg.conf.d directory with a number of dot cong files in it. Nothing monitor related though that isn’t just commented out.
There is an xorg.conf.install but what’s in it doesn’t make much sense.
John
xorg.conf has been depreciated but it can still be used for custom settings the nvidia driver can still use it
about “big icons” that could mean his resolution is too small?
anyhow linux is multi-user and the default graphics setup is not the same as the user setup
in my experience with custom resolution is that the nvidia driver uses the maximum supported unless told otherwise I had a bigger resolution setup for root (during boot and at the login screen) then as a user, running
kdesu nvidia-settigns
and exporting the setup to /etc/X11/xorg.conf fixed things (that file does not exist unless created)
Okay the problem seems to be with the KDE plasman DE. I installed GNOME and the problem seems to be gone.