Not sure if anyone mentioned, but there doesn’t seem to be any linux510-virtualbox-host-modules in official repos and also the virtualbox-host-dkms fails to install for kernel 5.10.
No errors or warnings seen when the update was run using the GUI.
But i notice there is a /etc/default/grub.pacnew
It must have been generated by a previous update i guess (looking at the date), so i just remove it and keep current one.
(I don’t even use grub to boot, but instead use sd-boot )
--- /etc/default/grub 2020-11-23 08:57:34.697374551 +0300
+++ /etc/default/grub.pacnew 2020-11-13 00:06:56.000000000 +0300
@@ -1,14 +1,13 @@
GRUB_DEFAULT=saved
-GRUB_TIMEOUT=10
-#GRUB_TIMEOUT_STYLE=hidden
-GRUB_TIMEOUT_STYLE=menu
+GRUB_TIMEOUT=5
+GRUB_TIMEOUT_STYLE=hidden
GRUB_DISTRIBUTOR="Manjaro"
-GRUB_CMDLINE_LINUX_DEFAULT="quiet apparmor=1 security=apparmor udev.log_priority=3 sysrq_always_enabled=1"
+GRUB_CMDLINE_LINUX_DEFAULT="quiet udev.log_priority=3"
GRUB_CMDLINE_LINUX=""
# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
-#GRUB_SAVEDEFAULT="true"
+GRUB_SAVEDEFAULT=true
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
@@ -30,21 +29,21 @@
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
-# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
-# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
+# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
+# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
-# Uncomment and set to the desired menu colors. Used by normal and wallpaper
+# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
-GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"
+#GRUB_THEME="/path/to/gfxtheme"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
/reboot
(seems to have booted )
Notable changes i had to perform since a fresh install from the LiveUSB image before all these updates:
Related to keeping the system time in sync with my timezone: timedatectl set-ntp true
Related to configuring ethernet network using SystemD instead of NetworkManager in combination with using 👩🏫[HowTo] DNS based advertising filter using Bind9 : sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf systemctl enable --now systemd-resolved
Related to nVidia in combination with Suspend/Resume/Hibernate: systemctl enable nvidia-{suspend,resume,hibernate}
I am sorry but nvidia-persistanced is not what you think it is. It will keep nothing after reboot.
quote:
A Linux daemon utility, nvidia-persistenced , addresses an undesirable side effect of the NVIDIA kernel driver behavior in certain computing environments. Whenever the NVIDIA device resources are no longer in use, the NVIDIA kernel driver will tear down the device state. Normally, this is the intended behavior of the device driver, but for some applications, the latencies incurred by repetitive device initialization can significantly impact performance.
To avoid this behavior, nvidia-persistenced provides a configuration option called “persistence mode” that can be set by NVIDIA management software, such as nvidia-smi . When persistence mode is enabled, the daemon holds the NVIDIA character device files open, preventing the NVIDIA kernel driver from tearing down device state when no other process is using the device. This utility does not actually use any device resources itself - it will simply sleep while maintaining a reference to the NVIDIA device state.
So if you have more than one Nvidia card in your system it is OK yo use it and latency is a problem.
May be it will be more useful to use nvidia-suspend.service, nvidia-resume.service, to save RAM of the card in Susepnd/Resume, but not reboot.
Thank you all envolved very much ! This was very nice and smooth update / upgrade for stable gnome! At first just accept new automatic packages from Pamac and then install new kernel 5.9.10-1 from Manjaro Settings Manager → reboot and that’s it !
One of the previous updates enabled the “pop sholl extension” and gave me the behavior you describe.
Perhaps your issue is caused by that extension being enabled by the update?
I am still suffering from the issue with QT5 apps on gnome not showing dialogs. I digged deeper on the cause and the maintainer supplied a fix in commit:
How can I help to get this commit included in the next (un)stable/testing release?
qgnomeplatform is currently at version 0.6.90+3+gd5a01ea-1
One question: 1. Where can I find a list of manjaro packages and their dependencies ?? like there is for arch
I have one orphan package software-center-web-jak(Install Software from Manjaro discover service). Do I remove it or what ?? That’s way I want to see list of packages.
After this update(KDE, kenerl from 5.8 to 5.9.8-2), optimus manager can’t change to hybrid mode or Nvidia mode. Thought some thing wrong with Nvidia driver, what should I do? Currently I can’t change the lightness and can’t light up my second screen which may due to this problem.