From nobody Tue Dec 06 07:08:40 2022 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4NRBNF4Rl1z4k4M0 for ; Tue, 6 Dec 2022 07:08:45 +0000 (UTC) (envelope-from pat@patmaddox.com) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4NRBND6TY0z400x for ; Tue, 6 Dec 2022 07:08:44 +0000 (UTC) (envelope-from pat@patmaddox.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=patmaddox.com header.s=fm3 header.b="c cP5Uoq"; dkim=pass header.d=messagingengine.com header.s=fm1 header.b="f PE3YvO"; spf=pass (mx1.freebsd.org: domain of pat@patmaddox.com designates 64.147.123.24 as permitted sender) smtp.mailfrom=pat@patmaddox.com; dmarc=none Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 872C93200918; Tue, 6 Dec 2022 02:08:43 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 06 Dec 2022 02:08:43 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=patmaddox.com; h=cc:cc:content-transfer-encoding:content-type:date:date:from :from:in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; t=1670310523; x= 1670396923; bh=RwVMM8lrCzOKSxU/2yyAoUffeH49/vPhJNB3K/zOhHo=; b=c cP5Uoqa+aDbqN81wd0R3TwA9MkMOvnzlbeIuhCtnVaQFbprnS4SKrde1Tf+axvdm U/8UZeo3EAf7R+FEobDn22+oxy9Pqz+E3+dFwcNknsU+MwYUDgTQfB/HcvmlCNr2 iGbfdjyOZ/HTleUQFWOMjzL6pUjO6/culfwYO6XvPHLiEpPSyU/jMdRyQe6sLS27 yP1LBGS+QHLgDC19T8aNND4qSjTNQivaF5nuQYZafh153o6fMCxo8mZhmNNkU6yF 1QafezklUN6G5HipvJaLozYi1gQCIw5VvfwrKJ/2g9ln1bTtpRV+K9tSuRjDHUJY nc0OaHplD6OgvzVBPBIWw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1670310523; x= 1670396923; bh=RwVMM8lrCzOKSxU/2yyAoUffeH49/vPhJNB3K/zOhHo=; b=f PE3YvOXkZtam4VpBCAcAEGR3FtFtkpTavxIWxUYcfq7G9h0oIww66/Sq1+N8laQG Fz52Md2Buend5ZVrRZem9/oosBmrflRlVL5xDHEH5UjeYVXMNOeqvZEWIBqXOIpR dCMdRW7ssbWoG1Uu0y9eVamPvpKAkqH087LMSiHkllKJdmCpRLXneBjR84f/aOPg jJxiC/dHbUokVM8qFdWBRpn18FlFUOgluMgIiMVrxnhjWkZaFOJGp0ZmSwtyHyUd ZfrbYpj/sut9eVaVxxNrqyVkTFtmJNuvzgtuQ+3NAmBAHBKjWautMFIs0bB0DjTq 6YaTnslBaTnuMBk11hvsQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudehgddutdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffokfgjfhggtgfgsehtqhhmtdertdejnecuhfhrohhmpedfrfgr thcuofgrugguohigfdcuoehprghtsehprghtmhgrugguohigrdgtohhmqeenucggtffrrg htthgvrhhnpeehgedtveeggfdtfedvveekieejfeefieeggedvudfhfeeluddvueegfeet iedvvdenucffohhmrghinhepuhhrlhguvghfvghnshgvrdgtohhmpdhfrhgvvggsshgurd horhhgpdhgihhthhhusgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgr mhepmhgrihhlfhhrohhmpehprghtsehprghtmhgrugguohigrdgtohhm X-ME-Proxy: Feedback-ID: i8b6c40f9:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 6 Dec 2022 02:08:42 -0500 (EST) From: "Pat Maddox" To: "Takanori Watanabe" Cc: freebsd-hackers@freebsd.org Subject: Re: kldload i915kms screen goes black Date: Mon, 05 Dec 2022 23:08:40 -0800 X-Mailer: MailMate (1.13.2r5673) 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> <3EE88B08-395F-47A1-B25B-E89C2B076654@patmaddox.com> <19286A43-0F72-4DA3-AF92-60E8BD11F7D7@patmaddox.com> List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-4.60 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[patmaddox.com:s=fm3,messagingengine.com:s=fm1]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.24]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.24:from]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DMARC_NA(0.00)[patmaddox.com]; FREEFALL_USER(0.00)[pat]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[patmaddox.com:+,messagingengine.com:+]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; RCVD_TLS_LAST(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[64.147.123.24:from] X-Rspamd-Queue-Id: 4NRBND6TY0z400x X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N 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