Re: Compiled i915kms.ko errors with incorrect file type does not match kernel

From: <robert_at_rrbrussell.com>
Date: Fri, 22 Mar 2024 16:27:33 UTC
On Fri, Mar 22, 2024, at 10:32, dvoich wrote:
>> On Mar 21, 2024 at 11:42 PM, Robert R. Russell <robert@rrbrussell.com> wrote: 
>> 
>> On Thu, 21 Mar 2024 10:22:15 -0400 (EDT)
>> dvoich@optonline.net wrote:
>> 
>> > I used portmaster to update my ports. When I booted up the next day
>> > X11 failed to start. I saw that i915kms.ko failed to load. I thought
>> > all I had to do was recompile and install drm-kmod. I compiled and
>> > installed both from the ports. Not the one marked &quot;ignore&quot;.
>> > They both failed to load.
>> > I am running 14.0 p5. 
>> > I must have missed some step but I have no clue what it could be.
>> 
>> The graphics/drm-kmod port is a meta port that pulls in the correct
>> graphics/drm-<VERSION>-kmod port and all of the
>> graphics/gpu-firmware-<MANUFACTURER>-kmod@<CODENAME> ports. Just
>> rebuilding it will not rebuild the dependencies.
>> 
>> For FreeBSD-14 you need graphics/drm-515-kmod and one of the
>> flavors of graphics/gpu-firmware-intel-kmod to provide the firmware
>> files. Once graphics/drm-515-kmod is rebuilt load the i915kms kernel
>> module and then check dmesg for the name of which firmware file it
>> couldn't load. Most of the files are named something like alk where the
>> a stands for alder and the lk stand for lake. ```make -V FLAVORS```
>> in graphics/gpu-firmware-intel-kmod will give you all of the FLAVORS
>> you can build.
>> 
>> Once you know which flavor you need I would put the portmaster
>> incantation to rebuild graphics/drm-515-kmod and
>> graphics/gpu-firmware-intel-kmod@<FLAVOR> in a shell script that you
>> can run after every kernel installation.
>>  I failed at the beginning. After loading i915kms.ko I see nothing in dmesg about failing to load anything. I tried kload -v also.
>> The CPU is a P8700 which is in the Penryn family. I have not been able to map that to any of the flavors.

Your processor is old enough to not require firmware for the video chip. Loading extra firmware became required around the 4000 series Core processors.