Perhaps I misread something; I’ve had a sleep since then.
1 Like
i have sort of a similar situation but not as drastic, turns off the screen for about 2 seconds once, when i boot. i have sort of a similar setup with intel i915 display driver on intel integrated 3-rd gen core processor.
like you happens only when i boot with kernel 6.6, however i get no flickers whatsoever when i boot from kernel 5.15.
Not directly - but plymouth 24.x comes
You have kms in the HOOKS array - that is what is referred to as late kms - that is good.
To have what is referred to as early kms the MODULES array - it has been mentioned above - may contain the modules required for your GPU - in this case intel
MODULES=(i915)
Save the file and rebuild init
sudo mkinitcpio -P
Monitor-1: HDMI-A-1 model: ASUS VY279 serial: <filter> built: 2022
res: 1920x1080 dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23")
diag: 686mm (27") ratio: 16:9 modes: max: 1920x1080 min: 720x400
Monitor-2: eDP-1 model: ChiMei InnoLux 0x14c3 built: 2016 res: 1366x768
dpi: 112 gamma: 1.2 size: 309x173mm (12.17x6.81") diag: 354mm (13.9")
ratio: 16:9 modes: 1366x768
I see that your built-in display is HD (1366x768) and the attached monitor is FHD (1920x1080). As you are using the most recent LTS and Intel HD Graphics 620 is very well supported in the kernel - to my knowledge - so there is that, I don’t know all even if I pretend to 
Since the mode is set to auto you could try changing the value to 1366x768 matching your built-in disply.
GRUB_GFXMODE=1366x768
Save the file and generate the grub config
sudo grub-mkconfig -o /boot/grub/grub-cfg
The flicker may happen when there is a hand-over of screen from firmware → boot loader → kernel → display manager and it is a wellknown issue which plymouth is designed to hide.
Plymouth is a project from Fedora and now listed among the freedesktop.org’s official resources providing a flicker-free graphical boot process. It relies on kernel mode setting (KMS) to set the native resolution of the display as early as possible, then provides an eye-candy splash screen leading all the way up to the login manager.
– Plymouth - ArchWiki
1 Like
Meaning I should run the unstable branch’s Plymouth package? Is it OK to leave it as it is in stable?
Do I need to do anything to kms from HOOKS? Or simply leave it there as it is and add i915 to MODULES=()?
The KMS article on Arch Wiki says:
Note: Users of kernel version >=6.9 have to provide their own custom EDID binary as the built-in modes were removed in version 6.9.
…
If you are doing early KMS, you must include the custom EDID file in the initramfs, otherwise you will run into problems.
Anything I should do about this?
Edit: I added i915 to the MODULES array and ran sudo mkinitcpio -P. The flickering did not appear to get any better after rebooting, so I removed i915 from MODULES. I also noticed while running sudo mkinitcpio -P that during the fallback image generation, it gives a warning:
==> WARNING: Possibly missing firmware for module: 'ast'
The firmware needed to get rid of this warning is in the AUR, which I prefer to avoid. Perhaps ‘ast’ is causing issues?