From nobody Sun May 28 05:18:24 2023 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 4QTRlB134jz4XLDx for ; Sun, 28 May 2023 05:18:30 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QTRl91g8fz4bm6; Sun, 28 May 2023 05:18:29 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=IjsqubWy; spf=pass (mx1.freebsd.org: domain of yaneurabeya@gmail.com designates 2607:f8b0:4864:20::62a as permitted sender) smtp.mailfrom=yaneurabeya@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-pl1-x62a.google.com with SMTP id d9443c01a7336-1ae763f9c0bso14839695ad.2; Sat, 27 May 2023 22:18:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685251107; x=1687843107; h=to:cc:date:message-id:subject:mime-version:from:from:to:cc:subject :date:message-id:reply-to; bh=k/oJbO3hJDmhCiS0iX8a8TRwnqMm9hICQO2pHoFNx1A=; b=IjsqubWy111Glw9MRAaFSiZ1FmNtmDLWrGz8OFjmInZQBOvUyoQs0tzzlxdop0GE42 axWjJAJ/2lfoCjHxrbjdEpCooR2bGfTtTLOZ3vs/IjSN3ef8FA7woVSdEr6eu7r9L9Wc N9mKeLqqcTM8MmH9UHVEK70KYOJWkaxQ8S5Saf+hE+hfmg2dSAv2eVyWVBOsXPpGydfs vCvx/gDvU/QA2XjIE29M+nj2opaGnnp8q7eTfauQ+K1SanUcjflUz6AIiTIYxRUWC21V k8LYTkQSJCI4BfLJC0pNRC1GFCDDjJVJTLSG745+aKfvxar8Wt8fnTuenhT1KpBm8nVo FScA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685251107; x=1687843107; h=to:cc:date:message-id:subject:mime-version:from:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=k/oJbO3hJDmhCiS0iX8a8TRwnqMm9hICQO2pHoFNx1A=; b=SbkLwVa4vN4uQdmJWG7V5XxXILtyZUd3BdqctQ687Gb+mtDfPld/aqwwsyog5WiNvZ zRajse/CNY+IRaMEfeCDxFw/4WzDvmxyEfpq8iP+aqjYR+01ku+zeB5CBpTRtM/FHxtR 2qq1dLKV6Gi6pUxWbKiLXSzrAjxXz7QBa/0NxIZjbOfBDQ+jmcf/OtBaqxzwBIoKi3rw hlLKZxg3WpSUXOZwdAv5jbHEAiOHQ95KwPsDWhM3XzJQdrUmRLy3402pOy3sl4XblZ/5 kBD4p5Z+Z9EvBingeyNzivlmnmSvrk3fnJFgA2TXVrPg2Twef/PpOdCLWVMdj0UbMSlC U6qg== X-Gm-Message-State: AC+VfDxruFli9t5Muk+QqSKzvL0BaGgQYH5GhbyCv7spmgqjPZNNVc73 JVNbUjBYKh4O4YkmoPhiVNMr1o0inJfSEQ== X-Google-Smtp-Source: ACHHUZ4do0BpliepSe4185B8wyi9Gm+dZOu66KBEvMatxFQh6QxuCtot7X6Emjni3t+hwnxnVXSwSA== X-Received: by 2002:a17:902:d2cf:b0:1ae:1237:8754 with SMTP id n15-20020a170902d2cf00b001ae12378754mr9277517plc.68.1685251107175; Sat, 27 May 2023 22:18:27 -0700 (PDT) Received: from smtpclient.apple (c-73-19-52-228.hsd1.wa.comcast.net. [73.19.52.228]) by smtp.gmail.com with ESMTPSA id b10-20020a170902d88a00b001aaecc15d66sm5655791plz.289.2023.05.27.22.18.26 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 27 May 2023 22:18:26 -0700 (PDT) From: Enji Cooper Content-Type: multipart/signed; boundary="Apple-Mail=_03B6F014-F320-4F2F-9F3E-5CE01D401001"; protocol="application/pgp-signature"; micalg=pgp-sha256 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.120.41.1.3\)) Subject: "make hierarchy" from main tree breaks c++ headers on older branches with unclear errors if "make install world" is interrupted Message-Id: Date: Sat, 27 May 2023 22:18:24 -0700 Cc: Dimitry Andric To: FreeBSD Current X-Mailer: Apple Mail (2.3696.120.41.1.3) X-Spamd-Result: default: False [-5.55 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.95)[-0.948]; MV_CASE(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; ARC_NA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; HAS_ATTACHMENT(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; DKIM_TRACE(0.00)[gmail.com:+]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::62a:from]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org] X-Rspamd-Queue-Id: 4QTRl91g8fz4bm6 X-Spamd-Bar: ----- X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_03B6F014-F320-4F2F-9F3E-5CE01D401001 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi all, I just tried to run =E2=80=9Cmake hierarchy=E2=80=9D from a main = tree on a 13.2-RELEASE system, and doing so completely broke my headers. It took me about 30 minutes to figure out what happened=E2=80=A6 = /usr/include/c++/v1/__string was a header, whereas on :main it=E2=80=99s = a directory?! $ git diff freebsd/releng/13.2 main -- etc/mtree/BSD.include.dist) ... @@ -47,8 +53,12 @@ .. __ranges .. + __string + .. __thread .. + __type_traits + .. __utility .. __variant @@ -202,6 +212,8 @@ ... $ make hierarchy seems to wipe out the file and replace it with a = directory, which I guess isn=E2=80=99t terribly confusing since it=E2=80=99= s just an unlink, but the error messages that followed from c++ was = confusing; the error message of note was the first part saying __string = was missing =E2=80=94 the rest was just garbage complaints about C++20 = extensions, e.g., :9:5: warning: use of function template name with no prior = declaration in function call with explicit template arguments is a C++20 = extension [-Wc++20-extensions] I reinstalled the headers by going to lib/libc++ in my = releng/13.2 tree, building, and installing all of the 13.2-RELEASE = headers. This change has been live for almost a year now on :main =E2=80=94= is this a known caveat when doing a source-based upgrade from = 13.2-RELEASE* to 14.0-CURRENT, i.e., that the installworld (if = interrupted) could break the c++ compiler? Thank you, -Enji $ git blame etc/mtree/BSD.include.dist ... 81ad626541db9 (Dimitry Andric 2022-07-04 21:20:19 +0200 56) = __string 81ad626541db9 (Dimitry Andric 2022-07-04 21:20:19 +0200 57) = .. ... $ git log 81ad626541db9^..81ad626541db9 commit 81ad626541db97eb356e2c1d4a20eb2a26a766ab Merge: 5fff09660e06 145449b1e420 Author: Dimitry Andric Date: Mon Jul 4 21:20:19 2022 +0200 Merge llvm-project main llvmorg-15-init-15358-g53dc0f10787 This updates llvm, clang, compiler-rt, libc++, libunwind, lld, lldb = and openmp to llvmorg-15-init-15358-g53dc0f10787. PR: 265425 MFC after: 2 weeks commit 145449b1e420787bb99721a429341fa6be3adfb6 (tag: = vendor/llvm-project/llvmorg-15-init-15358-g53dc0f107877) Author: Dimitry Andric Date: Sun Jul 3 16:10:23 2022 +0200 Vendor import of llvm-project main = llvmorg-15-init-15358-g53dc0f107877. --Apple-Mail=_03B6F014-F320-4F2F-9F3E-5CE01D401001 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEtvtxN6kOllEF3nmX5JFNMZeDGN4FAmRy5CEACgkQ5JFNMZeD GN7b2RAAlDTMcKDKVqzmA2H1Ghs9kob4itqlG4r+1/1S/kZNZvcp6JbNwVZxyc+p 09zRjt8otyZ13hlNsLZnCOQpN76KRytqtd9z0voza9nsQ3vW1HFzv0mLfTSodTxm CE5rahNQLYSaeojTd6mixlk9jefXt8y4EUJDNS9vxXZk0iSKAICvAod1Pr/KwlLZ hQfqmX1MdTHF3kgG456BSA3/Ymb01Ric01JVlD9guyLfJToO9aE342W/07KqYr/L WTbQFRc2kGzQnbulUmDn51//Zg/m7T7kviBt47KEQrv6hEqnD99oEGCAK55y/iva L8IUpxHOZ2rMBJFDEtt4Hruqhl3oCwwsJlr15+Zd03SZZPHnQfc/umYuM7N/t83E 9lLgPd1LhEipPf2xPbeJ/lvjoTIj0GCGekhG8K4Qs2SHvnmQnPFs8Jjy5qnFTABX Vvpr8+lTzvsmgGLeaDZqIvjxxQwCEKsoRVI8c4KhZcdaCrmMdbfRLkeY8DNG+wEP H+6dsGxTyfnkxp62ByueXDb0l8GO8qTh2SDTl/+AKY3cbaKPUXJpXvaD1kCAbqRq zXa2/bVA0Zj7kCulQVCzDBbSzz48q/Z0ABTn9oRndAKhawcdyG8KhggB019t9HUV sWjWkxkIfkvFV4UW0RWnaGk7dQmwQ4ZLdgLTCMpnAX8dqrBH8G0= =prPX -----END PGP SIGNATURE----- --Apple-Mail=_03B6F014-F320-4F2F-9F3E-5CE01D401001-- From nobody Sun May 28 10:53:15 2023 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 4QTb9m6cdKz4XDCg for ; Sun, 28 May 2023 10:53:32 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 4QTb9m623Bz3pyZ; Sun, 28 May 2023 10:53:32 +0000 (UTC) (envelope-from dim@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685271212; 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=pF3KeIQc2QSODgUdaGaNzWOrpwheKRheDSJrDQ5CKxc=; b=gPHHBJsZVkHRT2FtuYC2CGoYAUIzPpPaZNgH5oZXuOlxpDBg74ylq+2BAnfSq+BdX+EHCV YQAJChDCTwU7Tfda7fpcl+eE+MHoxnmGRoNasFbkvqo6PWks1Zf+kKImzIar/UJCzvKouj FZlD5ONrOrzo4yDSZ56hqanAaOPNlrhmWOeyFjH30b5Hdhw5SgMC7by1BUovrlFIGhSd5E 7VvP9Pz7EUymBfrblq+1uraY7LC7lPfr2WlkEYni5z0y83x0WXAwFlqNryHA7NJcohg/ue Bsxfbxg0rilJFSn1sLWSltRwiMz+KbKqpddfv8hNvRiSR6CvsFPzwVg2YVXCEw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685271212; 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=pF3KeIQc2QSODgUdaGaNzWOrpwheKRheDSJrDQ5CKxc=; b=H/gTca1OH8tIF2zgU6JD2fRTwQsITYxGGElQG4rdTX4WwUYCn8pxYlPW0Ajwl8hurf7z9j q6+Lrr/u18Ivh8nrWdIeNOZzgODT7gb26Gc+8R2k4z+M4rERAvrSatUtT+BOu/gEDOuFp2 tpmYJI+166+A8f7Ok2RiRn8Zun/czfmzn05jw4ODiyS1Ww20tlEhXHKZ5YwMwybeDRl8rO wItaah2UR6KHtdxKfrBnSlA1kaj6litzC6t3M/vEmfRIOaroHEGHx2Aw0Shtp1veLJoJ63 zaJ3ucI6LAxv//ZB4d25OoPCoFBqgoiPkxOx/6AzP9QB0F5oGCzuIZEhZl9x1w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1685271212; a=rsa-sha256; cv=none; b=Cv6Ezt22o0dUyaBkBTzoJA0cgkz2wFyoIHioqlWjIXX0qQcsEI1rYTZyKviiQ/H4WUyv8I iblMo7eqA1g5UXIBGY3pT87ijL7ARhCzw8dbQvEsNN7xbFh78hOqQazOeMus87O+SGVL29 qezpX3AWP3Nbc5HwGNolr5/HqZ7N8yxgGHBkZpYaiXNumzA12/KPkx1utPF5SOIA8eMJ77 0Hv1O37AUwqI7x2k79t9d7hlta7fG8nXIvIy/qTRAAS1rkaOvsd2HcKe/vzlTJJYt3iDZw y6igCIRLLvXdLBnBQ69ksBh2H1LBUXlLeiAQN5tdjo2WVx4xjtSBI5E7kbDcMg== Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (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 (2048 bits) client-digest SHA256) (Client CN "tensor.andric.com", Issuer "R3" (verified OK)) (Authenticated sender: dim) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QTb9m4Nf3zdb6; Sun, 28 May 2023 10:53:32 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from smtpclient.apple (longrow.home.andric.com [192.168.0.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id E5F624FFEB; Sun, 28 May 2023 12:53:30 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_F0A5DA72-7432-4EFC-B48C-F5618FB16633"; protocol="application/pgp-signature"; micalg=pgp-sha1 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 \(3731.600.7\)) Subject: Re: "make hierarchy" from main tree breaks c++ headers on older branches with unclear errors if "make install world" is interrupted From: Dimitry Andric In-Reply-To: Date: Sun, 28 May 2023 12:53:15 +0200 Cc: FreeBSD Current Message-Id: <0DA92266-62F8-439E-9C56-44106A6B0073@FreeBSD.org> References: To: Enji Cooper X-Mailer: Apple Mail (2.3731.600.7) X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_F0A5DA72-7432-4EFC-B48C-F5618FB16633 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On 28 May 2023, at 07:18, Enji Cooper wrote: >=20 > I just tried to run =E2=80=9Cmake hierarchy=E2=80=9D from a main tree = on a 13.2-RELEASE system, and doing so completely broke my headers. > It took me about 30 minutes to figure out what happened=E2=80=A6 = /usr/include/c++/v1/__string was a header, whereas on :main it=E2=80=99s = a directory?! Yes, upstream libc++ has split up large headers into multiple = components, in particular __string and __type_traits. Since we had a file named __string, it had to be somehow replaced by a = directory. This is what the distrib-cleanup target in the top-level = Makefile does: https://github.com/DimitryAndric/freebsd-src/commit/6b13b4a095e3 Afterwards, the replacement directory named __string is created as part = of the regular mtree commands. ... > I reinstalled the headers by going to lib/libc++ in my releng/13.2 = tree, building, and installing all of the 13.2-RELEASE headers. > This change has been live for almost a year now on :main =E2=80=94 is = this a known caveat when doing a source-based upgrade from 13.2-RELEASE* = to 14.0-CURRENT, i.e., that the installworld (if interrupted) could = break the c++ compiler? I think it should already be quite clear that interrupting installworld = is risky. If you were just in the middle of replacing libc or rtld, and = those were half-written, your system will be completely hosed. (I am = speaking from experience. :) The same goes for any system headers or = libraries, not only the C++ ones. If you have a half-installed tree, it = should not be used for anything except attempting another installworld. -Dimitry --Apple-Mail=_F0A5DA72-7432-4EFC-B48C-F5618FB16633 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCZHMymwAKCRCwXqMKLiCW o3ObAKCWU9dC7rMvTRTOf28qefpoWbKdwwCfc6JlfgTotbzLVh+Ew6ztHRpY4RE= =UBb8 -----END PGP SIGNATURE----- --Apple-Mail=_F0A5DA72-7432-4EFC-B48C-F5618FB16633-- From nobody Sun May 28 12:44:59 2023 X-Original-To: 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 4QTdfn5LXrz4XLRP; Sun, 28 May 2023 12:45:21 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [IPv6:2a01:4f8:1c1c:11e5::1]) (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 4QTdfn0dlCz42CZ; Sun, 28 May 2023 12:45:21 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; none Received: from mail (mail [IPv6:fd5c:5351:d272::3]) by mail.madpilot.net (Postfix) with ESMTP id 4QTdfc0nXTz6wCt; Sun, 28 May 2023 14:45:12 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :subject:subject:from:from:content-language:references:date:date :message-id:received; s=bjowvop61wgh; t=1685277897; x= 1687092298; bh=v2aG55yGD2DmtVs2gyaBIdmcUJsR42Ljc/xpfRc7PVg=; b=K Tc+1Ff5W3Tl3N8WEQzll8caxSooVEusNTBN5WUfJ6tg1le7jjIH7UoA4q48kShIp bIy9J6MFcdRgv9++MoGCUdc9EWU0+3hG3Ez0xfMKT6rCTTjGCldg45r44znD9UyW aHVO2B9fmBvPqinDolkZiANcvCHgjPEjokAXncgWW0GYGJlPrsG0Zb0YCLygKI2s fiIDaoQ4xm0jQJhpYMVZxnTPUWxV32Y+1bDEh0jNL8qgzjNKg6AH27jN3JwJOB9I 0I52gXU4+g0IffzpKGG+aeQ5IM+mmefRAfRGLAyvic0zK1cRq68CQhlfyf9YXSUl Pc5XL5J/dR3KHEldDdkRg== Received: from mail.madpilot.net ([IPv6:fd5c:5351:d272::3]) by mail (mail.madpilot.net [IPv6:fd5c:5351:d272::3]) (amavisd-new, port 10026) with ESMTP id IVVO3DX7oWOi; Sun, 28 May 2023 14:44:57 +0200 (CEST) Message-ID: <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> Date: Sun, 28 May 2023 14:44:59 +0200 To: Alastair Hogge , freebsd-current@freebsd.org, current@FreeBSD.org, freebsd-x11@freebsd.org References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> Content-Language: en-US From: Guido Falsi Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head In-Reply-To: <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4QTdfn0dlCz42CZ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/32, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N 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 On 28/05/23 00:42, Alastair Hogge wrote: > Hello, > > Is there some way to test your X session with minimum components, and > slowly adding whatever XFCE does? Maybe I was not perfectly clear. Xorg works fine, I already tested with another window manager. The only thing that changed is that I updated to more recent head, updated a bunch of ports (none directly related to Xorg/DRI3) and xfwm4 started crashing with the errors I reported. Everything else seems to work fine (except other xfce components that depend on xfwm4, which show various degrees of bad behavior caused by xfwm4 not running). xfwm4 was NOT updated or reinstalled. > > I would switch from using a X Display Manager, and launch X from the > login vty using startx (if not already ), with a minimum .xinitrc. I > would find out what is needed to get a minimal XFCE going, for example, > maybe just the Window Manager, no Compositor, or nothing at all to see > if X handles the display mode setting at all. As I said this is something already easily tested. Everything works except xfwm4 crashes on startup if DRI3 is enabled. I am reasonably sure xfwm4 would not crash if compiled without compositor support, since the crash happens in code that is protected by ifdefs and would be removed is disabling compositor. That should would also not run if disabling the compositor, so I'm reasonably sure that would be another possible (but even uglier than disabling DRI3) workaround. > > Also, where are your X logs? It is is normally at /var/log/X.something. > It this log empty after the crash? As stated before I posted a bug report with xfce: https://gitlab.xfce.org/xfce/xfwm4/-/issues/722 Please go there, there is the relevant line from .xsession-errors and a backtrace from the core file xfwm4 left behind. As a further note, for my usage keeping DRI3 is not a problem, so if the only worry I had was to get working xfce on my laptop I would be finished. What, instead, I'd like to try to understand is what is causing this and if it could affect more users in the future. -- Guido Falsi From nobody Sun May 28 12:44:59 2023 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 4QTdfn5LXrz4XLRP; Sun, 28 May 2023 12:45:21 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [IPv6:2a01:4f8:1c1c:11e5::1]) (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 4QTdfn0dlCz42CZ; Sun, 28 May 2023 12:45:21 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; none Received: from mail (mail [IPv6:fd5c:5351:d272::3]) by mail.madpilot.net (Postfix) with ESMTP id 4QTdfc0nXTz6wCt; Sun, 28 May 2023 14:45:12 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :subject:subject:from:from:content-language:references:date:date :message-id:received; s=bjowvop61wgh; t=1685277897; x= 1687092298; bh=v2aG55yGD2DmtVs2gyaBIdmcUJsR42Ljc/xpfRc7PVg=; b=K Tc+1Ff5W3Tl3N8WEQzll8caxSooVEusNTBN5WUfJ6tg1le7jjIH7UoA4q48kShIp bIy9J6MFcdRgv9++MoGCUdc9EWU0+3hG3Ez0xfMKT6rCTTjGCldg45r44znD9UyW aHVO2B9fmBvPqinDolkZiANcvCHgjPEjokAXncgWW0GYGJlPrsG0Zb0YCLygKI2s fiIDaoQ4xm0jQJhpYMVZxnTPUWxV32Y+1bDEh0jNL8qgzjNKg6AH27jN3JwJOB9I 0I52gXU4+g0IffzpKGG+aeQ5IM+mmefRAfRGLAyvic0zK1cRq68CQhlfyf9YXSUl Pc5XL5J/dR3KHEldDdkRg== Received: from mail.madpilot.net ([IPv6:fd5c:5351:d272::3]) by mail (mail.madpilot.net [IPv6:fd5c:5351:d272::3]) (amavisd-new, port 10026) with ESMTP id IVVO3DX7oWOi; Sun, 28 May 2023 14:44:57 +0200 (CEST) Message-ID: <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> Date: Sun, 28 May 2023 14:44:59 +0200 To: Alastair Hogge , freebsd-current@freebsd.org, current@FreeBSD.org, freebsd-x11@freebsd.org References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> Content-Language: en-US From: Guido Falsi Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head In-Reply-To: <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4QTdfn0dlCz42CZ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/32, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N 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 On 28/05/23 00:42, Alastair Hogge wrote: > Hello, > > Is there some way to test your X session with minimum components, and > slowly adding whatever XFCE does? Maybe I was not perfectly clear. Xorg works fine, I already tested with another window manager. The only thing that changed is that I updated to more recent head, updated a bunch of ports (none directly related to Xorg/DRI3) and xfwm4 started crashing with the errors I reported. Everything else seems to work fine (except other xfce components that depend on xfwm4, which show various degrees of bad behavior caused by xfwm4 not running). xfwm4 was NOT updated or reinstalled. > > I would switch from using a X Display Manager, and launch X from the > login vty using startx (if not already ), with a minimum .xinitrc. I > would find out what is needed to get a minimal XFCE going, for example, > maybe just the Window Manager, no Compositor, or nothing at all to see > if X handles the display mode setting at all. As I said this is something already easily tested. Everything works except xfwm4 crashes on startup if DRI3 is enabled. I am reasonably sure xfwm4 would not crash if compiled without compositor support, since the crash happens in code that is protected by ifdefs and would be removed is disabling compositor. That should would also not run if disabling the compositor, so I'm reasonably sure that would be another possible (but even uglier than disabling DRI3) workaround. > > Also, where are your X logs? It is is normally at /var/log/X.something. > It this log empty after the crash? As stated before I posted a bug report with xfce: https://gitlab.xfce.org/xfce/xfwm4/-/issues/722 Please go there, there is the relevant line from .xsession-errors and a backtrace from the core file xfwm4 left behind. As a further note, for my usage keeping DRI3 is not a problem, so if the only worry I had was to get working xfce on my laptop I would be finished. What, instead, I'd like to try to understand is what is causing this and if it could affect more users in the future. -- Guido Falsi From nobody Sun May 28 14:03:35 2023 X-Original-To: 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 4QTgP64kMcz4XR3x; Sun, 28 May 2023 14:03:38 +0000 (UTC) (envelope-from agh@riseup.net) Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) (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 (2048 bits) client-digest SHA256) (Client CN "mx0.riseup.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QTgP560xFz4Cgm; Sun, 28 May 2023 14:03:37 +0000 (UTC) (envelope-from agh@riseup.net) Authentication-Results: mx1.freebsd.org; none Received: from fews02-sea.riseup.net (fews02-sea-pn.riseup.net [10.0.1.112]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.riseup.net", Issuer "R3" (not verified)) by mx0.riseup.net (Postfix) with ESMTPS id 4QTgP40tN8z9t3L; Sun, 28 May 2023 14:03:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1685282616; bh=6VlYcDZSo1n+rkqLECy0qfBkDSjgpF1vk1WyIR8bDBQ=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=dCCMUP4txcowMaNPXAaWegMpbwsUyygeDVDxHbZsMVSaVNWzSn6qlK9rBM1kgA6MM 4H7sga460lHmyztghlZvefAL5x4LTP/rwhkx4PEBNNVau89cw8TNZWB2HF0zJJ2gb+ vlau0jvzOJlikewPJv1UVNywbQiS25scRcaKuZ8g= X-Riseup-User-ID: 460124B2F90AF6EE674C96D1DA530CF35C204C11C2C3FC0D08C047E9118E10FD Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews02-sea.riseup.net (Postfix) with ESMTPSA id 4QTgP35dvSzFpcg; Sun, 28 May 2023 14:03:35 +0000 (UTC) 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 Date: Sun, 28 May 2023 14:03:35 +0000 From: Alastair Hogge To: Guido Falsi Cc: freebsd-current@freebsd.org, current@freebsd.org Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head In-Reply-To: <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> Message-ID: <1635751e73bb8c4c600de231c8d43018@riseup.net> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4QTgP560xFz4Cgm X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Hello Guido, On 2023-05-28 12:44, Guido Falsi wrote: > On 28/05/23 00:42, Alastair Hogge wrote: >> Hello, >> >> Is there some way to test your X session with minimum components, and slowly adding whatever XFCE does? > > Maybe I was not perfectly clear. Xorg works fine, I already tested with another window manager. Perfection is an unhealthy Neo-liberal ideology, I avoid it at all cost. I missed the gitlab link earlier, tho thank you so much for taking the time to explain that again to me, sorry if I have caused an inconvenience here. My sympathies in your struggle, from another AMD GPU FreeBSD struggler. From nobody Sun May 28 14:03:35 2023 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 4QTgP64kMcz4XR3x; Sun, 28 May 2023 14:03:38 +0000 (UTC) (envelope-from agh@riseup.net) Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) (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 (2048 bits) client-digest SHA256) (Client CN "mx0.riseup.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QTgP560xFz4Cgm; Sun, 28 May 2023 14:03:37 +0000 (UTC) (envelope-from agh@riseup.net) Authentication-Results: mx1.freebsd.org; none Received: from fews02-sea.riseup.net (fews02-sea-pn.riseup.net [10.0.1.112]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.riseup.net", Issuer "R3" (not verified)) by mx0.riseup.net (Postfix) with ESMTPS id 4QTgP40tN8z9t3L; Sun, 28 May 2023 14:03:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1685282616; bh=6VlYcDZSo1n+rkqLECy0qfBkDSjgpF1vk1WyIR8bDBQ=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=dCCMUP4txcowMaNPXAaWegMpbwsUyygeDVDxHbZsMVSaVNWzSn6qlK9rBM1kgA6MM 4H7sga460lHmyztghlZvefAL5x4LTP/rwhkx4PEBNNVau89cw8TNZWB2HF0zJJ2gb+ vlau0jvzOJlikewPJv1UVNywbQiS25scRcaKuZ8g= X-Riseup-User-ID: 460124B2F90AF6EE674C96D1DA530CF35C204C11C2C3FC0D08C047E9118E10FD Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews02-sea.riseup.net (Postfix) with ESMTPSA id 4QTgP35dvSzFpcg; Sun, 28 May 2023 14:03:35 +0000 (UTC) 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 Date: Sun, 28 May 2023 14:03:35 +0000 From: Alastair Hogge To: Guido Falsi Cc: freebsd-current@freebsd.org, current@freebsd.org Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head In-Reply-To: <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> Message-ID: <1635751e73bb8c4c600de231c8d43018@riseup.net> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4QTgP560xFz4Cgm X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Hello Guido, On 2023-05-28 12:44, Guido Falsi wrote: > On 28/05/23 00:42, Alastair Hogge wrote: >> Hello, >> >> Is there some way to test your X session with minimum components, and slowly adding whatever XFCE does? > > Maybe I was not perfectly clear. Xorg works fine, I already tested with another window manager. Perfection is an unhealthy Neo-liberal ideology, I avoid it at all cost. I missed the gitlab link earlier, tho thank you so much for taking the time to explain that again to me, sorry if I have caused an inconvenience here. My sympathies in your struggle, from another AMD GPU FreeBSD struggler. From nobody Sun May 28 14:25:43 2023 X-Original-To: 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 4QTgtm692Xz4XSHv; Sun, 28 May 2023 14:25:52 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [IPv6:2a01:4f8:1c1c:11e5::1]) (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 4QTgtm5B4rz4JBC; Sun, 28 May 2023 14:25:52 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; none Received: from mail (mail [IPv6:fd5c:5351:d272::3]) by mail.madpilot.net (Postfix) with ESMTP id 4QTgtd1kqyz6f9b; Sun, 28 May 2023 16:25:45 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :from:from:references:content-language:subject:subject:date:date :message-id:received; s=bjowvop61wgh; t=1685283941; x= 1687098342; bh=E74c3QZLZAaCohzjpMkSA6P83ckwrPNxmIlBUy+E2XQ=; b=h tGywFyP9qd12xl/VHHyWOL/sx9IOmPssdvt+UW/y0Ky2BjDjmRMrV4RSS0qD/XAm 54oXFR5R4XWJUKR1z31KmqaFCd6sAjUl40VOVAdfyzS6ig3y6fF0sBq3aboPl0mJ Waep3gkkr8qvXlstTTqsySYlRyqqF8MPcnX3j+tLd6+G0B/TZTSpebIK4Ud6hhtG AY7PFOEWv3bx6hZtruLWrduTG9TuhMyjTf0jI4N/xjzlKnBj4bxdEAiOukJETXk0 MI7/yh8E0nkH6nxMWhZA6zOLIJIV/WsVq7sAd8nG7oBiW2MAK8yzwJBZBWdfkm4C XixONpjk9rXoSA0R3q69A== Received: from mail.madpilot.net ([IPv6:fd5c:5351:d272::3]) by mail (mail.madpilot.net [IPv6:fd5c:5351:d272::3]) (amavisd-new, port 10026) with ESMTP id fx2eFmzpwknE; Sun, 28 May 2023 16:25:41 +0200 (CEST) Message-ID: <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> Date: Sun, 28 May 2023 16:25:43 +0200 Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head Content-Language: en-US To: Alastair Hogge Cc: freebsd-current@freebsd.org, current@freebsd.org References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> <1635751e73bb8c4c600de231c8d43018@riseup.net> From: Guido Falsi In-Reply-To: <1635751e73bb8c4c600de231c8d43018@riseup.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4QTgtm5B4rz4JBC X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/32, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N 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 On 28/05/23 16:03, Alastair Hogge wrote: > Hello Guido, > > On 2023-05-28 12:44, Guido Falsi wrote: >> On 28/05/23 00:42, Alastair Hogge wrote: >>> Hello, >>> >>> Is there some way to test your X session with minimum components, and slowly adding whatever XFCE does? >> >> Maybe I was not perfectly clear. Xorg works fine, I already tested with another window manager. > > Perfection is an unhealthy Neo-liberal ideology, I avoid it at all cost. > I missed the gitlab link earlier, tho thank you so much for taking the > time to explain that again to me, sorry if I have caused an > inconvenience here. Well Maybe I came out a little aggressive, I did not mean perfection in any special way, just as a form of speech. Unluckily this is not an easy one to properly debug. I was lucky enough to find a workaround that is "good enough". > > My sympathies in your struggle, from another AMD GPU FreeBSD struggler. Actually my first struggle with AMD on this laptop, it has worked quite fine up to now. My other AMD machine I use as a headless builder, I sometimes connect a monitor but just to get to the console, so graphics drivers are not an issue there. -- Guido Falsi From nobody Sun May 28 14:25:43 2023 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 4QTgtm692Xz4XSHv; Sun, 28 May 2023 14:25:52 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [IPv6:2a01:4f8:1c1c:11e5::1]) (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 4QTgtm5B4rz4JBC; Sun, 28 May 2023 14:25:52 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; none Received: from mail (mail [IPv6:fd5c:5351:d272::3]) by mail.madpilot.net (Postfix) with ESMTP id 4QTgtd1kqyz6f9b; Sun, 28 May 2023 16:25:45 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :from:from:references:content-language:subject:subject:date:date :message-id:received; s=bjowvop61wgh; t=1685283941; x= 1687098342; bh=E74c3QZLZAaCohzjpMkSA6P83ckwrPNxmIlBUy+E2XQ=; b=h tGywFyP9qd12xl/VHHyWOL/sx9IOmPssdvt+UW/y0Ky2BjDjmRMrV4RSS0qD/XAm 54oXFR5R4XWJUKR1z31KmqaFCd6sAjUl40VOVAdfyzS6ig3y6fF0sBq3aboPl0mJ Waep3gkkr8qvXlstTTqsySYlRyqqF8MPcnX3j+tLd6+G0B/TZTSpebIK4Ud6hhtG AY7PFOEWv3bx6hZtruLWrduTG9TuhMyjTf0jI4N/xjzlKnBj4bxdEAiOukJETXk0 MI7/yh8E0nkH6nxMWhZA6zOLIJIV/WsVq7sAd8nG7oBiW2MAK8yzwJBZBWdfkm4C XixONpjk9rXoSA0R3q69A== Received: from mail.madpilot.net ([IPv6:fd5c:5351:d272::3]) by mail (mail.madpilot.net [IPv6:fd5c:5351:d272::3]) (amavisd-new, port 10026) with ESMTP id fx2eFmzpwknE; Sun, 28 May 2023 16:25:41 +0200 (CEST) Message-ID: <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> Date: Sun, 28 May 2023 16:25:43 +0200 Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head Content-Language: en-US To: Alastair Hogge Cc: freebsd-current@freebsd.org, current@freebsd.org References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> <1635751e73bb8c4c600de231c8d43018@riseup.net> From: Guido Falsi In-Reply-To: <1635751e73bb8c4c600de231c8d43018@riseup.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4QTgtm5B4rz4JBC X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/32, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N 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 On 28/05/23 16:03, Alastair Hogge wrote: > Hello Guido, > > On 2023-05-28 12:44, Guido Falsi wrote: >> On 28/05/23 00:42, Alastair Hogge wrote: >>> Hello, >>> >>> Is there some way to test your X session with minimum components, and slowly adding whatever XFCE does? >> >> Maybe I was not perfectly clear. Xorg works fine, I already tested with another window manager. > > Perfection is an unhealthy Neo-liberal ideology, I avoid it at all cost. > I missed the gitlab link earlier, tho thank you so much for taking the > time to explain that again to me, sorry if I have caused an > inconvenience here. Well Maybe I came out a little aggressive, I did not mean perfection in any special way, just as a form of speech. Unluckily this is not an easy one to properly debug. I was lucky enough to find a workaround that is "good enough". > > My sympathies in your struggle, from another AMD GPU FreeBSD struggler. Actually my first struggle with AMD on this laptop, it has worked quite fine up to now. My other AMD machine I use as a headless builder, I sometimes connect a monitor but just to get to the console, so graphics drivers are not an issue there. -- Guido Falsi From nobody Sun May 28 14:41:57 2023 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 4QThFb1p1rz4XTJ1 for ; Sun, 28 May 2023 14:42:11 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QThFb07knz4LwQ for ; Sun, 28 May 2023 14:42:10 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x52b.google.com with SMTP id 4fb4d7f45d1cf-5149c76f4dbso528663a12.1 for ; Sun, 28 May 2023 07:42:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1685284929; x=1687876929; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/YnD4EJC+OSl6MqteYigE3We1gQtPQp7P7YCIrl7nCA=; b=HFUOWR6BfTBgU+wa4vEuR6jRHEyroyMOiJu1GbVIhxN6tkpl3wdHwB+As4RvRnonEs u1PXt9xgop7vjmKPkUM2Fq/j2L8h57OZa3y9adxlMkuybqDoObYfmGsZAU3uHr/BOGQL 1dLr/7GOSD862w8HHV9+neWX/XBXILmIvLJtm2UwpmZOjuPaW48geAP1vi60vCI+GXdJ b4NaFdTCxnyGyg9Rawfo9hUzxXr9m0i34+65xfkitrMkn49b12vzL1Ill1+NDNfDHaIF fSQoL56Af+HGtKVvR7xTRr1Uuanhq7C76JNIUDmKUMYrOPMZdaS/T4sLK2mMyv1WJHsM 9XsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685284929; x=1687876929; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/YnD4EJC+OSl6MqteYigE3We1gQtPQp7P7YCIrl7nCA=; b=ThhvqrfkjMg458uvMK94lSQVJ0LhVbo1OxOo7YDh3Mxl6UXbe1mZUvdJ6T6qaX7Mi3 4e+sS3pwyQ/JBu7oU4EAvxCAF4So2T/jG3kTv8E+SnessEG++VOAQf/QVFqpB/wLx408 hzTS3B351rR2PFk4R8PPyCnwAISDfJPls8GSX9ko8IZpw9fd9PQvfN0EQ8TG2BPL/d6y GGIviehgjIXXPuVzib0FKFwRt+Fc8nhmMHGv7Ei5BQWYKltIU3aadcmUn3x8AmpnkTVW yDEidCeHB+ueL/BNYrWLIy2v6RyS8LPifNfMZBhkNlz96zQMjhBdcT601XRn7kWrzcy7 TtUQ== X-Gm-Message-State: AC+VfDytPVKdiSKsOyPbsvetau+q1Bsx7b7Tdo9LxKafBYfpG9AuFsyK m6orxWYBlwPjlldZZH6kmYFk7tVIR3dmarDCVePGsA== X-Google-Smtp-Source: ACHHUZ6/u9t8zg+PYvfLcGb+CUs5vQhihyC+Ln1pYx00lbRCFdmonpvoQVdaF/a/qL7WnCS+UhJPSjFfkcYj6k3BWkI= X-Received: by 2002:a17:907:7205:b0:973:9c54:5723 with SMTP id dr5-20020a170907720500b009739c545723mr8189918ejc.2.1685284928966; Sun, 28 May 2023 07:42:08 -0700 (PDT) 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 References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> <1635751e73bb8c4c600de231c8d43018@riseup.net> <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> In-Reply-To: <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> From: Warner Losh Date: Sun, 28 May 2023 08:41:57 -0600 Message-ID: Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head To: Guido Falsi Cc: Alastair Hogge , FreeBSD Current , FreeBSD Current Content-Type: multipart/alternative; boundary="00000000000089640b05fcc1f9c2" X-Rspamd-Queue-Id: 4QThFb07knz4LwQ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000089640b05fcc1f9c2 Content-Type: text/plain; charset="UTF-8" Sill questions. Did you update only some of your packages? You really need to update them all at the same time to have them be compatible. Some projects have a fast moving abi they don't keep compatible very well. Warner --00000000000089640b05fcc1f9c2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Sill questions.=C2=A0 Did you update only some of your pa= ckages? You really need to update them all at the same time to have them be= compatible. Some projects have a fast moving abi they don't keep compa= tible very well.

Warner
<= /div> --00000000000089640b05fcc1f9c2-- From nobody Sun May 28 14:41:57 2023 X-Original-To: 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 4QThFb5fXtz4XSqG for ; Sun, 28 May 2023 14:42:11 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QThFb07h0z4Lbs for ; Sun, 28 May 2023 14:42:10 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-96f850b32caso484449666b.3 for ; Sun, 28 May 2023 07:42:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1685284929; x=1687876929; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/YnD4EJC+OSl6MqteYigE3We1gQtPQp7P7YCIrl7nCA=; b=HFUOWR6BfTBgU+wa4vEuR6jRHEyroyMOiJu1GbVIhxN6tkpl3wdHwB+As4RvRnonEs u1PXt9xgop7vjmKPkUM2Fq/j2L8h57OZa3y9adxlMkuybqDoObYfmGsZAU3uHr/BOGQL 1dLr/7GOSD862w8HHV9+neWX/XBXILmIvLJtm2UwpmZOjuPaW48geAP1vi60vCI+GXdJ b4NaFdTCxnyGyg9Rawfo9hUzxXr9m0i34+65xfkitrMkn49b12vzL1Ill1+NDNfDHaIF fSQoL56Af+HGtKVvR7xTRr1Uuanhq7C76JNIUDmKUMYrOPMZdaS/T4sLK2mMyv1WJHsM 9XsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685284929; x=1687876929; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/YnD4EJC+OSl6MqteYigE3We1gQtPQp7P7YCIrl7nCA=; b=XW5SveOTMlL2uKeetRZamsASmNwZa4mqOqj2aN2AO9LCYvkVYzbz1U6Vj8DEd9USz1 GgVtIjGFS469ODjcRoFzcw/CciekbHwgTkxKLSlXR4hwHU1dt8dvZADH3g0HJGzNaXNV s+0uDIvqFxfvcqdk9jCqtEiKyOhdD28vx4jGGxtR0tQC6gI+YB1NRk5TEgxjBZdCR10H h6V3qAlHpmRVqAiwxuIBJIqKiZl8ufCJlhivecFLoTxN3ED3sPbPqcSo3DtLpTNZJxiw n3a8te34XsOldO1pY1C1TAOjUhOQ/aOXwgIcnlPJpVclAOZIKxwHlA+MERasFsPMtozX Bl+w== X-Gm-Message-State: AC+VfDwsk9lSp5DBqyuvZkCkeoc2fu7sIZZFP6jMAjaQ3YY9XOflE2Zy TIfy3qcQgOpbzHh9sJp7kvW4mmSlnl8uknsDE+HmKw== X-Google-Smtp-Source: ACHHUZ6/u9t8zg+PYvfLcGb+CUs5vQhihyC+Ln1pYx00lbRCFdmonpvoQVdaF/a/qL7WnCS+UhJPSjFfkcYj6k3BWkI= X-Received: by 2002:a17:907:7205:b0:973:9c54:5723 with SMTP id dr5-20020a170907720500b009739c545723mr8189918ejc.2.1685284928966; Sun, 28 May 2023 07:42:08 -0700 (PDT) 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 References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> <1635751e73bb8c4c600de231c8d43018@riseup.net> <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> In-Reply-To: <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> From: Warner Losh Date: Sun, 28 May 2023 08:41:57 -0600 Message-ID: Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head To: Guido Falsi Cc: Alastair Hogge , FreeBSD Current , FreeBSD Current Content-Type: multipart/alternative; boundary="00000000000089640b05fcc1f9c2" X-Rspamd-Queue-Id: 4QThFb07h0z4Lbs X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000089640b05fcc1f9c2 Content-Type: text/plain; charset="UTF-8" Sill questions. Did you update only some of your packages? You really need to update them all at the same time to have them be compatible. Some projects have a fast moving abi they don't keep compatible very well. Warner --00000000000089640b05fcc1f9c2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Sill questions.=C2=A0 Did you update only some of your pa= ckages? You really need to update them all at the same time to have them be= compatible. Some projects have a fast moving abi they don't keep compa= tible very well.

Warner
<= /div> --00000000000089640b05fcc1f9c2-- From nobody Sun May 28 15:20:52 2023 X-Original-To: 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 4QTj6H0c5Kz4XWFj; Sun, 28 May 2023 15:20:55 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (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 4QTj6G4wkCz4Qkw; Sun, 28 May 2023 15:20:54 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; none Received: from mail (mail [IPv6:fd5c:5351:d272::3]) by mail.madpilot.net (Postfix) with ESMTP id 4QTj6F1FYcz6yqv; Sun, 28 May 2023 17:20:53 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :from:from:references:content-language:subject:subject:date:date :message-id:received; s=bjowvop61wgh; t=1685287251; x= 1687101652; bh=ZiP9WWgppTQv6MQA8QwFlMYHngGl6GiRBkV6i1Pz7WM=; b=h fVdEDJ6FwSsh67bKWrpQjAunGaxcaRPLcT55/TUby7lYkFf7bC1T73E+5pFUuntv jRf8nMgEQIuzD2SCiceaADf/9XNDmRLQhT/8V+cZPJXgeNySUy6CLvne5Um0J56M tZ3VESWtv+92IYQFuh/ofZkW+148CIw/QzfcbxPvZ5h/Z8x8iQP8pFaCVeUz6hI5 U2EGyCV1UQ5z64rPRpTVHAavIBA7/0nWSVpH6UVMvKj6Mr3iP0f6Wi9Kx3GNFwez WwZf9VeFD/WZl1R5S86AtSuKnWgNN351HHQvY4iXZNpsznA3PQWGGs+yP8LX9ql7 x6pwL2dwUNEqfNqTghv2g== Received: from mail.madpilot.net ([IPv6:fd5c:5351:d272::3]) by mail (mail.madpilot.net [IPv6:fd5c:5351:d272::3]) (amavisd-new, port 10026) with ESMTP id WBdTNgDJrjgl; Sun, 28 May 2023 17:20:51 +0200 (CEST) Message-ID: Date: Sun, 28 May 2023 17:20:52 +0200 Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head Content-Language: en-US To: Warner Losh Cc: Alastair Hogge , FreeBSD Current , FreeBSD Current References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> <1635751e73bb8c4c600de231c8d43018@riseup.net> <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> From: Guido Falsi In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4QTj6G4wkCz4Qkw X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N 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 On 28/05/23 16:41, Warner Losh wrote: > Sill questions.  Did you update only some of your packages? You really > need to update them all at the same time to have them be compatible. > Some projects have a fast moving abi they don't keep compatible very well. > I'm running FreeBSD head here, using pkgbase. I upgraded a few base packages (I create them with poudriere). I also updated the ports tree and updated other ports using the resulting binaries (also created with poudriere) The pkgs that were updated when xfwm4 stopped working were listed in my first post [1]. I tested downgrading glib, but nothing changed. Other things updated there look completely unrelated (well except the kernel obviously). Now that you mention it, I may have forgot to force poudriere to rebuild the drm-kmod port. I'll try that, just in case! [1] https://lists.freebsd.org/archives/freebsd-current/2023-May/003734.html -- Guido Falsi From nobody Sun May 28 15:20:52 2023 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 4QTj6H0c5Kz4XWFj; Sun, 28 May 2023 15:20:55 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (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 4QTj6G4wkCz4Qkw; Sun, 28 May 2023 15:20:54 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; none Received: from mail (mail [IPv6:fd5c:5351:d272::3]) by mail.madpilot.net (Postfix) with ESMTP id 4QTj6F1FYcz6yqv; Sun, 28 May 2023 17:20:53 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :from:from:references:content-language:subject:subject:date:date :message-id:received; s=bjowvop61wgh; t=1685287251; x= 1687101652; bh=ZiP9WWgppTQv6MQA8QwFlMYHngGl6GiRBkV6i1Pz7WM=; b=h fVdEDJ6FwSsh67bKWrpQjAunGaxcaRPLcT55/TUby7lYkFf7bC1T73E+5pFUuntv jRf8nMgEQIuzD2SCiceaADf/9XNDmRLQhT/8V+cZPJXgeNySUy6CLvne5Um0J56M tZ3VESWtv+92IYQFuh/ofZkW+148CIw/QzfcbxPvZ5h/Z8x8iQP8pFaCVeUz6hI5 U2EGyCV1UQ5z64rPRpTVHAavIBA7/0nWSVpH6UVMvKj6Mr3iP0f6Wi9Kx3GNFwez WwZf9VeFD/WZl1R5S86AtSuKnWgNN351HHQvY4iXZNpsznA3PQWGGs+yP8LX9ql7 x6pwL2dwUNEqfNqTghv2g== Received: from mail.madpilot.net ([IPv6:fd5c:5351:d272::3]) by mail (mail.madpilot.net [IPv6:fd5c:5351:d272::3]) (amavisd-new, port 10026) with ESMTP id WBdTNgDJrjgl; Sun, 28 May 2023 17:20:51 +0200 (CEST) Message-ID: Date: Sun, 28 May 2023 17:20:52 +0200 Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head Content-Language: en-US To: Warner Losh Cc: Alastair Hogge , FreeBSD Current , FreeBSD Current References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> <1635751e73bb8c4c600de231c8d43018@riseup.net> <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> From: Guido Falsi In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4QTj6G4wkCz4Qkw X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N 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 On 28/05/23 16:41, Warner Losh wrote: > Sill questions.  Did you update only some of your packages? You really > need to update them all at the same time to have them be compatible. > Some projects have a fast moving abi they don't keep compatible very well. > I'm running FreeBSD head here, using pkgbase. I upgraded a few base packages (I create them with poudriere). I also updated the ports tree and updated other ports using the resulting binaries (also created with poudriere) The pkgs that were updated when xfwm4 stopped working were listed in my first post [1]. I tested downgrading glib, but nothing changed. Other things updated there look completely unrelated (well except the kernel obviously). Now that you mention it, I may have forgot to force poudriere to rebuild the drm-kmod port. I'll try that, just in case! [1] https://lists.freebsd.org/archives/freebsd-current/2023-May/003734.html -- Guido Falsi From nobody Sun May 28 16:22:18 2023 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 4QTkTM0zdJz4Xb0M for ; Sun, 28 May 2023 16:22:31 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QTkTL6NLrz3KqD for ; Sun, 28 May 2023 16:22:30 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x62c.google.com with SMTP id a640c23a62f3a-973bf581759so466255166b.0 for ; Sun, 28 May 2023 09:22:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1685290949; x=1687882949; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=xiaMyFYUStuVjS+z4FaK1uAI3uTIKibsEiXvbqe27Hw=; b=IbPDu8gr4sGmKrM5UxkVVYnrGamwJP3z2mP9kpFmbuguBwjoHS36zDbieOSt/UNh+F gz+rWnXaQiZ7ZNLidflFeo2JSZXsW5elV6Epd/I4KS0pNdvInhkt5JjRuN6CHHxTIyLd lEO+uW/ZemaH0f6PL98z9JdXf0XghE7DIK2I3H5xmuBMJngabpsYUOohf1VZZ4cnvJKa J4k5jdX5dmDOiJ5l3IFNYBc+e0JSWTaF++zbAgxdjnwnbK2RKH/aGLdOfzjHtZ8ZCXRZ QYCeb623HOP60zV2cY47fY5AESVoWbwVAcm62KETzO1C2pYvZLVlGqWyznu0Y/uuQZZ/ Htiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685290949; x=1687882949; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=xiaMyFYUStuVjS+z4FaK1uAI3uTIKibsEiXvbqe27Hw=; b=bqAU9EOncGj0qU9KSKvDOsKdilUylqb3e8iBhSO1sISTNFmyE4niW80rRa4Wu9wvHr Wgfx+h83j4jCdjYGVoA24gElyOgUJrh0fd0NVk8ZOomGh9XdtZs20PA3hSi8wQWs21dI OCCzCt1mBqsdBXB5pyh/OoiN5WAWZa61zYblOG2Ng64MANw++c9AIvaXbE0eLrJFrJEq 17Aou7C2zK0AGPkjn8sMSL9xCmKUSa7Xqsfdo9FfBbXzpynIGKmqAyX0yOA8uHFAmgYk 3x+8h0Q7SzQNx0/bPveCyVSEFbz7zpPAHn3LwOypXbeyKsoYdn8uqZF4/W0XSJ/WWH6l 1DtQ== X-Gm-Message-State: AC+VfDyJ+aUbCTAWlHaZmwXo/MjpGF8bOm3XRDCoi1e/EMPjrc3Dq+hy F5GOiXbr6D0Y6P57R/vs31lZZruaukDBajT/88GJfA== X-Google-Smtp-Source: ACHHUZ7+P1PEHq62q5Ciivw6IGgtoXlPh+BZV+Y5qSBACnHtxJc0IaqMuDyRJAcXLAbvUylY6VhmJubf4Pg7OEKJPM8= X-Received: by 2002:a17:907:98e:b0:957:943e:7416 with SMTP id bf14-20020a170907098e00b00957943e7416mr8872669ejc.15.1685290949342; Sun, 28 May 2023 09:22:29 -0700 (PDT) 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 References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> <1635751e73bb8c4c600de231c8d43018@riseup.net> <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> In-Reply-To: From: Warner Losh Date: Sun, 28 May 2023 10:22:18 -0600 Message-ID: Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head To: Guido Falsi Cc: Alastair Hogge , FreeBSD Current , FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000610d9305fcc3608b" X-Rspamd-Queue-Id: 4QTkTL6NLrz3KqD X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000610d9305fcc3608b Content-Type: text/plain; charset="UTF-8" On Sun, May 28, 2023, 9:20 AM Guido Falsi wrote: > On 28/05/23 16:41, Warner Losh wrote: > > Sill questions. Did you update only some of your packages? You really > > need to update them all at the same time to have them be compatible. > > Some projects have a fast moving abi they don't keep compatible very > well. > > > > I'm running FreeBSD head here, using pkgbase. I upgraded a few base > packages (I create them with poudriere). > > I also updated the ports tree and updated other ports using the > resulting binaries (also created with poudriere) > > The pkgs that were updated when xfwm4 stopped working were listed in my > first post [1]. > So not all of the non pkg base packages? Have you tried updating them all? Or you did update them all and the list of what updated was in the post? I read it when first posted and again now and am unsure which it is... It may well be something broke... but I'm just wanting to be double sure it's against a consistent package set. If something broke, then I can't help. Also a good time to plug zfs root and snapshots to roll back to if the upgrade fails. But that's like for future you... I tested downgrading glib, but nothing changed. Other things updated > there look completely unrelated (well except the kernel obviously). > Yea, I've rarely had good luck with that path. > Now that you mention it, I may have forgot to force poudriere to rebuild > the drm-kmod port. I'll try that, just in case! > That's unlikely the cause. Though it wouldn't hurt. Usually it simply won't load. And this package us matched to a specific kernel so make sure you rebuild against the headers of the kernel installed. Warner [1] https://lists.freebsd.org/archives/freebsd-current/2023-May/003734.html > > -- > Guido Falsi > > --000000000000610d9305fcc3608b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sun, May 28, 2023, 9:20 AM Guido Falsi <mad@madpilot.net> wrote:
On 28/05/23 16:41, Warner Losh wrote:
> Sill questions.=C2=A0 Did you update only some of your packages? You r= eally
> need to update them all at the same time to have them be compatible. <= br> > Some projects have a fast moving abi they don't keep compatible ve= ry well.
>

I'm running FreeBSD head here, using pkgbase. I upgraded a few base packages (I create them with poudriere).

I also updated the ports tree and updated other ports using the
resulting binaries (also created with poudriere)

The pkgs that were updated when xfwm4 stopped working were listed in my first post [1].

So not all of the non pkg base packages? Have you tried upda= ting them all? Or you did update them all and the list of what updated was = in the post? I read it when first posted and again now and am unsure which = it is...

It may well be = something broke... but I'm just wanting to be double sure it's agai= nst a consistent package set. If something broke, then I can't help.

Also a good time to plug z= fs root and snapshots to roll back to if the upgrade fails. But that's = like for future you...

<= div class=3D"gmail_quote">
I tested downgrading glib, but nothing changed. Other things updated
there look completely unrelated (well except the kernel obviously).


Yea, I've rarely had good luck with that path.

<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">
Now that you mention it, I may have forgot to force poudriere to rebuild the drm-kmod port. I'll try that, just in case!
<= /div>

That's unlikely the = cause. Though it wouldn't hurt. Usually it simply won't load. And t= his package us matched to a specific kernel so make sure you rebuild agains= t the headers of the kernel installed.

Warner

--000000000000610d9305fcc3608b-- From nobody Sun May 28 16:22:18 2023 X-Original-To: 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 4QTkTM4jyVz4XZQr for ; Sun, 28 May 2023 16:22:31 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QTkTM2Y24z3Kg7 for ; Sun, 28 May 2023 16:22:31 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x631.google.com with SMTP id a640c23a62f3a-97000a039b2so464247366b.2 for ; Sun, 28 May 2023 09:22:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1685290949; x=1687882949; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=xiaMyFYUStuVjS+z4FaK1uAI3uTIKibsEiXvbqe27Hw=; b=IbPDu8gr4sGmKrM5UxkVVYnrGamwJP3z2mP9kpFmbuguBwjoHS36zDbieOSt/UNh+F gz+rWnXaQiZ7ZNLidflFeo2JSZXsW5elV6Epd/I4KS0pNdvInhkt5JjRuN6CHHxTIyLd lEO+uW/ZemaH0f6PL98z9JdXf0XghE7DIK2I3H5xmuBMJngabpsYUOohf1VZZ4cnvJKa J4k5jdX5dmDOiJ5l3IFNYBc+e0JSWTaF++zbAgxdjnwnbK2RKH/aGLdOfzjHtZ8ZCXRZ QYCeb623HOP60zV2cY47fY5AESVoWbwVAcm62KETzO1C2pYvZLVlGqWyznu0Y/uuQZZ/ Htiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685290949; x=1687882949; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=xiaMyFYUStuVjS+z4FaK1uAI3uTIKibsEiXvbqe27Hw=; b=SgQZU23U3osB/rAa3XSSJmQafUNevRtdWWkhqTv5Q4zCNgUuq49j8Zm0mXSrCoi+ml fLRHoAMSk6VqUV7KnvP1NizkliMafYf5o1rrvFJfN8dAm0zIBFTKNNosYAxQsX42A0Do jsBOB3iuiKwcCIE/b2VV7XCVOm+jLJqY18xqg4sH0IFSx34CEkA/Dtk88ngj5+LLCqho O0GVNZgg24erJ63ySB2d//F5/N7X/AVD0784uKra6enIePeFz+vA14F4+H30MaKS5V0V yzpLy8LwQvdhE+LC2NRBJNmDMZnQc+ZEIyu8dx1EIfqxqH43qnbXnKzkhPzd7yBjAo9R 5qpg== X-Gm-Message-State: AC+VfDxqNtvRzjEw61cw61cs+ZFQtAbDGBCPw8/k2L4HeWzTIdH+XUcr vRICpVbyGRLiIki2HM0gWO5z+8ffRdyXgWFSpdIV4Hl95NIkMsLB X-Google-Smtp-Source: ACHHUZ7+P1PEHq62q5Ciivw6IGgtoXlPh+BZV+Y5qSBACnHtxJc0IaqMuDyRJAcXLAbvUylY6VhmJubf4Pg7OEKJPM8= X-Received: by 2002:a17:907:98e:b0:957:943e:7416 with SMTP id bf14-20020a170907098e00b00957943e7416mr8872669ejc.15.1685290949342; Sun, 28 May 2023 09:22:29 -0700 (PDT) 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 References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> <1635751e73bb8c4c600de231c8d43018@riseup.net> <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> In-Reply-To: From: Warner Losh Date: Sun, 28 May 2023 10:22:18 -0600 Message-ID: Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head To: Guido Falsi Cc: Alastair Hogge , FreeBSD Current , FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000610d9305fcc3608b" X-Rspamd-Queue-Id: 4QTkTM2Y24z3Kg7 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000610d9305fcc3608b Content-Type: text/plain; charset="UTF-8" On Sun, May 28, 2023, 9:20 AM Guido Falsi wrote: > On 28/05/23 16:41, Warner Losh wrote: > > Sill questions. Did you update only some of your packages? You really > > need to update them all at the same time to have them be compatible. > > Some projects have a fast moving abi they don't keep compatible very > well. > > > > I'm running FreeBSD head here, using pkgbase. I upgraded a few base > packages (I create them with poudriere). > > I also updated the ports tree and updated other ports using the > resulting binaries (also created with poudriere) > > The pkgs that were updated when xfwm4 stopped working were listed in my > first post [1]. > So not all of the non pkg base packages? Have you tried updating them all? Or you did update them all and the list of what updated was in the post? I read it when first posted and again now and am unsure which it is... It may well be something broke... but I'm just wanting to be double sure it's against a consistent package set. If something broke, then I can't help. Also a good time to plug zfs root and snapshots to roll back to if the upgrade fails. But that's like for future you... I tested downgrading glib, but nothing changed. Other things updated > there look completely unrelated (well except the kernel obviously). > Yea, I've rarely had good luck with that path. > Now that you mention it, I may have forgot to force poudriere to rebuild > the drm-kmod port. I'll try that, just in case! > That's unlikely the cause. Though it wouldn't hurt. Usually it simply won't load. And this package us matched to a specific kernel so make sure you rebuild against the headers of the kernel installed. Warner [1] https://lists.freebsd.org/archives/freebsd-current/2023-May/003734.html > > -- > Guido Falsi > > --000000000000610d9305fcc3608b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sun, May 28, 2023, 9:20 AM Guido Falsi <mad@madpilot.net> wrote:
On 28/05/23 16:41, Warner Losh wrote:
> Sill questions.=C2=A0 Did you update only some of your packages? You r= eally
> need to update them all at the same time to have them be compatible. <= br> > Some projects have a fast moving abi they don't keep compatible ve= ry well.
>

I'm running FreeBSD head here, using pkgbase. I upgraded a few base packages (I create them with poudriere).

I also updated the ports tree and updated other ports using the
resulting binaries (also created with poudriere)

The pkgs that were updated when xfwm4 stopped working were listed in my first post [1].

So not all of the non pkg base packages? Have you tried upda= ting them all? Or you did update them all and the list of what updated was = in the post? I read it when first posted and again now and am unsure which = it is...

It may well be = something broke... but I'm just wanting to be double sure it's agai= nst a consistent package set. If something broke, then I can't help.

Also a good time to plug z= fs root and snapshots to roll back to if the upgrade fails. But that's = like for future you...

<= div class=3D"gmail_quote">
I tested downgrading glib, but nothing changed. Other things updated
there look completely unrelated (well except the kernel obviously).


Yea, I've rarely had good luck with that path.

<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">
Now that you mention it, I may have forgot to force poudriere to rebuild the drm-kmod port. I'll try that, just in case!
<= /div>

That's unlikely the = cause. Though it wouldn't hurt. Usually it simply won't load. And t= his package us matched to a specific kernel so make sure you rebuild agains= t the headers of the kernel installed.

Warner

--000000000000610d9305fcc3608b-- From nobody Sun May 28 17:16:34 2023 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 4QTlgp4Nybz4Xdx4 for ; Sun, 28 May 2023 17:16:38 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 4QTlgp3j73z3j6n for ; Sun, 28 May 2023 17:16:38 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685294198; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=T1OdjsrsyYMe1Fa7CCapr046vqMdvaP4wkDPKV84Cbk=; b=LhNvgnCtA8YM2SVfYarMzDGAmt75OWObPKbuOsWnR9scGCipgLjSt1CR+141jet1DI+k2k 8Ls1EAyts57aU59IkFJp7hWdoBOqNpJuICo27X0toKN1pJ9462I0ep+BKMxOMeRzasINvU Qq2IYgLKgWrKAVMXa9XEY6epzpLFSqTDTCFQsqQR6EyD9IP5VRPOAu3D7z0nU+GO+gvFB/ 7drzCHzuGhIZFegRPDyd7rAVdXIm+bTvWrseFNGvHAIk8TK0q4p1+Q+Az2bO993KjTfOd7 zPJsa/fzRkhLu+ziSylLe5wBLxWwKwQQv2ij+KI5mQpsWuavMvMPUNQNuhf6cg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685294198; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=T1OdjsrsyYMe1Fa7CCapr046vqMdvaP4wkDPKV84Cbk=; b=QpgWC2Qqv383TTAnI0G3pq6ro7DtgQvi1ecKT01eodTL3XjrHhQz80koYOLHpkekjQZABU RJDh7xXjuaHfR7UsKxi41shzfo6uybobr1PkuLThuq1US2WEAE6pTx4nhbV81NZBDlx7Oj Jt1LMtEsUjNfMgnIiTO9vO3ipLoXiawyAqOnOHSiuIZBrNMNJuiRdT9oilvqiQBFOrn8Hf d6rzNUHFnMiq7vnzAGqF3XrG06yIg+WEYVyjfa0owPH8y4i9V01z60fR+EpuYg9DzxxNOu MNlKBJBC6KG4Q8O26lmW+bDOAH8BoHRh9wDUb1A29cAgLraKT8BytpyaN3Z0MQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1685294198; a=rsa-sha256; cv=none; b=ZmdBWewnRDFmynPouCbegs20OECge2zN0GFHCTg8ricXLiq9BWU45ooRTeAg8a5qtcHMeC z43H2pJdYSvopwGRIDueDBokNx9/akGJXxVe/6/4rAjnQoKxgw99E9y20Yi/JU5abxVV2e I/kAwUDmagLJw38uW/OikWEh2u3zv4hTutPApPtV2S9UFpvqUjpKMATstLc5vWU5cNS5in AimCrVvnx3vTCccfAYmPemqaHXG9AcZyNPNjpmWRKytByohppRMdZdNA5SWUdO+ZIGwkMl oK2gw8CMF5aOc9LS8vCGf7nznSfCfR+pzppV30FUbKpwPh1+rMtxdWTZoxWO3Q== Received: from [192.168.1.10] (host-2-100-161-236.as13285.net [2.100.161.236]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: grahamperrin) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QTlgp1MjBzlQs for ; Sun, 28 May 2023 17:16:38 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Message-ID: <489e34cd-2c11-0030-5839-ea8d5f687b2f@freebsd.org> Date: Sun, 28 May 2023 18:16:34 +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 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head Content-Language: en-US To: freebsd-current@freebsd.org References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> From: Graham Perrin Organization: FreeBSD In-Reply-To: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------SR08inx0i23Ty4UT0SR1hZcU" X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------SR08inx0i23Ty4UT0SR1hZcU Content-Type: multipart/mixed; boundary="------------oOkSwXabcG0XYMP1ioFq8y0P"; protected-headers="v1" From: Graham Perrin To: freebsd-current@freebsd.org Message-ID: <489e34cd-2c11-0030-5839-ea8d5f687b2f@freebsd.org> Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> In-Reply-To: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> --------------oOkSwXabcG0XYMP1ioFq8y0P Content-Type: multipart/alternative; boundary="------------ioN20ml0GTDB3tB46wQGOyKG" --------------ioN20ml0GTDB3tB46wQGOyKG Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 T24gMjcvMDUvMjAyMyAwOTozMSwgR3VpZG8gRmFsc2kgd3JvdGU6DQo+IEknbSBzZWVpbmcg YSBzdHJhbmdlIGlzc3VlIHdpdGggeGZ3bTQgb24gbXkgbGFwdG9wIA0KDQpIb3cgbXVjaCBt ZW1vcnksIGhvdyBtdWNoIFZSQU0/DQoNCj4gcnVubmluZyBoZWFkIChjb21taXQgNTgwNGI3 YWIzNzhkNjIwNzEzMGJkMTY4NWM5MzFkYTZhNGU3NmU1NSksIHVzaW5nIA0KPiBwa2diYXNl LCBldmVyeXRoaW5nIGJ1aWxkIG9uIHBvdWRyaWVyZS4NCj4NCj4gSSBoYXZlIGZpbGVkIGFu IGlzc3VlIHVwc3RyZWFtIHdpdGggYSBkZXNjcmlwdGlvbiBhbmQgc29tZSBmaW5kaW5nOg0K Pg0KPiBodHRwczovL2dpdGxhYi54ZmNlLm9yZy94ZmNlL3hmd200Ly0vaXNzdWVzLzcyMg0K Pg0KPiDigKYNCg0KSSByZWNlbnRseSBoYWQgYSBibGFja291dCBvbiBDVVJSRU5UIHdpdGgg ZXZlcnkgc3RhcnQgb2YgWGZjZS4gSSBkaWRuJ3QgDQpib3RoZXIgdG8gbG9vayBhdCBkZXRh aWxzIG9mIHRoZSBibGFja291dCwgYnV0IEkgd29ya2VkIGFyb3VuZCBieSBnaXZpbmcgDQpt b3JlIG1lbW9yeSB0byB0aGUgdmlydHVhbCBtYWNoaW5lLg0KDQo= --------------ioN20ml0GTDB3tB46wQGOyKG Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On 27/05/2023 09:31, Guido Falsi wrote= :
I'm seeing a strange issue with xfwm4 on my laptop

How much memory, how much VRAM?

runn= ing head (commit 5804b7ab378d6207130bd1685c931da6a4e76e55), using pkgbase, everything build on poudriere.

I have filed an issue upstream with a description and some finding:

https://gitlab.xfce.org/xfce/xfwm4/-/iss= ues/722

=E2=80=A6

I recently had a blackout on CURRENT with every start of Xfce. I didn't bother to look at details of the blackout, but I worked around by giving more memory to the virtual machine.

--------------ioN20ml0GTDB3tB46wQGOyKG-- --------------oOkSwXabcG0XYMP1ioFq8y0P-- --------------SR08inx0i23Ty4UT0SR1hZcU Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEWT/lssMHB+28ly8Kt2dIb0oY1AsFAmRzjHMFAwAAAAAACgkQt2dIb0oY1AsA zA/9GzSaIAn6ei9ePP71w6AyHEm+lQlIEW0X1hqXebldnLNWMCoXc+p1h6/I/oBA7rD18R23Pupr aS7J40lQX0w9juZCEEW4MItKRasnpSCVfQm/WP+rDiI45d756EFd4nYKGWvW20iXj0C9Zl98CGQr j/9FIiIviAVQFgALOSmlvinihRii0Tx37psDkqe6rWgEMdZWFuLXredrDg87CKDAzLSROHzNAuzI HoUgQ30p/IlsO3X2WTw+6MYy4S1Atq5PFHJnCuVZkA35caVMe7hiS5P/nxWWh24j1CxiyUofYrN2 vaP+S9FM+NXem3Uz9a9i+jtAnhmL6iewRt/qJW1vomJ3YBnAikOgvMPrq4xqEKKVSHVVGX1g5Hs0 Oqn1MviFVVt1Ua5Ui5IMDKCCP27/wIA3YIfqFPUjhct2m6yFJ6swbafcC906S1GU0NghVnv8Uhxo 6iNJsQbjIWeH2UfIjib1+1ZsfuM7aGGcfwTlkdoMzBUVkodU5n1VqBLmuoQcgqK23fLKCQTZTwFs gGOZuzzVwxpzU6p1grDEFl1jvCUMzwBAkyBoxfKOGr8xoTnSPyWX/K9Tkuw5JEkqb0Ei0E0Q58eP T3InXvx2u6MW2ZtEVzFEJs6Wt3mZp0Xw8+C9RRKyERlfV5TaWiMjC9+LY/Y2EHeAaTjT9sQ22FJW PPs= =L6o1 -----END PGP SIGNATURE----- --------------SR08inx0i23Ty4UT0SR1hZcU-- From nobody Sun May 28 18:45:41 2023 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 4QTngL1P1zz4XkVs; Sun, 28 May 2023 18:46:22 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (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 4QTngK5CNbz3rm3; Sun, 28 May 2023 18:46:21 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; none Received: from mail (mail [IPv6:fd5c:5351:d272::3]) by mail.madpilot.net (Postfix) with ESMTP id 4QTnfc4h2hz6yY6; Sun, 28 May 2023 20:45:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :from:from:content-language:references:subject:subject:date:date :message-id:received; s=bjowvop61wgh; t=1685299542; x= 1687113943; bh=7l2XY6/jtLzPmWCwv8qRsqz/soXWlvD60y6vgEH6zRI=; b=p 4LKtoVehLdG/uAELz6XC1+/ov1ijaoNR7Lgdr1XwnSP0fRtuLnjDPv2JEFlyUkRD uDY6LtqIaoXzLr0BOWAA/SjO1H2WEQuVvuIT7nqwDNkyy50li+7jPklJsxEK4Ycb GGg1tHvKJvKWd/kzCSfQcTHS+L7/uoQnqpvjBQat3aTw0UbHG85i9C0gWSUhvxHZ LsHUh+Y+EZd0jnw4YWvmPT4hVH+HTznYvGYhkpNR40IRRy9LlHWEDkIGs/jUZKHn YJO0bu+hHbcejQkKimajjisqePOeDQlva9TVnFe048ZuV+BB3qpG0quC2jTqW2kH 1TWp7bLvEnPiuZqvcXaPA== Received: from mail.madpilot.net ([IPv6:fd5c:5351:d272::3]) by mail (mail.madpilot.net [IPv6:fd5c:5351:d272::3]) (amavisd-new, port 10026) with ESMTP id C_jaIEOBpVHQ; Sun, 28 May 2023 20:45:42 +0200 (CEST) Message-ID: <0d4e3bda-4ef3-2b22-0a95-319f7f9baf23@madpilot.net> Date: Sun, 28 May 2023 20:45:41 +0200 Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head To: Warner Losh Cc: Alastair Hogge , FreeBSD Current , FreeBSD Current References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> <1635751e73bb8c4c600de231c8d43018@riseup.net> <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> Content-Language: en-US From: Guido Falsi In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4QTngK5CNbz3rm3 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N 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 On 28/05/23 18:22, Warner Losh wrote: > > > On Sun, May 28, 2023, 9:20 AM Guido Falsi > wrote: > > On 28/05/23 16:41, Warner Losh wrote: > > Sill questions.  Did you update only some of your packages? You > really > > need to update them all at the same time to have them be compatible. > > Some projects have a fast moving abi they don't keep compatible > very well. > > > > I'm running FreeBSD head here, using pkgbase. I upgraded a few base > packages (I create them with poudriere). > > I also updated the ports tree and updated other ports using the > resulting binaries (also created with poudriere) > > The pkgs that were updated when xfwm4 stopped working were listed in my > first post [1]. > > > So not all of the non pkg base packages? Have you tried updating them > all? Or you did update them all and the list of what updated was in the > post? I read it when first posted and again now and am unsure which it is... > > It may well be something broke... but I'm just wanting to be double sure > it's against a consistent package set. If something broke, then I can't > help. I see, I did not understand what you meant at first. What I posted was the result of a simple "pkg upgrade", which is what I usually do to update the machine, and usually works quite fine. I have not tested forcing all packages reinstallation ("pkg upgrade -f" if I get it correctly). That is something I was already planning to do. Will report back tomorrow for that. -- Guido Falsi From nobody Sun May 28 18:45:41 2023 X-Original-To: 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 4QTngL1P1zz4XkVs; Sun, 28 May 2023 18:46:22 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (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 4QTngK5CNbz3rm3; Sun, 28 May 2023 18:46:21 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; none Received: from mail (mail [IPv6:fd5c:5351:d272::3]) by mail.madpilot.net (Postfix) with ESMTP id 4QTnfc4h2hz6yY6; Sun, 28 May 2023 20:45:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :from:from:content-language:references:subject:subject:date:date :message-id:received; s=bjowvop61wgh; t=1685299542; x= 1687113943; bh=7l2XY6/jtLzPmWCwv8qRsqz/soXWlvD60y6vgEH6zRI=; b=p 4LKtoVehLdG/uAELz6XC1+/ov1ijaoNR7Lgdr1XwnSP0fRtuLnjDPv2JEFlyUkRD uDY6LtqIaoXzLr0BOWAA/SjO1H2WEQuVvuIT7nqwDNkyy50li+7jPklJsxEK4Ycb GGg1tHvKJvKWd/kzCSfQcTHS+L7/uoQnqpvjBQat3aTw0UbHG85i9C0gWSUhvxHZ LsHUh+Y+EZd0jnw4YWvmPT4hVH+HTznYvGYhkpNR40IRRy9LlHWEDkIGs/jUZKHn YJO0bu+hHbcejQkKimajjisqePOeDQlva9TVnFe048ZuV+BB3qpG0quC2jTqW2kH 1TWp7bLvEnPiuZqvcXaPA== Received: from mail.madpilot.net ([IPv6:fd5c:5351:d272::3]) by mail (mail.madpilot.net [IPv6:fd5c:5351:d272::3]) (amavisd-new, port 10026) with ESMTP id C_jaIEOBpVHQ; Sun, 28 May 2023 20:45:42 +0200 (CEST) Message-ID: <0d4e3bda-4ef3-2b22-0a95-319f7f9baf23@madpilot.net> Date: Sun, 28 May 2023 20:45:41 +0200 Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head To: Warner Losh Cc: Alastair Hogge , FreeBSD Current , FreeBSD Current References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> <1635751e73bb8c4c600de231c8d43018@riseup.net> <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> Content-Language: en-US From: Guido Falsi In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4QTngK5CNbz3rm3 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N 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 On 28/05/23 18:22, Warner Losh wrote: > > > On Sun, May 28, 2023, 9:20 AM Guido Falsi > wrote: > > On 28/05/23 16:41, Warner Losh wrote: > > Sill questions.  Did you update only some of your packages? You > really > > need to update them all at the same time to have them be compatible. > > Some projects have a fast moving abi they don't keep compatible > very well. > > > > I'm running FreeBSD head here, using pkgbase. I upgraded a few base > packages (I create them with poudriere). > > I also updated the ports tree and updated other ports using the > resulting binaries (also created with poudriere) > > The pkgs that were updated when xfwm4 stopped working were listed in my > first post [1]. > > > So not all of the non pkg base packages? Have you tried updating them > all? Or you did update them all and the list of what updated was in the > post? I read it when first posted and again now and am unsure which it is... > > It may well be something broke... but I'm just wanting to be double sure > it's against a consistent package set. If something broke, then I can't > help. I see, I did not understand what you meant at first. What I posted was the result of a simple "pkg upgrade", which is what I usually do to update the machine, and usually works quite fine. I have not tested forcing all packages reinstallation ("pkg upgrade -f" if I get it correctly). That is something I was already planning to do. Will report back tomorrow for that. -- Guido Falsi From nobody Mon May 29 03:24:02 2023 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 4QV18x442dz4Wp7y for ; Mon, 29 May 2023 03:24:17 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [66.165.241.226]) (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 (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QV18w0l0wz3jlF for ; Mon, 29 May 2023 03:24:16 +0000 (UTC) (envelope-from pete@nomadlogic.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=nomadlogic.org header.s=04242021 header.b=bEXRGAlx; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 66.165.241.226 as permitted sender) smtp.mailfrom=pete@nomadlogic.org; dmarc=pass (policy=quarantine) header.from=nomadlogic.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomadlogic.org; s=04242021; t=1685330646; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=zaGCs+IQT6DXzicsLPQalgmwzoS84xrxigTYWrZMyFU=; b=bEXRGAlxgD20iwBo5St8MnknqXYl79hc8RHZmtI8Wwe5yNMT6lE5QWvncVsl89jGGaUH+J 0oKBMD748LQ6gzrxLiNHjpKT5DDKPBnE/Q8+6rrjo1abuBSaDnZJl4l26rBAXrOa4DeXd7 2zf4rMYjedUUxxDTsBiN8G3EUe1nk28= Received: from [192.168.1.223] (cpe-24-24-168-214.socal.res.rr.com [24.24.168.214]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id d99024f4 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Mon, 29 May 2023 03:24:05 +0000 (UTC) Content-Type: multipart/alternative; boundary="------------9iohDwtn0vSPyYrMYruihYFZ" Message-ID: Date: Sun, 28 May 2023 20:24:02 -0700 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 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Content-Language: en-US To: FreeBSD Current From: Pete Wright Subject: PinePhone Pro Boots On CURRENT X-Spamd-Result: default: False [-3.63 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.63)[-0.627]; DMARC_POLICY_ALLOW(-0.50)[nomadlogic.org,quarantine]; R_DKIM_ALLOW(-0.20)[nomadlogic.org:s=04242021]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:29802, ipnet:66.165.240.0/22, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; DKIM_TRACE(0.00)[nomadlogic.org:+]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4QV18w0l0wz3jlF X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N This is a multi-part message in MIME format. --------------9iohDwtn0vSPyYrMYruihYFZ Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit i've had this pinephone pro for a few months now and finally got around to attempting to boot FreeBSD on it.  Here's the phone: https://wiki.pine64.org/wiki/PinePhone_Pro I needed to get this serial console adapter which works flawlessly with "cu" (USB TTL Serial Adapter Converter Cable 3.3v/3v3 3.5mm Stereo Jack Cable): https://www.amazon.com/dp/B00XSPECIA?psc=1&ref=ppx_yo2ov_dt_b_product_details then i just downloaded the latest CURRENT snapshot and put it on a microsd card and it booted into multi-user mode.  here's the dmesg: https://www.nomadlogic.org/ppro-dmesg.txt i am working on building a new image now to include the pinephone pro DTB file from Linux to see if that improves some of the hardware detection.  certainly a long way to go before this could be a useful mobile device, but i'm very encouraged that i can actually boot the thing. i suspect we'll need to use iwlwifi to get the AzureWave AW-CM256SM wifi and bluetooth card working... But, once i get the linux DTB for this guy into a disk image i'm going to see if i can get the display up next, but would love to hear any input or pointers from folks with more ARM porting experience than me. thanks! -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA --------------9iohDwtn0vSPyYrMYruihYFZ Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit i've had this pinephone pro for a few months now and finally got around to attempting to boot FreeBSD on it.  Here's the phone:
https://wiki.pine64.org/wiki/PinePhone_Pro

I needed to get this serial console adapter which works flawlessly with "cu"
(USB TTL Serial Adapter Converter Cable 3.3v/3v3 3.5mm Stereo Jack Cable):
https://www.amazon.com/dp/B00XSPECIA?psc=1&ref=ppx_yo2ov_dt_b_product_details

then i just downloaded the latest CURRENT snapshot and put it on a microsd card and it booted into multi-user mode.  here's the dmesg:
https://www.nomadlogic.org/ppro-dmesg.txt

i am working on building a new image now to include the pinephone pro DTB file from Linux to see if that improves some of the hardware detection.  certainly a long way to go before this could be a useful mobile device, but i'm very encouraged that i can actually boot the thing. 

i suspect we'll need to use iwlwifi to get the AzureWave AW-CM256SM wifi and bluetooth card working...

But, once i get the linux DTB for this guy into a disk image i'm going to see if i can get the display up next, but would love to hear any input or pointers from folks with more ARM porting experience than me.

thanks!
-pete



-- 
Pete Wright
pete@nomadlogic.org
@nomadlogicLA
--------------9iohDwtn0vSPyYrMYruihYFZ-- From nobody Mon May 29 04:04:31 2023 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 4QV23Q70r0z4Wrkj for ; Mon, 29 May 2023 04:04:34 +0000 (UTC) (envelope-from agh@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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 (2048 bits) client-digest SHA256) (Client CN "mx1.riseup.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QV23Q31Ykz3nYq for ; Mon, 29 May 2023 04:04:34 +0000 (UTC) (envelope-from agh@riseup.net) Authentication-Results: mx1.freebsd.org; none Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx1.riseup.net (Postfix) with ESMTPS id 4QV23N3TKrzDqP7; Mon, 29 May 2023 04:04:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1685333072; bh=ZejFQSKXBJJgp+gXUPWUoxqn93TmCO2Amo8xkmzD4xE=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Fs//nhgjDrArwHNW2whOp1OK2x4nWhvh+vvqqYEFYjMChfdqNwjz5f83rvgKGcQsl 4Igkqtbx4dzzfHIwWTseRfZmjfSKyyef7hNolVFnKOxoX1hl/RzY6/9WOF4TQM3C9A kJqmlAbcIWUl1usueWVGXXuUhFQ5Mbo45c2iIvrk= X-Riseup-User-ID: 4BD4D962A50B2B441F88B2D4EED9C92BE9CDC76DC3012E9D99CF1C2109C5FA90 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4QV23N1zZdzJmmN; Mon, 29 May 2023 04:04:32 +0000 (UTC) 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 Date: Mon, 29 May 2023 04:04:31 +0000 From: Alastair Hogge To: Pete Wright Cc: FreeBSD Current Subject: Re: PinePhone Pro Boots On CURRENT In-Reply-To: References: Message-ID: <3ffc15964a038a2f9628a8d7e1f42e95@riseup.net> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4QV23Q31Ykz3nYq X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 2023-05-29 03:24, Pete Wright wrote: > i've had this pinephone pro for a few months now and finally got > around to attempting to boot FreeBSD on it. Here's the phone: > https://wiki.pine64.org/wiki/PinePhone_Pro > > I needed to get this serial console adapter which works flawlessly > with "cu" > (USB TTL Serial Adapter Converter Cable 3.3v/3v3 3.5mm Stereo Jack > Cable): > https://www.amazon.com/dp/B00XSPECIA?psc=1&ref=ppx_yo2ov_dt_b_product_details > > then i just downloaded the latest CURRENT snapshot and put it on a > microsd card and it booted into multi-user mode. here's the dmesg: > https://www.nomadlogic.org/ppro-dmesg.txt My gosh, this is fantastically amazing! Great work, thanking you very muchly, and looking forward to the updates :-) To anarchy and health, Alastair From nobody Mon May 29 08:58:27 2023 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 4QV8bG2YgCz4XRMJ for ; Mon, 29 May 2023 08:59:06 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp052.goneo.de (smtp052.goneo.de [85.220.129.60]) (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 4QV8bD5Y8Bz4GG8 for ; Mon, 29 May 2023 08:59:04 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b="lljcf8x/"; spf=none (mx1.freebsd.org: domain of freebsd@walstatt-de.de has no SPF policy when checking 85.220.129.60) smtp.mailfrom=freebsd@walstatt-de.de; dmarc=none Received: from hub2.goneo.de (hub2.goneo.de [85.220.129.53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp5.goneo.de (Postfix) with ESMTPS id 10CF710A333F for ; Mon, 29 May 2023 10:58:57 +0200 (CEST) Received: from hub2.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPS id 7821110A3337 for ; Mon, 29 May 2023 10:58:55 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1685350735; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=SeNb44LyNMZUKWaxnAUkBo9jn1CX+c7pC6SrhgI1DYk=; b=lljcf8x/4/13j6sIPJv7VfQHL8odUKOdyTqoKY6tA3qzYICe4eYPJLNx6Gh8AsRoY0deMg Ns38ZwcQibnYgSOTL/B2Vyxr5t6Cl6eVCYEZ9tpQvGojlG9aJjbUe/cMR8ikV4QAd5QNSd Jc3nzFILotiy9pg6UqNd1p0zlY3heegeI0Yu/hUW9MTe/9jq1oZBGMJEjeWmDFu8W5u2CU wHhIU0vjZeSf6d+d3Kyh5p8BfmAzKiGU2g75JP9DwiG67vMNN4KLRideLJPagjLL3+zmzK LKPjLHPpQmRBsRsghRB2r8UocT/Clta8ZtwU6CCV0ITxTW1ush7ZVvG+4XDYzQ== Received: from thor.intern.walstatt.dynvpn.de (dynamic-089-014-002-075.89.14.pool.telefonica.de [89.14.2.75]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPSA id 511F010A3334 for ; Mon, 29 May 2023 10:58:55 +0200 (CEST) Date: Mon, 29 May 2023 10:58:27 +0200 From: FreeBSD User To: FreeBSD CURRENT Subject: WITH_BEARSSL: -8112 bytes available Message-ID: <20230529105854.1903226d@thor.intern.walstatt.dynvpn.de> Organization: walstatt-de.de 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-UID: 28e1b7 X-Rspamd-UID: 1941ee X-Spamd-Result: default: False [-3.29 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; NEURAL_HAM_MEDIUM(-0.99)[-0.992]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; MIME_GOOD(-0.10)[text/plain]; DKIM_TRACE(0.00)[walstatt-de.de:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_NA(0.00)[no SPF record]; TO_DN_ALL(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; HAS_ORG_HEADER(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[walstatt-de.de]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4QV8bD5Y8Bz4GG8 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N Hello, on CURRENT, enabling in /etc/src.conf WITH_BEARSSL= seems to result in a slightly enlarged loader binary, which seems to have a fixed size supposed on the error I get. See below. The system is amd64 (64 bit), for the record. Somewhere in the past developers mentioned this upcoming problem and provided a knob to adjust the used size - I forgot about that knob and I couldn't find it even in the loader docs - or looked at the wrong places. Can someone help me out here? The first error stops compileing world/kernel, but taking a second run, the error goes away. Kind regards and thanks in advance, oh [...] --- all_subdir_stand/efi --- SOURCE_DATE_EPOCH=1451606400 objcopy -j .peheader -j .text -j .sdata -j .data -j .dynamic -j .dynsym -j .rel.dyn -j .rela.dyn -j .reloc -j .eh_frame -j set_Xcommand_set -j set_Xficl_compile_set --output-target=efi-app-x86_64 loader_4th.sym loader_4th.efi --- all_subdir_stand/i386 --- -8112 bytes available 7.71 real 12.86 user 3.08 sys make[1]: stopped in /usr/src [...] -- O. Hartmann From nobody Mon May 29 13:03:26 2023 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 4QVG1P0J3Tz4Xkt3 for ; Mon, 29 May 2023 13:03:37 +0000 (UTC) (envelope-from jon@xyinn.org) Received: from mail-4317.proton.ch (mail-4317.proton.ch [185.70.43.17]) (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 "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QVG1N5MSSz4l2j for ; Mon, 29 May 2023 13:03:35 +0000 (UTC) (envelope-from jon@xyinn.org) Authentication-Results: mx1.freebsd.org; none Date: Mon, 29 May 2023 13:03:26 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xyinn.org; s=protonmail; t=1685365410; x=1685624610; bh=rahZDv1dPCzO8+6Z6K71WSNZ9sPLetQKAonhM14DLfE=; h=Date:To:From:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=SshrP0i8mqrkPk7dC9UBMiO7G3qhsZowsSmCXw79D8VArE34Fa0xAsyuNwfQ2p47O 0Po8o1N9bhCMra7WbBT2CuXW2bC36Xzdf+S7RE4Rnu49JWRfy11pQmReBIy3gqbwHC 64qJfTCo7POQTLbKYqvi6zBBFsOMInhGtoSsr7eMvRlXkrHtBjB3Qa1eAonPzeVoOw RoNWxPP8Hov7EIRpMJ8oqNUq7mU3gTOc8dA+chgJMNgTJsqQOomnh8xE92OKsNZ5o7 566x/86oaG/j6HLGUdXMZbiIDKEeNeiWm98SyAy3Xpeo4AbJ3aw1+Q9/UyMlNYIiYZ 5Vvmncx/RdXlw== To: pete@nomadlogic.org, freebsd-current@freebsd.org From: Jonathan Vasquez Subject: Re: PinePhone Pro Boots On CURRENT Message-ID: <4d_H-Oc7E9Afo9sSD07rhwMD_cpXkEBKuipAA2Nx9KzUHt64_uDXaGL63-vEmtT_6SXD6W20EVh2UJYh6ZoNmLcS-ipgubA9PW8ieitSELA=@xyinn.org> In-Reply-To: References: Feedback-ID: 12351801:user:proton 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 Content-Type: multipart/alternative; boundary="b1_bg964Xe7GXKvMTmZkPB4T6sm2PgBVoQgOq5ZN8AAw" X-Rspamd-Queue-Id: 4QVG1N5MSSz4l2j X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.43.0/24, country:CH] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N This is a multi-part message in MIME format. --b1_bg964Xe7GXKvMTmZkPB4T6sm2PgBVoQgOq5ZN8AAw Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 VGhpcyBpcyBhd2Vzb21lIHN0dWZmLiBJJ20gdmVyeSBoYXBweSBhbmQgZXhjaXRlZCB0byBoZWFy IHRoaXMgYW5kIHdpbGwgYmUgZm9sbG93aW5nIHlvdXIgcHJvZ3Jlc3MuIEkgcHJvYmFibHkgd2ls bCBmaW5hbGx5IGJ1eSB0aGUgUGluZVBob25lIFBybyBqdXN0IHRvIHRlc3Qgb3V0IHlvdXIgaW1h Z2VzLgoKS2VlcCBpdCB1cC4KClBTOiBaRlMgb24gdGhlIHBob25lIDwzIGhhaGEKCkpvbmF0aGFu IFZhc3F1ZXoKUEdQOiAzNERBIDg1OEMgMTQ0NyA1MDlFIEM3N0EgRDQ5RiBGQjg1IDkwQjcgQzRD QSA1Mjc5ClNlbnQgd2l0aCBQcm90b25NYWlsIFNlY3VyZSBFbWFpbAoKU2VudCBmcm9tIFByb3Rv biBNYWlsIG1vYmlsZQoKLS0tLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLS0tLQpPbiBNYXkg MjgsIDIwMjMsIDIzOjI0LCBQZXRlIFdyaWdodCB3cm90ZToKCj4gaSd2ZSBoYWQgdGhpcyBwaW5l cGhvbmUgcHJvIGZvciBhIGZldyBtb250aHMgbm93IGFuZCBmaW5hbGx5IGdvdCBhcm91bmQgdG8g YXR0ZW1wdGluZyB0byBib290IEZyZWVCU0Qgb24gaXQuIEhlcmUncyB0aGUgcGhvbmU6Cj4gaHR0 cHM6Ly93aWtpLnBpbmU2NC5vcmcvd2lraS9QaW5lUGhvbmVfUHJvCj4KPiBJIG5lZWRlZCB0byBn ZXQgdGhpcyBzZXJpYWwgY29uc29sZSBhZGFwdGVyIHdoaWNoIHdvcmtzIGZsYXdsZXNzbHkgd2l0 aCAiY3UiCj4gKFVTQiBUVEwgU2VyaWFsIEFkYXB0ZXIgQ29udmVydGVyIENhYmxlIDMuM3YvM3Yz IDMuNW1tIFN0ZXJlbyBKYWNrIENhYmxlKToKPiBodHRwczovL3d3dy5hbWF6b24uY29tL2RwL0Iw MFhTUEVDSUE/cHNjPTEmcmVmPXBweF95bzJvdl9kdF9iX3Byb2R1Y3RfZGV0YWlscwo+Cj4gdGhl biBpIGp1c3QgZG93bmxvYWRlZCB0aGUgbGF0ZXN0IENVUlJFTlQgc25hcHNob3QgYW5kIHB1dCBp dCBvbiBhIG1pY3Jvc2QgY2FyZCBhbmQgaXQgYm9vdGVkIGludG8gbXVsdGktdXNlciBtb2RlLiBo ZXJlJ3MgdGhlIGRtZXNnOgo+IGh0dHBzOi8vd3d3Lm5vbWFkbG9naWMub3JnL3Bwcm8tZG1lc2cu dHh0Cj4KPiBpIGFtIHdvcmtpbmcgb24gYnVpbGRpbmcgYSBuZXcgaW1hZ2Ugbm93IHRvIGluY2x1 ZGUgdGhlIHBpbmVwaG9uZSBwcm8gRFRCIGZpbGUgZnJvbSBMaW51eCB0byBzZWUgaWYgdGhhdCBp bXByb3ZlcyBzb21lIG9mIHRoZSBoYXJkd2FyZSBkZXRlY3Rpb24uIGNlcnRhaW5seSBhIGxvbmcg d2F5IHRvIGdvIGJlZm9yZSB0aGlzIGNvdWxkIGJlIGEgdXNlZnVsIG1vYmlsZSBkZXZpY2UsIGJ1 dCBpJ20gdmVyeSBlbmNvdXJhZ2VkIHRoYXQgaSBjYW4gYWN0dWFsbHkgYm9vdCB0aGUgdGhpbmcu Cj4KPiBpIHN1c3BlY3Qgd2UnbGwgbmVlZCB0byB1c2UgaXdsd2lmaSB0byBnZXQgdGhlIEF6dXJl V2F2ZSBBVy1DTTI1NlNNIHdpZmkgYW5kIGJsdWV0b290aCBjYXJkIHdvcmtpbmcuLi4KPgo+IEJ1 dCwgb25jZSBpIGdldCB0aGUgbGludXggRFRCIGZvciB0aGlzIGd1eSBpbnRvIGEgZGlzayBpbWFn ZSBpJ20gZ29pbmcgdG8gc2VlIGlmIGkgY2FuIGdldCB0aGUgZGlzcGxheSB1cCBuZXh0LCBidXQg d291bGQgbG92ZSB0byBoZWFyIGFueSBpbnB1dCBvciBwb2ludGVycyBmcm9tIGZvbGtzIHdpdGgg bW9yZSBBUk0gcG9ydGluZyBleHBlcmllbmNlIHRoYW4gbWUuCj4KPiB0aGFua3MhCj4gLXBldGUK Pgo+IC0tCj4gUGV0ZSBXcmlnaHQKPiBwZXRlQG5vbWFkbG9naWMub3JnCj4gQG5vbWFkbG9naWNM QQ== --b1_bg964Xe7GXKvMTmZkPB4T6sm2PgBVoQgOq5ZN8AAw Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 VGhpcyBpcyBhd2Vzb21lIHN0dWZmLiBJJ20gdmVyeSBoYXBweSBhbmQgZXhjaXRlZCB0byBoZWFy IHRoaXMgYW5kIHdpbGwgYmUgZm9sbG93aW5nIHlvdXIgcHJvZ3Jlc3MuIEkgcHJvYmFibHkgd2ls bCBmaW5hbGx5IGJ1eSB0aGUgUGluZVBob25lIFBybyBqdXN0IHRvIHRlc3Qgb3V0IHlvdXIgaW1h Z2VzLiA8YnI+PGJyPktlZXAgaXQgdXAuPGJyPjxicj5QUzogWkZTIG9uIHRoZSBwaG9uZSAmbHQ7 MyBoYWhhPGJyPjxicj48YnI+PGRpdj5Kb25hdGhhbiBWYXNxdWV6PGJyIC8+PC9kaXY+PGRpdj5Q R1A6IDM0REEgODU4QyAxNDQ3IDUwOUUgQzc3QSAgRDQ5RiBGQjg1IDkwQjcgQzRDQSA1Mjc5PGJy IC8+PC9kaXY+PGRpdj5TZW50IHdpdGggUHJvdG9uTWFpbCBTZWN1cmUgRW1haWw8YnIgLz48L2Rp dj48ZGl2PjxiciAvPjwvZGl2Pjxicj48YnI+U2VudCBmcm9tIFByb3RvbiBNYWlsIG1vYmlsZTxi cj48YnI+PGJyPjxicj4tLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tLS0tPGJyPk9uIE1h eSAyOCwgMjAyMywgMjM6MjQsIFBldGUgV3JpZ2h0IDwgcGV0ZUBub21hZGxvZ2ljLm9yZz4gd3Jv dGU6PGJsb2NrcXVvdGUgY2xhc3M9InByb3Rvbm1haWxfcXVvdGUiPjxicj48aHRtbD4NCiAgPGhl YWQ+DQoNCiAgICA8bWV0YSBodHRwLWVxdWl2PSJjb250ZW50LXR5cGUiIGNvbnRlbnQ9InRleHQv aHRtbDsgY2hhcnNldD1VVEYtOCI+DQogIDwvaGVhZD4NCiAgPGJvZHk+DQogICAgaSd2ZSBoYWQg dGhpcyBwaW5lcGhvbmUgcHJvIGZvciBhIGZldyBtb250aHMgbm93IGFuZCBmaW5hbGx5IGdvdA0K ICAgIGFyb3VuZCB0byBhdHRlbXB0aW5nIHRvIGJvb3QgRnJlZUJTRCBvbiBpdC7CoCBIZXJlJ3Mg dGhlIHBob25lOjxicj4NCiAgICA8YSBjbGFzcz0ibW96LXR4dC1saW5rLWZyZWV0ZXh0IiBocmVm PSJodHRwczovL3dpa2kucGluZTY0Lm9yZy93aWtpL1BpbmVQaG9uZV9Qcm8iPmh0dHBzOi8vd2lr aS5waW5lNjQub3JnL3dpa2kvUGluZVBob25lX1BybzwvYT48YnI+DQogICAgPGJyPg0KICAgIEkg bmVlZGVkIHRvIGdldCB0aGlzIHNlcmlhbCBjb25zb2xlIGFkYXB0ZXIgd2hpY2ggd29ya3MgZmxh d2xlc3NseQ0KICAgIHdpdGggImN1Ijxicj4NCiAgICAoPHNwYW4gaWQ9InByb2R1Y3RUaXRsZSIg Y2xhc3M9ImEtc2l6ZS1sYXJnZQ0KICAgICAgcHJvZHVjdC10aXRsZS13b3JkLWJyZWFrIj5VU0Ig VFRMIFNlcmlhbCBBZGFwdGVyIENvbnZlcnRlciBDYWJsZQ0KICAgICAgMy4zdi8zdjMgMy41bW0g U3RlcmVvIEphY2sgQ2FibGUpOjwvc3Bhbj48YnI+DQo8YSBjbGFzcz0ibW96LXR4dC1saW5rLWZy ZWV0ZXh0IiBocmVmPSJodHRwczovL3d3dy5hbWF6b24uY29tL2RwL0IwMFhTUEVDSUE/cHNjPTEm YW1wO3JlZj1wcHhfeW8yb3ZfZHRfYl9wcm9kdWN0X2RldGFpbHMiPmh0dHBzOi8vd3d3LmFtYXpv bi5jb20vZHAvQjAwWFNQRUNJQT9wc2M9MSZhbXA7cmVmPXBweF95bzJvdl9kdF9iX3Byb2R1Y3Rf ZGV0YWlsczwvYT48YnI+DQogICAgPGJyPg0KICAgIHRoZW4gaSBqdXN0IGRvd25sb2FkZWQgdGhl IGxhdGVzdCBDVVJSRU5UIHNuYXBzaG90IGFuZCBwdXQgaXQgb24gYQ0KICAgIG1pY3Jvc2QgY2Fy ZCBhbmQgaXQgYm9vdGVkIGludG8gbXVsdGktdXNlciBtb2RlLsKgIGhlcmUncyB0aGUgZG1lc2c6 PGJyPg0KICAgIDxhIGNsYXNzPSJtb3otdHh0LWxpbmstZnJlZXRleHQiIGhyZWY9Imh0dHBzOi8v d3d3Lm5vbWFkbG9naWMub3JnL3Bwcm8tZG1lc2cudHh0Ij5odHRwczovL3d3dy5ub21hZGxvZ2lj Lm9yZy9wcHJvLWRtZXNnLnR4dDwvYT48YnI+DQogICAgPGJyPg0KICAgIGkgYW0gd29ya2luZyBv biBidWlsZGluZyBhIG5ldyBpbWFnZSBub3cgdG8gaW5jbHVkZSB0aGUgcGluZXBob25lDQogICAg cHJvIERUQiBmaWxlIGZyb20gTGludXggdG8gc2VlIGlmIHRoYXQgaW1wcm92ZXMgc29tZSBvZiB0 aGUgaGFyZHdhcmUNCiAgICBkZXRlY3Rpb24uwqAgY2VydGFpbmx5IGEgbG9uZyB3YXkgdG8gZ28g YmVmb3JlIHRoaXMgY291bGQgYmUgYSB1c2VmdWwNCiAgICBtb2JpbGUgZGV2aWNlLCBidXQgaSdt IHZlcnkgZW5jb3VyYWdlZCB0aGF0IGkgY2FuIGFjdHVhbGx5IGJvb3QgdGhlDQogICAgdGhpbmcu wqAgPGJyPg0KICAgIDxicj4NCiAgICBpIHN1c3BlY3Qgd2UnbGwgbmVlZCB0byB1c2UgaXdsd2lm aSB0byBnZXQgdGhlIEF6dXJlV2F2ZSBBVy1DTTI1NlNNDQogICAgd2lmaSBhbmQgYmx1ZXRvb3Ro IGNhcmQgd29ya2luZy4uLjxicj4NCiAgICA8YnI+DQogICAgQnV0LCBvbmNlIGkgZ2V0IHRoZSBs aW51eCBEVEIgZm9yIHRoaXMgZ3V5IGludG8gYSBkaXNrIGltYWdlIGknbQ0KICAgIGdvaW5nIHRv IHNlZSBpZiBpIGNhbiBnZXQgdGhlIGRpc3BsYXkgdXAgbmV4dCwgYnV0IHdvdWxkIGxvdmUgdG8N CiAgICBoZWFyIGFueSBpbnB1dCBvciBwb2ludGVycyBmcm9tIGZvbGtzIHdpdGggbW9yZSBBUk0g cG9ydGluZw0KICAgIGV4cGVyaWVuY2UgdGhhbiBtZS48YnI+DQogICAgPGJyPg0KICAgIHRoYW5r cyE8YnI+DQogICAgLXBldGU8YnI+DQogICAgPGJyPg0KICAgIDxicj4NCiAgICA8YnI+DQogICAg PHByZSBjbGFzcz0ibW96LXNpZ25hdHVyZSIgY29scz0iNzIiPi0tDQpQZXRlIFdyaWdodA0KPGEg Y2xhc3M9Im1vei10eHQtbGluay1hYmJyZXZpYXRlZCIgaHJlZj0ibWFpbHRvOnBldGVAbm9tYWRs b2dpYy5vcmciPnBldGVAbm9tYWRsb2dpYy5vcmc8L2E+DQpAbm9tYWRsb2dpY0xBPC9wcmU+DQog IDwvYm9keT4NCjwvaHRtbD4NCjwvZGl2Pg== --b1_bg964Xe7GXKvMTmZkPB4T6sm2PgBVoQgOq5ZN8AAw-- From nobody Mon May 29 13:15:29 2023 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 4QVGHB6Flgz4XlsK for ; Mon, 29 May 2023 13:15:34 +0000 (UTC) (envelope-from Mathias.Picker@virtual-earth.de) Received: from www94.your-server.de (www94.your-server.de [213.133.104.94]) (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 4QVGHB4XhPz3G5T for ; Mon, 29 May 2023 13:15:34 +0000 (UTC) (envelope-from Mathias.Picker@virtual-earth.de) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=virtual-earth.de; s=default_1811; h=Content-Transfer-Encoding:Content-Type: MIME-Version:Message-ID:References:In-Reply-To:Subject:To:From:Date:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=hXDS7sHo4eR/zZVLtmsJN1KN8VjEaZGDRs80clGw51s=; b=OacbfwmxujbUEN8L+BOLFinU+p t/Y+Ws/t53Hivz3kT7iWPovP6vK3AQdfNowoeehz8FSYL2c8ewLK33yALfF9NbrjVHlSQWf1DN/w/ DDHn36BlPwOgOezxdLoCPimI43+Eq1PvW57izgKLdMDVYGud/lwNkpL8OY1dVDjFUBZZLAlBkmcdA Hd3rLkfG6RjEoSLoS0MZezQ+cc5GdDg2BZcCL5TtOYZb/cVk2VVHqIprkSuD9NO7lmT2sp7WK5Jv1 nkVxRPCWANclUC94MMSymNbiq4u+0saFQDBYX6C19Q3YP/lhclWdgSJcq7OkNhLiwjZNsvWvWezxs tqLtllGQ==; Received: from sslproxy01.your-server.de ([78.46.139.224]) by www94.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q3cih-0008sh-8T; Mon, 29 May 2023 15:15:31 +0200 Received: from [2a01:598:b9b2:2589:4033:397a:5340:5e8] (helo=[IPv6:::1]) by sslproxy01.your-server.de with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q3cih-000Oyk-1o; Mon, 29 May 2023 15:15:31 +0200 Date: Mon, 29 May 2023 15:15:29 +0200 From: Mathias Picker To: freebsd-current@freebsd.org, Pete Wright , FreeBSD Current Subject: Re: PinePhone Pro Boots On CURRENT User-Agent: K-9 Mail for Android In-Reply-To: References: Message-ID: <39F2BE9D-A185-44E6-A8D1-8AE58BB99478@virtual-earth.de> 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 Content-Type: multipart/alternative; boundary=----S5VFM3RKTI2IBX545GGLZWRSR3VCZ2 Content-Transfer-Encoding: 7bit X-Authenticated-Sender: Mathias.Picker@virtual-earth.de X-Virus-Scanned: Clear (ClamAV 0.103.8/26922/Mon May 29 09:22:38 2023) X-Rspamd-Queue-Id: 4QVGHB4XhPz3G5T X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:213.133.96.0/19, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N ------S5VFM3RKTI2IBX545GGLZWRSR3VCZ2 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am 29=2E Mai 2023 05:24:02 MESZ schrieb Pete Wright = : >i've had this pinephone pro for a few months now and finally got around t= o attempting to boot FreeBSD on it=2E=C2=A0 Here's the phone: >https://wiki=2Epine64=2Eorg/wiki/PinePhone_Pro > >I needed to get this serial console adapter which works flawlessly with "= cu" >(USB TTL Serial Adapter Converter Cable 3=2E3v/3v3 3=2E5mm Stereo Jack Ca= ble): >https://www=2Eamazon=2Ecom/dp/B00XSPECIA?psc=3D1&ref=3Dppx_yo2ov_dt_b_pro= duct_details > >then i just downloaded the latest CURRENT snapshot and put it on a micros= d card and it booted into multi-user mode=2E=C2=A0 here's the dmesg: >https://www=2Enomadlogic=2Eorg/ppro-dmesg=2Etxt > >i am working on building a new image now to include the pinephone pro DTB= file from Linux to see if that improves some of the hardware detection=2E= =C2=A0 certainly a long way to go before this could be a useful mobile devi= ce, but i'm very encouraged that i can actually boot the thing=2E > >i suspect we'll need to use iwlwifi to get the AzureWave AW-CM256SM wifi = and bluetooth card working=2E=2E=2E > >But, once i get the linux DTB for this guy into a disk image i'm going to= see if i can get the display up next, but would love to hear any input or = pointers from folks with more ARM porting experience than me=2E > >thanks! >-pete > > > >--=20 >Pete Wright >pete@nomadlogic=2Eorg >@nomadlogicLA Gesehen? Leider bin ich inzwischen Fold-Abh=C3=A4ngig=2E Trotzdem cool! Mathias Picker Gesch=C3=A4ftsf=C3=BChrer virtual earth Gesellschaft f=C3=BCr Wissens re/pr=C3=A4 sentation mbH Westendstr=2E 142 80339 M=C3=BCnchen +4915256178344 ------S5VFM3RKTI2IBX545GGLZWRSR3VCZ2 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Am 29=2E Mai 2023 05:= 24:02 MESZ schrieb Pete Wright <pete@nomadlogic=2Eorg>:
i've had this pinephone pro for a few months now and finally got around to attempting to boot FreeBSD on it=2E  Here's the phone:<= br> https://wiki=2Epine64=2Eorg/wiki/PinePhone_Pro

I needed to get this serial console adapter which works flawlessly with "cu"
(USB TTL Serial Adapter Converter Cable 3=2E3v/3v3 3=2E5mm Stereo Jack Cable):
https://www=2Ea= mazon=2Ecom/dp/B00XSPECIA?psc=3D1&ref=3Dppx_yo2ov_dt_b_product_details<= /a>

then i just downloaded the latest CURRENT snapshot and put it on a microsd card and it booted into multi-user mode=2E  here's the dm= esg:
https://www=2Enomadlogic=2Eorg/ppro-dmesg=2Etxt
i am working on building a new image now to include the pinephone pro DTB file from Linux to see if that improves some of the hardware detection=2E  certainly a long way to go before this could be a u= seful mobile device, but i'm very encouraged that i can actually boot the thing=2E 

i suspect we'll need to use iwlwifi to get the AzureWave AW-CM256SM wifi and bluetooth card working=2E=2E=2E

But, once i get the linux DTB for this guy into a disk image i'm going to see if i can get the display up next, but would love to hear any input or pointers from folks with more ARM porting experience than me=2E

thanks!
-pete



--=20
Pete Wright
pete@nomadlogic=2Eorg
@nomadlogicLA

Gesehen?

L= eider bin ich inzwischen Fold-Abh=C3=A4ngig=2E
Trotzdem cool!
Mathias Picker
Gesch=C3=A4ftsf=C3=BChrer
virtual earth G= esellschaft f=C3=BCr Wissens re/pr=C3=A4 sentation mbH
Westendstr=2E 142=
80339 M=C3=BCnchen
+4915256178344
------S5VFM3RKTI2IBX545GGLZWRSR3VCZ2-- From nobody Mon May 29 13:20:50 2023 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 4QVGPK71S8z4XmHp for ; Mon, 29 May 2023 13:20:53 +0000 (UTC) (envelope-from Mathias.Picker@virtual-earth.de) Received: from www94.your-server.de (www94.your-server.de [213.133.104.94]) (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 4QVGPJ6TWnz3Gwg for ; Mon, 29 May 2023 13:20:52 +0000 (UTC) (envelope-from Mathias.Picker@virtual-earth.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=virtual-earth.de header.s=default_1811 header.b=hv0m5JVM; spf=pass (mx1.freebsd.org: domain of Mathias.Picker@virtual-earth.de designates 213.133.104.94 as permitted sender) smtp.mailfrom=Mathias.Picker@virtual-earth.de; dmarc=pass (policy=none) header.from=virtual-earth.de DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=virtual-earth.de; s=default_1811; h=Content-Transfer-Encoding:Content-Type: MIME-Version:Message-ID:References:In-Reply-To:Subject:To:From:Date:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=Fp4+yv+lSymLhQFMMLeIBONb69O/MMdtnSYXGgJLqgk=; b=hv0m5JVM8lR9vpc9iJnVXl39+H fGK95r3al12rNoCArMQewVN/b1gzD7dUFikz9HObyvT0/3EADYxDIQGvf+8DGtqGxtzDLwZeKDvAd /nrJdGFfiYSBZc7peXxuD8wbrrj45KNCBiIAnkthlGmqi3fWW4qFNElcv3bHLPFHSghY1qxWASgom 20Gu1Dupxsc+Ce4nbRhf9e3TF0y7l8/Uygvf519OPg0XYnjovGBxSxyDJt1Kkk9cTl3nm7//IIFzh /YbFPyauwL9tBiIAWhY8RwJBvbB5fgg399M81UKM3oAWxG54XynF1pMPP8qhJLthzgt2kcUfOmF2B aGnHWpTQ==; Received: from sslproxy01.your-server.de ([78.46.139.224]) by www94.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q3cnr-0009xt-Rx; Mon, 29 May 2023 15:20:51 +0200 Received: from [2a01:598:b9b2:2589:4033:397a:5340:5e8] (helo=[IPv6:::1]) by sslproxy01.your-server.de with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q3cnr-000OWO-Kt; Mon, 29 May 2023 15:20:51 +0200 Date: Mon, 29 May 2023 15:20:50 +0200 From: Mathias Picker To: freebsd-current@freebsd.org, Pete Wright , FreeBSD Current Subject: Re: PinePhone Pro Boots On CURRENT User-Agent: K-9 Mail for Android In-Reply-To: <39F2BE9D-A185-44E6-A8D1-8AE58BB99478@virtual-earth.de> References: <39F2BE9D-A185-44E6-A8D1-8AE58BB99478@virtual-earth.de> Message-ID: 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 Content-Type: multipart/alternative; boundary=----CZ1ANPIFX6YNOO8AR82ZL848DYRGT4 Content-Transfer-Encoding: 7bit X-Authenticated-Sender: Mathias.Picker@virtual-earth.de X-Virus-Scanned: Clear (ClamAV 0.103.8/26922/Mon May 29 09:22:38 2023) X-Spamd-Result: default: False [-4.09 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.994]; DMARC_POLICY_ALLOW(-0.50)[virtual-earth.de,none]; R_DKIM_ALLOW(-0.20)[virtual-earth.de:s=default_1811]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[78.46.139.224:received]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; ASN(0.00)[asn:24940, ipnet:213.133.96.0/19, country:DE]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; HAS_X_AS(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[virtual-earth.de:+]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; RCVD_COUNT_THREE(0.00)[3]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4QVGPJ6TWnz3Gwg X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N ------CZ1ANPIFX6YNOO8AR82ZL848DYRGT4 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am 29=2E Mai 2023 15:15:29 MESZ schrieb Mathias Picker : >Am 29=2E Mai 2023 05:24:02 MESZ schrieb Pete Wright : >>i've had this pinephone pro for a few months now and finally got around = to attempting to boot FreeBSD on it=2E=C2=A0 Here's the phone: >>https://wiki=2Epine64=2Eorg/wiki/PinePhone_Pro >> >>I needed to get this serial console adapter which works flawlessly with = "cu" >>(USB TTL Serial Adapter Converter Cable 3=2E3v/3v3 3=2E5mm Stereo Jack C= able): >>https://www=2Eamazon=2Ecom/dp/B00XSPECIA?psc=3D1&ref=3Dppx_yo2ov_dt_b_pr= oduct_details >> >>then i just downloaded the latest CURRENT snapshot and put it on a micro= sd card and it booted into multi-user mode=2E=C2=A0 here's the dmesg: >>https://www=2Enomadlogic=2Eorg/ppro-dmesg=2Etxt >> >>i am working on building a new image now to include the pinephone pro DT= B file from Linux to see if that improves some of the hardware detection=2E= =C2=A0 certainly a long way to go before this could be a useful mobile devi= ce, but i'm very encouraged that i can actually boot the thing=2E >> >>i suspect we'll need to use iwlwifi to get the AzureWave AW-CM256SM wifi= and bluetooth card working=2E=2E=2E >> >>But, once i get the linux DTB for this guy into a disk image i'm going t= o see if i can get the display up next, but would love to hear any input or= pointers from folks with more ARM porting experience than me=2E >> >>thanks! >>-pete >> >> >> >>--=20 >>Pete Wright >>pete@nomadlogic=2Eorg >>@nomadlogicLA > >Gesehen? > >Leider bin ich inzwischen Fold-Abh=C3=A4ngig=2E >Trotzdem cool! >Mathias Picker >Gesch=C3=A4ftsf=C3=BChrer >virtual earth Gesellschaft f=C3=BCr Wissens re/pr=C3=A4 sentation mbH >Westendstr=2E 142 >80339 M=C3=BCnchen >+4915256178344 Sorrry,that shoud have been a forward=2E=20 Too much sun burned my brain out I guess=E2=80=A6 And that's great news! Mathias Picker Gesch=C3=A4ftsf=C3=BChrer virtual earth Gesellschaft f=C3=BCr Wissens re/pr=C3=A4 sentation mbH Westendstr=2E 142 80339 M=C3=BCnchen +4915256178344 ------CZ1ANPIFX6YNOO8AR82ZL848DYRGT4 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Am 29=2E Mai 2023 15:= 15:29 MESZ schrieb Mathias Picker <Mathias=2EPicker@virtual-earth=2Ede&g= t;:
Am 29=2E Mai 2023 05:24:02 ME= SZ schrieb Pete Wright <pete@nomadlogic=2Eorg>:
i've had this pinephone pro for a few months now and finally got around to attempting to boot FreeBSD on it=2E  Here's the phone:<= br> https://wiki=2Epine64=2Eorg/wiki/PinePhone_Pro

I needed to get this serial console adapter which works flawlessly with "cu"
(USB TTL Serial Adapter Converter Cable 3=2E3v/3v3 3=2E5mm Stereo Jack Cable):
https://www=2Ea= mazon=2Ecom/dp/B00XSPECIA?psc=3D1&ref=3Dppx_yo2ov_dt_b_product_details<= /a>

then i just downloaded the latest CURRENT snapshot and put it on a microsd card and it booted into multi-user mode=2E  here's the dm= esg:
https://www=2Enomadlogic=2Eorg/ppro-dmesg=2Etxt
i am working on building a new image now to include the pinephone pro DTB file from Linux to see if that improves some of the hardware detection=2E  certainly a long way to go before this could be a u= seful mobile device, but i'm very encouraged that i can actually boot the thing=2E 

i suspect we'll need to use iwlwifi to get the AzureWave AW-CM256SM wifi and bluetooth card working=2E=2E=2E

But, once i get the linux DTB for this guy into a disk image i'm going to see if i can get the display up next, but would love to hear any input or pointers from folks with more ARM porting experience than me=2E

thanks!
-pete



--=20
Pete Wright
pete@nomadlogic=2Eorg
@nomadlogicLA

Gesehen?

L= eider bin ich inzwischen Fold-Abh=C3=A4ngig=2E
Trotzdem cool!
Mathias Picker
Gesch=C3=A4ftsf=C3=BChrer
virtual earth G= esellschaft f=C3=BCr Wissens re/pr=C3=A4 sentation mbH
Westendstr=2E 142=
80339 M=C3=BCnchen
+4915256178344

Sorrry,that shoud have been a forward=2E
Too= much sun burned my brain out I guess=E2=80=A6

And that's great news= !
Mathias Picker
Gesch=C3=A4ftsf=C3=BChrer
vir= tual earth Gesellschaft f=C3=BCr Wissens re/pr=C3=A4 sentation mbH
Weste= ndstr=2E 142
80339 M=C3=BCnchen
+4915256178344
------CZ1ANPIFX6YNOO8AR82ZL848DYRGT4-- From nobody Mon May 29 13:55:11 2023 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 4QVH8z2K96z4Xpk2 for ; Mon, 29 May 2023 13:55:15 +0000 (UTC) (envelope-from gbe@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 4QVH8z1tfVz3Ljl; Mon, 29 May 2023 13:55:15 +0000 (UTC) (envelope-from gbe@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685368515; 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=Pzlpc8adgxjJlon5zEbKX7Wrb50Oy8SjDv02bnclboI=; b=js4ZJ7XUvmrl3mV8rpbl9N3eDXudyu748+GZHLDRWgR6spYXc+Y4LOEOBWH32tSzAqaF2k bFsM5u1lFFPLXq4BpoSc76E4QntLeVLcrHUea6gBP6NGya4kC2qn8iHyO03G+Jl7lriGYu bGRJXNf7fW3HH2TenLneP6jInbhZhhI4sZcvKhwtc+1hgpuhvGgwsTfRYEvBHePLQjKnsH Ffvi+UxZdx1q4W63FoM4zvviYnfk/3VrCKynydvBlG4UeIQZicEW19Ins7LhSsWmDrHK7c QWe2tNahXdfMEKI330UBdR74dMjYI+e49Te6HjZ8PVHN0CNKFLVFr6zl/m1rhQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685368515; 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=Pzlpc8adgxjJlon5zEbKX7Wrb50Oy8SjDv02bnclboI=; b=edrSV0Fx3vVsGdPb6b+GwRmpcSa3hd3tbSC6ISmf965RWGLzxFdKiK+V7CyymYQCW73DG6 dTByY8kjx4wN51yS0crNfKGDTmDnWxbfcxrNksaRUOEO4r1S4Rs7jz952lfhv93hYaMzPu E2R4RoG9PETe3MMlvGcwPf7yrHb9Y96YcE05XqzDvCj1YepDfZvG1npAWB/B5VT+QoZOaI 7Z6WPWw0/XqmwM++gtFoeAZ1iy3VWX2POdZo7rfq24GYJkN9nX5d6TKhEnxLgIcPkGNVKd AQl0ZmWlgDnDDZ3vAf8q6O+NxG/xPlWqNdho0I5emnU5oRtmFDz+uF6SOgQgfQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1685368515; a=rsa-sha256; cv=none; b=DQW2wzCgZ76BphzsgkpZxvc//l36730wV6Nbw7xDvwCOSUUxMiLvHujeM26wBVcrDtjeVm VrAumiwqoipA9d8pOkXZ6yb8uRthWw00VVl+WSG3fCwTLeMQVYZZnJ0kxSaala9JNv0fJm uhknFqeSRzBJh+T176PlD0+jR6VqyfZDNmU2IDwYq7/p4JUvZUUUbH23J8h2IUqIlI4+En fJSzM28YR2o1FIv51Sjww1RqvIzYrr25Q9cdF/xHfWv91g2OWj+7HzQUJdS+6r/KkSt8Ii bUxnD0BYwx0gPm79XwzZiu4fAKMy9yFzYvOLJ/sG0Y0+ynhMJHSs+u6Hs0XOcQ== Received: from localhost (p200300cb8732752b980dec3cb70c7fba.dip0.t-ipconnect.de [IPv6:2003:cb:8732:752b:980d:ec3c:b70c:7fba]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: gbe) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QVH8y5Jqzz1BVM; Mon, 29 May 2023 13:55:14 +0000 (UTC) (envelope-from gbe@freebsd.org) Date: Mon, 29 May 2023 15:55:11 +0200 From: Gordon Bergling To: FreeBSD User Cc: FreeBSD CURRENT Subject: Re: WITH_BEARSSL: -8112 bytes available Message-ID: References: <20230529105854.1903226d@thor.intern.walstatt.dynvpn.de> 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 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="8iIMxk1Pka9FlU7l" Content-Disposition: inline In-Reply-To: <20230529105854.1903226d@thor.intern.walstatt.dynvpn.de> X-Url: X-Operating-System: FreeBSD 13.2-STABLE amd64 X-Host-Uptime: 3:51PM up 4 days, 21:47, 3 users, load averages: 0.26, 0.23, 0.21 X-ThisMailContainsUnwantedMimeParts: N --8iIMxk1Pka9FlU7l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Mon, May 29, 2023 at 10:58:27AM +0200, FreeBSD User wrote: > on CURRENT, enabling in /etc/src.conf >=20 > WITH_BEARSSL=3D >=20 > seems to result in a slightly enlarged loader binary, which seems to have= a fixed size > supposed on the error I get. See below. >=20 > The system is amd64 (64 bit), for the record. >=20 > Somewhere in the past developers mentioned this upcoming problem and prov= ided a knob to adjust > the used size - I forgot about that knob and I couldn't find it even in t= he loader docs - or > looked at the wrong places. >=20 > Can someone help me out here? >=20 > The first error stops compileing world/kernel, but taking a second run, t= he error goes away. >=20 > Kind regards and thanks in advance, >=20 > oh >=20 >=20 >=20 > [...] > --- all_subdir_stand/efi --- > SOURCE_DATE_EPOCH=3D1451606400 objcopy -j .peheader -j .text -j .sdata -= j .data -j .dynamic -j > .dynsym -j .rel.dyn -j .rela.dyn -j .reloc -j .eh_frame -j set_Xcommand_= set -j > set_Xficl_compile_set --output-target=3Defi-app-x86_64 loader_4th.sym lo= ader_4th.efi --- > all_subdir_stand/i386 ---=20 >=20 > -8112 bytes available 7.71 real 12.86 user 3.08 sys >=20 > make[1]: stopped in /usr/src > [...] I often face a similiar error, not sure if it is BEARSSL related since I bu= ild it since a few month per default, but it often helps just to restart the bu= ild. --Gordon --8iIMxk1Pka9FlU7l Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEYbWI0KY5X7yH/Fy4OQX2V8rP09wFAmR0rr1fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYx QjU4OEQwQTYzOTVGQkM4N0ZDNUNCODM5MDVGNjU3Q0FDRkQzREMACgkQOQX2V8rP 09xRqggA1Inem3janyIl/tEqKo1KJrLtjRQJcwbjgS+5Fa2LC2vCIL+cNCYwRdVM PQ8NW9n8gIpzc6mgqfOIGQjW9s3Lrc4oTiJKPNYy7YsI3efiAc1x6hF1qLubXoWj pG0+S/QMyK2wyw0XREm3p5SOL7COMb61VWVCLNceJ01fkyE0VCGkeaQ7Qax4jU+y /TS2sg+4v3PiZkCXBhdRVvHH3YVIVv58QIjUvHtkvTDXfdHOgzKm0SgqvmapW9qr SSgcpx2t1jfzXjPRMTXZFjWyZ6nVc5ZRckjpGdwIHdA+El/gvmCTYp3JpiLainHS BkpT6xPL2KAjwpjdxPncw98wXvMzYQ== =ZJH4 -----END PGP SIGNATURE----- --8iIMxk1Pka9FlU7l-- From nobody Mon May 29 19:05:42 2023 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 4QVQ3P3v5Nz4Wl79 for ; Mon, 29 May 2023 19:05:53 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (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 4QVQ3N4QYQz4DDg for ; Mon, 29 May 2023 19:05:52 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=madpilot.net header.s=bjowvop61wgh header.b="B xN+Gci"; spf=pass (mx1.freebsd.org: domain of mad@madpilot.net designates 159.69.1.99 as permitted sender) smtp.mailfrom=mad@madpilot.net; dmarc=pass (policy=quarantine) header.from=madpilot.net Received: from mail (mail [IPv6:fd5c:5351:d272::3]) by mail.madpilot.net (Postfix) with ESMTP id 4QVQ3D5hSWz6jlk; Mon, 29 May 2023 21:05:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :references:from:from:content-language:subject:subject:date:date :message-id:received; s=bjowvop61wgh; t=1685387143; x= 1687201544; bh=4KDUeSyq3ltSEZRqKETd5Y2t02jG3w0wg5PyFA3yUyc=; b=B xN+GcivLulb4yho/8JYxnzZmGukwTPxA5+8X6/nEY6tVXy2YhOuw+b6+dKF9uh5y fuN9Njx5lEkoQtsbqf1o3JWTQ3WJRbmu1lkZKA69S2MNeZTejI+hOv6JjGMxlchR iFv7vxewGH7V8gUO5e6bt2jtnBav0IkO0sLjxMLS1oIwKCETvoDKLzuGfCwFPb9t 8joDLqYoJ+oFwJRsTpMYskwhX4qAoctZf4Pdze6YflhsS/wfXg3EjwqV1dcKP4JA TTx7YnmYxaPhkQdwGbUKvo26z1kTYDcQChc5hu9YyVwYovWMQwmVJHgfQIEltMyZ y2ohaQ0WH5jBqqq/Zlecg== Received: from mail.madpilot.net ([IPv6:fd5c:5351:d272::3]) by mail (mail.madpilot.net [IPv6:fd5c:5351:d272::3]) (amavisd-new, port 10026) with ESMTP id AEeolcVPjgct; Mon, 29 May 2023 21:05:43 +0200 (CEST) Message-ID: <7f4e8f75-5a23-d82a-f777-ea2cbbf95cae@madpilot.net> Date: Mon, 29 May 2023 21:05:42 +0200 Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head Content-Language: en-US From: Guido Falsi To: Warner Losh Cc: Alastair Hogge , FreeBSD Current References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> <1635751e73bb8c4c600de231c8d43018@riseup.net> <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> <0d4e3bda-4ef3-2b22-0a95-319f7f9baf23@madpilot.net> In-Reply-To: <0d4e3bda-4ef3-2b22-0a95-319f7f9baf23@madpilot.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-1.99 / 15.00]; MISSING_MIME_VERSION(2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.993]; DMARC_POLICY_ALLOW(-0.50)[madpilot.net,quarantine]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[madpilot.net:s=bjowvop61wgh]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[madpilot.net:+]; RCPT_COUNT_THREE(0.00)[3]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE]; RCVD_COUNT_THREE(0.00)[3]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4QVQ3N4QYQz4DDg X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N 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 On 28/05/23 20:45, Guido Falsi wrote: >> It may well be something broke... but I'm just wanting to be double >> sure it's against a consistent package set. If something broke, then I >> can't help. > > I see, I did not understand what you meant at first. > > What I posted was the result of a simple "pkg upgrade", which is what I > usually do to update the machine, and usually works quite fine. > > I have not tested forcing all packages reinstallation ("pkg upgrade -f" > if I get it correctly). > > That is something I was already planning to do. Will report back > tomorrow for that. > Well forcing reinstallation of all ports (with rebuilt kmod ports) made the issue disappear. SO it looks like it was really nothing. Sorry for the noise and thanks for the suggestions! -- Guido Falsi From nobody Mon May 29 22:18:50 2023 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 4QVVLF5f0yz4XGYC for ; Mon, 29 May 2023 22:19:01 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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 4QVVLD1ywXz3NYj for ; Mon, 29 May 2023 22:18:59 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp; dmarc=none Received: from kalamity.joker.local (123-1-88-210.area1b.commufa.jp [123.1.88.210]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 34TMIpZS082178 for ; Tue, 30 May 2023 07:18:51 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Tue, 30 May 2023 07:18:50 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head Message-Id: <20230530071850.c4af5a8607f23712ef73d2f4@dec.sakura.ne.jp> In-Reply-To: <7f4e8f75-5a23-d82a-f777-ea2cbbf95cae@madpilot.net> References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> <1635751e73bb8c4c600de231c8d43018@riseup.net> <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> <0d4e3bda-4ef3-2b22-0a95-319f7f9baf23@madpilot.net> <7f4e8f75-5a23-d82a-f777-ea2cbbf95cae@madpilot.net> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.2) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-1.43 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; NEURAL_HAM_LONG(-0.83)[-0.833]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; R_SPF_NA(0.00)[no SPF record]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_LAST(0.00)[]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; DMARC_NA(0.00)[sakura.ne.jp]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4QVVLD1ywXz3NYj X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N On Mon, 29 May 2023 21:05:42 +0200 Guido Falsi wrote: > On 28/05/23 20:45, Guido Falsi wrote: > > >> It may well be something broke... but I'm just wanting to be double > >> sure it's against a consistent package set. If something broke, then I > >> can't help. > > > > I see, I did not understand what you meant at first. > > > > What I posted was the result of a simple "pkg upgrade", which is what I > > usually do to update the machine, and usually works quite fine. > > > > I have not tested forcing all packages reinstallation ("pkg upgrade -f" > > if I get it correctly). > > > > That is something I was already planning to do. Will report back > > tomorrow for that. > > > > Well forcing reinstallation of all ports (with rebuilt kmod ports) made > the issue disappear. > > SO it looks like it was really nothing. Sorry for the noise and thanks > for the suggestions! > > -- > Guido Falsi IIRC, drm*-kmod port didn't seem to be updated in the first place. OTOH, generic kernel seems to be updated via pkgbase. This could cause problems with incompatibilities. And fixed with forcibly updating all pkgs. poudliere built new pkg, but pkg doesn't thought it's updated , maybe. -- Tomoaki AOKI From nobody Mon May 29 22:26:26 2023 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 4QVVVy422yz4XH97 for ; Mon, 29 May 2023 22:26:34 +0000 (UTC) (envelope-from tezeka@hotmail.com) Received: from BRA01-ROA-obe.outbound.protection.outlook.com (mail-roabra01olkn2079.outbound.protection.outlook.com [40.92.96.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "DigiCert Cloud Services CA-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QVVVx6QlTz3PmK for ; Mon, 29 May 2023 22:26:33 +0000 (UTC) (envelope-from tezeka@hotmail.com) Authentication-Results: mx1.freebsd.org; none ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bPqEv4bVoRejKRS8Rp52pW/TT0qNfX1pnpgQrFBm3/C1DWr7Ywbv0da5fiN1e5xjzTh1XBHDi6OrRBGfg9vqCO4uKlIzTFGsy6NINsuGTjiXAFrv20CO1vUW1sEcJhyHR11h8OXCAXJSQfqRRatcmpv6byanV5luQDIHAxHOUUTdNmO5Pc4//a2P6mxAMivp/taiaP6dMTEmXk1yiaccTSA9EPdCvOumebJSNPQyeg8RJWW3CQIVYfO8BQ/p+xNooz/Yo5KQBKPwZtyueqP3munEIy1wsdd5XZuL3b7cgdDngb9UwYf8hl7NraPTbWlmpajYxMYetSMkbtzW7I0bxg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=QyrRXRr3yjVqpZYj3FqGjK3GKmJsPW7upxrQJCgJ1TM=; b=d2tEOQCLvXmywsSqyOcu8BenIqmlRyLQ12U1qkL+BhFzkitArL1/IuRhBsvQs4eLrgL1cmr/y8MbTorL8e2pa1Ro5lAOw2Gija/rhzyj95pBynOg3WxFrjipAeXzqH/3C7ubtYibVA8oTzXab/kuMfe+kAPVUW8XQIbvqDiNvGa20HDnWll+Gj/SVFtHbMrK/SeHRJW+/SkENLfgr+KqePEbYIqlDVUZJH00ZvZP2wTgSJPQMzCPx6KpnZV08nfgd0FeOEAnhceZLsFb6pwpwicPayIuUFT8jFp5TfLX8AAo6Cni8ljeCg/a+E5xt6EkMoOk/4QzKTw4cLFfiKEWnA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=QyrRXRr3yjVqpZYj3FqGjK3GKmJsPW7upxrQJCgJ1TM=; b=AjOK/jTBPaVRVX2617SoUJSaRsBhKEU0TEe7RCotGO1EjxrNeio1QUatxsV7FKQgVVAb0FUY+a16ignPR2+MAoc1f5nCg1DfX3eiRtlrJ0kn7EA85U3DjSCwES0DeFRQzd9WT3ilCl9knFc4VH38IKe9rGZk4BG1TLd9Uzvf3088P0cLCiePHFgJsXakZneQssgBbUF2170B4wLLrSQromwlfnbB7ExxFZ2fvc1uOz/CiA1zfNokDS8lBIStonyBLxnjTkw3lThKofyJ47ebxFcaxii3e/jAUd1dQS64uxTkZSVzDw8iit3ukrdgmjMmk6UtpBf/oIUdYcrxPpfrpA== Received: from CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM (2603:10d6:103:118::12) by ROAP284MB1673.BRAP284.PROD.OUTLOOK.COM (2603:10d6:10:90::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6433.23; Mon, 29 May 2023 22:26:29 +0000 Received: from CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM ([fe80::5b39:489b:b684:1605]) by CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM ([fe80::5b39:489b:b684:1605%7]) with mapi id 15.20.6433.022; Mon, 29 May 2023 22:26:29 +0000 Date: Mon, 29 May 2023 19:26:26 -0300 (-03) From: Ivan Quitschal To: Tomoaki AOKI cc: freebsd-current@freebsd.org Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head In-Reply-To: <20230530071850.c4af5a8607f23712ef73d2f4@dec.sakura.ne.jp> Message-ID: References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> <1635751e73bb8c4c600de231c8d43018@riseup.net> <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> <0d4e3bda-4ef3-2b22-0a95-319f7f9baf23@madpilot.net> <7f4e8f75-5a23-d82a-f777-ea2cbbf95cae@madpilot.net> <20230530071850.c4af5a8607f23712ef73d2f4@dec.sakura.ne.jp> Content-Type: text/plain; charset=US-ASCII; format=flowed X-TMN: [x/qhI9/B5RiwqUQ6w1RlKzbxkGTBuHli] X-ClientProxiedBy: CP5P284CA0094.BRAP284.PROD.OUTLOOK.COM (2603:10d6:103:92::15) To CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM (2603:10d6:103:118::12) X-Microsoft-Original-Message-ID: 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 X-MS-Exchange-MessageSentRepresentingType: 1 X-MS-PublicTrafficType: Email X-MS-TrafficTypeDiagnostic: CP6P284MB1900:EE_|ROAP284MB1673:EE_ X-MS-Office365-Filtering-Correlation-Id: d04ae57d-6c8c-4da0-6088-08db6093bf8d X-Microsoft-Antispam: BCL:0; X-Microsoft-Antispam-Message-Info: X/m+r1aEbdHpgpUdMOfyxF6lg54UDHZ4Rx/hPF2hFtAtRVoYSvK8wd1EQUEUiy4cY1UIPyjMvxiiWTxw/UgiUUmSy73HNJcA6Ul9kQooBVMd+iRNHwkIslgfB7SA04YDZ1eNUboKH0bKFuXviKQwKW0fUcIAmF8M6dQaLZp7L1A8/0Qazo+x/6+HdbewIDF2rcSKItzaAzbqR58SiN2zPr5TQAc45luckCHETFYTAsKXL/Kn/iY9sNzzgBLJAryT3Qz8XOKMwp/YDIyuZ8cGS6N57R1qBUgFet5XMS8CZzY+scTVLp9HRQl4BqaQXY+bP3dv2X4jfvPeIlk1s5S5UwL9bHZbkZG3zVUTNsgsyuLbF5Nn0z3HAaHyYYe6JlHul48fCBQmmtfmBNbyCq3iZkrQkazbjJTHAT8gAPIO8lQ42bE6yOBheMepk66TMrsIuIBpaND2ubuE/1UW9T9zOgXreBn+Z7/jhwb3ZZrACPDVUtkCiY0+1RIdgRqFQVTeBE8yxI0o8kAXErJ7s1dpMWvXuqRT6C/ZPnPM2v+30MUlkIoH17g31/VKz1fBPHvuJTS44Z1zXz9aRz7MtoHVmsf5kyJtRNMKQR0QY2qKuGw= X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1 X-MS-Exchange-AntiSpam-MessageData-0: =?us-ascii?Q?SxlKYiaZUNc7VvszEuOzz2OY+rxhnsF6pP/Ra7Nx/+6GSO5JguNylMFwhhmY?= =?us-ascii?Q?kfVOmnYfDSGPDOgbKzz98rAjO4X5Wn9Nf26gUIQBZdCBUe/5gIs3P+7Bpln/?= =?us-ascii?Q?aqTGCaCEM0NPFXwVmJQlYRn1lolTwDtFyAyy4SHQPwptDOSXJD5GQgCrYfiP?= =?us-ascii?Q?e6kHKYuCMWNSZjbUqmgIH4J+ZmrVeW5KsYLOMG1wDw+sjrM8KqSpCjGmjd2d?= =?us-ascii?Q?MeODsfu/0nvhPgGVI/4We7WZWCWA+K//YD4BqmQF/QznWmuTXpqC81Vnke4a?= =?us-ascii?Q?hGII7qMsTX6LdbMEWoNgg/WVLtoipob7JhGCgj/tB336rLuce6onSmAt0RmG?= =?us-ascii?Q?sfxkyRUyk6sbb4dWG8/WYx7yPT9o26NDHu6WuoqKpN10NQF3Y2dYUvT0CsM5?= =?us-ascii?Q?W9vwV3LZbL1fbuqDkWJ47HjB08+1n/7WVqOx4h0FwL9Enr88HmGtH1ZPEwpO?= =?us-ascii?Q?ArY3E0cUjejFP/4k9gp/ATDO9hsFi9K70T4065ImvXTxrTvGx+XNncHKghFr?= =?us-ascii?Q?JV+vQYuWvR0GLdFfc+kuycGTyXCVlYAZU0txHZzMK4ZuXpFxtUZdatGATRna?= =?us-ascii?Q?N2aE8hJcbHrbyPEZ8xXuZDaFzVUlj9AgB6xVZm6X3DZsNSfWPC5Z7VIoBXN8?= =?us-ascii?Q?djiL0Nqy5liJB2aXLP8c6PLw3ZIMCfOR5aKUvWSwU5pOv+xqE82+4sUM8wYG?= =?us-ascii?Q?EXYqRecTsz10anobdP7oCIDzpPuu5UaYz5FJtJ+L7zd+h8uAV4mnCUzXBzuj?= =?us-ascii?Q?avEsD866XJ3cWdXwJkmdIG77WR8s0QEI6tTpvnfMoPsHANMqY9G4zVVsRzv2?= =?us-ascii?Q?L0154t6tZK2DCGe2CDhCUR+ecGszD9UTW/HWzEfN8VI3ixc4heJJz1MJa7eI?= =?us-ascii?Q?eNk8xceyWPwTzH+3zP6SX4vy0/jz7b83IrIBFIPi2fTuHJ1QQrYfYsw+EXHG?= =?us-ascii?Q?ZGxGoXKdg67/j3Y4KHF2FOlolUGXkG6lOigTEiI5QBFiUuzeGf7jLOmgp/iN?= =?us-ascii?Q?2cO0gKpcHURgqBnEiYEt1ehxvTmmIzrcUr4UNXGREi3g720IC9Fph0sNw+Vz?= =?us-ascii?Q?rN/VrFQuhEUR/+GeYvLxkRosF/WdrDfqhzW3/V4EoA5nQdDMy2AhEkSSCpxk?= =?us-ascii?Q?BoBiRz4oMOIaZttq04GZpTGq6vJNJzORQYwlJK4h0FlQ96sJoT5z8G7zrRXD?= =?us-ascii?Q?uPHx5jL+30SjSMD//IyHzPOdkoc8SkCorsrQNQ=3D=3D?= X-OriginatorOrg: sct-15-20-4755-11-msonline-outlook-7dc52.templateTenant X-MS-Exchange-CrossTenant-Network-Message-Id: d04ae57d-6c8c-4da0-6088-08db6093bf8d X-MS-Exchange-CrossTenant-AuthSource: CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-OriginalArrivalTime: 29 May 2023 22:26:29.8307 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-CrossTenant-Id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-Transport-CrossTenantHeadersStamped: ROAP284MB1673 X-Rspamd-Queue-Id: 4QVVVx6QlTz3PmK X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:8075, ipnet:40.80.0.0/12, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Mon, 29 May 2023, Tomoaki AOKI wrote: > On Mon, 29 May 2023 21:05:42 +0200 > Guido Falsi wrote: > >> On 28/05/23 20:45, Guido Falsi wrote: >> >>>> It may well be something broke... but I'm just wanting to be double >>>> sure it's against a consistent package set. If something broke, then I >>>> can't help. >>> >>> I see, I did not understand what you meant at first. >>> >>> What I posted was the result of a simple "pkg upgrade", which is what I >>> usually do to update the machine, and usually works quite fine. >>> >>> I have not tested forcing all packages reinstallation ("pkg upgrade -f" >>> if I get it correctly). >>> >>> That is something I was already planning to do. Will report back >>> tomorrow for that. >>> >> >> Well forcing reinstallation of all ports (with rebuilt kmod ports) made >> the issue disappear. >> >> SO it looks like it was really nothing. Sorry for the noise and thanks >> for the suggestions! >> >> -- >> Guido Falsi > > IIRC, drm*-kmod port didn't seem to be updated in the first place. > OTOH, generic kernel seems to be updated via pkgbase. > > This could cause problems with incompatibilities. > And fixed with forcibly updating all pkgs. > poudliere built new pkg, but pkg doesn't thought it's updated , maybe. > > > -- > Tomoaki AOKI > > try using this drm-kmod here, instead of the ones within ports git clone https://github.com/freebsd/drm-kmod thats the only one that works for me --tzk From nobody Tue May 30 06:33:34 2023 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 4QVjKX5DMMz4XxG8 for ; Tue, 30 May 2023 06:34:08 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (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 4QVjKX2y2Bz3GXF for ; Tue, 30 May 2023 06:34:08 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; none Received: from mail (mail [IPv6:fd5c:5351:d272::3]) by mail.madpilot.net (Postfix) with ESMTP id 4QVjJt20lNz6wDN; Tue, 30 May 2023 08:33:34 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :from:from:content-language:references:subject:subject:date:date :message-id:received; s=bjowvop61wgh; t=1685428412; x= 1687242813; bh=2xf58cf8Qs6AsHsqBb1+T5GRVfRMzLfeA8gLCKcJkgY=; b=l 42UZy6BvD8HGXc8QHnXQGoQUCtsjNzR6Ym28XRQE7s69eOGmyfbAt0qsQVuRHzUw dgjGSVVvyx+hKEaTtFmx0yRakHE1qlBLyYQ9BSF9sHrypOKP+dF40cmLrWTCVbCv rjzPdSI2K2IQs1fA1q6/WCtOUPUY35ZYfJkycavgYD5ppODRd/cYAHP1m3qBvyJ6 U5dQb7bH618bcnvFlBID2XsFgHa10JW98LnHdnmijdKtvt+SDmi/MWo3//LwNhqD 0/R6SRfKAg82AdU37/dsM3jtsjRJqJYAMRAI/CbEOt2jhMO4RuOZBWqkAGR4dSi3 zHckzKcvrcZpv3i9pb22w== Received: from mail.madpilot.net ([IPv6:fd5c:5351:d272::3]) by mail (mail.madpilot.net [IPv6:fd5c:5351:d272::3]) (amavisd-new, port 10026) with ESMTP id t2nOCw5rx9JR; Tue, 30 May 2023 08:33:32 +0200 (CEST) Message-ID: <5b6ab3a8-de1b-aca2-12fe-2470532e8bfd@madpilot.net> Date: Tue, 30 May 2023 08:33:34 +0200 Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head To: Tomoaki AOKI , freebsd-current@freebsd.org References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> <1635751e73bb8c4c600de231c8d43018@riseup.net> <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> <0d4e3bda-4ef3-2b22-0a95-319f7f9baf23@madpilot.net> <7f4e8f75-5a23-d82a-f777-ea2cbbf95cae@madpilot.net> <20230530071850.c4af5a8607f23712ef73d2f4@dec.sakura.ne.jp> Content-Language: en-US From: Guido Falsi In-Reply-To: <20230530071850.c4af5a8607f23712ef73d2f4@dec.sakura.ne.jp> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4QVjKX2y2Bz3GXF X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N 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 On 30/05/23 00:18, Tomoaki AOKI wrote: > On Mon, 29 May 2023 21:05:42 +0200 > Guido Falsi wrote: > >> On 28/05/23 20:45, Guido Falsi wrote: >> >>>> It may well be something broke... but I'm just wanting to be double >>>> sure it's against a consistent package set. If something broke, then I >>>> can't help. >>> >>> I see, I did not understand what you meant at first. >>> >>> What I posted was the result of a simple "pkg upgrade", which is what I >>> usually do to update the machine, and usually works quite fine. >>> >>> I have not tested forcing all packages reinstallation ("pkg upgrade -f" >>> if I get it correctly). >>> >>> That is something I was already planning to do. Will report back >>> tomorrow for that. >>> >> >> Well forcing reinstallation of all ports (with rebuilt kmod ports) made >> the issue disappear. >> >> SO it looks like it was really nothing. Sorry for the noise and thanks >> for the suggestions! >> >> -- >> Guido Falsi > > IIRC, drm*-kmod port didn't seem to be updated in the first place. > OTOH, generic kernel seems to be updated via pkgbase. > > This could cause problems with incompatibilities. > And fixed with forcibly updating all pkgs. > poudliere built new pkg, but pkg doesn't thought it's updated , maybe. Poudriere did not rebuild the kmod ports since there was no __FreeBSD_version change. I usually force it being rebuild by hand, but this time I forgot! I did force pkg reinstall for it by hand, but this just reinstalled the same previous package. In the end I forced rebuilding it and reinstalling everything and the issue disappeared. -- Guido Falsi From nobody Tue May 30 06:34:47 2023 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 4QVjLt0yn2z4Xwmg for ; Tue, 30 May 2023 06:35:18 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (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 4QVjLt08tVz3HqR for ; Tue, 30 May 2023 06:35:18 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; none Received: from mail (mail [IPv6:fd5c:5351:d272::3]) by mail.madpilot.net (Postfix) with ESMTP id 4QVjLH1G89z6wDN; Tue, 30 May 2023 08:34:47 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :from:from:references:content-language:subject:subject:date:date :message-id:received; s=bjowvop61wgh; t=1685428485; x= 1687242886; bh=pmNmpJNreUeENdtnhuCQRSxxNdk5hklpHya6IFhSkMQ=; b=b R6B3uHZPWk7L4HMEa8YKSgaicQECTEZj1vs2ryK/rN/NgS8xgp7d4xWNljalsMgr tFUgIqCvGwUQX8+SD4fLXzORwNDlObwDIC+tQ7BbdErnLHeUsZhi2WFfEoL+fGbl s2hCD+nZYA2dMjEgylj6xWy9J4ej4PT0z/ixq76+6xeGfrfaReph4w32Jrj3ntFq /wgSo6lxg3EZQQKcyTKcNBjUIzqh+/ZhrZEkI+K3fsx5ce2Ta/3lwTHjSxKQLVZ7 I6v2NNwgebWhd+l3UpOSaJS0QoyIC204S2iE2VSu0pnqD3jTzAMHQJwnhSPRYycz /A0wS0xFCOOUkrdQsJQIA== Received: from mail.madpilot.net ([IPv6:fd5c:5351:d272::3]) by mail (mail.madpilot.net [IPv6:fd5c:5351:d272::3]) (amavisd-new, port 10026) with ESMTP id jDF8dM3LDGUn; Tue, 30 May 2023 08:34:45 +0200 (CEST) Message-ID: <6b524926-d736-f17e-701a-c2e982cb960c@madpilot.net> Date: Tue, 30 May 2023 08:34:47 +0200 Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head Content-Language: en-US To: Ivan Quitschal , Tomoaki AOKI Cc: freebsd-current@freebsd.org References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> <1635751e73bb8c4c600de231c8d43018@riseup.net> <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> <0d4e3bda-4ef3-2b22-0a95-319f7f9baf23@madpilot.net> <7f4e8f75-5a23-d82a-f777-ea2cbbf95cae@madpilot.net> <20230530071850.c4af5a8607f23712ef73d2f4@dec.sakura.ne.jp> From: Guido Falsi In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4QVjLt08tVz3HqR X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N 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 On 30/05/23 00:26, Ivan Quitschal wrote: > > > On Mon, 29 May 2023, Tomoaki AOKI wrote: > >> On Mon, 29 May 2023 21:05:42 +0200 >> Guido Falsi wrote: >> >>> On 28/05/23 20:45, Guido Falsi wrote: >>> >>>>> It may well be something broke... but I'm just wanting to be double >>>>> sure it's against a consistent package set. If something broke, then I >>>>> can't help. >>>> >>>> I see, I did not understand what you meant at first. >>>> >>>> What I posted was the result of a simple "pkg upgrade", which is what I >>>> usually do to update the machine, and usually works quite fine. >>>> >>>> I have not tested forcing all packages reinstallation ("pkg upgrade -f" >>>> if I get it correctly). >>>> >>>> That is something I was already planning to do. Will report back >>>> tomorrow for that. >>>> >>> >>> Well forcing reinstallation of all ports (with rebuilt kmod ports) made >>> the issue disappear. >>> >>> SO it looks like it was really nothing. Sorry for the noise and thanks >>> for the suggestions! >>> >>> -- >>> Guido Falsi >> >> IIRC, drm*-kmod port didn't seem to be updated in the first place. >> OTOH, generic kernel seems to be updated via pkgbase. >> >> This could cause problems with incompatibilities. >> And fixed with forcibly updating all pkgs. >> poudliere built new pkg, but pkg doesn't thought it's updated , maybe. >> >> >> -- >> Tomoaki AOKI    >> >> > > > try using this drm-kmod here, instead of the ones within ports > > git clone https://github.com/freebsd/drm-kmod > > thats the only one that works for me I'm having good results with: > pkg info -o '*kmod*' drm-515-kmod-5.15.25_3 graphics/drm-515-kmod gpu-firmware-amd-kmod-picasso-20230210 graphics/gpu-firmware-amd-kmod gpu-firmware-amd-kmod-raven-20230210 graphics/gpu-firmware-amd-kmod from the official tree. -- Guido Falsi From nobody Tue May 30 06:41:33 2023 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 4QVjVQ5dFlz4Xxqf for ; Tue, 30 May 2023 06:41:50 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (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 ECDSA (P-256) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QVjVP0snDz3KM3 for ; Tue, 30 May 2023 06:41:49 +0000 (UTC) (envelope-from Alexander@leidinger.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=leidinger.net header.s=outgoing-alex header.b=Ib+Q+qNz; spf=pass (mx1.freebsd.org: domain of Alexander@leidinger.net designates 89.238.82.207 as permitted sender) smtp.mailfrom=Alexander@leidinger.net; dmarc=pass (policy=quarantine) header.from=leidinger.net Date: Tue, 30 May 2023 08:41:33 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1685428897; 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=yme+OjdCPn8TEFTKhrI/8eDY4f0ql5cD8zhntTJMwoc=; b=Ib+Q+qNzdZ5Tsy+98f/WSpXySBltKMeO3lMBHpkasamD88+fPdYGQ+R7MYWdGMYFrYcXK+ 0COUzs0IJsIX1TqtwKeZwi3Xr02FZ8anxFO45Ej6n7zNZax7FgEu9nb4mhlwj7EU5akiur TA0ifiOK3czQPfhqqEub94I3LiigNS8kmldp68Sa7PjjAlxaIXyZxuXKoLVUVpnvTj1kAx 8io6SnclI534RibwUUCdFpPmY9cuVEFEPRc+y/u2OV3+xfY4W9xQJzsv6KZH0JvbWNGR/x dpLEOW+WcljYFVpGIsWaWJUV3CcUHj+Xc+vWMtQmt57qOsftLpxUm96VHQ60RA== Message-ID: <20230530084133.Horde.4VevT2KY4XCtqoJgvP08jyB@webmail.leidinger.net> From: Alexander Leidinger To: bob prohaska Cc: Yuri , freebsd-current@freebsd.org Subject: Re: Surprise null root password References: <945C9B6D-F2A8-4F0D-BDB0-49A3DE870168@karels.net> <61e30711-f0da-2f42-3a6f-9bd91fc6b1ce@aetern.org> In-Reply-To: Accept-Language: de,en Content-Type: multipart/signed; boundary="=_Rpe4aGUFSs02wNReq4vofJ3"; protocol="application/pgp-signature"; micalg=pgp-sha256 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 X-Spamd-Result: default: False [-6.08 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.980]; DMARC_POLICY_ALLOW(-0.50)[leidinger.net,quarantine]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[leidinger.net:s=outgoing-alex]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[leidinger.net:+]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE] X-Rspamd-Queue-Id: 4QVjVP0snDz3KM3 X-Spamd-Bar: ------ X-ThisMailContainsUnwantedMimeParts: N This message is in MIME format and has been PGP signed. --=_Rpe4aGUFSs02wNReq4vofJ3 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting bob prohaska (from Fri, 26 May 2023=20=20 16:26:06=20-0700): > On Fri, May 26, 2023 at 10:55:49PM +0200, Yuri wrote: >> >> The question is how you update the configuration files, >> mergemaster/etcupdate/something else? >> > > Via etcupdate after installworld. In the event the system > requests manual intervention I accept "theirs all". It seems > odd if that can null a root password. > > Still, it does seem an outside possibility. I could see it adding > system users, but messing with root's existing password seems a > bit unexpected. As you are posting to -current@, I expect you to report this issue=20=20 about=2014-current systems. As such: there was a "recent" change=20=20 (2021-10-20)=20to the root entry to change the shell. =20=20=20=20=20=20 https://cgit.freebsd.org/src/commit/etc/master.passwd?id=3Dd410b585b6f00a26= c2de7724d6576a3ea7d548b7 By blindly accepting all changes, this has reset the PW to the default=20= =20 setting=20(empty). I suggest to review changes ("df" instead of "tf" in etcupdate) to at=20=20 least=20those files which you know you have modified, including the=20=20 password/group=20stuff. After that you can decide if the diff which is=20= =20 shown=20with "df" can be applied ("tf"), or if you want to keep the old=20= =20 version=20("mf"), or if you want to modify the current file ("e", with=20= =20 both=20versions present in the file so that you can copy/paste between=20= =20 the=20different versions and keep what you need). Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_Rpe4aGUFSs02wNReq4vofJ3 Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIzBAABCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmR1mp0ACgkQEg2wmwP4 2IZq4hAArHrDx25Ilk+njKh+EGkfPwUKDuDjtlcqFuzp9K2VsTACoU4d9M9a6AB/ I9wJRvgynJj6PRZpq29uEm1ScWbVwScTbaH5cpVt4WvbLbywDrJdmi42xH5mv7Ud bJSEYWkpVJg735RBk6ZIRB+85lKY3cUg+B20gh6AYX3tdwPDA7QYR/GCcWMnQOGM k3NTmlI4rVKaUw2zTv+f/ErQZA1Izwb9f1mYsfXzo3jsDY0fFa62Ym+0srzC+L/c wQK3K1JRlAvbaWb7aQlT5WeMRHRUKp3fHsA1KJJqLKa6GAkl78tnTOfrENT1B8wh Ka4RrJCJV5dYazQRTuS6uW9sOoyjPOAIVEM5G6Jqw6B0j6O2HhNGQcrNg+UPuIcm Q8OOYOjqdeK/I5eqXWLzGB2v1PoKNQf+kB4Se1OSpZxesgpYzQSa5XGsM2yUD0ce HkJKAFvjY9oCzAvd1Mw7M3SXAFkOXCC1qK661km1RPY2rOf79TYLZ7cQFmQgSGP5 FTgqLvKcJRtWAl7ihcSFW3Zo1mUZz9AzaoKFlxFQK3rukXaTaKWYa9TfEXmFW4Aw Km8NqXrZ7pRn49Cp5Um/JrEsq4E+WEnYLTMPBKW5/O2w0+YHWCz6HDriGeZdlD7L vaeGkiHkXacmrdKlCf0p60V6eBJUX/DnwJV6jAJpMyaGAPm2KGo= =dsyk -----END PGP SIGNATURE----- --=_Rpe4aGUFSs02wNReq4vofJ3-- From nobody Tue May 30 12:19:14 2023 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 4QVs0H4Kq1z4XNl1 for ; Tue, 30 May 2023 12:19:43 +0000 (UTC) (envelope-from sl-pub-lists@honeyguide.de) Received: from mlx.honeyguide.net (mlx.honeyguide.net [197.155.21.76]) (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 4QVs0G0jMwz48j0 for ; Tue, 30 May 2023 12:19:42 +0000 (UTC) (envelope-from sl-pub-lists@honeyguide.de) Authentication-Results: mx1.freebsd.org; dkim=fail ("headers rsa verify failed") header.d=honeyguide.de header.s=default header.b=t2QDO8rY; spf=pass (mx1.freebsd.org: domain of sl-pub-lists@honeyguide.de designates 197.155.21.76 as permitted sender) smtp.mailfrom=sl-pub-lists@honeyguide.de; dmarc=pass (policy=none) header.from=honeyguide.de Received: from pcf00001.honeyguide.net (aftr-62-216-207-162.dynamic.mnet-online.de [62.216.207.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mlx.honeyguide.net (Postfix) with ESMTPSA id E815512C1D; Tue, 30 May 2023 12:19:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=honeyguide.de; s=default; t=1685449171; bh=OhpiDE80pgwToHutw1z9nnSYZoga3Aa0bW+RzTK2f70=; h=From:To:Subject:References:CC:Date:In-Reply-To; b=t2QDO8rY31eplye3T3VvROaczzByWLSyUH8K7W8YdG5HWRiAl1phXTYIZPdER+OOG AX7QL5U0eAc8s46DcleekgRpMFtTqKhOXfTCpsqTFC2mAYQYVqOHiWDX+N90Er+zyw p2XZWZSuaCYWkrV6Jk927crbNohPfPJyWnlbIyn0= From: Stephan Lichtenauer To: Pete Wright Subject: Re: PinePhone Pro Boots On CURRENT Organization: Honeyguide GmbH References: CC: FreeBSD Current Date: Tue, 30 May 2023 14:19:14 +0200 In-Reply-To: (Pete Wright's message of "Sun, 28 May 2023 20:24:02 -0700") Message-ID: <86leh6ggfx.fsf@pcf00001.honeyguide.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (berkeley-unix) 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 Content-Type: text/plain; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-2.16 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.995]; R_MISSING_CHARSET(0.50)[]; DMARC_POLICY_ALLOW_WITH_FAILURES(-0.50)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_SPAM_LONG(0.13)[0.130]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; BLOCKLISTDE_FAIL(0.00)[62.216.207.162:server fail,197.155.21.76:server fail]; ASN(0.00)[asn:37199, ipnet:197.155.16.0/21, country:ZA]; MIME_TRACE(0.00)[0:+]; DMARC_POLICY_ALLOW(0.00)[honeyguide.de,none]; DKIM_TRACE(0.00)[honeyguide.de:-]; RCVD_COUNT_TWO(0.00)[2]; R_DKIM_REJECT(0.00)[honeyguide.de:s=default]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; HAS_WP_URI(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; HAS_ORG_HEADER(0.00)[]; TO_DN_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4QVs0G0jMwz48j0 X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N Hi Pete, Pete Wright writes: > i've had this pinephone pro for a few months now and finally got > around > to attempting to boot FreeBSD on it.. Here's the phone: > https://wiki.pine64.org/wiki/PinePhone_Pro > > I needed to get this serial console adapter which works > flawlessly with "cu" > (USB TTL Serial Adapter Converter Cable 3.3v/3v3 3.5mm Stereo > Jack Cable): > https://www.amazon.com/dp/B00XSPECIA?psc=1&ref=ppx_yo2ov_dt_b_product_details > > then i just downloaded the latest CURRENT snapshot and put it on > a > microsd card and it booted into multi-user mode.. here's the > dmesg: > https://www.nomadlogic.org/ppro-dmesg.txt > That is excellent news! I am so happy about that, thank you very much! > i am working on building a new image now to include the > pinephone pro > DTB file from Linux to see if that improves some of the hardware > detection.. certainly a long way to go before this could be > a useful > mobile device, but i'm very encouraged that i can actually boot > the thing. > > i suspect we'll need to use iwlwifi to get the AzureWave > AW-CM256SM wifi > and bluetooth card working... > > But, once i get the linux DTB for this guy into a disk image i'm > going > to see if i can get the display up next, but would love to hear > any > input or pointers from folks with more ARM porting experience > than me. I am probably telling you something you already know, but afaik the Pinephone Pro uses the Rockchip RK3399 which according to the datasheet (https://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf page 16, 1.2.9 Graphics Engine) contains a Mali GPU. That means Ruslan Bukin's Panfrost article in the FreeBSD Journal Jul/Aug 2021 at https://freebsdfoundation.org/wp-content/uploads/2021/08/The-Panfrost-Driver.pdf might be interesting regarding graphics. Looking forward to your updates! Best regards Stephan > > thanks! > -pete From nobody Tue May 30 13:02:38 2023 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 4QVsyX272Gz4XSmH for ; Tue, 30 May 2023 13:03:16 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QVsyX0VCpz4H5v for ; Tue, 30 May 2023 13:03:16 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb2d.google.com with SMTP id 3f1490d57ef6-bb131cd7c4aso71289276.1 for ; Tue, 30 May 2023 06:03:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685451795; x=1688043795; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=CyAFwX8wvMr1kcNU/8gSfdGaq22szMxqPXJdxm4HAAU=; b=ABtMg0qk1ymMLPPonQeMvAJ8KYW5nGeNIiZmbc4lo4nK1s0EFmPSuiN9RrO2CJtBNz UHrIJrs1/p/GrlxnNV8jV3xAhrisC1KENqP+jM00hlElblqUxl8umKJhEkP5UB8Hyo3u 9meEtjK+NbJ9NuT0Iur7cHwdFUKwn9+VEOYU1q4QRC2vmqe4ajkKym6mWTmdVKSko72m Mrl9PYoe6pHmqqKbESXS1+61yLKmaYIYFk/UFo/8jmJmLLcTM06ofKzuGF7u6oenAWny bLeAZWV8xXWPcXPuoD3g2Ce3WYWNiRqnV5Q5yrAVo63/CLG7oSz2v0HSx6/z6bOa9RDj MKjA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685451795; x=1688043795; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=CyAFwX8wvMr1kcNU/8gSfdGaq22szMxqPXJdxm4HAAU=; b=kZoR8zDiJYbdarxBqs8KzfdnqStZ78VMoXQt5Z0xA8/LBi6blGiwK8/JL9awyx37NH 5A9cDjWQO/vuxqZjkP1Z3ejgCIYtPDF6phFx3DJOJoX+V4jTkVGD5/POLoajo1xOrihL ES+Zh9BoNrR88y2TR2D7tK7LnkjErtABQOkq1N/FxCUYIxDVk02b0yvQt2D9+OYV2wz3 OMF51tXzm7SnF35Lp5PcSJ9NiW7aPDmjOOytZLP1kN2vc5l8GIO68wVL2N7sFeUBojPo R3EikYxrjvxczz5uhhi9iqpMJxMHXAx7CkBOhAs/oFxdwvuAHhNXwn/WxXxiPwevvxtj /oOw== X-Gm-Message-State: AC+VfDzKCGfpW7c3ojUNIRomCvV1QfiBQ3qS2aOrIhE0qMl1kREWSGfF LIrHQM7leLvMtu2/xcHFv3sZvQtAtj8VkMRqeXvBGYtprCSs0A== X-Google-Smtp-Source: ACHHUZ60IFQlUKOz7oOh/qlC3MiJse9TZTaTQ37NrrQu7lNFKhn4vW3QaMtYkoSUHnZ9ED8PkVcfmOpBZSOr4G2E9F4= X-Received: by 2002:a81:494f:0:b0:55d:3e67:2c6f with SMTP id w76-20020a81494f000000b0055d3e672c6fmr2288459ywa.22.1685451795123; Tue, 30 May 2023 06:03:15 -0700 (PDT) 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 References: <86leh6ggfx.fsf@pcf00001.honeyguide.net> In-Reply-To: <86leh6ggfx.fsf@pcf00001.honeyguide.net> From: Mario Marietto Date: Tue, 30 May 2023 15:02:38 +0200 Message-ID: Subject: Re: PinePhone Pro Boots On CURRENT To: Stephan Lichtenauer Cc: Pete Wright , FreeBSD Current Content-Type: multipart/alternative; boundary="00000000000088d30b05fce8d37f" X-Rspamd-Queue-Id: 4QVsyX0VCpz4H5v X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000088d30b05fce8d37f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable That's interesting. As I have already said,I haven't bought the pinephone pro,because it is expensive for me. So I'm working on a parallel project. I've bought this phone,instead : https://www.hdblog.it/schede-tecniche/samsung-galaxy-a6_i3655/ That's cheaper. Between the specs I read that it has a mali gpu,too : Mali-T830MP2 so,eventually,I can use the Lima and the PanFrost driver even for my samsung galaxy A6 ? I've started planning to install FreeBSD on top of the Android Kernel,using a specific patch,but now I'm thinking that maybe,I can install FreeBSD there natively. Can someone tell me if it is doable,giving a look at the specs of that phone model ? thanks. On Tue, May 30, 2023 at 2:19=E2=80=AFPM Stephan Lichtenauer < sl-pub-lists@honeyguide.de> wrote: > Hi Pete, > > Pete Wright writes: > > > i've had this pinephone pro for a few months now and finally got > > around > > to attempting to boot FreeBSD on it.. Here's the phone: > > https://wiki.pine64.org/wiki/PinePhone_Pro > > > > I needed to get this serial console adapter which works > > flawlessly with "cu" > > (USB TTL Serial Adapter Converter Cable 3.3v/3v3 3.5mm Stereo > > Jack Cable): > > > https://www.amazon.com/dp/B00XSPECIA?psc=3D1&ref=3Dppx_yo2ov_dt_b_product= _details > > > > then i just downloaded the latest CURRENT snapshot and put it on > > a > > microsd card and it booted into multi-user mode.. here's the > > dmesg: > > https://www.nomadlogic.org/ppro-dmesg.txt > > > > That is excellent news! I am so happy about that, thank you very > much! > > > i am working on building a new image now to include the > > pinephone pro > > DTB file from Linux to see if that improves some of the hardware > > detection.. certainly a long way to go before this could be > > a useful > > mobile device, but i'm very encouraged that i can actually boot > > the thing. > > > > i suspect we'll need to use iwlwifi to get the AzureWave > > AW-CM256SM wifi > > and bluetooth card working... > > > > But, once i get the linux DTB for this guy into a disk image i'm > > going > > to see if i can get the display up next, but would love to hear > > any > > input or pointers from folks with more ARM porting experience > > than me. > > I am probably telling you something you already know, but afaik > the Pinephone Pro uses the Rockchip RK3399 which according to the > datasheet > ( > https://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V= 2.1-20200323.pdf > page 16, 1.2.9 Graphics Engine) contains a Mali GPU. > > That means Ruslan Bukin's Panfrost article in the FreeBSD Journal > Jul/Aug 2021 at > > https://freebsdfoundation.org/wp-content/uploads/2021/08/The-Panfrost-Dri= ver.pdf > might be interesting regarding graphics. > > Looking forward to your updates! > > Best regards > > Stephan > > > > > thanks! > > -pete > > > > --=20 Mario. --00000000000088d30b05fce8d37f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
That's interesting. As I have already said,I have= n't bought the pinephone pro,because it is expensive for me. So I'm= working on a parallel project. I've bought this phone,instead :
<= div>

That's cheaper. Between the specs I= read that it has a mali gpu,too :=C2=A0 Mali-T830MP2

<= div>so,eventually,I can use the Lima and the PanFrost driver even for my sa= msung galaxy A6 ? I've started planning to install FreeBSD on top of th= e Android Kernel,using a specific patch,but now I'm thinking that maybe= ,I can install FreeBSD there natively. Can someone tell me if it is doable,= giving a look at the specs of that phone model ? thanks.

=

On Tue, May 30, 2023 at 2:19=E2=80=AFPM Stephan Lichtenauer <sl-pub-lists@honeyguide.de>= wrote:
Hi Pete,=

Pete Wright <pe= te@nomadlogic.org> writes:

> i've had this pinephone pro for a few months now and finally got <= br> > around
> to attempting to boot FreeBSD on it..=C2=A0 Here's the phone:
> https://wiki.pine64.org/wiki/PinePhone_Pro
>
> I needed to get this serial console adapter which works
> flawlessly with "cu"
> (USB TTL Serial Adapter Converter Cable 3.3v/3v3 3.5mm Stereo
> Jack Cable):
> https://ww= w.amazon.com/dp/B00XSPECIA?psc=3D1&ref=3Dppx_yo2ov_dt_b_product_details=
>
> then i just downloaded the latest CURRENT snapshot and put it on
> a
> microsd card and it booted into multi-user mode..=C2=A0 here's the=
> dmesg:
> https://www.nomadlogic.org/ppro-dmesg.txt
>

That is excellent news! I am so happy about that, thank you very
much!

> i am working on building a new image now to include the
> pinephone pro
> DTB file from Linux to see if that improves some of the hardware
> detection..=C2=A0 certainly a long way to go before this could be
> a useful
> mobile device, but i'm very encouraged that i can actually boot > the thing.
>
> i suspect we'll need to use iwlwifi to get the AzureWave
> AW-CM256SM wifi
> and bluetooth card working...
>
> But, once i get the linux DTB for this guy into a disk image i'm <= br> > going
> to see if i can get the display up next, but would love to hear
> any
> input or pointers from folks with more ARM porting experience
> than me.

I am probably telling you something you already know, but afaik
the Pinephone Pro uses the Rockchip RK3399 which according to the
datasheet
(https://op= ensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323= .pdf
page 16, 1.2.9 Graphics Engine) contains a Mali GPU.

That means Ruslan Bukin's Panfrost article in the FreeBSD Journal
Jul/Aug 2021 at
https://freebsdfound= ation.org/wp-content/uploads/2021/08/The-Panfrost-Driver.pdf
might be interesting regarding graphics.

Looking forward to your updates!

Best regards

Stephan

>
> thanks!
> -pete





--
Mario.
--00000000000088d30b05fce8d37f-- From nobody Tue May 30 14:38:46 2023 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 4QVw4y34JZz4Xbtc for ; Tue, 30 May 2023 14:38:58 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [66.165.241.226]) (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 (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QVw4x5LN9z4TX2 for ; Tue, 30 May 2023 14:38:57 +0000 (UTC) (envelope-from pete@nomadlogic.org) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomadlogic.org; s=04242021; t=1685457528; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=y+/BsSCjAm312rlNnYAHX7p1VdCZXx++Isd8iTpBN1Y=; b=RYJJTK3VRmYT+u9VHu90yGmprhrQzu8tfHxtntzxAYfQqIli8VQISj5EkmaFeaWA1XWRgM IbX25c9CTCU2YIdRzfOZrqWID/qKBllZ48Uy9XrTOio5bf2088+3XjrkHaA8uDTy8tlWN/ eJ2OlKu1ns8HGmCYa06BKk+u3jPag0k= Received: from [192.168.1.160] (cpe-24-24-168-214.socal.res.rr.com [24.24.168.214]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 0fbb1fd1 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 30 May 2023 14:38:47 +0000 (UTC) Message-ID: <6984826d-50b6-e311-baa5-581de8d5edf6@nomadlogic.org> Date: Tue, 30 May 2023 07:38:46 -0700 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 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: PinePhone Pro Boots On CURRENT Content-Language: en-US To: Stephan Lichtenauer Cc: FreeBSD Current References: <86leh6ggfx.fsf@pcf00001.honeyguide.net> From: Pete Wright In-Reply-To: <86leh6ggfx.fsf@pcf00001.honeyguide.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4QVw4x5LN9z4TX2 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:29802, ipnet:66.165.240.0/22, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 5/30/23 05:19, Stephan Lichtenauer wrote: > >> >> But, once i get the linux DTB for this guy into a disk image i'm >> going to see if i can get the display up next, but would love to hear >> any input or pointers from folks with more ARM porting experience >> than me. > > I am probably telling you something you already know, but afaik the > Pinephone Pro uses the Rockchip RK3399 which according to the > datasheet > (https://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf > page 16, 1.2.9 Graphics Engine) contains a Mali GPU. > > That means Ruslan Bukin's Panfrost article in the FreeBSD Journal > Jul/Aug 2021 at > https://freebsdfoundation.org/wp-content/uploads/2021/08/The-Panfrost-Driver.pdf > might be interesting regarding graphics. > > Looking forward to your updates! Oh sweet - I wasn't aware of that thanks for the pointer!  I'm hoping to have some cycles to hack on this this week and will post updates or if I'm feeling ambitious (and not burnt out from day job) will create a wiki page for this device. cheers! -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From nobody Tue May 30 14:49:26 2023 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 4QVwKm2tcmz4XcPV for ; Tue, 30 May 2023 14:50:04 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QVwKm14byz4WgN for ; Tue, 30 May 2023 14:50:04 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb2b.google.com with SMTP id 3f1490d57ef6-bacf5b89da7so6795819276.2 for ; Tue, 30 May 2023 07:50:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685458203; x=1688050203; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=McHrTmutPFECv6mEyyuC/ICzYfhZqvEuqGruss/2gHk=; b=aky662lfIOLZhcNReFnuHd+DqG1+Pu7wEsl9GZQDdiI0O8M/CZTtkY17xv9ndWjAF3 oy5TZeXO1Bgnl1sfKw/rxprjlwvhTybWUF+lGy7qUmHKkk+NNaIdKj/4bAh1e5zKW6Ed aF0cImpjADecaW9Rd67/Ung3PY68wHdbOY8eXFB+QBYUA9GLSjzdq95UfNIwiySRtRq2 KlGyFcUM/2A8kJ19+toxOmO9D4XBEpUj6y5QJLQohFwzqRlPlzvnSUQ1pk1d2/Gp6TUb tFdvR9IblobKHReIDgD+AvHiURFoA9kr8WVm0rbaBxkG5I+lVM/G/TK2Fe/nyotLNcvN He+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685458203; x=1688050203; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=McHrTmutPFECv6mEyyuC/ICzYfhZqvEuqGruss/2gHk=; b=FZQJ4y2bHWANYs0TO+qfsKGl17P11jI4vdD9jddpTIE+ZWp4aunUxAW2uasKJb0h7x XKilaQ3ff/sUsp9Vx1UQhA6uiofqWjrWuFLDDRLwKF0ThtBl70RDd/rbiaaystlIZszE 7MvbFIshUovSI/4R8oD7/PfXXH3G8FUfp77UTDxuCAsYgX20nXqfjs0X/S2qSFXek+Oi kL/twgqb94+LhkUsJnfzJo2DPXCPQlu7b9VuxwgrgzESQp+mg+53n8+5+YTaNqOuJ3po mZafuPi/T3QlgIJTbicEQ851wqmjByr6MJL6q+L6A2Ze/JYDH5Lyq3MV43lSDp8aMTi/ zfKw== X-Gm-Message-State: AC+VfDxtYbdQqJwUeCsd8J8PMIkEfjpg3qnlomJ0HywyTJJHHDFSgiF0 mZAUtxOKX82dDoI6/HxMUUrUWmTnXXZ02M2dn30XQBkEDGc= X-Google-Smtp-Source: ACHHUZ7SX4hyB3FOeSOX5EPdrIqfvfOTnaKZjKsUIDuYZF6mBVlAwxztbctWOzrBdFg4auAJBogVyR34GYus12LCZMY= X-Received: by 2002:a81:83cf:0:b0:568:b6a5:9100 with SMTP id t198-20020a8183cf000000b00568b6a59100mr2592348ywf.42.1685458203018; Tue, 30 May 2023 07:50:03 -0700 (PDT) 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 References: <86leh6ggfx.fsf@pcf00001.honeyguide.net> <6984826d-50b6-e311-baa5-581de8d5edf6@nomadlogic.org> In-Reply-To: <6984826d-50b6-e311-baa5-581de8d5edf6@nomadlogic.org> From: Mario Marietto Date: Tue, 30 May 2023 16:49:26 +0200 Message-ID: Subject: Re: PinePhone Pro Boots On CURRENT To: Pete Wright Cc: Stephan Lichtenauer , FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000798c9805fcea51b2" X-Rspamd-Queue-Id: 4QVwKm14byz4WgN X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000798c9805fcea51b2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Someone is reading what I'm writing ? I'm not sure because it seems that my messages are totally ignored. On Tue, May 30, 2023 at 4:39=E2=80=AFPM Pete Wright w= rote: > > > On 5/30/23 05:19, Stephan Lichtenauer wrote: > > > >> > >> But, once i get the linux DTB for this guy into a disk image i'm > >> going to see if i can get the display up next, but would love to hear > >> any input or pointers from folks with more ARM porting experience > >> than me. > > > > I am probably telling you something you already know, but afaik the > > Pinephone Pro uses the Rockchip RK3399 which according to the > > datasheet > > ( > https://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V= 2.1-20200323.pdf > > page 16, 1.2.9 Graphics Engine) contains a Mali GPU. > > > > That means Ruslan Bukin's Panfrost article in the FreeBSD Journal > > Jul/Aug 2021 at > > > https://freebsdfoundation.org/wp-content/uploads/2021/08/The-Panfrost-Dri= ver.pdf > > might be interesting regarding graphics. > > > > Looking forward to your updates! > > Oh sweet - I wasn't aware of that thanks for the pointer! I'm hoping to > have some cycles to hack on this this week and will post updates or if > I'm feeling ambitious (and not burnt out from day job) will create a > wiki page for this device. > > cheers! > -pete > > -- > Pete Wright > pete@nomadlogic.org > @nomadlogicLA > > > --=20 Mario. --000000000000798c9805fcea51b2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Someone is reading what I'm writing ? I'm not sure= because it seems that my messages are totally ignored.

On Tue, May 30,= 2023 at 4:39=E2=80=AFPM Pete Wright <pete@nomadlogic.org> wrote:


On 5/30/23 05:19, Stephan Lichtenauer wrote:
>
>>
>> But, once i get the linux DTB for this guy into a disk image i'= ;m
>> going to see if i can get the display up next, but would love to h= ear
>> any input or pointers from folks with more ARM porting experience =
>> than me.
>
> I am probably telling you something you already know, but afaik the > Pinephone Pro uses the Rockchip RK3399 which according to the
> datasheet
> (https= ://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-202= 00323.pdf
> page 16, 1.2.9 Graphics Engine) contains a Mali GPU.
>
> That means Ruslan Bukin's Panfrost article in the FreeBSD Journal =
> Jul/Aug 2021 at
> https://freebsd= foundation.org/wp-content/uploads/2021/08/The-Panfrost-Driver.pdf
> might be interesting regarding graphics.
>
> Looking forward to your updates!

Oh sweet - I wasn't aware of that thanks for the pointer!=C2=A0 I'm= hoping to
have some cycles to hack on this this week and will post updates or if
I'm feeling ambitious (and not burnt out from day job) will create a wiki page for this device.

cheers!
-pete

--
Pete Wright
pete@nomadlogic.or= g
@nomadlogicLA




--
Mario.
--000000000000798c9805fcea51b2-- From nobody Tue May 30 15:36:21 2023 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 4QVxM81Y2kz4XgvF for ; Tue, 30 May 2023 15:36:20 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QVxM74B6Xz4gW7 for ; Tue, 30 May 2023 15:36:19 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 34UFaLgH046134 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 30 May 2023 08:36:22 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 34UFaLNB046133; Tue, 30 May 2023 08:36:21 -0700 (PDT) (envelope-from fbsd) Date: Tue, 30 May 2023 08:36:21 -0700 From: bob prohaska To: Alexander Leidinger Cc: Yuri , freebsd-current@freebsd.org Subject: Re: Surprise null root password Message-ID: References: <945C9B6D-F2A8-4F0D-BDB0-49A3DE870168@karels.net> <61e30711-f0da-2f42-3a6f-9bd91fc6b1ce@aetern.org> <20230530084133.Horde.4VevT2KY4XCtqoJgvP08jyB@webmail.leidinger.net> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230530084133.Horde.4VevT2KY4XCtqoJgvP08jyB@webmail.leidinger.net> X-Rspamd-Queue-Id: 4QVxM74B6Xz4gW7 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Tue, May 30, 2023 at 08:41:33AM +0200, Alexander Leidinger wrote: > > Quoting bob prohaska (from Fri, 26 May 2023 16:26:06 > -0700): > > > On Fri, May 26, 2023 at 10:55:49PM +0200, Yuri wrote: > > > > > > The question is how you update the configuration files, > > > mergemaster/etcupdate/something else? > > > > > > > Via etcupdate after installworld. In the event the system > > requests manual intervention I accept "theirs all". It seems > > odd if that can null a root password. > > > > Still, it does seem an outside possibility. I could see it adding > > system users, but messing with root's existing password seems a > > bit unexpected. > > As you are posting to -current@, I expect you to report this issue about > 14-current systems. As such: there was a "recent" change (2021-10-20) to the > root entry to change the shell. > https://cgit.freebsd.org/src/commit/etc/master.passwd?id=d410b585b6f00a26c2de7724d6576a3ea7d548b7 > > By blindly accepting all changes, this has reset the PW to the default > setting (empty). So it's a line-by-line merge. That's the most sensible explanation available. > > I suggest to review changes ("df" instead of "tf" in etcupdate) to at least > those files which you know you have modified, including the password/group > stuff. After that you can decide if the diff which is shown with "df" can be > applied ("tf"), or if you want to keep the old version ("mf"), or if you > want to modify the current file ("e", with both versions present in the file > so that you can copy/paste between the different versions and keep what you > need). > The key sequences required to copy and paste between files in the edit screen were elusive. Probably it was thought self-evident, but not for me. I last tried it long ago, via mergemaster. Is there is a guide to commands for merging files using /etcupdate? Is it in the vi man page? I couldn't find it. Thanks for writing! bob prohaska From nobody Tue May 30 17:05:15 2023 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 4QVzL31Vb3z4Xpwj for ; Tue, 30 May 2023 17:05:31 +0000 (UTC) (envelope-from yetoohappy@gmail.com) Received: from mail-ej1-f51.google.com (mail-ej1-f51.google.com [209.85.218.51]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QVzL26zQTz3QMm for ; Tue, 30 May 2023 17:05:30 +0000 (UTC) (envelope-from yetoohappy@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-f51.google.com with SMTP id a640c23a62f3a-96f5d651170so441466b.1 for ; Tue, 30 May 2023 10:05:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685466328; x=1688058328; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=DactT0CDu5CMwtrEQFbKRs2ZO7/LmVhwmXToAA87BzY=; b=fqxaFM1gHfl3hN3eU+ealJzo70RU7GA2porUChiSjsU6LYfJywdPoHt3Cqi3oLuGdM YEkXY3gwsVDXXJpss3eezkokwNS/KWx8VD40IgsSqHjbHw+RpWW+rB29m9VKYcNYdtOy wCsiYGFWjwigV2vj5pCiE5iEjfwuHTbq4sicituWrPixvHrO11ajZ+6nXpPOxhA26Dlk fVKWS0OtFwwPlkRgVAnlT2/dobKV5j+2anNrHM3TuDfGHxE885urSU2a+o9Kqt5lDYO5 I+xXfdz7pXs60YqJfDSa6htxbfT6zp3XWgt8AEmLMA5ymVfVVpEeQeU4gnrSjpMssH9X BJPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685466328; x=1688058328; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=DactT0CDu5CMwtrEQFbKRs2ZO7/LmVhwmXToAA87BzY=; b=RvUZ9eJ/iTdhc62BamDwGl4YhR5/gE7EFl0/qTIB6yu3FwtO33qIldL4gQO49floTp R80XpmAB3pHRU0+4TIF3E19LvgPKuIDqZJGQzDcahi6sOuVh1E+X0ZVM1MgfNeVNLKDk bXKDuUgwy16F+DsbhjejuakjumjGBQ5W8NrQX7UoVcmX9ztyEVrMyoevdB1BIuOVO+tk VUCGS1FLmgp4q+k6kSeFNQUFQG+J+oEDYlJkHmgNJrmjGECi31TFUMqJpjK8oqnebXDa eUPud/Ce8BErZHbtKddKxrWXEkkwQ/niPKos88YYovg7EOSkbCe9KQyq1ofmLfP/RZ4z 51UA== X-Gm-Message-State: AC+VfDyaZsqtuQE2OVVR+1CF9oOiXsVozAV0rxi2MqP+ZKhHLfQDhHuj WHD2DIqBevhXjmoXdCme0MBMjLKxr1/A2vJ8PM8= X-Google-Smtp-Source: ACHHUZ5gYHgmduUCDEiNLagKrti2bvvrCmBk9pSe71p2gM/0AfzQBLfu4t/Fyyty/4S4ihvlw9Qvci7fSBmJV8aibGY= X-Received: by 2002:a17:906:ee88:b0:96f:aed9:2520 with SMTP id wt8-20020a170906ee8800b0096faed92520mr2583216ejb.21.1685466327529; Tue, 30 May 2023 10:05:27 -0700 (PDT) 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 References: <945C9B6D-F2A8-4F0D-BDB0-49A3DE870168@karels.net> <61e30711-f0da-2f42-3a6f-9bd91fc6b1ce@aetern.org> <20230530084133.Horde.4VevT2KY4XCtqoJgvP08jyB@webmail.leidinger.net> In-Reply-To: From: Yetoo Date: Tue, 30 May 2023 10:05:15 -0700 Message-ID: Subject: Re: Surprise null root password To: bob prohaska Cc: Alexander Leidinger , Yuri , freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4QVzL26zQTz3QMm X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Tue, May 30, 2023 at 8:36=E2=80=AFAM bob prohaska w= rote: > > On Tue, May 30, 2023 at 08:41:33AM +0200, Alexander Leidinger wrote: > > > > Quoting bob prohaska (from Fri, 26 May 2023 16:26:= 06 > > -0700): > > > > > On Fri, May 26, 2023 at 10:55:49PM +0200, Yuri wrote: > > > > > > > > The question is how you update the configuration files, > > > > mergemaster/etcupdate/something else? > > > > > > > > > > Via etcupdate after installworld. In the event the system > > > requests manual intervention I accept "theirs all". It seems > > > odd if that can null a root password. > > > > > > Still, it does seem an outside possibility. I could see it adding > > > system users, but messing with root's existing password seems a > > > bit unexpected. > > > > As you are posting to -current@, I expect you to report this issue abou= t > > 14-current systems. As such: there was a "recent" change (2021-10-20) t= o the > > root entry to change the shell. > > https://cgit.freebsd.org/src/commit/etc/master.passwd?id=3Dd410b585b6f0= 0a26c2de7724d6576a3ea7d548b7 > > > > By blindly accepting all changes, this has reset the PW to the default > > setting (empty). > > So it's a line-by-line merge. That's the most sensible explanation availa= ble. > > > > > I suggest to review changes ("df" instead of "tf" in etcupdate) to at l= east > > those files which you know you have modified, including the password/gr= oup > > stuff. After that you can decide if the diff which is shown with "df" c= an be > > applied ("tf"), or if you want to keep the old version ("mf"), or if yo= u > > want to modify the current file ("e", with both versions present in the= file > > so that you can copy/paste between the different versions and keep what= you > > need). > > > > The key sequences required to copy and paste between files in the edit sc= reen > were elusive. Probably it was thought self-evident, but not for me. I las= t tried > it long ago, via mergemaster. Is there is a guide to commands for merging= files > using /etcupdate? Is it in the vi man page? I couldn't find it. > > Thanks for writing! > > bob prohaska > > It's been a while for me so I forget if etcupdate resolve is automatic or there is a prompt or message about it, but the guide at https://docs.freebsd.org/en/books/handbook/cutting-edge/#updating-src-compl= eting-merge-etcupdate says: If etcupdate(8) is not able to merge a file automatically, the merge conflicts can be resolved with manual interaction by issuing: # etcupdate resolve But this info is far below the steps at https://docs.freebsd.org/en/books/handbook/cutting-edge/#updating-src-quick= -start with section 25.6.6.1 also not being mentioned in the steps. Info on merge commands, regardless, is under the Resolve Mode description in the etcupdate man page https://man.freebsd.org/cgi/man.cgi?etcupdate. From nobody Tue May 30 17:55:43 2023 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 4QW0S34HHMz4XtsW for ; Tue, 30 May 2023 17:55:47 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [66.165.241.226]) (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 (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QW0S22mgPz3nh0 for ; Tue, 30 May 2023 17:55:46 +0000 (UTC) (envelope-from pete@nomadlogic.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=nomadlogic.org header.s=04242021 header.b=Z+HPILQr; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 66.165.241.226 as permitted sender) smtp.mailfrom=pete@nomadlogic.org; dmarc=pass (policy=quarantine) header.from=nomadlogic.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomadlogic.org; s=04242021; t=1685469343; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=/EGNb77Shh9hZt8R7dZQdyAuZFBkc+zgyWzT1bJGAyI=; b=Z+HPILQr+o1Nxxa/K8S4FO2+jeWpMC9YfHp7Sp/2CTsIiz8wfphdCaKDjbcZQCSUIbwm0M aq5wCsNjA8tLd98yRz5mA9PCK7KR/KBT6bg0MMeMdTtxKtX0JamMxnd9osREX/8mCn5GvJ AqN4yKC2pCL7oe9zMX0JJ8Ra2Fd9Ya8= Received: from [192.168.1.240] (cpe-24-24-168-214.socal.res.rr.com [24.24.168.214]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 68334c8c (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Tue, 30 May 2023 17:55:43 +0000 (UTC) Message-ID: <58e672ec-f6f0-404f-7b92-fa8df0dc67e5@nomadlogic.org> Date: Tue, 30 May 2023 10:55:43 -0700 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:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: PinePhone Pro Boots On CURRENT To: freebsd-current@freebsd.org References: <86leh6ggfx.fsf@pcf00001.honeyguide.net> Content-Language: en-US From: Pete Wright In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.988]; DMARC_POLICY_ALLOW(-0.50)[nomadlogic.org,quarantine]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[nomadlogic.org:s=04242021]; MIME_GOOD(-0.10)[text/plain]; DKIM_TRACE(0.00)[nomadlogic.org:+]; ASN(0.00)[asn:29802, ipnet:66.165.240.0/22, country:US]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4QW0S22mgPz3nh0 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On 5/30/23 6:02 AM, Mario Marietto wrote: > That's interesting. As I have already said,I haven't bought the > pinephone pro,because it is expensive for me. So I'm working on a > parallel project. I've bought this phone,instead : > > https://www.hdblog.it/schede-tecniche/samsung-galaxy-a6_i3655/ > > That's cheaper. Between the specs I read that it has a mali gpu,too :  > Mali-T830MP2 > > so,eventually,I can use the Lima and the PanFrost driver even for my > samsung galaxy A6 ? I've started planning to install FreeBSD on top of > the Android Kernel,using a specific patch,but now I'm thinking that > maybe,I can install FreeBSD there natively. Can someone tell me if it > is doable,giving a look at the specs of that phone model ? thanks. > have you tried putting a snapshot from CURRENT on a memory card and booting it?  i'm not familiar with that device, but i suspect you'd need serial console access. -pete From nobody Tue May 30 18:02:13 2023 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 4QW0br5jVVz4XvFS for ; Tue, 30 May 2023 18:02:32 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic310-21.consmr.mail.gq1.yahoo.com (sonic310-21.consmr.mail.gq1.yahoo.com [98.137.69.147]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 4QW0bq4Bqmz3ptH for ; Tue, 30 May 2023 18:02:31 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=nRag0BjR; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.69.147 as permitted sender) smtp.mailfrom=marklmi@yahoo.com; dmarc=pass (policy=reject) header.from=yahoo.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1685469748; bh=D1JSFyMsQnJ0UnEEw1Mtbmmk8nKWJ5Tcf67xgNZdcHA=; h=From:Subject:Date:To:References:From:Subject:Reply-To; b=nRag0BjR4cx10z0dkQD4LNYuDl/FoDbMRisPhQzmUS4iYs9V9/NGoyYi8UulDoOrtP40mEHTdNyjBHV0FwCBO796A2z+zHZCH/pj7wVBPSFodLgJ995DAG29OsRvWqqWLALK+bIqby3Sl/8v3H+dU9dtaBjBIh71SipwYa9E8Yvb+ZqDN0TVHoCxmn43ONUe9isCc4cSFPWNXuPydddY+8LQGXlbGI+K/kxKMO6txezJGNWcJqEQv3DIJTKVw9TEirqeoM70AnxnZctwWWFiUIo4ATpjAsTnLhohk8iz4ExxPHxKFQcsyHNi30Jj5tZkD2OlktqGmsH9zaXkZwF48A== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1685469748; bh=abg20rPMMeOnJn/ktoonb9kgZ3Pul5U7TJQx+NBjv2s=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=aCU00j0++5X862Kn6o30cjM26kzCh4EF95HDJhjJYqzy084h4bVNeDbjor98wYCKOIxskXrM3fS/WhiaBcHLlm6EV40EFzHjq/8VNqsL2mQ5THfQ78EddfkV9Y2ZKKO1H5KLXPg7HnpPEfMiHrVtYZmEOY7HoEiFGfXuVAJ/8lAlI/FFpoDKiqVlzxI+n338AozROZO4wMNcpTZrjkwwH/xfz5jEsEt1Yesc7PI2A0l2MvezO2ec4WkWDkTasb4Ae+REfVOF6HVA56tJs7DBjS8tZVJ8lsechJAsGZoGuwq0SdSmG/12NxFLIHWgQ7gkbk5ciYMd5XMshQmFKrmJWQ== X-YMail-OSG: euQU_UkVM1l.XxdBasCeZzSuG5DG.oToVkdgpxL1tuGxmh44S_5N0M7ao3mQjJM a8Lvb3UaTPk8GQEot7n559t0bVav6Tw15l0K3JkB_9IUxCHeQAuX5B23o5AHuzahMZFVVT6MInzB 7K3254hTe9wHluSa.msoDjcqr0zGuWajliENkI18hIRM24AMdUrPXlEU5U_gMB_BHaGilrTYSrlF v5YDlBhS4PXYl4edU_LnxoRXemAXCJthE4SDo28II9jaCNIGDkq5R3ve9Ldj4nFXrQj6yr.7Egbu Wh87hb5_1qfFAudCW32Kf7SgWiWwKdmxi9FWuIsLwq4gw7FbLMtIu3p3tF5SWXy_whtSHdrQ9qs8 R_WveEeOHTvwk3hlFT2Ou_3W3riIK.J.wfXDguldZfZx018_etXLX31nwOGnjb9r6q_VKcbt_K5W kI2xSOuOa8pPG.VNBrEOCWUt.cGNmEon3unySuPYf7OrpzDtmTRmrTC4gMK6CPebRmGAJg3hYrah w8Y8YWeKNrCyk7AgK4Y9vQIBmWuSey_j5vv0uNHEv_aPgaGEFHAqce46eF2LqPojklK8kFjTfbl9 NdS4vpF6YbAi1IsKUKEisxI1jrrqBl.nhboUmURdRPHy36ScW7.VtgQNabE3PZ3i2CIi_GyqYwsF WDdVUP5Y3rVmCbn3hdmkgqdl6EpxLeIG0nNceGZguhytmQ1TwsjFRdjHglkXv8jF2nZkextZMUcK 7vL2r_qv.G0AfeBTRINg85dkt54bxbMYP5WNivWIWqg.laHGjAdu6uJk2VBuFSqCD0aFY3QUHJQJ ngtmWCI4olIn2jssCGl0Ibd4x9awbhTbRC3j3F5r5fdSwPDYlrnm1c4J0hMelsoPcRCl_0CfnRMg 76KVpp.ZDLitMqF5AG1yQdmj_YOd50q3XPOlOy6BzNLnp1GgUGW7SSWHs1ViVPjj0Rfk2PuRy58y beQsbbHZnaDYGnQZCe9qj.ot.43VnWc8BhZAr2ubqIElyMHl7_6ypDAe_K4kpDe48NpMo.1NlINB FniJSb0U1nYqeCxYF_7x8fQ5Nyjg1yMbyb64JOak.mT6R9tvXmSyzQ_S_08tsclLTb_xqaOr_VZQ dDEVOPTk.Mgp7N7wvCQY3S3dQ0PStWvtNZigGLKDULWy2I6Sf2Kw9vzfOMCE7OOb7mdi8ok8xyf. BJmEjvezoake24N9M4wbZo87DU6L1eDEnVsuhqVQ_UpVFsVH8gak5wnZmqAkxtvNdqBlh8MKSsYS 9MKbetmfgsLwTz4fKmjY3OP7yU76T1DNgkH0W8lggUdxeNDyz16ZV0.DN_HGtWKKOt96TU.aJpkc MPydwWeIPn7C92AjE9gYofkf4cV3BBMb_WjemEPTWb6NjnqFUJTzS0ad0iEQstVuhd8vSBHELhwA lRahbfHowIetIJlWFSOhfqID9i.O2jdj372vnYJFzLGXnbSrkQTg.ItfHwI2p0cE6UW2E5zKhuGV Bgs68jwAMuSA_Nq1U7WVAIfL6KWVMmGLfoOgINSOKuZ87aSA7kelmyuvtQAVsFlzBGRLpPsDAjNG sAkuo3y1k8YzaiyT_ePyHed.7pNnOIRWM4IhxrabAjJS4CsUENWVTmgaMR3dyOjKjrJzG2jn.W6p K_uVElQLS.Z3J.br3AztPVPVBCwZAprkCTkttzEW3shsVs861iwmoVRfkR8..rc8MgEYw0H6e5bj kFfzv.YWvqoNaHAQQDAixdJF1.SfGlpozLe7bHMzHuZtwkOx__diy8oaofd8LYkMibVF7OOyOZFx 8oPTt4ih1DaZx.INki0E6HtHwuRYdrsS0wFxsH4WgknZcHBcFeIc5j0ZBrYRDtF3brJ6ObeMznvt iIu1BU0Ad8gS6BzmnbYf1D0am.V0A8BuCHFIcd5yilonfWL9MSXTRrQyqo4vOaR3TaQwhQT_spRn 7LFnluKMAEFKdy3dUwCSETQ2YLnV8zPYiDc.R90z2mqktS0yf_Rq8zEGJF8mxbal.gXZwU4alS7L OwbPeNO6aGbunuFGyDEsr8YdJP4w884WYRmEcN59mj.EN2DdJW2SpdQHCrVp2eSoEDSaE5eljN50 X1xAY.78g3KvbGMbDfxP3I0d8j.vx5lZP2EF_XZMcNZWgD9f1v7KFzdPmrpAwpXli8UXC0INmHmT zzMio3Sed601ZSQJfbW7pBpT0dP6HiVnnS5Waa8ju0SAEhVXz25BSZGSmmDf3x6jynxXorzH3eYx 0YVyx4hyYZF697Dyvmb_HR4T_173mBiCMNeuSUv_0j_Fz3BtOkebHpmMx2J0kARGnhqzZC2bYAnL Fj7Sf X-Sonic-MF: X-Sonic-ID: 1abe14cc-0f6b-4bf5-9b38-37f25d9b4365 Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.gq1.yahoo.com with HTTP; Tue, 30 May 2023 18:02:28 +0000 Received: by hermes--production-bf1-54475bbfff-4p8s9 (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 15588e802c32bb315a3c8172d1941fc1; Tue, 30 May 2023 18:02:26 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable 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 \(3731.400.51.1.1\)) Subject: Re: Surprise null root password Message-Id: <8721FE04-3769-473C-BAAD-EB0A4FCFA1D7@yahoo.com> Date: Tue, 30 May 2023 11:02:13 -0700 To: bob prohaska , Current FreeBSD X-Mailer: Apple Mail (2.3731.400.51.1.1) References: <8721FE04-3769-473C-BAAD-EB0A4FCFA1D7.ref@yahoo.com> X-Spamd-Result: default: False [-3.41 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.91)[-0.907]; MV_CASE(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; RCVD_IN_DNSWL_NONE(0.00)[98.137.69.147:from]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_DN_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[yahoo.com]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.69.147:from] X-Rspamd-Queue-Id: 4QW0bq4Bqmz3ptH X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N bob prohaska wrote on Date: Tue, 30 May 2023 15:36:21 UTC : > On Tue, May 30, 2023 at 08:41:33AM +0200, Alexander Leidinger wrote: > >=20 > > Quoting bob prohaska (from Fri, 26 May 2023 = 16:26:06 > > -0700): > >=20 > > > On Fri, May 26, 2023 at 10:55:49PM +0200, Yuri wrote: > > > >=20 > > > > The question is how you update the configuration files, > > > > mergemaster/etcupdate/something else? > > > >=20 > > >=20 > > > Via etcupdate after installworld. In the event the system > > > requests manual intervention I accept "theirs all". It seems > > > odd if that can null a root password. > > >=20 > > > Still, it does seem an outside possibility. I could see it adding > > > system users, but messing with root's existing password seems a > > > bit unexpected. > >=20 > > As you are posting to -current@, I expect you to report this issue = about > > 14-current systems. As such: there was a "recent" change = (2021-10-20) to the > > root entry to change the shell. > > = https://cgit.freebsd.org/src/commit/etc/master.passwd?id=3Dd410b585b6f00a2= 6c2de7724d6576a3ea7d548b7 > >=20 > > By blindly accepting all changes, this has reset the PW to the = default > > setting (empty). >=20 > So it's a line-by-line merge. That's the most sensible explanation = available. >=20 > >=20 > > I suggest to review changes ("df" instead of "tf" in etcupdate) to = at least > > those files which you know you have modified, including the = password/group > > stuff. After that you can decide if the diff which is shown with = "df" can be > > applied ("tf"), or if you want to keep the old version ("mf"), or if = you > > want to modify the current file ("e", with both versions present in = the file > > so that you can copy/paste between the different versions and keep = what you > > need). > >=20 >=20 > The key sequences required to copy and paste between files in the edit = screen > were elusive. Probably it was thought self-evident, but not for me. I = last tried=20 > it long ago, via mergemaster. Is there is a guide to commands for = merging files=20 > using /etcupdate? Is it in the vi man page? I couldn't find it. # man etcpudate . . . CONFIG FILE The etcupdate utility can also be configured by setting variables = in an optional configuration file named /etc/etcupdate.conf. Note that = command line options override settings in the configuration file. The configuration file is executed by sh(1), so it uses that syntax to = set configuration variables. The following variables can be set: . . . EDITOR Specify a program to edit merge conflicts. . . . ENVIRONMENT The etcupdate utility uses the program identified in the EDITOR environment variable to edit merge conflicts. If EDITOR is not = set, vi(1) is used as the default editor. So, if you do not want to use vi, you can use either the EDITOR environment variable or an EDITOR assignment in /etc/etcupdate.conf to change what editor etcupdate uses for you to edit merge conflicts with. =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Tue May 30 18:20:20 2023 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 4QW10Z1gh9z4XwR9 for ; Tue, 30 May 2023 18:20:30 +0000 (UTC) (envelope-from garyj@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QW10Y4c1Tz3rrb for ; Tue, 30 May 2023 18:20:29 +0000 (UTC) (envelope-from garyj@gmx.de) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1685470820; i=garyj@gmx.de; bh=DOmTIRXNsjNOn+PVqk41TjA5FhfyYeEjs+BHHll8VE4=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:In-Reply-To:References: Reply-To; b=qyJ7xTzR+F2BoVU83GiPEMcu3CZmyyMN7LSuznXVoYNmFx+u4wFgAfy1aoJRluaic /DSVr/F6YuA4vcEKvd7FYYnYc4tCev6Xd7I3mwm3lQRuCvdUMi6Cb77Wql7KZRxutW FVvO/mxQFIfZAS6oqcnQWDCJXN2So5wogez/2sxjx7f+2moBCMtO4aKg6WSFUIcBCJ wnAaCQ49+HTboxWUIoUi+Aux0uENk/Dit+PtQIqvERA8KLtftsjkz94lnhC7odG+fo TLW1dnz9LaxgHFkte1ENcz2re3qhXyiMJlEJ11V3TtC2l7utrX4cYEc/vIHmqHdsLm wgKTKqhQVSntQ== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from ernst.home ([91.59.225.146]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1M4b1o-1q2PGE2WN4-001lut; Tue, 30 May 2023 20:20:20 +0200 Date: Tue, 30 May 2023 18:20:20 +0000 From: Gary Jennejohn To: Mario Marietto Cc: Stephan Lichtenauer , Pete Wright , FreeBSD Current Subject: Re: PinePhone Pro Boots On CURRENT Message-ID: <20230530202020.060be2bf@ernst.home> In-Reply-To: References: <86leh6ggfx.fsf@pcf00001.honeyguide.net> Reply-To: garyj@gmx.de X-Mailer: Claws Mail 3.19.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:r0RuzghLnyo13IYhfSjMVRzu/zAa+lcNxSxSPxDcPVirjWOc9uy 4DAcvxCyaeds0lJZfSj24DmjzsAKIxYwsugmxKPzjSHKxcYj8+I9FeLKGmlj6MZhyX7IYRq /Q+7obcaGLLhtQFDUw/O+5qkGC7+ZbuRP+dbuGzjB3J7/lC0G/2BTXdqjap/XQwBtG71eqn +1LKtdsfd5DWLDI1QaMMg== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:KY+ETFbxUWs=;NulOUPkmOlezc7bkbQvii/6dyIf RSnx5Kla/x6IhP6Ja+Hhm31rQN6Bo3X5DyxHb0hNqElqYdOSr7ZtvFGUF7tCFGaLtfDTOSVTj EELCLGRz1dTIlVmomZWjXmHsMXPHvAIT36JFtP4Vg1gkfiG9b8JbRVb4LkodXBweIH/PGS3QY JY63NYf5Yv6T7gJDSYxXA+kHM4B405jRBFHj1vONbC3VaRoYNx9Xu6BH+syFW9cwuhNN2BEdO Dw406f4+i+ZFTJYV6/PsGt9ncJu9uMIywg9/wxbUuxd7R8BttqywA3NimsmMaEypYtDsZiUia tnXtsTPd5xvCTZJn9IX1E19mgd+KQD1apbiaGTCbNefruBdogeUhjYBv250U7s5PzQLDoq5NV aYP+uNgMoGLmMmuD2ZTn8CRhQKmGqfLIAGsXPGDjRCcsrjSmQo08htl7MnlgrcSyZ1VfzzDa8 xqhW38hSZuUdtWqH88kN4T8uaewKQRkkiuhEZbaVC/fttWkxabdDFlrd97oUx8UNQLbKJumWu eO8e3atkmcWLhyH0Yv4QedZ1qZKZqK26GFLQvm4uqibxwvJ9dk9ofc9IbCwZkJb0k1nu1sL/P sLssheh9SnYafuWqgCPn4wHsBiZOkDH4Ny1+aOJpL5fcHjxsEJHD5AI/wFTT+19cwWfFqiS+B Ywzo6z4yVNgSs7SwhOQHTwJ4F5UmPVWR3r+/5mzL+SI2obfMDgp7wP9Nxpm8DkzUq6zAsFoFf 9KWVKjR3Sy2q0IyJ8FYgUZTQZLJgopGvY/nYhTM2jtrvZ2PLnuCxyj+xKDAl+3ub8Xqnd7Ief Hj8338md4esPjBOjN7cDrSwqBaFOLPXOx4dLLzVWpNYT6X7PeQMoBv88hDBjV6BzteP3L9zFT tLctOhHE6H5SS0ldMGgk+lyBRPpSBdpiR3nXrIHt8uA1N0obUg6L03c0GI554ELj9GcHtbuoq GNxtBg== X-Rspamd-Queue-Id: 4QW10Y4c1Tz3rrb X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Tue, 30 May 2023 15:02:38 +0200 Mario Marietto wrote: > That's interesting. As I have already said,I haven't bought the pinephon= e > pro,because it is expensive for me. So I'm working on a parallel project= . > I've bought this phone,instead : > > https://www.hdblog.it/schede-tecniche/samsung-galaxy-a6_i3655/ > > That's cheaper. Between the specs I read that it has a mali gpu,too : > Mali-T830MP2 > > so,eventually,I can use the Lima and the PanFrost driver even for my > samsung galaxy A6 ? I've started planning to install FreeBSD on top of t= he > Android Kernel,using a specific patch,but now I'm thinking that maybe,I = can > install FreeBSD there natively. Can someone tell me if it is doable,givi= ng > a look at the specs of that phone model ? thanks. > Based on my experience with Samsung it probably won't be a simple task. Samsung tends to block the bootloader such that it's very difficult to install anything but Android. https://www.xda-developers.com/ has a fair amount of info on the A6. It could be worth your while to take a look at what's there. =2D- Gary Jennejohn From nobody Tue May 30 18:31:20 2023 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 4QW1Fp5byMz4XxlK for ; Tue, 30 May 2023 18:31:58 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com [IPv6:2607:f8b0:4864:20::b35]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QW1Fp0n6Qz3vFN for ; Tue, 30 May 2023 18:31:58 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb35.google.com with SMTP id 3f1490d57ef6-bacf685150cso8694877276.3 for ; Tue, 30 May 2023 11:31:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685471517; x=1688063517; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=k5n9IP4EQaGWwem5e77ejKTzAiOcElWAMaEfQRrDna4=; b=bhAj43tEiJD+7+YYduryDv+mDcATAzUbTYa0uj9HDMCxUkkxndIu/p1KaTzxzSxZEB ReEkg/K6PPvsbeMnF3M1wsahMdiHKQfV4JQLUYf7Q1XSZ6GpwXKy+tKpvYgVfXESacXb dZvLyTQ6IfI7YvCjuVOIkD5hmGpeLJ+V5QkiwSp+nCDtbot79RmM86hbNW7HFy8KudH7 k8T6i5rg5/2niLK0itLa7gY4GlC/PzKLt9oT6Ewx40w48YpFNumwjtqFt72WlUYFA5fq G5SkNzz5NMXsChRC5NxZs2Ey9PBnave2Ly7Cg0nCCfum4Q0P+0+WbJhTS9TOiu380LwU fLrA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685471517; x=1688063517; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=k5n9IP4EQaGWwem5e77ejKTzAiOcElWAMaEfQRrDna4=; b=UK+wVPzviLLOONOR9FBfA0uFLikY3bxfXX+YqEdGylgKBDT81dZWWkQU849W3k7NPa dGNFPwkIQ/ATaL9H2v1owcl/o2DiNZQ6uq36oZ1Kv3GPEkszCGZh0ZvQuncgGmhfAbkT GuLMYm5ceFtL99rCyFNLhoLdO6uXKPRMq1gYyq1UQOLJib/4yHyFJlGZEn996HE0nOKA 2yCKUgsLOntuxl0+wLOQks2PfgsWOmIjP8Yv8z49qKyC5ZODmlodtoOkKjsiMtPQehFk jfS4jgiZH96jdLasVZH7wP73nfpHVyedJ7NI9ASaVVR4XnBur0a9/pGOlcZMKa2j/FSt Nz3Q== X-Gm-Message-State: AC+VfDwvnmmVeultBNHj+otBJH9GUt1PEt8/sFtP9cmtfNoBOKHLrycH BWDYRoMmQfMvUBqrsyQ+kXL+x+l5I8ZQR0xDT1ocB21d1SkmZg== X-Google-Smtp-Source: ACHHUZ5V93VCh89EkbdXc24XYHrSJ0jlinICryxsSFJZ3QEhBMrXRbmeqXTWbOYSDVSLZ59P+rNXWnOtwqdNlU+Ty8Q= X-Received: by 2002:a81:7d41:0:b0:561:ed46:2f51 with SMTP id y62-20020a817d41000000b00561ed462f51mr3304928ywc.22.1685471516789; Tue, 30 May 2023 11:31:56 -0700 (PDT) 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 References: <86leh6ggfx.fsf@pcf00001.honeyguide.net> <20230530202020.060be2bf@ernst.home> In-Reply-To: <20230530202020.060be2bf@ernst.home> From: Mario Marietto Date: Tue, 30 May 2023 20:31:20 +0200 Message-ID: Subject: Re: PinePhone Pro Boots On CURRENT To: garyj@gmx.de Cc: Stephan Lichtenauer , Pete Wright , FreeBSD Current Content-Type: multipart/alternative; boundary="00000000000009918305fced6b12" X-Rspamd-Queue-Id: 4QW1Fp0n6Qz3vFN X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000009918305fced6b12 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable My idea is to patch the kernel with this patch : https://github.com/sleirsgoevy/exynos-kvm-patch in the worst case scenario, I will virtualize FreeBSD with qemu + kvm on top of Android. On Tue, May 30, 2023 at 8:20=E2=80=AFPM Gary Jennejohn wrote= : > On Tue, 30 May 2023 15:02:38 +0200 > Mario Marietto wrote: > > > That's interesting. As I have already said,I haven't bought the pinepho= ne > > pro,because it is expensive for me. So I'm working on a parallel projec= t. > > I've bought this phone,instead : > > > > https://www.hdblog.it/schede-tecniche/samsung-galaxy-a6_i3655/ > > > > That's cheaper. Between the specs I read that it has a mali gpu,too : > > Mali-T830MP2 > > > > so,eventually,I can use the Lima and the PanFrost driver even for my > > samsung galaxy A6 ? I've started planning to install FreeBSD on top of > the > > Android Kernel,using a specific patch,but now I'm thinking that maybe,I > can > > install FreeBSD there natively. Can someone tell me if it is > doable,giving > > a look at the specs of that phone model ? thanks. > > > > Based on my experience with Samsung it probably won't be a simple task. > > Samsung tends to block the bootloader such that it's very difficult to > install anything but Android. > > https://www.xda-developers.com/ has a fair amount of info on the A6. It > could be worth your while to take a look at what's there. > > -- > Gary Jennejohn > --=20 Mario. --00000000000009918305fced6b12 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
My idea is to patch the kernel with this patch :


in the worst case scenario, I will virtualize FreeBSD with qemu + k= vm on top of Android.

On Tue, May 30, 2023 at 8:20=E2=80=AFPM Gar= y Jennejohn <garyj@gmx.de> wrote:=
On Tue, 30 May = 2023 15:02:38 +0200
Mario Marietto <marietto2008@gmail.com> wrote:

> That's interesting. As I have already said,I haven't bought th= e pinephone
> pro,because it is expensive for me. So I'm working on a parallel p= roject.
> I've bought this phone,instead :
>
> https://www.hdblog.it/schede-tecn= iche/samsung-galaxy-a6_i3655/
>
> That's cheaper. Between the specs I read that it has a mali gpu,to= o :
> Mali-T830MP2
>
> so,eventually,I can use the Lima and the PanFrost driver even for my > samsung galaxy A6 ? I've started planning to install FreeBSD on to= p of the
> Android Kernel,using a specific patch,but now I'm thinking that ma= ybe,I can
> install FreeBSD there natively. Can someone tell me if it is doable,gi= ving
> a look at the specs of that phone model ? thanks.
>

Based on my experience with Samsung it probably won't be a simple task.=

Samsung tends to block the bootloader such that it's very difficult to<= br> install anything but Android.

https://www.xda-developers.com/ has a fair amount of info on the = A6.=C2=A0 It
could be worth your while to take a look at what's there.

--
Gary Jennejohn


--
Mario.
--00000000000009918305fced6b12-- From nobody Tue May 30 18:50:52 2023 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 4QW1hL3CrZz4Xyn5 for ; Tue, 30 May 2023 18:51:30 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-yw1-x112f.google.com (mail-yw1-x112f.google.com [IPv6:2607:f8b0:4864:20::112f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QW1hK3fNrz40pn for ; Tue, 30 May 2023 18:51:29 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=QM9QC4P1; spf=pass (mx1.freebsd.org: domain of marietto2008@gmail.com designates 2607:f8b0:4864:20::112f as permitted sender) smtp.mailfrom=marietto2008@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-yw1-x112f.google.com with SMTP id 00721157ae682-565a3cdba71so67847137b3.0 for ; Tue, 30 May 2023 11:51:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685472688; x=1688064688; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=w8CYlwxaPoXpGTRB+hpyUZBrAU9JCgoU+zhnCCqGMgo=; b=QM9QC4P1F4r5ukFQa4kyiWXUCoZD0hgOsx+cEr4OY5s39CQFkMrAm/R2qbdvnnNjHo Gkhr4a1E1M/IuiYfN6mFw0spb5FJ5QNVCTzxnru7nrqJiF+9G4Zl9p3WzwMH7geytJqr gAQS7GiAsaCIjPxqvXnkg7RofKq8C123uLPTLln9lf5Cl+dJN+GPrOCRRKeiGDte70dQ 9oS9r1JKFI3MKc7EpOGWjK4Qr8ykOcqJ7Fwu6XZwZnuLcp+O0cG3U7wdHnjrFfXCJJ+d unzH16qBG/D/XBvbue6Fu2BHs3/fnK9M0AnPq1OTyYEic8YIhhyVHFdv/53+6LVINZO8 X7pQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685472688; x=1688064688; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=w8CYlwxaPoXpGTRB+hpyUZBrAU9JCgoU+zhnCCqGMgo=; b=S8TNANb0EaJuNL0GrLkBYGrrgVYXSPYQL8h9WXWJFv8NRbWv6qorpMLO9GUubr3Qcr RUMO63TNQlMbF7ZCrvDA/Dvv8ZHeDm3AYp8uvJf25ejgM97/YWAzf1M1k8ceeIY571i+ mATYfxsELCqZey28UoxRoL9CB+m5TSbrYNZb0WWKFvw1Pz9jnD3S99kuxJd7pi6OdeY6 1jdQsxUdlQ8Dxbc8Jx8+n79Uz/N/bfoz1QO6OqVuPVuipWK2hrKLyAwETmFH79COEUi1 ERZHGQfOoWudakBmCX1B3hX1g61DBxyTz2bvwuj9TJFS0nCSnc8wV4i+Sel/kAlV+p5l IU8g== X-Gm-Message-State: AC+VfDxwOkCbJY2oEUNQ5tG5A+8DK4UWfxeUfMFu+2+fZXUvw6gPACNQ BRihtEn4weo2hbI/MVfICyeqI8yjGoXy84cpQ6liQWSfbTfiEg== X-Google-Smtp-Source: ACHHUZ7LaT/5vnqkQWakAOswsG18WtK01SrHPFaUA9xS9u251/6aeCDn5cdnnYHM/5aq0Ty3oCGAKGMVlX+a0C66+rw= X-Received: by 2002:a81:a154:0:b0:561:e2dc:fc60 with SMTP id y81-20020a81a154000000b00561e2dcfc60mr3389565ywg.25.1685472688200; Tue, 30 May 2023 11:51:28 -0700 (PDT) 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 References: <86leh6ggfx.fsf@pcf00001.honeyguide.net> <20230530202020.060be2bf@ernst.home> In-Reply-To: From: Mario Marietto Date: Tue, 30 May 2023 20:50:52 +0200 Message-ID: Subject: Re: PinePhone Pro Boots On CURRENT To: garyj@gmx.de Cc: Stephan Lichtenauer , Pete Wright , FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000dbdf9f05fcedb014" X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::112f:from]; ARC_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FREEMAIL_TO(0.00)[gmx.de]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4QW1hK3fNrz40pn X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N --000000000000dbdf9f05fcedb014 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Check at this,also : https://github.com/raspiduino/a6lte-kvm/releases What I would like to know is if I can install Linux as the main OS,instead of Android. Thanks. On Tue, May 30, 2023 at 8:31=E2=80=AFPM Mario Marietto wrote: > My idea is to patch the kernel with this patch : > > https://github.com/sleirsgoevy/exynos-kvm-patch > > in the worst case scenario, I will virtualize FreeBSD with qemu + kvm on > top of Android. > > On Tue, May 30, 2023 at 8:20=E2=80=AFPM Gary Jennejohn wro= te: > >> On Tue, 30 May 2023 15:02:38 +0200 >> Mario Marietto wrote: >> >> > That's interesting. As I have already said,I haven't bought the >> pinephone >> > pro,because it is expensive for me. So I'm working on a parallel >> project. >> > I've bought this phone,instead : >> > >> > https://www.hdblog.it/schede-tecniche/samsung-galaxy-a6_i3655/ >> > >> > That's cheaper. Between the specs I read that it has a mali gpu,too : >> > Mali-T830MP2 >> > >> > so,eventually,I can use the Lima and the PanFrost driver even for my >> > samsung galaxy A6 ? I've started planning to install FreeBSD on top of >> the >> > Android Kernel,using a specific patch,but now I'm thinking that maybe,= I >> can >> > install FreeBSD there natively. Can someone tell me if it is >> doable,giving >> > a look at the specs of that phone model ? thanks. >> > >> >> Based on my experience with Samsung it probably won't be a simple task. >> >> Samsung tends to block the bootloader such that it's very difficult to >> install anything but Android. >> >> https://www.xda-developers.com/ has a fair amount of info on the A6. It >> could be worth your while to take a look at what's there. >> >> -- >> Gary Jennejohn >> > > > -- > Mario. > --=20 Mario. --000000000000dbdf9f05fcedb014 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

What I would like to know is if I can insta= ll Linux as the main OS,instead of Android. Thanks.


On Tue, May 30, 2023 at 8:31=E2=80=AFPM Mario Marietto <marietto2008@gmail.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">
My i= dea is to patch the kernel with this patch :


= in the worst case scenario, I will virtualize FreeBSD with qemu + kvm on to= p of Android.

On Tue, May 30, 2023 at 8:20=E2=80=AFPM Gary Jennej= ohn <garyj@gmx.de&= gt; wrote:
On Tu= e, 30 May 2023 15:02:38 +0200
Mario Marietto <marietto2008@gmail.com> wrote:

> That's interesting. As I have already said,I haven't bought th= e pinephone
> pro,because it is expensive for me. So I'm working on a parallel p= roject.
> I've bought this phone,instead :
>
> https://www.hdblog.it/schede-tecn= iche/samsung-galaxy-a6_i3655/
>
> That's cheaper. Between the specs I read that it has a mali gpu,to= o :
> Mali-T830MP2
>
> so,eventually,I can use the Lima and the PanFrost driver even for my > samsung galaxy A6 ? I've started planning to install FreeBSD on to= p of the
> Android Kernel,using a specific patch,but now I'm thinking that ma= ybe,I can
> install FreeBSD there natively. Can someone tell me if it is doable,gi= ving
> a look at the specs of that phone model ? thanks.
>

Based on my experience with Samsung it probably won't be a simple task.=

Samsung tends to block the bootloader such that it's very difficult to<= br> install anything but Android.

https://www.xda-developers.com/ has a fair amount of info on the = A6.=C2=A0 It
could be worth your while to take a look at what's there.

--
Gary Jennejohn


--
Mario.


--
Mario.
--000000000000dbdf9f05fcedb014-- From nobody Tue May 30 19:11:03 2023 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 4QW26y1tTnz4Y1Cm for ; Tue, 30 May 2023 19:11:06 +0000 (UTC) (envelope-from des@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 4QW26y1SmZz45Sx; Tue, 30 May 2023 19:11:06 +0000 (UTC) (envelope-from des@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685473866; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=F626/rP8ysjs0biA/zcFRCBJmkD0SS8/r/Fv53DOR7w=; b=SMCK11rJesgwG+WbxgdbATHkD8tHTm12yMi+tFjTeq3NToh+unzDyZKU2HBRibZ6SxDMTi oi9ya2LfKAeLKQUujPwddRJvO27Te57rw2vA7P9qyWnpToe3H58+N0fnLWHIihur0dTC62 /XqMrgSK2gC9dY3dHm99HrA3DPqDbMv1zueIdQ1KNgau29XWin+Hw5PEWfgh9CmscQWn2u 0+K+RWec5nJJU5bZvuQw0JG/gsJVJ10BPG5JBTZpv3iE1Y+wnWaYECKy+41eaSeGHu2p/L /cFLuir51+iDCoGTjvXOTgtXmoEa4Mz0Be9Zb5GIzj9JdCXNNU7pb3pByRI3dQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685473866; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=F626/rP8ysjs0biA/zcFRCBJmkD0SS8/r/Fv53DOR7w=; b=wPqkA4EP9lI87//rj+VekMWCaX3RIpLIN12rKpnRUZ8uQm123kLGvdj5+r2x/LNVOlhPG+ yGd8RGEUSNQ7/REzPW4Q+KMDNkgD/+ccc//Bvoo2CRimvUBBg/49Zwrfv1FldJTP0iy58m CGbW3OagTsn2FQR45p0kCVE0ItQ8BRCcksz52/xU9GIlmpFWNo2SYv2o6VxGaTFjuNGdzG 4cwZwCta0EweN1ms9AHfZSvPu+3vzxwbo+JnffrETfWJpyd3vD51AA0eE6gJKvoDdourt/ WWKmJfY9h9W57ePWg48GUKtKwTgwAehEoXsJ36I3RsRzlktnVQvPzJG1V7eWcg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1685473866; a=rsa-sha256; cv=none; b=fAdJAfvjq//dAgLwD/MRdysN7FghsPUqriu2NoYoFct9nfk/hr1bN7gmj7sSy0fq2sEBFb 5XcvV6VrF49ddR+wcV2cPLq5nkOp8rttNwbVb+HGzkMxqEcINpY1aGeU00j3OdDZkYihq3 gQ0u2m4IV1lNA7EH+mLE+8AagCr/tunMM6cq8nj9Pqug1BWcXxWA0Z36kHufFDVJ5MXuQt cJe/doEfTUVMAnb20+feuLw5Gc03JlQc0BYd4uUu/cH5Bs4Yq4CHGELE8q3JT/8jhpbyrz gLXKGVQtpvpx0Lz7OBvHcHcmXiT9r19Mit8xDjZHq86UPzqearsPOqnPEsdoow== Received: from ltc.des.no (2a02-8428-0993-f001-36e8-94ff-feca-9834.rev.sfr.net [IPv6:2a02:8428:993:f001:36e8:94ff:feca:9834]) (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) (Authenticated sender: des) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QW26x6f2lzltg; Tue, 30 May 2023 19:11:05 +0000 (UTC) (envelope-from des@freebsd.org) Received: by ltc.des.no (Postfix, from userid 1001) id E77B8E059D; Tue, 30 May 2023 21:11:03 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: David Chisnall Cc: Mike Karels , bob prohaska , freebsd-current@freebsd.org Subject: Re: Surprise null root password In-Reply-To: <850FF076-A511-4802-8D7C-2029752C3345@FreeBSD.org> (David Chisnall's message of "Sat, 27 May 2023 10:39:12 +0100") References: <850FF076-A511-4802-8D7C-2029752C3345@FreeBSD.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (berkeley-unix) Date: Tue, 30 May 2023 21:11:03 +0200 Message-ID: <86sfbdk52w.fsf@ltc.des.no> 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 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-ThisMailContainsUnwantedMimeParts: N David Chisnall writes: > There was a very nasty POLA violation a release or two ago. OpenSSH > defaults to disallowing empty passwords and so having a null password > was a convenient way of allowing people to su or locally log into that > user but disallowing ssh. This option does not work in recent > versions of FreeBSD. Turning on the option to permit root login while > keeping the root password blank used to be (mostly) safe because it > permitted su to root from people in the wheel group, root login via > SSH key remotely (for =E2=80=98everything is broken I can=E2=80=99t log i= n as a user > whose home directory is not on the root filesystem=E2=80=99 recovery) and > local login as root from consoles marked as secure. It now permits > root login from the network with a blank password. That is incorrect. PermitRootLogin defaults to =E2=80=9Cno=E2=80=9D in Fre= eBSD and to =E2=80=9Cprohibit-password=E2=80=9D upstream (and presumably in the port), = while PermitEmptyPasswords defaults to =E2=80=9Cno=E2=80=9D both in FreeBSD and u= pstream, cf. crypto/openssh/servconf.c (search for =E2=80=9Cpermit_root=E2=80=9D and =E2=80=9Cpermit_empty=E2=80=9D). DES --=20 Dag-Erling Sm=C3=B8rgrav - des@FreeBSD.org From nobody Tue May 30 19:36:47 2023 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 4QW2hv6m1kz4Y38C for ; Tue, 30 May 2023 19:37:03 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (plan-b.pwste.edu.pl [IPv6:2001:678:618::40]) (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 (2048 bits) client-digest SHA256) (Client CN "plan-b.pwste.edu.pl", Issuer "GEANT OV RSA CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QW2ht2cHDz4Cs1 for ; Tue, 30 May 2023 19:37:02 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=plan-b.pwste.edu.pl header.s=plan-b-mailer header.b=oOv7W6Vw; spf=none (mx1.freebsd.org: domain of zarychtam@plan-b.pwste.edu.pl has no SPF policy when checking 2001:678:618::40) smtp.mailfrom=zarychtam@plan-b.pwste.edu.pl; dmarc=pass (policy=none) header.from=plan-b.pwste.edu.pl Received: from [IPV6:2a02:22e0:cf00:1ff:85d3:3a8c:2653:140e] (mzar@[IPv6:2a02:22e0:cf00:1ff:85d3:3a8c:2653:140e]) (authenticated bits=0) by plan-b.pwste.edu.pl (8.17.1/8.17.1) with ESMTPSA id 34UJanBh009316 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO) for ; Tue, 30 May 2023 21:36:49 +0200 (CEST) (envelope-from zarychtam@plan-b.pwste.edu.pl) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=plan-b.pwste.edu.pl; s=plan-b-mailer; t=1685475412; bh=nfxGPZdN67wZrrRWKuqCBy5FM9pWUN9/3BCcMkBROMk=; h=Date:Subject:To:References:From:In-Reply-To; b=oOv7W6VwLTrKThWObmaGZLihb2EEV0T9FqwU85QZ05jwoZIg44fN5CzHZfTf8ock2 OwrZ5m/Na8dEVLADBMjveBspkD44Y4lZYf9eck2kBZC87aborym5JQAw5wG8scpfrN MbXYqw6iZ0cEEAcoopZGKwH32U6upNCjTYTb1sQEGOABOGWYbaSQs6qes1gn4/jluz p/Mu4EMxQKT83/gEcDWX3D03G011uCP/Ok1Ik4AqpQ7kPPyDu5MjPmnZIMKBpvmEDf /qDDSsqqE0232sig0FFCISGMFZOqc7IFHkkTZxQ6wyalt+3esyvOcuea6h4yMAB/6v TGY/0ePcAnw4Q== Message-ID: <83f96e4b-7f27-a34c-0c0a-5e348e3b28d1@plan-b.pwste.edu.pl> Date: Tue, 30 May 2023 21:36:47 +0200 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 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: Surprise null root password Content-Language: en-US To: freebsd-current@freebsd.org References: From: Marek Zarychta In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-3.79 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-0.99)[-0.995]; DMARC_POLICY_ALLOW(-0.50)[plan-b.pwste.edu.pl,none]; R_DKIM_ALLOW(-0.20)[plan-b.pwste.edu.pl:s=plan-b-mailer]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_SPF_NA(0.00)[no SPF record]; ASN(0.00)[asn:206006, ipnet:2001:678:618::/48, country:PL]; MIME_TRACE(0.00)[0:+]; DKIM_TRACE(0.00)[plan-b.pwste.edu.pl:+]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4QW2ht2cHDz4Cs1 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N W dniu 26.05.2023 o 19:35, bob prohaska pisze: > While going through normal security email from a Pi2 > running -current I was disturbed to find: > > Checking for passwordless accounts: > root::0:0::0:0:Charlie &:/root:/bin/sh This thread reminded me of another issue with passwords I encountered a few years ago. Setting stronger passwords by users can be enforced by pam_passwdqc(8). But if the password expiration policy is enabled, it doesn't work since the password change for expired passwords is called by ssh or login PAM module, thus to enforce stronger passwords for users with passwords expired pam_passwdqc should be added also to both: /etc/pam.d/{login,sshd}, otherwise user with an expired password just presses return twice during the login prompt and has an empty password set. I even have risen D27656 some time ago, but it had gained not much interest except for some rephrasing/grammar advice. So to use a password expiration policy and enforce high-quality passwords together, pam_passwdqc(8) has to activated in the three:  /etc/pam.d/{login,passwd,sshd}. Cheers -- Marek Zarychta From nobody Tue May 30 23:07:42 2023 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 4QW7N42y1wz4YKB9 for ; Tue, 30 May 2023 23:07:48 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QW7N32j9Kz3Nm7; Tue, 30 May 2023 23:07:47 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=mY636qKi; spf=pass (mx1.freebsd.org: domain of yaneurabeya@gmail.com designates 2607:f8b0:4864:20::102f as permitted sender) smtp.mailfrom=yaneurabeya@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-pj1-x102f.google.com with SMTP id 98e67ed59e1d1-256cda5c1c1so743097a91.1; Tue, 30 May 2023 16:07:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685488065; x=1688080065; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Z0iBtU9Wq54/CiRbpDHe5vyJ4zn9/PI5iglaf19R+3Y=; b=mY636qKiwdtHaVIvd0aQWU9hQLfiGNrpDo2jZZpP+SiS3YRchB4TB4+pHi67uFyOJj jlKbzIpqpFTjN7VsgiCnbF6OOt6tvmTKjkhC3f11xTMmSIia5m4HrVoCedjhRgyVTy9w 0Rs4TOSwLiplcoMQyvLnwDX4UzOODoyVWmckB8mog85a2MynCreSQlfJDcxZ7HwQZXvL gw1jGjCfayZSXRaOmVqMtKndua91adfvpIWPbnw3B4PBEKssh9tHPuYOmA0n1dxufMwY GZiDj04VUcI7tMGZWkuZ3RSh4avGobxJTqbwxqDqcyLjQQ+G/1wjQR5zvnAeO+sbvhs9 xYlQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685488065; x=1688080065; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Z0iBtU9Wq54/CiRbpDHe5vyJ4zn9/PI5iglaf19R+3Y=; b=BoSch1KDXJMZO1EdDQ+8rp3Qp24IrmVrqmEOlJVglkdQ5WU28/X6F0GuhXLtxjmO41 ovJ44yhwQmLLuQKeKWDZJpekmN9+fdyicdhGSZy9QwqVgBH6kgT4uiZkz8ucUOeLq42H 7/tbYXWsjJ0qjwII3fAeuWYIQsc7erV6AOyXg1LO6R4ht6Wksve4xB635N69YgNh7XLj owJCr0D3FLHAdWNnD6PXhQVFxCZGLaUmF9EBVdRae6dJSQO4DOglxSIVF3LcwKAjc3XK 09mtpykyo8xZ97ynn8fjL76sOLcAF1ztq35kSQnwr8oKBAlnbQHZTuXf0EWMWaKTkTYX JihQ== X-Gm-Message-State: AC+VfDy56FokZNepQqfw2BaaLPoQdnXUcRKpem0lR2bRfRjsw9MsnHBS R3veuv7FtkpR7rIOjH5SYM95glR8/HH1Ww== X-Google-Smtp-Source: ACHHUZ6Ba7unYOCeHxLviEwgjHAYfMvi2ikjITStdf9XxWPbKMO+sjj1Di4e1FrpY3SL+sTye8yZHg== X-Received: by 2002:a17:90a:b895:b0:256:2b45:8e1a with SMTP id o21-20020a17090ab89500b002562b458e1amr3983363pjr.25.1685488064410; Tue, 30 May 2023 16:07:44 -0700 (PDT) Received: from smtpclient.apple (c-73-19-52-228.hsd1.wa.comcast.net. [73.19.52.228]) by smtp.gmail.com with ESMTPSA id i16-20020a17090adc1000b00256799877ffsm4294335pjv.47.2023.05.30.16.07.43 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 May 2023 16:07:43 -0700 (PDT) Content-Type: multipart/signed; boundary="Apple-Mail=_CDECEF28-D00E-4847-8D23-755F608C0AA7"; protocol="application/pgp-signature"; micalg=pgp-sha256 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.120.41.1.3\)) Subject: Re: "make hierarchy" from main tree breaks c++ headers on older branches with unclear errors if "make install world" is interrupted From: Enji Cooper In-Reply-To: <0DA92266-62F8-439E-9C56-44106A6B0073@FreeBSD.org> Date: Tue, 30 May 2023 16:07:42 -0700 Cc: FreeBSD Current Message-Id: References: <0DA92266-62F8-439E-9C56-44106A6B0073@FreeBSD.org> To: Dimitry Andric X-Mailer: Apple Mail (2.3696.120.41.1.3) X-Spamd-Result: default: False [-4.59 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MV_CASE(0.50)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; NEURAL_SPAM_SHORT(0.01)[0.009]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FROM_HAS_DN(0.00)[]; BLOCKLISTDE_FAIL(0.00)[73.19.52.228:server fail,2607:f8b0:4864:20::102f:server fail]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::102f:from]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; HAS_ATTACHMENT(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org] X-Rspamd-Queue-Id: 4QW7N32j9Kz3Nm7 X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_CDECEF28-D00E-4847-8D23-755F608C0AA7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On May 28, 2023, at 3:53 AM, Dimitry Andric wrote: >=20 > On 28 May 2023, at 07:18, Enji Cooper wrote: >>=20 >> I just tried to run =E2=80=9Cmake hierarchy=E2=80=9D from a main tree = on a 13.2-RELEASE system, and doing so completely broke my headers. >> It took me about 30 minutes to figure out what happened=E2=80=A6 = /usr/include/c++/v1/__string was a header, whereas on :main it=E2=80=99s = a directory?! >=20 > Yes, upstream libc++ has split up large headers into multiple = components, in particular __string and __type_traits. >=20 > Since we had a file named __string, it had to be somehow replaced by a = directory. This is what the distrib-cleanup target in the top-level = Makefile does: >=20 > https://github.com/DimitryAndric/freebsd-src/commit/6b13b4a095e3 >=20 > Afterwards, the replacement directory named __string is created as = part of the regular mtree commands. >=20 >=20 > ... >> I reinstalled the headers by going to lib/libc++ in my releng/13.2 = tree, building, and installing all of the 13.2-RELEASE headers. >> This change has been live for almost a year now on :main =E2=80=94 is = this a known caveat when doing a source-based upgrade from 13.2-RELEASE* = to 14.0-CURRENT, i.e., that the installworld (if interrupted) could = break the c++ compiler? >=20 > I think it should already be quite clear that interrupting = installworld is risky. If you were just in the middle of replacing libc = or rtld, and those were half-written, your system will be completely = hosed. (I am speaking from experience. :) The same goes for any system = headers or libraries, not only the C++ ones. If you have a = half-installed tree, it should not be used for anything except = attempting another installworld. That=E2=80=99s a fair point, however, given that this follows the = standard installation workflow=E2=80=A6 1. etcupdate pre-run. 2. install kernel 3. reboot 4. make installworld 5. etcupdate post-run =E2=80=A6 this could surprise end-users. In particular, the C++ compiler = will be broken between step 1 and step 4. It would be good to bring this fact up in UPDATING or RELNOTES as a = warning because it could result in a broken system that=E2=80=99s = difficult to recover from. Cheers, -Enji --Apple-Mail=_CDECEF28-D00E-4847-8D23-755F608C0AA7 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEtvtxN6kOllEF3nmX5JFNMZeDGN4FAmR2gb4ACgkQ5JFNMZeD GN6YnQ/+L3uTxKy4u7jOtZB8KoPi4wYCwUPVxp0j0vH7KcfPOoVl9o8QulDJ30DC shIR36AVqaywHE8RghIhiJ8TtSXr+/8feDAPMNPDlqkpAaLLEu/t/QjVDxlWBOeA 2Y9SIkN+a3MEW5O9NMVbXTktZgU14S9xFt+KzUITqvQLRI3XI23QslyVvksW1Lfo rzyMsKjtUN8f4l2XiTDDoVJl6TUDFkBDPDcSeIz3mgqfkrbVLhSXZG1g8rBa7MfM bU8mHawLQsjdPBfYzG5UFdeWZwMCWojlYPGwBUilzCYvt2571kcG3pdOvvnDAGDY utEvQTvUdNAEqMWqHiKP+B1AJW/zJze1VZrmGDcT+X3HjryIkATYnxauLMvQnonv FGdcdjZp/8SxwVWOS/S4QxLeRPgqtzy9jbJtpMqu0L/pGk2Tph3UKTbQH9CUzp1d MkMvrC8uA/oYWDXUqlF79Z4sSDa33rom2l+a4W51WK4HKLhIptLLaKzcyuhThEY1 5KHl2CYGVxah6XUry9kVnsGb/ZpQFkV1fafqfJhvJ+NFdeLUMc+QsSkXvBGfatI1 cpaBhUMMW7GEuwt9awlwIOazXoIf0Fu7CRVtnNrZO3HCbwfRAMeyOSpjMEbTgWs9 hNmaQI3YdK4bZyjjllXCbyHHtpjCyW6xcjSJyYYZAFA4lgCRu9E= =Zzqs -----END PGP SIGNATURE----- --Apple-Mail=_CDECEF28-D00E-4847-8D23-755F608C0AA7-- From nobody Wed May 31 01:39:11 2023 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 4QWBkY1LTmz4XWqK for ; Wed, 31 May 2023 01:39:01 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWBkX4HgLz3tQ1 for ; Wed, 31 May 2023 01:39:00 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 34V1dBYx047770 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 30 May 2023 18:39:12 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 34V1dBwP047769; Tue, 30 May 2023 18:39:11 -0700 (PDT) (envelope-from fbsd) Date: Tue, 30 May 2023 18:39:11 -0700 From: bob prohaska To: Mark Millard Cc: Current FreeBSD Subject: Re: Surprise null root password Message-ID: References: <8721FE04-3769-473C-BAAD-EB0A4FCFA1D7.ref@yahoo.com> <8721FE04-3769-473C-BAAD-EB0A4FCFA1D7@yahoo.com> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8721FE04-3769-473C-BAAD-EB0A4FCFA1D7@yahoo.com> X-Rspamd-Queue-Id: 4QWBkX4HgLz3tQ1 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Tue, May 30, 2023 at 11:02:13AM -0700, Mark Millard wrote: > bob prohaska wrote on > Date: Tue, 30 May 2023 15:36:21 UTC : > > > On Tue, May 30, 2023 at 08:41:33AM +0200, Alexander Leidinger wrote: > > > > > > Quoting bob prohaska (from Fri, 26 May 2023 16:26:06 > > > -0700): > > > > > > > On Fri, May 26, 2023 at 10:55:49PM +0200, Yuri wrote: > > > > > > > > > > The question is how you update the configuration files, > > > > > mergemaster/etcupdate/something else? > > > > > > > > > > > > > Via etcupdate after installworld. In the event the system > > > > requests manual intervention I accept "theirs all". It seems > > > > odd if that can null a root password. > > > > > > > > Still, it does seem an outside possibility. I could see it adding > > > > system users, but messing with root's existing password seems a > > > > bit unexpected. > > > > > > As you are posting to -current@, I expect you to report this issue about > > > 14-current systems. As such: there was a "recent" change (2021-10-20) to the > > > root entry to change the shell. > > > https://cgit.freebsd.org/src/commit/etc/master.passwd?id=d410b585b6f00a26c2de7724d6576a3ea7d548b7 > > > > > > By blindly accepting all changes, this has reset the PW to the default > > > setting (empty). > > > > So it's a line-by-line merge. That's the most sensible explanation available. > > > > > > > > I suggest to review changes ("df" instead of "tf" in etcupdate) to at least > > > those files which you know you have modified, including the password/group > > > stuff. After that you can decide if the diff which is shown with "df" can be > > > applied ("tf"), or if you want to keep the old version ("mf"), or if you > > > want to modify the current file ("e", with both versions present in the file > > > so that you can copy/paste between the different versions and keep what you > > > need). > > > > > > > The key sequences required to copy and paste between files in the edit screen > > were elusive. Probably it was thought self-evident, but not for me. I last tried > > it long ago, via mergemaster. Is there is a guide to commands for merging files > > using /etcupdate? Is it in the vi man page? I couldn't find it. > > # man etcpudate > . . . > CONFIG FILE > The etcupdate utility can also be configured by setting variables in an > optional configuration file named /etc/etcupdate.conf. Note that command > line options override settings in the configuration file. The > configuration file is executed by sh(1), so it uses that syntax to set > configuration variables. The following variables can be set: > > . . . > > EDITOR Specify a program to edit merge conflicts. > . . . > ENVIRONMENT > The etcupdate utility uses the program identified in the EDITOR > environment variable to edit merge conflicts. If EDITOR is not set, > vi(1) is used as the default editor. > > > > So, if you do not want to use vi, you can use either the EDITOR > environment variable or an EDITOR assignment in > /etc/etcupdate.conf to change what editor etcupdate uses for > you to edit merge conflicts with. My difficulty is precisely a lack of skill with vi, which I've used and cursed since starting with 386BSD. Evidently I'm a slow learner.... I tried other editors, but vi is the only one always available. For the moment, etcupgrade isn't asking for manual intervention. When it next does I'll pay closer attention and ask better questions. Thanks to you in particular and everybody else who has helped! bob prohaska From nobody Wed May 31 03:05:49 2023 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 4QWDg15R86z4Xf9G for ; Wed, 31 May 2023 03:06:05 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic306-21.consmr.mail.gq1.yahoo.com (sonic306-21.consmr.mail.gq1.yahoo.com [98.137.68.84]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 4QWDg12y3sz42Lp for ; Wed, 31 May 2023 03:06:05 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1685502363; bh=QnSGc60KHMQQ2Ugn4CHGguWaeKsH16+e0NKbBmwGuHw=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=ZrUe/EIdpNJoIO2a2kPurx3Tb5lb7MGclHG1ekcLfe6cj6Mx8tWNoO62NeTOMt+zYXAE2SI/bFjlIlc9EKtA89gfDLqad9a3Vm2SmgZEDkoLxt6isB1WK9V94DPUIzJB7PZUT4BeQOZvBCgIdAPR8J3IljvvImRup8bA3Yapvfv2gOA+X2iTq0UXyLhoYyzffJdH7zCgMcSSZoHTjjb0D2aOBm0hld8vzHAc8f54OhlGnbYJWQZAG91Ff5geZqpiiWC+6bcqKsXpYOnVXpcWefSZMUe3+l/4YOgyOiCA0nLoFuGRi8PNtrgwnUvdxd7HmKPVlxWnn0a6oScpyQT3mw== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1685502363; bh=10xf/ZYe8CdbrmoZElEbmWX0eXK3J5i/kxHaVc03nBF=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=n28draZgG3tobT54ekf99u18xRFsDZ+yfcIjAiXJc/fE5Z10XW2BMUmqOJBQ2JqVLj5QCn0MR1o3vyCfeqX9Zw4bz0Qd6b4ShMzGFuYtN1aWgPNf01gYGyZr+YlMZ+vjfdrNFDlowoamEe6EOq0qsq4nS+KtUlfTUn1V4zygNmBwWcMOAclMaBTuqIaHpR9fEFXby9FNLR2vLNiG4Ecz1L3kCXUMMeXv6b53c8jQ97BOBo4ijYKKRKEC391ZmAsxjv7eLzUkXLP46nQyiKYswFu4DDdraLG48l/ZkEbDg59j6rK21hvUw6eXOYevuy4s7Q93HbdonFvwOScDWYw93g== X-YMail-OSG: bJXX5YYVM1nFf1btlWew9Tr6pL2XFKip9BuwPv0_NpmWyQ76d5BrluroQKNQflQ HVuINStLA9m_UGHUk4Q4ZMvTcBr1AksFkd7uD5zxi_F4uDPlETU.RzLG2vjRJIkK7RGMH6Jgwxvn lAIJCZ_ijI5d06dmha8wRzWHaBXg7w6FeNLh2v7.X2EvbwiBvbBWreXUhVpywFYC6VIYUQepjXEc DN9Cv.5F3eYOCNnCNo_bWZ3RRs2vUkzgDLk.abnbMemNZzx..9jtRVWVbsJLlBmfX2cHZog17kaP kTFGwp7qy_XXt19uAEnjPqRe1UJS5Eo3K5HhMXd0onNPIAv4ze_G7kBdTmJjCyIU7VBtv4vLi53g inQnzYkfVDVeDKC2zNAxFmRXqwFXBbtoDU9HJzITIiZipjgwmmB2jwKUqOV0DvSb1DmcXesuubou YdLlEw_JcsRyBVMFbnSFSAtDeWPoMWqIEXqFm2w0H_hSewYCuBl2pB15ntF7AIpYO2gRFiMNUo6d vOjm6Zxp.hBFe0UzKbqjnP8rJA3CEMfLt758x1UU.k5xZH5JAYTv3HrhtPD1v9714OXXSp9exBxo Xu.wIGwfSNNNbCbzX1duVTkdZ4EOVfAb_2pJFClu50l_Mkh99GXhiA4HuuGNf8lr_qWyvlVSnixy 7sy2hpg9I2AqhygW8xepU5U_lrIyOBymxGUe4hWGb2AihJ1hbbd43uTwoxDxLIRV5WuaJuaznQn2 i3meUYhIieLVeyrX0JMNbQ1fRiyGEDU_7TB8l6ZpEZOYNbSb7ZCyBD1QSwbM_.PDzFA6dwpp7k8l iY3t7nGBLmLV8XqWZgc_4sy.fg41bjxScJx7hFXiHpCExY3jfUkdOOFcfbvXE3YD22IuEWLIyEfk U3_hfqzU4NR2CcDWTCThlf_faHVFCK4.tSwI0ap0wsjz6aEu4xq04dR4gOLjFW743UEXxSZWwF36 X1K84.PICPAu1km.i1lWNzQFHb8u5nX1..CTSZOrcRi2JD6jGRosfeRytlVkEhmzEL_ZtdRlsN0H bBsRXFHy7jJsIRKSa.VIlaew_dpsFnW1bJBVDSZi1fL_42h5FBv4GaXwM.n2Ou.QaDGHmkHxQN4_ BKtvimIBiMj_1_TbvhRvS5.t.AqBkV.1n5VwyKmdUQCDZQUjHLk2mYv5dIKl9tgVg4b2rL5guoF3 _URtxyzlmcPoB.E_IMD4bgTfgHyi2lhLb8MoNq.SLGdTnnCUbN.FgxqwneptJl1lO4yJ10tpJzfx TnrU1Sl_P0v7PDKEX9GD.pMLmtoq8YIcqpMFixX0TGj2vFHY.YaqJ1ZF0PAL8TTIJHAvPFLBhNv. fsD33Ed.AUfW2JyzYPwIoMG7_Orr_eFcL6Xj8W68tH9azDr2.Jcx9yXQjdEiYGwfyeQKCNnSO9cL JaNuD_1q6SxLQ_xIsbP0aQhW4zMIiuSa2YkZXyClGXj.PdOS2k6ssFtFB1yGoiq0BrDqN9hcv71n OcMzIHgtmaquh.sr5qqqufxxFOnqQBhvx7frO36IKZnL5GOSAXzB84EOg1DXfL7iIuJuqLVsdyhV lpWj6H_x8A.VsX9Z91tG2rwFydRMbIB8vTKxqpt5O4F8t0iWMHT2TizC6iGb9kiZ2HwRixH_bTIW qTyQ6OfIJ2fScEBmkSfTl8MilYtNUljiB9AMrbg.ky_vP6mL_Ng3kV59dTdgRX0QIQVWbZ.rfJDn 3x2fTcdjjm2j8jBdBRVrnyoBbSmXz9NNPlmP1TcLQ2TBC0Ma1bxbL8UVNZ_VLRpbeZGSQ.hVgGy8 To0ufsbI.LeRaj5kopizM94Z2vmUew1H16r66XB.nBubTfqwiwrOuQVXDfLQLhVRuCuRvLOein9h 2AVCu3RoXECbtF1hLb516rBBX9F8Cl1M.rGfFPlM7W.aqm35jpFJ2hn94zygjtMGoUFLo96cIrc3 dn8OU70xPnk6VFVRlKnm.3l6BXdDfvVGZPUmCceo_mrOP88LtMCdyx291tVAQUjr0HWnpim6ThRX xV4OgYTEc2LlvCnG3B.gXdi3KzEM75E5ftj2AlQfdiNbdNgeq8H.N3VP9VNAj0Pjzc1stlqm52rO YTLFipqhLWt8nk7FdSijZ9iTwTrfDdINFIUrA4Q5owIinQYAtaEcO0aXasnilr01DiEZulUUD31e dhOTjFXaVTYSvKtfxEbIRQ_a_i0ZpxyR9bN9YfpBYVqsh62Y3TGLGNo5ndKmQ7x6k1uH8uOrlUji fcKFOKmbehuCqmgUAE1QJEESUpkti_I_.wIsWW2TDgl2.Uk3fFIEpTY4BE7vWBZEchbgtmAYoU_g - X-Sonic-MF: X-Sonic-ID: c8ab3422-7b4f-4c5b-b31a-d1c460177e8c Received: from sonic.gate.mail.ne1.yahoo.com by sonic306.consmr.mail.gq1.yahoo.com with HTTP; Wed, 31 May 2023 03:06:03 +0000 Received: by hermes--production-gq1-6db989bfb-66nkp (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID bddc827ba3d2fd7cc147709a7573a904; Wed, 31 May 2023 03:06:00 +0000 (UTC) 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 \(3731.400.51.1.1\)) Subject: Re: Surprise null root password From: Mark Millard In-Reply-To: Date: Tue, 30 May 2023 20:05:49 -0700 Cc: Current FreeBSD Content-Transfer-Encoding: quoted-printable Message-Id: References: <8721FE04-3769-473C-BAAD-EB0A4FCFA1D7.ref@yahoo.com> <8721FE04-3769-473C-BAAD-EB0A4FCFA1D7@yahoo.com> To: bob prohaska X-Mailer: Apple Mail (2.3731.400.51.1.1) X-Rspamd-Queue-Id: 4QWDg12y3sz42Lp X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On May 30, 2023, at 18:39, bob prohaska wrote: > On Tue, May 30, 2023 at 11:02:13AM -0700, Mark Millard wrote: >> bob prohaska wrote on >> Date: Tue, 30 May 2023 15:36:21 UTC : >>=20 >>> On Tue, May 30, 2023 at 08:41:33AM +0200, Alexander Leidinger wrote: >>>>=20 >>>> Quoting bob prohaska (from Fri, 26 May 2023 = 16:26:06 >>>> -0700): >>>>=20 >>>>> On Fri, May 26, 2023 at 10:55:49PM +0200, Yuri wrote: >>>>>>=20 >>>>>> The question is how you update the configuration files, >>>>>> mergemaster/etcupdate/something else? >>>>>>=20 >>>>>=20 >>>>> Via etcupdate after installworld. In the event the system >>>>> requests manual intervention I accept "theirs all". It seems >>>>> odd if that can null a root password. >>>>>=20 >>>>> Still, it does seem an outside possibility. I could see it adding >>>>> system users, but messing with root's existing password seems a >>>>> bit unexpected. >>>>=20 >>>> As you are posting to -current@, I expect you to report this issue = about >>>> 14-current systems. As such: there was a "recent" change = (2021-10-20) to the >>>> root entry to change the shell. >>>> = https://cgit.freebsd.org/src/commit/etc/master.passwd?id=3Dd410b585b6f00a2= 6c2de7724d6576a3ea7d548b7 >>>>=20 >>>> By blindly accepting all changes, this has reset the PW to the = default >>>> setting (empty). >>>=20 >>> So it's a line-by-line merge. That's the most sensible explanation = available. >>>=20 >>>>=20 >>>> I suggest to review changes ("df" instead of "tf" in etcupdate) to = at least >>>> those files which you know you have modified, including the = password/group >>>> stuff. After that you can decide if the diff which is shown with = "df" can be >>>> applied ("tf"), or if you want to keep the old version ("mf"), or = if you >>>> want to modify the current file ("e", with both versions present in = the file >>>> so that you can copy/paste between the different versions and keep = what you >>>> need). >>>>=20 >>>=20 >>> The key sequences required to copy and paste between files in the = edit screen >>> were elusive. Probably it was thought self-evident, but not for me. = I last tried=20 >>> it long ago, via mergemaster. Is there is a guide to commands for = merging files=20 >>> using /etcupdate? Is it in the vi man page? I couldn't find it. >>=20 >> # man etcpudate >> . . . >> CONFIG FILE >> The etcupdate utility can also be configured by setting variables = in an >> optional configuration file named /etc/etcupdate.conf. Note that = command >> line options override settings in the configuration file. The >> configuration file is executed by sh(1), so it uses that syntax = to set >> configuration variables. The following variables can be set: >>=20 >> . . . >>=20 >> EDITOR Specify a program to edit merge conflicts. >> . . . >> ENVIRONMENT >> The etcupdate utility uses the program identified in the EDITOR >> environment variable to edit merge conflicts. If EDITOR is not = set, >> vi(1) is used as the default editor. >>=20 >>=20 >>=20 >> So, if you do not want to use vi, you can use either the EDITOR >> environment variable or an EDITOR assignment in >> /etc/etcupdate.conf to change what editor etcupdate uses for >> you to edit merge conflicts with. >=20 > My difficulty is precisely a lack of skill with vi, which I've > used and cursed since starting with 386BSD. Evidently I'm a slow > learner.... I tried other editors, but vi is the only one always > available. =20 Well, there is ed ( and red ). But also built into FreeBSD is: ee ( and ree ). Beyond that you might have to install something. But if "always available" means across operating systems and built-in, instead of needing to be installed, it may be the most common for unixish contexts. But, as I understand, some Linux based OS's do not include (any variant of) vi, having things like, say, nano instead. Some variant of vi would be an install in such cases. I went something like 25 years between usage of vi and could do basic activity right off the bat. (Not that I was sure such would be true when I first had to edit via whatever editor I could find pre-installed at the time.) It is the only non-GUI editor for which such a thing has been true. Why it stuck so well, I do not know. An odd thing about this is that before the 25 year interval, my primary editor expertise was using TECO, including tailoring its interactive use. At this point, I only remember the name. > For the moment, etcupgrade isn't asking for manual intervention. > When it next does I'll pay closer attention and ask better questions. >=20 =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Wed May 31 06:00:21 2023 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 4QWJXy6hK4z4Y7S6 for ; Wed, 31 May 2023 06:01:06 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (mailgate.leidinger.net [IPv6:2a00:1828:2000:313::1:5]) (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 ECDSA (P-256) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWJXy3lXxz4K7f for ; Wed, 31 May 2023 06:01:06 +0000 (UTC) (envelope-from Alexander@leidinger.net) Authentication-Results: mx1.freebsd.org; none Date: Wed, 31 May 2023 08:00:21 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1685512854; 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=tP+tl6SCC/QFunueMh223ie1/WDStSIPSRcCoZ6I8Hw=; b=P1roDNWYBdx8YYqtyYPaDFPhToABUh6N4PS6FR64BLptAMjnu2dUevGm5I2W121sypTxnS 2ONp3BegOZEDvVJF/+iAku3ySqKvsOY30icGBYtMhcG3ESJDNCi45hTHzEg4ty9Fb4VvuW 2tHV0rkvL8H4Jp4h0GM1hJaSnDrds+Z3v5hj1mA3kQ8+sW1Ebf9vG6dScVR69j5qd+MYTm ABzig/QWyuBStWu55xIN7V41x8SVLYjz9V0cn8wVi2v3Sz9VkGrgLZlPGFMyUN0x5imiU+ tQAtA62MTJ46HA/lp5Xa9vFn7ZygialDwlexrg1063ad5L+BP97PFcI1TBKxiw== Message-ID: <20230531080021.Horde.4rhTtWEKR0KOgZ39bqdIoug@webmail.leidinger.net> From: Alexander Leidinger To: bob prohaska Cc: freebsd-current@freebsd.org Subject: Re: Surprise null root password References: <945C9B6D-F2A8-4F0D-BDB0-49A3DE870168@karels.net> <61e30711-f0da-2f42-3a6f-9bd91fc6b1ce@aetern.org> <20230530084133.Horde.4VevT2KY4XCtqoJgvP08jyB@webmail.leidinger.net> In-Reply-To: Accept-Language: de,en Content-Type: multipart/signed; boundary="=_qjSoY4OhUwOob3Tz1B3TtE_"; protocol="application/pgp-signature"; micalg=pgp-sha256 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 X-Rspamd-Queue-Id: 4QWJXy3lXxz4K7f X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:34240, ipnet:2a00:1828::/32, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N This message is in MIME format and has been PGP signed. --=_qjSoY4OhUwOob3Tz1B3TtE_ Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting bob prohaska (from Tue, 30 May 2023=20=20 08:36:21=20-0700): >> I suggest to review changes ("df" instead of "tf" in etcupdate) to at le= ast >> those files which you know you have modified, including the password/gro= up >> stuff. After that you can decide if the diff which is shown with "df" ca= n be >> applied ("tf"), or if you want to keep the old version ("mf"), or if you >> want to modify the current file ("e", with both versions present in the = file >> so that you can copy/paste between the different versions and keep what = you >> need). >> > > The key sequences required to copy and paste between files in the edit sc= reen > were elusive. Probably it was thought self-evident, but not for me.=20=20 >=20I last tried > it long ago, via mergemaster. Is there is a guide to commands for=20=20 >=20merging files > using /etcupdate? Is it in the vi man page? I couldn't find it. etcupdate respects the EDITOR env-variable. You can use any editor you=20= =20 like=20there. Typically I use the mouse to copy&paste myself and google every time I=20= =20 can't=20(https://linuxize.com/post/how-to-copy-cut-paste-in-vim/). Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_qjSoY4OhUwOob3Tz1B3TtE_ Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIzBAABCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmR24nQACgkQEg2wmwP4 2IZwBw/+Pz9Orf5fw8KtgtP/OYf1sDvolMuCao4GHQv4SWy2hbD4OJQGzcIyT+ju 0kWWIB/d1O0ribxhPx2nXOwtlQKhNbaMhFmcG22dKdifaJIL9dW7fMGPOg9UBhe5 LDk+l7ypu3qFRjOHyt+erWHmNpmGCwnxnykeJEfZRjHsGu6WwdX4r9A+GSIIDp+e Ji2uzsVq/MhbmAYVe3/z5pRc7cBWF+wv4RwN9uPlFJGZe9xPsuPPWBjpG93c/txv I4XLJ5K3KGtFziY7U3ASX1UIPVdoqsVtpQW3Odnye0JUQRYmDgdtB2gY8UYZYSvq uyhQIubwkiIxIyg02+5LQHZZEHW5qsp+83sZNEcXEuFCVUAlGdU7woQYeGyyDBHD 98LBaZn7lX1zL8ap99RJIH7q/ftQ/V9vUWHqr+/UTnmHkZnhE0jTCv07yyyf3MXv 41bSeMtqYO+ent/sOjApT22Zw1IwPLTko4x8w5FR7DoqyA94c9i8HLESpximfj9H YiICt7bOLOqZ2OL0uvRjXELcUpLudJ/2bzQQiy3bEWzRKiXTjXTnvI9IFEda5oRe UZW7HrkOxqDmYWH1cSYBmkoPDcS2meilC0RVb1uQfbQoIjnmiy/AYtDLQMkpcP9l vR/Ly2DdOJ0zU0e31lWWhA9UymZtf6+mVOUa7hL/CvkvSmO2e/M= =tha6 -----END PGP SIGNATURE----- --=_qjSoY4OhUwOob3Tz1B3TtE_-- From nobody Wed May 31 09:06:54 2023 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 4QWNgp5RS9z4YMlQ for ; Wed, 31 May 2023 09:07:18 +0000 (UTC) (envelope-from dim@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 4QWNgp4rNqz3RH0; Wed, 31 May 2023 09:07:18 +0000 (UTC) (envelope-from dim@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685524038; 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=UJE8h+xpt7XS1ew/ilSHMCU5ps5X5j1hL6+kwRTBk2A=; b=DxxMyMEi5n3H4udJtoWj5Gx96gWelqD73Jj4vZruUAAeJpgKOpqjQG+H3I692Rj66CM/h0 iRDllKKpmsztd4HGljCHfDoBGPq9VVI1gd9wQkcWGK7/qrlQYUOYT9Jcw50pECxiwOC168 n/MF9s+Ds52QzX4IbIUSqOdHAtChws5x4KovFt1HAoLQ4E9oDfW6frGMZ1TGvFh4+JgICP abxPqj1T7j1RlnTuA9IAWhvrXzLNm7nIKXLb7s1ij6RYa6XLzPD4F7iR4AOMGgPCr2l0/d 559Vg44pWFOu+qJzrgRrhKpa8PqAmZ7C71EqScbEAJzfszBTnoxnpmISaheG+Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685524038; 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=UJE8h+xpt7XS1ew/ilSHMCU5ps5X5j1hL6+kwRTBk2A=; b=Ehh53InBz0g782azmI1bsYMduDVeX02oHHCovra9c9n54QVkiUt8hu+zEeiBNmPeLjBffV 6YS53UWdVzYidycawn+xS4aERnXII1xd/eNj0HMhToBIy9Hnf0qSTouazV7SsCsYgIcuVf OEC5GKo0oeTwm8qRB8eiyNVSalNkP2hqZcH6pu5IRsB+Je/uddjdCK21dwvVkQOKxjEBLh PIkfEguR30kqdj+aaq1eMItaC0beKbgmh+VawSmIfdXwiIg36dzLbGaUYY2k8SJpODmOUE ckKkud7Ws5El39cbw/zM8nf4Gbe7AvoeuAEKXNJbqdzjZT1PmS6AKpIkILIEDw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1685524038; a=rsa-sha256; cv=none; b=jdEV6Rvw3QHFIKIQ2E+JEqyeKMY9eSj9QNV7Svp29RRHJSZYLcwVJ/I/ju2JkS7cPpuEHw Dw8zfUOiAl4PeA2S6Dlgpe1hjp+BiHMDNm6bLhIfbqBBwy2j1m72cCShDQmrleJpKsDMpD saNyjUYlEW4YhC3YEgzKX66akhcbdGZmakRuvnHd+Y4YxFuKDJ74NcNRMgo8xyizXYCYcZ LgWhg7nCv/ouTgOjRLROqeYpnim2miSgaBtq/MRSKwAzwRXBTw2Qa0D4Sxgyn3BImJuWg9 P/AgwfRd+NMthfTlk4/4QJ3FGqNQh+A75vt4f1eAmYUfypwTWUUeRCa/hY1qNg== Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (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 (2048 bits) client-digest SHA256) (Client CN "tensor.andric.com", Issuer "R3" (verified OK)) (Authenticated sender: dim) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QWNgp32ydz12W0; Wed, 31 May 2023 09:07:18 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from smtpclient.apple (92-111-45-100.static.v4.ziggozakelijk.nl [92.111.45.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id DCF644282C; Wed, 31 May 2023 11:07:16 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_4608D242-A0FB-4C83-BF73-C11493593DAA"; protocol="application/pgp-signature"; micalg=pgp-sha1 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 \(3731.600.7\)) Subject: Re: "make hierarchy" from main tree breaks c++ headers on older branches with unclear errors if "make install world" is interrupted From: Dimitry Andric In-Reply-To: Date: Wed, 31 May 2023 11:06:54 +0200 Cc: FreeBSD Current Message-Id: <8CD00413-E6B3-4DBA-8A71-CAFA647DF2FF@FreeBSD.org> References: <0DA92266-62F8-439E-9C56-44106A6B0073@FreeBSD.org> To: Enji Cooper X-Mailer: Apple Mail (2.3731.600.7) X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_4608D242-A0FB-4C83-BF73-C11493593DAA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On 31 May 2023, at 01:07, Enji Cooper wrote: >=20 >> On May 28, 2023, at 3:53 AM, Dimitry Andric wrote: >> On 28 May 2023, at 07:18, Enji Cooper wrote: >>>=20 >>> I just tried to run =E2=80=9Cmake hierarchy=E2=80=9D from a main = tree on a 13.2-RELEASE system, and doing so completely broke my headers. >>> It took me about 30 minutes to figure out what happened=E2=80=A6 = /usr/include/c++/v1/__string was a header, whereas on :main it=E2=80=99s = a directory?! >>=20 >> Yes, upstream libc++ has split up large headers into multiple = components, in particular __string and __type_traits. >>=20 >> Since we had a file named __string, it had to be somehow replaced by = a directory. This is what the distrib-cleanup target in the top-level = Makefile does: >>=20 >> https://github.com/DimitryAndric/freebsd-src/commit/6b13b4a095e3 >>=20 >> Afterwards, the replacement directory named __string is created as = part of the regular mtree commands. >>=20 >>=20 >> ... >>> I reinstalled the headers by going to lib/libc++ in my releng/13.2 = tree, building, and installing all of the 13.2-RELEASE headers. >>> This change has been live for almost a year now on :main =E2=80=94 = is this a known caveat when doing a source-based upgrade from = 13.2-RELEASE* to 14.0-CURRENT, i.e., that the installworld (if = interrupted) could break the c++ compiler? >>=20 >> I think it should already be quite clear that interrupting = installworld is risky. If you were just in the middle of replacing libc = or rtld, and those were half-written, your system will be completely = hosed. (I am speaking from experience. :) The same goes for any system = headers or libraries, not only the C++ ones. If you have a = half-installed tree, it should not be used for anything except = attempting another installworld. >=20 > That=E2=80=99s a fair point, however, given that this follows the = standard installation workflow=E2=80=A6 > 1. etcupdate pre-run. > 2. install kernel > 3. reboot > 4. make installworld > 5. etcupdate post-run > =E2=80=A6 this could surprise end-users. In particular, the C++ = compiler will be broken between step 1 and step 4. How so? The deletion of the old __string file is done as part of = installworld, i.e. in step 4, not in any of the earlier steps. The only = case where you can have problems is when you start installworld, let it = run until it has completed its distrib-cleanup target, and then = interrupt it before it can install the new headers. -Dimitry --Apple-Mail=_4608D242-A0FB-4C83-BF73-C11493593DAA Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCZHcOLgAKCRCwXqMKLiCW o5q1AJ0fT55YKDi0rZXKU1I/I+wJjp8Z7QCgkm+b/IZs0WPBSoXWNm4IcMpLsL4= =sBDQ -----END PGP SIGNATURE----- --Apple-Mail=_4608D242-A0FB-4C83-BF73-C11493593DAA-- From nobody Wed May 31 09:30:20 2023 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 4QWPBc3FlBz4YP5d for ; Wed, 31 May 2023 09:30:32 +0000 (UTC) (envelope-from garyj@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWPBb5tSBz3jgQ for ; Wed, 31 May 2023 09:30:31 +0000 (UTC) (envelope-from garyj@gmx.de) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1685525423; x=1686130223; i=garyj@gmx.de; bh=pJfoYsQVKDY3GiFwZkmMGmGTMBRzndGi/q0eMKWULPU=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:In-Reply-To:References:Reply- To; b=DKWeSlWwQiVIN850GHBiDnosJw8XRp22ZJSwrRaJLe03G+ZUqKMdxuzSmwW2Pwzj67n7fL4 v+C1XMuAbFiuYcDMRXEafjLXCJyCCzqKFytBpZmuV28gK72ZtK1b4BLkcRk5hihfn8Kh3XiuN Luk45A6xV9W1b9oKefFTxpIh5FMoev8+R31iC2fdDlh947rbqigJpXBkddfEGJeIvcUpZ2MOP EI5+hTMhXgz1ia7AZFrnsztcA+QLj3h5LOAU1NS/tz3F3d7bBMIyW7uPRApaVDjmIKcQTWE7+ zQhfbTp+uWVsS4LBGUk+x/agJ66+VoBgZAVnBQBKmiNAtjElR6pQ== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from ernst.home ([91.59.239.47]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1M2O2Q-1q4qv32cAQ-003vct; Wed, 31 May 2023 11:30:23 +0200 Date: Wed, 31 May 2023 09:30:20 +0000 From: Gary Jennejohn To: Mario Marietto Cc: Stephan Lichtenauer , Pete Wright , FreeBSD Current Subject: Re: PinePhone Pro Boots On CURRENT Message-ID: <20230531113020.51b6b3cf@ernst.home> In-Reply-To: References: <86leh6ggfx.fsf@pcf00001.honeyguide.net> <20230530202020.060be2bf@ernst.home> Reply-To: garyj@gmx.de X-Mailer: Claws Mail 3.19.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:1/lVfp1kPVqSU7MdDPPRLMNa+iA6wvXrz3jRakMpZ6t54RFphFe 30di03XrHQsMD/yXyjA0lsbAhNZoL+58CxTqUdsvM1xc29OTFyWJ1SpjZzDcuihgkVNPrIu cRcfesPvlu802+6iEinpC/DyULlMY9ClvdTjq9HHAcuzz1z6IdCKBnWU9Zcu2hX5CoWNHBS 7JFMo/5LO6seeVdM6jKdA== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:lX2OYiJNuX0=;EeFASsEAFn7zDWtl6ocH7Tofd25 fuchVNIFOd8mAeUHxhlti7KNAVV3kjLy2Kg++u3YvU6Jr/gyfdJx+XfUFejpPnLeSCqzN9Qqw DRW5loJlCIf50CVC31K386Kg0etk8zaR+NUw6fzCDvVR++OQy3e/W8Y2PwKki3KRffrWOkPzM 5Uonp9Ss7mQbJ0WP0QNZNyK5RX7c3juwLqcLzLCbFWC1UsU+gQjpGVGs4lp6M5QYlqI1iej/R ThHl0MelTMDWzfi5T+dB4Jccf9Uto2BvSoEj0dCfMC8RWs4yvU7qgpIOK+Y0y6DXr53KWEAkL btTdaecYIl+xglxbBHrCqOmS9Ef3EMtZu0aQewL2Rz8fVJj7BIre72QWI8shDs1VnE6pBRdmD zAMGkqhEzzvSExti3b2kMGyXSaHO6S2u6v4gAkpJ/9t8sGx7ARnj/2v6f9ITaJCOf4yv8SnFh Ylgalx+ZAz23S5Jj1I/MlVLqYXUCLdqtDlnUl4OyQ4henL8HKXCFVFh5vXZ22b44VDL0b5cEN h6TPsSPMuUwiUuq9MYdCEvT5WRoyRjhNrPrML/U1KJaqiXR3QKGpFkXMHDQAoQCeUqwslsluQ FFai0TYCOGLUrxiLYihEOoceeWCVn6NmW6an/61KTyNKyLl7FLHQp/4sZisgSORoWFvrSVw9B russgkq4/FQwP+bbNFn+RRtgUcEq8wqVWGVnfjfokH1+QgDV47RUXeXZz2DrGD/bHgxO8q5qD zAeQhxHs3UvmJ8tM6FEZzRUjww8JjFSCCg5y7zs/7+OHm+fTZq4TwfPd9lWz04F7e8NiiP4Qu BFX+sYlNIxKX0sXZECsnfnnfuniucb7HM87nz9uMoIgI03jzV3hNARH8vyLh3RHnaxNRihqzd 0BkTzRFeYyozWhSX6E22+qgpWCNpzG1z8QnodoDaXu0jjWtAJaVkKWyqZg1cxU0Ppou54fxsG x+B8xvZVG32Tw/o/r1o1EqKKuk4= X-Rspamd-Queue-Id: 4QWPBb5tSBz3jgQ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Tue, 30 May 2023 20:50:52 +0200 Mario Marietto wrote: > Check at this,also : https://github.com/raspiduino/a6lte-kvm/releases > This would definitely be the best approach, since the developer has alread= y tested Linux in the KVM. Odin, which I've used to install custom ROMs from xda, is a Windows progra= m. If you have Windows then this would be a way to do the installation. The developer also mentions using Heimdall under Linux. There's a Heimdal= l port for FreeBSD, so that might also be an option. > What I would like to know is if I can install Linux as the main OS,inste= ad > of Android. Thanks. > No, with this you cannot replace Android with Linux. This hack merely provides a way to run a different OS in a KVM. [SNIP] =2D- Gary Jennejohn From nobody Wed May 31 10:00:43 2023 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 4QWPtD05cFz4YR53 for ; Wed, 31 May 2023 10:01:24 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com [IPv6:2607:f8b0:4864:20::b35]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWPtC0yp4z3mVZ for ; Wed, 31 May 2023 10:01:23 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb35.google.com with SMTP id 3f1490d57ef6-bab8f66d3a2so7815067276.3 for ; Wed, 31 May 2023 03:01:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685527280; x=1688119280; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ZDDuIuyGJZCf+NGxYzqLXCvaoDMPAHF9LvLOZTztZ9w=; b=peDMsKdBT/uHIcdFtcNk25JwT1b/GJ1eCIcchCxLEVPaif25FbA9ILNscSPy9qnkJ2 mghwXaiqgpWhqucHAwbO/qUY8sNQyngnRYtv5PM4rv8m8NV+XPBN3yQL/N4a6Q1g/+9K RvWtz3/5DCbdoa6gN6cTPJv/p1ZQm7Gz6iHshhx08uBbYO5CoB8/XD7HQEyt9bJCBHo7 3cR7XV5okkFHIHLzc4TFIfdSGEWm2vew16BDdz+OQz0FtZH7aZui7pB5/t/CaUDq4ci0 GYVHn36frakpLdhaQgiKbr8VRMnjIVrFX1l+XrVhhrvS7ozSjmfV2WVs8EByQ5ENpwBk CkEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685527280; x=1688119280; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ZDDuIuyGJZCf+NGxYzqLXCvaoDMPAHF9LvLOZTztZ9w=; b=dMXfS9u/xmGqEbNeXeP4LGzp+dIpjg1r8ujqEzMNA97vhqqxX2/q8Gw9KOvwXDtgea d4xHq9S4i5z7++Mve9U0JK4bMvwG5mtGU4jYg3YcolYHKtjf1/r37+3q0juFqYnARSQV ovK5O/sUSlQ+CLUHdq4ZT37HYvwkOGDiaFK1a38yunPp3r/RaQRMTrexB63YHfCk2qmv PbOn/RTo4BjjnbpkH1YmiNpcxkkuJnb3zcZo8djFsUp7OOk5Nukj4vYzG2Sa4+R7l5CL kWaZgWrPi6oPAkWJSFJvJARc6Q1sYzHSZlhngYzT24MpGnxW46KvjKBCTQDFzlZLOZNd L9Kg== X-Gm-Message-State: AC+VfDzzkqO0wRFTh8mzLWvcElsSjNLnSqIXUJ5c7VeONr85BrtDyuA8 Db63w0pcl7cb3h2e1cSLxvCAA+SXAOR/GhS9hlo= X-Google-Smtp-Source: ACHHUZ7RGt6tNgoc9C/il6FySRgW+m1asTKsrh0lLlpIO5H42HqL0GuYFleDKWVFl59fdo8ZzGL+h6D6tDeUkX30uAo= X-Received: by 2002:a25:311:0:b0:ba1:66fa:ad35 with SMTP id 17-20020a250311000000b00ba166faad35mr5200705ybd.53.1685527279956; Wed, 31 May 2023 03:01:19 -0700 (PDT) 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 References: <86leh6ggfx.fsf@pcf00001.honeyguide.net> <20230530202020.060be2bf@ernst.home> <20230531113020.51b6b3cf@ernst.home> In-Reply-To: <20230531113020.51b6b3cf@ernst.home> From: Mario Marietto Date: Wed, 31 May 2023 12:00:43 +0200 Message-ID: Subject: Re: PinePhone Pro Boots On CURRENT To: garyj@gmx.de Cc: Stephan Lichtenauer , Pete Wright , FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000c7f7d205fcfa6691" X-Rspamd-Queue-Id: 4QWPtC0yp4z3mVZ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000c7f7d205fcfa6691 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable ---> No, with this you cannot replace Android with Linux. This hack merely provides a way to run a different OS in a KVM. ok,but what do I see as soon as I have flashed the boot.img to the phone with odin ? can I virtualize freebsd,right ? What tool can I use in FreeBSD to place phone calls and to send sms ? because this is what I want to do. A freeBSD powered phone. On Wed, May 31, 2023 at 11:30=E2=80=AFAM Gary Jennejohn wrot= e: > On Tue, 30 May 2023 20:50:52 +0200 > Mario Marietto wrote: > > > Check at this,also : https://github.com/raspiduino/a6lte-kvm/releases > > > > This would definitely be the best approach, since the developer has alrea= dy > tested Linux in the KVM. > > Odin, which I've used to install custom ROMs from xda, is a Windows > program. > If you have Windows then this would be a way to do the installation. > > The developer also mentions using Heimdall under Linux. There's a Heimda= ll > port for FreeBSD, so that might also be an option. > > > What I would like to know is if I can install Linux as the main > OS,instead > > of Android. Thanks. > > > > No, with this you cannot replace Android with Linux. This hack merely > provides a way to run a different OS in a KVM. > > [SNIP] > > -- > Gary Jennejohn > --=20 Mario. --000000000000c7f7d205fcfa6691 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
---> No, with this you cannot replace Android with= Linux.=C2=A0 This hack merely provides a way to run a different OS in a KV= M.

ok,but what do I see as soon as I have flashed = the boot.img to the phone with odin ? can I virtualize freebsd,right ? What= tool can I use in FreeBSD to place phone calls and to send sms ? because t= his is what I want to do. A freeBSD powered phone.

=

= On Wed, May 31, 2023 at 11:30=E2=80=AFAM Gary Jennejohn <garyj@gmx.de> wrote:
On Tue, 30 May 2023 20:50:52 +0200
Mario Marietto <marietto2008@gmail.com> wrote:

> Check at this,also : https://github.com/raspidu= ino/a6lte-kvm/releases
>

This would definitely be the best approach, since the developer has already=
tested Linux in the KVM.

Odin, which I've used to install custom ROMs from xda, is a Windows pro= gram.
If you have Windows then this would be a way to do the installation.

The developer also mentions using Heimdall under Linux.=C2=A0 There's a= Heimdall
port for FreeBSD, so that might also be an option.

> What I would like to know is if I can install Linux as the main OS,ins= tead
> of Android. Thanks.
>

No, with this you cannot replace Android with Linux.=C2=A0 This hack merely=
provides a way to run a different OS in a KVM.

[SNIP]

--
Gary Jennejohn


--
Mario.
--000000000000c7f7d205fcfa6691-- From nobody Wed May 31 12:48:13 2023 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 4QWTZn4F6Wz4Ydv9 for ; Wed, 31 May 2023 12:48:17 +0000 (UTC) (envelope-from theraven@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 4QWTZn3hRzz427Z for ; Wed, 31 May 2023 12:48:17 +0000 (UTC) (envelope-from theraven@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685537297; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=rapPkx6lMeghbwTnlO69Ro8p5mujOV5haUouNTy8rpU=; b=cNy4VhlOcAaVONvDmKpqNrR1iR1K3yDOgRQ2E1QuWd2qjN/pf7g/qCJu6zpvVnZ4jPQPwL AqX9Ja9szSPaPR63/m3xWMZI8UJYq2l1bjGF9FeuCoIyhFBMTSQj85IhtW+bLhBJFjO79F 8ngeoUlnpBZtaMiLdIMlbDpgDf7IQvHh4fomTxdPZWwHVfdY5Cwhg5gnosqieCVtyFnLZ2 xrVYOFEVTKrMGzJzqxv94JFHBLqD4rASEe/1vZ7IjxQhORcRHgMadPIBe4iOschuG2zRD6 0OZSIUkKBffEnBwm16KCaxObQsTFcIBMovsdaOIirWnxPYXQZsVgUNEVRxMM5Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685537297; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=rapPkx6lMeghbwTnlO69Ro8p5mujOV5haUouNTy8rpU=; b=XplMa9+BSbKy+eBA5xVuPoNRf+lo7rdSh8HPh4q8EA39mLZjMps87rPVBwl1lKfjjD8qA3 AGO6+kQAhor36NwW4eiKkzXIEQNTn3kYAxTbeUkJFyIypjh1bsDZ6TBrENoyKKR65qhl03 KiaR2OwTbtHi6LoA7kyhiFPyTQkM/CM/395qKQdqCwjdzG2lyYiz6QcyBb0hLdLrdCAms7 4eBrQ04nuyGpQ6kCtvGZhbygMOcG6I+Qgu+rYlzjSEANu+euOfYAnP1i3F3ktFQQdnA5Lw X4zzAkj373Frb22Ybov45GTljWltn7iuoN7On5cLGd2tYGbuIUnG6M1HooGHAQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1685537297; a=rsa-sha256; cv=none; b=GHlwjOz6tPFHrTYJBCin/Wc7c0OJdDd6sArXxIwa3qPqwYubiGT8RWbrFCw0CnjT4KFqYl howW557NyAl55n46TE96B8Tq2apVhQLBXUB/DHdSibMk/BiNuJdgfIMPE0QLsMtwdAGmsJ PEps8vAI13kX4Fdx7YP6Np5Z2Z+1w6Y1ZBp3mnmaXLnDenAhZzu+HyC84P2ezIkOw52hr2 ZzzwpQUvM7QuXojPCM6Kq69y8Pcf7rui8xTyF/TAU4EJXZUAYVshP8S7+A2IpNN9lEnVyM CXPP0mtP3YeR1qWayW6dYhRHJ8aADq3PRvuJoaq5lWCM4+pu1dn758AI8i/MqQ== Received: from smtp.theravensnest.org (smtp.theravensnest.org [45.77.103.195]) (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) (Authenticated sender: theraven) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QWTZn2h3Kz15WF for ; Wed, 31 May 2023 12:48:17 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from [192.168.1.202] (host86-136-198-116.range86-136.btcentralplus.com [86.136.198.116]) by smtp.theravensnest.org (Postfix) with ESMTPSA id 96A61118CD for ; Wed, 31 May 2023 13:48:15 +0100 (BST) Message-ID: <00390842-c06f-8396-d199-d854b24dc616@FreeBSD.org> Date: Wed, 31 May 2023 13:48:13 +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 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.11.2 Subject: Re: Surprise null root password To: freebsd-current@freebsd.org References: <850FF076-A511-4802-8D7C-2029752C3345@FreeBSD.org> <86sfbdk52w.fsf@ltc.des.no> Content-Language: en-GB From: David Chisnall In-Reply-To: <86sfbdk52w.fsf@ltc.des.no> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-ThisMailContainsUnwantedMimeParts: N On 30/05/2023 20:11, Dag-Erling Smørgrav wrote: > David Chisnall writes: >> There was a very nasty POLA violation a release or two ago. OpenSSH >> defaults to disallowing empty passwords and so having a null password >> was a convenient way of allowing people to su or locally log into that >> user but disallowing ssh. This option does not work in recent >> versions of FreeBSD. Turning on the option to permit root login while >> keeping the root password blank used to be (mostly) safe because it >> permitted su to root from people in the wheel group, root login via >> SSH key remotely (for ‘everything is broken I can’t log in as a user >> whose home directory is not on the root filesystem’ recovery) and >> local login as root from consoles marked as secure. It now permits >> root login from the network with a blank password. > That is incorrect. PermitRootLogin defaults to “no” in FreeBSD and to > “prohibit-password” upstream (and presumably in the port), while > PermitEmptyPasswords defaults to “no” both in FreeBSD and upstream, > cf. crypto/openssh/servconf.c (search for “permit_root” and > “permit_empty”). I didn't say it defaulted to anything else, but if you enable PermitRootLogin then you have a nasty surprise because PermitEmptyPasswords=no does not do anything and you can still log in via an empty password. There is presumably something I can put in pam.d that will prevent password-based login (without fully disabling keyboard-interactive from sshd_config) but I have never successfully understood anything after reading the PAM documentation. David From nobody Wed May 31 13:35:55 2023 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 4QWVdy57n7z4YjCJ for ; Wed, 31 May 2023 13:36:06 +0000 (UTC) (envelope-from garyj@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWVdx6fQCz47Cv for ; Wed, 31 May 2023 13:36:05 +0000 (UTC) (envelope-from garyj@gmx.de) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1685540158; i=garyj@gmx.de; bh=BR1bi37G1Fds/+3TGE2tBBu8L9Kyh5oxn99wY6zC0rA=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:In-Reply-To:References: Reply-To; b=HfoAAQeOrAqXRoVPzhIm6shvXappZPxqNeJdfcVVFM1KxN7iSLYQr4WfmAoarw+ZZ 51IVHEt2Bx43fwJbcejUNq7WHURccCQOIV2E/3NUGKFzxgluCEDSFbnXogcQQfj4Dr //U5MGmE4PofHS8qZP4hBAaAu9ncBVlBB4m4dK5WutLys5+NGQaKSsreZTxxDzUjba gf1q8YYF7MV+KyltNxT5XI95mCAcEP9ZEjUYgSjCPYeSBaMmreMErrL98NSKd09KzO q2QkDci/bxAk/nVhNJrOiiVRlO8RgVWIRO1zIRHcxXD1kj2J7DWRZri0+BnpmLjzYk CykMTsLLWCS/A== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from ernst.home ([91.59.239.47]) by mail.gmx.net (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MOiHl-1piZCz2OP1-00Q9J7; Wed, 31 May 2023 15:35:58 +0200 Date: Wed, 31 May 2023 13:35:55 +0000 From: Gary Jennejohn To: Mario Marietto Cc: Stephan Lichtenauer , Pete Wright , FreeBSD Current Subject: Re: PinePhone Pro Boots On CURRENT Message-ID: <20230531153555.472ac351@ernst.home> In-Reply-To: References: <86leh6ggfx.fsf@pcf00001.honeyguide.net> <20230530202020.060be2bf@ernst.home> <20230531113020.51b6b3cf@ernst.home> Reply-To: garyj@gmx.de X-Mailer: Claws Mail 3.19.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:/v9na5VxcqZP29lAaiB7jhX1RGboDblA3LrHPqlf3IsG5XzQCrv NTX2F+UktE1gKNIlQbzJkeC8nyhFJPbAasLLpVSRLPHg9CwpAAO9ATSJRFAti+6CismkGz+ szLahlQICiVSQZ0JLikJ5M5J9K9RQOBqv6MGHl3OJhSNxaa5UaMjwXT8vxHNjMUowHw55vG LIi+Frguvaak6zbva9gew== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:F1qVgurq4iI=;dOiFNoJhFjMtPP8jM0rV/1Jy0/I I+x0zrZZlT59N7Wf9omoHuk/c6fRgPheuGxaO//prkJabNFBA+bnYfBr9cFgL/mdRJLRgXpXA yxU9YCAhk5vyRvIxtxfdDSgms05EXdydczvbW0xGcVfSwi43lxwWj/ZPkPLwOToOyyuOEON3l ZbmPAfITK3Wn/XfI3Nyy2jFvKA/Lvo98se1UryZSwb8CUCDP4vQm2oGTI6xqw8q5bDc8gtcS5 USuLqam4GAY95X3odqiq9HInDqZG3XW8jv0HCAtSNTsTT4O816vtbmRLgdwHlwHtavxvL0742 dmzsq2f7A2q9gau8E4tcfWeHKRFyNAu1zk+m1iBD9/g2+ISEph2hgasR9jCXtRcd+nb0fikn9 D+NiCCkVMj2rnF+Op0o/htgQmfrM3zdaCTia822vds7KeWiHsKoBjHbqkeTjncKxDrt7TfoZG EkqvHC2SFJu9vH04QyEjIc1sfXg9FmQSUjAP87c8lpj60Q1qEVLo/+F5qxzNO+U/GAhctiL3F mkpKlzaKhoh50JIIR4v2ZxX8GThWIpR44NRgJLgwOMiDpQzb6Vpc6j1R9QsohjNpYB95yzVFO MnhnJWLRLLIQ9cq+/v21Qxro9actEPuqnso7H0ZxYkhgOxFPgSRQ/jmsWS3f1Cos+cDc4pv/X meUWLbLJX7bqoRi9yyjxgqfXFJ+nrnpdxkbMN0g4n29GOkQNkuxOph0vf4Yfmr9idb8N7hebB Ax1TyUojffCgADF6uQ+O9o7jwz6RxiG2l89L1iFtgAa4pT5UqzF+6LvGqShii3tRSblEIcvkd XM74riBpyvG3isNUzO+TLZ+HydxOfkF021ZTnuqpkbhHDMm8TzM8nPUOOJSVFZ8GPlgd8WGwm MOHweSMB+qDwOFSdlDnWuxRuHMc48IIm1Dp8WE6hml5YHjvCRlpPj2VWV3pgaI5qtPBV56d6A 7hlWjW4ivQisQDa2t77A7MaK9vc= X-Rspamd-Queue-Id: 4QWVdx6fQCz47Cv X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Wed, 31 May 2023 12:00:43 +0200 Mario Marietto wrote: > ---> No, with this you cannot replace Android with Linux. This hack mer= ely > provides a way to run a different OS in a KVM. > > ok,but what do I see as soon as I have flashed the boot.img to the phone > with odin ? can I virtualize freebsd,right ? What tool can I use in Free= BSD > to place phone calls and to send sms ? because this is what I want to do= . A > freeBSD powered phone. > You'll see the hacked Android version which the developer has provided. Android remains the OS for the phone. FreeBSD does not have the requiired proprietary driver blobs which are used by Android and I greatly doubt that FreeBSD running in a KVM will have access to all (or any) of the these hardware elements. Click on raspiduino/a6lte-kvm in the upper left corner of the github link. This will take you to the source repository which has a long document about his hack. Read it. [SNIP] =2D- Gary Jennejohn From nobody Wed May 31 13:48:44 2023 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 4QWVxG1W82z4Yjth for ; Wed, 31 May 2023 13:49:22 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-yw1-x1132.google.com (mail-yw1-x1132.google.com [IPv6:2607:f8b0:4864:20::1132]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWVxF4Rwvz49Lk for ; Wed, 31 May 2023 13:49:21 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-x1132.google.com with SMTP id 00721157ae682-565c3aa9e82so65520087b3.2 for ; Wed, 31 May 2023 06:49:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685540960; x=1688132960; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=38fEZYuiiDr2jDZKYSkGz8MY3z4uf8zpppq/QyFc1YE=; b=NLEjZFkks7fM70rcgRE8yd+08JGYwXww6NUBCFyTap6oexbTCpYHUxf1EKqcLYgdcu O/XdPv3Ot3qt+14zJ+w4Mjx6ig+7Ljtq+FOI5aB9QbuWoBJ/oWIsR+yl4RDnb4C2qnKE jVfmcxyE2GEbRe/Vkg3gDMrpR9fERj0zCQ9anCnSaj3TDHJFT96WR5ENgMgLBnwB/gA8 1GsNNSvXaVqezBjByHx7mGPAb5ke+0riylzyF9u1k03syTtMKJlxIOGtIoezVnUn4Vpu BPZpfkv9K3sVx6yVZNWgi4Pw0I8kI/V6l6SV8xOrhBWG03MrdPR+v4GTBlqyl5suJ+HO K2QQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685540960; x=1688132960; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=38fEZYuiiDr2jDZKYSkGz8MY3z4uf8zpppq/QyFc1YE=; b=bynjVm30lloJPsbkJRA87JtuiCgOVuVyyl84zQzNY8mtaG3oCWmUtvYD3TssDmhFvP Ipx48Rle5/6x0uWzhm7F3I6Ky9bQHJ5tFOxHcOG+23m2J9V6BkSJfiwwYVeJFpSKWwpe bCRxSGxZjWj+rzh6tctLA0CX/CVrG/QdBLgMMCudGFDTHdxkHxqG6KR5hwXrAMEMV4Ei CgTga/y4RjBpjX3Adw7B7Rlg/b6GwopPWo36cNsi6QZiD8xFENVToy+qrK1LUlyIaTJW 1hm8/ckbdjq267sEsJ4Vw1Z/lePGYeXWKkqHPzljJ1YbIyTMybtCmLPuk+WIvGCIz4FD BZ+g== X-Gm-Message-State: AC+VfDyAMyiSdRvsrA1h4CniKSthMFfApXxbQln3g4Z3VOF/+caNO4gT Qvzaee9pl37g4UDl0bQ2Uu4nAOXffV24SF3Qgpk= X-Google-Smtp-Source: ACHHUZ6pmZVK4e348+S98++HHL0pfo/Xk/SyOCUyb2gg23b4ix5rqZCf0u9JXxi7uDeUEltau4h9StqKnSCvKv9GjHs= X-Received: by 2002:a81:8444:0:b0:565:eae8:793b with SMTP id u65-20020a818444000000b00565eae8793bmr6205166ywf.25.1685540960362; Wed, 31 May 2023 06:49:20 -0700 (PDT) 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 References: <86leh6ggfx.fsf@pcf00001.honeyguide.net> <20230530202020.060be2bf@ernst.home> <20230531113020.51b6b3cf@ernst.home> <20230531153555.472ac351@ernst.home> In-Reply-To: <20230531153555.472ac351@ernst.home> From: Mario Marietto Date: Wed, 31 May 2023 15:48:44 +0200 Message-ID: Subject: Re: PinePhone Pro Boots On CURRENT To: garyj@gmx.de Cc: Stephan Lichtenauer , Pete Wright , FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000326cc805fcfd9648" X-Rspamd-Queue-Id: 4QWVxF4Rwvz49Lk X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000326cc805fcfd9648 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable ---> Android remains the OS for the phone. I'm not sure but I see that he talks even about Linux as main os that can be installed on the phone ---> FreeBSD does not have the required proprietary driver blobs which are used by Android and I greatly doubt that FreeBSD running in a KVM will have access to all (or any) of these hardware elements. This is true. But AFAIK qemu can provide the missing software components replacing them with the virtual ones. On Wed, May 31, 2023 at 3:35=E2=80=AFPM Gary Jennejohn wrote= : > On Wed, 31 May 2023 12:00:43 +0200 > Mario Marietto wrote: > > > ---> No, with this you cannot replace Android with Linux. This hack > merely > > provides a way to run a different OS in a KVM. > > > > ok,but what do I see as soon as I have flashed the boot.img to the phon= e > > with odin ? can I virtualize freebsd,right ? What tool can I use in > FreeBSD > > to place phone calls and to send sms ? because this is what I want to > do. A > > freeBSD powered phone. > > > > You'll see the hacked Android version which the developer has provided. > > Android remains the OS for the phone. FreeBSD does not have the requiire= d > proprietary driver blobs which are used by Android and I greatly doubt > that FreeBSD running in a KVM will have access to all (or any) of the > these hardware elements. > > Click on raspiduino/a6lte-kvm in the upper left corner of the github > link. This will take you to the source repository which has a long > document about his hack. Read it. > > [SNIP] > > -- > Gary Jennejohn > --=20 Mario. --000000000000326cc805fcfd9648 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
---> Android remains the OS for the phone.

I'm not sure but I see that he talks even about Linux= as main os that can be installed on the phone

--= -> FreeBSD does not have the required proprietary driver blobs which are= used by Android and I greatly doubt
that FreeBSD running in a KVM will have access to all (or any) of these har= dware elements.

This is true. But AFAIK qemu can p= rovide the missing software components replacing them wit= h the virtual ones.

On Wed, May 31, 2023 at 3:35=E2=80=AFPM Gar= y Jennejohn <garyj@gmx= .de> wrote:
On Wed, 31 May 2023 12:00:43 +0200
Mario Marietto <marietto2008@gmail.com> wrote:

> ---> No, with this you cannot replace Android with Linux.=C2=A0 Thi= s hack merely
> provides a way to run a different OS in a KVM.
>
> ok,but what do I see as soon as I have flashed the boot.img to the pho= ne
> with odin ? can I virtualize freebsd,right ? What tool can I use in Fr= eeBSD
> to place phone calls and to send sms ? because this is what I want to = do. A
> freeBSD powered phone.
>

You'll see the hacked Android version which the developer has provided.=

Android remains the OS for the phone.=C2=A0 FreeBSD does not have the requi= ired
proprietary driver blobs which are used by Android and I greatly doubt
that FreeBSD running in a KVM will have access to all (or any) of the
these hardware elements.

Click on raspiduino/a6lte-kvm in the upper left corner of the github
link.=C2=A0 This will take you to the source repository which has a long document about his hack.=C2=A0 Read it.

[SNIP]

--
Gary Jennejohn


--
Mario.
--000000000000326cc805fcfd9648-- From nobody Wed May 31 16:08:11 2023 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 4QWZ1j0xHHz4XBpm for ; Wed, 31 May 2023 16:08:25 +0000 (UTC) (envelope-from garyj@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWZ1h4P6Nz4VLm for ; Wed, 31 May 2023 16:08:24 +0000 (UTC) (envelope-from garyj@gmx.de) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1685549294; i=garyj@gmx.de; bh=OFandHvBSoRSQMHDfQMHROKuidNqNYPV0+GpGgdQPpg=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:In-Reply-To:References: Reply-To; b=OB2wuv63+YZZUYfeOpUoL8tzDQfR7YTihctXIhIxq0s+2M7FBV1EEzNyVsvV5aZDo mAZ21VbKMLONEk7zpYsdYvS1s5oO3+VcvRRLkhy8tT+WrM7nci4rQ0xXyC/Z9hxyxO BO6wTVc0uz47Cd+TkndSS9pIXGqgq3LYmSJfpHOcZduOOGd07ytCpnMpKZEkacFsKT B2KvsqoW3y7h1VNFWeGlwHuPU3p0wE4ek31d9cyaqDtmJA9YxeRl9cqTTa79DImuAr LfDy/VbQJtBFmffEsXz+NUbyl2VKGhIqbfACYf2rR+29vV5FwHPhDQeGaWLur8WD6M tULsXTSM216Ug== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from ernst.home ([91.59.239.47]) by mail.gmx.net (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1Mwwdl-1qJ1qH3EmR-00yNrI; Wed, 31 May 2023 18:08:14 +0200 Date: Wed, 31 May 2023 16:08:11 +0000 From: Gary Jennejohn To: Mario Marietto Cc: Stephan Lichtenauer , Pete Wright , FreeBSD Current Subject: Re: PinePhone Pro Boots On CURRENT Message-ID: <20230531180811.1403f4a9@ernst.home> In-Reply-To: References: <86leh6ggfx.fsf@pcf00001.honeyguide.net> <20230530202020.060be2bf@ernst.home> <20230531113020.51b6b3cf@ernst.home> <20230531153555.472ac351@ernst.home> Reply-To: garyj@gmx.de X-Mailer: Claws Mail 3.19.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:WSUIrWea2WKs17UEEhZC69dSn0CAsAJ+rnmgUFqkocvn0vILAvD VS7ROqRb0peYKSMkh9MqfXkrAX/4JM8gfOt3VZAu08rfB/ZjOm1eQfhFYoqa6FH9u84kW4f OTgh4c5Ptwx+fOpOh5l5YRSEUWIm2xl2OrHR4TgjhfSe3K7pMmCWZtlcZl3mVERTFhJw7UR Br3rU94MY4QKV+HV6+P4A== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:FT53Xguy+4c=;3R7lbWLNhhGoR/6fB1WcCiYOxi/ wlA4DQWQTFM/iJljEmQkebD7EnGg1Q3nCbB0ez9r5xAiHcoL0A5UN8uymzMLQVtUBCVCvJOAf yu+py71odbr1WLjYf/f8ZRfqCwhHfUe7yv7dtHQJg1PU5kfw84CoIQ+ubNUEl3hfCMgYWUngX mLXEk9dxSdl8g/BTpxt7kt3g3LEmdpD24KmS68hLj6m1+XT9cMzfu8r/n72J2FZBegu75GPfW xF5/m4UxJUKknzVlWNafes//5AVbY5S/9OYNF7JaEpa2BzE2vthOTK9+THp+PrRjmqDoaSss6 odbA1inBpLb8eIZm9zQ2ED5b30tUfMqnRuem6/mCnNDt34NqtDFjnvVicpfpEXMnE7PEePPnE 4LPxu1+9yhiwsjNoZgFQA3UgSqH4zcXWiQ1JtsafAxdnDcqZUXeTGKsy077CmehKLSFG3AA+U x/BSjMd4+eFlfEX3pF5kFAauRbsTm3/gsYXk5d2B/1OI7jVKVJjgiGPTANwAd2aoZSmSGaWLt R3FdZp3h6/lfuy92QHQ2MTbpC1MWKA+AFqjDojTZY0w1WzgyWFx3wvA7TY5G1UgqWde5Ue1iW uPacuCwweNs2IGIlTX2J88CFj5ftPv7kJicowpG4FGM9doOjQWi8dbTF14yJYqpGJmCzGZw84 G9FVxhBSbc4PueSWm/IyeL4YHuuaQb2cM/2CN68uKsaaWQ2F4xJRwypb2tbX3bXPQjlfVmJQh lw8EPlpj6o0HrbSQ0AuR2iTEuZopqibLxTgjPliebtTqdBLtwZgNHPW5IgPSHTqjFfkxUNNg3 6t5MMieBx5mHERp6JTsQo2nfnlERGCgcTHzVK/W2mX252O1g8Mv1zg0sPFmJz9/1M24LQzIRa VOClCvoUvB8FmjylF9OTK0nlGVYFvVtqfG3FdCpeSlFdJ+LvTuOgSRClRG1k2lhVe9aZglUDj O3S51qZ05umLMtBHYgUHAoj3Qeg= X-Rspamd-Queue-Id: 4QWZ1h4P6Nz4VLm X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Wed, 31 May 2023 15:48:44 +0200 Mario Marietto wrote: > ---> Android remains the OS for the phone. > > I'm not sure but I see that he talks even about Linux as main os that ca= n > be installed on the phone > No, Linux is installed in a chroot. So it's not replacing Android. See chroot(2) and chroot(8). The developer used Linux Deploy, an app from Google, which creates a chroot on a SD card and copies Linux to it. Since Android only supports FAT32 that means that the Linux distribution has to be smaller than 4GiB (about 4.295 billion bytes). Would be nice if there were an app like that for FreeBSD. > ---> FreeBSD does not have the required proprietary driver blobs which a= re > used by Android and I greatly doubt > that FreeBSD running in a KVM will have access to all (or any) of these > hardware elements. > > This is true. But AFAIK qemu can provide the missing software > components replacing > them with the virtual ones. > I can't imagine how that could work without the proprietary driver blobs. There are lots of drivers in the source tree, but based on the names it's difficult to tell just which hardware is supported. Not clear whether the modem is in the tree or a driver blob is required. =2D- Gary Jennejohn From nobody Wed May 31 18:15:12 2023 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 4QWcrG4XQtz4XMbD for ; Wed, 31 May 2023 18:15:26 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWcrF3Sjrz3GYP for ; Wed, 31 May 2023 18:15:25 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20221208.gappssmtp.com header.s=20221208 header.b=OOwNU72w; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2a00:1450:4864:20::235) smtp.mailfrom=wlosh@bsdimp.com; dmarc=none Received: by mail-lj1-x235.google.com with SMTP id 38308e7fff4ca-2af29e51722so68410471fa.1 for ; Wed, 31 May 2023 11:15:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1685556923; x=1688148923; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=dkD+If4JXesMXBA6I1BeoGioa0trXhs+xBSpUs5Zbs4=; b=OOwNU72wERtMrBJALhbVBQrYa8SX9sI1LDD3FeTTGRDrY4uLaDzyqupKyusdYGayi2 R198xb1fAVUHyn6Fk6IGAAVgtSnMI1I0RvLnnYkZBRTieSrSQGeASmKr2SU4mUZbNmAw TgJ7R6gDBfZB57hKOudEoFpGf5HE6pVuTjm3NVrO1kZE88TOjVocpvffKSHwMU03XfhF GFPcNZ2cszLSrtWsF48J3ayFT5BeeCQc5+k8+nuqRDMwkYQ1N0hqmMBdU0zWiUNTh+J9 y3N8SL1Eq7VHS9U5S2UzFuuFDC5CcDvHoVGGN7LmE/MmvuyBX9F+K3M2YBi63zMWmHT8 J5yQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685556923; x=1688148923; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=dkD+If4JXesMXBA6I1BeoGioa0trXhs+xBSpUs5Zbs4=; b=O5HqPqEvNmDsiqu3UZ42OzZHCByPK3wQfiwiRQAFJiPVk8y8VsoLdNmvTuA/cYc6Fn Zp8s9ndWIKgK8v7WB4uU93MDvnBsLCPG1ns5sSeQM8k/vvjc8Z5fw+mAKa7Y4GqKEgVE QqnCnLT2gHrrWZBR4fHjDvx5VTGPexPnt4SGvroXpzIXUt69hVkfsM4hlyMKVHGtrRPk nDPHenH4FhNpMI4gLmfjcyRcA3doBeQts60JbXZVV1r/glTjTZcD4i6VP/1DYSRyRHi2 3iLVlOJ890Wi/HvN8gqM8NXT4iteMR7CEvQefhyyJdVuy0Z4BXBqR8v8cOL91FyPRYiW 3SVQ== X-Gm-Message-State: AC+VfDwj8oC6TdlmDHcFkOIws63e3n9hdrS2xCTiRLUln79VkSPsK3dj bOuZjRBIOW9aYXUVOPzSa/ElmLh5Zx8HjitUveEJc0EdLSnnKDbtw/E= X-Google-Smtp-Source: ACHHUZ44QRGEqvt25emuxUuhthrR8a69tmoTAZ28PLEXDndMj5QZZjsvyMwFC+96l6DiLtjm/DDIDJNd/YnP+hIReno= X-Received: by 2002:a2e:8754:0:b0:2af:160d:8897 with SMTP id q20-20020a2e8754000000b002af160d8897mr3182699ljj.26.1685556923442; Wed, 31 May 2023 11:15:23 -0700 (PDT) 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 References: <20230529105854.1903226d@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20230529105854.1903226d@thor.intern.walstatt.dynvpn.de> From: Warner Losh Date: Wed, 31 May 2023 12:15:12 -0600 Message-ID: Subject: Re: WITH_BEARSSL: -8112 bytes available To: FreeBSD User Cc: FreeBSD CURRENT Content-Type: multipart/alternative; boundary="000000000000abbc5b05fd014d59" X-Spamd-Result: default: False [-2.94 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.94)[-0.944]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20221208.gappssmtp.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ARC_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; R_SPF_NA(0.00)[no SPF record]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::235:from]; DKIM_TRACE(0.00)[bsdimp-com.20221208.gappssmtp.com:+]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; DMARC_NA(0.00)[bsdimp.com]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4QWcrF3Sjrz3GYP X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --000000000000abbc5b05fd014d59 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, May 29, 2023 at 2:59=E2=80=AFAM FreeBSD User wrote: > Hello, > > on CURRENT, enabling in /etc/src.conf > > WITH_BEARSSL=3D > > seems to result in a slightly enlarged loader binary, which seems to have > a fixed size > supposed on the error I get. See below. > > The system is amd64 (64 bit), for the record. > > Somewhere in the past developers mentioned this upcoming problem and > provided a knob to adjust > the used size - I forgot about that knob and I couldn't find it even in > the loader docs - or > looked at the wrong places. > > Can someone help me out here? > > The first error stops compileing world/kernel, but taking a second run, > the error goes away. > > Kind regards and thanks in advance, > > oh > > > > [...] > --- all_subdir_stand/efi --- > SOURCE_DATE_EPOCH=3D1451606400 objcopy -j .peheader -j .text -j .sdata -= j > .data -j .dynamic -j > .dynsym -j .rel.dyn -j .rela.dyn -j .reloc -j .eh_frame -j > set_Xcommand_set -j > set_Xficl_compile_set --output-target=3Defi-app-x86_64 loader_4th.sym > loader_4th.efi --- > all_subdir_stand/i386 --- > > -8112 bytes available 7.71 real 12.86 user 3.08 sys bummer. I hate it when it's that close. You can try setting LOADERSIZE=3D560000 in your environment. We currently s= et the maximum to 550,000 bytes because that's the most conservative number due to variation in the available BIOS space available. This likely can be set even higher if you don't have add-in cards that are consuming space in the lower 640k of memory. 640k is the absolute limit, but you need 20-30k of stack for the loader so pushing this much past 625,000 or maybe 630,000 increases the risk of run-time crashes as the stack smashes through the top of the loader program. You may also have to disable the lua build, since it uses more stack and is just a smidge larger than the forth build. _simp will be the smallest of them all. On my system, without bearssl, I see: -r-xr-xr-x 3 root wheel 503808 May 22 15:25 /boot/loader_lua -r-xr-xr-x 1 root wheel 446464 May 22 15:25 /boot/loader_4th -r-xr-xr-x 1 root wheel 385024 May 22 15:25 /boot/loader_simp which suggests a ~60k bump for adding forth and ~115k bump for lua. So the 560,000 may need to be 625,000 which is living life on the edge for 4th, and simply too big for lua. I'd be open to adding docs on this, since I don't think this option is currently documented since I added it to experiment around with a good value. And no, I really do not want to support 'loadable modules'. BIOS booting is on the way out, and people that want to do complex stuff in the boot loader will simply have to do that in UEFI or maybe kboot/LinuxBoot. There's low RoI on adding this complexity, imho. We'd be better off, imho, making things like the graphics console optional since the fonts and code for that free up about 30k in stupid experiments that I've done (it's hard since vidconsole has a lot of calls into the graphics system that aren't optional and easy to disable, so I've had to do hack and slash to produce a super ugly result that is only suggestive of the final savings): -rw-r--r-- 1 imp imp 352256 May 31 12:04 loader_simp I don't know if I slashed too much, or not enough since the code is rather hard to separate out, so if you really wanted to go down this path, it would take a lot of work and patient understanding to make it so with the low end of savings 20k and the high end on the order of maybe 40k. There's likely other ways to conserve space. We've not had space issues with loader, et al, in the past, so it's not well setup for subsetting. Though the different filesystem support might also net you a fair amount: LOADER_NET_SUPPORT?=3D yes LOADER_NFS_SUPPORT?=3D yes LOADER_TFTP_SUPPORT?=3D yes LOADER_CD9660_SUPPORT?=3D yes LOADER_EXT2FS_SUPPORT?=3D yes LOADER_MSDOS_SUPPORT?=3D yes LOADER_UFS_SUPPORT?=3D yes LOADER_GZIP_SUPPORT?=3D yes LOADER_BZIP2_SUPPORT?=3D yes as would compiling w/o ZFS, which uses its own method (eg WITHOUT_LOADER_ZFS). Tuning the loader at this level does start to get into the weeds a bit, but can offer ~40k savings turning off all but NET and UFS: -rw-r--r-- 1 imp imp 344064 May 31 12:11 loader_simp you get even about ~100k when you disable ZFS support with -DWITHOUT_LOADER_ZFS: -rw-r--r-- 1 imp imp 241664 May 31 12:12 loader_simp (both of these are with the graphics console enabled without the silly hacks to see how much that takes up). Without the extras and ZFS, you might have bearssl and lua together even... Hope this helps. Warner --000000000000abbc5b05fd014d59 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, May 29, 2023 at 2:59=E2=80=AF= AM FreeBSD User <freebsd@walst= att-de.de> wrote:
Hello,

on CURRENT, enabling in /etc/src.conf

WITH_BEARSSL=3D

seems to result in a slightly enlarged loader binary, which seems to have a= fixed size
supposed on the error I get. See below.

The system is amd64 (64 bit), for the record.

Somewhere in the past developers mentioned this upcoming problem and provid= ed a knob to adjust
the used size - I forgot about that knob and I couldn't find it even in= the loader docs - or
looked at the wrong places.

Can someone help me out here?

The first error stops compileing world/kernel, but taking a second run, the= error goes away.

Kind regards and thanks in advance,

oh



[...]
--- all_subdir_stand/efi ---
SOURCE_DATE_EPOCH=3D1451606400=C2=A0 objcopy -j .peheader -j .text -j .sdat= a -j .data=C2=A0 -j .dynamic -j
.dynsym -j .rel.dyn=C2=A0 -j .rela.dyn -j .reloc -j .eh_frame -j set_Xcomma= nd_set=C2=A0 -j
set_Xficl_compile_set=C2=A0 --output-target=3Defi-app-x86_64 loader_4th.sym= loader_4th.efi ---
all_subdir_stand/i386 ---

-8112 bytes available 7.71 real=C2=A0 =C2=A0 =C2=A0 =C2=A0 12.86 user=C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A03.08 sys

bummer= . I hate it when it's that close.

You can try = setting LOADERSIZE=3D560000 in your environment. We currently set the maxim= um to 550,000
bytes because that's the most conservative numb= er due to variation in the available BIOS space available.
This l= ikely can be set even higher if you don't have add-in cards that are co= nsuming space in the lower 640k
of memory. 640k is the absolute l= imit, but you need 20-30k of stack for the loader so pushing this much past=
625,000 or maybe 630,000 increases the risk of run-time crashes = as the stack smashes through the top of
the loader program. You m= ay also have to disable the lua build, since it uses more stack and is just= a smidge
larger than the forth build. _simp will be the smallest= of them all. On my system, without bearssl, I see:
-r-xr-xr-x = =C2=A03 root =C2=A0wheel =C2=A0503808 May 22 15:25 /boot/loader_lua
-r-xr-xr-x =C2=A01 root =C2=A0wheel =C2=A0446464 May 22 15:25 /boot/= loader_4th
-r-xr-xr-x =C2=A01 root =C2=A0wheel =C2=A0385024 M= ay 22 15:25 /boot/loader_simp
which suggests a ~60k bump for = adding forth and ~115k bump for lua. So the 560,000 may need to be 625,000<= /div>
which is living life on the edge for 4th, and simply too big for = lua.

I'd be open to adding docs on this, since= I don't think this option is currently documented since I added it
to experiment around with a good value.

And= no, I really do not want to support 'loadable modules'. BIOS booti= ng is on the way out, and people
that want to do complex stuff in= the boot loader will simply have to do that in UEFI or maybe kboot/LinuxBo= ot.
There's low RoI on adding this complexity, imho. We'd= be better off, imho, making things like the graphics
console opt= ional since the fonts and code for that free up about 30k in stupid experim= ents that I've done
(it's hard since vidconsole has a lot= of calls into the graphics system that aren't optional and easy to dis= able,
so I've had to do hack and slash to produce a super ugl= y result that is only suggestive of the final savings):
-rw-r--r-= - =C2=A01 imp =C2=A0imp =C2=A0352256 May 31 12:04 loader_simp
I don't know if I slashed too much, or not enough since the code is ra= ther hard to separate out, so if you
really wanted to go down thi= s path, it would take a lot of work and patient understanding to make it so= with
the low end of savings 20k and the high end on the order of= maybe 40k.

There's likely other ways to conse= rve space. We've not had space issues with loader, et al, in the past,<= /div>
so it's not well setup for subsetting. Though the different f= ilesystem support might also net you a fair amount:
LOADER_NET_SU= PPORT?=3D =C2=A0 =C2=A0yes
LOADER_NFS_SUPPORT?=3D =C2=A0 =C2=A0yes
LO= ADER_TFTP_SUPPORT?=3D =C2=A0 yes
LOADER_CD9660_SUPPORT?=3D yes
LOADER= _EXT2FS_SUPPORT?=3D yes
LOADER_MSDOS_SUPPORT?=3D =C2=A0yes
LOADER_UFS= _SUPPORT?=3D =C2=A0 =C2=A0yes
LOADER_GZIP_SUPPORT?=3D =C2=A0 yes
LOAD= ER_BZIP2_SUPPORT?=3D =C2=A0yes
as would compiling w/o ZFS, wh= ich uses its own method (eg WITHOUT_LOADER_ZFS). Tuning the loader
at this level does start to get into the weeds a bit, but can offer ~40k = savings turning off all but NET and UFS:
-rw-r--r-- =C2=A01 imp = =C2=A0imp =C2=A0344064 May 31 12:11 loader_simp
you get even = about ~100k when you disable ZFS support with -DWITHOUT_LOADER_ZFS:
-rw-r--r-- =C2=A01 imp =C2=A0imp =C2=A0241664 May 31 12:12 loader_simp
(both of these are with the graphics console enabled without t= he silly hacks to see how much that takes up).
Without the extras= and ZFS, you might have bearssl and lua together even...

Hope this helps.

Warner
--000000000000abbc5b05fd014d59-- From nobody Wed May 31 19:30:26 2023 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 4QWfW54Wg0z4XSwG for ; Wed, 31 May 2023 19:30:41 +0000 (UTC) (envelope-from garyj@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWfW50rn5z3Nr0 for ; Wed, 31 May 2023 19:30:40 +0000 (UTC) (envelope-from garyj@gmx.de) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1685561434; i=garyj@gmx.de; bh=/SdHu9Rf1alSBTlk5lKCHN0qAkUkaLU5OWBmKxqsMi0=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:In-Reply-To:References: Reply-To; b=PedytMiTiNg2QfjZWIHJ5YYIguB0E144DgmZ83KzlDEe/9w4BTYDVfbfuhWqHIlip SimbNP2tBVwA/W/BUweSg7Bn4DjcjzC4KSWdSJKGAhbz9B5ChvCjuz1IBqT2PCtQ8I jvccs84B0GoTcZevimNJwVaMc2AR6hGc96uHvwnrfNx+dcOPC2H7sQVrCLWiwVmqdV fa9WDdroNI/vArJ9vUNAZrIK73JnoAupSrv1bgCxzC0qUeD8klqq6ZyL6gzF0vbGo7 a4G7UKZIXTJP6SHORLW/5yCsTh9G0TvqSx11ZLSCz2a/rlS340q/a2N26cstQg07QX pbKvH7DRetkAQ== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from ernst.home ([91.59.239.47]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1N4QsY-1qBUpY0S1u-011Pvt; Wed, 31 May 2023 21:30:34 +0200 Date: Wed, 31 May 2023 19:30:26 +0000 From: Gary Jennejohn To: Warner Losh Cc: FreeBSD User , FreeBSD CURRENT Subject: Re: WITH_BEARSSL: -8112 bytes available Message-ID: <20230531213026.275c4eaf@ernst.home> In-Reply-To: References: <20230529105854.1903226d@thor.intern.walstatt.dynvpn.de> Reply-To: garyj@gmx.de X-Mailer: Claws Mail 3.19.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:TLyvQpLavZDJ1u7I6/UNTtDBwvAq1u1qrf6KsulbFXV2yXioXID m5CxQa5ZAJ1k1mOYbbM9lnD6A8Qa3fC+cwCi8dAYvhZrnfQRc8G+lKjnAZcKXg+41sZuK9j so3JY190j9m1a49TMGeR8maTOLMstvQOhWGwP5/HILh9Gqd0zVHDfR48aEEnFV6ASVsKCQG om6YykLd1SKSDr24Ve3Mg== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:fcGmbVCyyYc=;1gVWIHtgRR6Gt/nl1gTtn9UoR1/ dO4jAJJSLHwilMW8Ec6BxhV6HcQgaoO100C8rRShyLFAjtIbyGsLA2m2zDV3T7C8b0s+8ra+q KHvB3GPaoA/jnMc3o4UhsTlYtkEuct8CSpMKA3CDbrFnOrULsc3eIbyR6ED+Kk8XeQ2MfDvje YEnRaJjJ7/HEGx5MHniOdVm6etcXpy9PJ+lR6/olMyHMGpMBj2gTPhmOFD1LLMOeXmC7rKG02 o9QbXQK2zGhIxAo1aLdldJj7fbj/1gYXwnbRBAOX3HAnl9FRJdoi+fHXC0Nn+zAfAWygKWc5Q /XJ5lSorNFqlmXXm95GhK0Ope4ljW/X89HZY4Fdo0LOpXYh7psBJSXihf321mq+7NfV+zMrFi I5slH/Lodj7gy0227466d0duri/jp0xIfqoCvY8JTmDTIZKke5iBvKNoi+IdPtR1k/An9aUx4 Iw91VTWSM1bRsVw8qUXIw2adKdV3OjAIBXHADKzQwTR9sF58w3uSZ29Z0sbYBHmcJnx+NWiQn 1RhC6/CzIM3WSSEA/D9COadr48ktmjp+xLjj9IgZKFlIgDAtCKjh8sj/8UKHtrFxbFPMzoRDE ZZLQAfkBtn658ZDgCqNqv6A/ISXZOr6qqDkhI7Q6zQEA40SQ79Ac/7BGnay/lP3ZQw8dy9TeT XlEmquPu79f6QoWyXHZD8h0Mn3aR24/BwcOa3l9GKdYQTe8IZjX3P/jYsShdVV4fsdLhhFdde JlbaihiZOMp0FhxJC0uChiSI4wePcNe9Kopd7O8by4gcSJLk60XG8DcnB0FBh3WianWG6N8eM UDyVs4pcAtmSnKyUKHOVhURJVCmVdUF3qOPlY3+fhXcrojSTB8nFEOmYxcbwgVJPjetmT33Hx qAxDlqHenMUanoCjAfCvjzWzM33n1B4Lptse8EBYQhVuPx/al5/6WAqebVLNJ5XcB4SNaqSfW OHOVtQYNZoMW9Vljr4VtBLe5m2U= X-Rspamd-Queue-Id: 4QWfW50rn5z3Nr0 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Wed, 31 May 2023 12:15:12 -0600 Warner Losh wrote: [SNIP irrelevant text] > And no, I really do not want to support 'loadable modules'. BIOS booting= is > on the way out, and people > that want to do complex stuff in the boot loader will simply have to do > that in UEFI or maybe kboot/LinuxBoot. So, what exactly does "BIOS booting is on the way out" mean? I have four computers which use BIOS booting. Three are too old to support UEFI and the other one I simply set to BIOS booting out of habit. The only computer I have which uses UEFI is a laptop which was already set up to use UEFI and I was too lazy to change it. > There's low RoI on adding this complexity, imho. We'd be better off, imh= o, > making things like the graphics > console optional since the fonts and code for that free up about 30k in > stupid experiments that I've done > (it's hard since vidconsole has a lot of calls into the graphics system > that aren't optional and easy to disable, > so I've had to do hack and slash to produce a super ugly result that is > only suggestive of the final savings): > -rw-r--r-- 1 imp imp 352256 May 31 12:04 loader_simp > I don't know if I slashed too much, or not enough since the code is rath= er > hard to separate out, so if you > really wanted to go down this path, it would take a lot of work and pati= ent > understanding to make it so with > the low end of savings 20k and the high end on the order of maybe 40k. > > There's likely other ways to conserve space. We've not had space issues > with loader, et al, in the past, > so it's not well setup for subsetting. Though the different filesystem > support might also net you a fair amount: > LOADER_NET_SUPPORT?=3D yes > LOADER_NFS_SUPPORT?=3D yes > LOADER_TFTP_SUPPORT?=3D yes > LOADER_CD9660_SUPPORT?=3D yes > LOADER_EXT2FS_SUPPORT?=3D yes > LOADER_MSDOS_SUPPORT?=3D yes > LOADER_UFS_SUPPORT?=3D yes > LOADER_GZIP_SUPPORT?=3D yes > LOADER_BZIP2_SUPPORT?=3D yes > as would compiling w/o ZFS, which uses its own method (eg > WITHOUT_LOADER_ZFS). Tuning the loader > at this level does start to get into the weeds a bit, but can offer ~40k > savings turning off all but NET and UFS: > -rw-r--r-- 1 imp imp 344064 May 31 12:11 loader_simp > you get even about ~100k when you disable ZFS support with > -DWITHOUT_LOADER_ZFS: > -rw-r--r-- 1 imp imp 241664 May 31 12:12 loader_simp > (both of these are with the graphics console enabled without the silly > hacks to see how much that takes up). > Without the extras and ZFS, you might have bearssl and lua together even= ... > > Hope this helps. > This is interesting information. =2D- Gary Jennejohn From nobody Wed May 31 20:01:22 2023 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 4QWgD66Mycz4XWkm for ; Wed, 31 May 2023 20:02:46 +0000 (UTC) (envelope-from sjg@juniper.net) Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.pphosted.com", Issuer "Thawte RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWgD631czz3jtX for ; Wed, 31 May 2023 20:02:46 +0000 (UTC) (envelope-from sjg@juniper.net) Authentication-Results: mx1.freebsd.org; none Received: from pps.filterd (m0108161.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 34VGaDA7022727; Wed, 31 May 2023 13:02:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=to : cc : subject : in-reply-to : references : from : mime-version : content-type : content-id : content-transfer-encoding : date : message-id; s=PPS1017; bh=oB5mOsEiaLNAijE+B5xwKn/tCRy7EbBN/M+VTwAwF1A=; b=BnM7wmvRaCdCFUx4ET7fSz2+Gb2xI6exSuRfU2DuRK/lFyPHYo4BzzVPkoZX62CkCYDr BAoL7hjp9k+PpQ64pCRxA4AILPMaPOo1+GRwiPrlqNXa75HXDfvaWodxM6VIOnQxyldU IQEzj7wGjTs52rnBMZnzXB0dkbbM9/L8V3PU84Y6ZzfJMde7ydwjkqPX04eCHfPn1nqN h5+sIbYA6mjH6rAHReGyBUUOIH18/udGWraFYdhSTdVxQy8vR5f0R0WLgA++ypv/aFui ijRjlZg9tlK171wMkyijfeNGA4958++/ixkubDoNJNO6d3XR0SPPjfohUNPgI8kdj32B +g== Received: from dm4pr02cu001.outbound.protection.outlook.com (mail-centralusazlp17012020.outbound.protection.outlook.com [40.93.13.20]) by mx0b-00273201.pphosted.com (PPS) with ESMTPS id 3qx394sbfk-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 31 May 2023 13:02:43 -0700 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CwU8wPkRGOOxTeYmzqQQzpWWvqXu1uxSLSLq3HVoUPcuUQHURuQCg/3QheIEeWUMCEqW4cIwL72kS/2PWLpDVe2Pift88d1fT+PfEDSohhXb4CbQOm6GD1sttqMPygpVf288N5hGp21fj5XtYb8/UCXCMtyz+aHTL4LElgDj6nZ/cMG4ILOf2WBntcVhJ5Rgh4i08V6tSiATuXt5Sod3+q3G+FbpNYU7lZZBJlb4dyr0EHzDsOtzbJ4fcLOWEZxgoM6jEd1ipn7sOSiB/4gxH8OeWICZflXHk6Wmz+KTgy8cq03L2SoT5vnnUyfwPLMM2Bgg5lmupsH3g01XAjcrwg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=oB5mOsEiaLNAijE+B5xwKn/tCRy7EbBN/M+VTwAwF1A=; b=V0ZrymsUPxLVIt+zOAqzLYr4OyKD21ZxMhDsIh42RsC0k71PSWQFPF0jzV0A+Us30b93JuTe1gOF7ArBHOPRJIlnqPiVBtmp690yw4jjaFbV9auZbDXajIgzn6+NHdjAYx3YOewxkejzKlIUChkuRb02iwUU9HUsjMdHiZWVxD3O476ctpKtT8+13iXBiYw1u7aNn0T7TxbLPL4cwvFAwY+vsD7dKQ45JC/OIxPQeU6gmDJz3pVEqT5FLOKbAEibxGp7uaPkwkB3DbsOrM/d4rCMKPQd5/bW/cnzD9BuNe3rAWj/paHyKa9LINqU+PRkT7s6vTEcWJU+Ba+Ph+wttQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=softfail (sender ip is 66.129.239.15) smtp.rcpttodomain=walstatt-de.de smtp.mailfrom=juniper.net; dmarc=fail (p=reject sp=reject pct=100) action=oreject header.from=juniper.net; dkim=none (message not signed); arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=oB5mOsEiaLNAijE+B5xwKn/tCRy7EbBN/M+VTwAwF1A=; b=IdUPvcJdhPLGhdgESFe1EmBHpAelc9YfXiXGDXwic1dOepfR/TESsnWS5+Cnxujd47Los9bdM0j60axACVEhtPxk3TTRZJKj+FX7NRuW2+vFFbto1TO1M4CSOf4MFHvub04qTriPyFW/xRCbkNaH48ZKC3HNxHZcBS0b4F5AvsY= Received: from BN8PR12CA0034.namprd12.prod.outlook.com (2603:10b6:408:60::47) by DM4PR05MB10170.namprd05.prod.outlook.com (2603:10b6:8:17f::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6433.24; Wed, 31 May 2023 20:02:41 +0000 Received: from BN8NAM12FT099.eop-nam12.prod.protection.outlook.com (2603:10b6:408:60:cafe::16) by BN8PR12CA0034.outlook.office365.com (2603:10b6:408:60::47) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6455.23 via Frontend Transport; Wed, 31 May 2023 20:02:41 +0000 X-MS-Exchange-Authentication-Results: spf=softfail (sender IP is 66.129.239.15) smtp.mailfrom=juniper.net; dkim=none (message not signed) header.d=none;dmarc=fail action=oreject header.from=juniper.net; Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.15 as permitted sender) Received: from p-exchfe-eqx-02.jnpr.net (66.129.239.15) by BN8NAM12FT099.mail.protection.outlook.com (10.13.183.226) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6477.7 via Frontend Transport; Wed, 31 May 2023 20:02:40 +0000 Received: from p-exchbe-eqx-02.jnpr.net (10.104.9.15) by p-exchfe-eqx-02.jnpr.net (10.104.9.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.21; Wed, 31 May 2023 15:02:39 -0500 Received: from p-exchbe-eqx-01.jnpr.net (10.104.9.14) by p-exchbe-eqx-02.jnpr.net (10.104.9.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.21; Wed, 31 May 2023 15:02:39 -0500 Received: from p-mailhub01.juniper.net (10.104.20.6) by p-exchbe-eqx-01.jnpr.net (10.104.9.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.21 via Frontend Transport; Wed, 31 May 2023 15:02:39 -0500 Received: from kaos.jnpr.net (kaos.jnpr.net [172.23.255.201]) by p-mailhub01.juniper.net (8.14.4/8.11.3) with ESMTP id 34VK2cG9022033; Wed, 31 May 2023 13:02:38 -0700 (envelope-from sjg@juniper.net) Received: by kaos.jnpr.net (Postfix, from userid 1377) id 2EE628F0DF; Wed, 31 May 2023 13:01:22 -0700 (PDT) Received: from kaos.jnpr.net (localhost [127.0.0.1]) by kaos.jnpr.net (Postfix) with ESMTP id 2E7888EF7B; Wed, 31 May 2023 13:01:22 -0700 (PDT) To: Warner Losh CC: FreeBSD User , FreeBSD CURRENT , Subject: Re: WITH_BEARSSL: -8112 bytes available In-Reply-To: References: <20230529105854.1903226d@thor.intern.walstatt.dynvpn.de> Comments: In-reply-to: Warner Losh message dated "Wed, 31 May 2023 12:15:12 -0600." From: "Simon J. Gerraty" X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 28.2 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 Content-Type: text/plain; charset="us-ascii" Content-ID: <98576.1685563282.1@kaos.jnpr.net> Content-Transfer-Encoding: quoted-printable Date: Wed, 31 May 2023 13:01:22 -0700 Message-ID: <27.1685563282@kaos.jnpr.net> X-EOPAttributedMessage: 0 X-MS-PublicTrafficType: Email X-MS-TrafficTypeDiagnostic: BN8NAM12FT099:EE_|DM4PR05MB10170:EE_ X-MS-Office365-Filtering-Correlation-Id: 6bd83869-71d6-4c70-fa91-08db6211fd85 X-MS-Exchange-SenderADCheck: 1 X-MS-Exchange-AntiSpam-Relay: 0 X-Microsoft-Antispam: BCL:0; X-Microsoft-Antispam-Message-Info: wuphOhSRpDyQK/zNrsXJdnonIgNGijMiJYO0lD4sN1OvkafWvXc/BPRJ5HRgusRJnUciM6goWoL9T6b7qFpwLjud4ibt2BglDaq6zh9zKDctf2D9UsNRkCpayoUyN+B9sVaOYYMPiVVIhtwgdO4LXXj0aCPuFagM5esGNxMdT4yEjCAHG6dcBtqqK2cifExtuXrekAvaba9qe/KiQuYwjuTRguJNh3Q7dbhpn+NHyUQ0fmmnJ8Iv9kTHPLWWvgUI6lWfyklL6TvX9Tobf6JB4uNjaQherdRsV0srHwKBj09IFmyX3BCYVDAtbM3t5m1mScY5h563OmlS1nj/xpDni1iVGlRjTPXY+jXY7Pratq9Whag0afSI7ddQD+/7JZzO/falpsGRez21a31Aj/XUsWEmOtU7LBMqth6Y3gz0lnBaZ3aVUm6MnPjTy4I1z8kuGKd4CwmBX4gpQwO3tyjk6yD1X40FgyaLBXpakwLhqUnRc2SFrszWY3tR+03SjuPhkj6ieP1SD2MWCwj3IgV6liJixXtcB6TPFvIV7jB/Y9F9IN5TRLlAgtei/Hg2d4foB7bFTgYBkCmXPEp9yuV0yzwCqH8h6lBbTDng2PrmQTA+cqCswY5GwVavjJ6a4lKLWiXwUdJKdc3xWG7NTd3x8Bkfb2Cat5JKO2TdojqDQY0xMXjn3wkGOZezaPdcx19Eckqyyb7hmVqfLHJ7w2wYQLH0EbcUXNcvj9L4DXU+52iu3jmi+j4gj8KyKDvxoAizVZytfc+zzfgopmHbSn0AIw== X-Forefront-Antispam-Report: CIP:66.129.239.15;CTRY:US;LANG:en;SCL:1;SRV:;IPV:CAL;SFV:NSPM;H:p-exchfe-eqx-02.jnpr.net;PTR:InfoDomainNonexistent;CAT:NONE;SFS:(13230028)(4636009)(376002)(39860400002)(136003)(346002)(396003)(451199021)(40470700004)(46966006)(36840700001)(47076005)(55016003)(36860700001)(336012)(40480700001)(83380400001)(82740400003)(6916009)(70586007)(70206006)(9686003)(26005)(7696005)(107886003)(478600001)(7126003)(54906003)(6266002)(186003)(86362001)(40460700003)(2906002)(5660300002)(8936002)(8676002)(356005)(4326008)(81166007)(41300700001)(316002)(82310400005)(36900700001);DIR:OUT;SFP:1102; X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-OriginalArrivalTime: 31 May 2023 20:02:40.8876 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 6bd83869-71d6-4c70-fa91-08db6211fd85 X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4;Ip=[66.129.239.15];Helo=[p-exchfe-eqx-02.jnpr.net] X-MS-Exchange-CrossTenant-AuthSource: BN8NAM12FT099.eop-nam12.prod.protection.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Anonymous X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM4PR05MB10170 X-Proofpoint-GUID: 3Nan75dF_9ZUy9i4t75VXO6238aAEwkq X-Proofpoint-ORIG-GUID: 3Nan75dF_9ZUy9i4t75VXO6238aAEwkq X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.957,Hydra:6.0.573,FMLib:17.11.176.26 definitions=2023-05-31_14,2023-05-31_03,2023-05-22_02 X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 lowpriorityscore=0 phishscore=0 bulkscore=0 adultscore=0 malwarescore=0 impostorscore=0 priorityscore=1501 suspectscore=0 mlxlogscore=504 clxscore=1011 mlxscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2304280000 definitions=main-2305310170 X-Rspamd-Queue-Id: 4QWgD631czz3jtX X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:22843, ipnet:67.231.152.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > the loader program. You may also have to disable the lua build, since it= uses more stack and is just a smidge > larger than the forth build. _simp will be the smallest of them > all. On my system, without bearssl, I see: Back when I first did the LOADER_VERIEXEC bits, I found lua pushed things over the edge. We use 4th anyway, and will likely be stuck with it for another decade at least. > -r-xr-xr-x 3 root wheel 503808 May 22 15:25 /boot/loader_lua > -r-xr-xr-x 1 root wheel 446464 May 22 15:25 /boot/loader_4th > -r-xr-xr-x 1 root wheel 385024 May 22 15:25 /boot/loader_simp > which suggests a ~60k bump for adding forth and ~115k bump for lua. So t= he 560,000 may need to be 625,000 > which is living life on the edge for 4th, and simply too big for lua. > = > I'd be open to adding docs on this, since I don't think this option is c= urrently documented since I added it > to experiment around with a good value. My own experiments found somewhere around 550k to be the limit. > And no, I really do not want to support 'loadable modules'. BIOS > booting is on the way out, and people = > that want to do complex stuff in the boot loader will simply have to > do that in UEFI or maybe kboot/LinuxBoot. = > There's low RoI on adding this complexity, imho. We'd be better off, > imho, making things like the graphics = > console optional since the fonts and code for that free up about 30k > in stupid experiments that I've done Yes. For those of us with serial only consoles, the graphics stuff is pure overhead. > Without the extras and ZFS, you might have bearssl and lua together even= ... FWIW our i386 loader with BEARSSL and LOADER_VERIEXEC and 4th rather than lua is 312K I can get that down to 308K by dropping LOADER_EXT2FS_SUPPORT which I am pretty sure we don't need. If I enable lua and disable 4th, the loader is still only 352K in our stable/12 branch and 364K in main I just did a quick test on a VM - that loader_lua was able to load kernel ok, so looks promising. Of course we have 8k lines of 4th that would need translating to lua before I could be sure. --sjg From nobody Wed May 31 20:41:23 2023 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 4QWh4w3kWFz4XZcl for ; Wed, 31 May 2023 20:41:36 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWh4v6bHZz3nvx for ; Wed, 31 May 2023 20:41:35 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-96fdc081cb3so910167966b.2 for ; Wed, 31 May 2023 13:41:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1685565694; x=1688157694; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=IJiJMDHifhjfAnxkSl3h41qlJj+GsqhZ2BkYK7rLGdg=; b=oHtTlcoBzIwfR7SEo3bNvYHcBjwPwEnGtnNwE2Hs7YQQIo3DFczFYN9NPGoUNodh2X Zz5WowkOzEHIUd+NKnHjurvRLLt33ZSo+rxOw0LZqe0LwPBbXEah/c05HAeSh38TbcZl ML9A/VToHY7De0EnvspMJRGDbD1DE1aj/ZP3PJsiVhSOTbLdmQQJk5/KCvTHG14bWRaJ Rszt/pxYFnG1n5RG/VclWTKlAqmYZyfmBMNojc/QywB4E9cMO/wEv5PDFHdOe/SYvXKE OlEFvisHKtmd6D4dP/DsrDQzZ3PQ7GMITpreJYAQ1o3MWNY5Loc1nt39EVvvclOSa+jO ApNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685565694; x=1688157694; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=IJiJMDHifhjfAnxkSl3h41qlJj+GsqhZ2BkYK7rLGdg=; b=XmEGHa01Eq5JHARCcG33RJefEmzFm4gW64ZVP4BK2uAyOfBABQ3AErBkae5yLNBHAO pw5JV8TKnPnkKxEfePPfRxl3ncDjK+Y4JyvzaD/QCWomHFnySA6fqKdcFiZc4JZU1uBD SwbcTPAu+fvHlHwlD61tg4k3+GPiKOw73rx2+zPNPodEqmVETGpXgtWUNes04U6Jj2kO dzej/LGnuc1S2YvvzU10MBH/yZo98JXN1dkLvgtYLr4vG0VG89TSfBypKO+uAlE8lwaI qJfNm5w/f51pzBgxLhzif0zxSoCUKUMzF7rHtAPpX+mbelMtMBjUkdxsRIAtXQt1jPrZ b22Q== X-Gm-Message-State: AC+VfDzW6nWb3BcjXCy/4z8LOGS2+QZDM5ZC+paXJU8cRKnxY8+zJ94Y OJy1eLwikHCmcaIy0zG11xD+QO8cS4yQm/5u6zzU+1TB6cEJtx5B X-Google-Smtp-Source: ACHHUZ74fzBLazCdRoRwF8Hi4QMBA9/aSduHpBYu+AJ0hBguvVujZVgiqHMLRcdh+ERT4gp6HERM83VXhMBSGDHb7g0= X-Received: by 2002:a17:907:2d9f:b0:973:ff4d:d01e with SMTP id gt31-20020a1709072d9f00b00973ff4dd01emr6138663ejc.31.1685565694536; Wed, 31 May 2023 13:41:34 -0700 (PDT) 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 References: <20230529105854.1903226d@thor.intern.walstatt.dynvpn.de> <20230531213026.275c4eaf@ernst.home> In-Reply-To: <20230531213026.275c4eaf@ernst.home> From: Warner Losh Date: Wed, 31 May 2023 14:41:23 -0600 Message-ID: Subject: Re: WITH_BEARSSL: -8112 bytes available To: garyj@gmx.de Cc: FreeBSD User , FreeBSD CURRENT Content-Type: multipart/alternative; boundary="0000000000007806f905fd035842" X-Rspamd-Queue-Id: 4QWh4v6bHZz3nvx X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --0000000000007806f905fd035842 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, May 31, 2023 at 1:30=E2=80=AFPM Gary Jennejohn wrote= : > On Wed, 31 May 2023 12:15:12 -0600 > Warner Losh wrote: > > [SNIP irrelevant text] > > > And no, I really do not want to support 'loadable modules'. BIOS bootin= g > is > > on the way out, and people > > that want to do complex stuff in the boot loader will simply have to do > > that in UEFI or maybe kboot/LinuxBoot. > > So, what exactly does "BIOS booting is on the way out" mean? I have four > computers which use BIOS booting. Three are too old to support UEFI and > the other one I simply set to BIOS booting out of habit. > New computers aren't supporting it. Its days are numbered. It's longevity i= s much shorter than UEFI's. These are all indisputable. I'm not planning on dropping it in 15, but the number of people that are using it is a declinin= g group over time. Time spent making EFI more effective will affect more people. That's what I mean. So I don't want to sink a ton of time into it. > The only computer I have which uses UEFI is a laptop which was already > set up to use UEFI and I was too lazy to change it. > > > There's low RoI on adding this complexity, imho. We'd be better off, > imho, > > making things like the graphics > > console optional since the fonts and code for that free up about 30k in > > stupid experiments that I've done > > (it's hard since vidconsole has a lot of calls into the graphics system > > that aren't optional and easy to disable, > > so I've had to do hack and slash to produce a super ugly result that is > > only suggestive of the final savings): > > -rw-r--r-- 1 imp imp 352256 May 31 12:04 loader_simp > > I don't know if I slashed too much, or not enough since the code is > rather > > hard to separate out, so if you > > really wanted to go down this path, it would take a lot of work and > patient > > understanding to make it so with > > the low end of savings 20k and the high end on the order of maybe 40k. > > > > There's likely other ways to conserve space. We've not had space issues > > with loader, et al, in the past, > > so it's not well setup for subsetting. Though the different filesystem > > support might also net you a fair amount: > > LOADER_NET_SUPPORT?=3D yes > > LOADER_NFS_SUPPORT?=3D yes > > LOADER_TFTP_SUPPORT?=3D yes > > LOADER_CD9660_SUPPORT?=3D yes > > LOADER_EXT2FS_SUPPORT?=3D yes > > LOADER_MSDOS_SUPPORT?=3D yes > > LOADER_UFS_SUPPORT?=3D yes > > LOADER_GZIP_SUPPORT?=3D yes > > LOADER_BZIP2_SUPPORT?=3D yes > > as would compiling w/o ZFS, which uses its own method (eg > > WITHOUT_LOADER_ZFS). Tuning the loader > > at this level does start to get into the weeds a bit, but can offer ~40= k > > savings turning off all but NET and UFS: > > -rw-r--r-- 1 imp imp 344064 May 31 12:11 loader_simp > > you get even about ~100k when you disable ZFS support with > > -DWITHOUT_LOADER_ZFS: > > -rw-r--r-- 1 imp imp 241664 May 31 12:12 loader_simp > > (both of these are with the graphics console enabled without the silly > > hacks to see how much that takes up). > > Without the extras and ZFS, you might have bearssl and lua together > even... > > > > Hope this helps. > > > > This is interesting information. > Thanks! Warner --0000000000007806f905fd035842 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, May 31, 2023 at 1:30=E2=80=AF= PM Gary Jennejohn <garyj@gmx.de> = wrote:
On Wed, 3= 1 May 2023 12:15:12 -0600
Warner Losh <imp@bsd= imp.com> wrote:

[SNIP irrelevant text]

> And no, I really do not want to support 'loadable modules'. BI= OS booting is
> on the way out, and people
> that want to do complex stuff in the boot loader will simply have to d= o
> that in UEFI or maybe kboot/LinuxBoot.

So, what exactly does "BIOS booting is on the way out" mean?=C2= =A0 I have four
computers which use BIOS booting.=C2=A0 Three are too old to support UEFI a= nd
the other one I simply set to BIOS booting out of habit.

New computers aren't supporting it. Its days are numb= ered. It's longevity is
much shorter than UEFI's. These a= re all indisputable. I'm not planning on
dropping it in 15, b= ut the number of people that are using it is a declining
group ov= er time. Time spent making EFI more effective will affect more
pe= ople. That's what I mean. So I don't want to sink a ton of time int= o it.
=C2=A0
The only computer I have which uses UEFI is a laptop which was already
set up to use UEFI and I was too lazy to change it.

> There's low RoI on adding this complexity, imho. We'd be bette= r off, imho,
> making things like the graphics
> console optional since the fonts and code for that free up about 30k i= n
> stupid experiments that I've done
> (it's hard since vidconsole has a lot of calls into the graphics s= ystem
> that aren't optional and easy to disable,
> so I've had to do hack and slash to produce a super ugly result th= at is
> only suggestive of the final savings):
> -rw-r--r--=C2=A0 1 imp=C2=A0 imp=C2=A0 352256 May 31 12:04 loader_simp=
> I don't know if I slashed too much, or not enough since the code i= s rather
> hard to separate out, so if you
> really wanted to go down this path, it would take a lot of work and pa= tient
> understanding to make it so with
> the low end of savings 20k and the high end on the order of maybe 40k.=
>
> There's likely other ways to conserve space. We've not had spa= ce issues
> with loader, et al, in the past,
> so it's not well setup for subsetting. Though the different filesy= stem
> support might also net you a fair amount:
> LOADER_NET_SUPPORT?=3D=C2=A0 =C2=A0 yes
> LOADER_NFS_SUPPORT?=3D=C2=A0 =C2=A0 yes
> LOADER_TFTP_SUPPORT?=3D=C2=A0 =C2=A0yes
> LOADER_CD9660_SUPPORT?=3D yes
> LOADER_EXT2FS_SUPPORT?=3D yes
> LOADER_MSDOS_SUPPORT?=3D=C2=A0 yes
> LOADER_UFS_SUPPORT?=3D=C2=A0 =C2=A0 yes
> LOADER_GZIP_SUPPORT?=3D=C2=A0 =C2=A0yes
> LOADER_BZIP2_SUPPORT?=3D=C2=A0 yes
> as would compiling w/o ZFS, which uses its own method (eg
> WITHOUT_LOADER_ZFS). Tuning the loader
> at this level does start to get into the weeds a bit, but can offer ~4= 0k
> savings turning off all but NET and UFS:
> -rw-r--r--=C2=A0 1 imp=C2=A0 imp=C2=A0 344064 May 31 12:11 loader_simp=
> you get even about ~100k when you disable ZFS support with
> -DWITHOUT_LOADER_ZFS:
> -rw-r--r--=C2=A0 1 imp=C2=A0 imp=C2=A0 241664 May 31 12:12 loader_simp=
> (both of these are with the graphics console enabled without the silly=
> hacks to see how much that takes up).
> Without the extras and ZFS, you might have bearssl and lua together ev= en...
>
> Hope this helps.
>

This is interesting information.

Thanks= !

Warner=C2=A0
--0000000000007806f905fd035842-- From nobody Thu Jun 1 00:00:28 2023 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 4QWmVP2Xplz4Xrpm; Thu, 1 Jun 2023 00:00:29 +0000 (UTC) (envelope-from salvadore@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (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 "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWmVP0vgyz463j; Thu, 1 Jun 2023 00:00:29 +0000 (UTC) (envelope-from salvadore@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685577629; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc; bh=BZDboLs55RS+2CA6Wp814zfKjcwV1ra3lerb9u3JLZI=; b=Ug/wWhRwqGQFAuUrgwT3oBoXaLiPDRtp/L0co+p9rSLgc1OuUUi1Rk030TAFda7iMn2Yug iJMDxXoqpmT9Qa7Y5ZjzLruc33cKDxgYybAyeriFCJ3eJ0eiQPoYkrwgnY5wtWOZZBnea4 FX48Kcp9LhsVy6QgZ+Q7s77Ihc9jlQ7dz6ZfLKFcTfQXCWELM6T5kN8fY7fbdAZbwJFOV5 nMUBwWKYLV+M1Bw6F3J/6qC4+p0cYvWapYv6eJ6ipx3zLkL4wh7U/XMD78YBjdDzPVPRDW vVmLueUvbAhvyxTLspbHVSbpZn0gM64GHRfWQcAgHCL4Nr+RJfecPFekSxNvmA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685577629; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc; bh=BZDboLs55RS+2CA6Wp814zfKjcwV1ra3lerb9u3JLZI=; b=R7JnTuWhx4x3bxn4CNmmNJxR2taz2FgYJVFxTXvzJs0SR9yc4vfcOcMgQxuObXv05S9cHw BXVJBIFC1TEEgIxkD3ldJKiw5oSmd0sZ1IoFNC0bxsa+8A/n28TUbWtPNEUp8fJZrQvPM8 1o9W56o/ZGg8TkfzNbkqPzl3POUhsutkWlZWMVW73Se897S8rtbJPVPZrU5NyeQPQ4L4eM VGkYEdbQk2jXfgvoenDcbnrQgvKt44BXUSVOBC7NH2znQeWBuCKfZrYb5hPHy312AqWssW 2HLjPPX11bodErlYhTA/DTzXGHSCznxFks24iDWFmwvuK8+VUCmAxXXvkxem9w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1685577629; a=rsa-sha256; cv=none; b=EwsPCVL7RZ9XMLH2wclnuyOtYcTfM+tZ4ol+6MRabMzHHbWjPZ7D9R1HS6MUHFqOT6eon9 6gB/fyPpwgiFDPPQtUiMDgdtrtI2Cjw3UqmX7XgA6Fpp0gQADoSQoH9NiV5SuET97lBvHR RtlqegzxByvtrB2uFFRD8wzjEKE6crmsFC8ia83lwjAghQkl0NoSk+CTAjYGW/2RMt6Bf/ lTr82pAgJm+603wng543NImaoWjhXCGKkt87wHuES8LigoyAJ3V6BJ++25/Kg+lvoL1ZQM Z9PKErBSoDTqkL4ILt4byP2FPSs2WTNEMFtgifb5UKFy11WWRSltythk/A7Z2Q== Received: by freefall.freebsd.org (Postfix, from userid 1472) id D980B91B8; Thu, 1 Jun 2023 00:00:28 +0000 (UTC) To: freebsd-status-calls@FreeBSD.org Subject: Call for 2023Q2 status reports Cc: freebsd-current@FreeBSD.org,freebsd-hackers@FreeBSD.org,devsummit@FreeBSD.org,info@bsdcan.org,soc-students@FreeBSD.org,soc-mentors@FreeBSD.org Message-Id: <20230601000028.D980B91B8@freefall.freebsd.org> Date: Thu, 1 Jun 2023 00:00:28 +0000 (UTC) From: Lorenzo Salvadore X-ThisMailContainsUnwantedMimeParts: N 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 Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is June, 30th 2023 for work done since the last round of quarterly reports: April 2023 - June 2023. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2023-04-2023-06/ (create it if it is missing); * submit a pull request at . You should put your reports in the directory doc/website/content/en/status/report-2023-04-2023-06/ (create it if it is missing); * send an email to status-submissions@FreeBSD.org including your report. An AsciiDoc template is available at . We look forward to seeing your 2023Q2 reports! Thanks, Lorenzo Salvadore (on behalf of status@) From nobody Thu Jun 1 02:42:05 2023 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 4QWr4y6qSjz4Y4mm for ; Thu, 1 Jun 2023 02:42:10 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWr4y4rgHz4M34; Thu, 1 Jun 2023 02:42:10 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pf1-x435.google.com with SMTP id d2e1a72fcca58-64d2f99c8c3so264012b3a.0; Wed, 31 May 2023 19:42:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685587329; x=1688179329; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=OwSiQF9UQJApCeN2Y5YAuDRHfN/jP687lJaN3drqT9U=; b=VwX9MbK41Ozw7/UsQro9yYWjqreXxqqfM1Z1ppuL9MdIZdkWsaj+j0IvCLv5NXgnQt 5oShVQ85VyA7ai5MIMlCQss+oKaD31yi7hUNz2VuAAZM0S8NJguiNVJwGqwXaEFaF2SN 3C2TyuyZKkfzSKJX3vJSm4qxhv2IM2q8JQfU61M3fwmMnRptYjcBvtem+v7UPN/wmcwN a52mMwSR1KfzCts8Q2KPvJvkt/1lF0MuHvwJi4vWj/3+Vqf0mYLJkAIT1AyIvIQAYKtz cnxKF1RK0//ilCJgEKgpDWU6jIqd0gAJcQKNqoJreonzrxFtkjKdfABt41QpHh7tcXnZ vaaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685587329; x=1688179329; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=OwSiQF9UQJApCeN2Y5YAuDRHfN/jP687lJaN3drqT9U=; b=PqEsj110e6qYOHgBAnSk3N/Fg6KrB3R8vap+ZPjq0KnsWc94eFzNev3y96zA0XCS1d ejSRViYCGSGJ9xNLBka6rFXWvvLHymap37hf6bLc2sEc3Q15NEw/bFohCi/UYIJXKy13 y1TXe5vEvgpx/6HdJ0pHrkuGjd5CNTwNQomTOn/068jlwt/Vnt6Jp1seyMIuZK4izcHQ kj1c+fmVzR/mvRbb/pHbwHkMEYcp74gcm9T1FWpLe5eVPfanTwLG8hVp/rhv2+E9/4Pd 4iUaRKUDEx9JgBQAnnZVuYdpxNckhYfEdg9bp/R5GZaNVbLFCyDNP2zKoNtdlgtPBQgk 7wLg== X-Gm-Message-State: AC+VfDzsXIX6PtJqW08hP7o7XRfPmbzN6MJ6MkyV8JcuUJ2eCCXFoSsG j71MCBt6jZp706i7a927B0e/Ms+BmaIhOA== X-Google-Smtp-Source: ACHHUZ7rtE3/Ou7/iwxQWpfT+tUQaUle2WofDUpNKPFHC7RxeJw55rMY58eJ1TDJ2r2hfevM3H+h8w== X-Received: by 2002:a05:6a00:174c:b0:643:98cb:ec1 with SMTP id j12-20020a056a00174c00b0064398cb0ec1mr7582389pfc.0.1685587328663; Wed, 31 May 2023 19:42:08 -0700 (PDT) Received: from smtpclient.apple (c-73-19-52-228.hsd1.wa.comcast.net. [73.19.52.228]) by smtp.gmail.com with ESMTPSA id x21-20020aa784d5000000b0063b86aff031sm3988916pfn.108.2023.05.31.19.42.07 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 May 2023 19:42:07 -0700 (PDT) From: Enji Cooper Message-Id: <3F4CBAD1-3C59-4A76-BDB2-F53A345BBB1A@gmail.com> Content-Type: multipart/signed; boundary="Apple-Mail=_C1F58AB8-E213-4CBF-B735-F42D49AE8532"; protocol="application/pgp-signature"; micalg=pgp-sha256 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.120.41.1.3\)) Subject: Re: "make hierarchy" from main tree breaks c++ headers on older branches with unclear errors if "make install world" is interrupted Date: Wed, 31 May 2023 19:42:05 -0700 In-Reply-To: <8CD00413-E6B3-4DBA-8A71-CAFA647DF2FF@FreeBSD.org> Cc: FreeBSD Current To: Dimitry Andric References: <0DA92266-62F8-439E-9C56-44106A6B0073@FreeBSD.org> <8CD00413-E6B3-4DBA-8A71-CAFA647DF2FF@FreeBSD.org> X-Mailer: Apple Mail (2.3696.120.41.1.3) X-Rspamd-Queue-Id: 4QWr4y4rgHz4M34 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_C1F58AB8-E213-4CBF-B735-F42D49AE8532 Content-Type: multipart/alternative; boundary="Apple-Mail=_5EC10A4A-3679-4F15-847E-EC6F9FE88D22" --Apple-Mail=_5EC10A4A-3679-4F15-847E-EC6F9FE88D22 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On May 31, 2023, at 2:06 AM, Dimitry Andric wrote: >=20 > On 31 May 2023, at 01:07, Enji Cooper > wrote: =E2=80=A6 >> That=E2=80=99s a fair point, however, given that this follows the = standard installation workflow=E2=80=A6 >> 1. etcupdate pre-run. >> 2. install kernel >> 3. reboot >> 4. make installworld >> 5. etcupdate post-run >> =E2=80=A6 this could surprise end-users. In particular, the C++ = compiler will be broken between step 1 and step 4. >=20 > How so? The deletion of the old __string file is done as part of = installworld, i.e. in step 4, not in any of the earlier steps. The only = case where you can have problems is when you start installworld, let it = run until it has completed its distrib-cleanup target, and then = interrupt it before it can install the new headers. No wait =E2=80=94 you=E2=80=99re right. The directories aren=E2=80= =99t created until =E2=80=9Cmake installworld=E2=80=9D is run so this is = a short-lived issue =E2=80=94 it impacts folks who run =E2=80=9Cmake = hierarchy=E2=80=9D out of band, but we=E2=80=99re an extreme exception, = not the norm. Thanks for helping me figure this out :). Cheers, -Enji --Apple-Mail=_5EC10A4A-3679-4F15-847E-EC6F9FE88D22 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
On = May 31, 2023, at 2:06 AM, Dimitry Andric <dim@FreeBSD.org> = wrote:

On 31 May 2023, = at 01:07, Enji Cooper <yaneurabeya@gmail.com> = wrote:

=E2=80=A6

That=E2=80=99s a fair point, however, given = that this follows the standard installation workflow=E2=80=A6
1. etcupdate pre-run.
2. install kernel
3. reboot
4. make installworld
5. = etcupdate post-run
=E2=80=A6 this could surprise = end-users. In particular, the C++ compiler will be broken between step 1 = and step 4.

How so? The = deletion of the old __string file is done as part of installworld, i.e. = in step 4, not in any of the earlier steps. The only case where you can = have problems is when you start installworld, let it run until it has = completed its distrib-cleanup target, and then interrupt it before it = can install the new headers.

= No wait =E2=80=94 you=E2=80=99re right. The directories aren=E2=80=99= t created until =E2=80=9Cmake installworld=E2=80=9D is run so this is a = short-lived issue =E2=80=94 it impacts folks who run =E2=80=9Cmake = hierarchy=E2=80=9D out of band, but we=E2=80=99re an extreme exception, = not the norm.
Thanks for helping me figure this = out :).
Cheers,
-Enji
= --Apple-Mail=_5EC10A4A-3679-4F15-847E-EC6F9FE88D22-- --Apple-Mail=_C1F58AB8-E213-4CBF-B735-F42D49AE8532 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEtvtxN6kOllEF3nmX5JFNMZeDGN4FAmR4BX0ACgkQ5JFNMZeD GN4ENxAAjoHcPrqjKSYTFyUGop3TlYwz/zBnn9F605oi332oVEptSaf0VJmvMyrY iDWw90oCt3NmeTJrdEYqO2+A4DVGf2X6pPHN/5ZLykxEW422tSaJPwtxJRYBqS+s nhV0PbtzVjbgs/H9lZL9ueGPEWQvq0C9QDcozrGJB5hppI6F83F3aE5BUF+ninX0 wpXnVs6xSh07AVQWQHON0k0FKfl6o07fJtSD8B2yhc7QSN15V37dKWVqOor+3BLB aGuk0tjxunLH94GG7Oc6yd0820MRO8rmxX/AQXnNRSC1qtlBaLA7+alO57KA3JlO Yi7sMWSh3JlojQdiKx1ebXlQagU4HzlkfLsoGfuk4leao16KHlX/DeDYM/fHq3vB cn7VHMSgzIvAVYR41+0GbvHc8k8BB1ElvWFPjBmLCsn8U5F3d2fymoQu7HqTAKSH hCQXBvA1fx1SxX4OO3Qb3zf5qjUvAMQVsfy3RytBoC/S7qu6BRWnSODu0a7xmbCf Ael04VrEOnfScy066VRXPzqB9lq/65ycbQRycuB+Sudnc+PlPvm+jg6/E5/HD0/2 I7Y/o+M3GFPM54An5zzR54Q0JlRGGDvSK+hKLqZE5pjx5EmVH8PPzxWe06EQbLEY 8rnO/6IDykzFSdjkSB8VUHm1qUQuaHyGn6zeFM+ny2OWGqsPN5c= =EOCb -----END PGP SIGNATURE----- --Apple-Mail=_C1F58AB8-E213-4CBF-B735-F42D49AE8532-- From nobody Thu Jun 1 08:30:10 2023 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 4QWzpg6KCrz4Y5L3 for ; Thu, 1 Jun 2023 08:30:19 +0000 (UTC) (envelope-from garyj@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QWzpg2t6Mz3pB3 for ; Thu, 1 Jun 2023 08:30:19 +0000 (UTC) (envelope-from garyj@gmx.de) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1685608215; i=garyj@gmx.de; bh=Dpb4C+/yXDqPLzg6iBp4BE195UXl3q1jFE+WEG4Ai/8=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:In-Reply-To:References: Reply-To; b=jkRsYa+BgVkM4iNbEM9AUddxmymGZJl+xX8lpKNc9d5+4Xw1cGusuychycAS7StEM mELto9gtvN+gCi93rf+IJfNbPWmckSlPdA/nRpcVprm6+5e93D5VJwFrCeM3est3bq BRVnHDe1JC3CccJVKsp6cwP/7GymNNiU30SQHGXkyvrBoZgpdSSKTalcW4gcwzp/Do hniF1RX9OB9+RBNNMrtY7NfG0JPDgS0WwwHkwvwdlLM7q4ZyiUa92Zrx2Fzi8Fjatj h8K8K0dO6tKc6IfvpI/hCsLuO7SHPuzUWLEfNHGwH6nOVi3niviB2Pertww65GMCR0 68RLB1iN0oZqQ== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from ernst.home ([91.59.239.47]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1M2f9b-1q4MiO2dId-004D30; Thu, 01 Jun 2023 10:30:15 +0200 Date: Thu, 1 Jun 2023 08:30:10 +0000 From: Gary Jennejohn To: Warner Losh Cc: FreeBSD CURRENT Subject: Re: WITH_BEARSSL: -8112 bytes available Message-ID: <20230601103010.69f92495@ernst.home> In-Reply-To: References: <20230529105854.1903226d@thor.intern.walstatt.dynvpn.de> <20230531213026.275c4eaf@ernst.home> Reply-To: garyj@gmx.de X-Mailer: Claws Mail 3.19.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:fE093BEt+CF/JkT1uCogaZm/8FjRmxhVg/4xT5D4S3Y6lWBgnLI PVAVjaQxgPYqQG0sMGZVnIrvDUbXQaX2p8Xboet9l2ZiBfGfV25gPKwVw1e+JTQi9SjKdFZ oKIwXw6RA2EBzoNZXheL4u23yxf1Z939ExNu6eCXjtfRc4IgtfuTHLw1UVAH+OlrykOAq/T Z9IpQ1smrOGNQy9MterDg== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:Ws+CzfXgkks=;Qfh//NRfMUjnYVmYDCT7JazIO8l gVDhSX2MEXyyh0FvDmUJ+j1X1r0964E2ue/GjSFN+LksAv8GKQa5inOBj0pONt0RSxozFtOrY +ciWr9BwU7h+M+daJAG3qrqkfM7D/QPIT2xYWPtkBkPffEvF9t1LZOcXKSJ7hXAlxBHe2ztnD GmJ+z6YiruYQCAoEGuQ9H88oHUu8NM0zAndTGdF77Is9lq38mrpd9Lxx6xH96jxs2PSlpfBrU 7HRzLQBDMYMeo9BpDpPNYbhyfxr7egedZwAFToe4SD+M/uviQTQfp3aHU76pqHg9TcuEXoHj8 jCdLW/fCqyNkXzFlBJIdz7HpgoyUpevh1b7epTD7zkrUXZjcL0RLACHnUZ5MM1JX6j0NbZiw5 T+74jCa4TUETrPvFVbp6WwvFzyMVVZ9FwtsvejUD7qjNUmZ5atefgsUWq2efFokNO8gTilY3V aiDOdJ7VPUS1HtaoRMbDFBVEDlnDU0dgOTk5xuxMsj2PL0A2E6xT2l9zOdGnjz9aUmTQWJPO2 Uh7f9YEwB1s7HwxpwddkdAS89XUf72ilZAuCRN70pO2OJ72GqPsLOAOoVMiPCW18O38kTM2Va b2KWiND036Q+aaLF/YWL3GQBoF/d4dvTrfv9WLvbxAtifprWGvlmFjehDS4JeNo0cWQaY0b28 LAtCx/e2sdklFA0Q8ocGSdSI/ASX/ZUlX3JnneMU5kbDk9BPfchuk50MdnuNgGNSXwm2RlccV 1GT7Tmbs0IsApy4gaOMR4vx9VQQuiizuZ/xIKLcjj8uJ5KUT0acWrD+WkJK/XtZaq8qRT/+0P K6VwRR9E9UIpaUoWspqzSOIA3Mnv8LFh6iGcwEQHTDtGaTiVBx95MuasONNHb+E13bG3n2kAP 568+jdX7+ot6ucvCtqJoCutFW19UjETA7MuW37y3+SmuXeEOuhECoSfEFx1tdk8mBTbRCoyeh ioieDw== X-Rspamd-Queue-Id: 4QWzpg2t6Mz3pB3 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Wed, 31 May 2023 14:41:23 -0600 Warner Losh wrote: > On Wed, May 31, 2023 at 1:30?PM Gary Jennejohn wrote: > > > On Wed, 31 May 2023 12:15:12 -0600 > > Warner Losh wrote: > > > > [SNIP irrelevant text] > > > > > And no, I really do not want to support 'loadable modules'. BIOS boo= ting > > is > > > on the way out, and people > > > that want to do complex stuff in the boot loader will simply have to= do > > > that in UEFI or maybe kboot/LinuxBoot. > > > > So, what exactly does "BIOS booting is on the way out" mean? I have f= our > > computers which use BIOS booting. Three are too old to support UEFI a= nd > > the other one I simply set to BIOS booting out of habit. > > > > New computers aren't supporting it. Its days are numbered. It's longevit= y is > much shorter than UEFI's. These are all indisputable. I'm not planning o= n > dropping it in 15, but the number of people that are using it is a decli= ning > group over time. Time spent making EFI more effective will affect more > people. That's what I mean. So I don't want to sink a ton of time into i= t. > OK, that makes sense. If it disappears after 15 I guess I'll have to maintain it myself. Should be doable. =2D- Gary Jennejohn From nobody Thu Jun 1 11:48:30 2023 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 4QX4Cf3QQPz4YMHw for ; Thu, 1 Jun 2023 11:48:46 +0000 (UTC) (envelope-from tsoome@me.com) Received: from mr85p00im-ztdg06011901.me.com (mr85p00im-ztdg06011901.me.com [17.58.23.198]) (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 4QX4Cf0mC2z48ty for ; Thu, 1 Jun 2023 11:48:46 +0000 (UTC) (envelope-from tsoome@me.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=1a1hai; t=1685620123; bh=K6vwHGhfkSkuJzMjUqjFS0zm0GD89FTpHBM/HfPlEk8=; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:To; b=kBdjiVNE3XvFs99yxuP/02iOqV0jEf5NbTywtLetMDbWui8rTqCKcRgaA5DKv3MVk ob2av30ybEGgaJ4DYdybPyr4xLKga4tcfOxFnymtSIOEvYSYButN31TZ0A3I/qctmI TPL9ilueIVg2tCNy7UtIzbN0fBFqhzBVBZGRb/B+RNlV92SZI/+t3GZ7Mp/RIpdaZm jjCydoLfDe5XWIPKJapCvcgP0i6nFf74QENoyNJ+OjWatxCDaF7uIF+3kiRI7YNA0v UZYphq3aRNXVEZwaEFC2LOe2+TLpgRvOmcBZ3HE07yEUSbTl7e80AuxAjo/zPvrVgy COYEujoOaXZzw== Received: from smtpclient.apple (mr38p00im-dlb-asmtp-mailmevip.me.com [17.57.152.18]) by mr85p00im-ztdg06011901.me.com (Postfix) with ESMTPSA id C84F0900129; Thu, 1 Jun 2023 11:48:42 +0000 (UTC) From: Toomas Soome Message-Id: <3A0E5086-8397-45AD-8312-23B8CC5104CE@me.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_8C26DF97-1C6A-4917-8D0C-D47BCE962D69" 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 \(3731.600.7\)) Subject: Re: WITH_BEARSSL: -8112 bytes available Date: Thu, 1 Jun 2023 14:48:30 +0300 In-Reply-To: <20230601103010.69f92495@ernst.home> Cc: Warner Losh , FreeBSD CURRENT To: garyj@gmx.de References: <20230529105854.1903226d@thor.intern.walstatt.dynvpn.de> <20230531213026.275c4eaf@ernst.home> <20230601103010.69f92495@ernst.home> X-Mailer: Apple Mail (2.3731.600.7) X-Proofpoint-ORIG-GUID: 0oP4I5czwjpCiSMWB9DOTAyciNCY3bRZ X-Proofpoint-GUID: 0oP4I5czwjpCiSMWB9DOTAyciNCY3bRZ X-Proofpoint-Virus-Version: =?UTF-8?Q?vendor=3Dfsecure_engine=3D1.1.170-22c6f66c430a71ce266a39bfe25bc?= =?UTF-8?Q?2903e8d5c8f:6.0.425,18.0.816,17.11.62.513.0000000_definitions?= =?UTF-8?Q?=3D2022-01-18=5F01:2022-01-14=5F01,2022-01-18=5F01,2021-12-02?= =?UTF-8?Q?=5F01_signatures=3D0?= X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 clxscore=1011 suspectscore=0 malwarescore=0 phishscore=0 mlxlogscore=801 adultscore=0 bulkscore=0 mlxscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2212070000 definitions=main-2306010105 X-Rspamd-Queue-Id: 4QX4Cf0mC2z48ty X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:714, ipnet:17.58.16.0/20, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_8C26DF97-1C6A-4917-8D0C-D47BCE962D69 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On 1. Jun 2023, at 11:30, Gary Jennejohn wrote: >=20 > On Wed, 31 May 2023 14:41:23 -0600 > Warner Losh > wrote: >=20 >> On Wed, May 31, 2023 at 1:30?PM Gary Jennejohn wrote: >>=20 >>> On Wed, 31 May 2023 12:15:12 -0600 >>> Warner Losh wrote: >>>=20 >>> [SNIP irrelevant text] >>>=20 >>>> And no, I really do not want to support 'loadable modules'. BIOS = booting >>> is >>>> on the way out, and people >>>> that want to do complex stuff in the boot loader will simply have = to do >>>> that in UEFI or maybe kboot/LinuxBoot. >>>=20 >>> So, what exactly does "BIOS booting is on the way out" mean? I have = four >>> computers which use BIOS booting. Three are too old to support UEFI = and >>> the other one I simply set to BIOS booting out of habit. >>>=20 >>=20 >> New computers aren't supporting it. Its days are numbered. It's = longevity is >> much shorter than UEFI's. These are all indisputable. I'm not = planning on >> dropping it in 15, but the number of people that are using it is a = declining >> group over time. Time spent making EFI more effective will affect = more >> people. That's what I mean. So I don't want to sink a ton of time = into it. >>=20 >=20 > OK, that makes sense. If it disappears after 15 I guess I'll have to > maintain it myself. Should be doable. >=20 >=20 I have this change in my queue: https://reviews.freebsd.org/D40375 toomas --Apple-Mail=_8C26DF97-1C6A-4917-8D0C-D47BCE962D69 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

On 1. = Jun 2023, at 11:30, Gary Jennejohn <garyj@gmx.de> wrote:

On Wed, 31 May 2023 = 14:41:23 -0600
Warner = Losh <imp@bsdimp.com> = wrote:

On Wed, May 31, 2023 at 1:30?PM Gary Jennejohn = <garyj@gmx.de> wrote:

On Wed, 31 = May 2023 12:15:12 -0600
Warner Losh <imp@bsdimp.com> = wrote:

[SNIP irrelevant text]

And = no, I really do not want to support 'loadable modules'. BIOS = booting
is
on the way out, = and people
that want to do complex stuff in the boot loader will = simply have to do
that in UEFI or maybe = kboot/LinuxBoot.

So, what exactly does "BIOS booting = is on the way out" mean?  I have four
computers which use BIOS = booting.  Three are too old to support UEFI and
the other one I = simply set to BIOS booting out of habit.


New = computers aren't supporting it. Its days are numbered. It's longevity = is
much shorter than UEFI's. These are all indisputable. I'm not = planning on
dropping it in 15, but the number of people that are = using it is a declining
group over time. Time spent making EFI more = effective will affect more
people. That's what I mean. So I don't = want to sink a ton of time into it.


OK, that makes sense. =  If it disappears after 15 I guess I'll have to
maintain it myself. =  Should be doable.



I have = this change in my queue: https://reviews.freebsd.org/D4= 0375

toomas

= --Apple-Mail=_8C26DF97-1C6A-4917-8D0C-D47BCE962D69-- From nobody Fri Jun 2 09:56:44 2023 X-Original-To: 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 4QXdh00Ybdz4ZHvv for ; Fri, 2 Jun 2023 09:56:48 +0000 (UTC) (envelope-from garyj@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QXdgy6kdmz3QFc for ; Fri, 2 Jun 2023 09:56:46 +0000 (UTC) (envelope-from garyj@gmx.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmx.de header.s=s31663417 header.b=DMkAZuPN; spf=pass (mx1.freebsd.org: domain of garyj@gmx.de designates 212.227.17.22 as permitted sender) smtp.mailfrom=garyj@gmx.de; dmarc=pass (policy=none) header.from=gmx.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1685699805; x=1686304605; i=garyj@gmx.de; bh=FbZrVhBdosjQGLjBW22QzNk7TZwk5NzHT7muE71FYxQ=; h=X-UI-Sender-Class:Date:From:To:Subject:Reply-To; b=DMkAZuPNV2ablvHelRhiMmT8c6B1///7JJy0ExK9RmIa5XR2ngrnzC6tggmRxJjEZl5BeUB tQ4feRWf85lBfqG1mAmVRZEzaoOdS5p6qBeckFknPMkKm99HbTJVCyf2sy5LcEUUUJsjjJImb Ki6s61gEfUB9ktdMEDWfA0/h1K9unHBwcpWFIuNJidz8AMC5xTdxv2Ka4/Z0U1C9KT5pzCrYM gnm0js3V5uVNpRu6Yxsu0unFHCQDAPtou1FifSWxNzLexI7dNiKOush9fEBLcX6mI806gArdg Q9LjUwOmxlShLs2TWJKqZVzO0GCI4XYAB75g5g5XQgQbtP2kMtdw== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from ernst.home ([91.59.239.189]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1Mw9UK-1qNeGn10Fg-00s52l for ; Fri, 02 Jun 2023 11:56:45 +0200 Date: Fri, 2 Jun 2023 09:56:44 +0000 From: Gary Jennejohn To: current@freebsd.org Subject: Error building world in current Message-ID: <20230602115644.7ce88b9f@ernst.home> Reply-To: garyj@gmx.de X-Mailer: Claws Mail 3.19.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:67T8PI5K/iDRedyysY5deT0wCldEL88j95PL8G5+mRqdTp2SN4l Ixdk69fecF3ub38/kXEBo6nnhXZvvocxvuXTmPE2Pcb52W+csmgwWcLk5ZUd4eXCqpGV1Ay 3ygmi0a1nqxPLIhpdsmFTSdsr5Fxs1+WPEJOEKcHlwaZxIKv3HPsARBEeJRzvf7TE5CF8fZ OiXsrVtYOPWK7goFYJbtQ== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:An9RNlrdUxs=;tNhV93x9xI2S31unyHaHO1CamgA Eifqh6yt1ScD5NQtqiIW7Db2MKr3FHHzU6+gem5RtjAOyuZ+5HCd0AxLu2wHQiVxUkm6LpWhA ebDt7yZn67sJe6vpVUvphmQ9GVwTO6Ux+MKYPcv2K1wqArbcuHmyvWj0Nacj1VjKt6icvjrTf 141GgfJd7GhhBITSIEa0LvkmAHIw7mQNdTpF6lFmP4BT91js8oE2NYfQhR84SxZeTc7ZMzcPD DwdjkeM+XI32VXldpXGJd8RBIc0lOHSLBDOGvWUU1KExeICIxwFVQNFwUZAQD9eYOn5EVMBom Cti9jVJbgjITU11XZqt1DTb+WNiPOe46GnSsM7bnZ4Yhi3WRLVqFFL1R3q5Hwu/spX2w+Gp38 XAG7qrE0hevFBG6+IUrFy3aRwHWkLIZrrAPkwsRWRTy86K/itBlZzbqN8n0L13OZK1m1K/90N 7+X2+gW9aa+M58HvVNUypFU6OngzNzqKHw0/5SmFvoVrpj+x/8bj+0cwnxw4zLgD8Eo569Ait jKqbT4lad3DwgoTzSmOi0dZ/jCmqnuSVO20SR54nHrDKrbh41EG7NaGjYpiqRquYD2qmVU3cD rvU2Fjl3senPuxRofxUVUaXNQUGuUzchZg/GVLDog9Mo3wnoMudMuWZ9OzX0uprJBp6i+daYJ ov4SZo9BbWodqbjelypFaRVN81TgSFvhI4SHmL4uhA3vtNKeMz4CfJTtAc9hYB0fhNJ3xeFd9 +mp6yX7OexBJ4oOszvg7fctcBgwbNgDPJwphPjcye47qHTud/8KlyrH0UCZTITFVdZ2DzJxGb zUZLClxWVkVWQgg3WEfu4zzcPV4GFRrUIeW8weyxJtc5QcT5rBeJwWH7CMEpPQv5C+gA8LEzQ giFSTf/cR5XXD8gVMA2AIXYYisH4L4mswIJEO/L9et3ydB8XAT4UTmZMIct6KR8lRp560+Jv2 MYGrHoQzGU2egr7xHfttQfmmltU= X-Spamd-Result: default: False [0.21 / 15.00]; NEURAL_SPAM_MEDIUM(0.86)[0.857]; NEURAL_SPAM_SHORT(0.57)[0.567]; DMARC_POLICY_ALLOW(-0.50)[gmx.de,none]; R_SPF_ALLOW(-0.20)[+ip4:212.227.17.0/27]; R_DKIM_ALLOW(-0.20)[gmx.de:s=s31663417]; NEURAL_HAM_LONG(-0.11)[-0.114]; RCVD_IN_DNSWL_LOW(-0.10)[212.227.17.22:from]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[current@freebsd.org]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; FREEMAIL_REPLYTO(0.00)[gmx.de]; HAS_REPLYTO(0.00)[garyj@gmx.de]; ARC_NA(0.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; REPLYTO_ADDR_EQ_FROM(0.00)[]; FREEMAIL_FROM(0.00)[gmx.de]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmx.de:+]; FREEMAIL_ENVFROM(0.00)[gmx.de]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4QXdgy6kdmz3QFc X-Spamd-Bar: / X-ThisMailContainsUnwantedMimeParts: N Error building world in current: =2D------------------------------------------------------------- >>> stage 3.1: building everything =2D------------------------------------------------------------- /usr/src/sys/netlink/route/iface.c:1315:22: error: use of undeclared identifier 'if_flags' if (error =3D=3D 0 && !(if_flags & IFF_UP) && (if_getflags(ifp) & = IFF_UP)) ^ 1 error generated. =2D-- iface.o --- *** [iface.o] Error code 1 My source tree was updated just a few minutes ago and I didn't see any recent changes to iface.c. I have WITHOUT_NETLINK_SUPPORT=3D in my src.conf. =2D- Gary Jennejohn From nobody Fri Jun 2 09:59:40 2023 X-Original-To: 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 4QXdlS4LzRz4ZJdr for ; Fri, 2 Jun 2023 09:59:48 +0000 (UTC) (envelope-from garyj@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QXdlR4RBLz3h86 for ; Fri, 2 Jun 2023 09:59:47 +0000 (UTC) (envelope-from garyj@gmx.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmx.de header.s=s31663417 header.b=G0cGwSpY; spf=pass (mx1.freebsd.org: domain of garyj@gmx.de designates 212.227.17.21 as permitted sender) smtp.mailfrom=garyj@gmx.de; dmarc=pass (policy=none) header.from=gmx.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1685699986; x=1686304786; i=garyj@gmx.de; bh=XgUzeb4zGWsc1b2ipJnHrgTxUSFAvmqr6WAf7V+MoZA=; h=X-UI-Sender-Class:Date:From:To:Subject:In-Reply-To:References:Reply-To; b=G0cGwSpYQ2q84sQFvanpUtMDl9VdBH7FLet2ldv6R+wkqZB2ZkTKDRKCV1Y9yxra/MGkUkM BFFEdlFAmgawG+VQ8IVLakwD5l6vt3mJdSAd1qh8c13RLpndzB60+3aNnnj1MtqikvK/cy/fv iUiF44RPN3oDbj5IZAYC+8B3C3RshbMpbRCiHbK6IkU18nGIPjETaUogNhVdayz2gtFiARgOA xCXoR60MiNBZByKMw5gUIV8TshOUYzrUj2c7m8t6UkmSXyrfmGxU/k3pcTN9OejvVt2Afapds 73BxLtS3W4hatshaP6aD+1ksDJXJtRgcgwsmkCcNDkhOCwZPmhIg== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from ernst.home ([91.59.239.189]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MUXpQ-1pef213UfI-00QR8t for ; Fri, 02 Jun 2023 11:59:45 +0200 Date: Fri, 2 Jun 2023 09:59:40 +0000 From: Gary Jennejohn To: current@freebsd.org Subject: Re: Error building kernel in current Message-ID: <20230602115940.7c9d2f4e@ernst.home> In-Reply-To: <20230602115644.7ce88b9f@ernst.home> References: <20230602115644.7ce88b9f@ernst.home> Reply-To: garyj@gmx.de X-Mailer: Claws Mail 3.19.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:AWax73Dmahz1YwcR//vFm6Qda/kndJDWphOW3mHZ3Sxffp2YOK/ n4uSy6r7EEQNFYvK0Clzf7AOIOr9SEWtDUuX4pbLpxA7AToaYeE+YIFGx68lE49d6JfYWZz pbbIJHaWVuTuW1ln8bTaOnQJT+up79kOVb1/1YIkOKdQ/pCmF2PqbxxBwowFIiHHukId8Ds BNFGrNXjKcuiJRp+DTOwA== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:u34RM/GaVYI=;aZM5lebrHoPkkxbqWYES9tTPOTK nnN8a0X2SgatqhlxxnvYwTQ05yZpmzJu8mkJLqobPI6iIabh9cf2jo8idbSB0WdHVKhnHsPRQ RloyfJ8Z37UMCDeHNAjnewCF8NtpSoT2CJ9QdkonHHNTvIJBkq85XDBlIxIFePObQ9mzvPgWQ Y225W5QR+ZYq6XdRpEREyzNsQakji3udql5jMB+2KVUTxQYyR9ZFI3Q63jFiaRDmLPnY7cSmS xutKCSIL7I/AdsmdCfu4hf/wAhkJseBvG0Sr4hAamJM5wT9ePFN1UvZa1QFNucnIRMtU8u8pQ Vd7VXBZ+VrVD2WKQzXRd22H3rpga2Tcv7MKXv0yV28Xj+83mJml0r0PCUbIZA+h3UOBFlkgPN 0OiEXHnMgnQx/PaKeWsnY1sNNmuumOiMgwDzbe56DU+ylAbV/L29fD+c/t6NspBGG1umuiY1c O+HWZWRS1nSqHwKaPZ8zDtkpC1svSQ2YOuhCxmwgVRQS7csot68bxNh5T6t4CD7gy3lsmhD8D fukAtdVQHKqVNtneX2mixM4fUG1Y8HUGcErc84/Run2Lw7PTwVcGdU47D7sD7X95tq+4yDGkq syOmP8CMR3qIMQnL2vVTzXiWNbSc9nE/RzliSdQlwKt16dzIShcbjtjlKLMlHGjEFYEn637Gd 6lcBMmRKzqHZmWjOpZE3eXTGJh/2zVqlTNjQ8mO+EiopmB0xvY8OblPPgAqx/WepvapzmBejK +jlleMnAu6MZw/sc7sPQFahWhqBPe4cQ6JS7A0k9mjcIDSMTlO/BcnbMwvrciJEFyneDbrX8v miHJ7erpCKOI4GG3sdxUo/fgLXvN8ckT1pXGmapKLekLRgeRsGCF8N8PTIXPO89+RzzxxoGq2 9NkGu085eJ8NtDxY/D4QPxLp6kIfKd8/+L8NLuClrCtOG+7Ee2HMMEbU/6ErMDo+0zrxV08TG g0BXrPOExAtNPXSqzgGR1DlGLJ8= X-Spamd-Result: default: False [-2.10 / 15.00]; NEURAL_HAM_LONG(-0.89)[-0.890]; NEURAL_SPAM_SHORT(0.62)[0.615]; NEURAL_HAM_MEDIUM(-0.53)[-0.525]; DMARC_POLICY_ALLOW(-0.50)[gmx.de,none]; R_DKIM_ALLOW(-0.20)[gmx.de:s=s31663417]; RWL_MAILSPIKE_VERYGOOD(-0.20)[212.227.17.21:from]; R_SPF_ALLOW(-0.20)[+ip4:212.227.17.0/27:c]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[212.227.17.21:from]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[current@freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; FREEMAIL_REPLYTO(0.00)[gmx.de]; HAS_REPLYTO(0.00)[garyj@gmx.de]; ARC_NA(0.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; REPLYTO_ADDR_EQ_FROM(0.00)[]; FREEMAIL_FROM(0.00)[gmx.de]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmx.de:+]; FREEMAIL_ENVFROM(0.00)[gmx.de]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4QXdlR4RBLz3h86 X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N On Fri, 2 Jun 2023 09:56:44 +0000 Gary Jennejohn wrote: > Error building kernel in current: > > -------------------------------------------------------------- > >>> stage 3.1: building everything > -------------------------------------------------------------- > /usr/src/sys/netlink/route/iface.c:1315:22: error: use of undeclared > identifier 'if_flags' > if (error =3D=3D 0 && !(if_flags & IFF_UP) && (if_getflags(ifp) = & IFF_UP)) > ^ > 1 error generated. > --- iface.o --- > *** [iface.o] Error code 1 > > My source tree was updated just a few minutes ago and I didn't see any > recent changes to iface.c. > > I have WITHOUT_NETLINK_SUPPORT=3D in my src.conf. > Ah, my error. The failure occurs while building the kernel, so I fixed Subject accordingly. =2D- Gary Jennejohn From nobody Fri Jun 2 15:30:55 2023 X-Original-To: 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 4QXn5b120Tz4YmrM for ; Fri, 2 Jun 2023 15:30:59 +0000 (UTC) (envelope-from garyj@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QXn5Y1cQ1z4Mdn for ; Fri, 2 Jun 2023 15:30:56 +0000 (UTC) (envelope-from garyj@gmx.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmx.de header.s=s31663417 header.b=DhJfdozi; spf=pass (mx1.freebsd.org: domain of garyj@gmx.de designates 212.227.17.22 as permitted sender) smtp.mailfrom=garyj@gmx.de; dmarc=pass (policy=none) header.from=gmx.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1685719855; x=1686324655; i=garyj@gmx.de; bh=L9WwymbLK2rlpaXTQ5U8PbnzjKm6qX8wWutlIzz3Ecw=; h=X-UI-Sender-Class:Date:From:To:Subject:In-Reply-To:References:Reply-To; b=DhJfdoziqaz2UrZNg7pw9p5tPQrSM7zQLjVsbZCwWPbwP9bllHy4OmVEBjmMVRIoCca29Sm ORgp9C2I3HmNby25GVYvKgwDoh6VujCAQQlIOQdfKAGCGQHgA84/1m09L7TW75HhhgWLNZsph tyoHBNj9xOGN6nO0q/vT8wzJOYBOZFHF4RhwyOOwHXHrPXI9RqYsL7I7o+iBWIXqbKiCa6lLW qMV57mhO3X8KznqtSVfFPRnTOyFk4oUp3kItEOUcz3OTH+O0VYOmXh2HzblCICpQPFeWh3jGl Yu0KTivqUN1C8LXNUygq+gGdfDefR8U4zMxOGd223SxACXWWqSzg== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from ernst.home ([91.59.239.189]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MuUjC-1qMMTV2ls2-00rU3e for ; Fri, 02 Jun 2023 17:30:55 +0200 Date: Fri, 2 Jun 2023 15:30:55 +0000 From: Gary Jennejohn To: current@freebsd.org Subject: Re: Error building kernel in current Message-ID: <20230602173055.583db61d@ernst.home> In-Reply-To: <20230602115940.7c9d2f4e@ernst.home> References: <20230602115644.7ce88b9f@ernst.home> <20230602115940.7c9d2f4e@ernst.home> Reply-To: garyj@gmx.de X-Mailer: Claws Mail 3.19.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:53Nacr1uYH7ibPfnP0rhh7IA5ikL/7IGx7fY5bSqz6K5HTdPoAJ KUh7K/LoUVYG7vUgsWtNmeA1/SlS0jFYZfzTGcs0n3fl1KZTv2pFm65SH6E2nSuzHc0puHS q18T90Kb2g1MXddGmWXX7BoWiVS3nxz5DZU2wbQ00pCxfwTWPbsEp5DXMrDISQXbjVvtlqj VucljfYLavKMI6COnwZvw== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:Ifv5euR5wg0=;QVKSfb7id/bs9+VlcAsGqUl2TDe /Jfff8LNl0KQILh3FoBd0A5cIdWX5iEHp+KLJNiZ2cWBRAXv80Yd24DuhvJooh4+lB86kfrMT GiuI5aCY25wA9gXqO0A/+H5NN4pTSbgmVcuQkuvb4WUpyYQ4En3OgT2y/kUpTl4kJEXVMSYaX DC6gBR9NLGKabmjll8cUByFhyMv7behX/FmexbSX2W00lyIRZp3pjD8hVk+BmHg1hImorXrD2 zKYYhfRAYjan5QG8y3w5YBleB2AKm9FMsLjjH7xbI0Cad8jrv1qn4Js/o81nDGVUXBSWPFMQZ bDEGUP5jJtFSAzAncJwI5QTVxHG/DzGSsSuYYsE+rhybn+e0yIUhh08uYNYoLcWUzX+klZhLS +5+4ZlqIwdFzzpF/o1zpkw4tvPhMeoYN+xCBakWeiEMM+wuyMYt/FINnWPTrb73A4fMwcbeMi VT7rxyqfiXdSlyDLTXfmJZowyZFgH2cuYPPS9o8Cxw+EtDYd4bDb80n/Mb23rKI20rz6YxIxq ipZoBuy7L1LBuLqItHDJGvxonccM3GQ5UkssPJJGR3qDbxfHDwoKgWWnxBmGjShvkgYA4Wj6L /2u/1RAi2IWNvbd0uXgIY9ODRS9XYyROEhjK3i09a8nZU+TTl+xi/OdWAzDjZXahLvm5K+RQP K2oUEMe3Z80I3yIu2VW+bU/wdLBNG0dyv7B4mVXKrt2NM970Zu4i2jpM/2yCleniv0VpSB+rv VL4Wwx0aBFnpcsczO9ZzYKGDAWQWac4Gh1J1lxZmCqbsWNghX2oDCSUokV30pIWzoyshZOVpV fuQtU9EquzelntA+459xFezLDqAC3qtBg5D/gUeP533MYAXIZlFPeB4U4WkVBtl/aMvrsIhgr TaDDl8HkJz3Qy38AfOXt5h9uguPWTerNSgyCmTHn5M2B0MM39MyGiLV27D3J5A2LH1K/7l+RW WntRzZZc4I4CVuOqy5YjB1RAjqQ= X-Spamd-Result: default: False [-0.55 / 15.00]; NEURAL_SPAM_MEDIUM(0.88)[0.879]; NEURAL_HAM_LONG(-0.88)[-0.876]; NEURAL_SPAM_SHORT(0.55)[0.548]; DMARC_POLICY_ALLOW(-0.50)[gmx.de,none]; R_DKIM_ALLOW(-0.20)[gmx.de:s=s31663417]; R_SPF_ALLOW(-0.20)[+ip4:212.227.17.0/27]; RCVD_IN_DNSWL_LOW(-0.10)[212.227.17.22:from]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; HAS_REPLYTO(0.00)[garyj@gmx.de]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_REPLYTO(0.00)[gmx.de]; MLMMJ_DEST(0.00)[current@freebsd.org]; BLOCKLISTDE_FAIL(0.00)[91.59.239.189:server fail,212.227.17.22:server fail]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; REPLYTO_ADDR_EQ_FROM(0.00)[]; FREEMAIL_FROM(0.00)[gmx.de]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmx.de:+]; FREEMAIL_ENVFROM(0.00)[gmx.de]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4QXn5Y1cQ1z4Mdn X-Spamd-Bar: / X-ThisMailContainsUnwantedMimeParts: N On Fri, 2 Jun 2023 09:59:40 +0000 Gary Jennejohn wrote: > On Fri, 2 Jun 2023 09:56:44 +0000 > Gary Jennejohn wrote: > > > Error building kernel in current: > > > > -------------------------------------------------------------- > > >>> stage 3.1: building everything > > -------------------------------------------------------------- > > /usr/src/sys/netlink/route/iface.c:1315:22: error: use of undeclared > > identifier 'if_flags' > > if (error =3D=3D 0 && !(if_flags & IFF_UP) && (if_getflags(ifp= ) & IFF_UP)) > > ^ > > 1 error generated. > > --- iface.o --- > > *** [iface.o] Error code 1 > > > > My source tree was updated just a few minutes ago and I didn't see any > > recent changes to iface.c. > > > > I have WITHOUT_NETLINK_SUPPORT=3D in my src.conf. > > > > Ah, my error. The failure occurs while building the kernel, so I fixed > Subject accordingly. > OK, this is another INET6 error. I don't have INET6 enabled. At line 1280 we have: #ifdef INET6 int if_flags =3D if_getflags(ifp); #endif and if_flags is used at line 1315 without checking whether INET6 is defined. if_flags seems to be totally redundant, since the code at line 1315 will invoke if_getflags(ifp) if !(if_flags & IFF_UP) is true. =2D- Gary Jennejohn From nobody Fri Jun 2 18:57:40 2023 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 4QXshT2PPFz4YTbP for ; Fri, 2 Jun 2023 18:58:01 +0000 (UTC) (envelope-from melifaro@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 4QXshT1slRz3wLG for ; Fri, 2 Jun 2023 18:58:01 +0000 (UTC) (envelope-from melifaro@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685732281; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=5RFi+o9Myd4qvhSe83AF1b6L3gUHbSNAAlHz8eZkJMI=; b=EVc12E2ca554n1qgAJ1KoW/TiLISWYBOUkXzYuI12WU41e0Zl5FzpqOeVStwfCDCOtaFra nLli/ix4r3DIdS4yC6fERSXHj17siXYCKo7AU3ZDW01HEo6sFRtn72CXIVSlPS8/s/bjB/ UHkD90+ep6U+/onrxgfTNbY2CicGVbi6umvDj7qy9GnIKNvfMMJsO+xaM0ooDUk8MMznX9 OnSc1QOYbR962kT1kErEvUWzcFMWBZ6iSuAWQRES0udxLJ2F0E8FsMiFkKBcpi0cZEibWH 22C+Qe+E3cveaRS0pCxC4K3Z0J/1loOLZfRmDh3IRm8CfFXZXbbNdyRaaK0w1w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685732281; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=5RFi+o9Myd4qvhSe83AF1b6L3gUHbSNAAlHz8eZkJMI=; b=rQh4CQganT2SrCxeBQZM4swfqTf2Hm2X6XLTMkPxku++mt/KMpfwLgeHQ1YX7uCFiEH0MM PrEaFmyavKl/kfIBfeYx2S9AA1rxsNSmjXH7zGp6iqUBp19glxHkZNxgKwuVq1/rMB9PBm Wo8j6e8M6o0ILRXDKRBh9D26Yel5av8wfTTFAwBGXluny9faBEgrqFvgZaGKCa7mh6Nw3D cNCwlVOkZ6/+0188+bs17y7y9fnaygrSqEYY3Izvp9etPBVA2KspH6vJtJ4vIp/mLal+ks lo5FfZfPeUDyd6knoC/9DIFLr6a+vRePHY9utCIklrpXr/DoRnsMZwlJO+KN9A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1685732281; a=rsa-sha256; cv=none; b=TW6qBtmvFn50zjl3zWup+R7woApWTMgZubLrizZx7yHPFIxXvV8rL9x9ucY9jRm3uN9bQu yfhxqj+9O/mCoVAb3G8vqlAT1N3sYBCoAIdd+/o2N88z7UXqbc/2N3cyXlA4S+cRYKrSo+ 4GTkZ4OHSwcVFzsYENFqhqpX7NdBS7wOSn/SPum8w/us9xwCebdR8wGwf7+7eIq8LDOokp Mn7pCRZUJ/oc+NtZkrCUSdwKoz/91taFgly21vCECglWsgGvMyiyohquMcqp9HcfeICbS1 0CrmlQ4fqmzFYEfZJP2rPR/NJxCgp0BvqnipbN8LZSBYIi1Nlldm5NovuFtPdg== Received: from auth2-smtp.messagingengine.com (auth2-smtp.messagingengine.com [66.111.4.228]) (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) (Authenticated sender: melifaro/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QXshT0mwrz1Bj6 for ; Fri, 2 Jun 2023 18:58:01 +0000 (UTC) (envelope-from melifaro@FreeBSD.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailauth.nyi.internal (Postfix) with ESMTP id 67E6D27C0054 for ; Fri, 2 Jun 2023 14:58:00 -0400 (EDT) Received: from imap43 ([10.202.2.93]) by compute4.internal (MEProxy); Fri, 02 Jun 2023 14:58:00 -0400 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeelfedguddvlecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrg dtreerreerjeenucfhrhhomhepfdetlhgvgigrnhguvghrucevhhgvrhhnihhkohhvfdcu oehmvghlihhfrghroheshfhrvggvuefuffdrohhrgheqnecuggftrfgrthhtvghrnhepge dvjedtieejvedttdffvddttefgteevhedtgfeuveejjeekfedtveelgfekgeffnecuffho mhgrihhnpehfrhgvvggsshgurdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrg hrrghmpehmrghilhhfrhhomhepmhgvodhmvghsmhhtphgruhhthhhpvghrshhonhgrlhhi thihqddufedvledvuddvfedvqddvleefiedutdegkedqmhgvlhhifhgrrhhopeephfhrvg gvuefuffdrohhrghesmhhplhhsrdhivg X-ME-Proxy: Feedback-ID: i02494642:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 34A702D4008E; Fri, 2 Jun 2023 14:58:00 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-447-ge2460e13b3-fm-20230525.001-ge2460e13 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 Message-Id: In-Reply-To: <20230602173055.583db61d@ernst.home> References: <20230602115644.7ce88b9f@ernst.home> <20230602115940.7c9d2f4e@ernst.home> <20230602173055.583db61d@ernst.home> Date: Fri, 02 Jun 2023 19:57:40 +0100 From: "Alexander Chernikov" To: freebsd-current@freebsd.org Subject: Re: Error building kernel in current Content-Type: multipart/alternative; boundary=198b55cd52044226aa60ed116c0f2a28 X-ThisMailContainsUnwantedMimeParts: N --198b55cd52044226aa60ed116c0f2a28 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable On Fri, 2 Jun 2023, at 4:30 PM, Gary Jennejohn wrote: > On Fri, 2 Jun 2023 09:59:40 +0000 > Gary Jennejohn wrote: >=20 > > On Fri, 2 Jun 2023 09:56:44 +0000 > > Gary Jennejohn wrote: > > > > > Error building kernel in current: > > > > > > -------------------------------------------------------------- > > > >>> stage 3.1: building everything > > > -------------------------------------------------------------- > > > /usr/src/sys/netlink/route/iface.c:1315:22: error: use of undeclar= ed > > > identifier 'if_flags' > > > if (error =3D=3D 0 && !(if_flags & IFF_UP) && (if_getflags= (ifp) & IFF_UP)) > > > ^ > > > 1 error generated. > > > --- iface.o --- > > > *** [iface.o] Error code 1 Sorry for the breakage, I=E2=80=99ll fix it in a couple of hours. > > > > > > My source tree was updated just a few minutes ago and I didn't see= any > > > recent changes to iface.c. > > > > > > I have WITHOUT_NETLINK_SUPPORT=3D in my src.conf. > > > > > > > Ah, my error. The failure occurs while building the kernel, so I fi= xed > > Subject accordingly. > > >=20 > OK, this is another INET6 error. I don't have INET6 enabled. >=20 > At line 1280 we have: > #ifdef INET6 > int if_flags =3D if_getflags(ifp); > #endif >=20 > and if_flags is used at line 1315 without checking whether INET6 is > defined. >=20 > if_flags seems to be totally redundant, since the code at line 1315 wi= ll > invoke if_getflags(ifp) if !(if_flags & IFF_UP) is true. I wish it was true. The case here is that interface flags can change aft= er adding the address, as many interface drivers silently bring the inte= rface up upon the first address addition. Please see https://cgit.freebs= d.org/src/commit/sys/netinet6?id=3Da77facd27368f618520d25391cfce11149879= a41 description for a more detailed explanation. >=20 > -- > Gary Jennejohn >=20 >=20 /Alexander --198b55cd52044226aa60ed116c0f2a28 Content-Type: text/html;charset=utf-8 Content-Transfer-Encoding: quoted-printable

= On Fri, 2 Jun 2023, at 4:30 PM, Gary Jennejohn wrote:
On Fri, 2 Jun 2023 09:59:40 += 0000
Gary Jennejohn <ga= ryj@gmx.de> wrote:

> On Fri, 2 Ju= n 2023 09:56:44 +0000
> Gary Jennejohn <garyj@gmx.de> wrote:
>
> > Error building kernel in current:
> = >
> > -------------------------------------------= -------------------
> > >>> stage 3.1: buil= ding everything
> > --------------------------------= ------------------------------
> > /usr/src/sys/netl= ink/route/iface.c:1315:22: error: use of undeclared
> &= gt; identifier 'if_flags'
> >    = ;     if (error =3D=3D 0 && !(if_flags &= IFF_UP) && (if_getflags(ifp) & IFF_UP))
> = >           &n= bsp;           &n= bsp;     ^
> > 1 error generated= .
> > --- iface.o ---
> > *** [i= face.o] Error code 1
Sorry for the breakage, = I=E2=80=99ll fix it in a couple of hours.
> >
> > My source t= ree was updated just a few minutes ago and I didn't see any
> > recent changes to iface.c.
> >
=
> > I have WITHOUT_NETLINK_SUPPORT=3D in my src.conf.
> >
>
> Ah, my error.&nbs= p; The failure occurs while building the kernel, so I fixed
> Subject accordingly.
>

<= div>OK, this is another INET6 error.  I don't have INET6 enabled.

At line 1280 we have:
#ifdef I= NET6
int if_flags =3D if_getflags(ifp);
#end= if

and if_flags is used at line 1315 withou= t checking whether INET6 is
defined.

if_flags seems to be totally redundant, since the code at line 1= 315 will
invoke if_getflags(ifp) if !(if_flags & IFF_U= P) is true.
I wish it was true. The case here= is that interface flags can change after adding the address, as many in= terface drivers silently bring the interface up upon the first address a= ddition. Please see https://cgit= .freebsd.org/src/commit/sys/netinet6?id=3Da77facd27368f618520d25391cfce1= 1149879a41 description for a more detailed explanation.

--
<= /div>
Gary Jennejohn



/A= lexander

--198b55cd52044226aa60ed116c0f2a28-- From nobody Sat Jun 3 08:18:43 2023 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 4QYCSS447xz4Z0ly for ; Sat, 3 Jun 2023 08:18:48 +0000 (UTC) (envelope-from garyj@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.gmx.net", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QYCSR4sN0z4NpG; Sat, 3 Jun 2023 08:18:47 +0000 (UTC) (envelope-from garyj@gmx.de) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1685780325; x=1686385125; i=garyj@gmx.de; bh=ZEngNEc0TnNEBatqBIMpr4wY0bz4WTqIr7cK2Bfk/44=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:In-Reply-To:References:Reply- To; b=EphlgQ25PfbQAfzL8KZ7JoJ/Cn8CZ9a224ApTrPDM5ecTv9kxBLqKPGsc+9D7BlqIZ5vLuF ojO2QUq+gKiRsdNVVMfzQ8mHCZRPJeLP6Ft8abs6YTSXNr1exyDrbk9iSyViOFFIliagYVs1u lKBMNtv0CSCRCcXu/AwK2Hila+lRM9YfvGOLn9NmqsDh9zsmDBOlISrir9gmhw3dOGC6t0zhO ZJj9YGNE3KziFr0LAGYkdcxoedih3BX0HnLtPJIBGRDssUdzPP7H62g7y70LCjgtoyQQyrBfO 4dRWNLYm7/ZP2geWjUdC0v7D9ZguOd2FrmN2cCvtK9GVzNNlr3oA== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from ernst.home ([91.59.239.189]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MLzBp-1pny2m3AoL-00Huxm; Sat, 03 Jun 2023 10:18:45 +0200 Date: Sat, 3 Jun 2023 08:18:43 +0000 From: Gary Jennejohn To: "Alexander Chernikov" Cc: freebsd-current@freebsd.org Subject: Re: Error building kernel in current Message-ID: <20230603101843.717e30c9@ernst.home> In-Reply-To: References: <20230602115644.7ce88b9f@ernst.home> <20230602115940.7c9d2f4e@ernst.home> <20230602173055.583db61d@ernst.home> Reply-To: garyj@gmx.de X-Mailer: Claws Mail 3.19.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:VjnTCkiourr31l4vBV6AsTWYjwvebNVBg+yPQRwdidbbbQbBUNR PjhOGvLHcEolbawude2YChNNrVA/zarw7OZ/YDS142hzQXeObJWuvssBbkwlIpbdyY0XO4J GF70nexwAqbhHTzAThR5rKprnX3Vq1NptcBSAmNvbMBcsZ06EaIzVDA9QxClcTEpdIvV0X9 DGoTSZSq9Q2Utz6MrVv5g== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:r9coonT7nUY=;3QKVqAuMCXxYcmuRSu5bQpUxmzN KPAowoOPWpwMSvUVhNRC1xCPn9FHhBn64+qAkSzgBsilm4Wjcur8T/oQ1c2ly2ytavOTqmbJY ge8Vk4WEfZdYGYc/QPl1C9ubDt7KVF3M5NPMN54FuhhqQuCZZPfHj8EIzibKoifx4QI3FISvT 2RMWe40UCl00bsbIU9LbbuRJNya6yY7Smt3U7kjJjZOe4Uuo7PH63bAccZTXU0eMdIYbnVyms aJOklOi3Fz21we9pfBHOxh70Dwq54/0hlkdEv0wRLjt/SdR3XgciEmGeSmSb9hBAwXQ7q5Irv dD+ZTLDs3qZNZMAAaERgXtfRag9WbGWiXzkhIUcGYksuwY/oC/DGFJWUBrLmIPaSk9crC4vBH JJbM0yHm/m/U2E2Zo95sGpKSr+kXSI2iiQlV62pWRy5vRkWtPldZpD6oL+Bah+W+fqh/nnFm+ OcCCc1l+bU9C/i8mYktLX+2at6BNNvlOHoGMibUB3xVKTBCBnlDevzr77kbPUrZ8+S8keJsEX 1UUNcQBARLnFgWRUPcBEpZnHNlbV7DP9HaA+g9y4w1GzeUxifS5CDHTn3ZEP8pQgAuZKrWM3+ YHeRTw18AVzq+1NDT2w4IituoPUqdRfr5oXeoqMMjJiLHaKVpmYarF9QnpvOJ30w+KsHB05N6 VOgNXqD6mqxooPGDhoeUXxdtFOVXsR8zmpD+VqwgRbe5D8DNlT3izgqAibDKCWDG99/avBMlO 8D0Y9SVU7FuHx/OmzT6HTcGmYBs6VHLK/rkcDqlCrFR5os6/lD51A5rBF4Q/prPZ+ybrOYWt1 5G+6JAdd3ZwcIyDz8F7iDtoHuHg1uyn/AX4fJoyKJZtrcPQAQ6TXU6iWqeyMzG9kH0VBf5W9a ZmauHMPjSUqI8QoFR+1cr8TollBG3ci42Z1lw92Gh6mPg7W0Q/7y9KDfsSyuWfftEA/Kp5n2W nwVxovXI7L1QFscPTGxVbLwLtMw= X-Rspamd-Queue-Id: 4QYCSR4sN0z4NpG X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Fri, 02 Jun 2023 19:57:40 +0100 "Alexander Chernikov" wrote: > On Fri, 2 Jun 2023, at 4:30 PM, Gary Jennejohn wrote: > > On Fri, 2 Jun 2023 09:59:40 +0000 > > Gary Jennejohn wrote: > > > > > On Fri, 2 Jun 2023 09:56:44 +0000 > > > Gary Jennejohn wrote: > > > > > > > Error building kernel in current: > > > > > > > > -------------------------------------------------------------- > > > > >>> stage 3.1: building everything > > > > -------------------------------------------------------------- > > > > /usr/src/sys/netlink/route/iface.c:1315:22: error: use of undeclar= ed > > > > identifier 'if_flags' > > > > if (error =3D=3D 0 && !(if_flags & IFF_UP) && (if_getflags= (ifp) & IFF_UP)) > > > > ^ > > > > 1 error generated. > > > > --- iface.o --- > > > > *** [iface.o] Error code 1 > Sorry for the breakage, I?ll fix it in a couple of hours. > > > > > > > > My source tree was updated just a few minutes ago and I didn't see= any > > > > recent changes to iface.c. > > > > > > > > I have WITHOUT_NETLINK_SUPPORT=3D in my src.conf. > > > > > > > > > > Ah, my error. The failure occurs while building the kernel, so I fi= xed > > > Subject accordingly. > > > > > > > OK, this is another INET6 error. I don't have INET6 enabled. > > > > At line 1280 we have: > > #ifdef INET6 > > int if_flags =3D if_getflags(ifp); > > #endif > > > > and if_flags is used at line 1315 without checking whether INET6 is > > defined. > > > > if_flags seems to be totally redundant, since the code at line 1315 wi= ll > > invoke if_getflags(ifp) if !(if_flags & IFF_UP) is true. > > > I wish it was true. The case here is that interface flags can change > after adding the address, as many interface drivers silently bring the > interface up upon the first address addition. Please see > https://cgit.freebsd.org/src/commit/sys/netinet6?id=3Da77facd27368f61852= 0d25391cfce11149879a41 > description for a more detailed explanation. I suspected that may have been the reason, but I wasn't sure. Thanks for the link. =2D- Gary Jennejohn From nobody Sat Jun 3 15:02:49 2023 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 4QYNRJ2jHhz4Z04J for ; Sat, 3 Jun 2023 15:03:24 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp052.goneo.de (smtp052.goneo.de [85.220.129.60]) (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 4QYNRH0Sj8z4JcZ for ; Sat, 3 Jun 2023 15:03:22 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b=B00FdHdK; spf=none (mx1.freebsd.org: domain of freebsd@walstatt-de.de has no SPF policy when checking 85.220.129.60) smtp.mailfrom=freebsd@walstatt-de.de; dmarc=none Received: from hub2.goneo.de (hub2.goneo.de [IPv6:2001:1640:5::8:53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp5.goneo.de (Postfix) with ESMTPS id 5FD3910A1E88; Sat, 3 Jun 2023 17:03:19 +0200 (CEST) Received: from hub2.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPS id BD6AB10A3337; Sat, 3 Jun 2023 17:03:17 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1685804597; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=A5B9wXa+oRAC1v16vroDQgVdP1UTVcMmFzOnR097wPE=; b=B00FdHdKMuTjHrtPEpYHrXOBWR8CczZBLfGUefIujZuKrR1Bjvef+Y/N+r6YeIYgn/Q4D2 WqKs6UTdgdfWLZ37ZQz37plb5nQliCnub4UeMQEQQEW40kBzEKmOZOnhRmEQVmwshy2fCE zVf6YyyTQm8PYM0ZiY07tdGgd0ckMWr9QJ6/v0Rd3iYYNa/ol4Wv4BN9FUW7bDNhMp/Iga 46CL7Njnaqb4HqU1+FZvGR/fwnSARZ2DX1ncNB9NafsefzycPSu/G4OiOUSUCJCgfpGP/A PCbg+E5PSK05DkoVmO4drI6KakdU+JdOoLIa4SdL/bA60SbVWRAB2QE4b6bM0g== Received: from thor.intern.walstatt.dynvpn.de (dynamic-077-191-239-118.77.191.pool.telefonica.de [77.191.239.118]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPSA id 7860110A3332; Sat, 3 Jun 2023 17:03:16 +0200 (CEST) Date: Sat, 3 Jun 2023 17:02:49 +0200 From: FreeBSD User To: Warner Losh Cc: FreeBSD CURRENT Subject: Re: WITH_BEARSSL: -8112 bytes available Message-ID: <20230603170316.74ea78f1@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20230529105854.1903226d@thor.intern.walstatt.dynvpn.de> Organization: walstatt-de.de 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 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-UID: f170e8 X-Rspamd-UID: 039139 X-Spamd-Result: default: False [-3.23 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.986]; NEURAL_HAM_LONG(-0.94)[-0.940]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; R_SPF_NA(0.00)[no SPF record]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; DKIM_TRACE(0.00)[walstatt-de.de:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ASN(0.00)[asn:25394, ipnet:85.220.128.0/17, country:DE]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; DMARC_NA(0.00)[walstatt-de.de]; RCVD_COUNT_THREE(0.00)[4]; HAS_ORG_HEADER(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4QYNRH0Sj8z4JcZ X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N Am Wed, 31 May 2023 12:15:12 -0600 Warner Losh schrieb: Sorry for the late response. > On Mon, May 29, 2023 at 2:59=E2=80=AFAM FreeBSD User wrote: >=20 > > Hello, > > > > on CURRENT, enabling in /etc/src.conf > > > > WITH_BEARSSL=3D > > > > seems to result in a slightly enlarged loader binary, which seems to ha= ve > > a fixed size > > supposed on the error I get. See below. > > > > The system is amd64 (64 bit), for the record. > > > > Somewhere in the past developers mentioned this upcoming problem and > > provided a knob to adjust > > the used size - I forgot about that knob and I couldn't find it even in > > the loader docs - or > > looked at the wrong places. > > > > Can someone help me out here? > > > > The first error stops compileing world/kernel, but taking a second run, > > the error goes away. > > > > Kind regards and thanks in advance, > > > > oh > > > > > > > > [...] > > --- all_subdir_stand/efi --- > > SOURCE_DATE_EPOCH=3D1451606400 objcopy -j .peheader -j .text -j .sdata= -j > > .data -j .dynamic -j > > .dynsym -j .rel.dyn -j .rela.dyn -j .reloc -j .eh_frame -j > > set_Xcommand_set -j > > set_Xficl_compile_set --output-target=3Defi-app-x86_64 loader_4th.sym > > loader_4th.efi --- > > all_subdir_stand/i386 --- > > > > -8112 bytes available 7.71 real 12.86 user 3.08 sys =20 >=20 >=20 > bummer. I hate it when it's that close. >=20 > You can try setting LOADERSIZE=3D560000 in your environment. We currently= set > the maximum to 550,000 I tried to find find anything related to LOADER or SIZE in the docs. I reme= mber you mentioned the existence of that variable months ago, but with no clue what to look af= ter, it is almost impossible yo figure out as a non developer what the right knob might be. A grep -r on /usr/src shows up only in=20 [...] ./stand/i386/loader/Makefile:LOADERSIZE?=3D 550000 # Largest= known safe size for loader.bin ./stand/i386/loader/Makefile: @set -- `ls -l ${.TARGET}` ; x=3D$$((${LOAD= ERSIZE}-$$5)); \ [...] There is no sign/trace of it in any man page related to loader and sibbling= s. I found the variable rather quickly after knowing what to look after. > bytes because that's the most conservative number due to variation in the > available BIOS space available. > This likely can be set even higher if you don't have add-in cards that are > consuming space in the lower 640k > of memory. 640k is the absolute limit, but you need 20-30k of stack for t= he > loader so pushing this much past > 625,000 or maybe 630,000 increases the risk of run-time crashes as the > stack smashes through the top of > the loader program. You may also have to disable the lua build, since it > uses more stack and is just a smidge > larger than the forth build. _simp will be the smallest of them all. On my > system, without bearssl, I see: > -r-xr-xr-x 3 root wheel 503808 May 22 15:25 /boot/loader_lua > -r-xr-xr-x 1 root wheel 446464 May 22 15:25 /boot/loader_4th > -r-xr-xr-x 1 root wheel 385024 May 22 15:25 /boot/loader_simp In my case, with supposedly blewn up loader size by BEARSSL enables, it is: -r-xr-xr-x 1 root wheel - 503808 3 Juni 12:33 /boot/loader_4th* -r-xr-xr-x 1 root wheel - 643584 3 Juni 12:33 /boot/loader_4th.efi* -r-xr-xr-x 1 root wheel - 503808 3 Juni 07:45 /boot/loader_4th.old* -r-xr-xr-x 3 root wheel - 569344 3 Juni 12:33 /boot/loader_lua* -r-xr-xr-x 2 root wheel - 737280 3 Juni 12:33 /boot/loader_lua.efi* -r-xr-xr-x 1 root wheel - 569344 3 Juni 07:45 /boot/loader_lua.old* -r-xr-xr-x 1 root wheel - 446464 3 Juni 12:33 /boot/loader_simp* -r-xr-xr-x 1 root wheel - 589312 3 Juni 12:33 /boot/loader_simp.efi* -r-xr-xr-x 1 root wheel - 446464 3 Juni 07:45 /boot/loader_simp.old* on FreeBSD 14.0-CURRENT #58 main-n263387-556b43492297: Fri Jun 2 20:19:55 = CEST 2023 amd64. > which suggests a ~60k bump for adding forth and ~115k bump for lua. So the > 560,000 may need to be 625,000 > which is living life on the edge for 4th, and simply too big for lua. >=20 > I'd be open to adding docs on this, since I don't think this option is > currently documented since I added it > to experiment around with a good value. See above, personally I'd like to see some hints on that variable, even if = I do not fiddle around with it. >=20 > And no, I really do not want to support 'loadable modules'. BIOS booting = is > on the way out, and people > that want to do complex stuff in the boot loader will simply have to do > that in UEFI or maybe kboot/LinuxBoot. > There's low RoI on adding this complexity, imho. We'd be better off, imho, > making things like the graphics > console optional since the fonts and code for that free up about 30k in > stupid experiments that I've done > (it's hard since vidconsole has a lot of calls into the graphics system > that aren't optional and easy to disable, > so I've had to do hack and slash to produce a super ugly result that is > only suggestive of the final savings): > -rw-r--r-- 1 imp imp 352256 May 31 12:04 loader_simp > I don't know if I slashed too much, or not enough since the code is rather > hard to separate out, so if you > really wanted to go down this path, it would take a lot of work and patie= nt > understanding to make it so with > the low end of savings 20k and the high end on the order of maybe 40k. >=20 > There's likely other ways to conserve space. We've not had space issues > with loader, et al, in the past, > so it's not well setup for subsetting. Though the different filesystem > support might also net you a fair amount: > LOADER_NET_SUPPORT?=3D yes > LOADER_NFS_SUPPORT?=3D yes > LOADER_TFTP_SUPPORT?=3D yes > LOADER_CD9660_SUPPORT?=3D yes > LOADER_EXT2FS_SUPPORT?=3D yes > LOADER_MSDOS_SUPPORT?=3D yes > LOADER_UFS_SUPPORT?=3D yes > LOADER_GZIP_SUPPORT?=3D yes > LOADER_BZIP2_SUPPORT?=3D yes > as would compiling w/o ZFS, which uses its own method (eg > WITHOUT_LOADER_ZFS). Tuning the loader > at this level does start to get into the weeds a bit, but can offer ~40k > savings turning off all but NET and UFS: > -rw-r--r-- 1 imp imp 344064 May 31 12:11 loader_simp > you get even about ~100k when you disable ZFS support with > -DWITHOUT_LOADER_ZFS: > -rw-r--r-- 1 imp imp 241664 May 31 12:12 loader_simp > (both of these are with the graphics console enabled without the silly > hacks to see how much that takes up). > Without the extras and ZFS, you might have bearssl and lua together even.= .. >=20 > Hope this helps. Very much appreciated, thanks. I'm not so much concerned by the space sonsumption or a corrupted boot proc= ess, I don't even know whether I really need this i386 stuff mentioned here, since all of my = boxes are UEFI, except the APU2, which are driven by SeaBIOS and bootin non UEFI. The cosmetic issue is that whenever anything reagrding the loader gets touc= hed by the compiler, out build system drops out with an error - a second run then per= forms clean (which is a kind of weird I guess). >=20 > Warner Thank you very much, Kind regards Oliver --=20 O. Hartmann From nobody Sat Jun 3 20:46:06 2023 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 4QYX2z3ZgXz4YVD4 for ; Sat, 3 Jun 2023 20:46:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QYX2z1Y9Sz44tC for ; Sat, 3 Jun 2023 20:46:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-5149c76f4dbso5033232a12.1 for ; Sat, 03 Jun 2023 13:46:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1685825177; x=1688417177; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=9gUQG10ntlK5mtZ7D2uVzokC0LtBpwoNs89BZ1rIrr0=; b=ENvycvpahhaQrX+92dPSTY0zmyR/abX1MT3j7aWg4bjT7ExowIoUhswzeEH6isBwIl X9lF3zxYRoyzRUNCwX4o3oabMNAWtMRkOUXS3q2UrzbwXkWiLyUntO/eZXXIjGBkaO2F nfXHuQ1+SIAVYMrzl+3wgPwiarg1JyJPp3XgC4AO34+SrDV7RqpbTxehcGkD5krd/pFc NpTItZmy7MEOAUU1s6fqpuaP3rXaTNLwqM4l98DaKDhTmWOB6lNiDlzLtXJy7/rpBkzL R5Um37QkU/3kKS+wnkCYzdM6eVYK7/n5+ZO4x+SzrbDJP+fSbNGI1RvbvDX/+Eon/H05 dBXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685825177; x=1688417177; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=9gUQG10ntlK5mtZ7D2uVzokC0LtBpwoNs89BZ1rIrr0=; b=ISNG2g42sb6Ka9GMr2B4dStQTOazpuVlGNIJeYvJV10GNp4wDNRWC++bQKkpR0RNdI uIQ6GiPi08FBqWI/i0PEP/rfd2oG18QcJopWDS5A66WroXN29cBIeuIlkccd6DYJAvjb Tk4Rxi5yb7zJQ5bTJ3vCqouQKWOPJqUTG+XSb9N/3oHe7WPjEQnjh0QEYWIykVpXMUG6 WNSvD4tt6wBYtjwtJuKxiactw4hqCBzRr0hZNfzhTUIn+vPPxZkHBc1+kaX3H3jAuQ5n mMrBaowU64Vy1N60msIqqa0u7pjQzsf/grxdSJ60jc4OIpDqVytE7jdj10Zb4c7vpJhR XHew== X-Gm-Message-State: AC+VfDxHrjN7LotkpQoLZ0fKoGAa96JzSzEW/WkJDrowDFMBY+OIPkXS K5zUt4PUt5Wg1L/7zuuNACo8cVu2SQSvNd4NjwiXLwk3MuuiLzgo X-Google-Smtp-Source: ACHHUZ49uzNAhYE5cn58soaFi5X6cWXIID3MKplxiLy/aaDd1sfOlP4CZHwL4X5BlQRuikpn2LnJxZZAIX37uwHxgGM= X-Received: by 2002:aa7:c2c7:0:b0:50b:caae:784 with SMTP id m7-20020aa7c2c7000000b0050bcaae0784mr4302747edp.20.1685825177333; Sat, 03 Jun 2023 13:46:17 -0700 (PDT) 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 References: <20230529105854.1903226d@thor.intern.walstatt.dynvpn.de> <20230603170316.74ea78f1@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20230603170316.74ea78f1@thor.intern.walstatt.dynvpn.de> From: Warner Losh Date: Sat, 3 Jun 2023 14:46:06 -0600 Message-ID: Subject: Re: WITH_BEARSSL: -8112 bytes available To: FreeBSD User Cc: FreeBSD CURRENT Content-Type: multipart/alternative; boundary="000000000000d945db05fd3fc245" X-Rspamd-Queue-Id: 4QYX2z1Y9Sz44tC X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000d945db05fd3fc245 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Jun 3, 2023 at 9:03=E2=80=AFAM FreeBSD User wrote: > Am Wed, 31 May 2023 12:15:12 -0600 > Warner Losh schrieb: > > Sorry for the late response. > > > > On Mon, May 29, 2023 at 2:59=E2=80=AFAM FreeBSD User > wrote: > > > > > Hello, > > > > > > on CURRENT, enabling in /etc/src.conf > > > > > > WITH_BEARSSL=3D > > > > > > seems to result in a slightly enlarged loader binary, which seems to > have > > > a fixed size > > > supposed on the error I get. See below. > > > > > > The system is amd64 (64 bit), for the record. > > > > > > Somewhere in the past developers mentioned this upcoming problem and > > > provided a knob to adjust > > > the used size - I forgot about that knob and I couldn't find it even = in > > > the loader docs - or > > > looked at the wrong places. > > > > > > Can someone help me out here? > > > > > > The first error stops compileing world/kernel, but taking a second ru= n, > > > the error goes away. > > > > > > Kind regards and thanks in advance, > > > > > > oh > > > > > > > > > > > > [...] > > > --- all_subdir_stand/efi --- > > > SOURCE_DATE_EPOCH=3D1451606400 objcopy -j .peheader -j .text -j .sda= ta > -j > > > .data -j .dynamic -j > > > .dynsym -j .rel.dyn -j .rela.dyn -j .reloc -j .eh_frame -j > > > set_Xcommand_set -j > > > set_Xficl_compile_set --output-target=3Defi-app-x86_64 loader_4th.sy= m > > > loader_4th.efi --- > > > all_subdir_stand/i386 --- > > > > > > -8112 bytes available 7.71 real 12.86 user 3.08 sys > > > > > > bummer. I hate it when it's that close. > > > > You can try setting LOADERSIZE=3D560000 in your environment. We current= ly > set > > the maximum to 550,000 > > I tried to find find anything related to LOADER or SIZE in the docs. I > remember you mentioned > the existence of that variable months ago, but with no clue what to look > after, it is almost > impossible yo figure out as a non developer what the right knob might be. > Fair point. > A grep -r on /usr/src shows up only in > > [...] > ./stand/i386/loader/Makefile:LOADERSIZE?=3D 550000 # Large= st > known safe size for > loader.bin > ./stand/i386/loader/Makefile: @set -- `ls -l ${.TARGET}` ; > x=3D$$((${LOADERSIZE}-$$5)); \ > [...] > > There is no sign/trace of it in any man page related to loader and > sibblings. I found the > variable rather quickly after knowing what to look after. > To be fair, this is a very under documented area, semi on purpose... But that's a good point that it is under documented. And now that the size is creeping up and we have options that explode things, maybe it should be better documented. > > bytes because that's the most conservative number due to variation in t= he > > available BIOS space available. > > This likely can be set even higher if you don't have add-in cards that > are > > consuming space in the lower 640k > > of memory. 640k is the absolute limit, but you need 20-30k of stack for > the > > loader so pushing this much past > > 625,000 or maybe 630,000 increases the risk of run-time crashes as the > > stack smashes through the top of > > the loader program. You may also have to disable the lua build, since i= t > > uses more stack and is just a smidge > > larger than the forth build. _simp will be the smallest of them all. On > my > > system, without bearssl, I see: > > -r-xr-xr-x 3 root wheel 503808 May 22 15:25 /boot/loader_lua > > -r-xr-xr-x 1 root wheel 446464 May 22 15:25 /boot/loader_4th > > -r-xr-xr-x 1 root wheel 385024 May 22 15:25 /boot/loader_simp > > In my case, with supposedly blewn up loader size by BEARSSL enables, it i= s: > > -r-xr-xr-x 1 root wheel - 503808 3 Juni 12:33 /boot/loader_4th* > -r-xr-xr-x 1 root wheel - 643584 3 Juni 12:33 /boot/loader_4th.efi* > -r-xr-xr-x 1 root wheel - 503808 3 Juni 07:45 /boot/loader_4th.old* > -r-xr-xr-x 3 root wheel - 569344 3 Juni 12:33 /boot/loader_lua* > -r-xr-xr-x 2 root wheel - 737280 3 Juni 12:33 /boot/loader_lua.efi* > -r-xr-xr-x 1 root wheel - 569344 3 Juni 07:45 /boot/loader_lua.old* > -r-xr-xr-x 1 root wheel - 446464 3 Juni 12:33 /boot/loader_simp* > -r-xr-xr-x 1 root wheel - 589312 3 Juni 12:33 /boot/loader_simp.efi* > -r-xr-xr-x 1 root wheel - 446464 3 Juni 07:45 /boot/loader_simp.old* > > on FreeBSD 14.0-CURRENT #58 main-n263387-556b43492297: Fri Jun 2 20:19:5= 5 > CEST 2023 amd64. > > which suggests a ~60k bump for adding forth and ~115k bump for lua. So > the > > 560,000 may need to be 625,000 > > which is living life on the edge for 4th, and simply too big for lua. > > > > I'd be open to adding docs on this, since I don't think this option is > > currently documented since I added it > > to experiment around with a good value. > > See above, personally I'd like to see some hints on that variable, even i= f > I do not fiddle > around with it. > OK. that makes sense. In fact, it may make sense to disable the build of the BIOS loader entirely sometimes, which we can't easily do today. > > > > And no, I really do not want to support 'loadable modules'. BIOS bootin= g > is > > on the way out, and people > > that want to do complex stuff in the boot loader will simply have to do > > that in UEFI or maybe kboot/LinuxBoot. > > There's low RoI on adding this complexity, imho. We'd be better off, > imho, > > making things like the graphics > > console optional since the fonts and code for that free up about 30k in > > stupid experiments that I've done > > (it's hard since vidconsole has a lot of calls into the graphics system > > that aren't optional and easy to disable, > > so I've had to do hack and slash to produce a super ugly result that is > > only suggestive of the final savings): > > -rw-r--r-- 1 imp imp 352256 May 31 12:04 loader_simp > > I don't know if I slashed too much, or not enough since the code is > rather > > hard to separate out, so if you > > really wanted to go down this path, it would take a lot of work and > patient > > understanding to make it so with > > the low end of savings 20k and the high end on the order of maybe 40k. > > > > There's likely other ways to conserve space. We've not had space issues > > with loader, et al, in the past, > > so it's not well setup for subsetting. Though the different filesystem > > support might also net you a fair amount: > > LOADER_NET_SUPPORT?=3D yes > > LOADER_NFS_SUPPORT?=3D yes > > LOADER_TFTP_SUPPORT?=3D yes > > LOADER_CD9660_SUPPORT?=3D yes > > LOADER_EXT2FS_SUPPORT?=3D yes > > LOADER_MSDOS_SUPPORT?=3D yes > > LOADER_UFS_SUPPORT?=3D yes > > LOADER_GZIP_SUPPORT?=3D yes > > LOADER_BZIP2_SUPPORT?=3D yes > > as would compiling w/o ZFS, which uses its own method (eg > > WITHOUT_LOADER_ZFS). Tuning the loader > > at this level does start to get into the weeds a bit, but can offer ~40= k > > savings turning off all but NET and UFS: > > -rw-r--r-- 1 imp imp 344064 May 31 12:11 loader_simp > > you get even about ~100k when you disable ZFS support with > > -DWITHOUT_LOADER_ZFS: > > -rw-r--r-- 1 imp imp 241664 May 31 12:12 loader_simp > > (both of these are with the graphics console enabled without the silly > > hacks to see how much that takes up). > > Without the extras and ZFS, you might have bearssl and lua together > even... > > > > Hope this helps. > > Very much appreciated, thanks. > > I'm not so much concerned by the space sonsumption or a corrupted boot > process, I don't even > know whether I really need this i386 stuff mentioned here, since all of m= y > boxes are UEFI, > except the APU2, which are driven by SeaBIOS and bootin non UEFI. > Yea, I'm starting to think that the best way forward should include some way to turn off the BIOS loader if you know you won't need it and it's too big. > The cosmetic issue is that whenever anything reagrding the loader gets > touched by the > compiler, out build system drops out with an error - a second run then > performs clean (which > is a kind of weird I guess). > Yea, the check should cause it to be deleted when it fails, but doesn't. Warner > > > > Warner > > Thank you very much, > > Kind regards > Oliver > > > -- > O. Hartmann > --000000000000d945db05fd3fc245 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sat, Jun 3, 2023 at 9:03=E2=80=AFA= M FreeBSD User <freebsd@walsta= tt-de.de> wrote:
Am Wed, 31 May 2023 12:15:12 -0600
Warner Losh <imp@bsd= imp.com> schrieb:

Sorry for the late response.


> On Mon, May 29, 2023 at 2:59=E2=80=AFAM FreeBSD User <freebsd@walstatt-de.de&g= t; wrote:
>
> > Hello,
> >
> > on CURRENT, enabling in /etc/src.conf
> >
> > WITH_BEARSSL=3D
> >
> > seems to result in a slightly enlarged loader binary, which seems= to have
> > a fixed size
> > supposed on the error I get. See below.
> >
> > The system is amd64 (64 bit), for the record.
> >
> > Somewhere in the past developers mentioned this upcoming problem = and
> > provided a knob to adjust
> > the used size - I forgot about that knob and I couldn't find = it even in
> > the loader docs - or
> > looked at the wrong places.
> >
> > Can someone help me out here?
> >
> > The first error stops compileing world/kernel, but taking a secon= d run,
> > the error goes away.
> >
> > Kind regards and thanks in advance,
> >
> > oh
> >
> >
> >
> > [...]
> > --- all_subdir_stand/efi ---
> > SOURCE_DATE_EPOCH=3D1451606400=C2=A0 objcopy -j .peheader -j .tex= t -j .sdata -j
> > .data=C2=A0 -j .dynamic -j
> > .dynsym -j .rel.dyn=C2=A0 -j .rela.dyn -j .reloc -j .eh_frame -j<= br> > > set_Xcommand_set=C2=A0 -j
> > set_Xficl_compile_set=C2=A0 --output-target=3Defi-app-x86_64 load= er_4th.sym
> > loader_4th.efi ---
> > all_subdir_stand/i386 ---
> >
> > -8112 bytes available 7.71 real=C2=A0 =C2=A0 =C2=A0 =C2=A0 12.86 = user=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A03.08 sys=C2=A0
>
>
> bummer. I hate it when it's that close.
>
> You can try setting LOADERSIZE=3D560000 in your environment. We curren= tly set
> the maximum to 550,000

I tried to find find anything related to LOADER or SIZE in the docs. I reme= mber you mentioned
the existence of that variable months ago, but with no clue what to look af= ter, it is almost
impossible yo figure out as a non developer what the right knob might be.

Fair point.
=C2=A0
A grep -r on /usr/src shows up only in

[...]
./stand/i386/loader/Makefile:LOADERSIZE?=3D=C2=A0 =C2=A0 =C2=A0 =C2=A055000= 0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 # Largest known safe size for
loader.bin
./stand/i386/loader/Makefile:=C2=A0 =C2=A0@set -- `ls -l ${.TARGET}` ; x=3D= $$((${LOADERSIZE}-$$5)); \
[...]

There is no sign/trace of it in any man page related to loader and sibbling= s. I found the
variable rather quickly after knowing what to look after.
<= div>
To be fair, this is a very under documented area, semi o= n purpose...=C2=A0 But that's a good point that it is
under d= ocumented. And now that the size is creeping=C2=A0up and we have options th= at explode things,
maybe it should be better documented.
=C2=A0
> bytes because that's the most conservative number due to variation= in the
> available BIOS space available.
> This likely can be set even higher if you don't have add-in cards = that are
> consuming space in the lower 640k
> of memory. 640k is the absolute limit, but you need 20-30k of stack fo= r the
> loader so pushing this much past
> 625,000 or maybe 630,000 increases the risk of run-time crashes as the=
> stack smashes through the top of
> the loader program. You may also have to disable the lua build, since = it
> uses more stack and is just a smidge
> larger than the forth build. _simp will be the smallest of them all. O= n my
> system, without bearssl, I see:
> -r-xr-xr-x=C2=A0 3 root=C2=A0 wheel=C2=A0 503808 May 22 15:25 /boot/lo= ader_lua
> -r-xr-xr-x=C2=A0 1 root=C2=A0 wheel=C2=A0 446464 May 22 15:25 /boot/lo= ader_4th
> -r-xr-xr-x=C2=A0 1 root=C2=A0 wheel=C2=A0 385024 May 22 15:25 /boot/lo= ader_simp

In my case, with supposedly blewn up loader size by BEARSSL enables, it is:=

-r-xr-xr-x=C2=A0 1 root=C2=A0 wheel=C2=A0 - 503808=C2=A0 3 Juni 12:33 /boot= /loader_4th*
-r-xr-xr-x=C2=A0 1 root=C2=A0 wheel=C2=A0 - 643584=C2=A0 3 Juni 12:33 /boot= /loader_4th.efi*
-r-xr-xr-x=C2=A0 1 root=C2=A0 wheel=C2=A0 - 503808=C2=A0 3 Juni 07:45 /boot= /loader_4th.old*
-r-xr-xr-x=C2=A0 3 root=C2=A0 wheel=C2=A0 - 569344=C2=A0 3 Juni 12:33 /boot= /loader_lua*
-r-xr-xr-x=C2=A0 2 root=C2=A0 wheel=C2=A0 - 737280=C2=A0 3 Juni 12:33 /boot= /loader_lua.efi*
-r-xr-xr-x=C2=A0 1 root=C2=A0 wheel=C2=A0 - 569344=C2=A0 3 Juni 07:45 /boot= /loader_lua.old*
-r-xr-xr-x=C2=A0 1 root=C2=A0 wheel=C2=A0 - 446464=C2=A0 3 Juni 12:33 /boot= /loader_simp*
-r-xr-xr-x=C2=A0 1 root=C2=A0 wheel=C2=A0 - 589312=C2=A0 3 Juni 12:33 /boot= /loader_simp.efi*
-r-xr-xr-x=C2=A0 1 root=C2=A0 wheel=C2=A0 - 446464=C2=A0 3 Juni 07:45 /boot= /loader_simp.old*

on FreeBSD 14.0-CURRENT #58 main-n263387-556b43492297: Fri Jun=C2=A0 2 20:1= 9:55 CEST 2023 amd64.
> which suggests a ~60k bump for adding forth and ~115k bump for lua. So= the
> 560,000 may need to be 625,000
> which is living life on the edge for 4th, and simply too big for lua.<= br> >
> I'd be open to adding docs on this, since I don't think this o= ption is
> currently documented since I added it
> to experiment around with a good value.

See above, personally I'd like to see some hints on that variable, even= if I do not fiddle
around with it.

OK. that makes sense. I= n fact, it may make sense to disable the build of the BIOS
loader= entirely sometimes, which we can't easily do today.
=C2=A0
>
> And no, I really do not want to support 'loadable modules'. BI= OS booting is
> on the way out, and people
> that want to do complex stuff in the boot loader will simply have to d= o
> that in UEFI or maybe kboot/LinuxBoot.
> There's low RoI on adding this complexity, imho. We'd be bette= r off, imho,
> making things like the graphics
> console optional since the fonts and code for that free up about 30k i= n
> stupid experiments that I've done
> (it's hard since vidconsole has a lot of calls into the graphics s= ystem
> that aren't optional and easy to disable,
> so I've had to do hack and slash to produce a super ugly result th= at is
> only suggestive of the final savings):
> -rw-r--r--=C2=A0 1 imp=C2=A0 imp=C2=A0 352256 May 31 12:04 loader_simp=
> I don't know if I slashed too much, or not enough since the code i= s rather
> hard to separate out, so if you
> really wanted to go down this path, it would take a lot of work and pa= tient
> understanding to make it so with
> the low end of savings 20k and the high end on the order of maybe 40k.=
>
> There's likely other ways to conserve space. We've not had spa= ce issues
> with loader, et al, in the past,
> so it's not well setup for subsetting. Though the different filesy= stem
> support might also net you a fair amount:
> LOADER_NET_SUPPORT?=3D=C2=A0 =C2=A0 yes
> LOADER_NFS_SUPPORT?=3D=C2=A0 =C2=A0 yes
> LOADER_TFTP_SUPPORT?=3D=C2=A0 =C2=A0yes
> LOADER_CD9660_SUPPORT?=3D yes
> LOADER_EXT2FS_SUPPORT?=3D yes
> LOADER_MSDOS_SUPPORT?=3D=C2=A0 yes
> LOADER_UFS_SUPPORT?=3D=C2=A0 =C2=A0 yes
> LOADER_GZIP_SUPPORT?=3D=C2=A0 =C2=A0yes
> LOADER_BZIP2_SUPPORT?=3D=C2=A0 yes
> as would compiling w/o ZFS, which uses its own method (eg
> WITHOUT_LOADER_ZFS). Tuning the loader
> at this level does start to get into the weeds a bit, but can offer ~4= 0k
> savings turning off all but NET and UFS:
> -rw-r--r--=C2=A0 1 imp=C2=A0 imp=C2=A0 344064 May 31 12:11 loader_simp=
> you get even about ~100k when you disable ZFS support with
> -DWITHOUT_LOADER_ZFS:
> -rw-r--r--=C2=A0 1 imp=C2=A0 imp=C2=A0 241664 May 31 12:12 loader_simp=
> (both of these are with the graphics console enabled without the silly=
> hacks to see how much that takes up).
> Without the extras and ZFS, you might have bearssl and lua together ev= en...
>
> Hope this helps.

Very much appreciated, thanks.

I'm not so much concerned by the space sonsumption or a corrupted boot = process, I don't even
know whether I really need this i386 stuff mentioned here, since all of my = boxes are UEFI,
except the APU2, which are driven by SeaBIOS and bootin=C2=A0 non UEFI.
=

Yea,=C2=A0 I'm starting to think that = the best way forward should include some way to turn off
the BIOS= loader if you know you won't need it and it's too big.
= =C2=A0
The cosmetic issue is that whenever anything reagrding the loader gets touc= hed by the
compiler, out build system drops out with=C2=A0 an error - a second run the= n performs clean (which
is a kind of weird I guess).

Yea, the c= heck should cause it to be deleted when it fails, but doesn't.

Warner
=C2=A0
>
> Warner

Thank you very much,

Kind regards
Oliver


--
O. Hartmann
--000000000000d945db05fd3fc245--