Apparently, my graphical card isn't recognized

From the log, that intel card isn't that old, so shouldn't need mesa-amber.
I do see however that most of the time you are using the intel driver instead of the in-kernel modesetting driver.
Default installs for KaOS do not use the xf86-video-intel driver anymore, in-kernel is for almost all systems better, and is fully maintained. The intel driver has not seen a stable release in over 6 years, and no commits for close to 18 months, so pretty much dead. You still see the same issue with latest mesa and xf86-video-intel removed?

Then 2 more notes from the log, pacman -Qm shows that you have a bunch still installed that are no longer in the repositories (some have been gone for close to 2 years.....), best to run pacman -Qm once a month or so and remove packages that you don't build and maintain yourself.
Second, the intel-ucode package is useless to install, it is only used for kernel building, the ucode package makes it possible to include the intel microcode within the kernel (so you already always have the latest microcodo).

Once you remove x86-video-intel, on reboot the modesetting driver is automatically loaded, no need to do any. Blacklisting the amd card has no effect on this.
So it seems your system will need the legacy mesa-amber.....

No, it is not in, I was hoping it was only needed for really old cards, will be added now that a system this new needs it.

mesa-amber is also up:

sudo pacman -U http://kaosx.tk/repo/build/mesa-amber-21.3.8-1-x86_64.pkg.tar.zst

That will ask you to replace mesa, answer yes.

So, combined with this thread https://forum.kaosx.us/d/2958-new-iso-live-boot-get-blank-screen-202206/34
I need to find a way to make the ISO include both mesa & mesa-amber (so they need to be co-installable) and see if that stops the exclusion of a bit older hardware.

@"Rafael" Could you run a test for me? I have it now that both mesa & mesa-amber can be installed at the same time. Tested on a newer system, it works fine (and uses the parts from newer mesa), but no idea if your system will find the needed mesa-amber parts yet. So, can you install with:

sudo pacman -U http://kaosx.tk/repo/build/mesa-amber-21.3.9-4-x86_64.pkg.tar.zst

that should install mesa again too.

demm I have similar card in desktop too:

Graphics:
  Device-1: Intel 4th Generation Core Processor Family Integrated Graphics
    vendor: Acer Incorporated ALI driver: i915 v: kernel arch: Gen7.5
    bus-ID: 00:02.0
  Display: x11 server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.2 driver:
    X: loaded: modesetting unloaded: vesa gpu: i915 resolution: 1920x1080~60Hz
  OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2)
    v: 4.5 Mesa 21.3.9 direct render: Yes

This command runs system without acceleration (both mesa and mesa-amber is installed):

sudo pacman -U http://kaosx.tk/repo/build/mesa-amber-21.3.9-4-x86_64.pkg.tar.zst

But installing mesa-amber 21.3.9-2 from main repo (which removes mesa), enables acceleration after reboot.

adam This command runs system without acceleration (both mesa and mesa-amber is installed):

OK, good start then, system still boots into X, now figuring what is not loading for such a system, when both are installed.
Since I don't have such hardware I have to rely on feedback to make the co-install of mesa & mesa-amber work (so it can be used in the next ISO).
Inxi output above, is that for just mesa-amber? Or is is for the combined mesa packages? Also would be goo to compare the /var/log/Xorg.xx logs for both.

demm
Logs and inxi for mesa-amber only is here: https://adam.234.cz/kaos/only-amber.txt
Logs and inxi for mesa + mesa-amber is here: https://adam.234.cz/kaos/mesa+amber.txt

So no mesa for openGL, llvmpipe instead, with the combined package:

OpenGL: renderer: llvmpipe (LLVM 14.0.6 256 bits) v: 4.5 Mesa 22.1.3
    direct render: Yes

and:

 2.367] (II) modeset(0): Refusing to try glamor on llvmpipe
[     2.368] (II) modeset(0): glamor initialization failed
[     2.368] (II) modeset(0): ShadowFB: preferred YES, enabled YES
[     2.368] (II) modeset(0): Double-buffered shadow updates: off

So, adjustments needed for openGL/Glamor

demm
This shows for cobined mesa+mesa-amber:

libGL: screen 0 does not appear to be DRI2 capable
libGL: MESA-LOADER: dlopen(/usr/lib/dri/swrast_dri.so)
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/adam/.drirc: No such file or directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/adam/.drirc: No such file or directory.

This show for mesa-amber only:

libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/adam/.drirc: No such file or directory.
libGL: using driver i915 for 4
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/adam/.drirc: No such file or directory.
libGL: pci id for fd 4: 8086:041e, driver i965
libGL: MESA-LOADER: dlopen(/usr/lib/dri/i965_dri.so)
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/adam/.drirc: No such file or directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/adam/.drirc: No such file or directory.
libGL: Using DRI3 for screen 0
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.