Thank you Alex. When located in fs1:\EFI\debian, elilo -C \EFI\debian\elilo.conf perfectly works. But once in Linux, elilo -v --efiboot failed with error messages regarding a missing BootCurrent-... variable in /proc/efi/vars.
As suggested by Dann, I upgraded efibootmgr and elilo. I used the one on the Hewlett Packard ia64-net (20030304) CD. I don't know which package effectively corrected the problem, but the missing BootCurrent-... variable was created and elilo -c --efiboot successfully created the entry in the EFI boot menu. Le mar 20/01/2004 Ã 16:33, Alex Williamson a Ãcrit : > Emeric, > > Old versions of elilo, like in woody, don't look for the config file > in the current directory. If you go to fs1:\efi\debian and run 'elilo > -C \efi\debian\elilo.conf' does it work? If you can get the system up, > it'll be much easier to understand why you don't have a boot entry. > >From a linux prompt, run 'elilo -v --efiboot' This should try to > recreate the boot menu entry. A common problem is mounting your efi > partition at /boot. This will cause the elilo script to fail. You can > run efibootmgr before you reboot to get a listing of boot menu entries. > Alex > > On Tue, 2004-01-20 at 06:42, Emeric Maschino wrote: > > Hi there, > > > > I have a question regarding the boot process of Woody on an IA-64 > > platform. Where should the kernel images and elilo.* files go? > > > > I have a hp workstation i2000 with 3 HDDs. On the first (/dev/sda) is > > Windows XP 64-Bit Edition installed. On the second (/dev/sdb) is Debian > > GNU/Linux Woody installed. On the third (/dev/sdc) is HP-UX 11i v1.5 > > installed. Current BIOS is 1.17c due to my Itanium processors being C0 > > stepping. > > > > When asking to make the system bootable during the Woody installation > > process, I choose to install elilo on /dev/sdb1. I can briefly see a > > efibootmgr error message just before the reboot process starts. At boot > > up, there's no Debian entry in the EFI menu (might be related to the > > efibootmgr error I think). So, using the EFI shell, I navigate through > > fs1:\EFI\debian and manually enter elilo with no luck. I'm given an > > error about a missing vmlinux file. This path however contains > > elilo.conf, elilo.efi, README and vmlinuz. Trying to rename vmlinuz to > > vmlinux doesn't solve the problem. Moving all these files in fs1:\EFI > > changes nothing but moving them to fs1:\ makes the system bootable. > > Really stange because in my elilo.conf file, all paths are related to > > EFI/debian. > > > > Any idea what's wrong with elilo and why the boot entry isn't created? I > > have no problem with other Linux distributions on the same system > > (Mandrake 8.1, SuSE 7.2, OpenLinux 3.1 or Red Hat 7.x). > > > > Thanks. > -- > Alex Williamson HP Linux & Open Source Lab > >
