Sponsored Content
Full Discussion: EFI on BSDs problem
Special Forums Hardware Boot Loaders EFI on BSDs problem Post 302462759 by Blackbird on Friday 15th of October 2010 01:53:38 AM
Old 10-15-2010
Yes, I will go for that later on.

I'm using amd64, first I'd want to install FreeBSD 8.1.
It seems the easiest version would be to install it first on an usual USB stick and then make a manual install to the GPT disk, wouldn't it?
 

7 More Discussions You Might Find Interesting

1. 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

2. Solaris

EFI Disk labels on 3510 raid array

Hi Peeps, Can anyone help me an EFI lablel on a 3510 raid array that I cannot get rid of, format -e and label just asks you if you want to label it. Want an SMI label writing to it. Anyone got any ideas on how to remove the EFI label? Thanks in advance Martin (2 Replies)
Discussion started by: callmebob
2 Replies

3. Solaris

Installing using ZFS - need to remove EFI disk labels

What is the preferred way of doing this from a bare metal install? (3 Replies)
Discussion started by: LittleLebowski
3 Replies

4. HP-UX

Map EFI Internal Bootable DVD

Hi, I try to get hands on my new RX2600 HP Servers. For the cold installation of the HP-UX OS the mapping to the Internal Bootable DVD is gone in the EFI Shell. ON one of my two HP RX2600 Servers the entry stays there: EFI Boot Manager ver 1.10 Firmware ver 2.31 Please select a... (2 Replies)
Discussion started by: sdohn
2 Replies

5. Linux

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... (0 Replies)
Discussion started by: indus123
0 Replies

6. Solaris

Trouble creating a disk partition slice (EFI)

Hi all, I am using SPARC Solaris 11.1 with EFI labelled disks. I am new to ZFS file systems and slightly stuck when trying to create a partition (slice) on one of my LUNs. EFI labels use sectors and blocks and I am not sure how exactly it works. From here I can try and create a... (2 Replies)
Discussion started by: selectstar
2 Replies

7. What is on Your Mind?

Are the BSDs dying?

Source a quick google search making clear that this isn't really new, and if we look at our bsd Forum we see that its the only operation systems forum with the last comment dated to June last year, whereas all the others have more recent comments. One comment dated to 2014 is exactly what I... (10 Replies)
Discussion started by: dodona
10 Replies
efi(4)							     Kernel Interfaces Manual							    efi(4)

NAME
efi - Extensible Firmware Interface description DESCRIPTION
The EFI (Extensible Firmware Interface) is an interface between HP-UX and the Itanium-based platform firmware. The file system supported by the Extensible Firmware Interface is based on the FAT file system. EFI encompasses the use of FAT-32 for a system partition, and FAT-12 or FAT-16 for removable media. The system partition is required on a bootable disk for the Itanium-based platform. For a hard disk, the system partition is a contiguous grouping of sectors on the disk, where the starting sector and size are defined by the EFI partition table, which resides on the second logical block of the hard disk, and/or by the Master Boot Record (MBR), which resides on the first sector of the hard disk. For a floppy disk, a partition is defined to be the entire disk. The System Partition can contain directories, data files, and EFI Images. The EFI system firmware may search the directory of the EFI sys- tem partition, EFI volume, to find possible EFI Images that can be loaded. The HP-UX bootloader is one example of an EFI Image. HP-UX contains a set of EFI utilities: efi_fsinit(1M) Initialize an EFI volume; that is, create a header and an empty directory. efi_cp(1M) Copy files to and from an EFI volume. efi_mkdir(1M) Create directories in an EFI volume. efi_ls(1M) List the contents of an EFI volume. efi_rm(1M) Remove files from an EFI volume. efi_rmdir(1M) Remove directories from an EFI volume. The EFI utilities are the only utilities in HP-UX where the internal structure of an EFI volume is known. To the rest of HP-UX, an EFI system partition is simply a partition containing unspecified data. The EFI volume cannot be mounted to HP-UX currently. An EFI volume can be created on any HP-UX file (either regular disk file or device special file) that supports random access via lseek(2). Within an EFI volume, individual files and directories are identified by 1- to 255-character file names. File names can consist of any alphanumeric characters (A through Z, a through z, and 0 through 9) and the certain set of special characters (. $ % ' - _ @ ~ ` ! ( ) + , : ; = # & ? ^ [ ] { } space). The first character of an EFI file name can be any valid EFI characters, except the space. When comparing two EFI names, differences in the case of alphabetic characters are not significant. For example, the following file names are considered the same: If one exists, the user will not be able to create the other. The directory may be made up of multiple components, separated by slashes(/). The last directory component must be followed by a slash to separate it from the file name. There are two special directory components, (.) and (..). They represent the current directory and the parent directory as in other file systems. SEE ALSO
efi_cp(1M), efi_fsinit(1M), efi_ls(1M), efi_mkdir(1M), efi_rm(1M), efi_rmdir(1M). Itanium(R)-Based Processor Family Only efi(4)
All times are GMT -4. The time now is 11:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy