After restarting, I can no longer log in!!! the system freezes when logging in!
Luckily I was able to return to the previous status using TimeShift.
I repeated it a total of 5 times. Below are the details of the kernel update window. I suspectes this is where the problem lies. I use KDE Plasma. X11. Kernel: linux67
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
I solved this by installing upd72020x-fw and linux-firmware-qlogic. Nevertheless, I cannot log in after the update. This error message appears when booting up, see screenshot.
If itâs legacy (BIOS) boot on GPT, surely there should be a BIOS_GRUB partition at the start? My original Manjaro installation on the T440 doesnât have one, but as far as I know it should do.
Could it be that you boot via an other disk? You could check the boot entry in your firmware.
If you want to continue to boot in BIOS mode a GPT parted disk, I would recommend to create the required small unformatted partitiion with bios_grub flag and then to restore the boot loader, accordingly. How to do it in detail? Use a search engine of your choice or ask here.
I added a second (small) SSD a year ago, but itâs only for data. I honestly donât know what you actually mean here! Would you please explain it a little more simply, thank you in advance.
⯠test -d /sys/firmware/efi && echo efi || echo bios
sudo fdisk -l
sudo blkid
cat /etc/fstab
cat /etc/default/grub
efi
[sudo] Passwort fĂŒr wael:
Festplatte /dev/nvme0n1: 476,94 GiB, 512110190592 Bytes, 1000215216 Sektoren
Festplattenmodell: KBG50ZNT512G LS KIOXIA
Einheiten: Sektoren von 1 * 512 = 512 Bytes
SektorgröĂe (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-GröĂe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: gpt
Festplattenbezeichner: 308BD0A0-3547-03B2-28F4-22CC518DEC00
GerĂ€t Anfang Ende Sektoren GröĂe Typ
/dev/nvme0n1p1 2048 1000214527 1000212480 476,9G Linux-Dateisystem
Festplatte /dev/nvme1n1: 476,94 GiB, 512110190592 Bytes, 1000215216 Sektoren
Festplattenmodell: SKHynix_HFS512GD9TNG-L3A0B
Einheiten: Sektoren von 1 * 512 = 512 Bytes
SektorgröĂe (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-GröĂe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: gpt
Festplattenbezeichner: 3369A323-768F-449C-981A-23C6FF540641
GerĂ€t Anfang Ende Sektoren GröĂe Typ
/dev/nvme1n1p1 2048 534527 532480 260M EFI-System
/dev/nvme1n1p2 534528 567295 32768 16M Microsoft reserviert
/dev/nvme1n1p3 567296 210282495 209715200 100G Microsoft Basisdaten
/dev/nvme1n1p4 998166528 1000214527 2048000 1000M Windows-Wiederherstellungsumgebung
/dev/nvme1n1p5 210282496 419997695 209715200 100G Linux-Dateisystem
/dev/nvme1n1p6 419997696 524855295 104857600 50G Linux-Dateisystem
/dev/nvme1n1p8 524855296 839428095 314572800 150G Linux-Dateisystem
/dev/nvme1n1p10 839428096 981389311 141961216 67,7G Linux-Dateisystem
/dev/nvme1n1p11 981389312 998166527 16777216 8G Linux Swap
PartitionstabelleneintrÀge sind nicht in Festplatten-Reihenfolge.
Festplatte /dev/sda: 119,25 GiB, 128043712512 Bytes, 250085376 Sektoren
Festplattenmodell: MassStorageClass
Einheiten: Sektoren von 1 * 512 = 512 Bytes
SektorgröĂe (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-GröĂe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: dos
Festplattenbezeichner: 0x7ac5c969
GerĂ€t Boot Anfang Ende Sektoren GröĂe Kn Typ
/dev/sda1 2048 250083327 250081280 119,2G 83 Linux
/dev/nvme0n1p1: LABEL="SSD2" UUID="c73f8e05-15ea-4b6e-bb7f-dda205df2ba4" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="bd867749-3a12-2e43-815a-5ad539b76c28"
/dev/nvme1n1p4: LABEL="WINRE_DRV" BLOCK_SIZE="512" UUID="968C75B48C75900B" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="c345b77b-dc48-4bb4-9759-f9b0ce055d73"
/dev/nvme1n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="5c1ee7f9-f923-42c5-8084-b58807b9b85f"
/dev/nvme1n1p10: LABEL="Timeshift" UUID="831c25f6-3fbf-422c-882f-1bdd91e223aa" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="983edf7c-8b69-aa45-9503-3584266fd8ae"
/dev/nvme1n1p5: LABEL="Manjaro" UUID="bd1d44ca-91e0-4a22-b906-6d798639c31c" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="c32050f9-9595-2d43-9b71-44229d646de7"
/dev/nvme1n1p3: LABEL="Windows-SSD" BLOCK_SIZE="512" UUID="0E3674F63674E05F" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="d67bfd1a-525f-4c79-8946-951debac5e81"
/dev/nvme1n1p1: LABEL="SYSTEM_DRV" UUID="9473-F81C" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="7aea648f-de83-4199-b26e-a63022f6ef06"
/dev/nvme1n1p8: LABEL="DATA" UUID="4ea227aa-5aeb-4056-8339-ba7d638f1356" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="28305e6f-03f4-4344-bb64-dbdd519b424d"
/dev/nvme1n1p11: LABEL="swap" UUID="1e5e3666-1b53-42ab-a1fa-0c97603711c1" TYPE="swap" PARTUUID="a70bf29d-fd78-1043-8d22-f8f8ac8646a6"
/dev/nvme1n1p6: LABEL="VirtualBox" UUID="5e127960-be70-4df7-9d07-045736e2650a" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b2800eb7-a31e-3e4e-a9a1-ad0829d3a8df"
/dev/sda1: LABEL="microSD" UUID="aa222ad6-b213-4525-9528-051ba3213931" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="7ac5c969-01"
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=bd1d44ca-91e0-4a22-b906-6d798639c31c / ext4 noatime 0 1
UUID=aa222ad6-b213-4525-9528-051ba3213931 /home/wael/microSD ext4 noexec 0 0
UUID=4ea227aa-5aeb-4056-8339-ba7d638f1356 /home/wael/Data ext4 defaults 0 0
GRUB_DEFAULT="Manjaro Linux"
GRUB_TIMEOUT="3"
GRUB_TIMEOUT_STYLE="hidden"
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet resume=LABEL=swap apparmor=1 security=apparmor 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="false"
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK="y"
# Uncomment to use basic console
GRUB_TERMINAL_INPUT="console"
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT="console"
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE="auto"
# 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"
#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
# 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"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
# Uncomment this option to enable os-prober execution in the grub-mkconfig command
GRUB_DISABLE_OS_PROBER=false
Is this your ESP? Why has it the label âSYSTEM DRVâ?
I wonder why you donât have an entry in /etc/fstabâŠ
Might be needed to restore the boot loader after updating.
yes, i have read it and replied to it, i think. i have done the whole update several times, but each time i was not able to use the system afterwards, so each time i did timeshift. I did the update via the GUI, but also directly via sudo pacman -Syu
Regarding âSYSTEM DRVâ: Iâm not sure, but I think itâs still from Windows. I mentioned that I use dual boot.
but i can try @stephane 's suggestion and report back afterwards. thanks in advance.
sudo pacman-mirrors -c all
sudo pacman -Syyu
pacman -Qs dbus
I got this output:
⯠sudo pacman -Qs dbus
[sudo] Passwort fĂŒr wael:
local/bluez-qt5 5.113.0-1 (kf5)
Qt wrapper for Bluez 5 DBus API
local/dbus 1.14.10-2
Freedesktop.org message bus system
local/dbus-broker 35-2
Linux D-Bus Message Broker
local/dbus-broker-units 35-2
Linux D-Bus Message Broker - Service units
local/dbus-glib 0.112-3
GLib bindings for D-Bus (deprecated)
local/dbus-python 1.3.2-2
Python bindings for D-Bus
local/kdbusaddons5 5.113.0-1 (kf5)
Addons to QtDBus
local/lib32-dbus 1.14.10-2
Freedesktop.org message bus system - 32-bit
local/libcloudproviders 0.3.5-1
DBus API that allows cloud storage sync clients to expose their services
local/libdbusmenu-glib 16.04.0.r498-2
Library for passing menus over DBus
local/libdbusmenu-gtk3 16.04.0.r498-2
Library for passing menus over DBus (GTK+ 3 library)
local/libdbusmenu-qt5 0.9.3+16.04.20160218-6
A library that provides a Qt implementation of the DBusMenu spec
local/modemmanager-qt5 5.113.0-1 (kf5)
Qt wrapper for ModemManager DBus API
local/python-jeepney 0.8.0-2
Low-level, pure Python DBus protocol wrapper
local/python-secretstorage 3.3.3-2
Securely store passwords and other private data using the SecretService DBus API
local/xdg-dbus-proxy 0.1.5-1
Filtering proxy for D-Bus connections
After restarting I got the same problem as described above.
All pacnew files should be merged, but especially thins one: itâs for your display manager.
edit: Did you try to login at a tty and look at some logs whydbus would not start? dbus-broker seems to be a little less lenient when some configuring xml files are errornousâŠ
