From nobody Tue Nov 21 20:54:33 2023 X-Original-To: questions@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 4SZc7n4RrJz52HFf for ; Tue, 21 Nov 2023 20:54:45 +0000 (UTC) (envelope-from ralf-mardorf@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 4SZc7m6NmKz3Spg for ; Tue, 21 Nov 2023 20:54:44 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=qwyfvUZm; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.6 as permitted sender) smtp.mailfrom=ralf-mardorf@riseup.net; dmarc=pass (policy=none) header.from=riseup.net 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) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4SZc7f2WfZz9wMF for ; Tue, 21 Nov 2023 20:54:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1700600082; bh=B5tsAxnRTlEY3w25bSYWzhsNJMTYHgTWPDIc/pl+2dk=; h=Subject:From:To:Date:In-Reply-To:References:From; b=qwyfvUZm340r62CdXzaUttvvuOdBw27SLQ1SWF9ehz5naU5bQ/k7ic62JC+l9V0cE 35a4oUUFybKAgfA0n7C1XoirlJ1G/RXmuMCv2zJ2+cjWagPVJgSpAFBNae9b2j394O H99ZbngFYA7WhZbRdK0J0miFpgNX6Sf4xHhEoZLw= X-Riseup-User-ID: 6D738472F57CD3D5D505410CC0D3978EB62AE76F5AD000080A52759120B1FF40 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews02-sea.riseup.net (Postfix) with ESMTPSA id 4SZc7d5BbxzFvhR for ; Tue, 21 Nov 2023 20:54:37 +0000 (UTC) Message-ID: <7f5b40d9837ee59d919ae8c08c4084d57c9e5725.camel@riseup.net> Subject: Re: I am sick and tired of the poor quality of documentation on FreeBSD From: Ralf Mardorf To: questions@freebsd.org Date: Tue, 21 Nov 2023 21:54:33 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 X-Spamd-Result: default: False [-5.50 / 15.00]; DWL_DNSWL_LOW(-1.00)[riseup.net:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; RWL_MAILSPIKE_EXCELLENT(-0.40)[198.252.153.6:from]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; R_SPF_ALLOW(-0.20)[+a:mx0.riseup.net]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.6:from]; MIME_GOOD(-0.10)[text/plain]; FROM_EQ_ENVFROM(0.00)[]; TO_DN_NONE(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; RCVD_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[questions@freebsd.org]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[riseup.net:+]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4SZc7m6NmKz3Spg X-Spamd-Bar: ----- On Tue, 2023-11-21 at 20:51 +0100, iio7@tutanota.com wrote: > Take a look at have it's done on Arch Linux! Hi, Arch Linux and iPadOS are my everyday operating systems. The bootloader documentation is not as clear-cut as you think, even under Arch Linux. Before I bought a new mobo, I ensured that it provides legacy boot. I migrated from an old Intel processor with integrated GPU to a new mobo with a new Intel processor with an integrated GPU. Each time I chose legacy boot it was ignored. The reason for this is, that the integrated GPU does enforce efi boot. When the Intel processor was new, it was documented exactly somewhere hidden in nowhere. The enforced migration from legacy boot to efi boot has resulted in a whole chain of incompatibilities, so I decided to migrate from syslinux to grub 2 and after that I still needed to use kernel parameters, for Arch Linux e.g. ibt=3Doff, for Alpine Linux e.g. modules=3Dext4 ... the freakish kernel parameters where found with some help from the communities. IMO "you might need to update the boot code" is quite straight forward. You need to rewrite the bootloader, how depends on the used bootloader, legacy vs efi boot and probably a few other pitfalls. Boot processes are a can of worms! When I set up a Windows 11 VM I needed to BypassTPMCheck, BypassSecureBootCheck and I don't remember what else, by hidden Microsoft Windows 11 registry features. Keep in mind that almost all hardware is not aimed for BSD or Linux. I didn't run into a bootloader issue when migrating from one iPad to another iPad ;). A bootloader documentation covering all corner cases is hard to archive, if nor impossible at all. If I where you, I would take a look at "gptzfsboot(8) and loader.efi(8) for details" and if needed ask for help. Regards, Ralf