Ok, I am not exactly sure how, but after running the update yesterday after the software manager notified me of a number of updated packages, my system tried to come back up using the real time kernel, which basically caused all kinds of booting issues. I was using 5.15 LTS when performing the update, so is there any way to determine why my system was using the real time kernel after the update? This was on a machine installed at 21.3.5 and only a week or two old, so really had no history with any previous kernels.
I had to manually uninstall the kernel and manually install 5.18.14 afterwards. I also uninstalled virtualbox as the “watchdog: BUG soft lockup” error seemed to indicate issues with “vboxdrv(0E+”, but noticed when manually installing 5.18.14 that the software manager added virtuabox elements back again, although my software manager doesn’t show any at this point.
All in all a pretty confusing upgrade for a semi-knowledgeable user.
So this particular install is my first Manjaro experience, having come from using Garuda for the last 6+ months. I installed a few weeks ago from the available .iso and updated when notified. I know 5.15 LTS was the version I was running yesterday, and I haven’t touched one button in that section of the system manager. If I did anything to cause this, I have no recollection of doing that.
Based on your idea, I wonder if I didn’t add the RT kernel as an option during the initial install, and didn’t realize the ramification of doing so. Is there an option during the live installer to choose the RT kernel?
( 9/19) Install DKMS modules
==> dkms install --no-depmod v4l2loopback/0.12.5 -k 5.15.55-1-rt48-MANJARO
Deprecated feature: REMAKE_INITRD
Error! Bad return status for module build on kernel: 5.15.55-1-rt48-MANJARO (x86_64)
Consult /var/lib/dkms/v4l2loopback/0.12.5/build/make.log for more information.
==> WARNING: `dkms install --no-depmod v4l2loopback/0.12.5 -k 5.15.55-1-rt48-MANJARO' exited 10
the make.log shows
DKMS make.log for v4l2loopback-0.12.5 for kernel 5.15.55-1-rt48-MANJARO (x86_64)
dom 31 jul 2022 00:31:17 -04
Building v4l2-loopback driver...
make -C /usr/lib/modules/5.15.55-1-rt48-MANJARO/build M=/var/lib/dkms/v4l2loopback/0.12.5/buil
d modules
make[1]: se entra en el directorio '/usr/lib/modules/5.15.55-1-rt48-MANJARO/build'
CC [M] /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.o
cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
make[2]: *** [scripts/Makefile.build:288: /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback
.o] Error 1
make[1]: *** [Makefile:1886: /var/lib/dkms/v4l2loopback/0.12.5/build] Error 2
make[1]: se sale del directorio '/usr/lib/modules/5.15.55-1-rt48-MANJARO/build'
make: *** [Makefile:43: v4l2loopback.ko] Error 2
I’m using a laptop (Asus Tuf A17 2022 w/ nvidia dGPU), and the backlight of the display panel is always off after this update using kernel 5.15, the 5.10 is fine.
I can enter lockscreen password, but it just goes back to suspend after I hit enter. After which, the lockscreen is completely unresponsive (recognizes no keyboard / mouse inputs), and the only way I can get back in is with a reboot.
Used Timeshift to restore to before update and no longer have the issue.
element-desktop starts up and after few seconds (~37s) crashes with core dump.
[me@computer ~]$ element-deskto
/home/me/.config/Element exists: no
/home/me/.config/Riot exists: yes
Using legacy user data path: /home/me/.config/Riot
No update_base_url is defined: auto update is disabled
Fetching translation json for locale: en_EN
Changing application language to en-us
Fetching translation json for locale: en-us
Resetting the UI components after locale change
Resetting the UI components after locale change
Changing application language to en-us
Fetching translation json for locale: en-us
Resetting the UI components after locale change
Trace/breakpoint trap (core dumped)
Downgrading element-desktop and element-web to previous version (1.11.0-1) seems to fix the problem.
2022.08.08:
Latest stable .1.11.2-1 has the same crash problem as 1.11.1-1. Downgrading to 1.11.0-1 fixes the problem.
after updating I can’t use zig. I’ve tried uninstalling and reinstalling.
(base) [biom4st3r@AA graph-zig]$ zig
zig: error while loading shared libraries: libclang-cpp.so.13: cannot open shared object file: No such file or directory
sorry for my late answer, but I was not at home for some days.
After the Stable update from 21.07. I had big problems:
Kernel 5.19: Touchpad was not working
Kernel 5.15: System very very slow and unstable. It was not usable too.
Since the latest stable update from 29.07. it is a little bit better:
Kernel 5.19: Touchpad was not working too
Kernel 5.15: Now it works fine.
With Kernel 5.19 the touchpad is not working before and after login. No chance to use this kernel. I hope, it will better with the next Kernel update to 5.19.0 (actually in testing branch).