On Wed, 2019-05-08 at 21:27 +0000, Hans Malissa via blfs-support wrote: > On May 4, 2019 at 11:47 PM, Wayne Blaszczyk <[email protected]> wrote: > > On Sun, 2019-05-05 at 01:50 +0000, Hans Malissa via blfs-support wrote: > > > On May 4, 2019 at 1:03 PM, Ken Moffat via blfs-support > > > <[email protected]> wrote: > > > > On Sat, May 04, 2019 at 05:08:25AM +0000, Hans Malissa via blfs-support > > > > wrote: > > > > > Hello!Did you build it into the kernel? I've noticed that I have to > > > > > build my firmware into the kernel, or otherwise it fails to load at > > > > > runtime. > > > > > Yes (CONFIG_DRM_I915=y; I believe that is the correct kernel > > > > > setting).Greetings, > > > > > Hans > > > > > > > > To build it in, you need to edit the kernel config (menuconfig is > > > > fine, but check the resultsby looking at .config afterwards : if you > > > > start from nothing, it can sometimes end up a bit strange. > > > > > > > > For an old radeon with only 3 items of firmware, I have in the > > > > .config > > > > > > > > # > > > > # Firmware loader > > > > # > > > > CONFIG_FW_LOADER=y > > > > CONFIG_EXTRA_FIRMWARE="radeon/R600_rlc.bin radeon/RS780_pfp.bin > > > > radeon/RS780_me.bin" > > > > CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" > > > > # CONFIG_FW_LOADER_USER_HELPER is not set > > > > > > > > i.e.: > > > > enable the loader > > > > provide a space-separated list of subdirectory/blob items > > > > tell it all firmware is in /lib/firmware > > > > > > > > HTH > > > > > > Thanks a lot! Okay, that does make a difference. > > > I've added the file in question to CONFIG_EXTRA_FIRMWARE, it is now: > > > > > > CONFIG_EXTRA_FIRMWARE="i915/glk_dmc_ver1_04.bin" > > > > > > After compiling the kernel and booting, I get: > > > > > > # dmesg | grep firware > > > [...] [drm] GuC: No firmware known for this platform! > > > [...] [drm] HuC: No firmware known for this platform! > > > [...] [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v1.4) > > > ... > > > > > > So that seems to be working to some degree. Not sure what to do about the > > > first two lines. > > > Greetings, > > > > > > Hans > > > > You might want to try setting CONFIG_DRM_I915=m rather than y. This is what > > I have done. > > I don't have CONFIG_EXTRA_FIRMWARE set, and all 3 blobs are picked up for > > me. > > I also have the following file: > > /etc/modprobe.d/i915.conf > > with the following content: > > options i915 enable_guc=3 > > Okay, I've tried this too. When I compile the kernel with CONFIG_DRM_I915=m, > and add "options i915 enable_guc=3" to /etc/modprobe.d/i915.conf, linux hangs > during startup with the following output: > > ... > [...] Setting dangerous option enable_guc - tainting kernel > [...] [drm] GuC: No firmware known for this platform! > [...] [drm] HuC: No firmware known for this platform! > [...] [drm] Incompatible option detected: enable_guc=3, no GuC firmware! > [...] [drm] Incompatible option detected: enable_guc=3, no HuC firmware! > [...] fb0: switching to inteldrmfb from EFI > > And then the system is stuck. > Otherwise, the only change from CONFIG_DRM_I915=y to CONFIG_DRM=m is that the > firmware blob i915/glk_dmc_ver1_04.bin is being loaded automatically from > /lib/firmware, and doesn't have to be > explicitly added to CONFIG_EXTRA_FIRMWARE, otherwise the system behaves the > same. > I'm guessing that my hardware doesn't support GuC/HuC. There must be > documentation about that somewhere, where can I look up whether my video > controller supports GuC/HuC? > Thanks a lot, > > Hans
https://01.org/linuxgraphics/documentation https://wiki.archlinux.org/index.php/Intel_graphics Regards, Wayne. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
