Difference between pages "Weechat" and "UEFI Install Guide"

From Funtoo
(Difference between pages)
Jump to: navigation, search
 
 
Line 1: Line 1:
== Introduction ==
+
This tutorial will show you how to install Funtoo on a UEFI system. UEFI, also known as the [[Wikipedia:Unified Extensible Firmware Interface|Unified Extensible Firmware Interface]], is a new firmware interface that is used on some newer computers as a replacement for the traditional PC BIOS. It has an integrated boot loader, so setting up booting is different.
WeeChat is a terminal based chat client. It can be scripted with Python, Perl, Ruby, Lua, C, Tcl, and Scheme.  
+
  
== More Information ==
+
This tutorial is meant to be an "overlay" over the Regular Funtoo Installation. Follow the normal installation and only follow steps in this tutorial when dealing with partitioning and configuring the boot loader (GRUB). All steps are otherwise identical to the regular installation process.
[http://www.weechat.org/files/doc/stable/weechat_user.en.html User's Guide]
+
  
[http://www.weechat.org/scripts/ Plugins]
+
== What Are We Doing? ==
  
== Installation ==
+
This guide will show you how to set up your UEFI system to load the GRUB boot loader, which will then load your Funtoo Linux kernel and initramfs. This is the "UEFI + GRUB" method as described on the [[Boot Methods]] page.
 +
 
 +
== First Steps ==
 +
 
 +
To install Funtoo Linux on a UEFI system, first you need to boot SysRescueCD in UEFI mode. To do this, enable UEFI in your BIOS, and if necessary disable legacy booting. After some fiddling, you should be able to boot SysRescueCD and get a black and white text menu instead of the traditional aqua/cyan-colored menu. The black and white menu indicates that you booted SysRescueCD in UEFI mode. Once you've accomplished this, you're ready to continue with your Funtoo Linux installation and partition your drive. See below for details.
 +
 
 +
== Partitioning ==
 +
 
 +
To set up your partitions for UEFI booting, you will create a ~500MB FAT32 partition on <tt>/dev/sda1</tt>, and set it to type <tt>EF00</tt> using <tt>gdisk</tt>.
  
 
<console>
 
<console>
###i## emerge weechat
+
Command: ##i##n ↵
 +
Partition Number: ##i##1 ↵
 +
First sector: ##i##↵
 +
Last sector: ##i##+500M ↵
 +
Hex Code: ##i##EF00
 
</console>
 
</console>
{{Fancynote|If you are going to use plugins, make sure to add the USE flags corresponding to the language of the plugins you wish to use.}}
 
  
== Configuration ==
+
This partition will serve as your Funtoo <tt>/boot</tt> filesystem as well as the partition that the UEFI firmware can read to load GRUB. Then you will set up swap on <tt>/dev/sda2</tt> and your root filesystem on <tt>/dev/sda3</tt>. To create the FAT32 filesystem, type:
  
Configuration can be done in three ways.
+
<console>
* '''iset''': A script used within WeeChat
+
# ##i##mkfs.vfat -F 32 /dev/sda1
* '''/set''' and '''/window''': Using input commands to change options within WeeChat
+
</console>
* '''.conf''': Using the .conf files that are in ~/.weechat.
+
 
 +
Your <tt>/etc/fstab</tt> entry for this filesystem will also differ, and will look like this:
 +
 
 +
<pre>
 +
/dev/sda1 /boot vfat noatime 1 2
 +
</pre>
 +
 
 +
Make sure you add VFAT support to your kernel if you are building it manually.
 +
 
 +
== Boot Loader ==
 +
 
 +
=== Emerging GRUB ===
 +
 
 +
You will still use GRUB as a boot loader, but before emerging grub, you will need to enable EFI booting. To do this,
 +
add the following line to <tt>/etc/portage/make.conf</tt>:
 +
 
 +
<pre>
 +
GRUB_PLATFORMS="efi-64"
 +
</pre>
 +
 
 +
Then, <tt>emerge grub</tt>. You will notice <tt>efibootmgr</tt> getting pulled in as a dependency. This is expected and good.
 +
 
 +
=== Installing GRUB ===
 +
 
 +
Now, for the magic of getting everything in place for booting. You should copy your kernel and initramfs (if you have one -- you will if you are following the default install) to <tt>/boot</tt>. GRUB will boot those. But how do we get UEFI to boot GRUB? Well, we need to run the following command:
 +
 
 +
<console>
 +
# ##i##grub-install --target=x86_64-efi --efi-directory=/boot /dev/sda
 +
</console>
 +
This command will simply install all the stuff to <tt>/boot/EFI</tt> and <tt>/boot/grub</tt> that your system needs to boot. In particular, the <tt>/boot/EFI/grub/grubx64.efi</tt> file will be created. This is the GRUB boot image that UEFI will load and start.
 +
=== Configuring GRUB ===
  
For the sake of this wiki, the '''/set''' and '''/window''' commands will be used for configuration.
+
OK, now UEFI has the GRUB image it needs to boot. But we still need to configure GRUB itself so it finds and boots your kernel and initramfs. This is done by performing the following steps.
=== Windows ===
+
This is just an example of how windows can be split. If a user wants 24 windows, that is possible.
+
The percentage used is relative to the current window being split:
+
<pre style="color:green">/window splith 20</pre>
+
This gives you a horizontal split at 20% on the top and 80% on the bottom
+
<pre style="color:green">/window 1</pre>
+
<pre style="color:green">/window splitv 50</pre>
+
This will split the bottom screen into two horizontal windows.
+
<pre style="color:green">/window 2</pre>
+
<pre style="color:green">/window splitv 50</pre>
+
This will split the top screen into two horizontal windows.
+
  
The window will now be broken into 4 sections dependent upon the percentage used during the splits.
+
First, let's copy <tt>/usr/share/grub/fonts/unifont.pf2</tt> to <tt>/boot/grub/font.pf2</tt>. This is the bitmap font that we'll tell GRUB to use for the GRUB boot menu.
  
{| border="1"
+
Next, since boot-update doesn't yet support UEFI, we will not use boot-update directly and will create a <tt>/boot/grub/grub.cfg</tt> file manually that looks like this:
| Window 2
+
| Window 4
+
|-
+
| Window 1
+
| Window 3
+
|}
+
=== Bars ===
+
Use the /bar command to manipulate bars.
+
  
To list current bars:
+
<pre>
<pre style="color:green">/bar</pre>
+
set timeout=3
For example, to add a root inputbar:
+
# Display settings
<pre style="color:green">/bar add rootinput root bottom 1 0 [buffer_name]+[input_prompt],input_text</pre>
+
if loadfont /grub/font.pf2 ; then
<pre style="color:green">/set weechat.bar.rootinput.color_bg black</pre>
+
    set gfxmode=auto
<pre style="color:green">/bar del input</pre>
+
    insmod efi_gop
 +
    insmod efi_uga
 +
    insmod gfxterm       
 +
    terminal_output gfxterm
 +
fi
  
Check the user guide for more configurations and bar types.  
+
menuentry "Funtoo Linux genkernel - kernel-debian-sources-x86_64-3.2.35-2" { 
 +
    insmod part_gpt
 +
    insmod fat 
 +
    set root=(hostdisk//dev/sda,gpt1) 
 +
    search --no-floppy --fs-uuid --set __REPLACE_UUID_OF_SDA1__
 +
    linux /kernel-debian-sources-x86_64-3.2.35-2 real_root=/dev/sda3
 +
    initrd /initramfs-debian-sources-x86_64-3.2.35-2 
 +
    set gfxpayload=keep
 +
}
 +
set default=0
 +
</pre>
  
=== Scripts ===
+
Note the <tt>search</tt> line where it says <tt>__REPLACE_UUID_OF_SDA1__</tt> above. You will need to run <tt>blkid /dev/sda1</tt> and use the UUID value that is displayed. For example, on my system, I need to use <tt>C34B-19CF</tt>. You can also change the <tt>menuentry</tt> line text in quotes to say whatever you want, and the <tt>linux</tt> and <tt>initrd</tt> lines should reference your kernel versions in <tt>/boot</tt>. As above, use the path <tt>/</tt> instead of <tt>/boot</tt> as the path should be relative to the root of the VFAT filesystem.
Use the /script command to go to the script list.
+
  
To install a script:
+
== Known Issues ==
<pre style="color:green">/script install <name of script></pre>
+
With pure UEFI boot mode, with legacy mode disabled, following error expected:  
or
+
* video driver not supported, boot hangs, hard reboot required.
using the keybinds of the script buffer, Alt+i to install.
+
Choose UEFI first, next legacy driver. It depends on motherboard vendor and efi bios version.
 +
In UEFI bios choose grub option, if your succeeded with above guide, additional menu should appear in Boot Menu, otherwise it boots into EFI shell:
 +
* grub:NAME of you hard drive
  
The title screen has more information on the keybinds/commands that are available.
+
=== Done! ===
  
[[Category:IRC]]
+
Remember to follow all other steps in the regular Funtoo Install Guide. Assuming you did everything correctly, your system should now boot via UEFI! We will be adding UEFI support to boot-update soon to make this process easier.

Revision as of 14:48, 7 July 2013

This tutorial will show you how to install Funtoo on a UEFI system. UEFI, also known as the Unified Extensible Firmware Interface, is a new firmware interface that is used on some newer computers as a replacement for the traditional PC BIOS. It has an integrated boot loader, so setting up booting is different.

This tutorial is meant to be an "overlay" over the Regular Funtoo Installation. Follow the normal installation and only follow steps in this tutorial when dealing with partitioning and configuring the boot loader (GRUB). All steps are otherwise identical to the regular installation process.

What Are We Doing?

This guide will show you how to set up your UEFI system to load the GRUB boot loader, which will then load your Funtoo Linux kernel and initramfs. This is the "UEFI + GRUB" method as described on the Boot Methods page.

First Steps

To install Funtoo Linux on a UEFI system, first you need to boot SysRescueCD in UEFI mode. To do this, enable UEFI in your BIOS, and if necessary disable legacy booting. After some fiddling, you should be able to boot SysRescueCD and get a black and white text menu instead of the traditional aqua/cyan-colored menu. The black and white menu indicates that you booted SysRescueCD in UEFI mode. Once you've accomplished this, you're ready to continue with your Funtoo Linux installation and partition your drive. See below for details.

Partitioning

To set up your partitions for UEFI booting, you will create a ~500MB FAT32 partition on /dev/sda1, and set it to type EF00 using gdisk.

Command: n ↵
Partition Number: 1 ↵
First sector: 
Last sector: +500M ↵
Hex Code: EF00

This partition will serve as your Funtoo /boot filesystem as well as the partition that the UEFI firmware can read to load GRUB. Then you will set up swap on /dev/sda2 and your root filesystem on /dev/sda3. To create the FAT32 filesystem, type:

# mkfs.vfat -F 32 /dev/sda1

Your /etc/fstab entry for this filesystem will also differ, and will look like this:

/dev/sda1		/boot		vfat		noatime	1 2

Make sure you add VFAT support to your kernel if you are building it manually.

Boot Loader

Emerging GRUB

You will still use GRUB as a boot loader, but before emerging grub, you will need to enable EFI booting. To do this, add the following line to /etc/portage/make.conf:

GRUB_PLATFORMS="efi-64"

Then, emerge grub. You will notice efibootmgr getting pulled in as a dependency. This is expected and good.

Installing GRUB

Now, for the magic of getting everything in place for booting. You should copy your kernel and initramfs (if you have one -- you will if you are following the default install) to /boot. GRUB will boot those. But how do we get UEFI to boot GRUB? Well, we need to run the following command:

# grub-install --target=x86_64-efi --efi-directory=/boot /dev/sda

This command will simply install all the stuff to /boot/EFI and /boot/grub that your system needs to boot. In particular, the /boot/EFI/grub/grubx64.efi file will be created. This is the GRUB boot image that UEFI will load and start.

Configuring GRUB

OK, now UEFI has the GRUB image it needs to boot. But we still need to configure GRUB itself so it finds and boots your kernel and initramfs. This is done by performing the following steps.

First, let's copy /usr/share/grub/fonts/unifont.pf2 to /boot/grub/font.pf2. This is the bitmap font that we'll tell GRUB to use for the GRUB boot menu.

Next, since boot-update doesn't yet support UEFI, we will not use boot-update directly and will create a /boot/grub/grub.cfg file manually that looks like this:

set timeout=3
# Display settings
if loadfont /grub/font.pf2 ; then 
    set gfxmode=auto
    insmod efi_gop
    insmod efi_uga
    insmod gfxterm        
    terminal_output gfxterm
fi

menuentry "Funtoo Linux genkernel - kernel-debian-sources-x86_64-3.2.35-2" {  
    insmod part_gpt
    insmod fat  
    set root=(hostdisk//dev/sda,gpt1)  
    search --no-floppy --fs-uuid --set __REPLACE_UUID_OF_SDA1__
    linux /kernel-debian-sources-x86_64-3.2.35-2 real_root=/dev/sda3
    initrd /initramfs-debian-sources-x86_64-3.2.35-2  
    set gfxpayload=keep
}
set default=0

Note the search line where it says __REPLACE_UUID_OF_SDA1__ above. You will need to run blkid /dev/sda1 and use the UUID value that is displayed. For example, on my system, I need to use C34B-19CF. You can also change the menuentry line text in quotes to say whatever you want, and the linux and initrd lines should reference your kernel versions in /boot. As above, use the path / instead of /boot as the path should be relative to the root of the VFAT filesystem.

Known Issues

With pure UEFI boot mode, with legacy mode disabled, following error expected:

  • video driver not supported, boot hangs, hard reboot required.

Choose UEFI first, next legacy driver. It depends on motherboard vendor and efi bios version. In UEFI bios choose grub option, if your succeeded with above guide, additional menu should appear in Boot Menu, otherwise it boots into EFI shell:

  • grub:NAME of you hard drive

Done!

Remember to follow all other steps in the regular Funtoo Install Guide. Assuming you did everything correctly, your system should now boot via UEFI! We will be adding UEFI support to boot-update soon to make this process easier.