On 7/24/25 13:35, Michael wrote:
On Thursday, 24 July 2025 17:44:40 British Summer Time Dennis Clarke wrote:
On 7/24/25 11:51, Michael wrote:
On Thursday, 24 July 2025 16:46:10 British Summer Time Nuno Silva wrote:
On 2025-07-24, Michael wrote:
On Thursday, 24 July 2025 15:17:02 British Summer Time Dennis Clarke


<snip>

The GRUB situation is very strange.

p550#
p550# mount /dev/mmcblk0p3 /mnt/gentoo

I did the emerge twice inside the chroot stage3 :

p550#
p550# grep -n 'completed' /mnt/gentoo/var/log/emerge.log | grep -i 'grub'
561:1753295980:  ::: completed emerge (5 of 5) sys-boot/grub-2.12-r7 to /
610:1753297404:  ::: completed emerge (6 of 6) sys-boot/grub-2.12-r7 to /
p550#

That results in a GRUB binary that is very different from the thing I
stole from the SiFive Ubuntu flash stuff :

p550#
p550# ls -l /opt/gentoo_efi/EFI/gentoo/grubriscv64.efi
-rwxr-xr-x 1 root root 159744 Jul 23 19:07
/opt/gentoo_efi/EFI/gentoo/grubriscv64.efi
p550#
p550# ls -l /mnt/mmc_efi/EFI/ubuntu/grubriscv64.efi
-rwxr-xr-x 1 root root 3608576 Jul 16 13:06
/mnt/mmc_efi/EFI/ubuntu/grubriscv64.efi
p550#

Very different sizes there. The Ubuntu stuff is from 16th of July and
seems to be at least twice as large. Could be more modules. No idea
really.

Is there a reason you have borrowed the Ubuntu GRUB executable?  I wouldn't
min 'n match bootloader images.  If you must try them both, try them one at a
time.


I tried to boot with the GRUB built within the chroot stage3. I was very
careful to mount the correct FAT32 dos partition. The one on the board
which appears as /dev/mmcblk0p1. However the board would not boot. It
had some strange message and I did not record it.

I guess I need to try that again.



The GRUB that I built inside the stage3 chroot has never seen the light
of day yet. It exists but I have not used it. It may be a better way
to go here. For the moment just getting past this strange dracut UUID
mixup seems reasonable.

I suggest in the first instance you mount *all* necessary partitions and then
follow the gentoo handbook to chroot into it.  Once you are in the chroot'ed
system you check GRUB_PLATFORMS="..." is set correctly for your platform's
architecture, re-install GRUB, run 'dracut', before you finally run 'grub-
mkconfig -o /boot/grub/grub.cfg' to generate GRUB's configuration.

Exit, unmount and reboot to see what you get.

A better question is "Why dracut"?  Can I just build a kernel and then
get an initramfs image file without the dracut stuff at all? Is this
something really needed?


--
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken

Reply via email to