Fresh Trixie install on VisionFive 2
Dear all,
Having used the StarFive provided debian image for a while on my
VisionFive 2, I wanted to forge ahead and install a "proper" Debian from
scratch using the Trixie installer.
(If this is the wrong list for this question please accept my apologies
in advance - it is my impression that this is very riscv specific
though)
What I ended up doing was getting the latest weekly Trixie netinst image
and writing that to an USB stick.
I then boot my VF2 into U-Boot (and have a serial console attached).
I start up the USB subsystem with "usb start"
I load the EFI image as well as the DTB and boot using EFI:
fatload usb 0:2 0x40200000 efi/boot/bootriscv64.efi
fatload usb 0:2 0x46000000 /dtb/starfive/jh7110-starfive-visionfive-2-v1.3b.dtb
bootefi 0x40200000 0x46000000
This successfully loads up the Debian Trixie GRUB and I get presented
with the installation options - so far so good(!)
Any attempt to boot the installer kernel results in:
"relocation overflow"
from GRUB.
Any subsequent attempt simply states "out of memory".
Using plain GRUB command line I get the same result at any attempt to
load the kernel image.
According to GRUB there is more than plenty of free memory:
grub> lsmmap
base_addr = 0x40000000, length = 0x80000, reserved RAM
base_addr = 0x40080000, length = 0x7e18000, available RAM
base_addr = 0x47e98000, length = 0x27000, ACPI reclaimable RAM
base_addr = 0x47ebf000, length = 0x4e000, faulty RAM (BadRAM)
base_addr = 0x47f0d000, length = 0xae6ac000, available RAM
base_addr = 0xf65b9000, length = 0x2000, faulty RAM (BadRAM)
base_addr = 0xf65bb000, length = 0xe8000, available RAM
base_addr = 0xf66a3000, length = 0x12000, available RAM
base_addr = 0xf66b5000, length = 0xf000, available RAM
base_addr = 0xf66c4000, length = 0x17000, faulty RAM (BadRAM)
base_addr = 0xf66db000, length = 0x1000, available RAM
base_addr = 0xf66dc000, length = 0x149924000, available RAM
grub>
I would appreciate any direction on how to proceed from here. Is there
anything I can do to further troubleshoot this? Or should I simply
approach this differently?
Thank you in advance,
--
/ jakob
Reply to: