nixos-hardware
nixos-hardware copied to clipboard
Published
20 hours ago •
NixOS
NixOS
VisionFive 2 NVME boot
Saw that in #964, NVME boot is possible. Trying it and it's not working:
<<< NixOS Stage 1 >>>
loading module clk-starfive-jh7110-aon...
[ 3.243664] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation.
[ 3.247057] mmc_host mmc1: Bus speed (slot 0) = 204799999Hz (slot req 300000Hz, actual 299415HZ div = 342)
[ 3.252929] starfive-jh7110-aon-pinctrl 17020000.pinctrl: StarFive GPIO chip registered 4 GPIOs
loading module clk-starfive-jh7110-stg...
loading module phy-jh7110-pcie...
loading module p[ 3.291095] mmc_host mmc0: Bus speed (slot 0) = 204799999Hz (slot req 300000Hz, actual 299415HZ div = 342)
[ 3.299676] pcie-starfive 2b000000.pcie: error -ENODEV: failed to get valid pcie domain
[ 3.299843] pcie-starfive 2c000000.pcie: error -ENODEV: failed to get valid pcie domain
loading module nvme...
loading module dm_mod...
[ 3.542940] device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: [email protected]
running udev...
[ 3.609137] mmc_host mmc1: Bus speed (slot 0) = 204799999Hz (slot req 50000000Hz, actual 34133333HZ div = 3)
Starting systemd-udevd version 2[ 3.620683] mmc1: new high speed SDXC card at address aaaa
56.8
kbd_mode: KDSKBMODE: Inappropriate ioctl for device
Gstarting device mapper and LVM...
File descriptor 8 (/dev/console) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/bin/ash
File descriptor 9 (/dev/console) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/bin/ash
waiting for device /dev/disk/by-uuid/997fc0c7-2860-4924-a732-04493c579f20 to appear...File descriptor 3 (/nix/store/r6hn0pf2lvxxcjkg2vsncdv3wk75zpim-initrd-fsinfo) leaked on l
vm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/bin/ash
File descriptor 8 (/dev/console) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/bin/ash
File descriptor 9 (/dev/console) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/bin/ash
.File descriptor 3 (/nix/store/r6hn0pf2lvxxcjkg2vsncdv3wk75zpim-initrd-fsinfo) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/
bin/ash
File descriptor 8 (/dev/console) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/bin/ash
File descriptor 9 (/dev/console) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/bin/ash
.File descriptor 3 (/nix/store/r6hn0pf2lvxxcjkg2vsncdv3wk75zpim-initrd-fsinfo) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/
bin/ash
File descriptor 8 (/dev/console) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/bin/ash
File descriptor 9 (/dev/console) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/bin/ash
.File descriptor 3 (/nix/store/r6hn0pf2lvxxcjkg2vsncdv3wk75zpim-initrd-fsinfo) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/
bin/ash
File descriptor 8 (/dev/console) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/bin/ash
File descriptor 9 (/dev/console) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/bin/ash
.File descriptor 3 (/nix/store/r6hn0pf2lvxxcjkg2vsncdv3wk75zpim-initrd-fsinfo) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/
bin/ash
File descriptor 8 (/dev/console) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/bin/ash
File descriptor 9 (/dev/console) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/bin/ash
.File descriptor 3 (/nix/store/r6hn0pf2lvxxcjkg2vsncdv3wk75zpim-initrd-fsinfo) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/
bin/ash
File descriptor 8 (/dev/console) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/bin/ash
File descriptor 9 (/dev/console) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/bin/ash
.File descriptor 3 (/nix/store/r6hn0pf2lvxxcjkg2vsncdv3wk75zpim-initrd-fsinfo) leaked on lvm invocation. Parent PID 1: /nix/store/4nc7aajxlpclfb1gx0hp5d1kswdjprb3-extra-utils/
bin/ash
Timed out waiting for device /dev/disk/by-uuid/997fc0c7-2860-4924-a732-04493c579f20, trying to mount anyway.
mounting /dev/disk/by-uuid/997fc0c7-2860-4924-a732-04493c579f20 on /...
[ 43.434639] /dev/disk/by-uuid/997fc0c7-2860-4924-a732-04493c579f20: Can't lookup blockdev
mount: mounting /dev/disk/by-uuid/997fc0c7-2860-4924-a732-04493c579f20 on /mnt-root/ failed: No such file or directory
Meanwhile the installer image can see the NVME on boot:
[ 6.291783] pcie-starfive 9c0000000.pcie: port link up
[ 6.297978] pcie-starfive 9c0000000.pcie: PCI host bridge to bus 0001:00
[ 6.299790] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[ 6.304747] pci_bus 0001:00: root bus resource [bus 00-ff]
[ 6.317018] pci_bus 0001:00: root bus resource [mem 0x38000000-0x3fffffff]
[ 6.323933] pci_bus 0001:00: root bus resource [mem 0x980000000-0x9bfffffff pref]
[ 6.331556] pci 0001:00:00.0: [1556:1111] type 01 class 0x060400 PCIe Root Port
[ 6.338923] pci 0001:00:00.0: PCI bridge to [bus 01]
[ 6.343912] pci 0001:00:00.0: bridge window [mem 0x38000000-0x380fffff]
[ 6.350722] pci 0001:00:00.0: bridge window [mem 0x900000000-0x9000fffff 64bit pref]
[ 6.359042] pci 0001:00:00.0: supports D1 D2
[ 6.363343] pci 0001:00:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 6.371530] pci 0001:01:00.0: [144d:a808] type 00 class 0x010802 PCIe Endpoint
[ 6.378797] pci 0001:01:00.0: BAR 0 [mem 0x00000000-0x00003fff 64bit]
[ 6.385433] pci 0001:01:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at 0001:00:00.0 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link)
[ 6.407795] pci_bus 0001:01: busn_res: [bus 01-ff] end is updated to 01
[ 6.414474] pci 0001:00:00.0: bridge window [mem 0x38000000-0x380fffff]: assigned
[ 6.421982] pci 0001:01:00.0: BAR 0 [mem 0x38000000-0x38003fff 64bit]: assigned
[ 6.429337] pci 0001:00:00.0: PCI bridge to [bus 01]
[ 6.434324] pci 0001:00:00.0: bridge window [mem 0x38000000-0x380fffff]
[ 6.441150] pci_bus 0001:00: resource 4 [mem 0x38000000-0x3fffffff]
[ 6.447433] hub 1-1:1.0: USB hub found
[ 6.447441] pci_bus 0001:00: resource 5 [mem 0x980000000-0x9bfffffff pref]
[ 6.451340] hub 1-1:1.0: 4 ports detected
[ 6.458076] pci_bus 0001:01: resource 1 [mem 0x38000000-0x380fffff]
[ 6.458411] pcieport 0001:00:00.0: PME: Signaling with IRQ 56
loading module nvme...
[ 6.573825] nvme nvme0: pci function 0001:01:00.0
[ 6.578599] nvme 0001:01:00.0: enabling device (0000 -> 0002)
[ 6.587231] nvme nvme0: missing or invalid SUBNQN field.
[ 6.592879] nvme nvme0: D3 entry latency set to 8 seconds
[ 6.599815] mmc_host mmc0: Bus speed (slot 0) = 45511111Hz (slot req 100000Hz, actual 99805HZ div = 228)
[ 6.605750] hwmon hwmon0: temp1_input not attached to any thermal zone
[ 6.615884] hwmon hwmon0: temp2_input not attached to any thermal zone
[ 6.622441] hwmon hwmon0: temp3_input not attached to any thermal zone
[ 6.639329] nvme nvme0: 4/0/0 default/read/poll queues
[ 6.655998] nvme0n1: p1 p2
loading module dm_mod...
[ 6.732731] device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: [email protected]
Device config: https://github.com/RossComputerGuy/dotfiles/blob/master/devices/jegan/default.nix
CC @onny since they got it working before.
Hey, which image did you use? I copied the sd-image over to the NVME device (using dd) exactly as with the installation to sd-card
I did a
nixos-installonto the NVME
In this case I can't tell. You would still need to copy Uboot into the NVME because I guess nixos-install won't do this yet automatically.
I'm using my sdcard for u-boot which is doing a uefi boot on the NVME.
I tried to dd the generated sd-card image to the nvme but fails with:
starfive_pcie pcie@2C000000: Port link up.
starfive_pcie pcie@2C000000: Starfive PCIe bus probed.
PCI: Failed autoconfig bar 10
Device 0: Vendor: 0x17aa Rev: 2.5.0412 Prod: 1280934701896
Type: Hard Disk
Capacity: 244198.3 MB = 238.4 GB (500118192 x 512)
... is now current device
Try booting from NVME0 ...
Can't set block device
## Warning: Input data exceeds 1048576 bytes - truncated
## Info: input data size = 1048578 = 0x100002
## Error: "boot2" not defined
Device 0: Vendor: 0x17aa Rev: 2.5.0412 Prod: 1280934701896
Type: Hard Disk
Capacity: 244198.3 MB = 238.4 GB (500118192 x 512)
... is now current device
Try booting from NVME0 ...
Can't set block device
## Warning: Input data exceeds 1048576 bytes - truncated
## Info: input data size = 1048578 = 0x100002
## Error: "boot2" not defined
Tring booting distro ...
Card did not respond to voltage select! : -110
Card did not respond to voltage select! : -110
Device 0: Vendor: 0x17aa Rev: 2.5.0412 Prod: 1280934701896
Type: Hard Disk
Capacity: 244198.3 MB = 238.4 GB (500118192 x 512)
... is now current device
Try booting from NVME0 ...
Can't set block device
## Warning: Input data exceeds 1048576 bytes - truncated
## Info: input data size = 1048578 = 0x100002
Retrieving file: /extlinux/extlinux.conf
Can't set block device
Error reading config file
Device 0: Vendor: 0x17aa Rev: 2.5.0412 Prod: 1280934701896
Type: Hard Disk
Capacity: 244198.3 MB = 238.4 GB (500118192 x 512)
... is now current device
Try booting from NVME0 ...
Can't set block device
## Warning: Input data exceeds 1048576 bytes - truncated
## Info: input data size = 1048578 = 0x100002
Retrieving file: /extlinux/extlinux.conf
Can't set block device
Error reading config file
The stock image from https://github.com/starfive-tech/VisionFive2/releases/ sdcard.img does boot fine directly from the nvme with this output:
starfive_pcie pcie@2C000000: Port link up.
starfive_pcie pcie@2C000000: Starfive PCIe bus probed.
PCI: Failed autoconfig bar 10
Device 0: Vendor: 0x17aa Rev: 2.5.0412 Prod: 1280934701896
Type: Hard Disk
Capacity: 244198.3 MB = 238.4 GB (500118192 x 512)
... is now current device
Try booting from NVME0 ...
1235 bytes read in 4 ms (300.8 KiB/s)
141142766 bytes read in 817 ms (164.8 MiB/s)
## Loading kernel from FIT Image at 60000000 ...
Using 'config-1' configuration
Trying 'vmlinux' kernel subimage
Description: vmlinux
Type: Kernel Image
Compression: uncompressed
Data Start: 0x600000c8
Data Size: 24178176 Bytes = 23.1 MiB
Architecture: RISC-V
OS: Linux
Load Address: 0x40200000
Entry Point: 0x40200000
Verifying Hash Integrity ... OK
## Loading fdt from FIT Image at 60000000 ...
Using 'config-1' configuration
Trying 'fdt' fdt subimage
Description: unavailable
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x6868d8cc
Data Size: 52430 Bytes = 51.2 KiB
Architecture: RISC-V
Load Address: 0x46000000
Hash algo: sha256
Hash value: 9537d7c8ea049fa11e59710e7eb3dcbf79cf028829bda12709552c0ffc3a646f
Verifying Hash Integrity ... sha256+ OK
Loading fdt from 0x6868d8cc to 0x46000000
Booting using the fdt blob at 0x46000000
## Loading loadables from FIT Image at 60000000 ...
Trying 'ramdisk' loadables subimage
Description: buildroot initramfs
Type: RAMDisk Image
Compression: uncompressed
Data Start: 0x6170ef7c
Data Size: 116910212 Bytes = 111.5 MiB
Architecture: RISC-V
OS: Linux
Load Address: 0x46100000
Entry Point: unavailable
Hash algo: sha256
Hash value: bb8ce30808171cff1c6863dcbbd13f7f5f94c611580a898210893fe4818717fb
Verifying Hash Integrity ... sha256+ OK
Loading loadables from 0x6170ef7c to 0x46100000
Loading Kernel Image
Booting kernel in
## Flattened Device Tree blob at 46000000
Booting using the fdt blob at 0x46000000
Using Device Tree in place at 0000000046000000, end 000000004600ffff
Starting kernel ...
clk u0_mipitx_dphy_clk_txesc already disabled
[ 0.000000] Linux version 5.15.0 (jenkins@soft05) (riscv64-buildroot-linux-gnu-gcc.br_real (Buildroot JH7110_VF2_515_v5.11.3) 12.2.0, GNU ld (GNU Binutils) 2.39) #1 SMP Thu Mar 14 19:21:20 CST 2024
The image from their githube page seems to give a different partiton layout:
loop0
├─loop0p1
├─loop0p2
├─loop0p3 vfat FAT16 F01E-258D
└─loop0p4 ext4 1.0 rootfs 483c9a6c-c90f-41cc-ae87-177c44dce036
VS the image generated by nix:
loop1
├─loop1p1
├─loop1p2
└─loop1p3 ext4 1.0 NIXOS_SD 44444444-4444-4444-8888-888888888888
OP's problem seems to be from an incorrect devicetree. I'm pretty sure this is because the U-Boot -> EFI -> systemd-boot flow doesn't support finding the correct dtb file from a directory, like, at all, so it's using the U-Boot devicetree which lacks a valid linux,pci-domain property, somehow.
Depending on the hardware, one of these should help:
hardware.deviceTree.name = "starfive/jh7110-starfive-visionfive-2-v1.3b.dtb";
hardware.deviceTree.name = "starfive/jh7110-starfive-visionfive-2-v1.2a.dtb";
When U-Boot 2025.04 eventually lands we'll have this https://github.com/u-boot/u-boot/commit/84d3911a01783ce386883a97fcc4157039793144 and that should make it use the right devicetree all the way and then we won't need to load a devicetree in the boot config. Unless we want to change it...
As for the other problem where U-Boot doesn't even see the NVMe device, I have no clue
Unsure why the image I build fails to bootstrap vs teh sdcard.img provided by sifive @ https://github.com/starfive-tech/VisionFive2/releases/. they are both dd'd to the nvme drive directly. the nixos image I generate from the readme.md flake via nix build. any ideas what I am doing wrong? I have v1.3B of the board and update the uboot and firmware to the latest via the tftpd process first.
@evilbulgarian where did you get the firmware? is it nixos-hardware?
From here: https://github.com/starfive-tech/VisionFive2/releases/ they have from last week these two:
@evilbulgarian Booting from the StarFive firmware is not supported. It does not follow mainline U-Boot conventions.
Unfortunately #1296 made it slightly harder to just get the firmware. Instead, grab any visionfive 2 nixos-hardware configuration and build config.system.build.uboot and use u-boot.itb and u-boot-spl.bin.normal.out from that.
@evilbulgarian Booting from the StarFive firmware is not supported. It does not follow mainline U-Boot conventions.
Unfortunately #1296 made it slightly harder to just get the firmware. Instead, grab any visionfive 2 nixos-hardware configuration and build
config.system.build.ubootand useu-boot.itbandu-boot-spl.bin.normal.outfrom that.
I see thanks so much! Seems like same issue with failed to retrieve file: /extlinux/extlinux.conf:
StarFive # tftpboot 0xa0000000 ${serverip}:u-boot-spl.bin.normal.out
Using ethernet@16040000 device
TFTP from server 192.168.120.100; our IP address is 192.168.120.222
Filename 'u-boot-spl.bin.normal.out'.
Load address: 0xa0000000
Loading: *
ARP Retry count exceeded; starting again
StarFive # tftpboot 0xa0000000 ${serverip}:u-boot-spl.bin.normal.out
Using ethernet@16040000 device
TFTP from server 192.168.120.100; our IP address is 192.168.120.222
Filename 'u-boot-spl.bin.normal.out'.
Load address: 0xa0000000
Loading: ###########
28 MiB/s
done
Bytes transferred = 146850 (23da2 hex)
StarFive # tftpboot 0xa0000000 ${serverip}:u-boot.itb
Using ethernet@16040000 device
TFTP from server 192.168.120.100; our IP address is 192.168.120.222
Filename 'u-boot.itb'.
Load address: 0xa0000000
Loading: #################################################################
#####
29.7 MiB/s
done
Bytes transferred = 1026267 (fa8db hex)
StarFive # reboot
Unknown command 'reboot' - try 'help'
StarFive # reset
resetting ...
U-Boot SPL 2021.10 (Mar 31 2025 - 22:49:23 +0800)
LPDDR4: 4G version: g8ad50857.
Trying to boot from SPI
OpenSBI v1.2
____ _____ ____ _____
/ __ \ / ____| _ \_ _|
| | | |_ __ ___ _ __ | (___ | |_) || |
| | | | '_ \ / _ \ '_ \ \___ \| _ < | |
| |__| | |_) | __/ | | |____) | |_) || |_
\____/| .__/ \___|_| |_|_____/|___/_____|
| |
|_|
Platform Name : StarFive VisionFive V2
Platform Features : medeleg
Platform HART Count : 5
Platform IPI Device : aclint-mswi
Platform Timer Device : aclint-mtimer @ 4000000Hz
Platform Console Device : uart8250
Platform HSM Device : ---
Platform PMU Device : ---
Platform Reboot Device : pm-reset
Platform Shutdown Device : pm-reset
Platform Suspend Device : ---
Firmware Base : 0x40000000
Firmware Size : 392 KB
Firmware RW Offset : 0x40000
Runtime SBI Version : 1.0
Domain0 Name : root
Domain0 Boot HART : 1
Domain0 HARTs : 0*,1*,2*,3*,4*
Domain0 Region00 : 0x0000000002000000-0x000000000200ffff M: (I,R,W) S/U: ()
Domain0 Region01 : 0x0000000040000000-0x000000004003ffff M: (R,X) S/U: ()
Domain0 Region02 : 0x0000000040040000-0x000000004007ffff M: (R,W) S/U: ()
Domain0 Region03 : 0x0000000000000000-0xffffffffffffffff M: (R,W,X) S/U: (R,W,X)
Domain0 Next Address : 0x0000000040200000
Domain0 Next Arg1 : 0x0000000042200000
Domain0 Next Mode : S-mode
Domain0 SysReset : yes
Domain0 SysSuspend : yes
Boot HART ID : 1
Boot HART Domain : root
Boot HART Priv Version : v1.11
Boot HART Base ISA : rv64imafdcbx
Boot HART ISA Extensions : none
Boot HART PMP Count : 8
Boot HART PMP Granularity : 4096
Boot HART PMP Address Bits: 34
Boot HART MHPM Count : 2
Boot HART MIDELEG : 0x0000000000000222
Boot HART MEDELEG : 0x000000000000b109
U-Boot 2021.10 (Mar 31 2025 - 22:49:23 +0800), Build: jenkins-github_visionfive2-34
CPU: rv64imacu_zba_zbb
Model: StarFive VisionFive V2
DRAM: 4 GiB
MMC: sdio0@16010000: 0, sdio1@16020000: 1
Loading Environment from SPIFlash... SF: Detected gd25lq128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment
StarFive EEPROM format v2
--------EEPROM INFO--------
Vendor : StarFive Technology Co., Ltd.
Product full SN: VF7110B1-2253-D004E000-40000343
data version: 0x2
PCB revision: 0xb2
BOM revision: A
Ethernet MAC0 address: 6c:cf:39:00:2e:4b
Ethernet MAC1 address: 6c:cf:39:00:2e:4c
--------EEPROM INFO--------
In: serial
Out: serial
Err: serial
Model: StarFive VisionFive V2
Net: eth0: ethernet@16030000, eth1: ethernet@16040000
Hit any key to stop autoboot: 0
Card did not respond to voltage select! : -110
Card did not respond to voltage select! : -110
starfive_pcie pcie@2B000000: Port link up.
starfive_pcie pcie@2B000000: Starfive PCIe bus probed.
PCI: Failed autoconfig bar 10
starfive_pcie pcie@2C000000: Port link up.
starfive_pcie pcie@2C000000: Starfive PCIe bus probed.
PCI: Failed autoconfig bar 10
Device 0: Vendor: 0x17aa Rev: 2.5.0412 Prod: 1280934701896
Type: Hard Disk
Capacity: 244198.3 MB = 238.4 GB (500118192 x 512)
... is now current device
Try booting from NVME0 ...
Can't set block device
## Warning: Input data exceeds 1048576 bytes - truncated
## Info: input data size = 1048578 = 0x100002
## Error: "boot2" not defined
Device 0: Vendor: 0x17aa Rev: 2.5.0412 Prod: 1280934701896
Type: Hard Disk
Capacity: 244198.3 MB = 238.4 GB (500118192 x 512)
... is now current device
Try booting from NVME0 ...
Can't set block device
## Warning: Input data exceeds 1048576 bytes - truncated
## Info: input data size = 1048578 = 0x100002
## Error: "boot2" not defined
Tring booting distro ...
Card did not respond to voltage select! : -110
Card did not respond to voltage select! : -110
Device 0: Vendor: 0x17aa Rev: 2.5.0412 Prod: 1280934701896
Type: Hard Disk
Capacity: 244198.3 MB = 238.4 GB (500118192 x 512)
... is now current device
Try booting from NVME0 ...
Can't set block device
## Warning: Input data exceeds 1048576 bytes - truncated
## Info: input data size = 1048578 = 0x100002
Retrieving file: /extlinux/extlinux.conf
Can't set block device
Error reading config file
Device 0: Vendor: 0x17aa Rev: 2.5.0412 Prod: 1280934701896
Type: Hard Disk
Capacity: 244198.3 MB = 238.4 GB (500118192 x 512)
... is now current device
Try booting from NVME0 ...
Can't set block device
## Warning: Input data exceeds 1048576 bytes - truncated
## Info: input data size = 1048578 = 0x100002
Retrieving file: /extlinux/extlinux.conf
Can't set block device
Error reading config file
StarFive #
You did not actually write the files to flash. See the sf probe and sf update commands here besides tftpboot https://doc-en.rvspace.org/VisionFive2/Quick_Start_Guide/VisionFive2_SDK_QSG/spl_new.html
You did not actually write the files to flash. See the
sf probeandsf updatecommands here besidestftpboothttps://doc-en.rvspace.org/VisionFive2/Quick_Start_Guide/VisionFive2_SDK_QSG/spl_new.html
Yup, I missed the sf update 0xa0000000 0x100000 $filesize thanks so much booted fine now!
Throwing in the device tree option for my VF2's revision fixed the issue.