Visual bug wont go away very annoying

I was looking something up and saw this

System:
  Kernel: 6.1.12-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
    root=UUID=f057ab0b-fbae-4962-b6a1-c852b0ec828d rw quiet splash
    udev.log_priority=3
  Desktop: KDE Plasma v: 5.26.5 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: Dell product: Latitude E6510 v: 0001
    serial: <superuser required> Chassis: type: 9 serial: <superuser required>
  Mobo: Dell model: 0N5KHN v: A02 serial: <superuser required> BIOS: Dell
    v: A17 date: 05/12/2017
Battery:
  ID-1: BAT0 charge: 52.8 Wh (100.0%) condition: 52.8/57.7 Wh (91.5%)
    volts: 12.5 min: 11.1 model: Samsung SDI DELL PT43696 type: Li-ion
    serial: <filter> status: full
Memory:
  RAM: total: 15.56 GiB used: 10.93 GiB (70.2%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i7 Q 720 bits: 64 type: MT MCP arch: Nehalem
    gen: core 1 level: v2 built: 2008-10 process: Intel 45nm family: 6
    model-id: 0x1E (30) stepping: 5 microcode: 0xA
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 1786 high: 2688 min/max: 933/1600 boost: enabled scaling:
    driver: acpi-cpufreq governor: schedutil cores: 1: 2291 2: 2113 3: 2688
    4: 2168 5: 933 6: 933 7: 2229 8: 933 bogomips: 25550
  Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc
    cpuid cx16 cx8 de ds_cpl dtes64 dtherm dts ept est flexpriority flush_l1d
    fpu fxsr ht ibpb ibrs ida lahf_lm lm mca mce mmx monitor msr mtrr
    nonstop_tsc nopl nx pae pat pbe pdcm pebs pge pni popcnt pse pse36 pti
    rdtscp rep_good sep smx ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm
    tm2 tpr_shadow tsc vme vmx vnmi vpid xtopology xtpr
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode;
    SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: retbleed status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: conditional, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GT218M [NVS 3100M] vendor: Dell Latitude E6510
    driver: nouveau v: kernel non-free: series: 340.xx status: legacy (EOL) last:
    release: 340.108 kernel: 5.4 xorg: 1.20 arch: Tesla process: 40-80nm
    built: 2006-13 pcie: gen: 2 speed: 5 GT/s lanes: 16 ports:
    active: DP-1,VGA-1 off: eDP-1 empty: DP-2 bus-ID: 01:00.0
    chip-ID: 10de:0a6c class-ID: 0300 temp: 72.0 C
  Device-2: Ricoh HD Webcam type: USB driver: uvcvideo bus-ID: 1-1.4:5
    chip-ID: 05ca:1814 class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.7 compositor: kwin_x11 driver: X:
    loaded: modesetting alternate: fbdev,vesa dri: nouveau gpu: nouveau
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3600x1080 s-dpi: 96 s-size: 950x285mm (37.40x11.22")
    s-diag: 992mm (39.05")
  Monitor-1: DP-1 pos: right model: BenQ G2200W serial: <filter> built: 2009
    res: 1680x1050 dpi: 90 gamma: 1.2 size: 474x296mm (18.66x11.65")
    diag: 559mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400
  Monitor-2: VGA-1 pos: primary,left model: Dell P2311H serial: <filter>
    built: 2010 res: 1920x1080 hz: 60 dpi: 96 gamma: 1.2
    size: 509x286mm (20.04x11.26") diag: 584mm (23") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  Monitor-3: eDP-1 note: disabled model: LG Display built: 2009
    res: 1920x1080 dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64")
    diag: 395mm (15.5") ratio: 16:9 modes: max: 1920x1080 min: 800x600
  API: OpenGL v: 3.3 Mesa 22.3.5 renderer: NVA8 direct-render: Yes
Audio:
  Device-1: Intel 5 Series/3400 Series High Definition Audio
    vendor: Dell Latitude E6510 driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:3b56 class-ID: 0403
  Device-2: NVIDIA High Definition Audio vendor: Dell Latitude E6510
    driver: snd_hda_intel v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:0be3 class-ID: 0403
  Sound API: ALSA v: k6.1.12-1-MANJARO running: yes
  Sound Interface: sndio v: N/A running: no
  Sound Server-1: JACK v: 1.9.22 running: no
  Sound Server-2: PulseAudio v: 16.1 running: yes
  Sound Server-3: PipeWire v: 0.3.65 running: yes
Network:
  Device-1: Intel 82577LM Gigabit Network vendor: Dell Latitude E6510
    driver: e1000e v: kernel port: 8040 bus-ID: 00:19.0 chip-ID: 8086:10ea
    class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:422c
    class-ID: 0280
  IF: wlp3s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Device-3: Dell F3607gw v2 Mobile Broadband Module type: USB
    driver: cdc_acm,cdc_ether,cdc_wdm bus-ID: 2-1.6:3 chip-ID: 413c:8184
    class-ID: 0202 serial: <filter>
  IF: wwp0s29u1u6i6 state: down mac: <filter>
  WAN IP: <filter>
Bluetooth:
  Device-1: Dell DW375 Bluetooth Module type: USB driver: btusb v: 0.8
    bus-ID: 2-1.7:4 chip-ID: 413c:8187 class-ID: fe01 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
    v: 3.0 port: 8020 bus-ID: 00:1f.2 chip-ID: 8086:282a rev: N/A class-ID: 0104
Drives:
  Local Storage: total: 119.24 GiB used: 17.01 GiB (14.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD PM800 2.5 128GB
    size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
    type: SSD serial: <filter> rev: 5D1Q scheme: MBR
  Optical-1: /dev/sr0 vendor: Optiarc model: DVD+-RW AD-7930H rev: 100A
    dev-links: cdrom
  Features: speed: 24 multisession: yes audio: yes dvd: yes
    rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
  ID-1: / raw-size: 119.24 GiB size: 116.81 GiB (97.96%)
    used: 17.01 GiB (14.6%) fs: ext4 dev: /dev/sda1 maj-min: 8:1 label: N/A
    uuid: f057ab0b-fbae-4962-b6a1-c852b0ec828d
Swap:
  Alert: No swap data was found.
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: Full speed or root hub ports: 3 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
    speed: 480 Mb/s chip-ID: 8087:0020 class-ID: 0900
  Hub-3: 1-1.1:3 info: Dell internal USB Hub of E-Port Replicator ports: 3
    rev: 2.0 speed: 480 Mb/s power: 2mA chip-ID: 413c:2513 class-ID: 0900
  Hub-4: 1-1.2:4 info: Dell internal USB Hub of E-Port Replicator ports: 3
    rev: 2.0 speed: 480 Mb/s power: 2mA chip-ID: 413c:2513 class-ID: 0900
  Device-1: 1-1.2.1:6 info: Holtek Keyboard type: Keyboard,HID
    driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s power: 100mA
    chip-ID: 04d9:a096 class-ID: 0300
  Device-2: 1-1.2.2:7 info: Logitech Mouse type: Mouse
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 1.5 Mb/s
    power: 100mA chip-ID: 046d:c077 class-ID: 0301
  Device-3: 1-1.4:5 info: Ricoh HD Webcam type: Video driver: uvcvideo
    interfaces: 2 rev: 2.0 speed: 480 Mb/s power: 200mA chip-ID: 05ca:1814
    class-ID: 0e02
  Hub-5: 2-0:1 info: Full speed or root hub ports: 3 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-6: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0
    speed: 480 Mb/s chip-ID: 8087:0020 class-ID: 0900
  Device-1: 2-1.6:3 info: Dell F3607gw v2 Mobile Broadband Module
    type: Communication,Abstract (modem),CDC-Data,Mobile Direct Line
    driver: cdc_acm,cdc_ether,cdc_wdm interfaces: 11 rev: 2.0 speed: 480 Mb/s
    power: 20mA chip-ID: 413c:8184 class-ID: 0202 serial: <filter>
  Device-2: 2-1.7:4 info: Dell DW375 Bluetooth Module type: Bluetooth
    driver: btusb interfaces: 4 rev: 2.0 speed: 12 Mb/s power: 100mA
    chip-ID: 413c:8187 class-ID: fe01 serial: <filter>
  Device-3: 2-1.8:5 info: Broadcom BCM5880 Secure Applications Processor
    with fingerprint swipe sensor type: Smart Card driver: N/A interfaces: 2
    rev: 1.1 speed: 12 Mb/s power: 100mA chip-ID: 0a5c:5801 class-ID: 0b00
    serial: <filter>
Sensors:
  System Temperatures: cpu: 77.0 C mobo: N/A sodimm: SODIMM C gpu: nouveau
    temp: 72.0 C
  Fan Speeds (RPM): cpu: 3594
Info:
  Processes: 238 Uptime: 6h 10m wakeups: 1 Init: systemd v: 252
  default: graphical tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7
  Packages: 1203 pm: pacman pkgs: 1199 libs: 330 tools: pamac,yay pm: flatpak
  pkgs: 4 Shell: Bash v: 5.1.16 running-in: konsole inxi: 3.3.25

Can you try to create another new user to see if it reproduces the same issue?

Sorry for the quilety but its even worse on a new user

It looks like an issue with the Nvidia driver.

When did this issue first appear? After the update of the stable branch?

It was there allways but its getting on my nerfs now

I strongly suspect a problem with the nouveau driver. Have you tried the proprietary driver? Maybe as a debugging step, try booting from a live usb, and try both free and non free drivers and see if either has the problem. It looks like the nvidia chip is from 2007, nouveau might not be as reliable on older hardware if its not tested as much.

Found this after i coulnd find one NVIDIA GT218M / NVS 3100M: notification warning Software Renderer in Use - #4 by Fabby
Also found this but idk which one to choose https://catalog.update.microsoft.com/Search.aspx?q=nvidia+nvs+3100m

Are you really asking which WINDOWS driver to chose for install? You’re using Manjaro, a LINUX based system, so NO WINDOWS driver can work obviously. Also, you do NOT install external packages not provided by your distribution (Manjaro), especially if you do not really know what you’re doing, or else you’re getting into trouble. Always use the systems in place to update/install things, provided by Manjaro.

Give the output of command mhwd -l

//EDIT: waiting for your reply, I searched a little bit, and you may be supported only by the previous Legacy v340 driver, that Manjaro doesn’t ship anymore. However it may be possible to still install it, but it involves manual installation of foreign packages (the exact thing I said earlier you shouldn’t do, when you’re not very tech-savy and don’t really know your way around solving potential issues, or non bootable system).

Idk how to install drivers on linux i am quit new as you already noticed.
Output:

0000:01:00.0 (0300:10de:0a6c) Display controller nVidia Corporation:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2018.05.04                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI

OK that confirms what I was almost sure already: Manjaro doesn’t provide a compatible Nvidia proprietary driver for your video card.

As I said, there might still be a possibility of installing foreign packages not provided by Manjaro, and have the old Nvidia v340 driver that is apparently compatible with your GPU.

If you would like to go that route, I would agree to help and guide you (to the extent of my knowledge and capabilities). But first we would need to have some bases in place:

  • you need a Manjaro live USB installer ready in case things go terribly wrong and we can’t work from the real system (we can always work on the real system then from the live USB)
  • you need to have a system snapshot in place (with TimeShift application for example), and making sure you know how it works, how you can use it to create snapshots and how to restore your system to a working state from the real system (from a TTY for example if it is not fully broken) or from the live USB

If you wish to go that route, we can work towards that and eventually try to install these old legacy drivers.

2 Likes

What would i have from having the right driver other then the text in the system manger not being mest up

The proper performance/features of the GPU. I don’t know the GPU so maybe it would have same performance as with the Nouveau free driver.

Ill hold of for now ty tho. :slight_smile:

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.