Re: Firmware kbl_dme_ver1.bin?

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

Try

http://mail-index.netbsd.org/tech-x11/2020/10/27/msg002161.html


On Wed, 26 Apr 2023 at 08:10, Mouse <mouse%rodents-montreal.org@localhost> wrote:
>
> I'm trying to help someone who's trying to use X on NetBSD 9.1.  It's
> failing (of course, or I wouldn't be writing!), and the guy working on
> it came to me for help.  This is far enough outside my knowledge that
> I'm wondering if perhaps some kind soul on the list would in turn be
> willing to give me a hand with it.
>
> It's failing to start the server.  What I have is a snapshot of the
> display when it wedges trying to, apparently, start the X server.  The
> first thing I noticed is that it looks as though it's still running the
> hardware in text mode, rather than the usual 9.1 text-via-graphics
> mode.  Here's a ten-finger copy of what I see displayed.  (I've
> manually undone wrapping of lines long enough to wrap.)
>
> [   3.8541541] kern info [drm] failed to find VBIOS tables
> [   3.8551116] i915drmkms0: interrupting at ioapic 0 pin 16 (i915drmkms0)
> [   3.8581088] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_drv.c:636)i915_firmware_load_error_print] *ERROR* failed to load firmware i915/kbl_dmc_ver1.bin (0)
> [   3.8581088] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_drv.c:661)i915_firmware_load_error_print] *ERROR* The driver is built-in, so to load the firmware you need to
> [   3.8581088] include it either in the kernel (see CONFIG_EXTRA_FIRMWARE) or
> [   3.8581088] in your initrd/initramfs image.
> [   3.8936088] kern info [drm] failed to retrieve link info, disabling eDP
> [   3.8946299] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/io915/intel_guc_loader.c:560)guc_fw_fetcH] *ERROR* Failed to fetch GuC firmware fromk i915/kbl_guc_ver9_14.bin (error -2)
> [   3.8987335] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_gem.c:5417)i915_gem_init_hw] *ERROR* Failed to initialize GuC, error -5 (ignored)
> [   3.8998627] i915drmkms0: info: No connectors reported connected with modes
> [   3.8998627] kern info: [drm] Cannot find any crtc or sizes - going 1024x768
> [   3.9008587] intelfb0 at i915drmkms0
> [   3.9022339] wsdisplay1 at intelfb0 kbdmux 1
>
> At this point there is a little application-specific blather from
> userland (distinguishable because the kernel output is cyan and the
> userland output is white), into the middle of which is interjected
>
> [   4.8992338] kern info: [drm] RC6 on
>
> and I am told it's been stuck there for multiple days.
>
> Based on the userland output, I suspect it's wedged trying to start the
> X server, but I don't know why it's wedging rather than failing.
>
> I don't know enough about the 9.1 kernel support to really understand
> this (for example, the line aboiut VBIOS tables is cryptic to me).  It
> also appears to think this is Linux, blathering about initrd/initramfs
> (which, actually, would explain the horrible formatting - that looks
> very Linuxy to me - and the negative errors; I doubt it's complaining
> about EJUSTRETURN and EDUPFD, but ENOENT and EIO would actually make
> some amount of sense).
>
> Is this just a case of "hardware not yet supported", or is it more
> "you need this restricted-license binary firmware blob", or
> "something's broken, you should have $FOO in /some/path/$BAR", or "that
> code slipped through the convert-Linux-to-NetBSD net when it was
> checked in", or what?
>
> I would tend to assume that everything after the failure to load
> firmware is expected in view of that failure, but, as I said, I don't
> know this code enough to be confident of that.
>
> /~\ The ASCII                             Mouse
> \ / Ribbon Campaign
>  X  Against HTML                mouse%rodents-montreal.org@localhost
> / \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B
>


-- 
----