@manuel_songokuh Can you change nvidia.drm_modset=1 to nvidia_drm.modeset=1 a typo on my part.
inxi -GSaz
System:
Kernel: 6.4.0-150600.23.17-default arch: x86_64 bits: 64 compiler: gcc
v: 7.5.0 parameters: BOOT_IMAGE=/boot/vmlinuz-6.4.0-150600.23.17-default
root=UUID=542228e9-832a-48b2-b02c-141539733762 splash=silent
video=1920x1080 preempt=full quiet security=apparmor nvidia_drm.modeset=1
mitigations=auto
Desktop: KDE Plasma v: 5.27.11 tk: Qt v: 5.15.12 wm: kwin_x11 vt: 2
dm: SDDM Distro: openSUSE Leap 15.6
Graphics:
Device-1: NVIDIA GM204 [GeForce GTX 970] vendor: PNY driver: nvidia
v: 550.107.02 alternate: nouveau,nvidia_drm non-free: 530.xx+
status: current (as of 2023-05) arch: Maxwell code: GMxxx
process: TSMC 28nm built: 2014-19 pcie: gen: 3 speed: 8 GT/s lanes: 8
link-max: lanes: 16 ports: active: none off: DVI-I-1 empty: DP-1, DP-2,
DP-3, HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:13c2 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.11 with: Xwayland v: 24.1.1
compositor: kwin_x11 driver: X: loaded: nvidia
unloaded: fbdev,modesetting,vesa alternate: nouveau,nv
gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
Screen-1: 0 s-res: 1600x900 s-dpi: 75 s-size: 541x304mm (21.30x11.97")
s-diag: 621mm (24.43")
Monitor-1: DVI-I-1 note: disabled res: 1600x900 hz: 60 size: N/A modes:
max: 1024x768 min: 640x480
API: OpenGL v: 4.6.0 NVIDIA 550.107.02 renderer: NVIDIA GeForce GTX
970/PCIe/SSE2 direct-render: Yes
same issue…
maybe i will do re-install other RUN (BRANCH)…?
(this is branch…NVIDIA-Linux-x86_64-560.35.03.run)
my pc installed RUN (official/certificate)
NVIDIA-Linux-x86_64-550.107.02.run
…
@manuel_songokuh It won’t make a difference, there is some detection (EDID) issue with the monitor.
[ 16.238] (II) NVIDIA(0): Setting mode "DVI-I-1: 1600x900 @1600x900 +0+0 {ViewPortIn=1600x900, ViewPortOut=1600x900+0+0}"
Can you switch to the HDMI or DP ports on the card?
i use DVI… i will try HDMI later…
but windows 10 works nvidia close driver same cable DVI… but issue only to opensuse…it is true strange… but neauveau was works same cable DVI…i don’t understand…
Can you create a test user and login as the test user and see if can adjust there.
@manuel_songokuh Also as you user can you open a terminal and in your $HOME directory run fgrep -r "ViewPort" *
i did new user testing, nothing adjust…same 1600x900 
fgrep -r "ViewPort" *
/preview/ita/a--js/wwb19.min.js:(function(a){a.fn.inViewPort=function(b){var c=a(window).scrollTop(),d=c+a(window).height(),e=a(this).offset().top,g=e+a(this).height();return(!0===b?e:g)<=d&&(!0===b?g:e)>=c}})(jQuery);
/preview/eng/a--js/wwb19.min.js:(function(a){a.fn.inViewPort=function(b){var c=a(window).scrollTop(),d=c+a(window).height(),e=a(this).offset().top,g=e+a(this).height();return(!0===b?e:g)<=d&&(!0===b?g:e)>=c}})(jQuery);
/Free-templates/boolar_theme/Boolar Template/Boolar html template/bolar.html: if (!$obj.hasClass("in-viewport") && $obj.inViewPort(false))
/Free-templates/boolar_theme/Boolar Template/Boolar html template/bolar.html: if ($obj.hasClass("in-viewport") && !$obj.inViewPort(true))
/Free-templates/boolar_theme/Boolar Template/Boolar html template/bolar.html: if (!$('#Button1').inViewPort(true))
/Free-templates/boolar_theme/Boolar Template/Boolar html template/bolar.html: if (!$obj.hasClass("in-viewport") && $obj.inViewPort(false))
/Free-templates/boolar_theme/Boolar Template/Boolar html template/index.html: if (!$obj.hasClass("in-viewport") && $obj.inViewPort(false))
/Free-templates/boolar_theme/Boolar Template/Boolar html template/index.html: if ($obj.hasClass("in-viewport") && !$obj.inViewPort(true))
/Free-templates/boolar_theme/Boolar Template/Boolar html template/index.html: if (!$('#Button1').inViewPort(true))
/Free-templates/boolar_theme/Boolar Template/Boolar html template/script/wwb17.min.js:(function(a){a.fn.inViewPort=function(b){var c=a(window).scrollTop(),d=c+a(window).height(),e=a(this).offset().top,g=e+a(this).height();return(!0===b?e:g)<=d&&(!0===b?g:e)>=c}})(jQuery);
if issue is remain… so can ask to forum NVIDIA official?
@manuel_songokuh If you run fgrep -r "ViewPort" /etc/X11/* any output there?
Sure, you can ask wherever you like 
I suspect it’s some sort of regression somewhere…
nothing output of fgrep: /etc/X11/* /etc/* /bin/* but i find somethings from /usr/*
here output:
sudo fgrep -r "ViewPort" /usr/*
/usr/bin/inxi: # ViewPortOut=1280x1024+0+0}, DPY-1: nvidia-auto-select @1280x1024 +1280+0 {ViewPortIn=1280x1024,
/usr/bin/inxi: # ViewPortOut=1280x1024+0+0}
Il file binario /usr/bin/nvidia-settings corrisponde
Il file binario /usr/lib/libXxf86vm.so.1.0.0 corrisponde
Il file binario /usr/lib/wine/i386-unix/winex11.so corrisponde
Il file binario /usr/lib/virtualbox/VBoxDD.so corrisponde
Il file binario /usr/lib64/qt5/plugins/okularpart.so corrisponde
/usr/lib64/xorg/protocol.txt:R003 XFree86-DGA:GetViewPortSize
/usr/lib64/xorg/protocol.txt:R004 XFree86-DGA:SetViewPort
/usr/lib64/xorg/protocol.txt:R009 XFree86-DGA:ViewPortChanged
/usr/lib64/xorg/protocol.txt:R011 XFree86-VidModeExtension:GetViewPort
/usr/lib64/xorg/protocol.txt:R012 XFree86-VidModeExtension:SetViewPort
Il file binario /usr/lib64/xorg/modules/drivers/nvidia_drv.so corrisponde
Il file binario /usr/lib64/libXxf86vm.so.1.0.0 corrisponde
Il file binario /usr/lib64/libnvidia-gtk3.so.550.107.02 corrisponde
Il file binario /usr/lib64/libreoffice/program/libmergedlo.so corrisponde
Il file binario /usr/lib64/firefox/omni.ja corrisponde
Il file binario /usr/lib64/firefox/libxul.so corrisponde
Il file binario /usr/lib64/jvm/java-11-openjdk-11/lib/modules corrisponde
Il file binario /usr/lib64/wine/x86_64-unix/winex11.so corrisponde
Il file binario /usr/lib64/libnvidia-gtk2.so.550.107.02 corrisponde
Il file binario /usr/lib64/libXxf86dga.so.1.0.0 corrisponde
/usr/share/X11/XErrorDB:XRequest.XFree86-VidModeExtension.11: XF86VidModeGetViewPort
/usr/share/X11/XErrorDB:XRequest.XFree86-VidModeExtension.12: XF86VidModeSetViewPort
/usr/share/X11/XErrorDB:XRequest.XFree86-DGA.3: XF86DGAGetViewPortSize
/usr/share/X11/XErrorDB:XRequest.XFree86-DGA.4: XF86DGASetViewPort
/usr/share/X11/XErrorDB:XRequest.XFree86-DGA.9: XF86DGAViewPortChanged
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: transformation from the ViewPortOut for a display device to a region
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: "DFP-0: 1920x1080 +0+0 { PixelShiftMode = 4kTopLeft, ViewPortIn =
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: ViewPortIn = 3840x2160 }"
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: In 8K pixel shift mode, the image is downscaled from the ViewPortIn
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: each display are in X screen (ViewPortIn) coordinates:
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: "DFP-0: 1024x2400 +0+0 { PixelShiftMode=8k, ViewPortIn = 2048x4800 },
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: DFP-1: 1024x2400 +2048+0 { PixelShiftMode=8k, ViewPortIn = 2048x4800 },
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: DFP-2: 1024x2400 +4096+0 { PixelShiftMode=8k, ViewPortIn = 2048x4800 },
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: DFP-4: 1024x2400 +6144+0 { PixelShiftMode=8k, ViewPortIn = 2048x4800 }"
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: In both examples above, the ViewPortIn is provided here for illustrative
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: purposes only. When PixelShiftMode is used, the ViewPortIn and
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: ViewPortOut are always inferred from the mode timings: the ViewPortOut
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: resolution. The ViewPortIn will be twice the ViewPortOut, in order to
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: o "ViewPortOut": this specifies the region within the mode sent to the
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: the mode outside the ViewPortOut will contain black. The format is "WIDTH
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: "DFP-0: 1920x1080 { ViewPortOut=1900x1060+10+10 }"
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: "DFP-0: 1920x1080 { ViewPortOut=960x540+960+540 }"
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: When not specified, the ViewPortOut defaults to the size of the mode.
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: o "ViewPortIn": this defines the size of the region of the X screen which
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: will be displayed within the ViewPortOut. The format is "WIDTH x HEIGHT".
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: ViewPortIn is useful for configuring scaling between the X screen and the
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: "DFP-0: 1920x1200 { ViewPortIn=800x600 }"
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: "DFP-0: 1920x1200 { ViewPortIn=2560x1600 }"
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: Or, in conjunction with ViewPortOut, to scale an 800x600 region of the X
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: "DFP-0: 1920x1200 { ViewPortIn=800x600, ViewPortOut=1600x1200+160+0
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: Scaling from ViewPortIn to ViewPortOut is also expressible through the
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: "Transform" attribute. In fact, ViewPortIn is just a shortcut for
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: populating the transformation matrix. If both ViewPortIn and Transform
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: are specified in the MetaMode for a display device, ViewPortIn is
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: ViewPortIn is also ignored if PixelShiftMode is enabled, as
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: ViewPortIn that will activate panning if the pointer hits them. If the
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: of the ViewPortIn (the default). If the borders are positive, the display
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: ViewPortIn. If the borders are negative, the display device will pan when
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: the pointer is beyond the edge of the ViewPortIn.
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: makes use of the composition pipeline to apply ViewPortOut scaling.
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: scaling ViewPortOut) are in use. Possible values are "Bilinear"
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: ViewPortIn=800x600, ViewPortOut=1600x1200+160+0 }"
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: This property is functionally equivalent to the ViewPortOut MetaMode
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: ViewPortIn, and nvidia-auto-select will be the mode. The ViewPortOut will
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: be configured such that the ViewPortIn is aspect scaled within the mode.
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: 12 for details of the relationship between ViewPortIn, ViewPortOut, and
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: o "Scaling": specifies how the ViewPortOut should be configured between
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: the ViewPortIn and the mode for the common resolution-based implicit
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: will be used as the ViewPortIn, the nvidia-auto-select mode will be
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: used as the mode, and the ViewPortOut will be computed to aspect
/usr/share/doc/NVIDIA_GLX-1.0/README.txt: composition pipeline to apply ViewPortOut scaling.
/usr/share/doc/NVIDIA_GLX-1.0/NVIDIA_Changelog: * Fixed a regression that caused the current MetaMode's ViewPortIn and
/usr/share/doc/NVIDIA_GLX-1.0/NVIDIA_Changelog: ViewPortOut settings to be preserved across RandR modesets. The driver now
/usr/share/doc/NVIDIA_GLX-1.0/NVIDIA_Changelog: clears ViewPortIn and ViewPortOut when the mode is set through RandR,
/usr/share/doc/NVIDIA_GLX-1.0/NVIDIA_Changelog: underscan border around the ViewPortOut. This feature was
/usr/share/doc/NVIDIA_GLX-1.0/NVIDIA_Changelog: configuration, such as the ViewPort or panning domain, changed.
/usr/share/doc/NVIDIA_GLX-1.0/NVIDIA_Changelog: properties, which can be used to configure the ViewPortOut of an
/usr/share/doc/NVIDIA_GLX-1.0/NVIDIA_Changelog: RandR output. This is functionally equivalent to the "ViewPortOut"
/usr/share/doc/NVIDIA_GLX-1.0/NVIDIA_Changelog: information when an RandR output has a custom ViewPortIn.
/usr/share/doc/NVIDIA_GLX-1.0/NVIDIA_Changelog: information when an RandR output has a custom ViewPortIn.
/usr/share/doc/NVIDIA_GLX-1.0/NVIDIA_Changelog: MetaMode ViewPort scaling.
/usr/share/doc/NVIDIA_GLX-1.0/NVIDIA_Changelog: * Added support for configuring the ViewPortIn and ViewPortOut for display
/usr/share/doc/NVIDIA_GLX-1.0/NVIDIA_Changelog: "ViewPortOut" : specifies the region of the mode in which to
/usr/share/doc/NVIDIA_GLX-1.0/NVIDIA_Changelog: "ViewPortIn" : specifies the size of the region in the X screen
/usr/share/doc/NVIDIA_GLX-1.0/NVIDIA_Changelog: to display in the ViewPortOut
/usr/share/doc/NVIDIA_GLX-1.0/NVIDIA_Changelog: through the ViewPortIn and ViewPortOut MetaMode attributes.
/usr/share/doc/NVIDIA_GLX-1.0/NVIDIA_Changelog: configured explicitly through the new "ViewPortIn" and "ViewPortOut"
/usr/share/doc/NVIDIA_GLX-1.0/NVIDIA_Changelog: Any desired scaling can be configured through the new "ViewPortIn"
/usr/share/doc/NVIDIA_GLX-1.0/NVIDIA_Changelog: and "ViewPortOut" MetaMode attributes.
/usr/share/doc/NVIDIA_GLX-1.0/html/xconfigoptions.html:resolution will be the ViewPortIn, and nvidia-auto-select will be
/usr/share/doc/NVIDIA_GLX-1.0/html/xconfigoptions.html:the mode. The ViewPortOut will be configured such that the
/usr/share/doc/NVIDIA_GLX-1.0/html/xconfigoptions.html:ViewPortIn is aspect scaled within the mode. Each common resolution
/usr/share/doc/NVIDIA_GLX-1.0/html/xconfigoptions.html:relationship between ViewPortIn, ViewPortOut, and the mode within a
/usr/share/doc/NVIDIA_GLX-1.0/html/xconfigoptions.html:<p>"Scaling": specifies how the ViewPortOut should be configured
/usr/share/doc/NVIDIA_GLX-1.0/html/xconfigoptions.html:between the ViewPortIn and the mode for the common resolution-based
/usr/share/doc/NVIDIA_GLX-1.0/html/xconfigoptions.html:MetaModes: the resolution will be used as the ViewPortIn, the
/usr/share/doc/NVIDIA_GLX-1.0/html/xconfigoptions.html:ViewPortOut will be computed to aspect scale the resolution within
/usr/share/doc/NVIDIA_GLX-1.0/html/xconfigoptions.html:composition pipeline to apply ViewPortOut scaling.</p>
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:defines a transformation from the ViewPortOut for a display device
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html: "DFP-0: 1920x1080 +0+0 { PixelShiftMode = 4kTopLeft, ViewPortIn = 3840x2160 }, DFP-1: 1920x1080 +0+0 { PixelShiftMode = 4kBottomRight, ViewPortIn = 3840x2160 }"
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:ViewPortIn resolution to the mode timing resolution, to produce two
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:the panning offsets of each display are in X screen (ViewPortIn)
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html: "DFP-0: 1024x2400 +0+0 { PixelShiftMode=8k, ViewPortIn = 2048x4800 }, DFP-1: 1024x2400 +2048+0 { PixelShiftMode=8k, ViewPortIn = 2048x4800 }, DFP-2: 1024x2400 +4096+0 { PixelShiftMode=8k, ViewPortIn = 2048x4800 }, DFP-4: 1024x2400 +6144+0 { PixelShiftMode=8k, ViewPortIn = 2048x4800 }"
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:<p>In both examples above, the ViewPortIn is provided here for
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:ViewPortIn and ViewPortOut are always inferred from the mode
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:timings: the ViewPortOut will match the mode timing resolution,
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:which is half the intended resolution. The ViewPortIn will be twice
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:the ViewPortOut, in order to achieve the pixel shift effect.</p>
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:<p>"ViewPortOut": this specifies the region within the mode sent to
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:region of the mode outside the ViewPortOut will contain black. The
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html: "DFP-0: 1920x1080 { ViewPortOut=1900x1060+10+10 }"
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html: "DFP-0: 1920x1080 { ViewPortOut=960x540+960+540 }"
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:<p>When not specified, the ViewPortOut defaults to the size of the
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:<p>"ViewPortIn": this defines the size of the region of the X
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:screen which will be displayed within the ViewPortOut. The format
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:<p>ViewPortIn is useful for configuring scaling between the X
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html: "DFP-0: 1920x1200 { ViewPortIn=800x600 }"
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html: "DFP-0: 1920x1200 { ViewPortIn=2560x1600 }"
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:<p>Or, in conjunction with ViewPortOut, to scale an 800x600 region
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html: "DFP-0: 1920x1200 { ViewPortIn=800x600, ViewPortOut=1600x1200+160+0 }"
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:<p>Scaling from ViewPortIn to ViewPortOut is also expressible
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:through the "Transform" attribute. In fact, ViewPortIn is just a
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:ViewPortIn and Transform are specified in the MetaMode for a
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:display device, ViewPortIn is ignored.</p>
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:<p>ViewPortIn is also ignored if PixelShiftMode is enabled, as
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:the ViewPortIn that will activate panning if the pointer hits them.
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:hits the edge of the ViewPortIn (the default). If the borders are
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:to the edge of the ViewPortIn. If the borders are negative, the
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:ViewPortIn.</p>
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:ViewPortOut scaling.</p>
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html:WarpMesh or scaling ViewPortOut) are in use. Possible values are
/usr/share/doc/NVIDIA_GLX-1.0/html/configtwinview.html: nvidia-settings --assign CurrentMetaMode="DFP-0: 1920x1200 { ViewPortIn=800x600, ViewPortOut=1600x1200+160+0 }"
/usr/share/doc/NVIDIA_GLX-1.0/html/xrandrextension.html:<p>This property is functionally equivalent to the ViewPortOut
/usr/share/doc/packages/libgtkmm-3_0-1/NEWS:* IconView, Layout, TextView, ToolPallete, TreeView, ViewPort:
/usr/share/doc/packages/xscreensaver/README: * Added "GetViewPortIsFullOfLies" preference to work around
/usr/share/vim/vim91/syntax/xf86conf.vim:syn keyword xf86confKeyword VertRefresh VideoRam ViewPort Virtual VScan VTimings nextgroup=xf86confComment,xf86confValue
/usr/share/vim/vim91/syntax/pascal.vim: syn keyword pascalFunction Arc Bar Bar3D Circle ClearDevice ClearViewPort
/usr/share/vim/vim91/syntax/pascal.vim: syn keyword pascalFunction SetTextStyle SetUserCharSize SetViewPort
/usr/share/vim/vim91/syntax/pascal.vim: syn keyword pascalType TextSettingsType ViewPortType
/usr/share/augeas/lenses/dist/xorg.aug: * > ViewPort x0 y0
/usr/share/augeas/lenses/dist/xorg.aug: entry_xy "ViewPort" /[vV]iew[pP]ort/ |
Il file binario /usr/share/wine/mono/wine-mono-8.1.0/lib/mono/4.5/System.Reflection.Metadata.dll corrisponde
Il file binario /usr/share/wine/mono/wine-mono-8.1.0/lib/mono/gac/PresentationFramework/4.0.0.0__31bf3856ad364e35/PresentationFramework.dll corrisponde
/usr/src/linux-6.4.0-150600.23.17/drivers/media/usb/pwc/pwc-if.c: { USB_DEVICE(0x046D, 0x08B7) }, /* Logitech ViewPort AV 100 */
/usr/src/linux-6.4.0-150600.23.17/drivers/media/usb/pwc/pwc-if.c: PWC_INFO("Logitech ViewPort AV 100 webcam detected.\n");
/usr/src/linux-6.4.0-150600.23.17/drivers/media/usb/pwc/pwc-if.c: name = "Logitech ViewPort AV 100";
/usr/src/linux-6.4.0-150600.23.17/drivers/video/fbdev/kyro/STG4000Interface.h:extern int SetOverlayViewPort(volatile STG4000REG __iomem *pSTGReg,
/usr/src/linux-6.4.0-150600.23.17/drivers/video/fbdev/kyro/STG4000OverlayDevice.c:int SetOverlayViewPort(volatile STG4000REG __iomem *pSTGReg,
/usr/src/linux-6.4.0-150600.23.17/drivers/video/fbdev/kyro/fbdev.c: SetOverlayViewPort(deviceInfo.pSTGReg,
/usr/src/linux-6.4.0-150600.23.17/Documentation/admin-guide/media/other-usb-cardlist.rst:pwc Logitech ViewPort AV 100 046D:08B7
Il file binario /usr/src/nvidia-550.107.02/nvidia-modeset/nv-modeset-kernel.o_binary corrisponde
Il file binario /usr/src/kernel-modules/nvidia-550.100-default/nvidia-modeset.ko corrisponde
Il file binario /usr/src/kernel-modules/nvidia-550.100-default/nvidia-modeset.o corrisponde
note: my Card video nvidia: has port HDMI (but it is mini-hdmi, so i have not it the cable mini-hdmi, i will buy…) but i don’t understand: windows 10 same calbe DVI, resolution is correct: 1920x1080… also boot grub2 has 1920x1080…but not opensuse with KDE…maybe problem is Xorg X11 starting to KDE…?
now my resolution is 1600x900…
hi
nothing reply…?
@manuel_songokuh I don’t run Plasma, so can’t really offer advice. Do you have an xorg.conf file?
hi, i don’t find file xorg.conf…
i will try desktop of MATE for testing?
update:
i did try icewm , result default is 1280x720
i did try wayland, result default is 800x600
now is X11 = 1600x900 maybe is problem from X11 / Xorg… check version of x11?
@manuel_songokuh Seems to be a modeline issue/regression (which sets the resolution). I think a bug report may be needed…
ok, where i will sent the report isssue/bug?
i see that report is hard for me to write in english… you can write for me?
@manuel_songokuh On second thoughts since it’s using the proprietary driver a report on the Nvidia Forums might be better.
As root user, run nvidia-bug-report.sh to create the log file they want “nvidia-bug-report.log.gz” and suggest you open a new thread there explaining the issue.
i did open topic to forum nvidia but nothing reply…