On 2026-09-08, mail--- via wrote: > I have a Pine64 RockPro64 single-board ARM computer. I am trying to > get Guix running on it, and running into an odd issue. The folks in > the IRC chat suggested I reach out to the mailing list for help.
> I am able to run Debian on an SD card and install Guix there. I have > an EMMC module (linked below) that I can attach to the board while > Debian is running. > > https://pine64.com/product/128gb-emmc-module/ > > I am able to successfully partition the module, mount the ext4 > partition and run 'guix system init' to install. > > Starting the board with only the EMMC module attached, the bootloader > starts successfully, but fails to find the installation > partition. Running 'ls /dev' in the bourneish shell doesn't show any > mmc devices. > > I tried looking through dmesg in Debian and adding any kernel modules > that seemed relevant to initrd-modules, but got the same result. Probably just did not add enough modules ... there are some obscure ones such as clocks and regulators that are indirect dependencies to get the hardware fully functional... Here are the ones I use, which might be more than you need and although I am booting from SCSI... pretty sure I have all the modules that used to successfully work on microSD, which should be almost the same as eMMC... so many tricky combinations! (initrd-modules (append (list ;; scsi modules "ahci" "libata" "sd_mod" "scsi_common" ;; "t10_pi" ; not present in 6.13.x? ;; regulators and clocks "rk808-regulator" "clk-rk808" "fixed" "fan53555" ;; "rk808" ; not present in 6.13.x? replaced by MFD_RK8XX_I2C a.k.a. rk8xx-i2c "rk8xx-i2c" ; replaces rk808 "i2c-rk3x" "pl330" "dwc3" "rtc-rk808" "sdhci" "sdhci-pltfm" "dw_mmc" "dw_mmc-pltfm" ;; "dw_mmc-rockchip" "phy_rockchip_pcie" "pcie_rockchip_host" "nvme"))) > I've also tried to modify the SCM to look for the partition by UUID instead > of path, with no success. > I'm attaching my config.scm and the log from u-boot. > Any help would be appreciated! Yeah, you definitely want to use some sort of unique identifier for the device, e.g. uuid or partition label... Good luck! > Starting kernel ... > > GC Warning: pthread_getattr_np or pthread_attr_getstack failed for main thread > GC Warning: Could not open /proc/stat > Welcome, this is GNU's early boot Guile. > Use 'gnu.repl' for an initrd REPL. > > loading kernel modules... > e2fsck: No such file or directory while trying to open /dev/mmcblk1p1 > Possibly non-existent device? > File system check on /dev/mmcblk1p1 failed Curiously, /dev/mmcblk1 is microSD on mine ... do you have a /dev/mmcblk0 ? Though as you can probably guess, these do swap around from time to time on kernel upgrades, so way better to use uuid or partition labels... live well, vagrant
signature.asc
Description: PGP signature
