#48314 [PATCH] Install guix system on Raspberry Pi

Message #158 received at 48314@debbugs.gnu.org (full text, mbox, reply):

Received: (at 48314) by debbugs.gnu.org; 20 Jul 2022 07:16:53 +0000
From debbugs-submit-bounces@debbugs.gnu.org Wed Jul 20 03:16:53 2022
Received: from localhost ([127.0.0.1]:55711 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces@debbugs.gnu.org>)
	id 1oE3wz-00039X-0y
	for submit@debbugs.gnu.org; Wed, 20 Jul 2022 03:16:53 -0400
Received: from mail-4322.protonmail.ch ([185.70.43.22]:55775)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <phodina@protonmail.com>) id 1oE3wu-00039H-4M
 for 48314@debbugs.gnu.org; Wed, 20 Jul 2022 03:16:51 -0400
Date: Wed, 20 Jul 2022 07:16:34 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
 s=protonmail3; t=1658301401; x=1658560601;
 bh=u4gbV7LEyga3zXt30KqOPqCPhB874j5pxYwvlqLu4Fg=;
 h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To:
 References:Feedback-ID:From:To:Cc:Date:Subject:Reply-To:
 Feedback-ID:Message-ID;
 b=KRDRrswa5ip98mL/0+rufBWdWiZdu19I1ShAQUE5G+rBml6m+NQhUwNPLICBr8Yq8
 M/ZrUh1bdBjrZj7cnvmQD9P2iwDc1bv/hqe86PQZRSNFyAhrrAnzw+0X0PPSpfOcM2
 CXdR5DfRKD8yFKFAsRHcIAvNy31OLBzoCMlg7j4XvlBgT/G+4+z7Ycbz3OyWiCf2bT
 vF9zfO+U9wkTF1sn6DLY0S2bq96PmSJGP/ZQJcXE6HQJ8KintFeBF22wCwczIotnIh
 TH3ZY4eDdAjsH816w0nzdWVaaVPxHMqCF/0hemgYBKH12L69FPSkEgQPAOcGZ7/ZJ2
 KKgUDtm/WU3/w==
To: Stefan <stefan-guix@vodafonemail.de>
From: phodina <phodina@protonmail.com>
Subject: Re: [PATCH v3] Install guix system on Raspberry Pi
Message-ID: <t2GTPoH03C4JrkGm9sXt_K8RQtTPqvNzKN7L8a7ws6oklFIlhvY3n2vH4EQ_ohOldf6Nqz21gzmv9IfEoyV28_inllHOOVbEF1iP7yLyepU=@protonmail.com>
In-Reply-To: <9A647306-1C70-4A55-B6AB-35A414E6E633@vodafonemail.de>
References: <gSGTYbtO2aatMamvptaZ2ENBQ9AjVkovjsV1SOD9u1oa0lpJoX9oiq5MNllaAQmvbYOO941T58pfy_L3bi_Dhd9oawdiSBrv1BFSg4JMG-A=@protonmail.com>
 <9A647306-1C70-4A55-B6AB-35A414E6E633@vodafonemail.de>
Feedback-ID: 14143818:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.0 (/)
X-Debbugs-Envelope-To: 48314
Cc: Vagrant Cascadian <vagrant@debian.org>, dannym@scratchpost.org,
 Ludovic Courtès <ludo@gnu.org>, 48314@debbugs.gnu.org
X-BeenThere: debbugs-submit@debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request@debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit@debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request@debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request@debbugs.gnu.org?subject=subscribe>
Reply-To: phodina <phodina@protonmail.com>
Errors-To: debbugs-submit-bounces@debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

Hi Stefan,

> > So now I get some weird guix error during copying files:
>
> > initializing operating system under '/mnt'...
> > copying to '/mnt'... [#################### ]guix system: error: readdir: Bad message
> > copying to '/mnt'...
>
>
> The function make-grub-efi-netboot-installer in gnu/bootloader/grub.scm first uses copy-recursively to copy the collection of bootloader files to /mnt/boot/efi and creates afterwards the symlinks to /gnu/store and /boot/grub/grub.cfg or – as in your case – creates a /mnt/boot/efi/efi/boot/grub.cfg to point GRUB to the root partition to access /boot/grub/grub.cfg and /gnu/store.
>
> Yesterday your guix system init struggled to create these symlinks. That means it was already done with the copy-recursively call.
>
> I’m pretty sure that this copy-recursively is using readdir internally. The functionallity afterwards is surely not.
>
> Yesterday you also got the message ‘populating '/mnt'…’ before the symlink struggle. Therefore I assume that your current error has nothing to do with the bootloader installation.
>
> Maybe there are leftovers from yesterday in /mnt, which prevent guix to copy files sucessfully onto /dev/mmcblk0p2?
>
> Reformatting the ext4 filesystem might help.


the issue seems to be connected to my guix instance on the host. I got another weird messages and what finally help was to clean the profile cache in my home dir.

I then reformatted the SD card just to be sure.

# parted /dev/mmcblk0
GNU Parted 3.5
Using /dev/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Model: NORELSYS 1081CS0 (scsi)
Disk /dev/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  269MB   268MB   primary  fat32        lba
 2      269MB   31.3GB  31.0GB  primary  ext4

And then I also copied the firmware files [1] neccessary to boot:
$ ls /mnt/boot/efi
bcm2708-rpi-b.dtb       bcm2710-rpi-2-b.dtb       bcm2711-rpi-4-b.dtb   efi/          fixup_db.dat      start4.elf
bcm2708-rpi-b-plus.dtb  bcm2710-rpi-3-b.dtb       bcm2711-rpi-cm4.dtb   fixup4cd.dat  fixup_x.dat       start4x.elf
bcm2708-rpi-b-rev1.dtb  bcm2710-rpi-3-b-plus.dtb  bcm2711-rpi-cm4s.dtb  fixup4.dat    LICENCE.broadcom  start_cd.elf
bcm2708-rpi-cm.dtb      bcm2710-rpi-cm3.dtb       bootcode.bin          fixup4db.dat  manifest          start_db.elf
bcm2708-rpi-zero.dtb    bcm2710-rpi-zero-2.dtb    bootloader.txt        fixup4x.dat   overlays/         start.elf
bcm2708-rpi-zero-w.dtb  bcm2710-rpi-zero-2-w.dtb  config.txt            fixup_cd.dat  start4cd.elf      start_x.elf
bcm2709-rpi-2-b.dtb     bcm2711-rpi-400.dtb       dtb.txt               fixup.dat     start4db.elf      u-boot.bin

The board powers up and I see the RGB screen when the raspberrypi boots. Then it switches to black screen and I don't see any output on the HDMI. Also there is no IP address assigned on the Ethernet even though the port itself is active.

I haven't run tcpdump or attached serial adapter yet so I don't know what's wrong and where the system hangs.

I'm testing this on Raspberry Pi 4.

[1] https://github.com/raspberrypi/firmware


----
Petr

Send a report that this bug log contains spam.