(09-24-2021, 02:32 AM)t4_4t Wrote: It fails at the last stage of the installation process. ('grub-install dummy' failed)
So we have to deal with that part manually, but other than that there are no problems.

If we choose the graphical installation, we can use the mouse/keyboard and the locale will work correctly.

With this workmanship, it is comparable to a standard x86/x64 installer.

(09-24-2021, 02:32 AM)t4_4t Wrote: It fails at the last stage of the installation process. ('grub-install dummy' failed)
So we have to deal with that part manually, but other than that there are no problems.

If we choose the graphical installation, we can use the mouse/keyboard and the locale will work correctly.

With this workmanship, it is comparable to a standard x86/x64 installer.

(09-26-2021, 04:02 AM)t4_4t Wrote: > The problem was caused by the "HDMI to VGA adapter",
> and connecting it directly to the monitor solved your second report.

> Then just like my case, you also encountered Error: "'grub-install dummy' failed".

> I interpreted your report as such, is that correct ?
> If so, you should be able to boot from the SD-Card with the same solution as I did.

> But, the conditions are as follows
> If the above meets your requirements, I can describe how I did it.

----

Yes, the error I'm getting is "grub-install dummy failed," and at the exact point which you described.
I was looking at some potential solutions, like the one at https://wiki.debian.org/GrubEFIReinstall
but when I got to step 2 there were some immediate problems:
I tried passiing the kernel parameter "efi=runtime" by pressing the 'e' key with Graphical Rescue selected, then adding that parameter to the line beginning with 'linux.' I then booted (Ctrl-X) into rescue mode, but the directory /sys/firmware/efi/efivars remains empty, and any attempt to mount it results in failure, just as it did when automatically selecting the default rescue mode parameters.
I'm very interested in learning your method of getting Debain to boot off the microSD.

> In the manual partitioning you mention, there are an infinite number of combinations.
> Naturally, it is impossible to try every partition.
> Therefore, I have only tried the following standard partitioning that seems to be recommended.

My partitioni scheme is heavily cutomized but I don't think it'll be an issue in this case, as all directories mentioned in the tutorial are contained on the root (/)  parititon (/, swap, /home, /srv, /tmp and /var are their own separate primary partitions). There is also an EFI partition that I created first during setup.
I'm definitely willing to give your way a try with this setup.
Thanks again for your detailed instructions. esterday I didn't even think I'd get this far.

(09-26-2021, 08:47 AM)t4_4t Wrote: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963208

The version of the installer is different, so the specific steps are different, but the overall process is the same as above.

The following is the manual process after "Executing 'grub-install dummy' failed.".

1. Go back to the upstream menu, and select "Execute a shell" to execute.
2. From the shell, execute the following command.

Code:

# cp -ar /cdrom/EFI/boot /target/boot/efi/EFI/
# chroot /target/
# update-grub

# exit
# exit

3. Go back to the upstream menu, and select "Continue without boot loader" to execute.
4. The rest of the process will be completed (password, etc. will be written back? for a few tens of seconds), you are done.
5. When the installation is finished, the system will automatically reboot and boot from the SD-Card you installed.

Good luck.

(10-01-2021, 01:24 PM)t4_4t Wrote: You seem to be stumped on "GRUB" .

> Is there a way to get the text consoles active in Debian.

If your goal is to solve the above problem, and not to play with "GRUB".
The solution is to boot directly from "u-boot" as in other distributions.
That way, the "boot messages" output, and the console switching by "Ctrl+Alt+Fn", both will work properly.