Wonderful. Thank you. It’s disabled.
My history of a failed system update:
pamac gui showed system update notification.
I ran timeshift to take a snapshot of the system.
While timeshift was running, a terminal and gedit were launched. I edited bmenu and tested it in terminal.
By mistake from the terminal command history, I ran sudo pacman -Syu. pacman found system updates and offered to install them (choose: y/n). I chose cancel.
At this time, the system freezes and I could not do anything until the timeshift job was over. At the end of timeshift, the system returned to its normal state.
I opened the pamac gui window and proceeded with the suggested update. The update was not going as usual, the system was constantly freezing, the update took a very long time. At the end of the update, the system returned to working condition, but something was not as usual.
I rebooted my computer and got a bootloader error: Kernel missing, please load the kernel first. Windows boot items disappeared from the grub menu.
I booted the live CD and found that /boot was missing the kernel and the windows and linux images. Root folder was empty…
I restored the system from the last timeshift snapshot: the system started up, but wifi did not work and there was no uefi settings item in the grub menu.
I restored the system from another timeshift snapshot - everything worked as it should. On a clean booted system, I ran the update with the sudo pacman -Syu command. The system has been updated and everything works great.
I concluded for myself: update the system only after creating a clean backup, do not load the system while timeshift is running, run the update on a clean boot system, using the sudo pacman -Syu command, pamac and pacman may conflict with each other.
Maybe someone will benefit from this experience.
3 Likes
Ooof, been a while since I’ve had one of these:
error: failed to prepare transaction (could not satisfy dependencies)
:: installing nvidia-utils (515.48.07-2) breaks dependency 'nvidia-utils=510.60.02' required by linux516-nvidia
I can see that kernel 5.16 is no longer supported (whoops, not sure why I am running this one).
Anyway, attempting to install one of the LTS ones, like 5.15 now fails with the exact same error message.
Same for 5.17 
After updating to Linux-5.18 and the related module packages (incl. linux518-nvidia) I am not able to boot. The service systemd-modules-load.service fails to start and I am stuck on the systemd output in the terminal. I assume that this is due to the nvidia module.
Journal output of systemd-modules-load.service, failed boot with Linux 5.18
-- Boot 737abeb71a0f43dfa3d14c24d4002ab3 --
čen 13 10:10:37 okonecny-laptop systemd-modules-load[414]: Inserted module 'crypto_user'
čen 13 10:10:37 okonecny-laptop systemd-modules-load[414]: Inserted module 'sg'
čen 13 10:10:37 okonecny-laptop systemd-modules-load[414]: Inserted module 'ipmi_devintf'
čen 13 10:10:37 okonecny-laptop systemd-modules-load[414]: Inserted module 'vboxdrv'
čen 13 10:10:37 okonecny-laptop systemd-modules-load[414]: Inserted module 'vboxnetadp'
čen 13 10:10:37 okonecny-laptop systemd-modules-load[414]: Inserted module 'vboxnetflt'
čen 13 10:10:38 okonecny-laptop systemd[1]: systemd-modules-load.service: Main process exited, code=killed, status=11/SEGV
čen 13 10:10:38 okonecny-laptop systemd[1]: systemd-modules-load.service: Failed with result 'signal'.
čen 13 10:10:38 okonecny-laptop systemd[1]: Failed to start Load Kernel Modules.
čen 13 10:10:38 okonecny-laptop systemd[1]: systemd-modules-load.service: Consumed 1.057s CPU time.
čen 13 10:10:38 okonecny-laptop systemd[1]: Starting Load Kernel Modules...
čen 13 10:10:51 okonecny-laptop systemd[1]: systemd-modules-load.service: Main process exited, code=killed, status=15/TERM
čen 13 10:10:51 okonecny-laptop systemd[1]: systemd-modules-load.service: Failed with result 'signal'.
čen 13 10:10:51 okonecny-laptop systemd[1]: Stopped Load Kernel Modules.
Journal output of systemd-modules-load.service, successful boot with Linux 5.17
-- Boot 4124dcd54505494b8c885523e368019a --
čen 13 10:12:15 okonecny-laptop systemd-modules-load[430]: Inserted module 'crypto_user'
čen 13 10:12:15 okonecny-laptop systemd-modules-load[430]: Inserted module 'sg'
čen 13 10:12:15 okonecny-laptop systemd-modules-load[430]: Inserted module 'ipmi_devintf'
čen 13 10:12:15 okonecny-laptop systemd-modules-load[430]: Inserted module 'vboxdrv'
čen 13 10:12:15 okonecny-laptop systemd-modules-load[430]: Inserted module 'vboxnetadp'
čen 13 10:12:15 okonecny-laptop systemd-modules-load[430]: Inserted module 'vboxnetflt'
čen 13 10:12:16 okonecny-laptop systemd-modules-load[430]: Inserted module 'nvidia'
čen 13 10:12:17 okonecny-laptop systemd-modules-load[430]: Inserted module 'nvidia_drm'
čen 13 10:12:17 okonecny-laptop systemd-modules-load[430]: Inserted module 'nvidia_uvm'
čen 13 10:12:17 okonecny-laptop systemd-modules-load[430]: Inserted module 'uinput'
čen 13 10:12:17 okonecny-laptop systemd[1]: Finished Load Kernel Modules.
Package versions
- linux518 5.18.3-1
- linux518-nvidia 515.48.07-4
- linux518-virtualbox-host-modules 6.1.34-5
- systemd 251.2-3
After 5.17 lots of realtek drivers are borked.
I’d suggest:
- install the free driver
- remove the non-free driver
- update
- install LTS kernel
- reboot to LTS kernel
- remove 5.16 kernel
- install non-free driver
- remove free driver
- reboot
In case things go south, you may want to prepare a plan B beforehand:
- prepare a liveUSB
- note how to boot without graphical manager
[HowTo] Reach a minimal system
Ended up with the same error after reboot. That is updating via pacman and with kernel 5.15. Will have to see if I can fix it on my own later in the day.
Edit: Fixed it by chrooting via .iso and installing kernels again.
I have a custom theme (Matcha-dark-sea) on Gnome.
Every app other than Evolution has no issue with this setup.
However, it’s only acting up on X11, it’s fine on Wayland.
Weirdly, it’s starting up with the default light theme even though I have selected dark in Settings > Appearence?!?
Worked around by changing every Exec=evolution WHATEVER to Exec=env GTK_THEME='Matcha-dark-sea' evolution WHATEVER in /usr/share/applications/org.gnome.Evolution.desktop
Note: Setting $GTK_THEME in /etc/environment messed up Gnome native apps for some reason. Better to copy the gtk-4.0 folder from your /usr/share/themes/THEME_NAME to ~/.config
After updating to VirtualBox-6.1.34-4 i had massive stability issues in Linux (Debian Bullseye) guest systems.
1 Like
I have no problem using vim. Maybe try to refresh your mirror or change to an up-to-date one.
Anyone know / findout that we can use options amd-pstate replace=1 on 5.18.3?
So with these pending patches it would allow simply having amd_pstate.replace=1 as a kernel parameter to boot the system and use AMD P-State without blacklisting ACPI CPUFreq or rebuilding your kernel with this new driver built-in. This would also allow users to toss “options amd-pstate replace=1” into the /etc/modprobe.d directory on distributions like Ubuntu as another easy means of switching. Thus this convenient patch series is making things much simpler for the kernel builds out there having AMD P-State as a module and ultimately making it even easier for users to opt into using this new driver focused on better power efficiency.
Same here with Windows (10) clients. VMs working ok for some minutes, then freeze with 100% CPU usage. Virtualbox log states:
00:05:53.750434 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e P1=0xffffffffc0000005 P2=0xfffff8073f676d5a P3=0x0 P4=0x28
00:05:53.750470 GIMHv: BugCheck 1e {ffffffffc0000005, fffff8073f676d5a, 0, 28}
00:05:53.750471 KMODE_EXCEPTION_NOT_HANDLED
00:05:53.750471 P1: ffffffffc0000005 - exception code - STATUS_ACCESS_VIOLATION
00:05:53.750471 P2: fffff8073f676d5a - EIP/RIP
00:05:53.750471 P3: 0000000000000000 - Xcpt param #0
00:05:53.750471 P4: 0000000000000028 - Xcpt param #1
00:05:56.065743 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:05:56.397603 VMMDev: Guest Log: VBoxGuest: BugCheck! P0=0x1e P1=0xffffffffc0000005 P2=0xfffff8073f676d5a P3=0x0 P4=0x28
Already tried switching between the LTS kernels.
2 Likes
Even worse, the new grub update now requires shim-signed 15.6, which most popular distro like Fedora and Ubuntu don’t even have it yet. Thus you’ll get prohibited by secure boot policy from grub
Having some odd display issues with Flatpak apps only, and just since rebooting after the last update.
Happens with all flatpak apps (with the excpection of junction for some reason) and as far as I can tell flatpak apps only. I can’t include media or links but I have examples if needed.
Application buttons work fine, but app window is pixelated and not readable at all
There is no option amd_pstate.replace in the list of modinfo.
You can check what is the output of sudo modinfo -p amd_pstate that shows only one parameter/option.
shared_mem:enable amd-pstate on processors with shared memory solution (false = disabled (default), true = enabled) (bool)
That means the option replace does not exist in Linux Kernel 5.18.3
And the other option amd_pstate.enable does not exist too.
1 Like
A post was split to a new topic: Installation von nvidia-utils (515.48.07-2) verletzt Abhängigkeit »nvidia-utils=510.73.05«, benötigt von linux414-nvidia
Workaround at this point is to start program as
MESA_GL_VERSION_OVERRIDE=4.1 blender
I’m getting a loud BEEP from my laptop at the exact moment I click the “restart” button on the restart dialogue window. I’ve never heard a beep like this from the laptop before.
Edit: (also for power off)
1 Like