During my last system update, which included updating the kernels, everything froze in Plasma. I couldn’t move the mouse or Alt+F2 my way out. I waited for a while in case the update was still going on in the background somehow. Then I killed the system by pressing the power button.
Now, when trying to boot, it says that no kernel is found.
How can I install a kernel again and boot into the system?
Thank you! I followed the instructions and during the update pacman complained about existing files for the kernel and nvidia packages, so I used “–overwrite “*””, which seemed to fix it.
However, after rebooting two things happened:
Grub doesn’t show any UI - it’s all black until suddenly the system starts to boot.
I have verbose boot mode on, and suddenly I see a lot of red errors. I managed to read something about D-bus (it went by too quickly to read in detail). Afterwards, I’m greeted with a black screen and can do nothing (except Ctrl-Alt Del my way out).
I tried booting back into the live USB doing manjaro-chroot and calling “journalctl -b”, but it says there are no entries. Trying to do the update again states there are no new packages.
But even if I get the menu to show up it won’t solve the failed boot. How do I find the messages if “journalctl” in manjaro-chroot won’t show them?
EDIT: I managed to get the menu to show again. It seems that it was set to hidden in /etc/default/grub, I changed it back to “menu”.
As for the error I expect is behind the system not booting correctly:
May 13 08:10:41 dbus-broker-launch[869]: Invalid XML in /etc/dbus-1/system.d/org.manjaro.pamac.daemon.conf +1: no element found
May 13 08:10:41 dbus-broker-launch[869]: ERROR run @ ../dbus-broker-36/src/launch/main.c +152: Return code 1
May 13 08:10:41 dbus-broker-launch[869]: main @ ../dbus-broker-36/src/launch/main.c +178
May 13 08:10:41 dbus-broker-launch[869]: Exiting due to fatal error: -131
May 13 08:10:41 systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE
May 13 08:10:41 systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
May 13 08:10:41 systemd[1]: Failed to start D-Bus System Message Bus.
May 13 08:10:41 systemd[1]: Dependency failed for Network Manager.
May 13 08:10:41 systemd[1]: NetworkManager.service: Job NetworkManager.service/start failed with result 'dependency'.
May 13 08:10:41 systemd[1]: Reached target Network.
May 13 08:10:41 systemd[1]: Starting D-Bus System Message Bus...
May 13 08:10:41 dbus-broker-launch[874]: Invalid XML in /etc/dbus-1/system.d/org.manjaro.pamac.daemon.conf +1: no element found
May 13 08:10:41 dbus-broker-launch[874]: ERROR run @ ../dbus-broker-36/src/launch/main.c +152: Return code 1
May 13 08:10:41 dbus-broker-launch[874]: main @ ../dbus-broker-36/src/launch/main.c +178
May 13 08:10:41 dbus-broker-launch[874]: Exiting due to fatal error: -131
May 13 08:10:41 systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE
May 13 08:10:41 systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
May 13 08:10:41 systemd[1]: Failed to start D-Bus System Message Bus.
May 13 08:10:41 systemd[1]: Starting D-Bus System Message Bus...
May 13 08:10:41 dbus-broker-launch[879]: Invalid XML in /etc/dbus-1/system.d/org.manjaro.pamac.daemon.conf +1: no element found
May 13 08:10:41 dbus-broker-launch[879]: ERROR run @ ../dbus-broker-36/src/launch/main.c +152: Return code 1
May 13 08:10:41 dbus-broker-launch[879]: main @ ../dbus-broker-36/src/launch/main.c +178
May 13 08:10:41 dbus-broker-launch[879]: Exiting due to fatal error: -131
May 13 08:10:41 systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE
May 13 08:10:41 systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
May 13 08:10:41 systemd[1]: Failed to start D-Bus System Message Bus.
May 13 08:10:41 systemd[1]: Starting D-Bus System Message Bus...
May 13 08:10:41 dbus-broker-launch[884]: Invalid XML in /etc/dbus-1/system.d/org.manjaro.pamac.daemon.conf +1: no element found
May 13 08:10:41 dbus-broker-launch[884]: ERROR run @ ../dbus-broker-36/src/launch/main.c +152: Return code 1
May 13 08:10:41 dbus-broker-launch[884]: main @ ../dbus-broker-36/src/launch/main.c +178
May 13 08:10:41 dbus-broker-launch[884]: Exiting due to fatal error: -131
May 13 08:10:41 systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE
May 13 08:10:41 systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
May 13 08:10:42 systemd[1]: Failed to start D-Bus System Message Bus.
May 13 08:10:42 systemd[1]: Starting D-Bus System Message Bus...
May 13 08:10:42 dbus-broker-launch[889]: Invalid XML in /etc/dbus-1/system.d/org.manjaro.pamac.daemon.conf +1: no element found
May 13 08:10:42 dbus-broker-launch[889]: ERROR run @ ../dbus-broker-36/src/launch/main.c +152: Return code 1
May 13 08:10:42 dbus-broker-launch[889]: main @ ../dbus-broker-36/src/launch/main.c +178
May 13 08:10:42 dbus-broker-launch[889]: Exiting due to fatal error: -131
May 13 08:10:42 systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE
May 13 08:10:42 systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
May 13 08:10:42 systemd[1]: Failed to start D-Bus System Message Bus.
May 13 08:10:42 systemd[1]: dbus-broker.service: Start request repeated too quickly.
May 13 08:10:42 systemd[1]: dbus-broker.service: Failed with result 'exit-code'.
May 13 08:10:42 systemd[1]: Failed to start D-Bus System Message Bus.
May 13 08:10:42 systemd[1]: dbus.socket: Failed with result 'service-start-limit-hit'.
I solved the D-bus error by installing it from the other provider.
Now, however, I have no network interfaces when booting into Manjaro. Wifi doesn’t work and it doesn’t recognize any networks at all.
Here are some potentially relevant entries from “journalctl -b”
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: loading /lib/firmware/iwlwifi-9000-pu-b0-jf-b0-46.ucode.zst failed with error -22
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -22
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-43.ucode failed with error -2
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-42.ucode failed with error -2
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-41.ucode failed with error -2
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-40.ucode failed with error -2
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-39.ucode failed with error -2
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: loading /lib/firmware/iwlwifi-9000-pu-b0-jf-b0-38.ucode.zst failed with error -22
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-38.ucode failed with error -22
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-37.ucode failed with error -2
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-36.ucode failed with error -2
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-35.ucode failed with error -2
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: loading /lib/firmware/iwlwifi-9000-pu-b0-jf-b0-34.ucode.zst failed with error -22
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-34.ucode failed with error -22
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-33.ucode failed with error -2
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-32.ucode failed with error -2
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-31.ucode failed with error -2
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-30.ucode failed with error -2
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: no suitable firmware found!
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: minimum version required: iwlwifi-9000-pu-b0-jf-b0-30
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: maximum version supported: iwlwifi-9000-pu-b0-jf-b0-46
maj 14 07:48:44 kernel: iwlwifi 0000:00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
maj 14 07:48:47 systemd[1]: Started Network Manager Script Dispatcher Service.
maj 14 07:48:47 kernel: r8169 0000:07:00.0: loading /lib/firmware/rtl_nic/rtl8168h-2.fw.zst failed with error -22
maj 14 07:48:47 kernel: r8169 0000:07:00.0: Direct firmware load for rtl_nic/rtl8168h-2.fw failed with error -22
maj 14 07:48:47 kernel: r8169 0000:07:00.0: Unable to load firmware rtl_nic/rtl8168h-2.fw (-22)
maj 14 07:48:47 kernel: Generic FE-GE Realtek PHY r8169-0-700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-700:00, irq=MAC)
maj 14 07:48:47 kernel: r8169 0000:07:00.0 enp7s0: Link is Down
In which case an update is incoming, as mentioned there.
But if you really really need it now you can temporarily follow the downgrade instructions there.
Or if you have no way to download packages then you can use pacman with the cache directly via something like
Basically, I re-installed D-bus using the “dbus-daemon-units” package instead of the default dbus-broker one.
I solved the issue with Wifi (writing this in my Manjaro installation now) by reinstalling all packages mentioned by the output in the “pacman -Qkk” command with the “–overwrite ‘*’” flag. Re-running “pacman -Qkk” chrooted in the live USB didn’t then give those errors. However, running the same command booted into Manjaro does return the same errors (even though Wifi works). Is that anything to be worried about?