Re: Lost hardware acceleration from >=drm-515-kmod for Cherryview and Valleyview i915kms

Hello


Adding another tidbit. This is not exactly the same scenario as the 
Xorg.0.log. It's a feeble attempt to catch what happens with 
/usr/local/libexec/Xorg when it runs.

This is the output from 14.1-RELEASE with drm-515-kmod. After 
unsuccesful boot in console logged in as root running "lldb 
/usr/local/libexec/Xorg" says:

(==) Log file: "/var/log/Xorg.0.log". Time: Sun Jun 7 23:34:41 2026
(==) Using system config directory "/usr/local/share/X11/xorg.conf.d"
scfb trace: probe start
scfb trace: probe done
Process 1583 stopped
* thread #1, name = 'Xorg', stop reason = signal SIGABRT
frame #0: 0x000000082ae3c10a libc.so.7 __sys_thr_kill +10
-> 0x82ae3c10a <+10>: jb
0x82ae3c110 <+16>: retq
0x82ae3c111 int3
0x82ae3c112 int3
(lldb) Stopping sddm.

/Roger

Den 2026-06-07 kl. 15:06, skrev Alexey Dokuchaev:
> On Sun, Jun 07, 2026 at 02:42:13PM +0200, Roger Olofsson wrote:
>> Hello everyone!
>>
>> [...]
>>
>> On a 14.1-RELEASE with drm-510-kmod the hardware acceleration works.
>> On same 14.1-RELEASE with drm-515 the hardware acceleration does not
>> work.
> Hello Roger,
>
> This is not surprising: Linux code only regresses with time and higher
> version numbers.  If you must use Linux code (as we all are with DRM)
> my best advice is to stick to the lowest version which works.
>
>> I am aware that 14.1 is an unsupported system but it's the last known
>> RELEASE that is supported by drm-510-kmod. Also drm-510-kmod is about
>> to vanish, it's clinging in ports 2026Q2.
> Nothing prevents you to checkout drm-510-kmod after its removal and keep
> using it during the 14.x timeline.  HTH,
>
> ./danfe