From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: wip blog post: running Guix System on ARM Date: Thu, 14 Nov 2019 10:29:22 +0100 Message-ID: <87k182g619.fsf@ambrevar.xyz> References: <20191113222154.6eb6a78c@sybil.lepiller.eu> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:33574) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iVBRS-0000an-9n for guix-devel@gnu.org; Thu, 14 Nov 2019 04:29:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iVBRQ-0004El-Jy for guix-devel@gnu.org; Thu, 14 Nov 2019 04:29:29 -0500 Received: from relay3-d.mail.gandi.net ([217.70.183.195]:49595) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iVBRQ-0004CT-3l for guix-devel@gnu.org; Thu, 14 Nov 2019 04:29:28 -0500 In-Reply-To: <20191113222154.6eb6a78c@sybil.lepiller.eu> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Julien Lepiller , guix-devel@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Neat, thanks for this article! Question: how do you intend to convert the markdown to Texinfo? Some typos / nits below: > ### The kernel modules > > In order for Guix to be able to load the system from the initramfs, it wi= ll probably need Maybe define initramfs? Or just link to https://en.wikipedia.org/wiki/Init= ramfs. > to load some modules, especially to access the root file system. In my c= ase, the SSD is > on an ahci device, so I need a driver for it. The kernel defines `ahci_s= unxi` for that AHCI > Your own board may need other kernel modules to boot properly, however it= is hard to discover > them. Guix can tell you when a module is missing in your configuration f= ile if it is loaded > as a module. Most distros however build these modules in the kernel dire= ctly, so Guix cannot Maybe "distributions" unabridged? > Also note that module names are not consistent between what Guix expects = and what is printed by > dmesg, especially when the contain a "-" or a "_". You will find the cor= rect file name by building Word missing here: "when the contain". > Here, I could find a file named "kernel/drivers/mmc/host/sunxi-mmc.ko", h= ence the module > name `sunxi-mmc`. For the other driver, I found a "kernel/drivers/ata/ah= ci_sunxi.ko", > hence the name `ahci_sunxi`, even if dmesg suggested `ahci-sunxi`. Maybe add "(notice the '_' and the '-' difference)." > In my case, I wanted to install the system on an external SSD, while the = currently running > foreign distribution was running from the SD card. What is nice with thi= s setup is that, > in case of real trouble (you SSD caught fire or broke), you can still boo= t from the old "your SSD" > foreign system with an installed Guix and all your tools by re-flashing o= nly the bootloader. > > In this scenario, we use the foreign system as we would the installer iso= , using the manual Word missing: "we would the installer iso". Also: iso -> ISO. > Make sure there is an empty /etc, or the new system won't boot > properly. Isn't this a bug in Guix? Cheers! =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAl3NHnIACgkQm9z0l6S7 zH+x6QgApVuvyGBZ+iS7y+9vr4P/vTkC9YBmfZiN0GuGUmtoaHACNlhQdW+KTbS6 LwL+lZ5NdJfFdPgmkd2ZxZaY9qKq/joDgrigvpAi2VOb/wiW1xNDEJzPFbd2a8Ry Z7GW/moSsMjkXVO1002Lr2jPJZqabxtUUYADavJs5uSg74cG10f9jv66md2LhbXD OZS63lZenwiglLukP4ZnvpVV+IbH7LdRNOEAQkbEwdakDBkxfjQ+rVGjX/GT6fD9 /VSTMtDC5BarOeKt6f2iQXpMYjdFSJva0LaeohsFyu1ykzN9lU4TVlLSc50BxCbu 808aHLU1TiRyud0Zv797N4uN3FXf8g== =3lRk -----END PGP SIGNATURE----- --=-=-=--