[1] https://cdimage.debian.org/cdimage/ports/grub-test/
From 134c589ab28ef5557a3d914a7ed0e4f675940fd5 Mon Sep 17 00:00:00 2001From: John Paul Adrian Glaubitz <glaubitz@localhost>
Did you generate the netboot images as well? To test things remotely (iLO) it is generally more convenient to use netboot that cd-image.
[1] https://cdimage.debian.org/cdimage/ports/grub-test/
Thats fine. I can test the CD image tomorrow Ill have physical access to the box.You can test the netboot image if you want, I uploaded it into the
[1] https://cdimage.debian.org/cdimage/ports/grub-test/
Thats fine. I can test the CD image tomorrow Ill have physical access to the box.You can test the netboot image if you want, I uploaded it into the
Either I am doing something wrong, or this doesnt seem to be quite working.does the debian-installer folder need to be on a specific, hardcoded, path within the EFI partition?
When I run bootnetia64.efi from the debian-installer package I just get the GRUB prompt no config was loaded. I cant even manually load one with configfile since it doesnt seem to be able to parse the partition table.
(...)
When I run the GRUB that was installed by my previous OS installation (grubia64.efi), it does parse the HD partitions correctly
(...)
So, whats the deal with bootnetia64.efi? Does it need to load all the mod files that are present in the grub directory in order to understand GPT partitions? If thats the case, why is it not loading them? Do relative paths not work? In other words,
Did you generate the netboot images as well? To test things remotely (iLO) it is generally more convenient to use netboot that cd-image.
[1] https://cdimage.debian.org/cdimage/ports/grub-test/
Either I am doing something wrong, or this doesnt seem to be quite working.
When I run bootnetia64.efi from the debian-installer package I just get the GRUB prompt no config was loaded. I cant even manually load one with configfile since it doesnt seem to be able to parse the partition table.
Fair enough. This is what I have been doing since forever with ELILO tho. It is very convenient because I can just transfer the package to the EFI partition and remote-start it, all via iLO. Since ELILO is (was) all path-relative, everything worksirrespective of where the bundle got extracted to.
Again it seems as the GRUB version that comes with netinst is incapable of parsing the GPT partition scheme. Once I replaced the EFI executable alone, everything worked and I was able to bootstrap the setup process. I do realize that the reason theoriginal executable may not be parsing the GPT is because it might not be finding the modules present in the grub/ia64-efi folder.
Meanwhile I also tried the latest CD on my Alpha LX164 and I got stuck very early in setup. It appears as the CMD64x module is not present in the CD Debian-installer. This is the EDI controller on many EV56 motherboards. Without it setup cantrecognize the disk or the cdrom.
On 4/30/19 6:13 PM, Pedro Miguel Justo wrote:
And setup will proceed correctly. So, this is what mean by “replacing the executable”. In a nutshell replacing bootnetia64.efi with bootnetia64.efi and keep everything else in the tarball.
This pretty much sounds to me that the GRUB EFI executable from the netboot image is
really just to be used for netboots and not local boots using your particular hack.
I have just created the first test image for debian-installer on ia64 with grub-efi as a bootloader instead of elilo. The changes have not been committed
to git yet but a test image can be found at [1].
Could someone test whether this image does something useful for them?
For anyone interested, the patches for d-i and debian-cd are attached.
Adrian
[1] https://cdimage.debian.org/cdimage/ports/grub-test/
I test-booted it on RX2660 (booted into installer fine) and RX1600 (grub loads, kernel starting reboots as do most kernels on RX1600, RX1620 and RX2800).
Did not try how it installs grub (yet) because I did not have a vacant disk there.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 57:23:48 |
Calls: | 6,652 |
Calls today: | 4 |
Files: | 12,200 |
Messages: | 5,331,023 |