Threaded Mode | Linear Mode

rahuls551 · 2019-01-21, 05:58

Hi Guys,

I am building a .rom and when i try to load the rom i am getting the option rom is failing with Installation failed - cannot continue.

The build command i am using is make bin-x86_64-pcbios/x.rom.

Any ideas?

***NiKiZe*** · 2019-01-21, 06:19

This post has little or no usefull information!

What is the _exact_ error message you get, full message, case sensitive!
What are you actually building?
Where are you uploading the ROM?
Have you tried with normal 32bit builds?
Have you tried a .usb build first and that boots ok on the same hardware?

So "\nInstallation failed - cannot continue\n" comes from
https://git.ipxe.org/ipxe.git/blob/3946a...fix.S#l993
Which was introduced in https://git.ipxe.org/ipxe.git/commitdiff...927eedfbf4 which might give a few hints on what to check next.

rahuls551 · (This post was last modified: 2019-01-21 09:08 by rahuls551.)

(2019-01-21 06:19)NiKiZe Wrote: This post has little or no usefull information!

What is the _exact_ error message you get, full message, case sensitive!
It says:
iPXE(PCI XX:XX:XX) starting execution...00000000 FA000000 0000AA55
Installation failed...cannot continue.

What are you actually building?
I am actually trying to build an option rom that will work for the legacy boot.
Where are you uploading the ROM?
I am flashing it on the hardware
Have you tried with normal 32bit builds?
I have not tried that yet. I assumed that i would need x86_64 as a build target. Like i mentioned before the make command i am using is make bin-x86_64-pcbios/optionrom.rom. I have even tried with mrom the same problem occurs.
Have you tried a .usb build first and that boots ok on the same hardware?
No. i have not tried this yet. But when i built the x86_64-efi.optionrom.efirom that works just fine in the EFI mode. I am trying to build the optionrom for legacy mode boot and i am not sure what i am doing wrong.

One thing i did have to build my mrom/rom images was to do -fno-pie as without it my ipxe wwasnt even compiling.
So "\nInstallation failed - cannot continue\n" comes from
https://git.ipxe.org/ipxe.git/blob/3946a...fix.S#l993
Which was introduced in https://git.ipxe.org/ipxe.git/commitdiff...927eedfbf4 which might give a few hints on what to check next.

***NiKiZe*** · 2019-01-21, 09:31

(2019-01-21 08:39)rahuls551 Wrote:
(2019-01-21 06:19)NiKiZe Wrote: What is the _exact_ error message you get, full message, case sensitive!
It says:
iPXE(PCI XX:XX:XX) starting execution...00000000 FA000000 0000AA55
Installation failed...cannot continue.

What are you actually building?
I am actually trying to build an option rom that will work for the legacy boot.

Still not telling us what you are actually building

(2019-01-21 08:39)rahuls551 Wrote:
(2019-01-21 06:19)NiKiZe Wrote: Where are you uploading the ROM?
I am flashing it on the hardware

And which hardware is that?, the nic you are running on, what nic is that?

(2019-01-21 08:39)rahuls551 Wrote:
(2019-01-21 06:19)NiKiZe Wrote: Have you tried with normal 32bit builds?
I have not tried that yet. I assumed that i would need x86_64 as a build target. Like i mentioned before the make command i am using is make bin-x86_64-pcbios/optionrom.rom. I have even tried with mrom the same problem occurs.

Don't use 64bit pcbios builds unless you have to and understand why you have to.

(2019-01-21 08:39)rahuls551 Wrote:
(2019-01-21 06:19)NiKiZe Wrote: Have you tried a .usb build first and that boots ok on the same hardware?
No. i have not tried this yet. But when i built the x86_64-efi.optionrom.efirom that works just fine in the EFI mode. I am trying to build the optionrom for legacy mode boot and i am not sure what i am doing wrong.

Before burning anything - always be sure it works without possibly destroying hardware by flashing it, it's simple enough to test with USB.

(2019-01-21 08:39)rahuls551 Wrote: One thing i did have to build my mrom/rom images was to do -fno-pie as without it my ipxe wwasnt even compiling.

So you where not telling us this why?
And why are you not including the error message of that build?!?!?!?

rahuls551 · 2019-01-21, 17:00

(2019-01-21 09:31)NiKiZe Wrote:
(2019-01-21 08:39)rahuls551 Wrote:
(2019-01-21 06:19)NiKiZe Wrote: What is the _exact_ error message you get, full message, case sensitive!
It says:
iPXE(PCI XX:XX:XX) starting execution...00000000 FA000000 0000AA55
Installation failed...cannot continue.

What are you actually building?
I am actually trying to build an option rom that will work for the legacy boot.
Still not telling us what you are actually building

(2019-01-21 08:39)rahuls551 Wrote:
(2019-01-21 06:19)NiKiZe Wrote: Where are you uploading the ROM?
I am flashing it on the hardware
And which hardware is that?, the nic you are running on, what nic is that?

(2019-01-21 08:39)rahuls551 Wrote:
(2019-01-21 06:19)NiKiZe Wrote: Have you tried with normal 32bit builds?
I have not tried that yet. I assumed that i would need x86_64 as a build target. Like i mentioned before the make command i am using is make bin-x86_64-pcbios/optionrom.rom. I have even tried with mrom the same problem occurs.
Don't use 64bit pcbios builds unless you have to and understand why you have to.

(2019-01-21 08:39)rahuls551 Wrote:
(2019-01-21 06:19)NiKiZe Wrote: Have you tried a .usb build first and that boots ok on the same hardware?
No but the same hardware and UEFI build and boot works just fine.
No. i have not tried this yet. But when i built the x86_64-efi.optionrom.efirom that works just fine in the EFI mode. I am trying to build the optionrom for legacy mode boot and i am not sure what i am doing wrong.
Before burning anything - always be sure it works without possibly destroying hardware by flashing it, it's simple enough to test with USB.

I will try this and let you know.

(2019-01-21 08:39)rahuls551 Wrote: One thing i did have to build my mrom/rom images was to do -fno-pie as without it my ipxe wwasnt even compiling.
So you where not telling us this why?
And why are you not including the error message of that build?!?!?!?

The build error i am getting with removing -fno-pie is :
[PARSEROM]
[DEPS] arch/x86/drivers/net/undiisr.S
cc1: error: code model kernel does not support PIC mode
[DEPS] arch/x86/transitions/libkir.S
cc1: error: code model kernel does not support PIC mode
[DEPS] arch/x86/transitions/libpm.S
cc1: error: code model kernel does not support PIC mode
[DEPS] arch/x86/transitions/liba20.S
cc1: error: code model kernel does not support PIC mode
[DEPS] arch/x86/transitions/librm.S
cc1: error: code model kernel does not support PIC mode
[DEPS] arch/x86/prefix/libprefix.S

I am testing this on a Cisco UCS server so i assumed that i need the bin-x86_64-pcbios builds. Please correct me if i am wrong.

***NiKiZe*** · 2019-01-21, 18:05

(2019-01-21 17:00)rahuls551 Wrote: I am testing this on a Cisco UCS server so i assumed that i need the bin-x86_64-pcbios builds. Please correct me if i am wrong.

I will repeat myself from before:

(2019-01-21 09:31)NiKiZe Wrote: Don't use 64bit pcbios builds unless you have to and understand why you have to.

Unless you really have to - don't!
That means if you have not tried yet, do try! Wink

And even if that dosn't work you should still be able to explain why you need 64-bit builds for pcbios before using them - without any assumptions.

rahuls551 · 2019-01-21, 19:36

(2019-01-21 18:05)NiKiZe Wrote:
(2019-01-21 17:00)rahuls551 Wrote: I am testing this on a Cisco UCS server so i assumed that i need the bin-x86_64-pcbios builds. Please correct me if i am wrong.

I will repeat myself from before:

(2019-01-21 09:31)NiKiZe Wrote: Don't use 64bit pcbios builds unless you have to and understand why you have to.

Unless you really have to - don't!
That means if you have not tried yet, do try!
And even if that dosn't work you should still be able to explain why you need 64-bit builds for pcbios before using them - without any assumptions.

I am hitting the same issue with the 32bit build also. In this case even though i have enabled DEBUG messages i dont even see the Installation failed message.

***NiKiZe*** · 2019-01-21, 19:40

So it sounds you are using a build environment that is broken/not supported
If you have added -no-pie yeah I would expect any iPXE binaries created with that to be totally broken.

rahuls551 · 2019-01-21, 19:46

(2019-01-21 19:40)NiKiZe Wrote: So it sounds you are using a build environment that is broken/not supported
If you have added -no-pie yeah I would expect any iPXE binaries created with that to be totally broken.

No i removed the -no-pie stuff. I only required it for the bin-x86_64-pcbios build for the bin build it is not required.