Problem in displaying message on RHEL6 on EFI during PXE boot


 
Thread Tools Search this Thread
Operating Systems Linux Problem in displaying message on RHEL6 on EFI during PXE boot
# 1  
Old 10-04-2013
Problem in displaying message on RHEL6 on EFI during PXE boot

Hi,

I am doing PXE boot for RHEL6.4 on EFI and want to display custom messsage before loading vmlinuz and initrd.img, which is not working.


boot server side (In case of BIOS client):

In /var/lib/tftpboot/default file I am putting the message in below format:

SAY hello world

boot server side(In case of EFI client):

In /var/lib/tftpboot/efidefault file I am putting the message in below format:

SAY hello world

In case of BIOS client machine, message is being displayed successfully but in case of EFI it is not.

Please suggest any similar method for EFI as its very urgent.

Regards,
Indus
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Red Hat

dual boot RHEL5 and RHEL6

have a server pre-installed with RHEL5, with 12 SCSI disks being /dev/sda with RHEL5, and managed to put RHEL6 into /dev/sdc /dev/sda is the first bootable disk on the SCSI chain.. editing /etc/grub.conf would not allow me to boot RHEL6 , the entries seem to be right.. any advices,... (0 Replies)
Discussion started by: ppchu99
0 Replies

2. Red Hat

pxe boot server

Hi Hoping someone can help ove setup a pxe/dhcp boot server for auto installs on centos My server seems to be providing dhcp fine but the installation fails to progress when it reaches the pxe boot menu. I make my selection and nothing happens. I am serving the media via http from the same... (3 Replies)
Discussion started by: duckeggs01
3 Replies

3. Red Hat

Interactive PXE Boot Menu

I have been asked to modify our PXE server such that there will be only one entry in the pxelinux.cfg/default file, where the same kernel and initrd.img will be used regardless of what operating system is to be installed, and the user will type in the path to the kickstart file that will be used. ... (7 Replies)
Discussion started by: ceb
7 Replies

4. Solaris

PXE boot problems in Solaris 10

Hi folks, I was trying to setup Network based NFS installation with PXE. I'm using virtual box for this purpose. I have one redhat (DHCP) server and Solaris 10 (Install server - Source) and on the other one am trying to install solaris using PXE. As in, dhcp address and boot file can be fetched... (2 Replies)
Discussion started by: vijaytrendz
2 Replies

5. Boot Loaders

PXE boot not taking the init= option

Hi Experts, I am doing PXE boot for my GNU/Linux device and pxelinux.0 loads the kernel as well as initrd images I have mentioned in the config file but it looks like it is not considering the init= option. Instead it starts the default INIT program. I wanted my customized init program to be... (3 Replies)
Discussion started by: learn more
3 Replies

6. UNIX for Advanced & Expert Users

PXE diskless boot fails

Hi, I am trying to setup a server for a diskless boot of a computer class (with ubuntu) I followed the guidelines in https://help.ubuntu.com/community/DisklessUbuntuHowto I have two computers: one is the server I installed and the other is my macbook on which I run a virtual machine... (8 Replies)
Discussion started by: yotamhc
8 Replies

7. UNIX for Advanced & Expert Users

Setting up a PXE Boot Server

I've set up a PXE boot server and I'm having a slight snag in the booting process. On the client machine, DHCP renders fine and TFTP seems to begin but then the system hangs. On the server, the error message "Client does not accept options" occurs -- which from reading online is a common message... (2 Replies)
Discussion started by: Colton
2 Replies

8. HP-UX

How to add Boot path for ALUA lun in EFI?

Hi All, I am trying to make a Boot from San setup on 11.31 IA64 (rx2660). The San array I am using is EMC Clariion with failover mode ALUA. Now, My setup is ready and I am able to boot my host from the Lun. I have 4 paths to my Lun from my host. Question is how do I add the entries in EFI... (0 Replies)
Discussion started by: barun agarwal
0 Replies

9. UNIX for Dummies Questions & Answers

what is PXE boot bare-metal

hi members i am reading RHEL and i am unable to under stand about PXE boot and bare metal (1 Reply)
Discussion started by: wagmare
1 Replies

10. HP-UX

PXE boot port issue

Hi,all: I want to boot an IA unix box from network, I am sure I set the DHCP and boot server, but it still failed ! It says : Client MAC Address: 00 18 FE 28 91 82 .....- PXE-E16: Valid PXE offer not received. Load of Core LAN Gb A failed: Not Found I use the nettl command to trace the UDP... (0 Replies)
Discussion started by: bluepluto
0 Replies
Login or Register to Ask a Question
BOOTCTL(1)							      bootctl								BOOTCTL(1)

NAME
bootctl - Control the firmware and boot manager settings SYNOPSIS
bootctl [OPTIONS...] status bootctl [OPTIONS...] list bootctl [OPTIONS...] update bootctl [OPTIONS...] install bootctl [OPTIONS...] remove DESCRIPTION
bootctl checks, updates, installs or removes the boot loader from the current system. bootctl status checks and prints the currently installed versions of the boot loader binaries and all current EFI boot variables. bootctl list displays all configured boot loader entries. bootctl update updates all installed versions of systemd-boot, if the current version is newer than the version installed in the EFI system partition. This also includes the EFI default/fallback loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is created if there is no current entry. The created entry will be added to the end of the boot order list. bootctl install installs systemd-boot into the EFI system partition. A copy of systemd-boot will be stored as the EFI default/fallback loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is created and added to the top of the boot order list. bootctl remove removes all installed versions of systemd-boot from the EFI system partition, and removes systemd-boot from the EFI boot variables. If no command is passed, status is implied. OPTIONS
The following options are understood: -h, --help Print a short help text and exit. --version Print a short version string and exit. --path= Path to the EFI System Partition (ESP). If not specified, /efi, /boot, and /boot/efi are checked in turn. It is recommended to mount the ESP to /boot, if possible. -p, --print-path This option modifies the behaviour of status. Just print the path to the EFI System Partition (ESP) to standard output and exit. --no-variables Do not touch the EFI boot variables. EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise. SEE ALSO
Boot loader specification[1] systemd boot loader interface[2] NOTES
1. Boot loader specification https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec 2. systemd boot loader interface https://www.freedesktop.org/wiki/Software/systemd/BootLoaderInterface systemd 237 BOOTCTL(1)