You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 6, 2023. It is now read-only.
Thanks for this project. The installation procedure are clear and worked pretty well. I want to report one small issue which arose when reusing the Ubuntu kernel's configuration.
Context
I have a new Intel laptop featuring an Intel Iris Max Xe GPU and was going through the Intel instructions when some issue arose while compiling this kernel from a newly installed stock Ubuntu 20.04 LTS:
Issue
make[3]: *** No rule to make target 'debian/canonical-certs.pem', needed by 'certs/x509_certificate_list'. Stop.
The issue seems to come from the newer kernel configurations, namely /boot/config-5.8.0-45-generic and /boot/config-5.10.0-1017-oem which contain the following line:
Simply running the following "solved" the problem for me:
cp /boot/config-$(uname -r) ${HOME}/kernel-xe-max/.config
sed -i 's%CONFIG_SYSTEM_TRUSTED_KEYS=".*"%CONFIG_SYSTEM_TRUSTED_KEYS=""%' ${HOME}/kernel-xe-max/.config
make olddefconfig
I'm not sure if this should be added to the README instructions or if it's possible to fix the issue in the Ubuntu kernel configuration to begin with?
The text was updated successfully, but these errors were encountered:
Hello,
Thanks for this project. The installation procedure are clear and worked pretty well. I want to report one small issue which arose when reusing the Ubuntu kernel's configuration.
Context
I have a new Intel laptop featuring an Intel Iris Max Xe GPU and was going through the Intel instructions when some issue arose while compiling this kernel from a newly installed stock Ubuntu 20.04 LTS:
Issue
The issue seems to come from the newer kernel configurations, namely
/boot/config-5.8.0-45-generic
and/boot/config-5.10.0-1017-oem
which contain the following line:Fix
Simply running the following "solved" the problem for me:
I'm not sure if this should be added to the README instructions or if it's possible to fix the issue in the Ubuntu kernel configuration to begin with?
The text was updated successfully, but these errors were encountered: