On 25/04/2019 07:29, John Paul Adrian Glaubitz wrote: > On 4/25/19 8:07 AM, Mark Cave-Ayland wrote: >>> Yes, that would be most likely the sparc64.elf image that grub-mkimage >>> produces. But >>> I don't know yet how to encode the boot path for that into the bootable >>> image. >> >> I'm struggling to see from the man pages the relationship between >> sparc64.elf and >> cdboot.img. Presumably grub-mkimage generates sparc64.elf which is a >> self-contained >> grub executable, whilst cdboot.img is the compiled version of boot.S? > > Yes, sparc64.elf is the boot image created by grub-mkimage and whose bootpath > needs > to be passed to the initial boot loader.
I'd expect that to be done by boot.S since the PROM on it's own can't load sparc64.elf directly. A quick browse of the source shows that it looks up bootpath and tries to load the grub kernel from the same device, i.e. the partition or slice that cdrom and/or disk in the PROM is aliased to. I can't see how that would work because that's where boot.S was loaded from in the first place. When grub is installed to disk as per your latest ISO images, what is the filesystem/partition type being used? ATB, Mark.
