Why sometimes I get random freezes even with Nvidia Proprietary Drivers?

pinguin20 · 02-02-2022, 05:03 PM

Nouveau causes random freezes more frequently, but even blacklisting it and installing Nvidia instead I still get random freezes but less frequently. I don't know if I need to uninstall a package or if forgot to install something really important. I installed Nvidia via Yast by the way and here are the screenshots of my Yast Software Manager

[1]: https://i.stack.imgur.com/RZOc8.png
[2]: https://i.stack.imgur.com/ye9qC.png
[3]: https://i.stack.imgur.com/YPbNU.png
[4]: https://i.stack.imgur.com/4lylP.png

openSUSE Leap 15.3 64 bits

MATE 1.24.0

kernel 5.3.18-150300.59.43-default

Intel® Core™ i3 CPU 540 @ 3.07GHz × 4

RAM: 3,7 GiB

Nvidia GTX 550 Ti

ondoho · 02-03-2022, 04:01 AM

Duplicate/continuation of this: https://www.linuxquestions.org/quest...es-4175707161/

It seems they now switched From KDE to Cinnamon to MATE, still on the same install.

Why do you post screenshots instead of text? Is this a virtual machine?

pinguin20 · 02-03-2022, 08:11 AM

''It seems they now switched From KDE to Cinnamon to MATE, still on the same install''

No it didn't happen. During installation I chose KDE, and then after installation, I searched on the internet for Cinnamon and Mate desktops and I installed them via terminal

ondoho · 02-03-2022, 10:19 AM

Quote:

Originally Posted by pinguin20

No it didn't happen. During installation I chose KDE, and then after installation, I searched on the internet for Cinnamon and Mate desktops and I installed them via terminal

That's exactly what I meant.

pinguin20 · 02-03-2022, 10:41 AM

Quote:

Originally Posted by ondoho

That's exactly what I meant.

I don't know what are you trying to say, but this isn't' a virtual machine

ondoho · 02-03-2022, 11:02 AM

Quote:

Originally Posted by pinguin20

this isn't' a virtual machine

Then stop posting screenshots and copy-paste text instead. Use CODE blocks for command output, logs etc. (see my signature).

pinguin20 · 02-03-2022, 11:07 AM

Quote:

Originally Posted by ondoho

Then stop posting screenshots and copy-paste text instead. Use CODE blocks for command output, logs etc. (see my signature).

But these screenshots are about Yast Software Manager there is no way to copy package's name and paste here

computersavvy · 02-03-2022, 11:49 AM

Quote:

Originally Posted by pinguin20

But these screenshots are about Yast Software Manager there is no way to copy package's name and paste here

Not true.
Everything seen on the screen as text can be captured to a file by using tee, or can just be highlighted by the mouse and copy/pasted.
From the gui it can be highlighted by the mouse then copy/pasted. This is the case with rare exception in a gui screen.

To copy the entire text program output to a file (including error messages) simply use

Code:

<command> 2>&1 | tee <filename>

I have not used yast, so do not know if it is one of the exceptions, but you will not know until you try.

pinguin20 · 02-03-2022, 11:56 AM

Quote:

Originally Posted by computersavvy

Not true.
Everything seen on the screen as text can be captured to a file by using tee, or can just be highlighted by the mouse and copy/pasted.
From the gui it can be highlighted by the mouse then copy/pasted. This is the case with rare exception in a gui screen.

To copy the entire text program output to a file (including error messages) simply use

Code:

<command 2>&1 | tee <filename>

I have not used yast, so do not know if it is one of the exceptions, but you will not know until you try.

In my case ''filename'' would be Yast Software Manager?

boughtonp · 02-03-2022, 12:12 PM

The documentation for your OS is available here: https://doc.opensuse.org/

It took just a couple of clicks to go from there to 1.4 YaST command line options.

There is also a chapter on Managing software with command line tools, which is perhaps more useful.

(Also, inxi is a tool that makes providing diagnostic information nice and easy.)

pan64 · 02-03-2022, 12:30 PM

Quote:

Originally Posted by pinguin20

In my case ''filename'' would be Yast Software Manager?

definitely not. But it looks like you need to learn [at least] the basic usage of the command line environment. Not for us (or for me), but for yourself, to be able to maintain your own computer.

ondoho · 02-04-2022, 01:34 PM

Quote:

Originally Posted by pinguin20

But these screenshots are about Yast Software Manager there is no way to copy package's name and paste here

Well I would prefer if you would take the effort to properly describe your problem, and post the text part of the problem (I don't know Yast but e.g. synaptic has a dropdown with command output etc.).
Posting screenshots to imgur is low effort - and even if I wanted to put more effort into solving your problem than you, I can't because you are the only one who's in direct contact with the machine.
Maybe you'd like to read the first link in my signature.

mrmazda · 02-04-2022, 08:48 PM

What follows are some examples of commands for finding and installing software in openSUSE, and commands useful for providing troubleshooting information to those interested in helping to solve problems that may involve graphics issues:

Code:

# zypper se -s vidia
Loading repository data...
Reading installed packages...

S  | Name                   | Type    | Version         | Arch   | Repository
---+------------------------+---------+-----------------+--------+-----------
i+ | kernel-firmware-nvidia | package | 20210208-2.4    | noarch | OSS
   | nvidia-texture-tools   | package | 2.1.2-bp153.1.1 | x86_64 | OSS
   | pcp-pmda-nvidia-gpu    | package | 5.2.2-1.4       | x86_64 | OSS
# zypper -v in xf86-video-vesa xf86-video-fbdev xf86-video-nouveau xf86-input-libinput xorg-x11-server
...
The following 5 NEW packages are going to be installed:
  xf86-input-libinput  0.28.1-4.32
  xf86-video-fbdev     0.5.0-4.31
  xf86-video-nouveau   1.0.15-5.26
  xf86-video-vesa      2.4.0-3.31
  xorg-x11-server      1.20.3-22.5.42.1

5 new packages to install.
Overall download size: 1.7 MiB. Already cached: 0 B. After the operation, additional 5.9 MiB will be used.
Continue? [y/n/v/...? shows all options] (y): y
...
# rpm -qa | egrep 'ouveau|idia|Mesa|video|nel-def' | sort
Mesa-20.2.4-57.13.x86_64
Mesa-demo-x-8.3.0-1.33.x86_64
Mesa-dri-20.2.4-57.12.x86_64
Mesa-dri-nouveau-20.2.4-57.12.x86_64
Mesa-gallium-20.2.4-57.12.x86_64
Mesa-libEGL1-20.2.4-57.13.x86_64
Mesa-libGL1-20.2.4-57.13.x86_64
Mesa-libglapi0-20.2.4-57.13.x86_64
Mesa-libva-20.2.4-57.12.x86_64
kernel-default-5.3.18-59.27.1.x86_64
kernel-default-5.3.18-59.40.1.x86_64
kernel-default-extra-5.3.18-59.27.1.x86_64
kernel-default-extra-5.3.18-59.40.1.x86_64
kernel-firmware-nvidia-20210208-2.4.noarch
libXvMC_nouveau-20.2.4-57.12.x86_64
libdrm_nouveau2-2.4.104-1.12.x86_64
libvdpau_nouveau-20.2.4-57.12.x86_64
xf86-video-fbdev-0.5.0-4.31.x86_64
xf86-video-nouveau-1.0.15-5.26.x86_64
xf86-video-vesa-2.4.0-3.31.x86_64
# lsmod | egrep 'vidi|veau' | sort
button                 24576  1 nouveau
drm                   614400  5 drm_kms_helper,ttm,nouveau
drm_kms_helper        262144  1 nouveau
i2c_algo_bit           16384  1 nouveau
mxm_wmi                16384  1 nouveau
nouveau              2252800  2
ttm                   118784  1 nouveau
video                  53248  1 nouveau
wmi                    36864  2 mxm_wmi,nouveau
# grep onnect /var/log/Xorg.0.log
[    40.180] (II) modeset(0): Output DVI-I-1 connected
[    40.180] (II) modeset(0): Output HDMI-1 disconnected
[    40.180] (II) modeset(0): Output VGA-1 disconnected
# inxi -SMyz
System:
  Kernel: 5.3.18-59.40-default x86_64 bits: 64 Desktop: KDE 3.5.10
    Distro: openSUSE Leap 15.3
Machine:
  Type: Desktop System: HP-Pavilion product: RX900AA-ABA a6010n v: N/A
    serial: <filter>
  Mobo: ASUSTek model: LEONITE v: 5.00 serial: <filter> BIOS: Phoenix
    v: 5.10 date: 01/30/2007
# inxi -Gayz
Graphics:
  Device-1: NVIDIA GT218 [GeForce 210] vendor: eVga.com. driver: nouveau
    v: kernel bus-ID: 01:00.0 chip-ID: 10de:0a65 class-ID: 0300
  Display: x11 server: X.Org 1.20.3 driver: loaded: modesetting
    unloaded: fbdev,vesa alternate: nouveau,nv,nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 120 s-size: 541x304mm (21.3x12.0")
    s-diag: 621mm (24.4")
  Monitor-1: DVI-I-1 res: 2560x1440 hz: 60 dpi: 109
    size: 598x336mm (23.5x13.2") diag: 686mm (27")
  OpenGL: renderer: NVA8 v: 3.3 Mesa 20.2.4 direct render: Yes
# xrandr | egrep 'onnect|creen|\*' | grep -v disconn | sort -r
Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
DVI-I-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
   2560x1440     59.95*+

Instructions for the use of the commands in bold above following "#", which is part of the shell prompt employed when root is logged in, like most commands in Linux, are accessible via the man and/or info commands. e.g. man inxi, to learn about other switches for inxi, such as for RAM or HDDs & SSDs, and adding additional detail. Inxi even has one for updating itself, -U, needed by Leap users because its packagers don't keep it up to date. To use some of the commands above requires root access, which when not logged in as root may be available via the command prefix "sudo", which when used requires providing the root user password to enable execution of the command.