Syslinux - Oct 2014 - Will syslinux UEFI boot the RHEL7.0 kernel (3.10.0-123.el7.x86_64) ?

All,

Is syslinux 6.03 able to UEFI boot the RHEL7.0 Linux kernel? I'm trying
&
failing
to do this.

I haven't UEFI-booted RHEL7.0 kernel via syslinux before.  (But I have UEFI
pxelinux
booted Fedora 20, which is approximately RHEL7.0.)

I remember HPA mentioned that older Linux kernels required "UEFI boot
assist",
something that GRUB2 offers but syslinux does not.

And indeed, the RHEL 6.5 kernel was so old it was that way.

However, the boot/install kernel for RHEL7.0 is 3.10.0-123.el7.x86_64.

I do a UEFI boot and load my syslinux boot menu off my USB install media.
(I'm using syslinux 6.03, official binaries.)  All looks good, until I
select
my RHEL7 menu item.

LABEL oel70_x86_64
   MENU label ^OEL 7.0/64 (Std build)
   MENU DEFAULT
   MENU INDENT 3
   TEXT HELP
               Pick me!  Pick me! I'm the only choice anyway.
   ENDTEXT
   KERNEL /boot/ol/7.0/x86_64/vmlinuz
   APPEND initrd=/boot/ol/7.0/x86_64/initrd.img
inst.stage2=hd:LABEL=EFIBOOT:/stage2/squashfs.img
inst.ks=hd:LABEL=EFIBOOT:/ks.cfg inst.gpt

It loads the vmlinuz, then starts loading the initrd.img, then dies. (No
output).  And returns to the syslinux menu.

I've tried "rd.debug=1 and rescue". No additional output.

Doing BIOS boot (more correctly, "Legacy BIOS mode under UEFI"), the
kernel/vmlinuz boots fine.

Spike

On Fri, Oct 24, 2014 at 7:04 PM, Spike White <spikewhitetx at gmail.com>
wrote:
> All,
>
> Is syslinux 6.03 able to UEFI boot the RHEL7.0 Linux kernel? I'm trying
&
> failing
> to do this.
>
> I haven't UEFI-booted RHEL7.0 kernel via syslinux before.  (But I have
UEFI
> pxelinux
> booted Fedora 20, which is approximately RHEL7.0.)
>
> I remember HPA mentioned that older Linux kernels required "UEFI boot
> assist",
> something that GRUB2 offers but syslinux does not.
>
> And indeed, the RHEL 6.5 kernel was so old it was that way.
>
> However, the boot/install kernel for RHEL7.0 is 3.10.0-123.el7.x86_64.
>
> I do a UEFI boot and load my syslinux boot menu off my USB install media.
> (I'm using syslinux 6.03, official binaries.)  All looks good, until I
> select
> my RHEL7 menu item.
Did you try doing just a simple approach of eliminating the menu and
making your LABEL the default?  If you use the following just before
your LABEL and nothing more, it'd probably be your best baseline.

DEFAULT oel70_x86_64
PROMPT 1
TIMEOUT 600
> LABEL oel70_x86_64
>    MENU label ^OEL 7.0/64 (Std build)
>    MENU DEFAULT
>    MENU INDENT 3
>    TEXT HELP
>                Pick me!  Pick me! I'm the only choice anyway.
>    ENDTEXT
>    KERNEL /boot/ol/7.0/x86_64/vmlinuz
>    APPEND initrd=/boot/ol/7.0/x86_64/initrd.img
> inst.stage2=hd:LABEL=EFIBOOT:/stage2/squashfs.img
> inst.ks=hd:LABEL=EFIBOOT:/ks.cfg inst.gpt
>
> It loads the vmlinuz, then starts loading the initrd.img, then dies. (No
> output).  And returns to the syslinux menu.
>
> I've tried "rd.debug=1 and rescue". No additional output.
>
> Doing BIOS boot (more correctly, "Legacy BIOS mode under UEFI"),
the
> kernel/vmlinuz boots fine.
>
> Spike
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux


-- 
-Gene

A: Because it messes up the order in which people normally read text,
especially the archives of mailing lists.
Q: Why is Top-posting such a bad thing?

"No one ever says, 'I can't read that ASCII(plain text) e-mail you
sent me.'"

Dropped other recipients, don't need a flame war.

What's wrong with putting your opinion in your signature? Let's take a
look shall we.

"In general, an opinion is a judgment, viewpoint, or statement about
matters commonly considered to be subjective, i.e. based on that which is less
than absolutely certain, and is the result of emotion or interpretation of
facts." Wikipedia

When we issue an opinion, we nearly force someone else to consider that opinion
and it's relevancy towards anything they are doing, especially the first
time it is issued. Quite often embedded within the opinion are 'some' of
the facts that the issuer drew upon to create the opinion. The receiver may
choose to evaluate the opinion based just upon those facts, or they may wish to
gather more facts on their own before rendering their judgment on the issuers
opinion. Ultimately, however, the receiver must decide whether or not they
mostly agree with the opinion. If they do, then everything else communicated by
the issuer has more weight with regards to knowledge or situations the receiver
is less qualified to evaluate.

Now here is where things get dicey, if they do 'not' agree with the
opinion, then the issuer loses status with the receiver. Anything and everything
communicated by the issuer becomes subject to a much higher level of scrutiny.
So much so, that the receiver may choose to disregard everything communicated
just for the expediency of not having to investigate it. Things only get worse
from here, because if the opinion is re-issued, the receiver quite often takes
it as an insult to their intelligence, and insulting someone is not the way to
get things done.

I couldn't even imagine the damage to the reputation of a project that
allowed key support personnel to constantly insult would be participants and
users. Bashing people over the head with an opinion is very very offensive, and
this is exactly what happens when you put an opinion in a signature.

A better way to effect global change might be to approach the IOS.

Best Regards,
Don Cupp

What wrong with bottom and in-line posting? You always have to hunt for the new
words, which is sometimes like finding a needle in a haystack.



On Friday, October 24, 2014 6:56 PM, Gene Cumm <gene.cumm at gmail.com>
wrote:
 



On Fri, Oct 24, 2014 at 7:04 PM, Spike White <spikewhitetx at gmail.com>
wrote:
> All,
>
> Is syslinux 6.03 able to UEFI boot the RHEL7.0 Linux kernel? I'm trying
&
> failing
> to do this.
>
> I haven't UEFI-booted RHEL7.0 kernel via syslinux before.  (But I have
UEFI
> pxelinux
> booted Fedora 20, which is approximately RHEL7.0.)
>
> I remember HPA mentioned that older Linux kernels required "UEFI boot
> assist",
> something that GRUB2 offers but syslinux does not.
>
> And indeed, the RHEL 6.5 kernel was so old it was that way.
>
> However, the boot/install kernel for RHEL7.0 is 3.10.0-123.el7.x86_64.
>
> I do a UEFI boot and load my syslinux boot menu off my USB install media.
> (I'm using syslinux 6.03, official binaries.)  All looks good, until I
> select
> my RHEL7 menu item.
Did you try doing just a simple approach of eliminating the menu and
making your LABEL the default?  If you use the following just before
your LABEL and nothing more, it'd probably be your best baseline.

DEFAULT oel70_x86_64
PROMPT 1
TIMEOUT 600
> LABEL oel70_x86_64
>    MENU label ^OEL 7.0/64 (Std build)
>    MENU DEFAULT
>    MENU INDENT 3
>    TEXT HELP
>                Pick me!  Pick me! I'm the only choice anyway.
>    ENDTEXT
>    KERNEL /boot/ol/7.0/x86_64/vmlinuz
>    APPEND initrd=/boot/ol/7.0/x86_64/initrd.img
> inst.stage2=hd:LABEL=EFIBOOT:/stage2/squashfs.img
> inst.ks=hd:LABEL=EFIBOOT:/ks.cfg inst.gpt
>
> It loads the vmlinuz, then starts loading the initrd.img, then dies. (No
> output).  And returns to the syslinux menu.
>
> I've tried "rd.debug=1 and rescue". No additional output.
>
> Doing BIOS boot (more correctly, "Legacy BIOS mode under UEFI"),
the
> kernel/vmlinuz boots fine.
>
> Spike
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux


-- 
-Gene

A: Because it messes up the order in which people normally read text,
especially the archives of mailing lists.
Q: Why is Top-posting such a bad thing?

"No one ever says, 'I can't read that ASCII(plain text) e-mail you
sent me.'"
_______________________________________________
Syslinux mailing list
Submissions to Syslinux at zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux

The reply I should have sent.

On Fri, Oct 24, 2014 at 7:04 PM, Spike White <spikewhitetx at gmail.com>
wrote:
> However, the boot/install kernel for RHEL7.0 is 3.10.0-123.el7.x86_64.
>
> I do a UEFI boot and load my syslinux boot menu off my USB install media.
> (I'm using syslinux 6.03, official binaries.)  All looks good, until I
> select
> my RHEL7 menu item.
Did you try doing just a simple approach of eliminating the menu and
making your LABEL the default?  If you use the following just before
your LABEL and nothing more, it'd probably be your best baseline.

DEFAULT oel70_x86_64
PROMPT 1
TIMEOUT 600
> LABEL oel70_x86_64
>    MENU label ^OEL 7.0/64 (Std build)
>    MENU DEFAULT
>    MENU INDENT 3
>    TEXT HELP
>                Pick me!  Pick me! I'm the only choice anyway.
>    ENDTEXT
>    KERNEL /boot/ol/7.0/x86_64/vmlinuz
>    APPEND initrd=/boot/ol/7.0/x86_64/initrd.img
> inst.stage2=hd:LABEL=EFIBOOT:/stage2/squashfs.img
> inst.ks=hd:LABEL=EFIBOOT:/ks.cfg inst.gpt
>
> It loads the vmlinuz, then starts loading the initrd.img, then dies. (No
> output).  And returns to the syslinux menu.
Your output was hidden by your Syslinux configuration file setup.  Try
above to see the error.
> Doing BIOS boot (more correctly, "Legacy BIOS mode under UEFI"),
the
> kernel/vmlinuz boots fine.
Presuming this test is the same PC, that should indicate the
kernel/initrd compatibility with your hardware.

-- 
-Gene