When using Nvidia 495 and Plasma 5.23+, the plasma shell (kwin?) doesn’t graphically update unless I move my mouse around, anyone else? Can’t figure out if this is a bug I should report to KDE or not.
I don’t have that issue and I have 495 nvidia and 5.23.2,maybe you are in Wayland?
Yes, forgot to mention that, sorry. I’ve gotten too accustomed to Wayland as my daily driver it seems.
I’m mostly curious if it’s just on my machine or something everyone/others are experiencing 
I couldn’t get the same to happen in an Arch VM but obviously that’s a bit different when it comes to rendering graphics.
You seem to have KDE+Nvidia+Wayland so to me that’s the death combo. Your VM is totaly different setup. You can’t compare it.
Well we added now 470.82.00. Let’s see how it works.
5 Likes
3 posts were split to a new topic: Package information is present in db, but the package itself is absent on the servers
Are you reporting a bug or requesting a feature? Please open a new thread.
It’s just a question, since 495.44 drivers has a bug, that’s for Nvidia to fix. What I linked was just a workaround to stop the logs from filling up with dbus warnings. Not sure if it prevents dbus-daemon from bloating up. Mine got to over 500 MiB at its worst.
2 Likes
Hi, I noticed that there is a GPU hang regression on the Kernel 5.10.77
Arch Linux have already a patch for this:
1 Like
Thanks a lot!
Is fixed upstream already:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/ttm/ttm_bo_util.c?h=v5.10.77&id=c21b4002214c1c7e7b627b9b53375612f7aab6db
2 Likes
Well the fix introduced a regression so they reverted it at Arch… I’ve you look at stable-queue.git you will find more reverts reported by Fedora and Arch.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.10
Other kernel series might be affected too…
1 Like
Yup, have checked that so next Kernel Series should be fine.
Update to kernel 5.15.1-1 has rendered Virtualbox unable to launch a guest OS. sudo vboxreload did not fix the issue either. (That command threw up another error)It was the message that the drivers were not installed or installed incorrectly etc… It is working fine with 5.10 kernel. For some reason the update ( pacman via TTY) did not pick up the linux515-virtualbox-host-modules update. I had to update manually.
The following is from pamac history:
[2021-11-06T16:18:31-0400] [ALPM] installed linux515-virtualbox-host-modules (6.1.28-3)
[2021-11-06T16:06:22-0400] [ALPM] upgraded linux515-headers (5.15.0-2 -> 5.15.1-1)
[2021-11-06T16:06:20-0400] [ALPM] upgraded linux515 (5.15.0-2 -> 5.15.1-1)
[2021-11-06T16:06:12-0400] [ALPM] upgraded linux510-virtualbox-host-modules (6.1.28-3 -> 6.1.28-4)
[2021-11-06T16:06:12-0400] [ALPM] upgraded linux510-headers (5.10.77-1 -> 5.10.78-1)
[2021-11-06T16:06:09-0400] [ALPM] upgraded linux510 (5.10.77-1 -> 5.10.78-1)
[2021-11-06T16:06:07-0400] [ALPM] upgraded foomatic-db (3:20211009-1 -> 3:20211106-1)
[2021-11-06T16:06:06-0400] [ALPM] upgraded fmt (8.0.1-1 -> 8.0.1-2)
[2021-11-06T16:06:06-0400] [ALPM] upgraded ffmpeg (2:4.4-6 -> 2:4.4.1-1)
sudo vboxreload
[sudo] password for jrichard:
Unloading modules:
Loading modules: modprobe: ERROR: could not insert 'vboxnetadp': Exec format error
modprobe: ERROR: could not insert 'vboxnetflt': Exec format error
modprobe: ERROR: could not insert 'vboxdrv': Exec format error
edit: FIXED with update to 6.128-4 and sudo vboxreload.
Thank you for the quick fix.
Magic number mismatch again. Between kernel 5.15.1-1 and linux515-nvidia-470xx 470.82.00-2.
Looking at Branch Compare, a new revision of Nvidia package hasn’t been built? Mirror list refresh didn’t bring it up, at least.
Edit: More precisely kernel: nvidia: version magic '5.15.0-2-MANJARO SMP preempt mod_unload ' should be '5.15.1-1-MANJARO SMP preempt mod_unload '
Fixed! Thanks, @oberon !
System: Gnome unstable / B550 Board / MSI RX5500 8GB / Ryzen 7 3700X /
(only with:) Kernel 5.15.1-1
Warning in systemd.log:
.....
kernel: ata3.00: Read log page 0x08 failed, Emask 0x1
kernel: ata3.00: Read log page 0x08 failed, Emask 0x1
.....
Solution taken from:
https://askubuntu.com/questions/1060245/what-do-these-ata-error-messages-mean
==> add to: GRUB_CMDLINE_LINUX_DEFAULT new entry: “libata.force=noncq”
EDIT: please look for:
2-EDIT: problem has gone with kernl-version 5.15.2-2
2 Likes
There’s an nvidia-fake-powerd package in the AUR now, built from those instructions.
I think it should go without saying, but use at your own discretion! Used with 495xx drivers.
Nvidia GT730 Geforce not longer working after update (unstable) 07.11.2021.
Error: “Driver doesnot support your GT730”
SOLUTION:
in GRUB press “E” and add to bootoptions: 3 nomodeset
Boot (F10) => login prompt => login and type:
sudo mhwd -r pci $(mhwd -li |grep 'video-' | awk '{print $1}')
sudo mhwd -a pci free 0300
reboot…
(Nvidia-driver replaced by opensource-driver)
1 Like
Or install the new Nvidia driver package made for the occasion (The previous driver)?
mhwd -l