From nobody Sat Mar 11 16:48:18 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PYplr6gb6z3xqSh for ; Sat, 11 Mar 2023 16:48:56 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 4PYplr6Fd6z3kLc for ; Sat, 11 Mar 2023 16:48:56 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x532.google.com with SMTP id r15so5577715edq.11 for ; Sat, 11 Mar 2023 08:48:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678553335; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=DX3L0qJ6QeNoNNdqnrRVwgHunbKjh1ibKRGztUFyAu8=; b=kI33YiWAHl1GfJE5XcrKi9GRToO25lo6JC1X5nuu8bfv7yhqnuvrHj8riF2Xb6S8DC dklDu30vHsFilqAMP6lbrbC7r/U6x/rNMnsWLZmUFZgxxGqTg0CD/MxBG/qhV/8VGMR/ vhp37lTb3KaXflpvX7GXhhbi6gYec4qJyeLkT46x/PlIBFPd+A0RayBrAZCGHKXKsZu0 0yINO90hczAhU+IqbEJSQPQ4vZXcrZx01DkSGC9u9zaQpdE9KqFZ5t3rz/GtTrzKskl+ PGHBXIDnv1u3fZ0PdM4yrOdyUcewZVDxGXIRgfHQBvRmLv6t9Ba78q9znY5IEvU19cCy DkdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678553335; 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=DX3L0qJ6QeNoNNdqnrRVwgHunbKjh1ibKRGztUFyAu8=; b=oW2OJbEzdq1LgIKmYxdaSd4X/Hh08abQsEi4PHdIGIiVWw9lv5fVh5aRlgalylDLt3 DdMYeQpr1psOmT3AHfxwsU9ufMIOWgxxDkx/ucLTEpDJekA3i34/EPMnilnbhii7X7IK 7U4e1KccFghw+gqwMYhH7gY8kVLyQPf17BLWobbFaLU+Dan1AO8UaspFWlABHcfnPb4B tsPmeRDlJjU1Ty06JoaVHFFQrx2c7JXqSV4J82jiTFI2GejXpLwZRg/jD8INN97GxbbJ gh8iMeXG2/XOJduWD5HNgfkTsSxWiWbdBkH0hoGwBupySWhcsZPCF8UCZRqftD3S0f0L 8cXQ== X-Gm-Message-State: AO0yUKXeoZOqTXaQQqYWnCpezR3Q3Qm+8ovAOyA9Nd5rMupwJw/1/3m0 fSpOIgFvSg9LqaSTvzybRBIkAPn4buDQDetU1N5F3zpdhYEPpQ== X-Google-Smtp-Source: AK7set/2rvshYGbF3RpAiT9l8P4x8FttNzfgFxxMaqnkdR5mlfgb3D2tMBrJLE3Coj6Wrdhzqvmuj/D1T0/2s9QkH6Q= X-Received: by 2002:a17:906:6d98:b0:8ab:b606:9728 with SMTP id h24-20020a1709066d9800b008abb6069728mr15016231ejt.5.1678553334871; Sat, 11 Mar 2023 08:48:54 -0800 (PST) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Mario Marietto Date: Sat, 11 Mar 2023 17:48:18 +0100 Message-ID: Subject: Re: quirks To: Souji Thenria Cc: freebsd-hackers@freebsd.org Content-Type: multipart/alternative; boundary="00000000000042faa705f6a2a7a2" X-Rspamd-Queue-Id: 4PYplr6Fd6z3kLc 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 --00000000000042faa705f6a2a7a2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello. Exactly. This is valid even in the scenario that I'm going to explain. I would like to allow the passthru of an nVidia gpu to a Windows VM (virtualized with bhyve). Infact after one month of research we (me,an humble bugs hunter,soft system administrator and developers recruiter) in collaboration with Corvin Kohne and some other developers we have found the technical reasons why a modern nvidia gpu if passed through inside a windows 10 / 11 vm produces the error 43 (actually the error 12 after having added some new features). It happens because it misses "line interrupts support for passed through devices" ; actually there is the need of a massive change inside the bhyve source code. I'm collaborating with one hypervisor developer and a qemu/kvm/haxm advanced developer to reach that goal. To achieve the goal will be a very step forward for bhyve and for all the BSD community. We have an external,affiliated github and all the changes we made go inside it first of all and only later,maybe much later,some of them will go inside the official bhyve source code. But we want to have this experimental feature in a reasonable amount of time,not in many many years.i There is a partial INTx support missing in bhyve and it is an important feature already implemented in qemu a lot of time ago. Bhyve can't miss it. Passing thru an AMD and an NVIDIA modern GPU card inside a Windows VM will expand the number of tasks that can be done in FreeBSD using Windows as an intermediate medium. I'm interested in the development of bhyve. Not only to the passthru. I'm trying to help to improve bhyve trying many combinations and looking for bugs. I would really like it if one nvidia gpu can be passed to a windows 10 vm, First of all because I like challenges. I like to break the limits that do not allow users to freely use many functions connected to the purchased item. And second,I like everything that sounds geek / geekish that I can assemble and disassemble like legos,to understand how it works "inside". Unfortunately I'm not a developer. But I've found some very competent programmers who want to collaborate and I'm trying to find others to start working on this project. On november 2021,with the collaboration of Corvin Kohne and Peter Grehan,we have been able to pass through succesfully an nvidia graphic card inside a linux os,as u can see below,may people demonstrate appreciation : https://twitter.com/bhyve_dev/status/1459298927312662528 On Sat, Mar 11, 2023 at 5:46=E2=80=AFPM Souji Thenria wrote: > On 3/11/23 16:43, void wrote: > > What are 'quirks', how are they applied, why, where can I read up about > > them, are they documented? > > Hey tia, > > I have found this [http://www.root.org/~nate/freebsd/scsi/quirks.html]: > > FreeBSD drivers make every attempt possible to support the standards > behind hardware. Where possible and not in conflict with the standard, > they also attempt to work around hardware which doesn't strictly > conform. However, some devices have flaws which can't be worked around > while keeping the driver compatible with the standard. For these > devices, we have created a quirks mechanism to indicate to the driver > that it must avoid certain commands or use them differently with a > specific model and/or version of hardware. This document focuses on > identifying and committing quirks for storage hardware involving CAM and > UMASS but is applicable to other areas. > > Based on that, quirks are just identifiers for the driver, to compensate > for non-standard hardware implementations. > > -- > Souji Thenria > > > --=20 Mario. --00000000000042faa705f6a2a7a2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 
Hello.

Exactly. This is valid even in the s=
cenario that I'm going to explain.
I would like to allow the passthr=
u of an nVidia gpu to a Windows VM (virtualized with bhyve). 
Infact aft=
er one month of research we (me,an humble bugs hunter,soft system=20
administrator and developers recruiter) in collaboration with Corvin=20
Kohne and some other developers we have found the technical reasons why a
modern nvidia gpu if passed through inside a windows 10 / 11 vm=20
produces the error 43 (actually the error 12 after having added some new
features). It happens because it misses "line interrupts support for=
=20
passed through devices" ; actually there is the need of a massive chan=
ge
inside the bhyve source code. I'm collaborating with one hypervisor=20
developer and a qemu/kvm/haxm advanced developer to reach that goal. To=20
achieve the goal will be a very step forward for bhyve and for all the=20
BSD community. We have an external,affiliated github and all the changes
we made go inside it first of all and only later,maybe much later,some=20
of them will go inside the official bhyve source code. But we want to=20
have this experimental feature in a reasonable amount of time,not in=20
many many years.i There is a partial INTx support missing in bhyve and=20
it is an important feature already implemented in qemu a lot of time=20
ago. Bhyve can't miss it. Passing thru an AMD and an NVIDIA modern GPU=
=20
card inside a Windows VM will expand the number of tasks that can be=20
done in FreeBSD using Windows as an intermediate medium. I'm interested=
=20
in the development of bhyve. Not only to the passthru. I'm trying to=20
help to improve bhyve trying many combinations and looking for bugs. 
I =
would really like it if one nvidia gpu can be passed to a windows 10 vm,First of all because I like challenges. I like to break the limits that do=
=20
not allow users to freely use many functions connected to the purchased=20
item. And second,I like everything that sounds geek / geekish that I=20
can assemble and disassemble like legos,to understand how it works=20
"inside". Unfortunately I'm not a developer. But I've fou=
nd some very=20
competent programmers who want to collaborate and I'm trying to find=20
others to start working on this project. On november 2021,with the=20
collaboration of Corvin Kohne and Peter Grehan,we have been able to pass th=
rough=20
succesfully an nvidia graphic card inside a linux os,as u can see=20
below,may people demonstrate appreciation :



<= div class=3D"gmail_quote">
On Sat, Mar= 11, 2023 at 5:46=E2=80=AFPM Souji Thenria <mail@souji-thenria.net> wrote:
On 3/11/23 16:43, void wrote:
> What are 'quirks', how are they applied, why, where can I read= up about
> them, are they documented?

Hey tia,

I have found this [http://www.root.org/~nate/freeb= sd/scsi/quirks.html]:

FreeBSD drivers make every attempt possible to support the standards
behind hardware. Where possible and not in conflict with the standard,
they also attempt to work around hardware which doesn't strictly
conform. However, some devices have flaws which can't be worked around =
while keeping the driver compatible with the standard. For these
devices, we have created a quirks mechanism to indicate to the driver
that it must avoid certain commands or use them differently with a
specific model and/or version of hardware. This document focuses on
identifying and committing quirks for storage hardware involving CAM and UMASS but is applicable to other areas.

Based on that, quirks are just identifiers for the driver, to compensate for non-standard hardware implementations.

--
Souji Thenria




--
Mario.
--00000000000042faa705f6a2a7a2-- From nobody Sun Mar 12 13:54:10 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PZLqq3z4bz3xv44 for ; Sun, 12 Mar 2023 13:54:15 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PZLqp2qkMz3L04 for ; Sun, 12 Mar 2023 13:54:14 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b=P++EI67P; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=YMBOk1Zr; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.24 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id AE83332003D3 for ; Sun, 12 Mar 2023 09:54:12 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 12 Mar 2023 09:54:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm2; t=1678629252; x=1678715652; bh=iK AfOyyzMmmOwuG8BQPgii69Cc+sh93MNly+WTl8W/g=; b=P++EI67Po7az2l5e0O jLwZs6L/heuy4GgOUVt5TO71/wDw4lyAh3n3yMhpgEAvGtCboJozgpeTMGoIpXtQ lVtUrvVgnqcEOs5Z+XrwMfWtI0JPJZQzrAkLlhRrhJgACoQ6uNCVspqYkZ+zgV0q 4oNjyru2w1MqyYyo4h6/ogQQkrqjf8Y0yV/HI/T3xjJLccrMLQ1B5U0iZkf8W/wW qVyQwR7xKFh+W1aMLYPxVOGIM4SQXIc8jbRIRTF9b5DqbY7PCtDW0zQ3R0i6qzyD ehHIYVsCsd7PNOKbQHh4kyCMQZUbWF6JwFtxSaxAI3E9uSDxQPqTNgwA9QcKDtZe sfyA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; t=1678629252; x=1678715652; bh=iKAfOyyzMmmOw uG8BQPgii69Cc+sh93MNly+WTl8W/g=; b=YMBOk1Zrt4iKENRXrgB97Q6VLYApm px523QCRcS+8PZ5cBJA0NpaSBGtT4Af1F8B7Gnx9CbE5i+L9F15Z9GjojNp+p8V9 K8+nThWT6E00U1i1tZvHyC4Rem2sBfeang9f0Wkgd2vm4OQOCeSeBHDj0wEfAII2 cFIRFxmn/on5oNw7WpX1g/pp87utV4/PQiQciDnC3EbqSBt8DkVeFcPCuRYQaUCs 7aJuOEeRMnPa9GuEpXFSJpnYuGoylwY1TI42qcJFCUIsK7tPyC24LlRUq2oBIHd9 AEr/xDQDNibVhMVlAAfMSAh6UER+l2WNF0xMO2CiH0aVRrbwQSPxAPxPw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvddvvddgheeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnhepjeetkeeffedvieelffegkeeugfetgfejfffgteevkeeufeefledvkeekvd ffkeetnecuffhomhgrihhnpehrohhothdrohhrghenucevlhhushhtvghrufhiiigvpedt necurfgrrhgrmhepmhgrihhlfhhrohhmpehvohhiugesfhdqmhdrfhhm X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sun, 12 Mar 2023 09:54:11 -0400 (EDT) Date: Sun, 12 Mar 2023 13:54:10 +0000 From: void To: freebsd-hackers@freebsd.org Subject: Re: quirks Message-ID: Mail-Followup-To: freebsd-hackers@freebsd.org References: List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-4.60 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.24]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.24:from]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; RCPT_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; FREEMAIL_FROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[64.147.123.24:from]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4PZLqp2qkMz3L04 X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N On Sat, Mar 11, 2023 at 05:45:44PM +0100, Souji Thenria wrote: > >I have found this [http://www.root.org/~nate/freebsd/scsi/quirks.html]: Thanks for that, very useful -- From nobody Sun Mar 12 14:46:44 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PZN0g4sTxz3xxZV for ; Sun, 12 Mar 2023 14:46:59 +0000 (UTC) (envelope-from manav1811kumar@gmail.com) Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (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 4PZN0f4FvLz3h8D for ; Sun, 12 Mar 2023 14:46:58 +0000 (UTC) (envelope-from manav1811kumar@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=B5VjISIG; spf=pass (mx1.freebsd.org: domain of manav1811kumar@gmail.com designates 2607:f8b0:4864:20::62f as permitted sender) smtp.mailfrom=manav1811kumar@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-pl1-x62f.google.com with SMTP id ja10so670724plb.5 for ; Sun, 12 Mar 2023 07:46:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678632416; h=mime-version:subject:references:in-reply-to:message-id:to:from:date :from:to:cc:subject:date:message-id:reply-to; bh=YlsVVboT+nO72+XHU4l5rwRN3fvyPn0jiQtiSqf+g0o=; b=B5VjISIGvV7i2PH2qOAhn+8ZHfYgRAXWBl+duFT0bsheIdF8/WhxA5HNvSQD/KaP6i l+SIAJBnfJQ+KGP/4Q52NCHexXFLmYAU823VY3m3iSa5HS0OgVNl+GzeeiUOV8KqSShq C40So2eWovjS8pozOiI2uDp154SA6I5tZYKyxXNRv1mMAJZNMeL6w8eeQx/GqN8buBzq 5zargPkT7GtDHNZwG/jsTnhSxxO19C7tagMttbRdSBvuoR7bhnGEK8K6AWt/WKUN1ALT XPviv3rr9Znwcoi9mBBlKEbMTqqWfIzwphmoOgpnJJaXl/CVFAti76Qva78xvnpW/Fqv exsg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678632417; h=mime-version:subject:references:in-reply-to:message-id:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=YlsVVboT+nO72+XHU4l5rwRN3fvyPn0jiQtiSqf+g0o=; b=nA/hBs34RaD/ip4A5ZXdC33RX5Xxip5g1HP3xaMRtuPkLooIDdNhDGx/LxTRh8aDlt KFfIr/37DcsYz0E2HznXV44CLeWPGRPJo3Ngg1APHAwiJ17+ZcJ/jhZGwo48xGTA42in WBLzp7p8wQIMhKIc79iWHOapUH9ce1wXP3rOAYCkLCpiVjhFuJLcfKLtNLqL/aAZvzC8 USywMlW6xpMEUa9hLdSpG8wDG8MgN1GBnN9CEz5SY7lyERlCYQN29FeVbwiBMOlrd2b1 oY6xI6f3w6bYcKguMaySir1ivIIcumazEAecDXBckAUQCWb2ZcVhjJwBh6BGlou+2V3k 1BhQ== X-Gm-Message-State: AO0yUKUb0ORdXmmDu4+sVawrtLGPlpXadw/800VujZl7yMpACjNGvqxq ehYBlPkE4kXzEqbG2XQ8f20yRR/V7Ts= X-Google-Smtp-Source: AK7set8SietBHSYB1vCwsZoqtm8wSgT6KOJrq0nIhWWQ6oOR6fzO1wRDNRPaHWq1pJpwyKXUoIpaMg== X-Received: by 2002:a05:6a20:7f85:b0:cb:c276:5898 with SMTP id d5-20020a056a207f8500b000cbc2765898mr37078886pzj.0.1678632416647; Sun, 12 Mar 2023 07:46:56 -0700 (PDT) Received: from [2401:4900:1f33:95b9:100::] ([2401:4900:1f33:95b9:e482:7d0f:1860:2f9]) by smtp.gmail.com with ESMTPSA id d19-20020a63d713000000b0050301745a5dsm2943014pgg.50.2023.03.12.07.46.53 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 Mar 2023 07:46:56 -0700 (PDT) Date: Sun, 12 Mar 2023 20:16:44 +0530 From: MANAV KUMAR To: freebsd-hackers@freebsd.org Message-ID: In-Reply-To: References: Subject: Re: quirks X-Readdle-Message-ID: d3cc8636-7c46-40fb-b14c-dbe37a523259@Spark List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="640de5db_643c9869_10658" X-Spamd-Result: default: False [-3.47 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.974]; MID_RHS_NOT_FQDN(0.50)[]; 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=20210112]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::62f:from]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; DKIM_TRACE(0.00)[gmail.com:+]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4PZN0f4FvLz3h8D X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N --640de5db_643c9869_10658 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Pls unsubscribe me from the emailing list. Best Regards, Manav Kumar Sr. Member Of Technical Staff, Siemens EDA Mob: 9592830271 Mailto: manav1811kumar@gmail.com / mkumar_be17@thapar.edu On 12 Mar 2023, 7:24 PM +0530, void , wrote: > On Sat, Mar 11, 2023 at 05:45:44PM +0100, Souji Thenria wrote: > > > > I have found this [http://www.root.org/~nate/freebsd/scsi/quirks.html]: > > Thanks for that, very useful > -- > --640de5db_643c9869_10658 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Pls unsubscribe me from the emailing list.

Best Regards,
Manav Kumar
Sr. Member Of Technical Staff, Siemen= s EDA=E2=80=8B
Mob: 9592830271
Mailto: manav1811kumar=40gmail.com / mkumar=5Fbe17=40= thapar.edu

On 12 Mar 2023, 7:24 PM +0530, void= <void=40f-m.fm>, wrote:
On Sat, Mar 11, 2023 at 05:45:44PM +0100, Souji Thenria wrote:<= br />

I have found this =5Bhttp://www.root.org/=7Enate/freebsd/scsi/quirks.html= =5D:

Thanks for that, very useful
--

--640de5db_643c9869_10658-- From nobody Sun Mar 12 15:53:10 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PZPTJ1xlbz3y22N for ; Sun, 12 Mar 2023 15:53:24 +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 4PZPTG1fCtz3nl4 for ; Sun, 12 Mar 2023 15:53:21 +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 32CFrBd7040711 for ; Mon, 13 Mar 2023 00:53:11 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Mon, 13 Mar 2023 00:53:10 +0900 From: Tomoaki AOKI To: freebsd-hackers@freebsd.org Subject: How to unsubscribe Message-Id: <20230313005310.2f6285930502a1f54f66928a@dec.sakura.ne.jp> In-Reply-To: References: Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.2) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-1.58 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.995]; NEURAL_HAM_LONG(-0.99)[-0.986]; 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-hackers@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-hackers@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4PZPTG1fCtz3nl4 X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N You should look into welcome mail you should have received when you register yourself here. It should contain descriptions as below. If you ever wish to unsubscribe, send a message to using this email address. The subject and the body of the message can be anything. You will then receive confirmation or further instructions. For other information and help about this list, send a message to . For everyone else: Sorry for the noise. Gmail hesitates to receive from my email address directly, maybe because the SMTP server doesn't add SPF record. On Sun, 12 Mar 2023 20:16:44 +0530 MANAV KUMAR wrote: > Pls unsubscribe me from the emailing list. > > Best Regards, > Manav Kumar > Sr. Member Of Technical Staff, Siemens EDA > Mob: 9592830271 > Mailto: manav1811kumar@gmail.com / mkumar_be17@thapar.edu > > On 12 Mar 2023, 7:24 PM +0530, void , wrote: > > On Sat, Mar 11, 2023 at 05:45:44PM +0100, Souji Thenria wrote: > > > > > > I have found this [http://www.root.org/~nate/freebsd/scsi/quirks.html]: > > > > Thanks for that, very useful > > -- > > -- Tomoaki AOKI From nobody Sun Mar 12 18:55:17 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PZTWT1DGGz3xTsM for ; Sun, 12 Mar 2023 18:55:33 +0000 (UTC) (envelope-from dmitry@kernelgen.org) Received: from mail-oa1-x30.google.com (mail-oa1-x30.google.com [IPv6:2001:4860:4864:20::30]) (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 4PZTWR5pPkz46wt for ; Sun, 12 Mar 2023 18:55:31 +0000 (UTC) (envelope-from dmitry@kernelgen.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=kernelgen-org.20210112.gappssmtp.com header.s=20210112 header.b=YDT9vMmT; spf=none (mx1.freebsd.org: domain of dmitry@kernelgen.org has no SPF policy when checking 2001:4860:4864:20::30) smtp.mailfrom=dmitry@kernelgen.org; dmarc=none Received: by mail-oa1-x30.google.com with SMTP id 586e51a60fabf-177b78067ffso479594fac.7 for ; Sun, 12 Mar 2023 11:55:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernelgen-org.20210112.gappssmtp.com; s=20210112; t=1678647329; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=XZf6nDWM2o9K+HQswL493EW21E2fNekUDS3hcGi8D5A=; b=YDT9vMmTjY2w19AdQUYNWv9xYpSelIdqNredTz0TrWaYbc4bDJLIkG+IdYNlwRbMun o9U8zVFzE++TSpVV3IS5GNbmYNcs/xZIRMwQ2vuEMJEJrJHkIyb96n4K5xvyrvHQPw4K thLSEQJkaa8qlgmWixqqkTaJt3OS22wGFj1wXwRSQnG35ZJIquRcECGE619CjNrNFtBC 3DqaDVnJli5alJ7qeAjF7qqXwGqvQOLiAHdUWrOsp3MBzeo0bDKi/2P9HA8YiijmTrXl BFUzkXQ6lR8PMNJyno1ZwHg8SYy0GT1BS9prvTIwDx/spgVWAcaoKOJYD4iFx8rZEncd Qp7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678647329; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=XZf6nDWM2o9K+HQswL493EW21E2fNekUDS3hcGi8D5A=; b=zBNlt5LcDZsSBS7ipBo/LXlBb38xiO9958ajTsOKevC98cffgYCicvy5oGWoJZRdFa 93uPy/3KHC0THnRZFW4MDVCcwu8zon/I2V/Blg/2ePcVmG58OiWuthyf0uxdispuVbJf E3dA0mkzYFH04MauzSE+RQJf14AobCBffsdIMPqZ86NwQpozMNJv2p4kBZANcWK2pRgE /aYBqHCFWHjtp07IXYr+b0unMeHr4UQKZpHanxXWst6itNDdSE4+ieRXiRMl1+LT0s2b hcaXs+OxomNnfPrdqukX/YEBJEiU0QSRR8MHfSnbaq8cXrn7eCKSbgm2CNpNjj8iKNUw rkAg== X-Gm-Message-State: AO0yUKVPRYy29lefWmbBPW2MrHfzvjscsHP/jAXot2Fbvy7lsV//gmbk a7hYkMpQNGO0860PNBS9VWpyrfaEhfD7f285xcQh40CTshj2H6WYoh0= X-Google-Smtp-Source: AK7set9ENh5pf9/oL2j0Zl7Rp+iWqoT37uoiKtvdMKGY5A/Yr4m233nQtxqzzKZOywOarYRUjeMZDX0m2/vRD967sng= X-Received: by 2002:a05:6870:1247:b0:177:a8c9:9028 with SMTP id 7-20020a056870124700b00177a8c99028mr624846oao.11.1678647329504; Sun, 12 Mar 2023 11:55:29 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 From: Dmitry Mikushin Date: Sun, 12 Mar 2023 19:55:17 +0100 Message-ID: Subject: Does FreeBSD support ramdisk via U-boot? To: freebsd-hackers@freebsd.org Content-Type: multipart/alternative; boundary="000000000000c76b2605f6b8893a" X-Spamd-Result: default: False [-2.30 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; R_DKIM_ALLOW(-0.20)[kernelgen-org.20210112.gappssmtp.com:s=20210112]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_IN_DNSWL_NONE(0.00)[2001:4860:4864:20::30:from]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; R_SPF_NA(0.00)[no SPF record]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[kernelgen-org.20210112.gappssmtp.com:+]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DMARC_NA(0.00)[kernelgen.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4PZTWR5pPkz46wt X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --000000000000c76b2605f6b8893a Content-Type: text/plain; charset="UTF-8" >From U-boot we can specify the initrd argument to booti. The FreeBSD kernel boots fine, but it doesn't sense the presence of ramdisk. Is it supported in general, is there possibly some configuration missing? booti $kernel_addr_r $ramdisk_addr_r:$filesize $fdt_addr_r Uncompressing Kernel Image Moving Image from 0x2080000 to 0x2200000, end=2fbe000 ## Flattened Device Tree blob at 02000000 Booting using the fdt blob at 0x2000000 Working FDT set to 2000000 Loading Ramdisk to 7df27000, end 7df2807d ... OK Loading Device Tree to 000000007df17000, end 000000007df2658f ... OK Working FDT set to 7df17000 Starting kernel ... ---<>--- GDB: debug ports: uart GDB: current port: uart KDB: debugger backends: ddb gdb KDB: current backend: ddb WARNING: DTB version is 5.9 while kernel expects 5.13, please update the DTB in the ESP Copyright (c) 1992-2023 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 14.0-CURRENT #0 main-n261390-129ea078cd16-dirty: Sun Mar 12 01:44:19 CET 2023 ... mountroot> ? List of GEOM managed disk devices: (empty) --000000000000c76b2605f6b8893a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
From U-boot we can specify the initrd argument to booti. T= he FreeBSD kernel boots fine, but it doesn't sense the presence of ramd= isk. Is it supported in general, is there possibly some configuration missi= ng?

booti $kernel_addr_r $ramdisk_addr_r:$filesize = $fdt_addr_r
=C2=A0 =C2=A0Uncompressing Kernel Image
Moving Image from= 0x2080000 to 0x2200000, end=3D2fbe000
## Flattened Device Tree blob at = 02000000
=C2=A0 =C2=A0Booting using the fdt blob at 0x2000000
Working= FDT set to 2000000
=C2=A0 =C2=A0Loading Ramdisk to 7df27000, end 7df280= 7d ... OK
=C2=A0 =C2=A0Loading Device Tree to 000000007df17000, end 0000= 00007df2658f ... OK
Working FDT set to 7df17000

Starting kernel .= ..

---<<BOOT>>---
GDB: debug ports: uart
GDB: curr= ent port: uart
KDB: debugger backends: ddb gdb
KDB: current backend: = ddb
WARNING: DTB version is 5.9 while kernel expects 5.13, please update= the DTB in the ESP
Copyright (c) 1992-2023 The FreeBSD Project.
Copy= right (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
=C2= =A0 =C2=A0 =C2=A0 =C2=A0 The Regents of the University of California. All r= ights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundat= ion.
FreeBSD 14.0-CURRENT #0 main-n261390-129ea078cd16-dirty: Sun Mar 12= 01:44:19 CET 2023
...
mountroot> ?

Lis= t of GEOM managed disk devices:

(empty)
<= /div> --000000000000c76b2605f6b8893a-- From nobody Mon Mar 13 16:22:57 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Pb2513ZyHz3xv32 for ; Mon, 13 Mar 2023 16:23:01 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pb25057V8z4F8F for ; Mon, 13 Mar 2023 16:23:00 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b=mTaIkn2b; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=moSd8YNJ; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.27 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 8C4AD5C01F0 for ; Mon, 13 Mar 2023 12:22:59 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Mon, 13 Mar 2023 12:22:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:sender:subject:subject:to:to; s=fm2; t=1678724579; x=1678810979; bh=0x2PZQD1CUZF0Ut38eyJ9pVZh A+2jG1OlTJMwoC54s0=; b=mTaIkn2bfSMfJpGN5E8oAN0HDnLzsdUAwSh2bN+e/ vWoJbyhrG6LWeKfm1ZzVGayP0Qik0Hmcw4C+J+bAhdxUIip+9SLazYZNB/Uqym2U j+exNXE1ie3X0BMfk/jgoZpbI5LS3beT5dVnhX/UFgANZqH69ex0d3QTBjdMnSbN /MxtN3qP272xfhuVi9Y9CtcNx391LkzkV86kTROjYazhMdkHbmxlBfnjswypdp3j fPVUgOy9NjBGu0xFTHMZ46agX7VHi/8rotPh9IAbpPXbh9VeuaRk9LAdagROq0MR qXcYmTs5/4Cmr/nVyBew3veB1zmW/6Eod0jfw7T9MiTZg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1678724579; x=1678810979; bh=0x2PZQD1CUZF0Ut38eyJ9pVZhA+2jG1OlTJ MwoC54s0=; b=moSd8YNJHElTkAzHT4vd7KQOlEpAaL6V9jmkMXBl20nDu9H9cXO GCbY1ziu5RhUtt8K48wgOXjhZOd1ejygsO5BUTopSt95HGV+rnsjVCulBax6yDS1 CADDSDEqUeRkyVPw17p3xA0couc+WiIK5ZHDQV3X4Lhb/1jEEHMq80cn2CaryTNC 3G2WGo609rxstTHe8FsvKfL0BqOLPopnEWJ0eYYwrm5sCwhKhoHjAQBjDRrziKo4 PbSLKFaJy7kxT2o5oTYWym7C3lK9p8QGEOf7nPuUsFh73fCmXfdT59yiO8eNnwiD GKB77lj7gkvRXBIAsWWFRL1C6Mp9anKpu/Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvddvgedgkeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtugesthdtredttd dtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgrthht vghrnhepveduffeivdfffffghfegfeejfefftdeiteehteekfefhvdefgfettdeuheegff eunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepvhho ihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Mon, 13 Mar 2023 12:22:59 -0400 (EDT) Date: Mon, 13 Mar 2023 16:22:57 +0000 From: void To: freebsd-hackers@freebsd.org Subject: CPU supports Enhanced Speedstep, but is not recognized. Message-ID: Mail-Followup-To: freebsd-hackers@freebsd.org List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Spamd-Result: default: False [-4.52 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.98)[-0.977]; NEURAL_HAM_SHORT(-0.94)[-0.941]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.27]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.27:from]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; RCPT_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; FREEMAIL_FROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[66.111.4.27:from]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4Pb25057V8z4F8F X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N Hello hackers@ On a 13/stable system built today with generic kernel, there are these lines for each cpu in the dmesg:- ### est0: numa-domain 0 on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 231100002100 device_attach: est0 attach returned 6 ### and then, later ### interface hwpstate_intel.1 already present in the KLD 'kernel'! linker_load_file: /boot/kernel/cpufreq.ko - unsupported file type ### The system is a HP ProLiant dual Xeon E5-2690 v2, so there are 40 "cpus" ie 20 if hyperthreading is turned off, in total. I was kind of surprised this didn't work out-of-the-box considering the age of the cpu, its use-context and how widely it was/is used in that context. Clearly I'm doing something wrong or missing something. Should it work? Do I need to build a custom kernel? How can I debug this? I tried using powerd but I understand from later reading that powerd is incompatible with hwpstate_intel, so it's deactivated at the moment. -- From nobody Mon Mar 13 16:29:33 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Pb2Dk0fNLz3xvHy for ; Mon, 13 Mar 2023 16:29:42 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (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 "smarthost1.sentex.ca", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pb2Dj0Shqz4G27 for ; Mon, 13 Mar 2023 16:29:41 +0000 (UTC) (envelope-from mike@sentex.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of mike@sentex.net designates 2607:f3e0:0:1::12 as permitted sender) smtp.mailfrom=mike@sentex.net; dmarc=none Received: from pyroxene2a.sentex.ca (pyroxene19.sentex.ca [199.212.134.19]) by smarthost1.sentex.ca (8.17.1/8.16.1) with ESMTPS id 32DGTXKK024043 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL) for ; Mon, 13 Mar 2023 12:29:33 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [IPV6:2607:f3e0:0:4:cc49:d452:d41:c697] ([IPv6:2607:f3e0:0:4:cc49:d452:d41:c697]) by pyroxene2a.sentex.ca (8.16.1/8.15.2) with ESMTPS id 32DGTXZ3059295 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO) for ; Mon, 13 Mar 2023 12:29:33 -0400 (EDT) (envelope-from mike@sentex.net) Message-ID: <9df2ec48-aacd-e2c4-04b6-8cba90a237be@sentex.net> Date: Mon, 13 Mar 2023 12:29:33 -0400 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: CPU supports Enhanced Speedstep, but is not recognized. Content-Language: en-US To: freebsd-hackers@freebsd.org References: From: mike tancsa In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.84 X-Spamd-Result: default: False [-3.37 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_HAM_MEDIUM(-0.97)[-0.975]; R_SPF_ALLOW(-0.20)[+ip6:2607:f3e0::/32]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[199.212.134.19:received]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; ASN(0.00)[asn:11647, ipnet:2607:f3e0::/32, country:CA]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEFALL_USER(0.00)[mike]; RCVD_COUNT_THREE(0.00)[3]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; DMARC_NA(0.00)[sentex.net]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4Pb2Dj0Shqz4G27 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On 3/13/2023 12:22 PM, void wrote: > The system is a HP ProLiant dual Xeon E5-2690 v2, so there are 40 "cpus" > ie 20 if hyperthreading is turned off, in total. > > I was kind of surprised this didn't work out-of-the-box considering > the age of the cpu, its use-context and how widely it was/is used > in that context. Clearly I'm doing something wrong or missing something. > > Should it work? > Is the hw pstate taking precedence perhaps ? What does sysctl -a dev.hwpstate_intel show ?     ---Mike From nobody Mon Mar 13 17:01:54 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Pb2xx5w46z3xxLl for ; Mon, 13 Mar 2023 17:01:57 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pb2xx2J46z4Kn0 for ; Mon, 13 Mar 2023 17:01:57 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b=hsedXSW3; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=N0bLLlYd; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.27 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 8FE325C0159 for ; Mon, 13 Mar 2023 13:01:56 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 13 Mar 2023 13:01:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm2; t=1678726916; x=1678813316; bh=BS IWmHTQh8aT2fdHFUvhfoYyhse7IbnkZ7LrcY9hJe8=; b=hsedXSW3sRF0c4DoWg KsH7Mg3hvWNzk1p3uOMCrFFhwsjriucX7XYACi0JrR7C8+phQ5TVopK4VdDBj0+7 gJREUJ5sL/TWEwcQN7SnshBugb47Y5qFw7gBDfSWMLOvNn0K1vT5ZKqimVluZgRh jc2ouZkU/RqeNWM/HrIb+T3aFihrHmDc4k1KTjhwcjWfeKIdaUFSO3HNuE9Rkcyn TUP7r+y5hnLpUCp1CuYt+I9v392OtimDSl1xswFRraJhMEA85X/BLp/1UKpDeRWR myil7baWCjFIDwoJ7HcevjW3eclxHlrmfe6hnEtpVOHt8sR5Qhp3uM5JW74UXVLo gmzw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; t=1678726916; x=1678813316; bh=BSIWmHTQh8aT2 fdHFUvhfoYyhse7IbnkZ7LrcY9hJe8=; b=N0bLLlYdiEufdtIHl7YcdPlCMC3ln HU9KetDr3dUweEgVqw/yJydvKnMzWOzdeuhuCtsW7MQMTD5DZEyYpMbZXjKhvuSU hbgeb6hnphiURYwZoYpkfjjdlXmRpXj0Efy2IC1fnctZxMY9LMj/PBQKNs32yH4B /yB7bg7YnD75u+I7ETwZl66gg/Mull5r7Ieo1yY20AMmIpEcLRK4KIFnQ4BJHMPS l01K7VtKPGY5ZkkT6rRCMObp/Uzlb1SLn/Wr+MAaK9ruOaP22/6LkcD3C/glwbAS ARtJyZCYFTQLtFBJQ3hCFnWrBGFxJuW+gCBoCgoPMoJFieENYVX+mrHbw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvddvgedgleegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnhepkeeluddvlefhieelfefggffhffektdehleelgfdugfdvgeekjeejuddthe ehgfeunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep vhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Mon, 13 Mar 2023 13:01:56 -0400 (EDT) Date: Mon, 13 Mar 2023 17:01:54 +0000 From: void To: freebsd-hackers@freebsd.org Subject: Re: CPU supports Enhanced Speedstep, but is not recognized. Message-ID: Mail-Followup-To: freebsd-hackers@freebsd.org References: <9df2ec48-aacd-e2c4-04b6-8cba90a237be@sentex.net> List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <9df2ec48-aacd-e2c4-04b6-8cba90a237be@sentex.net> X-Spamd-Result: default: False [-4.56 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.98)[-0.978]; NEURAL_HAM_SHORT(-0.98)[-0.978]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.27:c]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.27:from]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; RCPT_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; FREEMAIL_FROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[66.111.4.27:from]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4Pb2xx2J46z4Kn0 X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N On Mon, Mar 13, 2023 at 12:29:33PM -0400, mike tancsa wrote: >Is the hw pstate taking precedence perhaps ? What does > >sysctl -a dev.hwpstate_intel > >show ? % doas sysctl -a dev.hwpstate_intel sysctl: unknown oid 'dev.hwpstate_intel' -- From nobody Mon Mar 13 17:08:37 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Pb35h38rFz3xxNm for ; Mon, 13 Mar 2023 17:08:40 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pb35g46Jpz4Lvs for ; Mon, 13 Mar 2023 17:08:39 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b=A+Y754IX; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=jYT9q3uI; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.27 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 51D005C0138 for ; Mon, 13 Mar 2023 13:08:39 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 13 Mar 2023 13:08:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm2; t=1678727319; x=1678813719; bh=B2 P44Cjz9zveDV7/emvowYUrDVUxgXh/qTuE0V1ngnI=; b=A+Y754IX/1mLp/qG0l pOIi/A8oI125D35QpUgi5s4GGSiO1dsGTpyJeTzOnhYevOSgFsOXqie/tRTOHwFA wfwV+TrH4mLtmgK7dJjU5uJ2hYaTlyMEYbRJRjKJlwS0i2UmP1IzMs2qAN5qxMyO vi8GZKjBanrngSJ65tcUICYTUW7wL3AtNTSkDLl9xcChrx3oQtoylJeVzaIP+4kz AHyCtf5XDfxeAOaW9WJ3pZHhFBS8EsPq3SIkIT60A8pddBU1C+l0vPEWMfe2z9f6 DYN+khQnYr3Igz/PiFe9FvyWvCkYiurvMTUl4xqPte9xi2yaJznamZxLoewQklqR 0VgA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; t=1678727319; x=1678813719; bh=B2P44Cjz9zveD V7/emvowYUrDVUxgXh/qTuE0V1ngnI=; b=jYT9q3uInI5TacvC8bErcu+abXCIM m7Ryg52vvU4bHaglDv94mq83RiG9Jo1+LyrgJYtwUYCcmBgIFOpg6J3CUAJ0XPoN 7M/ZzyAV23KXe0Iq4AamWJOgoIRtb6cNCy0y8WqwO+RyAuu/QU3EAKwRpE2frZsL LoQsrh3E2zhXepSwOufVKbjwPxysF0qj3nc7RsrFfd3uAjXmv9sGCKdR6s201u66 1tpnBQ/gzPBIBz8n54uhnaMOulh960PrPh6wIGzcohwjyMVWR6I8XMNJ+4nAWEtQ 5cNy1qOLT3R1TZ7wVCqOggBJXlqf0eImx+N6pQbsxpEdwIFawnuhF4FGg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvddvgedgleehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnhepkeeluddvlefhieelfefggffhffektdehleelgfdugfdvgeekjeejuddthe ehgfeunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep vhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Mon, 13 Mar 2023 13:08:38 -0400 (EDT) Date: Mon, 13 Mar 2023 17:08:37 +0000 From: void To: freebsd-hackers@freebsd.org Subject: Re: CPU supports Enhanced Speedstep, but is not recognized. Message-ID: Mail-Followup-To: freebsd-hackers@freebsd.org References: <9df2ec48-aacd-e2c4-04b6-8cba90a237be@sentex.net> List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-4.59 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.99)[-0.989]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.27:c]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.27:from]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; RCPT_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; FREEMAIL_FROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[66.111.4.27:from]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4Pb35g46Jpz4Lvs X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N On Mon, Mar 13, 2023 at 05:01:54PM +0000, void wrote: >% doas sysctl -a dev.hwpstate_intel >sysctl: unknown oid 'dev.hwpstate_intel' % doas sysctl -a | grep hwp interface hwpstate_intel.1 already present in the KLD 'kernel'! kern.hwpmc.softevents: 16 kern.features.hwpmc_hooks: 1 debug.hwpstate_pstate_limit: 0 debug.hwpstate_verify: 0 debug.hwpstate_verbose: 0 machdep.hwpstate_pkg_ctrl: 1 -- From nobody Mon Mar 13 18:10:38 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Pb4TJ5VvJz3y1gk for ; Mon, 13 Mar 2023 18:10:44 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (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 4Pb4TH5hmvz4SYj for ; Mon, 13 Mar 2023 18:10:43 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b=rRHKRZG1; dkim=pass header.d=messagingengine.com header.s=fm2 header.b="q p0YQVl"; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.19 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id B1B2D3200893 for ; Mon, 13 Mar 2023 14:10:41 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 13 Mar 2023 14:10:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1678731041; x=1678817441; bh=Yn7pKf1XX29sHZoHG2Hpgp47aDFS0e+GG5V a7fqemTQ=; b=rRHKRZG1p0hGmD47JJI+kyFlEgOOUp1jqQo+vxvJuAvTAserK5j sp3Br5Eyj9VsDo1Z0jBaganI6l1h4m5nT70Xs0TsQiuUYdfjwyBzHAOpDA/e3/1T rC/BIydiqycXRrlp9X3wMMmVPdmlp6QUOx/SSIKzeJZ4y8AdH5dnpQJyiv/8jjUI Av4Aj0cjXYjYg2xk4lCC8K1CmWLKXXEXI1AbVPx2v0QGouJ0N2hKXe96y67y/cGF VuSKriiAip4N7d06xLXmVreOQeze2Ctv/+cqxHD5rkx61qgVOoD8zm2qssn6ylHp e6UKM3yhAolTZQPOT8Axg6eZBPmLiE6YkBg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1678731041; x= 1678817441; bh=Yn7pKf1XX29sHZoHG2Hpgp47aDFS0e+GG5Va7fqemTQ=; b=q p0YQVlu8hAUA9ViRXWwMUP8rGVFHB5f9sEcSfk7Bd+M51Qi9CI3t1cBaInpVJp4E gP5F2PnDKubLQvbDxD30tfZzlwucAO84rkUwQD/k/BjngHG9Hu9kFEc7yrX+mYI0 PHlvfrS3MFkk/UpSy2V3EuWPjHlINxOIjEFBRHmm0kv39Mh4ptIjkw00WTAG8wGZ nNC/jnCZ7BQH6t3uGpwCFO3D6Hh7FLWUMnig0Nqhb4N3VO8NHwry66e+q/gsKoi+ 6wB2iypdc0P6ZJd8Q+EMPAp4aRVyrorQd1huEWM+IZTUNH1YbrPC/GOOMzWG/Y1o UW/JYu07F88Peq9flfUvg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvddvgedguddtkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtugfgjgesth ekredttddtudenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggft rfgrthhtvghrnhepkedvjeeitdejheekieekkeeiuddtffdvudetheevgeeijeehtdfffe eggeektdefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhho mhepvhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Mon, 13 Mar 2023 14:10:40 -0400 (EDT) Date: Mon, 13 Mar 2023 18:10:38 +0000 From: void To: freebsd-hackers@freebsd.org Subject: Re: CPU supports Enhanced Speedstep, but is not recognized. Message-ID: Mail-Followup-To: freebsd-hackers@freebsd.org References: <9df2ec48-aacd-e2c4-04b6-8cba90a237be@sentex.net> List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9df2ec48-aacd-e2c4-04b6-8cba90a237be@sentex.net> X-Spamd-Result: default: False [-4.59 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.994]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; MID_RHS_NOT_FQDN(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.19]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.19:from]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4Pb4TH5hmvz4SYj X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N On Mon, Mar 13, 2023 at 12:29:33PM -0400, mike tancsa wrote: >On 3/13/2023 12:22 PM, void wrote: >> The system is a HP ProLiant dual Xeon E5-2690 v2, so there are 40 "cpus" >> ie 20 if hyperthreading is turned off, in total. >> >> I was kind of surprised this didn't work out-of-the-box considering >> the age of the cpu, its use-context and how widely it was/is used >> in that context. Clearly I'm doing something wrong or missing something. >> >> Should it work? >> >Is the hw pstate taking precedence perhaps ? What does > >sysctl -a dev.hwpstate_intel > >show ? Think I might have found the answer in est(4): ### est: CPU supports Enhanced Speedstep, but is not recognized.   est: cpu_vendor GenuineIntel, msr 471c471c0600471c   device_attach: est%d attach returned 6   Indicates all attempts to attach to this interface have failed. This usually indicates an improper BIOS setting restricting O/S control of the CPU speeds. Consult your BIOS documentation for more details. ### so the next problem is out-of-band access, so not a freebsd problem. Sorry for the noise. -- From nobody Wed Mar 15 00:00:24 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PbrBK44kFz3xgWH; Wed, 15 Mar 2023 00:00:25 +0000 (UTC) (envelope-from salvadore@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (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 4PbrBK3K2Hz46vb; Wed, 15 Mar 2023 00:00:25 +0000 (UTC) (envelope-from salvadore@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1678838425; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc; bh=RFj1VdEIjRH9Ujoxl7wlSwRzRrt5zBaLRd0ZexNmzH8=; b=Y0993ISzu8bSevPu5B87jO8VxJ9BeQka14BmmphuInzj0MMJpRLml047+IOWyDDRIIdTSx Au754URGKBbLVMOyt3R9XyPK8EVZDcgHDZfAq/Mo54M1HcMzDdFp0I/nE5HQF92cf3UEbP LZ+9mVCYtM0WjImKMKmzD+alFIC3e+DebMNnKFUskv+gwDD/3qunhDCvU+jHZNPTuLhgPL aTKmhkkGX9IH1Ni+eV8u3i0kYaPRooqJoqPJSHxgztg9NnCJLgHAtkMEdsW5lS6XosJ9OK LzeZLZ6GuOx4xmczSQKP3bt0ZAQmBWIG1u0A2llZyYizcJOQgU2/6KB8A/HtvQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1678838425; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc; bh=RFj1VdEIjRH9Ujoxl7wlSwRzRrt5zBaLRd0ZexNmzH8=; b=iqBy7ChwJHwclvepqeeugs3U+wgHGqjvX+Szwz/xBcWhHMQ1VkfNSdylg+ks/8YaBoBCFv N7C5QNHllf+HrWwMFcWZEv8AfuMMfru436+CFbVpQoa8AjRH66CDnheGxyOXYRN10rydVl 72Yr7Yb9G8c37qIfZUhkmdeSkowMmsObetzgrxhYcUnxyETLOxjxva6RtgYHE7Evj5Dv1N ERcuS3+U+7BYn3IVR0wUETlE2SsvUtnNXmVN7TWv7TqXJTJyE2Q/QRKikHRCjfTZeWpxey qO90mBa/rEfBOVVOS17n2ikcm9JFWQrsrYGoPDIa7h7rl+44QZ2F7cZ3m7gcSA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1678838425; a=rsa-sha256; cv=none; b=hxfqW3V7qG4xmydEuejwjfVviGrOUftc+znf76yyOPqU7NuRHnKllM+8YE5gQJN1VOBnw3 MXS/EWZndqb7UyiRq2muqBro2/UeIIXB9e+gk91oYIaYsSyXPj54oLdVFC775pd4VK+vtA dtUX1ZUyWJcGZpzYfWDAIUO2us1t2IbO+WsY4rZr6sKfWX0qB3X2qcqesNFsXhJ22UvACx iAqveSXq3apogM5BDWAGdb3lS05S4Rl3mRl3kOFRR9OKbMltcSGaX96ioHLkzzPNH7wRge /gHluH5E3i3Zc7Xn4dDWGu55nIlElC/HlYfDpJuGaXf4pz3rQNby0m9VzKLeIQ== Received: by freefall.freebsd.org (Postfix, from userid 1472) id 5743010B89; Wed, 15 Mar 2023 00:00:24 +0000 (UTC) To: freebsd-status-calls@FreeBSD.org Subject: [2 WEEKS LEFT REMINDER] Call for 2023Q1 status reports Cc: freebsd-current@FreeBSD.org,freebsd-hackers@FreeBSD.org,devsummit@FreeBSD.org,secretary@asiabsdcon.org Message-Id: <20230315000025.5743010B89@freefall.freebsd.org> Date: Wed, 15 Mar 2023 00:00:24 +0000 (UTC) From: Lorenzo Salvadore X-ThisMailContainsUnwantedMimeParts: N List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is March, 31st 2023 for work done since the last round of quarterly reports: January 2023 - March 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 earliest 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-01-2023-03/ (create it if it is missing); * submit a pull request at https://github.com/freebsd/freebsd-doc . You should put your reports in the directory doc/website/content/en/status/report-2023-01-2023-03/ (create it if it is missing); * send an email to status-submissions@FreeBSD.org including your report. An AsciiDoctor template is available at https://www.FreeBSD.org/status/report-sample.adoc . We look forward to seeing your 2023Q1 reports! Thanks, Lorenzo Salvadore (on behalf of status@) From nobody Wed Mar 15 16:58:59 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PcGp82YSRz3ykkm for ; Wed, 15 Mar 2023 16:59:28 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: from mail-vs1-f43.google.com (mail-vs1-f43.google.com [209.85.217.43]) (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 4PcGp72gLSz3Dpb for ; Wed, 15 Mar 2023 16:59:27 +0000 (UTC) (envelope-from 6yearold@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of 6yearold@gmail.com designates 209.85.217.43 as permitted sender) smtp.mailfrom=6yearold@gmail.com; dmarc=none Received: by mail-vs1-f43.google.com with SMTP id by13so17544652vsb.3 for ; Wed, 15 Mar 2023 09:59:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678899566; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=P0E34ninwxidTile7eIhPTchSQGsm8AeRw5NwVKVs1k=; b=n6zSeVaqPT2tDd0g9PFrEn11bj0/bX2f5xuZ3FPFgGa3Hvnj4bfwQytSf5gPXykSB2 YgR6L6VpPoSqp6jBkgoJByZ6V1UHf9peL/fmj6vmO2pnKTS6XcP26gNaE+alB1ord9nS jLPIjhA+Zi6PQzaoJ3ev3H19GZWboG0pW4tnYLQrclT6rxnCmhdDQjY3Yp0yo1WeKdL0 TJ46nJYwBuSFNk5rv5SFr2mksOymSLYiSFypcjJ6ifOeypNqzR9S1YoE57u/yf7LhMNs F3jnwjfrZaHKp+vMWnmLikF5LVcoQxrrxlZEUSCE0InZ7plDo7fC5qAslXvCmPSNtWcX y5Iw== X-Gm-Message-State: AO0yUKXEWLMkyEirp/eiB7bzDObmndqlMnckdODdSAJiEBqbCw347zOy KpWJGBOjUh9CQz+PCeRdK9qX8jJIJTexSA== X-Google-Smtp-Source: AK7set+2oib1VzIKR5oP6zf189H18/k7aWb+MN+pSqOSppzZ6mGsfoJ9qF3WxwHSrcbDtJeCCsnX9Q== X-Received: by 2002:a05:6102:338a:b0:3eb:39d5:68c2 with SMTP id i10-20020a056102338a00b003eb39d568c2mr22108294vsh.10.1678899566414; Wed, 15 Mar 2023 09:59:26 -0700 (PDT) Received: from mail-ua1-f44.google.com (mail-ua1-f44.google.com. [209.85.222.44]) by smtp.gmail.com with ESMTPSA id l22-20020a67fdd6000000b003fb4ef8f686sm522219vsq.13.2023.03.15.09.59.25 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 15 Mar 2023 09:59:26 -0700 (PDT) Received: by mail-ua1-f44.google.com with SMTP id ay14so6659899uab.13 for ; Wed, 15 Mar 2023 09:59:25 -0700 (PDT) X-Received: by 2002:a1f:a9c7:0:b0:401:73f4:dfe with SMTP id s190-20020a1fa9c7000000b0040173f40dfemr26249047vke.3.1678899565807; Wed, 15 Mar 2023 09:59:25 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 From: Gleb Popov Date: Wed, 15 Mar 2023 19:58:59 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: splash(4) support in vt To: freebsd-hackers Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-2.97 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.971]; FORGED_SENDER(0.30)[arrowd@freebsd.org,6yearold@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[text/plain]; R_DKIM_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[arrowd@freebsd.org,6yearold@gmail.com]; RCVD_IN_DNSWL_NONE(0.00)[209.85.217.43:from,209.85.222.44:received]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.217.43:from]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; TO_DN_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; TO_DOM_EQ_FROM_DOM(0.00)[] X-Rspamd-Queue-Id: 4PcGp72gLSz3Dpb X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N Hello hackers! I found an old post [1] regarding splash(4) support for vt. The company I'm working for wants to invest some time into making the FreeBSD boot process as shiny as possible. Can someone knowledgeable on the topic give us some insight on where to start? Our ultimate task is being able to render a GIF logo right from the boot splash screen and until X session kicks in. Thanks in advance! [1] https://lists.freebsd.org/pipermail/freebsd-hackers/2018-September/053331.html From nobody Wed Mar 15 19:56:44 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PcLl11BXSz3xjYK for ; Wed, 15 Mar 2023 19:57:01 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-lf1-f51.google.com (mail-lf1-f51.google.com [209.85.167.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 4PcLl06Kczz3pM1; Wed, 15 Mar 2023 19:57:00 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lf1-f51.google.com with SMTP id d36so25714395lfv.8; Wed, 15 Mar 2023 12:57:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678910218; 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=rPqP2k3Z6g3y41xxUGDcUU/JfCsIuWXsPLmX1z6LYAU=; b=cCJ36AydJdrrd7rU/F466vBzYEF9d69kA4ZmTLjHPNon8X4eKU+Di8QYxqYhsFW97N K+Bz7Q+onJxbcJCEZEEqe94F04z+NXivSGdXlCPyAa71pnTK7KZ3LisrDtus0JPshdiT H3awx1j4lttYRMIQfs9p2IFP70/z67qBFeljBetcoFpnNygs0f7EIW8ZG3kqq1gVfdHy Qe7b9OuboRB5I8y8fnfdjWbeGF8May5vedr1PvWw/UuwBrkg55Ar61PF3AduAvv8/TWg nG5MpPTkRJe9QmKoPZTumvgUqkWlKludCzIdnu2zpVWGQrmayLxm0M5Xh0suhJxgz6zf wTvg== X-Gm-Message-State: AO0yUKV6UGdLUZ/9I2+sQv6ZcGqv06SHGgzgH0nd6zm2wVcR9QuiGxK5 tkTXPxx2a+DCjUKb6Tz5lGDJCpVn1PkayWQQNiKj/Xj+Sl0= X-Google-Smtp-Source: AK7set8elxEwGS14HS2iEQn/piCZqrt5aX63rgaPWrqaovkYk8wHRwY1B5guHYqb63omFQREP8kt8tfZwiK5MqBoNio= X-Received: by 2002:a05:6512:10d1:b0:4e8:6261:7dd0 with SMTP id k17-20020a05651210d100b004e862617dd0mr722214lfg.4.1678910217797; Wed, 15 Mar 2023 12:56:57 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Ed Maste Date: Wed, 15 Mar 2023 15:56:44 -0400 Message-ID: Subject: Re: splash(4) support in vt To: Gleb Popov Cc: freebsd-hackers Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4PcLl06Kczz3pM1 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 Wed, 15 Mar 2023 at 12:59, Gleb Popov wrote: > > Hello hackers! > > I found an old post [1] regarding splash(4) support for vt. The > company I'm working for wants to invest some time into making the > FreeBSD boot process as shiny as possible. Can someone knowledgeable > on the topic give us some insight on where to start? > > Our ultimate task is being able to render a GIF logo right from the > boot splash screen and until X session kicks in. That's great, I'd very much like to see this supported. HelloSystem has the same desire, you can see the issue at https://github.com/helloSystem/ISO/issues/226. There are many individual tasks to be taken on; we need at least to get the image displayed earlier in the boot process, support more than just a 2-colour image, and support a user-provided (rather than compiled-in) image. We probably also need some animation support (e.g. a spinner). These tasks are all related but are mostly independent, so could be taken on in any order. What is your priority on these? The Wiki page linked from the mailing list posting is https://wiki.freebsd.org/MateuszPiotrowski/ImproveVtSplashScreenSupport, and it has a basic introduction. Looking at the source, the current logo is stored in sys/dev/vt/logo/logo_freebsd.c as a C array holding a 257x219 bitmap. If you look at vt_fb_bitblt_bitmap (and similar functions in other drivers) you can see that it loops over each pixel where the image will be drawn, and sets it to either the foreground or background color. The compiled in logo is passed to the specific driver's vd_bitblt_bmp function in vtterm_splash(). From nobody Thu Mar 16 06:26:30 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Pccjx5KyXz3yQqt for ; Thu, 16 Mar 2023 06:27:01 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: from mail-ua1-f41.google.com (mail-ua1-f41.google.com [209.85.222.41]) (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 4Pccjx3bj2z3mld; Thu, 16 Mar 2023 06:27:01 +0000 (UTC) (envelope-from 6yearold@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ua1-f41.google.com with SMTP id s23so495593uae.5; Wed, 15 Mar 2023 23:27:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678948018; 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=p9jFR9/G/QBWt3llUPDH+5h8LAyXMwje+H9nmOeKUug=; b=XvoLZXFcUo4xtO+jM3QuSCW1l1f4S973L061HP3NKjAc5qycGShmCoYHdqPlBP8HS7 cwIxq++EcSNO4Pmd7jpYYJQY7QKLPon/38jkHd1exn11i1bC6Z9PF3CclKLhuebzcyCk 8OZpU4c3fDssdugpdlJ3a0COwVfyVnjhAWe7kJy1MRg3xCqGej7144qVmJ/ZzBZA7IJJ WrpiDLrcNqEMBk95tnt4E7S8+79vLEwq1asF3OtwPB0eLETQekm6CyxvanM3RrKeN2PS z6hkKgXAFuQpJGhl854uG/suVzTN69wSBzLGxQoBPLMXLQZ2QKWb5mrmgcfy6amFx9wH ytXg== X-Gm-Message-State: AO0yUKXBxgYWe0eDGRdGUTZRadiKAlb83i7cauxCucV5EASkkb7YzYwD zUavg+CI6jog35SYD8HgHLKVNkmx6DbskB9s X-Google-Smtp-Source: AK7set9MI+xzoi3VUP99+JW5Dl6ZZj9o3ahFbZ8EgV8bRq42AAuA2ZS0bLKBUZCEZRPyj/RmyV7QUw== X-Received: by 2002:a1f:9b87:0:b0:401:32f5:a867 with SMTP id d129-20020a1f9b87000000b0040132f5a867mr13807090vke.2.1678948017123; Wed, 15 Mar 2023 23:26:57 -0700 (PDT) Received: from mail-ua1-f43.google.com (mail-ua1-f43.google.com. [209.85.222.43]) by smtp.gmail.com with ESMTPSA id 19-20020a1f1613000000b0043290c8d6d3sm141582vkw.40.2023.03.15.23.26.56 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 15 Mar 2023 23:26:56 -0700 (PDT) Received: by mail-ua1-f43.google.com with SMTP id 89so522850uao.0; Wed, 15 Mar 2023 23:26:56 -0700 (PDT) X-Received: by 2002:a9f:311a:0:b0:73f:f15b:d9e3 with SMTP id m26-20020a9f311a000000b0073ff15bd9e3mr11716643uab.0.1678948016644; Wed, 15 Mar 2023 23:26:56 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Gleb Popov Date: Thu, 16 Mar 2023 09:26:30 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: splash(4) support in vt To: Ed Maste Cc: freebsd-hackers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Pccjx3bj2z3mld 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 Wed, Mar 15, 2023 at 10:57=E2=80=AFPM Ed Maste wrot= e: > > > There are many individual tasks to be taken on; we need at least to > get the image displayed earlier in the boot process, support more than > just a 2-colour image, and support a user-provided (rather than > compiled-in) image. We probably also need some animation support (e.g. > a spinner). These tasks are all related but are mostly independent, so > could be taken on in any order. What is your priority on these? I think we'd need to start from getting more colors work. Our final goal is a GIF-animated splash. > > The Wiki page linked from the mailing list posting is > https://wiki.freebsd.org/MateuszPiotrowski/ImproveVtSplashScreenSupport, > and it has a basic introduction. Looking at the source, the current > logo is stored in sys/dev/vt/logo/logo_freebsd.c as a C array holding > a 257x219 bitmap. If you look at vt_fb_bitblt_bitmap (and similar > functions in other drivers) you can see that it loops over each pixel > where the image will be drawn, and sets it to either the foreground or > background color. Which is the reason it only supports 2-color images, I presume? Thanks for the links, I'll take a look! From nobody Thu Mar 16 08:20:07 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PcgDg6bj1z3yY46 for ; Thu, 16 Mar 2023 08:20:19 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (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 "mx.blih.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PcgDg061dz3wqj; Thu, 16 Mar 2023 08:20:18 +0000 (UTC) (envelope-from manu@bidouilliste.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1678954810; 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=J9pWK5IQyNFNShE81Gq4ebBLEJ1rMb3lIFNrfDlDAlU=; b=qyZkF4xV0jLJbwdCyXdhB5V9MuWEeG47m/6n6+qqo6gTDVUzTa+LzUhSuWLRfDNtLrW0uH wpi+g9lQIeAStA8DhSbSYeDQntrDiQS4KJ+KA3GjEXhO5BOQJ9KhlQCrUsnqw0TDpIhNOp g5o65XCNubejyLHWo7KmKYIfxiY/zgk= Received: from skull.home.blih.net (lfbn-lyo-1-2174-135.w90-66.abo.wanadoo.fr [90.66.97.135]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 7c9ce258 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Thu, 16 Mar 2023 08:20:10 +0000 (UTC) Date: Thu, 16 Mar 2023 09:20:07 +0100 From: Emmanuel Vadot To: Gleb Popov Cc: Ed Maste , freebsd-hackers Subject: Re: splash(4) support in vt Message-Id: <20230316092007.6a2695e995f5e4c589140886@bidouilliste.com> In-Reply-To: References: X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4PcgDg061dz3wqj X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Thu, 16 Mar 2023 09:26:30 +0300 Gleb Popov wrote: > On Wed, Mar 15, 2023 at 10:57?PM Ed Maste wrote: > > > > > > There are many individual tasks to be taken on; we need at least to > > get the image displayed earlier in the boot process, support more than > > just a 2-colour image, and support a user-provided (rather than > > compiled-in) image. We probably also need some animation support (e.g. > > a spinner). These tasks are all related but are mostly independent, so > > could be taken on in any order. What is your priority on these? >=20 > I think we'd need to start from getting more colors work. Our final > goal is a GIF-animated splash. >=20 > > > > The Wiki page linked from the mailing list posting is > > https://wiki.freebsd.org/MateuszPiotrowski/ImproveVtSplashScreenSupport, > > and it has a basic introduction. Looking at the source, the current > > logo is stored in sys/dev/vt/logo/logo_freebsd.c as a C array holding > > a 257x219 bitmap. If you look at vt_fb_bitblt_bitmap (and similar > > functions in other drivers) you can see that it loops over each pixel > > where the image will be drawn, and sets it to either the foreground or > > background color. >=20 > Which is the reason it only supports 2-color images, I presume? >=20 > Thanks for the links, I'll take a look! >=20 Hi Gleb, Thanks for being interested in this, a few notes on how I think it should be done below. First step is to handle more colors for the embeded logo, we only support a depth of 1 currently, see https://cgit.freebsd.org/src/tree/sys/dev/vt/vt_core.c#n1483 Second step should be to switch from a compiled-in logo to a file loaded from loader. The old sc(4) console support this (see splash_bmp_load/splash_pcx_load in loader.conf(5)). I don't think that the kernel should be aware of image format, instead loader(8) should be able to load an image and convert in to a blob of pixel to draw based on the framebuffer information (with EFI it's simple to know this). So I suggest adding a new type of module named 'splash_logo' of something like that that will hold the data, size and depth of the image. You can have a look at how this worked with sc(4) here : https://cgit.freebsd.org/src/tree/sys/dev/fb/splashreg.h Maybe this should also hold a screen position (probably in percentage). For animated logo adding a splash_spinner type is probably the best way. The problem will be to animate this, not sure that handling this in the kernel is the best way. I think that in Linux it's handled by plymouth and since it's start early in initrd it's easier for them to do it that way. But I think that you have enough work for now :) Cheers, --=20 Emmanuel Vadot From nobody Sat Mar 18 19:56:09 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PfBbB5yqWz3yxkH for ; Sat, 18 Mar 2023 19:56:38 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: from mail-vs1-f41.google.com (mail-vs1-f41.google.com [209.85.217.41]) (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 4PfBb96lJlz3mYF; Sat, 18 Mar 2023 19:56:37 +0000 (UTC) (envelope-from 6yearold@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of 6yearold@gmail.com designates 209.85.217.41 as permitted sender) smtp.mailfrom=6yearold@gmail.com; dmarc=none Received: by mail-vs1-f41.google.com with SMTP id c10so198602vsh.12; Sat, 18 Mar 2023 12:56:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679169396; 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=re3vit38YiiAuoPLqE1QHzSvNwvGdF/RWFVn/P4YY/k=; b=sU+ELBzXz+CUqVGjtN/XGn69oG0azXRFNAoLzZny+uNViliay78nNn4n7lStWQhj9c qT1b571PvY+i1dlzAm0I8ZzC565mW5u2NQWStYfSLVj6cQU4MB65yS2Qzrm2XfR1TiEu 8a6wysBQ5RpVmUnlfc8RCy5i0awcakSeqyLS+x71vCb232nKrslzSCc8rdfpDnk+baid sTb/KO+DDCzmoKYbfJ4547N47AKwUIYuRkS9uad18MVs8OyipQ28MEr5Zl3OPB3RjIGJ nW5jGdrD1SaQcPMuhemcvMXatyOIPrNH2dBXyL0+p1pAItG5vG281Jx5YN/1DGBR+hC8 Yvwg== X-Gm-Message-State: AO0yUKWCjOwV4St3MGy3bRONDMXP11TTOVsmGv94ZDcaDmb+9Ika9t03 MSAG5Fv52gpkW8q5v3kKPUM47hkPMck= X-Google-Smtp-Source: AK7set8lx/wP8G2w6fZs5lzRGCsR7vbZiIDNEmXMJZjOH/EchFI1mbsGLUloZ3bgN2Px2ISfcK2qPQ== X-Received: by 2002:a67:fdd5:0:b0:422:25e4:d77c with SMTP id l21-20020a67fdd5000000b0042225e4d77cmr966102vsq.10.1679169396443; Sat, 18 Mar 2023 12:56:36 -0700 (PDT) Received: from mail-ua1-f53.google.com (mail-ua1-f53.google.com. [209.85.222.53]) by smtp.gmail.com with ESMTPSA id k1-20020a056102004100b0041ec99a5913sm625088vsp.29.2023.03.18.12.56.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 18 Mar 2023 12:56:36 -0700 (PDT) Received: by mail-ua1-f53.google.com with SMTP id x33so5469872uaf.12; Sat, 18 Mar 2023 12:56:36 -0700 (PDT) X-Received: by 2002:a05:6130:c0f:b0:68b:817b:eec8 with SMTP id cg15-20020a0561300c0f00b0068b817beec8mr1304407uab.0.1679169395884; Sat, 18 Mar 2023 12:56:35 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: <20230316092007.6a2695e995f5e4c589140886@bidouilliste.com> In-Reply-To: <20230316092007.6a2695e995f5e4c589140886@bidouilliste.com> From: Gleb Popov Date: Sat, 18 Mar 2023 22:56:09 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: splash(4) support in vt To: freebsd-hackers Cc: Ed Maste , Emmanuel Vadot Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-2.92 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.92)[-0.924]; FORGED_SENDER(0.30)[arrowd@freebsd.org,6yearold@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_NONE(0.00)[209.85.217.41:from,209.85.222.53:received]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.217.41:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_HAS_DN(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[freebsd.org]; FROM_NEQ_ENVFROM(0.00)[arrowd@freebsd.org,6yearold@gmail.com] X-Rspamd-Queue-Id: 4PfBb96lJlz3mYF X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N Thanks for the pointers! It just occurred to me that splash only hides kernel messages, but after init(8) starts the image disappears and the textual boot sequence is resumed. What are the approaches to solve this? Should we handoff rendering to some usermode program? Would that be seamless?