Plan 9: Quick Boot with UEFI

 UEFI (Unified Extensible Firmware Interface) provides a quick way to set up a Plan 9 terminal on modern hardware. EFI System Partition (ESP) is a FAT32 partition. You should be able to modify it in most of the operating systems.


  

Run mk in \sys\src\boot\efi. aux/aout2efi converts an a.out file to an EFI executable. Copy over the files bootx64.efi, 9pc64, plan9.ini (for x86_64 hardware) to \EFI\plan9\ directory in the ESP. If you want it be the default OS, you can create a symlink \EFI\boot to \EFI\plan9. Remember to include the full path to the kernel in plan9.ini.

bootfile=\EFI\plan9\9pc64 
   

When bootx64.efi fails to find the bootfile (e.g. kernel is missing, plan9.ini is missing or path is incorrect), you can provide the arguments at > prompt followed by a boot command.

You can use EFI shell or efibootmgr on Linux to modify the EFI entries that are displayed during boot.

 

Test in QEMU

Before running on actual hardware, it might help to get familiar with the process in a virtual environment. OVMF, or Open Virtual Machine Firmware, is an open-source implementation of the UEFI (Unified Extensible Firmware Interface) specification for virtual machines. Install QEMU and OVMF.
sudo apt-get install qemu-system ovmf

Copy all the files mentioned above to a root dir maintaining the directory structure. Also copy OVMF.fd to the current dir.
cp /usr/share/qemu/OVMF.fd .

Then run QEMU using the following:
qemu-system-x86_64 -drive if=pflash,format=raw,file=OVMF.fd -drive format=raw,file=fat:rw:root
 

Manage boot configuration with efibootmgr

Use efibootmgr to manage the EFI boot configuration. Linux mounts the ESP at /boot/efi.

efibootmgr -c -d /dev/sda -p 7 -L "Plan 9" -l EFI/plan9/bootx64.efi

 

EFI Shell

EFI Shell follows DOS conventions - it is case insensitive and uses backslash (\) for directory separator. 
List attached devices:
map
 
Boot an EFI application on FS0:
FS0:
EFI\plan9\bootx64.efi 
 
Add Plan 9 as the first (zero based index) boot option.
bcfg boot add 0 FS0:\EFI\plan9\bootx64.efi "Plan 9"
 

Programming

Print a CHAR16 string txt:
eficall(ST->ConOut->OutputString, ST->ConOut, txt);   
 

Image file path:

typedef struct {
  void *ConvertDeviceNodeToText;
  void *ConvertDevicePathToText;
} EFI_DEVICE_PATH_TO_TEXT_PROTOCOL;

static EFI_GUID EFI_DEVICE_PATH_TO_TEXT_PROTOCOL_GUID = {
  0x8b843e20,0x8132,0x4852,
  {0x90,0xcc,0x55,0x1a,0x4e,0x4a,0x7f,0x1c}
};


EFI_DEVICE_PATH_TO_TEXT_PROTOCOL *dpt;
CHAR16 *txt;
eficall(ST->BootServices->LocateProtocol, &EFI_DEVICE_PATH_TO_TEXT_PROTOCOL_GUID, nil, &dpt);
txt = (CHAR16*) eficall(dpt->ConvertDevicePathToText, image->FilePath, 1, 1);
   

  

Lessons Learnt

  • Always backup ESP especially if you need Windows. It's almost impossible to get bootmgr.efi for Windows from external sources. (Boot manager: \EFI\Microsoft\Boot\bootmgfw.efi , OS loader: \windows\system32\windload.efi) 
  • Depending on your configuration in Linux, you might have a copy of the ESP at /boot/efi.

 

References


Comments

Post a Comment

Popular posts from this blog

Plan 9 : The Infinity Notebook

Image
  Plan 9 is an Operating System (OS) from Bell Labs which is a successor to UNIX. It builds on the learnings from the previous Operating systems. Network computing and graphics is an integral part of the OS rather than an afterthought. It is modular and portable - it comes with a cross compiler . It is available, under MIT License , which anybody can use, learn and tweak. Features Everything is a file. Singular Grid: All the computers running Plan 9 OS and connected together act like a singular grid. So there's no need for remote access solutions like VNC or RDP. This cool video shows a small glimpse of the possibilities. Process Isolation: Processes run within their own namespaces and are isolated from each other. So you can run rio (the window manager) within rio. Applications like Browsers don't need complicated sandboxing. And a crashing program is unlikely to bring down the OS. No DLL Hell : Binaries are always statically linked. So there's no DLL hell and there...
Read more

Emacs: Binary File Viewer

Image
  Quick visualization tool for Binary data using C header definition. Semantic parses the C header file and generates a type definition. The type definition is passed to bindat-unpack along with the binary data. The result is displayed using speedbar . ;; Note: The command works on the binary data in the current buffer.   M-x hexl-form   (hexl-form)      The image shows the example included in the commentary section of bindat.el .   Conversions (format "%02X" 255) ;; => "FF" (string-to-number "FF" 16) ;; => 255   ;; Little endian unpacking (let* ((bindat-raw [1 2 3 4 5 6 7 8])           (bindat-idx 0))   (bindat--unpack-u64r))   ;; Little endian packing (let* ((bindat-raw [0 0 0 0 0 0 0 0])           (bindat-idx 0))   (bindat--pack-u64r #x0102030405060708)   bindat-raw)      Insert Binary Data Emacs creates a multibyte buffer ...
Read more

Emacs: A non-intrusive browser

Image
  Web is simple. Browser can be simpler.     Features No pop-up ads Content first (CSS and images are loaded asynchronously) No beacon or marketing pixel ( zero pixel) image tracking Split panes Fully customizable (custom theme using CSS) Fully extensible (write your plugins/extensions) Easy cookie mangement   The technical details are here .  
Read more