Using grub-image ? - Printable Version +- PINE64 (https://forum.pine64.org) +-- Forum: Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=111) +--- Forum: Linux on Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=114) +--- Thread: Using grub-image ? (/showthread.php?tid=9515) |
Using grub-image ? - ScarFez - 03-25-2020 Would it be safe to use the grub-image, with all the modules (as long as it doesn't exceed 16 MB) and flash it to the spi ? Which would eliminate the need for uboot entirely ? Just checking my options before i get an ssd, for the nvme adaper (pbp) RE: Using grub-image ? - tophneal - 03-25-2020 You'll have to do some real configuring to use GRUB, and it will still rely on u-boot. If you want to flash to SPI, there are already u-boots for the SPI that are capable of booting from NVMe drives in the PBP. (Thanks to users dhivael and pcm720, respectively!) RE: Using grub-image ? - amiraeva - 03-25-2020 I got grub to work as an EFI payload from uboot, only caveat is that the display doesn't work. Install grub with --target=arm64-efi and --removable flags, and use the following boot script (adjust as needed to your setup): Code: setenv bootargs initrd=/boot/initramfs-linux.img console=ttyS0 console=tty1 root=LABEL=ROOT_MNJRO rw rootwait video=eDP-1:1920x1080@60 video=HDMI-A-1:1920x1080@60 bootsplash.bootfile=bootsplash-themes/manjaro/bootsplash Code: set timeout_style="menu" I've been poking around the u-boot source code to try and get the eDP and LCD drivers working <https://github.com/amiraeva/uboot-pbp>. So far I can get the display to flicker for a brief second before the u-boot serial console loads, and have run out of things to try. Any ideas/suggestions would be appreciated! RE: Using grub-image ? - Arwen - 03-25-2020 @ScarFez, you don't want to flash Grub to the SPI. There are more things in the U-Boot package than just booting. One of the sections is for the dual control processors, which handle the speed adjustment and thermal limiting, (if I understand it correctly). Many vendors use closed source code for this function. We do have some work alike open source for that code, (can't remember it's name). Plus, there is DRAM initialization and other SoC specific code that needs to run. Anyway, you want U-Boot, (or similar firmware), to be in SPI, (eventually), and have Grub as the payload. Thus, we can change kernels, boot devices, password protect booting, or editing grub menu entries, all from Grub. That's my ideal end result. Stable, fully open source SPI firmware that will check USB, SD card, NVMe and then eMMC for booting. Whence a device has been selected, Grub takes over from that specific device. (So if Grub gets screwed up on your eMMC, you can boot using USB or SD card to recover.) RE: Using grub-image ? - pgwipeout - 05-21-2020 (03-25-2020, 01:40 PM)amiraeva Wrote: I got grub to work as an EFI payload from uboot, only caveat is that the display doesn't work. Install grub with --target=arm64-efi and --removable flags, and use the following boot script (adjust as needed to your setup): Did you get the grub serial console to work? I only seem to get this output when booting grub from u-boot: Code: 139264 bytes read in 12 ms (11.1 MiB/s) But no menu. Edit: Figured it out, if anyone ever feels like they are nuking something, remember to change this: Code: GRUB_TIMEOUT_STYLE=hidden Code: GRUB_TIMEOUT_STYLE=menu |