Hit the numlock key right after seeing Manjaro with the three large dots to then get the login screen. Otherwise, the Manjaro with the three large dots disappears and is replaced with three small dots requiring a CTRL-ALT-DELETE to reboot.
I solved the problem with
==> 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'
by installing upd72020x-fw and linux-firmware-qlogic.
but I still can’t log in after the update. Nevertheless, I cannot log in after the update. This error message appears when booting up, see screenshot.
Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text
Have the login problem on the machine where the kernel was upgraded from 6.1 to 6.6. The machine that has a clean install with kernel 6.6 does not have this login problem.
Fixed with gnome-shell 1:45.3-1.
1 Like
Looks like mkinitcpio-37.2 got downgraded to mkinitcpio-37.1 a few minutes ago.
It happened while I was downloading :
error: failed retrieving file 'mkinitcpio-37.2-1-any.pkg.tar.zst' from gsl-syd.mm.fcix.net : The requested URL returned error: 404
After I looked at a few other mirror sites in a browser, it seemed to be a downgrade,
so I ran pacman -Sy again, and then pacman -Suuw was able to finish OK.
1 Like
Strictly speaking, that’s not true. The /boot directory and the EFI partition are both only accessed by maintenance utilities such as grub-install, update-grub and mkinitcpio.
The system itself does not access either /boot or /boot/efi during the boot process.
-
In the event of a legacy BIOS boot, the BIOS reads the MBR, which loads the first stage of GRUB, and GRUB itself will then either read the raw blocks of the
/bootpartition (on MSDOS-style partitioned drives) or of the unformattedbios_grubpartition (on GPT-style partitioned drives) in order to load its intermediary stage. This intermediary stage then contains a filesystem driver and will then mount the/bootpartition as its own root partition. Upon manually or automatically choosing a GRUB menu entry, the compressed kernel image and theinitramfsare read into RAM and decompressed. From that point onward,/bootis no longer being accessed by the system. -
In the event of a native UEFI boot, the UEFI reads the chosen or default EFI executable into RAM and executes it. The UEFI-native version of GRUB installs such an executable in the EFI system partition — both in
/boot/efi/EFI/bootand in/boot/efi/EFI/manjaro— and from there on, GRUB will, by way of a filesystem driver, mount/bootas its own root filesystem and load the (chosen or default) compressed kernel image and theinitramfsinto memory. Once again, as soon as the kernel image is decompressed and begins booting, it no longer accesses either the ESP or the/bootdirectory.
2 Likes
For 2. VNC output only 4:3 and cut off:
Uninstalling Krfb, deleting the config file (/home/user/.config/krfbc) and reinstalling the package solved this issue…
Still no clue about the Steam display issue though.
The error just vanished 20min ago, before it also appeares on my my second device.
Maybe it was a server issue.
I also think it was mainly related to AUR.
Thanks anyways.
I always do, so I can see there the fails pop up, I remove quiet and splash…good luck
1 Like
Hey, I have mkinitcpo 37.2-1 installed. And my system boots.
Just a silly question I know → should I downgrade just to be save?
Or should I don’t touch something which seems to be fine 
Thanks in advance.
Edit:
I have found my answer:
1 Like
That was always likely. Though I since found Failed to synchronize AUR database (albeit a year old) which might have been related.
As if by magic!
Exactly, its also not the first time i had saw this error.
i ended up keeping it,update went fine.
Your use of “original” is confusing.
My suggestion: “Original” file is the one in the old package version. The “current” file is the original modified by the user or some util. The pacnew is then… well the file in the new package version.
The Steam client had an update yesterday.
Since that the display issue is also gone.
Only to you, it seems. In context, the original is that which is to be modified; the file in situ; and the new file – the .pacnew – contains the new information.
You could think of that
- old original file → The default file that would exist if it was current and never changed by the user.
- local file → The file that was on this PC immediately before the update
- suggested file → This is the suggestion to switch to after its changes have been reviewed
I don’t mean to say that my suggestions are the best. Choosing good names can help prevent misunderstandings. 
1 Like
After applying this update, xfwm4 freezes a minute after logging in and starting Firefox. If I’m lucky, I can login in with Ctrl-Alt-F2 and run pkill -9 xfwm4 and then Ctrl-Alt-F7 to get an unfrozen terminal. Sometimes I am not lucky and the system freezes and requires a hard power cycle.
Can you help me localize this behavior? I am not sure what commands to run to test this.
I’ve now updated mkinitcpio to 37.2-1.6, which fixes the extramodules situation and also kms hook for kernels older than 5.17.
2 Likes