<p dir="ltr">I'm using CentOS 7.1 on a Dell PowerEdge R630. I hadn't bothered with UEFI on any of our older servers, but this one has a RAID array larger than 2TB (i.e. so big that I have to use GPT). In order to continue using BIOS, I would need to install a BIOS Boot partition, which I haven't found a way to specify in a kickstart file (and I don't want to auto-partition my servers or install the OS manually). Which makes this whole thing a weird sort of "chicken-and-egg" problem.</p>
<p dir="ltr">I did find that CentOS 6 works on the same hardware, in BIOS mode but without any BIOS Boot partition. Maybe the older version of Grub is small enough that it doesn't need a special boot partition?</p>
<br><div class="gmail_quote"><div dir="ltr">On Wed, Sep 23, 2015, 9:57 AM Omar Eljumaily <<a href="mailto:omar@omnicode.com">omar@omnicode.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Which version of Centos are you using? UEFI seems to be well
supported in 7, but marginally in other versions.<br>
<br>
<a href="https://wiki.centos.org/HowTos/UEFI" target="_blank">https://wiki.centos.org/HowTos/UEFI</a><br>
<br>
Booting seems to be getting harder and harder these days. I got a
very popular MB from Amazon and had big problems with a fresh
install of the latest Ubuntu LTS. <br>
<br>
Also switching from one motherboard to another used to be very
straightforward, and now it's very tricky. I always thought it was
a benefit of Linux. When Windows got temperamental about switching
Mobos, Linux wouldn't. But now that seems to have changed, at least
for the technology, but not DRM.<br>
<br>
Omar</div><div bgcolor="#FFFFFF" text="#000000"><br>
<br>
On 9/23/2015 9:47 AM, Lincoln Peters wrote:<br>
</div><div bgcolor="#FFFFFF" text="#000000"><blockquote type="cite">
<p dir="ltr">I have a new server that can boot in a legacy BIOS
mode or a UEFI mode. On a server using BIOS, I can boot from a
RHEL or CentOS CD or DVD and direct it to use a kickstart file
by adding something like this to the Grub command line:</p>
<p dir="ltr">ks=<a href="http://other.server/ks.cfg" target="_blank">http://other.server/ks.cfg</a></p>
<p dir="ltr">However, when I switch to UEFI mode and boot from a
CentOS DVD, I can edit the boot parameters, but the format is
very different. Most notably, the configuration is split across
multiple lines. I can find documentation that describes the new
format, but none of it mentions kickstarts.</p>
<p dir="ltr">I've tried adding the "ks=..." to the end of the line
that specifies the kernel, but that caused a syntax error. I
then tried specifying it using the "set" and "setparams"
commands. Neither had any effect.</p>
<p dir="ltr">Is there something else that I should be trying?</p>
<p dir="ltr">Thanks in advance.</p>
<br>
<fieldset></fieldset>
<br>
</blockquote></div><div bgcolor="#FFFFFF" text="#000000"><blockquote type="cite"><pre>_______________________________________________
talk mailing list
<a href="mailto:talk@nblug.org" target="_blank">talk@nblug.org</a>
<a href="http://nblug.org/cgi-bin/mailman/listinfo/talk" target="_blank">http://nblug.org/cgi-bin/mailman/listinfo/talk</a>
</pre>
</blockquote>
<br>
</div>
_______________________________________________<br>
talk mailing list<br>
<a href="mailto:talk@nblug.org" target="_blank">talk@nblug.org</a><br>
<a href="http://nblug.org/cgi-bin/mailman/listinfo/talk" rel="noreferrer" target="_blank">http://nblug.org/cgi-bin/mailman/listinfo/talk</a><br>
</blockquote></div>