Re: Issues with intelfb(4) and USB keyboards

[RVP <rvp%SDF.ORG@localhost>]

On Sat, 19 Dec 2020, Brian Buhrow wrote:

> 	hello.  Thanks for the quick explanation.  It still doesn't work, but the errors are different.
> Any ideas what to try next?  How does one set the dot clock?
>
> [     7.099124] warning: ../../../../external/bsd/drm2/dist/drm/i915/i915_drv.c:591: WARN_ON(!IS_KABYLAKE(dev_priv))kern info: [drm] Memory usable by graphics device = 4096M
> [     7.111382] kern info: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [     7.119122] kern info: [drm] Driver supports precise vblank timestamp query.
> [     7.139122] kern info: [drm] failed to find VBIOS tables
> [     7.159122] i915drmkms0: interrupting at ioapic0 pin 16 (i915drmkms0)
> [     7.169123] kern error: [drm:(../../../../external/bsd/drm2/dist/drm/drm_irq.c:810)drm_calc_timestamping_constants] *ERROR* crtc 21: Can't calculate constants, dotclock = 0!
> [     7.169123] warning: ../../../../external/bsd/drm2/dist/drm/i915/intel_pm.c:3276: WARN_ON(p->pixel_rate == 0)intelfb0 at i915drmkms0
> [     7.199122] intelfb0: framebuffer at 0xffff8e0139e14000, size 1280x1024, depth 32, stride 5120
> [     8.009123] kern error: [drm:(../../../../external/bsd/drm2/dist/drm/i915/intel_dp.c:3797)intel_dp_link_training_clock_recovery] *ERROR* too many full retries, give up
> [     8.049123] kern error: [drm:(../../../../external/bsd/drm2/dist/drm/i915/intel_dp.c:3797)intel_dp_link_training_clock_recovery] *ERROR* too many full retries, give up
> [     8.079128] kern error: [drm:(../../../../external/bsd/drm2/dist/drm/i915/intel_dp.c:3797)intel_dp_link_training_clock_recovery] *ERROR* too many full retries, give up
> [     8.119123] kern error: [drm:(../../../../external/bsd/drm2/dist/drm/i915/intel_dp.c:3797)intel_dp_link_training_clock_recovery] *ERROR* too many full retries, give up
> [     8.159124] kern error: [drm:(../../../../external/bsd/drm2/dist/drm/i915/intel_dp.c:3797)intel_dp_link_training_clock_recovery] *ERROR* too many full retries, give up
> [     8.199143] kern info: [drm] RC6 on
> [     8.199143] kern error: [drm:(../../../../external/bsd/drm2/dist/drm/i915/intel_dp.c:3797)intel_dp_link_training_clock_recovery] *ERROR* too many full retries, give up
> [     8.249123] kern error: [drm:(../../../../external/bsd/drm2/dist/drm/i915/intel_dp.c:3797)intel_dp_link_training_clock_recovery] *ERROR* too many full retries, give up
> [     8.249123] kern error: [drm:(../../../../external/bsd/drm2/dist/drm/i915/intel_dp.c:3868)intel_dp_link_training_channel_equalization] *ERROR* failed to train DP, aborting

So, the firmware got loaded OK.

You shouldn't need to set the dot clocks--the CRT, unless it is a
very old one, should respond to an EDID query and supply the correct
display-timing info back to the driver. Is the monitor OK?

If it isn't a CRT issue, then I don't know how to make the DRMKMS
driver use a custom modeline.

Suggestions:

1. Try the latest -HEAD build. It may have fixes.

2. Try `genfb/wsfb'--the generic framebuffer and the X driver which
runs on top of `genfb'. Disable i915drmkms using the userconf facility:

https://mail-index.netbsd.org/tech-x11/2020/12/10/msg002183.html

-RVP