similar to: Centos 6.5 problems with UEFI PXE and GRUB

Ok, so some of this now works, but I'm still having problems. With the bootif option, the system now correctly configures and uses the same interface to get its kickstart file. However, when the system is done and boots up, the interfaces are still messed up. So this is what I have in the kickstart file: # On-Board Port 1 with public IP configuration network --noipv6 --onboot yes --bootproto

Thanks for that Jason but it didn't solve the problem. The system is still coming up with the interfaces shuffled. It seems to *always* want to use the added ethernet card as eth0. On Wed, Feb 25, 2015 at 1:37 PM, Jason Warr <jason at warr.net> wrote: > Starting back in RHEL/Cent 5 I found that the only way to make sure your > interface enumeration was consistent after install

I am getting the following error with memdisk when attempting to boot. I am booting UEFI device using elilo.efi and loading a elilo.conf file with below configuration. Attached is also a print sceen of the error I am getting about memdisk. # force chooser to textmenu chooser=textmenu delay=20 prompt # # the files containing the text (with attributes) to display # message=textmenu-message.msg

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/15 08:16 PM, Steven Tardy wrote: > >> On Feb 23, 2015, at 6:34 PM, Ashley M. Kirchner >> <ashley at pcraft.com> wrote: >> >> I have a Dell server that has two built-in ethernet devices. When >> I kickstart the machine, they are correctly identified as eth0 >> and eth1 (correctly meaning they

Hi, In a corporate environment we are not allowed to use DHCP/PXE for doing network installations. This means we have to look for other solutions. Our solution is to use an ISO image (mounted via a KVM solution) to kick off the network installation. A big problem currently is that the order of the network interfaces is arbitrary (depends on the order of the drivers loaded) and is not

Starting back in RHEL/Cent 5 I found that the only way to make sure your interface enumeration was consistent after install with what you had during install was to create a udev rules file using the mac addresses as the key. It is easy to run a short script in postinstall to create it based on how anaconda has seen them. In order for this to work on Cent 6 you have to set biosdevname=0

<overly trimmed> On 02/25/2015 01:56 PM, Ashley M. Kirchner wrote: > Ok, so some of this now works, but I'm still having problems. With the > bootif option, the system now correctly configures and uses the same > interface to get its kickstart file. However, when the system is done and > boots up, the interfaces are still messed up. So this is what I have in the >

Ok, when I run that, it creates a now "custom" 70-persistent-net.rules, but the interfaces are still out of order, with the added one listed first, and the built-ins 2nd and 3rd. On Wed, Feb 25, 2015 at 2:00 PM, Jason Warr <jason at warr.net> wrote: > Here is my script for post install if you want to try it. > > In order for the shuffling to not occur you do need to

Version 6.6 ... On Wed, Feb 25, 2015 at 1:17 PM, Jim Perrin <jperrin at centos.org> wrote: > <overly trimmed> > > On 02/25/2015 01:56 PM, Ashley M. Kirchner wrote: > > Ok, so some of this now works, but I'm still having problems. With the > > bootif option, the system now correctly configures and uses the same > > interface to get its kickstart file.

Out of order meaning, it puts the additional ethernet card as eth0, with the built-in ports as eth1 and eth2 respectively. WITHOUT the additional card installed, it puts the built-in ports as eth0 and eth1, which is what I want it to do. The additional card should be eth2, at least that's what I want it to do. Looking at persistent-net.rules, it always puts the additional card first, both

Hi all, First time here, so please be gentle! :) I'm trying to configure a system that will pxeboot and retrieve a kickstart file from a server based on that host's macaddress as part of my Edison project[0] however I'm having issues getting the dns lookup to work and I'm hoping you can help! My pxelinux.cfg/default file is as follows: ======================= default linux

Here is my script for post install if you want to try it. In order for the shuffling to not occur you do need to create the udev rules file somehow. I am not sure how mangled this will be in email but it is worth a try. It should run OK with nothing else. I have a better version in the works but the enhancements are mainly useful for Fedora 19-21. I did forget to say I also block

All, I'm having an issue with my menu.c32. I created a menu and it appears correctly, but once I get to my choice, it won't select it and begin the install. Below is my pxelinux.cfg/default: default menu.c32 timeout 600 display boot.msg menu title Welcome to the incNETWORKS RHEL5/6 PXEBOOT Server! menu color border 0 #ffffffff #00000000 menu color sel 7 #ffffffff #ff000000 menu color

On Wed, 25 Feb 2015 16:45:04 -0600, Ashley M. Kirchner <ashley at pcraft.com> wrote: > Out of order meaning, it puts the additional ethernet card as eth0, with > the built-in ports as eth1 and eth2 respectively. WITHOUT the additional > card >installed, it puts the built-in ports as eth0 and eth1, which is > what I want it to do. The additional card should be eth2, at

Once upon a time, isdtor <isdtor at gmail.com> said: > We have a working PXE setup. I've tried to adapt it to UEFI as per > RHEL6 manual, but the client won't boot. I have BIOS+UEFI PXE boot set up, although it took some doing. I still use SYSLINUX for BIOS, but GRUB2 plus Red Hat's secure boot shim for UEFI. I never could get SYSLINUX's UEFI support working very

Greetings all, Is there currently any mechanism in pxelinux the would send a mac address of the pxe booted interface through to the linux kernel much like ipappend can send the ip address? Kickstarting a system with multiple interfaces can be troublesome. ksdevice is helpful but only in some circumstances such as forcing eth0, but that doesn't always work since probe order changes depending

Hi I am running a pxe diskless node in f13 and I have some proposals to make ovirt-early working in this version. nash is no more available (nash/mkinitrd is replaced by dracut), so this following command fails : "echo "network --device $DEVICE --bootproto dhcp" | nash" it makes the network configuration incomplete. I replace the linuxrc command by dhclient and it's

Define out of order in this case just so I know for sure what you mean. What my solution does, or at least does reliably in my case, is make sure the interfaces are in the same order once installed as the install kernel saw them. It won't re-order them to be sequential based on bus, mac or driver. I am working on that but it will also include naming the devices based on the module

On Wed, Dec 11, 2013 at 9:22 PM, ?? <kun.he at cs2c.com.cn> wrote: > When we meet UEFI or EFI firmware, lots of linux os release use > GRUB bootloader. But I wanna use isolinux to boot the installation > environment and also the linux os installed. Some question puzzled me. Now, > I look for your help: > > 1. I didn't found information about how to use >

> On Feb 23, 2015, at 6:34 PM, Ashley M. Kirchner <ashley at pcraft.com> wrote: > > I have a Dell server that has two built-in ethernet devices. When I > kickstart the machine, they are correctly identified as eth0 and eth1 > (correctly meaning they correspond to the physical device ports 1 and 2). I > need a third one and want that to come up as eth2. After adding the