Solved Intel Alder Lake does not start the graphics card with FBSD14.1

[judd]

The laptop is an Asus with an I7-1260p graphics card and Intel Alder Lake-P GT2 [Iris Xe Graphics]

After installing Xorg, I manually run sysrc kldload i915kms.ko and it instantly reboots with two final lines in the screenshot that I don't know what they mean:


After that reboot I installed:
.drm-61-kmod
.gpu-firmware-intel-drm-alderlake

I haven't been able to upload the graphics card either.

 

[Erichans]

I manually run sysrc kldload i915kms.ko

Please show the output of cat /etc/rc.conf | grep kld_list

After that reboot I installed:
.drm-61-kmod
.gpu-firmware-intel-drm-alderlake

How did you install these two?

Did you recently upgraded from a previous FreeBSD -RELEASE, for example 14.0-RELEASE?

 

[judd]

Erichans

kld_list="/boot/modules/i915.kms.ko"

 

[judd]

Did you recently upgraded from a previous FreeBSD -RELEASE, for example 14.0-RELEASE?

No, it is a clean installation.

 

[Erichans]

After that reboot I installed:
.drm-61-kmod
.gpu-firmware-intel-drm-alderlake

How did you install these two?

---

kld_list="/boot/modules/i915.kms.ko"

You have a typo. It should be i915kms - no point after "i915"
You only need to specify i915kms, try:

# sysrc kld_list="i915kms"
kld_list: /boot/modules/i915.kms.ko -> i915kms
# sysrc kld_list
kld_list: i915kms

Now reboot and verify that the module has been loaded:

# kldstat | grep i915kms
 6    1 0xffffffff82d94000   1e2228 i915kms.ko

 

[judd]

Now reboot and verify that the module has been loaded:

# kldstat | grep i915kms
6 1 0xffffffff82d94000 1e2228 i915kms.ko

This is a good result.

Now when I reboot, the modules no longer load:


and when you press enter it restarts and so on permanently ...

 

[Erichans]

- Others need help you further.

Your OP screenshot shows that then your system booted OK.
I don't know exactly what's going on based on your last screenshot.

If possible, try disabling as much as possible in your /boot/loader.conf and /etc/rc.conf files: make them comments.
Be sure you keep your ZFS and network stuff.

 

[T-Aoki]

If you installed kmod ports via official pre-built packages, try installing them via ports.
The official packages are built against oldest supported release of the branch, now should be 14.0 on 14 series of releases.
This surely mis-matches for 14.1 for kmods.
This is why I'm proposing to prohibit providing kmod pkgs and force installing from ports on several threads.

 

[judd]

Erichans

I just did another clean install and when I installed drm-kmod and rebooted, exactly what I see in my last screenshot happens, it no longer loads the kernel modules and reboots in an endless loop.

Besides i915kms and installing drm-kmod, I don't know what other option I have to do ?

 

[fmc000]

Do what T-Aoki just suggested in the post just above yours. Try compiling drm-61-kmod from the ports and uninstall whatever drm-kmod release you currently have.

 

[Cath O'Deray]

… I'm proposing to prohibit providing kmod pkgs and force installing from ports

Please, no.

on several threads.

Instead, please create a single topic; for discussions to not be scattered.

 

[Cath O'Deray]

… restarts and so on permanently …

I perceive a fix to the msdosfs file system on the EFI system partition. If a repair was truly required: in my experience, that's extraordinary.

 

[T-Aoki]

Instead, please create a single topic; for discussions to not be scattered.

Unfortunately, it's meaningless.
On upgrading, different person create a thread per person independently.
On each case I noticed, I'm replying the same thing. Not my intention.
And the fact made me think providing pkg for kmod ports is the near-root cause of the problem. (Yes, not the actual root cause.)
And discussing about it would fit better on MLs, maybe freebsd-arch or freebsd-ports which more developers are reading. Not here, unfortunately.

 

[judd]

I reinstalled and compiled the drm-61-kmod port, without being able to raise the graph.

Inside what you can see by a picture in /var/log/Xorg.0.log is this:

Maybe according to the log I am missing a file, in /dev/dri/card0, I don't know ...

Thanks for your help!

 

[fmc000]

No, that file is auto-generated when the video card is recognized. i get:

[    16.160] (++) using VT number 9

[    16.192] (II) modeset(0): using drv /dev/dri/card0

Instead of launching X from the command line try:

[16:03][fmc000@tu45b-freebsd][~]
 ⤷ $ dmesg|grep 915
drmn0: successfully loaded firmware image 'i915/tgl_dmc_ver2_12.bin'
drmn0: [drm] Finished loading DMC firmware i915/tgl_dmc_ver2_12.bin (v2.12)
[drm] Initialized i915 1.6.0 20201103 for drmn0 on minor 0
name=drmn0 id=i915drmfb flags=0x0 stride=7680
[16:04][fmc000@tu45b-freebsd][~]
 ⤷ $

Also, be sure to NOT have a xorg.conf file and let the system detect everything by itself.

 

[judd]

fmc000

dmesg|grep 915 does not produce any results.

i915kms is in rc.conf but it doesn't load the module on reboot and it doesn't appear in kldstat either. If I load it manually with kldload the recursive reboot occurs.

 

[fmc000]

Do you have something like this?

[16:11][fmc000@tu45b-freebsd][~]
 ⤷ $ grep 915 /etc/rc.conf
kld_list="i915kms"
[17:26][fmc000@tu45b-freebsd][~]
 ⤷ $

Anyways, if a manual kldload causes a reboot I think you're out of luck... Your last chance I believe is to try drm-515-kmod

 

[Cath O'Deray]

… with kldload the recursive reboot occurs.

If you'll perform a fresh installation of FreeBSD … I wonder whether the issue will be reproducible with FreeBSD 15.0-CURRENT and the Project-provided package for graphics/drm-61-kmod (currently 6.1.92).

 

[judd]

fmc000​

Your last chance I believe is to try drm-515-kmod

Yes, that's the way it's going !


After uninstalling drm-61-kmod port and installing by drm-515-kmod ports i915 works:

# kldstat | grep i915kms
 4    1 0xffffffff831e5000   1b2920 i915kms.ko

After the above it works and I can log in!

Thanks for your help!

 

[fmc000]

Good...but weird. 515 is the default in 14.1 so you shouldn't have had the problem in the first place. Even weirder, 61 should be more "modern" than 515 and therefore be more compatible with Alder Lake.

BTW, I run 61 on my Tiger Lake and I see no improvement when compared to 515 but also no regressions.

 

[Cath O'Deray]

… 515 is the default in 14.1 …

I think not.

Please see the Makefile for drm-kmod.

 

[T-Aoki]

515 is the default in 14.1

No. 61 is the default for 14.1.
graphics/drm-kmod checks OSVERSION (comes from __FREEBSD_VERSION in /usr/include/sys/param.h) and if it's equal to or above 1400508, 61 is chosen. 14.1 has OSVERSION of 1401000.
So graphics/drm-61-kmod should have problem(s).

 

[fmc000]

So weird, in my case it installed 515 and I had to compile 61 from the ports. Not only that:

21:40][fmc000@tu45b-freebsd][~]
 ⤷ $ se kmod|grep drm
drm-510-kmod-5.10.163_9        DRM drivers modules
drm-515-kmod-5.15.160          DRM drivers modules
drm-kmod-20220907_3            Metaport of DRM modules for the linuxkpi-based KMS components
gpu-firmware-kmod-20240401,1   Firmware modules for the drm-kmod drivers
nvidia-drm-510-kmod-550.54.14_1 NVIDIA DRM Kernel Module
nvidia-drm-515-kmod-550.54.14_1 NVIDIA DRM Kernel Module
nvidia-drm-kmod-550.54.14      NVIDIA DRM Kernel Module
[21:40][fmc000@tu45b-freebsd][~]
 ⤷ $ uname -KrU
14.1-RELEASE 1401000 1401000
[21:41][fmc000@tu45b-freebsd][~]
 ⤷ $

( se is just an alias to 'pkg search ')

I'm clearly missing something.

 

[T-Aoki]

So weird, in my case it installed 515 and I had to compile 61 from the ports.

Which branch (for ports) are you on?
The change for choosing 61 for 14.* having OSVERSION 1400508 or above is committed at 2024-03-12 16:19:13 +0000 on ports main branch.
So if you are on 2024Q2 or main equal to or newer than the commit, you should have it.
If you are on 2024Q1 or earlier, it's not merged. So you shouldn't have it.

 

[fmc000]

Honestly, I have no idea. I just installed FreeBSD for the first time this week using the 14.1 memstick image. How do I know what branch I'm on and what should I do to switch to the latest one?