[Stable Update] 2020-12-30 - Kernels, KDE, Cinnamon, LibreOffice, Python 3.9, Mesa 20.3.1

Jaspa - I had exactly the same problem at first. Installing the -dkms package didn’t enable wifi, and I tried to get it working by re-installing broadcom-wl - without success. However, I eventually came across the post from r4jk3 - which included the direction to update the headers. Their post included the command language you quoted in your question.

So, I updated the headers first, re-installed the -dkms package (which automatically removes the broadcom-wl package as conflicting), and then, after the second installation of broadcom-wl-dkms, it worked.

I actually found those directions for updating the headers in Manjaro much easier to follow:

https://linuxconfig.org/manjaro-linux-kernel-headers-installation

I hope this helps. Frankly, I had a lot of trial and error before wifi worked again. For me, it looks like updating the headers before installing the -dkms package was the key.

1 Like

Thank you it worked!! :grinning:
As you’ve described, I first updated the headers for my kernel using the tutorial you found, rebooted, re-installed broadcom-wl-dkms and rebooted again and voilà. I still don’t understand what headers exactly are for, but it did the trick. Thanks again.

1 Like

My rolling release of Manjaro updated 4 days ago to Kernel 5.9.16-1 (And welcomed me, with a blackscreen, 1 month ago there was another nvidia bug because of the dropped support from 440.xx and lower, thats the second update that i have to manually reinstall the nvidia drivers per TTY in 1 month!).

I dont get it why this 5.9 Kernel is marked as EOL already? And why is 5.10 not marked as recommended in Manjaro Settings Manager? Why is my rolling release from manjaro automatic updated to a EOL Kernel instead going straight to 5.10?

Because 5.10 is out. That’s how it normally works. See https://www.kernel.org/

Because it was found it was the most stable when building the newest ISOs. 5.10 just barely came out. Sometimes there are still a few quirks to iron out in the first few point releases. FYI, 5.10 just barely made it out of the Arch Testing phase.

3 Likes

I need driver 430xx max and after how much drama my laptop is with GPU driver changes I got scared to death when I booted my laptop this morning. But, got it working again with the fix for rolling back on 430xx. I had posted about it here Update broke nvidia, can't boot but I found out I should have read the sticky post better as the solution is literally what’s at the bottom there.

@Philm I think you missed a “pci” in one of your mhwd commands (at the" install the driver first" under the " If proprietary drivers don’t fix everything, please click the ► at the beginning of this line to view more info"). I think “mhwd --install video-hybrid-XXX-nvidia-prime” should be “mhwd --install pci video-hybrid-XXX-nvidia-prime”. Otherwise you get an error you’re using --install/-i wrong (at least I did when I typed it earlier :sweat_smile:)

I’m in the process of updating and on one machine I have this after the update, which went completely fine without additional commands:

Some shell-commands with output
$ inxi -G --display
Graphics:
  Device-1: NVIDIA GK208B [GeForce GT 710] driver: nvidia v: 455.45.01 
  Display: x11 server: X.Org 1.20.10 driver: nvidia s-res: 1280x1024 
  OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 455.45.01 
$ mhwd -l
> 0000:03:00.0 (0200:10ec:8168) Network controller Realtek Semiconductor Co., Ltd.:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
         network-r8168            2016.04.20                true            PCI


> 0000:01:00.0 (0300:10de:128b) Display controller nVidia Corporation:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
    video-nvidia-390xx            2020.11.30               false            PCI
           video-linux            2018.05.04                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI
$ mhwd -li
> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
          video-nvidia            2020.11.30               false            PCI


Warning: No installed USB configs!
$ pacman -Qe | grep nvidia
linux419-nvidia 455.45.01-4
linux54-nvidia 455.45.01-6
nvidia-utils 455.45.01-2

I’m totally confused what’s installed and used here:

  • GT 710 graphics card available (this is true)
  • the available configuration is video-nvidia-390xx
  • video-nvidia is installed
  • packages for 455xx are installed

Uhm, what?! The current status is that X, lightdm and XFCE start and graphics look fine so basically I shouldn’t complain, but the above just doesn’t make sense to me.

  • where does video-nvidia-390xx come from?
  • how do I remove video-nvidia-390xx? (I assume it has no use here)
  • why doesn’t it say video-nvidia-455xx?
  • is video-nvidia the official representation of video-nvidia-455xx? (I hope it isn’t as the version number would be interesting to see IMHO)

Can anyone please explain this to me? Maybe something is broken here?

It’s also compatible with the GPU.

It’s not installed.

The names have been changed.

video-nvidia always refers to the latest driver, 455.45.01 at the moment.


I believe if you reinstall the mhwd-db package, then video-nvidia should appear in the list of compatible configurations.

Yep, I reinstalled it and now see this:

$ mhwd -l
...
> 0000:01:00.0 (0300:10de:128b) Display controller nVidia Corporation:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
          video-nvidia            2020.11.30               false            PCI
    video-nvidia-390xx            2020.11.30               false            PCI
           video-linux            2018.05.04                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI

But, also this!

$ mhwd -li
Warning: No installed PCI configs!
Warning: No installed USB configs!

Should I reboot now to make it work? Or do I need to install video-nvidia first?

Interesting, I suggest installing video-nvidia, and not rebooting until that’s done.

OK, after mhwd -i pci video-nvidia it’s back in the list. After a reboot it looks as expected, but this has changed:

$ pacman -Qe | grep nvidia
lib32-nvidia-utils 455.45.01-3
linux419-nvidia 455.45.01-4
linux54-nvidia 455.45.01-6
nvidia-utils 455.45.01-2

So lib32-nvidia-utils was added, no idea why that was missing beforehand.

Thanks :slight_smile:

Edit:

Same thing happened on another PC, fixed the same. So the “interesting” part might actually be a normal case.

3 posts were split to a new topic: Checkrebuild reporting same packages after rebuilding

Sorry for the late reply

System:
  Kernel: 5.10.2-2-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64 
  root=UUID=c54a3f3c-0a78-4457-a868-72023734becd rw quiet apparmor=1 
  security=apparmor udev.log_priority=3 
  Desktop: Xfce 4.14.3 tk: Gtk 3.24.23 info: xfce4-panel wm: xfwm4 
  dm: LightDM 1.30.0 Distro: Manjaro Linux 
Machine:
  Type: Desktop Mobo: Gigabyte model: X570 GAMING X v: x.x serial: <filter> 
  UEFI: American Megatrends v: F30 date: 09/15/2020 
CPU:
  Info: 12-Core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 2 
  family: 17 (23) model-id: 71 (113) stepping: N/A microcode: 8701021 
  L2 cache: 6 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 182130 
  Speed: 4132 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 
  1: 4132 2: 4131 3: 4126 4: 4125 5: 4130 6: 4130 7: 4131 8: 4135 9: 4135 
  10: 4135 11: 4137 12: 4110 13: 4132 14: 4123 15: 4118 16: 4142 17: 4117 
  18: 4134 19: 4135 20: 4135 21: 4133 22: 4131 23: 4132 24: 4126 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: 
  conditional, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] 
  vendor: ASRock driver: amdgpu v: kernel bus ID: 0b:00.0 chip ID: 1002:731f 
  Display: x11 server: X.Org 1.20.10 driver: amdgpu,ati 
  unloaded: modesetting,radeon alternate: fbdev,vesa display ID: :0.0 
  screens: 1 
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3") 
  s-diag: 583mm (23") 
  OpenGL: renderer: AMD Radeon RX 5700 XT (NAVI10 DRM 3.40.0 5.10.2-2-MANJARO 
  LLVM 11.0.0) 
  v: 4.6 Mesa 20.3.1 direct render: Yes 
Audio:
  Device-1: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel 
  bus ID: 0b:00.1 chip ID: 1002:ab38 
  Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus ID: 0d:00.4 chip ID: 1022:1487 
  Device-3: webcam type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-1:2 
  chip ID: 1d6c:0103 
  Device-4: GN Netcom Jabra EVOLVE 20 type: USB 
  driver: jabra,snd-usb-audio,usbhid bus ID: 5-2:3 chip ID: 0b0e:0301 
  serial: <filter> 
  Sound Server: ALSA v: k5.10.2-2-MANJARO 
Network:
  Device-1: Realtek RTL8125 2.5GbE driver: N/A modules: r8169 port: e000 
  bus ID: 04:00.0 chip ID: 10ec:8125 
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Gigabyte driver: r8168 v: 8.048.03-NAPI modules: r8169 port: d000 
  bus ID: 05:00.0 chip ID: 10ec:8168 
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  IF-ID-1: virbr0 state: down mac: <filter> 
  IF-ID-2: virbr0-nic state: down mac: <filter> 
Drives:
  Local Storage: total: 476.94 GiB used: 123.16 GiB (25.8%) 
  SMART Message: Required tool smartctl not installed. Check --recommends 
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: OM8PCP3512F-AB 
  size: 476.94 GiB block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s 
  lanes: 4 serial: <filter> rev: ECFK52.3 temp: 30.9 C 
Partition:
  ID-1: / raw size: 476.64 GiB size: 468.16 GiB (98.22%) 
  used: 123.16 GiB (26.3%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2 
  ID-2: /boot/efi raw size: 300 MiB size: 299.4 MiB (99.80%) 
  used: 312 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 
Swap:
  Alert: No Swap data was found. 
Sensors:
  System Temperatures: cpu: 70.5 C mobo: 16.8 C gpu: amdgpu temp: 31.0 C 
  mem: 34.0 C 
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 0 
Info:
  Processes: 414 Uptime: 1d 11h 22m wakeups: 0 Memory: 31.37 GiB 
  used: 5.35 GiB (17.1%) Init: systemd v: 247 Compilers: gcc: 10.2.0 Packages: 
  pacman: 1489 lib: 424 flatpak: 0 Shell: Bash v: 5.1.0 running in: alacritty 
  inxi: 3.2.01 

Hope this helps

Tony

And I found the culprit! It’s Mesa, I installed another distro (kde neon, to salvage my data) and today I got a round of Mesa updates and guess what? The same freakin bug! Only mouse cursor and black background .

So I guess most of the gpu related issues may come from a botched Mesa release.

1 Like

well after a lot recurring crashes, I found that this line always repeats itself…

and after googling those drm:gfx errors it seems like a “know” problem with GPU drivers called by Mesa. Did anybody else experience this kind of crash?

@Enigmaxg2
may I ask if you do have something alike my drm:gfx or drm:amdgpu… in your logs? Maybe we are on the same boat with our Mesa related crahes??..??

Jan 06 21:19:48 x570 kernel: [drm:gfx_v9_0_priv_reg_irq [amdgpu]] *ERROR* Illegal register access in command stream
Jan 06 21:19:48 x570 kernel: audit: type=1701 audit(1609964388.923:238): auid=1000 uid=1000 gid=1000 ses=2 subj==unconfined pid=78428 comm="vlc" exe="/usr/bin>
Jan 06 21:19:48 x570 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=8769987, emitted seq=8769988
Jan 06 21:19:48 x570 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process vlc pid 78428 thread vlc:cs0 pid 78495
Jan 06 21:19:48 x570 kernel: amdgpu 0000:08:00.0: amdgpu: GPU reset begin!
Jan 06 21:19:48 x570 audit: BPF prog-id=26 op=LOAD
Jan 06 21:19:48 x570 audit: BPF prog-id=27 op=LOAD

my specs are:

CPU:
  Info: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64
  type: MT MCP arch: Zen/Zen+ note: check family: 17 (23) model-id: 18 (24)
  stepping: 1 microcode: 8108109 L2 cache: 2 MiB
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  bogomips: 59116
  Speed: 1271 MHz min/max: 1400/3700 MHz boost: enabled Core speeds (MHz):
  1: 1271 2: 1829 3: 1272 4: 2852 5: 1272 6: 2124 7: 1274 8: 2928
  Vulnerabilities: Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: spec_store_bypass
  mitigation: Speculative Store Bypass disabled via prctl and seccomp
  Type: spectre_v1
  mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP:
  disabled, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Picasso driver: amdgpu v: kernel bus ID: 08:00.0
  chip ID: 1002:15d8
  Display: x11 server: X.Org 1.20.10 driver: amdgpu,ati unloaded: modesetting
  alternate: fbdev,vesa display ID: :0.0 screens: 1
  Screen-1: 0 s-res: 5520x2160 s-dpi: 96 s-size: 1460x571mm (57.5x22.5")
  s-diag: 1568mm (61.7")
  Monitor-1: DisplayPort-0 res: 3840x2160 hz: 60 dpi: 140
  size: 697x392mm (27.4x15.4") diag: 800mm (31.5")
  Monitor-2: HDMI-A-0 res: 1680x1050 hz: 60 dpi: 90
  size: 474x296mm (18.7x11.7") diag: 559mm (22")
  OpenGL: renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.39.0
  5.9.16-1-MANJARO LLVM 11.0.0)
  v: 4.6 Mesa 20.3.1 direct render: Yes

After this update, Firefox has a weird problem. It does not show any space between words in tab titles, popup menus and even in the text of the preference pages. Also, typing a search item in the address bar does not show spaces although after hitting enter, the spaces show up in duckduckgo search engine.
Any idea?
[edit] Here are some details of my laptop:

Install the linux-latest dummy package and your will always rollover to the newest stable kernel. Linux latest is currently at 5.10-1

1 Like

Now a day later I’m a bit confused on how to proceed. It asks me to update “manjaro-release” to 20.2-1 (despite that already being current version) telling me that the lib32, lib32 utils, mhwd and opencl from Nvidia driver 455.45.01 have to be retrieved (this is the only thing it lists). Is it save to update these packages (knowing I have to stay at 430xx), do I have to update the manjaro-release package and rollback the drivers to 430xx or should I ignore the update?

And if I need to keep it this way, how can I avoid having to roll back my drivers after every future update? For every kernel update it was mentioned, that’s ok. But for every normal update would be a pain in the ass often. Can I put the manjaro-release package in pacmans ignore list or will it also contain other things with future updates?

Everything seemed OK for a couple of days, however today I ran into this bug :

Dolphin & Krusader crash when selecting “Apply to All” in “Folder Already Exists” prompt.

Terminal output after crash: Segmentation fault (core dumped)

At the boot, I’m getting the “Failed to start Network Manager”, “Dependency failed for Network Manager Wait Online”, “Failed to start User Login Management”, “Failed to start Load Kernel Module drm.”
I’ve been updating the Manjaro on regular basis.

https://bugs.kde.org/show_bug.cgi?id=430374

1 Like