From nobody Sat Jan 29 22:59:53 2022 X-Original-To: freebsd-current@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 78574199AAE1; Sat, 29 Jan 2022 22:59:56 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JmVCJ2CNjz3mJq; Sat, 29 Jan 2022 22:59:56 +0000 (UTC) (envelope-from se@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643497196; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=OGvSVKYjYzn1C5wS9Jd9xF+Hb+bHnvQR3X50d4fpSug=; b=l9v62YwgIiJmMyoCSgxPC9+sXrEzxgGvrz6bX4x80E59A9p1relmGoA+xdN+GWMuRBn93c HXp8kVmT188ly4u4LiabD+0pHHVOL94dckUVoixVXufZqrZIsMqnErkTWgLl8t5/mFE1S/ cLQ1FU9rvsmhddsJ9s4h0K7U5BaEDDOUA6ilw1PEI2sp+sUYi+WkhC731xSgDpDA21ifsf 3fWCGFIs6xopy8lc7GjWKMmoGkejIC9Xe3dsSdEcvgt5s48ORa3+0qGUanj2kL1p0vRbLp 83QziOVH9gZXm++SEwKl14QoegFSb7syPKZX/LujW27WuMpoMi03YiKw6JI9MQ== Received: from [IPV6:2003:cd:5f0c:9800:b50a:1ab6:2f63:fb85] (p200300cd5f0c9800b50a1ab62f63fb85.dip0.t-ipconnect.de [IPv6:2003:cd:5f0c:9800:b50a:1ab6:2f63:fb85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: se/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 9647B2E52F; Sat, 29 Jan 2022 22:59:55 +0000 (UTC) (envelope-from se@FreeBSD.org) Message-ID: Date: Sat, 29 Jan 2022 23:59:53 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.1 Subject: Latest drm-devel-kmod port not working? (was: Re: Kernel changes causing AMDGPU / DRM to fail? i2c related?) Content-Language: de-DE To: Tomoaki AOKI , x11@freebsd.org Cc: FreeBSD CURRENT References: <20220130072549.85a1365c78a5779238d72183@dec.sakura.ne.jp> From: Stefan Esser In-Reply-To: <20220130072549.85a1365c78a5779238d72183@dec.sakura.ne.jp> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------QLR7m6aktuDOmnFFnvgNa15V" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643497196; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=OGvSVKYjYzn1C5wS9Jd9xF+Hb+bHnvQR3X50d4fpSug=; b=Ejzfvms8zhQi+hGqmmfS34RIRA6DKqKM9/gfjdSL7CJ97HrpHaSK1nRYnvKulNutg6S9Ok 55SmmFcnJ4aOG5wsGrwNURyBUM73jk4jw7RhK0bR684VeAvNTKjYWVlb6LoKgyZDX0ayKa B8kAVH9STZE6qh8y/R2SV+QE39s5AuHHKV21hHWNQ7b79b+9bBYiH/M9b/+YoiAhBs2HVh FHLYTUXUafunbn+PfNqZ2HXtzWxnoECSQGoeb5NgvlMOsTgg7I/hjOHhfl4dX0zD+eWUNA n3kO6EzNH2M+Jn/xTDFeg0e0KyYjlGV0WUyaOvrhFqAddVHYsc8XnxMce7D8JA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1643497196; a=rsa-sha256; cv=none; b=fVBq2YFH5kayEbC4SGem+Ss+sOWItgUdOBbj8JUAC5vgYswqR95ytzIHd/Bp+xGZHEVtdA GEdIvO4bmRn1UtUWr1ZZxuiiwL2JNNt4PCTgi1IwCKoXEZoQizITEGTQy+d5EgvejLDT32 idzWdWZH6fExZ7QkmlQZ7R6wjtzB9E/OrH7OV9dLb0hk+wq2w/ejgM/JuLMB4CJ26FRLGL z6ymVNBtiuM1K7JiMwxpKFdnH09jBiucKD1HktEEYhuVOFHGhaninXQzUwB6kFcvKJxK1g 4m4ASM9joZ+JCvgzuvPQfateVVccTop21eT2VoYQdhfLSdgWQEY8p5IdirPTTQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------QLR7m6aktuDOmnFFnvgNa15V Content-Type: multipart/mixed; boundary="------------jsV0PxIPDTHgxFwXO60CNg0V"; protected-headers="v1" From: Stefan Esser To: Tomoaki AOKI , x11@freebsd.org Cc: FreeBSD CURRENT Message-ID: Subject: Latest drm-devel-kmod port not working? (was: Re: Kernel changes causing AMDGPU / DRM to fail? i2c related?) References: <20220130072549.85a1365c78a5779238d72183@dec.sakura.ne.jp> In-Reply-To: <20220130072549.85a1365c78a5779238d72183@dec.sakura.ne.jp> --------------jsV0PxIPDTHgxFwXO60CNg0V Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am 29.01.22 um 23:25 schrieb Tomoaki AOKI: > On Sat, 29 Jan 2022 22:25:17 +0100 > Stefan Esser wrote: >=20 >> After rebooting with freshly built world, kernel and the amdgpu driver= >> my console stopped working. It goes blank and the display goes into a >> power save mode, as soon as the amdgpu driver is loaded. >> >> The GPU (a Radeon R7 250E) is correctly detected as before, but there >> is an error message "drmn0: [drm] Cannot find any crtc or sizes". [...] > Are you sure your ports tree is up-to-date and graphics/drm-*-kmod > you installed (IIRC, should be needed for -intel and -amdgpu drivers) > is also updated? drm-*-kmod could be affected by LinuxKPI updates in > base. Yes, I rebuild the system from sources at least once a day, but do only reboot every few days, especially if there has been any change that might cause incompatibilities between kernel and user land. And I always rebuild all KLDs together with the kernel, including all the driver module ports relevant for X11. > *There can be some (sometime very wide) timeframe between LinuxKPI > update and corresponding linux-*-kmod catches up with it. X11 was working just fine on a system built and rebooted a few days ago. > Looking into cgit.freebsd.org, at least drm-current-kmod is updated 36 > hours ago. Not sure it's related or not, though. I had missed that update - and YES you are right. I'm using the devel version and after reverting the update to drm_v5.5.19_7 the driver does attach again. Thanks for the hint! > *I always prefer nvidia dGPU because of these dangerous span. > So I've forced to choose ThinkPad P series (without "s") which > usually can disable CPU-integrated Intel GPU and run nvidia GPU > alone though BIOS setting. I had issues with Nvidia cards (and the closed source driver modules and libraries) before and for that reason bought a passively cooled Radeon card for this development workstation. Best regards, STefan --------------jsV0PxIPDTHgxFwXO60CNg0V-- --------------QLR7m6aktuDOmnFFnvgNa15V Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAmH1xukFAwAAAAAACgkQR+u171r99UTZ IAf/eBuIpV5aLt/NMvZE6O6J2PoTxYIZj3199fhKCE/5tFJtICSMK6lrxacJDkJ0KRf5IIto92io f6g4Fmxs+EokcOUXAlb9ZVvlTOKrKDWWxAdqX9uErHjFCHInFT3INUFrSHIncBiCJdndqAb/B7Ut O46fa8POKWKqtwxzmWZyydyU0N3sA8/222dVxvl7tGZRa7ti1fhCQXs50vDYNObte0J1+GjIcDDD M6gFvhok2oexMGK87dvtSA9AD4Q4oMqSGUmpyhHMDdHy/R+Xz0SmNtk6w/mtpeb45wx9JDbQ8YR8 kdaU7fMhR7wC58SWL95NdCZ+4u3aoMVxe8+I0LrttA== =pMRs -----END PGP SIGNATURE----- --------------QLR7m6aktuDOmnFFnvgNa15V--