Results 1 to 9 of 9

Thread: Nvidia driver and oversize X windows/toolbar

  1. #1
    Join Date
    Aug 2020
    Location
    Lyon, France
    Posts
    8

    Default Nvidia driver and oversize X windows/toolbar

    Hi everyone.

    I have been pulling my hairs for some time, trying to get Nvidia driver working on my PC. I have done quite some reading and haven't found the solution. I need more hints and knowledge sharing.

    The issue I have, after installing x11-video-nvidiaG05 for my GT 1030 graphic card, is the icones on the task manager area of the toolbar are oversize (including the application menu) and the window bars are oversize too with huge font size. Of course, I haven't change the KDE configuration moving from Nouveau to Nvidia driver. The screen resolution is correct (1920x1080). Here are a few screenshots of the full screen to illustrate :







    Interesting enough maybe, the last screen shot shows a spotify window with the correct size inside despite the oversize window bar and buttons. I have installed spotify with flatpak.
    I have followed the instruction of the wiki https://en.opensuse.org/SDB:NVIDIA_drivers and used zypper for the installation.

    I have the following hardware and configuration (inxi -SGxxz) :
    Code:
    System:
      Kernel: 5.3.18-lp152.33-default x86_64 bits: 64 compiler: gcc v: 7.5.0 
      Desktop: N/A dm: SDDM Distro: openSUSE Leap 15.2 
    Graphics:
      Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: Gigabyte driver: nvidia 
      v: 450.57 bus ID: 01:00.0 chip ID: 10de:1d01 
      Display: x11 server: X.Org 1.20.3 compositor: kwin_x11 driver: nvidia 
      unloaded: fbdev,modesetting,nouveau,vesa alternate: nv 
      resolution: 1920x1080~60Hz s-dpi: 305 
      OpenGL: renderer: GeForce GT 1030/PCIe/SSE2 v: 4.6.0 NVIDIA 450.57 
      direct render: Yes
    I have installed openSUSE in legacy mode and I am not using UEFI neither secure boot. But I have tried before with an UEFI installation (without secure boot still) and I got the same result...

    The Nvidia driver seems to load even if I get a complain on the log file about nvidia module signature verification failure. I don't have the folder /var/lib/nvidia-pubkeys as pointed out by the wiki. I don't get the EFI tool starting at reboot either.
    Here below is the outpout of journalctl -xe | grep -i nvidia
    Code:
    Aug 06 07:13:28 localhost kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
    Aug 06 07:13:28 localhost kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 242
    Aug 06 07:13:28 localhost kernel: nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
    Aug 06 07:13:28 localhost kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  450.57  Sun Jul  5 14:42:25 UTC 2020
    Aug 06 07:13:28 localhost kernel: audit: type=1400 audit(1596690808.785:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=783 comm="apparmor_parser"
    Aug 06 07:13:28 localhost kernel: audit: type=1400 audit(1596690808.785:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=783 comm="apparmor_parser"
    Aug 06 07:13:28 localhost kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
    Aug 06 07:13:28 localhost kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input17
    Aug 06 07:13:28 localhost kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input18
    Aug 06 07:13:28 localhost kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input19
    Aug 06 07:13:28 localhost kernel: input: HDA NVidia HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input20
    Aug 06 07:13:29 localhost kernel: nvidia-uvm: Loaded the UVM driver, major device number 240.
    Aug 06 07:13:29 localhost kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  450.57  Sun Jul  5 14:52:29 UTC 2020
    Aug 06 07:13:29 localhost kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
    Aug 06 07:13:29 localhost kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
    Aug 06 07:13:37 localhost.localdomain dbus-daemon[2339]: [session uid=1000 pid=2339] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.2' (uid=1000 pid=2347 comm="nvidia-settings --load-config-only ")
    Aug 06 07:13:37 localhost.localdomain dbus-daemon[2339]: [session uid=1000 pid=2339] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.5' (uid=1000 pid=2347 comm="nvidia-settings --load-config-only ")
    Aug 06 07:31:27 localhost.localdomain sudo[2886]:  barthol : TTY=pts/2 ; PWD=/home/barthol ; USER=root ; COMMAND=/usr/bin/nvidia-xconfig
    Aug 06 07:32:37 localhost.localdomain sudo[2902]:  barthol : TTY=pts/2 ; PWD=/home/barthol ; USER=root ; COMMAND=/usr/bin/nvidia-xconfig
    Aug 06 07:32:56 localhost.localdomain at-spi-bus-launcher[2397]: dbus-daemon[2402]: Activating service name='org.a11y.atspi.Registry' requested by ':1.19' (uid=1000 pid=2923 comm="/usr/bin/nvidia-settings ")
    Running nvidia-xconfig as root has not changed anything.

    When I installed the nvidia driver, I got 104 new packages installed and no error (a few warnings though). Here below is the output of the installation using sudo zypper in x11-video-nvidiaG05
    Code:
    Chargement des données du dépôt...
    Lecture des paquets installés...
    Résolution des dépendances des paquets...
    
    Les 104 NOUVEAUX paquets suivants vont être installés :
      gcc gcc7 glibc-32bit glibc-devel kernel-default-devel kernel-devel kernel-macros krb5-32bit libacl1-32bit libargon2-1-32bit libasan4 libatomic1 libattr1-32bit libaudit1-32bit libavahi-client3-32bit libavahi-common3-32bit libblkid1-32bit libcap2-32bit libcilkrts5 libcom_err2-32bit libcrack2-32bit libcryptsetup12-32bit libcups2-32bit libdbus-1-3-32bit libdcerpc0-32bit libdcerpc-binding0-32bit libdevmapper1_03-32bit libelf-devel libfam0-gamin-32bit libffi7-32bit libgcrypt20-32bit libglvnd-32bit libgmp10-32bit libgnutls30-32bit libgpg-error0-32bit libhogweed4-32bit libidn2-0-32bit libitm1 libjansson4-32bit libjson-c3-32bit libkeyutils1-32bit libldap-2_4-2-32bit libldb2-32bit liblsan0 liblz4-1-32bit liblzma5-32bit libmpx2 libmpxwrappers2 libndr0-32bit libndr-krb5pac0-32bit libndr-nbt0-32bit libndr-standard0-32bit libnetapi0-32bit libnettle6-32bit libnscd1-32bit libnsl2-32bit libopenssl1_1-32bit libp11-kit0-32bit libpcre1-32bit libpopt0-32bit libsamba-credentials0-32bit libsamba-errors0-32bit libsamba-hostconfig0-32bit libsamba-passdb0-32bit libsamba-util0-32bit libsamdb0-32bit libsasl2-3-32bit libseccomp2-32bit libselinux1-32bit libsmbconf0-32bit libsmbldap2-32bit libsystemd0-32bit libtalloc2-32bit libtasn1-6-32bit libtdb1-32bit libtevent0-32bit libtevent-util0-32bit libtirpc3-32bit libtsan0 libubsan0 libudev1-32bit libunistring2-32bit libuuid1-32bit libverto1-32bit libwbclient0-32bit libX11-6-32bit libXau6-32bit libxcb1-32bit libXext6-32bit libz1-32bit linux-glibc-devel Mesa-libGLESv1_CM1 Mesa-libGLESv2-2 mokutil nss-mdns-32bit nvidia-computeG05 nvidia-gfxG05-kmp-default nvidia-glG05 pam-32bit samba-client-32bit samba-libs-32bit systemd-32bit x11-video-nvidiaG05 zlib-devel
    
    Les 5 paquets recommandés suivants ont été automatiquement sélectionnés :
      gcc Mesa-libGLESv1_CM1 Mesa-libGLESv2-2 nvidia-glG05 x11-video-nvidiaG05
    
    .....
    .....
    (101/104) Installation de : nvidia-gfxG05-kmp-default-450.57_k5.3.18_lp152.19-lp152.38.1.x86_64 [............fait]
    .....
    /usr/src/kernel-modules/nvidia-450.57-default/nvidia/nv-mmap.c: In function ‘nvidia_mmap’:
    /usr/src/kernel-modules/nvidia-450.57-default/nvidia/nv-mmap.c:662:9: warning: unused variable ‘i’ [-Wunused-variable]
         int i = 0;
             ^
    /usr/src/kernel-modules/nvidia-450.57-default/nvidia/nv-mmap.c: In function ‘nv_encode_caching’:
    /usr/src/kernel-modules/nvidia-450.57-default/nvidia/nv-mmap.c:334:16: warning: this statement may fall through [-Wimplicit-fallthrough=]
                 if (NV_ALLOW_CACHING(memory_type))
                    ^
    /usr/src/kernel-modules/nvidia-450.57-default/nvidia/nv-mmap.c:336:9: note: here
             default:
             ^~~~~~~
    .......
    .......
    rm: cannot remove '/lib/modules/5.3.18-lp152.33-default/updates/nvidia*.ko': No such file or directory
    depmod: WARNING: could not open modules.order at /lib/modules/5.3.18-lp152.19-default: No such file or directory
    depmod: WARNING: could not open modules.builtin at /lib/modules/5.3.18-lp152.19-default: No such file or directory
    EFI variables are not supported on this system
    update-alternatives: using /usr/lib/nvidia/alternate-install-present-default to provide /usr/lib/nvidia/alternate-install-present (alternate-install-present) in auto mode
    
    Modprobe blacklist files have been created at /etc/modprobe.d to prevent Nouveau from loading. This can be reverted by deleting /etc/modprobe.d/nvidia-*.conf.
    
    *** Reboot your computer and verify that the NVIDIA graphics driver can be loaded. ***
    
    grep: /etc/sysconfig/kernel: No such file or directory
    What did I miss ?

    Thanks!

  2. #2
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    2,392

    Default Re: Nvidia driver and oversize X windows/toolbar

    Quote Originally Posted by squidfr View Post
    Code:
    ...
      resolution: 1920x1080~60Hz s-dpi: 305
    ...
    What did I miss ?
    I can't tell you why screen DPI is 305 (baseline is 96), but it's the reason for big text and icons. If the NVidia driver installer created any /etc/X11/xorg.con* files you should share them (using code tags, # icon above input window) if pasting here, but if more than several lines, better to submit them using the susepaste command or by visiting http://susepaste.org/.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.1, TW, 15.2 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&15.1 on i965P/Radeon
    Tertiary: TW,15.2,15.1,Fedora,Debian,more on Kaby Lake,iQ45,iQ43,iG41,iG3X,i965G,AMD,NVidia&&&

  3. #3
    Join Date
    Aug 2020
    Location
    Lyon, France
    Posts
    8

    Default Re: Nvidia driver and oversize X windows/toolbar

    Quote Originally Posted by mrmazda View Post
    I can't tell you why screen DPI is 305 (baseline is 96), but it's the reason for big text and icons. If the NVidia driver installer created any /etc/X11/xorg.con* files you should share them (using code tags, # icon above input window) if pasting here, but if more than several lines, better to submit them using the susepaste command or by visiting http://susepaste.org/.
    Hi @mrmazda. Thanks for stopping by.

    I have indeed a few xorg.conf* files. Here is the output of ls -l /etc/X11/xorg.con*

    Code:
    -rw-r--r-- 1 root root 1226  6 août  07:32 xorg.conf
    -rw-r--r-- 1 root root  938 25 juil. 11:55 xorg.conf.install
    -rw-r--r-- 1 root root    0  6 août  07:31 xorg.conf.nvidia-xconfig-original

    • xorg.conf.nvidia-xconfig-original is empty.
    • Here is xorg.conf (I think it is not too big to be shared in-between # tags)

    Code:
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig:  version 450.57
    
    
    Section "ServerLayout"
        Identifier     "Layout0"
        Screen      0  "Screen0" 0 0
        InputDevice    "Keyboard0" "CoreKeyboard"
        InputDevice    "Mouse0" "CorePointer"
    EndSection
    
    Section "Files"
    EndSection
    
    Section "InputDevice"
    
        # generated from data in "/etc/sysconfig/mouse"
        Identifier     "Mouse0"
        Driver         "mouse"
        Option         "Protocol" "IMPS/2"
        Option         "Device" "/dev/input/mice"
        Option         "Emulate3Buttons" "yes"
        Option         "ZAxisMapping" "4 5"
    EndSection
    
    Section "InputDevice"
    
        # generated from default
        Identifier     "Keyboard0"
        Driver         "kbd"
    EndSection
    
    Section "Monitor"
        Identifier     "Monitor0"
        VendorName     "Unknown"
        ModelName      "Unknown"
        Option         "DPMS"
    EndSection
    
    Section "Device"
        Identifier     "Device0"
        Driver         "nvidia"
        VendorName     "NVIDIA Corporation"
    EndSection
    
    Section "Screen"
        Identifier     "Screen0"
        Device         "Device0"
        Monitor        "Monitor0"
        DefaultDepth    24
        SubSection     "Display"
            Depth       24
        EndSubSection
    EndSection

    • Here is xorg.conf.install

    Code:
    Section "Device"
      Identifier "vboxvideo"
      Driver  "vboxvideo"
    EndSection
    
    Section "Screen"
      Identifier "vboxvideo"
      Device "vboxvideo"
    EndSection
    
    
    Section "Device"
      Identifier "vmware"
      Driver  "vmware"
    EndSection
    
    Section "Screen"
      Identifier "vmware"
      Device "vmware"
    EndSection
    
    
    Section "Device"
      Identifier "modesetting"
      Driver  "modesetting"
      Option "PreferCloneMode" "true"
      Option "AccelMethod" "none"
    EndSection
    Section "Screen"
      Identifier "modesetting"
      Device "modesetting"
    EndSection
    
    
    Section "Device"
      Identifier "fbdev"
      Driver  "fbdev"
    EndSection
    Section "Screen"
      Identifier "fbdev"
      Device "fbdev"
    EndSection
    
    
    Section "Device"
      Identifier "vesa"
      Driver  "vesa"
    EndSection
    
    Section "Screen"
      Identifier "vesa"
      Device "vesa"
    EndSection
    
    
    Section "ServerLayout"
      Identifier "Layout"
      Screen  "vboxvideo"
      Screen  "vmware"
      Screen  "modesetting"
      Screen  "fbdev"
      Screen  "vesa"
    EndSection
    Any idea ?

    Thanks!

  4. #4
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    2,392

    Default Re: Nvidia driver and oversize X windows/toolbar

    Quote Originally Posted by squidfr View Post
    Code:
    ...
    Section "Monitor"
        Identifier     "Monitor0"
        VendorName     "Unknown"
        ModelName      "Unknown"
        Option         "DPMS"
    EndSection
    ...
    Any idea ?
    Try adding:
    Code:
    Option	"DPI" "96 x 96"
    and/or
    Code:
    Option "UseEdidDpi" "False"
    to 'Section "Monitor"'. Once you have tried, please upload the newer of /var/log/Xorg.0.log or .local/share/xorg/Xorg.0.log using susepaste or via web browser to http://susepaste.org/
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.1, TW, 15.2 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&15.1 on i965P/Radeon
    Tertiary: TW,15.2,15.1,Fedora,Debian,more on Kaby Lake,iQ45,iQ43,iG41,iG3X,i965G,AMD,NVidia&&&

  5. #5
    Join Date
    Aug 2020
    Location
    Lyon, France
    Posts
    8

    Default Re: Nvidia driver and oversize X windows/toolbar

    Hi @mrmazda

    So, spot on, DPI value was the issue.

    I set the following option in /etc/X11/Xorg.conf :
    Code:
    Option "UseEdidDpi" "False"
    and got a DPI equals to 75. It was much better but not like with Nouveau driver.

    Then, I used
    Code:
    Option    "DPI" "96 x 96"
    and it looked like with Nouveau.

    To make sure it was the Nouveau DPI value, I reverted to the Nouveau driver by rolling back to the snapshot I created before installing Nvidia. Indeed, 96x96 is the DPI value used by Nouveau.

    Then, I reinstalled the Nvidia driver using zypper. I didn't get any xorg.conf created.
    I don't know why or how I got the idea to force the DPI font value in the Fonts menu of the KDE system configuration. But when I tick the box to force the DPI to 96, I get the same result than when I was able to modify the xorg.conf file with the DPI 96x96 option.

    So, I will leave it like that.

    Here is the link to the Xorg.0.log : https://paste.opensuse.org/93424926

    Would you have an explanation why Nouveau driver doesn't need to force the DPI but Nvidia one does ?
    Would you like any additional test or info from me before I set this thread as solved ?

    Thanks again! Take care!

  6. #6
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    2,392

    Default Re: Nvidia driver and oversize X windows/toolbar

    Quote Originally Posted by squidfr View Post
    Would you have an explanation why Nouveau driver doesn't need to force the DPI but Nvidia one does ?
    Would you like any additional test or info from me before I set this thread as solved ?
    FOSS software gets heavily tested as an integrated system. How much testing proprietary software gets when mixed with particular FOSS software there's no way to know. When using the FOSS nouveau DDX, absent intervention, X automatically forces 96 DPI regardless of physical DPI. The proprietary driver was likely trying to force an accurate DPI, and botching it. It could be that driver's fault, but it also could be that some part of the EDID for your display has some defect that caused the proprietary driver to grossly miscalculate. To try to determine which you could report your observations on an official NVidia forum. You might also inquire whether your display has an available firmware update, and same for your motherboard, and your GT 1030. A defect in any could impact the calculations.

    Note that NVidia and Nouveau are not your only X driver choices. There's also a DDX named Modesetting, as explained here.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.1, TW, 15.2 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&15.1 on i965P/Radeon
    Tertiary: TW,15.2,15.1,Fedora,Debian,more on Kaby Lake,iQ45,iQ43,iG41,iG3X,i965G,AMD,NVidia&&&

  7. #7
    Join Date
    Aug 2020
    Location
    Lyon, France
    Posts
    8

    Default Re: Nvidia driver and oversize X windows/toolbar

    Quote Originally Posted by mrmazda View Post
    Note that NVidia and Nouveau are not your only X driver choices. There's also a DDX named Modesetting, as explained here.
    Thanks for your pedagogic answer and link.
    In fact, my intend by installing Nvidia driver is to get a better integration of opencl and use of cuda core.
    But, maybe, it is wrongly assumed and I should better stay with Nouveau. Should I ?

  8. #8
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    2,392

    Default Re: Nvidia driver and oversize X windows/toolbar

    Quote Originally Posted by squidfr View Post
    In fact, my intend by installing Nvidia driver is to get a better integration of opencl and use of cuda core.
    But, maybe, it is wrongly assumed and I should better stay with Nouveau. Should I ?
    That really depends on whether the apps you use utilize opencl and cuda at all, or to an extent you would find worth the effort involved with keeping kernel and NVidia drivers in sync. Nouveau or modesetting might make more sense, but likely you can't be sure without trying all three choices.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.1, TW, 15.2 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&15.1 on i965P/Radeon
    Tertiary: TW,15.2,15.1,Fedora,Debian,more on Kaby Lake,iQ45,iQ43,iG41,iG3X,i965G,AMD,NVidia&&&

  9. #9
    Join Date
    Aug 2020
    Location
    Lyon, France
    Posts
    8

    Default Re: Nvidia driver and oversize X windows/toolbar

    Quote Originally Posted by mrmazda View Post
    That really depends on whether the apps you use utilize opencl and cuda at all, or to an extent you would find worth the effort involved with keeping kernel and NVidia drivers in sync. Nouveau or modesetting might make more sense, but likely you can't be sure without trying all three choices.
    Hi @mrmazda

    It is especially to be used with Foldingathome and I know Opencl and/or Cuda is required.
    I understand then only testing will provide the answer. Will do that.

    Thanks again for your support and take care.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •