Date: Mon, 05 Dec 2022 23:08:40 -0800 From: "Pat Maddox" <pat@patmaddox.com> To: "Takanori Watanabe" <takawata@init-main.com> Cc: freebsd-hackers@freebsd.org Subject: Re: kldload i915kms screen goes black Message-ID: <553FF6AA-4786-4DEA-9C4B-B2F28914BF72@patmaddox.com> In-Reply-To: <19286A43-0F72-4DA3-AF92-60E8BD11F7D7@patmaddox.com> References: <2CFF7511-C45A-4986-8881-2A68DC52F555@patmaddox.com> <PH0PR19MB49383025CD74B8621A7D83989E1B9@PH0PR19MB4938.namprd19.prod.outlook.com> <3EE88B08-395F-47A1-B25B-E89C2B076654@patmaddox.com> <Y47Qp41kGd%2BrsZHa@sana.init-main.com> <19286A43-0F72-4DA3-AF92-60E8BD11F7D7@patmaddox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5 Dec 2022, at 22:18, Pat Maddox wrote: > On 5 Dec 2022, at 21:18, Takanori Watanabe wrote: > >> On Mon, Dec 05, 2022 at 09:43:17PM -0800, Pat Maddox wrote: >>> On 5 Dec 2022, at 20:55, Chen, Alvin W wrote: >>> >>>>> >>>>> I have a newly-built system with an ASUS Prime Z590M-Plus and = >>>>> Intel >>>>> 10900k >>>>> with onboard graphics (UHD 630, according to intel). >>>>> >>>>> I specifically chose a 10th gen processor because I believed it = >>>>> was >>>>> well- >>>>> supported by 13.1+. Unfortunately I can=E2=80=99t even install 13.1= >>>>> (https://urldefense.com/v3/__https://forums.freebsd.org/threads/can= t- >>>>> install-i-just-get-a-little-white-box-and-a-mouse- >>>>> cursor.87334/__;!!LpKI!iRRMC3ef9hbS1NKXTBUoIDxlVz9pU_m1Jocnzh2Tlxfd= >>>>> s5SnkbHHXEM4iKqU7weuEiObV8rfJXfY$ [forums[.]freebsd[.]org]) >>>>> >>>>> I have successfully installed >>>>> FreeBSD-14.0-CURRENT-amd64-20221201-d1f3abc89250-259495. >>>>> >>>>> When I run `kldload i915kms`, the screen just goes black. >>>>> >>>>> I have never used graphics before on FreeBSD, so I=E2=80=99m not su= re = >>>>> where >>>>> to >>>>> begin diagnosing. I did as much research as I could upfront, but = >>>>> have >>>>> run into >>>>> this obstacle. >>>>> >>>>> I=E2=80=99ll be content to run 14.0-CURRENT because I can still cre= ate = >>>>> 13.1 >>>>> jails. >> >> How about logging in from remote and load kernel module? >> This is my example. >> https://github.com/freebsd/drm-kmod/issues/159 > > When I do that, the screen still goes black, but kldload does return = > in my remote terminal. This is in /var/log/messages: = > https://gist.github.com/patmaddox/1a2b7bb8769cf1251beb514a9646a69e Well, I don=E2=80=99t know if this has anything to do with anything, but = when = I run `pkg install drm-kmod` it lists all of these intel bits: gpu-firmware-intel-kmod-broxton: 20220511 gpu-firmware-intel-kmod-coffeelake: 20220511 gpu-firmware-intel-kmod-elkhartlake: 20220511 gpu-firmware-intel-kmod-geminilake: 20220511 gpu-firmware-intel-kmod-icelake: 20220511 gpu-firmware-intel-kmod-kabylake: 20220511 gpu-firmware-intel-kmod-rocketlake: 20220511 gpu-firmware-intel-kmod-skylake: 20220511 gpu-firmware-intel-kmod-tigerlake: 20220511 My 10th gen i9 is a =E2=80=9Ccomet lake=E2=80=9D - not in the list. I=E2=80= =99m not sure = if it should be covered by a different one, but it is interesting that = it=E2=80=99s absent. drm-kmod has a bunch of references to cometlake: = https://github.com/freebsd/drm-kmod/search?q=3Dcometlake But drm-kmod-firmware does not: = https://github.com/freebsd/drm-kmod-firmware/search?q=3Dcometlake I did make an effort to support a cometlake flavor: = https://github.com/patmaddox/drm-kmod-firmware/commit/20570f61ee927e19d5f= d6303f94eac00aa2f3bfd But it didn=E2=80=99t work, which is no surprise, because I have no idea = what = I=E2=80=99m doing when it comes to kernel drivers. Does the fact that cometlake is absent from the list mean 1) it was an = oversight 2) it=E2=80=99s not supported 3) nothing at all? Pat
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?553FF6AA-4786-4DEA-9C4B-B2F28914BF72>