Arch Linux

ua4000

Member

Registered: 2015-10-14

Posts: 558

[SOLVED] "very late" load the graphics drivers - with xinit ?

Hello, I'm using xinit to manually start an Xorg display server after my login in the tty.

What is bothering me,
that during boot, when the graphics drivers is loaded my screen flickers and changes resolution.
On several machines, one with AMDGPU, Intel graphics and an older one with Nouveau I think.

Is it possible to "very late" load the graphics drivers at the time-point when Xorg starts?
In the wiki I found "Early KMS start" - but I would like the opposite: very late with xinit.

Thanks!

Last edited by ua4000 (2024-01-20 20:11:06)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,037

Re: [SOLVED] "very late" load the graphics drivers - with xinit ?

You can blacklist the module and load it explicitly w/ your xinitrc, but will have to grant yourself (passwordless) sudo permissions or so (only root can load modules)
Have you tried to enabled early KMS to do the opposite and have the flickering resolution change as fast as possible?

Alternatively you can tell your framebuffer console to use a specific resolution, https://www.kernel.org/doc/Documentation/fb/modedb.rst

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

ua4000

Member

Registered: 2015-10-14

Posts: 558

Re: [SOLVED] "very late" load the graphics drivers - with xinit ?

Thanks seth,
I will have a look at 2nd and 3rd idea, maybe the early KMS will do the trick for me.
1st one would solve it probably for me, but I use xinit do start x without root for security reason, requiring sudo to load the driver as normal user is probably going into the wrong direction.

For my intel system I found also https://wiki.archlinux.org/title/Intel_ … s#Fastboot and will have a deeper look.

ua4000

Member

Registered: 2015-10-14

Posts: 558

Re: [SOLVED] "very late" load the graphics drivers - with xinit ?

So, it's now better as before:

I found KMS hook was missing in mkinitcpio - I had an older installation and probably missed the migration step in the past.
In addition I found a "GRUB_TERMINAL=console" in my grub config, which caused a further screen flicker. I reviewed all my grub settings and came to a one liner "GRUB_TIMEOUT=3".