JustAnotherHumanBeing
commented
1 year ago This bug is also mentioned here: https://bugs.archlinux.org/task/70477 . I wonder if it's possible to modify the patch that was talked about on that page and apply it to the 5.10 branch of freebsd drm-kmod. Or maybe I could try to apply the unmodified patch to the 5.12 branch run by dumbbell?
I have the same issue this linux guy had when he was running linux-kernel ver 5.10: https://forums.gentoo.org/viewtopic-t-1136289-postdays-0-postorder-asc-start-0.html . The issue is "[drm] ERROR crtc 51: Can't calculate constants, dotclock = 0!" He was able to get rid of the issue after upgrading to linux-kernel-5.13. So, instead of waiting until freebsd drm-kmod gets updated and starts corresponding to version 5.13 of the linux kernel, maybe I could apply some quick fix to the current freebsd drm-kmod sources, so I would be able to get rid of this issue for my uhd 630 graphics/Asus motherboard combination? If such a quick fix exists, please show me what it is. Thank you.