It looks like the NVMe image is broken. do we get an ipdated Image ?
1 Like
Yes, it’s missing a large part of the image. We still haven’t seen anything in this thread about a new image coming.
In the mean time, several of us have had success using the SD card image to repair it.
- Boot from the SD card with the NVMe installed.
- dd if=/dev/mmcblk1p4 of=/dev/nvme0n1p4 bs=4M
- Remove the SD card and reboot
This worked well enough but a fixed image would be nice.
3 Likes
dd if=/dev/mmcblk1p4 of=/dev/nvme0n1p4 bs=4M status=progress to seeing progress of command.
but still not working, here the log:
U-Boot SPL 2021.10 (Mar 14 2024 - 19:21:18 +0800)
LPDDR4: 8G 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 14 2024 - 19:21:18 +0800), Build: jenkins-github_visionfive2-23
CPU: rv64imacu_zba_zbb
Model: StarFive VisionFive V2
DRAM: 8 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: VF7110A1-2250-########-00000###
data version: 0x2
PCB revision: 0xa1
BOM revision: A
Ethernet MAC0 address: ##:##:##:##:##:##
Ethernet MAC1 address: ##:##:##:##:##:##
--------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: 0x144d Rev: 5B2QGXA7 Prod: S5GXNX1W311984F
Type: Hard Disk
Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
… is now current device
Try booting from NVME0 …
Failed to load ‘vf2_uEnv.txt’
Info: input data size = 829 = 0x33D
Error: “boot2” not defined
Device 0: Vendor: 0x144d Rev: 5B2QGXA7 Prod: S5GXNX1W311984F
Type: Hard Disk
Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
… is now current device
Try booting from NVME0 …
Failed to load ‘vf2_uEnv.txt’
Info: input data size = 829 = 0x33D
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: 0x144d Rev: 5B2QGXA7 Prod: S5GXNX1W311984F
Type: Hard Disk
Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
… is now current device
Try booting from NVME0 …
419 bytes read in 3 ms (135.7 KiB/s)
Retrieving file: /extlinux/extlinux.conf
1386 bytes read in 4 ms (337.9 KiB/s)
U-Boot menu
1: Debian GNU/Linux bookworm/sid 6.6.20-starfive
2: Debian GNU/Linux bookworm/sid 6.6.20-starfive (rescue target)
3: Debian GNU/Linux bookworm/sid 5.15.0-starfive
4: Debian GNU/Linux bookworm/sid 5.15.0-starfive (rescue target)
Enter choice: 1: Debian GNU/Linux bookworm/sid 6.6.20-starfive
Retrieving file: /initrd.img-6.6.20-starfive
** No partition table - nvme 0 **
Couldn’t find partition nvme 0:3
Can’t set block device
Skipping l0 for failure retrieving initrd
2: Debian GNU/Linux bookworm/sid 6.6.20-starfive (rescue target)
Retrieving file: /initrd.img-6.6.20-starfive
** No partition table - nvme 0 **
Couldn’t find partition nvme 0:3
Can’t set block device
Skipping l0r for failure retrieving initrd
3: Debian GNU/Linux bookworm/sid 5.15.0-starfive
Retrieving file: /initrd.img-5.15.0-starfive
** No partition table - nvme 0 **
Couldn’t find partition nvme 0:3
Can’t set block device
Skipping l1 for failure retrieving initrd
4: Debian GNU/Linux bookworm/sid 5.15.0-starfive (rescue target)
Retrieving file: /initrd.img-5.15.0-starfive
** No partition table - nvme 0 **
Couldn’t find partition nvme 0:3
Can’t set block device
Skipping l1r for failure retrieving initrd
Device 0: Vendor: 0x144d Rev: 5B2QGXA7 Prod: S5GXNX1W311984F
Type: Hard Disk
Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
… is now current device
Try booting from NVME0 …
** No partition table - nvme 0 **
Couldn’t find partition nvme 0:3
Can’t set block device
Retrieving file: /extlinux/extlinux.conf
** No partition table - nvme 0 **
Couldn’t find partition nvme 0:3
Can’t set block device
Error reading config file
same here. last working image 202311 
I also had the problem with the image for nvme, it doesn’t boot. Seeing the size of the file I ask the riscv team to check if an incorrect or corrupt file was uploaded by mistake.
The other images are 1GB and I don’t understand why the one for nvme is 542MB
Greetings to the entire riscv team and thank you for everything you are doing @Michael.Zhu
exactly same issue here.
booting from SD image worked, but no network
dding SD to SSD … no boot
Board revision
--------EEPROM INFO--------
Vendor : StarFive Technology Co., Ltd.
Product full SN: VF7110A1-2250-########-00000###
data version: 0x2
PCB revision: 0xa1
BOM revision: A
Ethernet MAC0 address: ##:##:##:##:##:##
Ethernet MAC1 address: ##:##:##:##:##:##
--------EEPROM INFO--------
My bad 
just upload the correct one
3 Likes
I was a little embarrassed to ask you to check, but I’m happy it was just a problem of having uploaded the file wrong.
@Michael.Zhu when you have time try to correct the file extension to .bz2 because currently the extension is .img and can be confusing when uploading to nvme.
Thank you as always for your prompt willingness to resolve.
- Thanks for uploading a fresh image
Downloaded,
flashed NVMe, still problems, Debian is not loaded.
(re)flashing NVMe, with deactivated Antivirus. boot success
but onboard Network adapers do not connect (remain in status connecting) . any clue, how to fix ?
there seems te same problem with the 202403 image
You need to rename the file from img extension to img.bz2 and unzip the file. The size of the decompressed image file is approximately 4GB
1 Like
yes, did fresh download.
boots now (flash seems to need disabled antivirus)
but no network
no network for me too
There are a few things you can try：
1.checking network under uboot.
2.updating spl and uboot in Flash.
3.eraseenv under uboot.
4.checking is there any network by flashing SD image and boot from SD card bootmode.
Have already updated both to latest version
U-Boot SPL 2021.10 (Mar 14 2024 - 19:21:18 +0800)
LPDDR4: 8G version: g8ad50857.
Trying to boot from SPI
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 6c:cf:39:00:20:79 brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 6c:cf:39:00:20:7a brd ff:ff:ff:ff:ff:ff
4: sit0@NONE: mtu 1480 qdisc noop state DOWN group default qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0
How about the network under uboot? Could you please ping a IP under uboot?
no idea, how i can do.
image 202311 worked fine out of the box, since 202403 not. so network in principle should work, but i have no clue jet, i maybe miss a config setting … but which. as you can see, it does not get an ip-address
U-Boot 2021.10 (Mar 14 2024 - 19:21:18 +0800), Build: jenkins-github_visionfive2-23
CPU: rv64imacu_zba_zbb
Model: StarFive VisionFive V2
DRAM: 8 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: VF7110A1-2250-D008E000-00000407
data version: 0x2
PCB revision: 0xa1
BOM revision: A
Ethernet MAC0 address: 6c:cf:39:00:20:79
Ethernet MAC1 address: 6c:cf:39:00:20:7a
--------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
StarFive # ping 10.168.246.1
ethernet@16030000 Waiting for PHY auto negotiation to complete… done
Using ethernet@16030000 device
Warning: gatewayip needed but not set
Warning: gatewayip needed but not set
ping failed; host 10.168.246.1 is not alive
StarFive # ping 10.168.246.2
Using ethernet@16030000 device
Warning: gatewayip needed but not set
host 10.168.246.2 is alive
