All kernels are available in the releases area on GitHub Releases · agreenbhm/linux · GitHub
Yes thanks @agreenbhm. I saw them I was just wondering whether there is some built in way (like apt). Anyway I was able to boot from sdcard and recognize nvme with 6.5. Unfortunately with that one network interfaces does not seem to work Any chance new kernel may work with newer SPI image (v3)? Anyway I will try some time toom. And the 6.4 as well. Hopefully I find some setup where both network and nvme works
I haven’t had time to really be working with my VF2 lately so all the builds are being done automatically and I haven’t tested them. I did have to resolve a bunch of merge conflicts from mainline to my branch a week or so ago which may have resulted in some booting issues, even though the build is successful. It’s possible that’s what you’ve run into, but I am just speculating.
Yea so I tried latest 6.4, 6.5 and 6.6. With these results:
6.4 - no nvme
6.5 - no network interface (btw I have 1.3B)
6.6 - no boot
Unfortunately I am out of time for now. So now I wait either to get more time to tackle with this or until we get more feature complete ubuntu release.
Anyway thank you @agreenbhm. It is great to have rolling kernels to experiment
Im pretty sure I’ve had working NVME and ethernet (very slow about 50mbits. but working).
However 6.6 also didn’t boot for me.
New Ubuntu 23.10 with NVME support on VF2:
These look to be 23.04 releases.
Also, I assume I can dd the image to a nvme also. Am I wrong?
But the 23.10 release directory is here: https://cdimage.ubuntu.com/releases/23.10/release/
Sorry if this is trolling, but I think similar enough to the thread. The Ubuntu wiki referenced above provides this sequence for booting:
pci enum
nvme scan
load mmc 0:1 $fdt_addr_r dtb/starfive/jh7110-starfive-visionfive-2-v1.3b.dtb
load mmc 0:1 $kernel_addr_r EFI/boot/bootriscv64.efi
bootefi $kernel_addr_r $fdt_addr_r
I am close to converting that to the nvme device. I assume that the bootefi command will boot the linux kernel. How does this process tell the linux kernel where the root filesystem is?
I have formatted my NVMe and put EFI on partition 1 and Ubuntu on partition 2. Where do I tell the system that my root is /dev/nvme0n1p2?
It is all boot loaders chained to other boot loaders.
My assumption is EFI/boot/bootriscv64.efi then calls EFI/ubuntu/grubriscv64.efi the efi version of grub.
grub then looks for the grub.cfg config file in the boot file system to give you a menu for things to boot.
I’ve used the installer sd card image and done a clean install to nvme and it’s worked well.
It works well. However, for reasons unknown to me, I had to change load mmc 0:1
to load mmc 1:1
.