From nobody Tue Apr 19 16:02:04 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 2A25711E233E for ; Tue, 19 Apr 2022 16:02:19 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.ipv6.vt.edu [IPv6:2001:468:c80:a103:2:5000:5555:5555]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4KjT8T60Mdz3Mgk for ; Tue, 19 Apr 2022 16:02:17 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from smtpclient.apple (unknown [IPv6:2001:470:e15b:23::23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 70B8C45537; Tue, 19 Apr 2022 12:02:05 -0400 (EDT) Content-Type: text/plain; charset=us-ascii 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 (Mac OS X Mail 16.0 \(3696.80.82.1.1\)) Subject: Re: advice sought: workflow with -CURRENT and amd GPU [Re: -CURRENT hangs since at least 2022-04-04] From: Paul Mather In-Reply-To: Date: Tue, 19 Apr 2022 12:02:04 -0400 Cc: Michael Schuster Content-Transfer-Encoding: quoted-printable Message-Id: References: <0c1b4885-dd0f-b48f-2ffe-12ccfd2ec118@filis.org> <3b85072c-eb07-6a74-fae3-258c99756c11@nomadlogic.org> To: FreeBSD CURRENT X-Mailer: Apple Mail (2.3696.80.82.1.1) X-Rspamd-Queue-Id: 4KjT8T60Mdz3Mgk X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=vt.edu (policy=none); spf=none (mx1.freebsd.org: domain of paul@gromit.dlib.vt.edu has no SPF policy when checking 2001:468:c80:a103:2:5000:5555:5555) smtp.mailfrom=paul@gromit.dlib.vt.edu X-Spamd-Result: default: False [-2.18 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[vt.edu : No valid SPF, No valid DKIM,none]; FREEFALL_USER(0.00)[paul]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-0.99)[-0.989]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-0.96)[-0.958]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-0.73)[-0.730]; MLMMJ_DEST(0.00)[freebsd-current]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:1312, ipnet:2001:468:c80::/48, country:US]; FREEMAIL_CC(0.00)[gmail.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N On Apr 19, 2022, at 4:49 AM, Michael Schuster = wrote: > Hi, >=20 > I'm highjacking and re-purposing the previous thread, I hope that's OK > (I did change the subject ;-)) - I'm keeping some of the previous > contents for reference. >=20 > I have similar HW to OP (Ryzen 7 4700 w. Renoir Graphics), and have > been using a similar approach to keep the machine up to date - or so I > suspect. Still, after a while (several months), I end up with one or > more of these: > - I get some sort of panic in DRM (at startup or, currently, at = shutdown) > - when I boot into to a previous BE to attempt a fix and then again > reboot into the current one, I get tons of messages like this > "... kernel: KLD iic.ko: depends on kernel - not available or > version mismatch > ... kernel: linker_load_file: /boot/kernel/iic.ko - unsupported = file type" > and computer refuses to accept input (let alone start X) >=20 > and some others I don't recall right now. >=20 > Before I ask for advice (see below), let me explain the approaches > I've taken so far. I install with ZFS from the beginning, current boot > env is "N". These are outlines, not exact commands: >=20 > I) never touch the current BE, always update a new one: > 1) given current BE N, I create a new BE N+1 and mount it on /mnt, > 2) 'cd /usr/src; git pull; sudo make DESTDIR=3D/mnt ... (build, = install, etc)' > 3) 'cd usr/ports/graphics/drm-devel-kmod; sudo make DESTDIR=3D/mnt = install' > 4) beadm activate BE N+1; reboot >=20 > II) keep a "new" BE as backup/fallback, update current BE: > 1) given current BE N, I create a new BE N+1 (mounting not required) > (this is the intended 'fallback') > 2) 'cd /usr/src; git pull"; then "make" as described in the Handbook > "24.6. Updating FreeBSD from Source" > 3) 'cd usr/ports/graphics/drm-devel-kmod; sudo make install' > 4) reboot >=20 > in both scenarios(sp?), I do "pkg update; pkg upgrade" from time to > time (also following the resp. approach shown above). >=20 > I suspect that I'm missing something fundamental in my approaches - > does anyone have a (for them) foolproof approach along these lines, or > can someone show me what I'm missing in either of mine (in private, if > you prefer)? I don't know whether you're missing anything, but I wanted to mention I recently found a tool useful in helping my own BE-based source upgrades: /usr/src/tools/build/beinstall.sh I've found it helps with the build/upgrade steps. See man beinstall(8) for details. Cheers, Paul.