Export translations

Settings

Group

Language

Format

Export for off-line translation

Export in native format

<languages/>
__TOC__
{{BoxWarning|<span lang="en" dir="ltr" class="mw-content-ltr">Warning</span>|<div lang="en" dir="ltr" class="mw-content-ltr">
This page is outdated. If you have checked or updated this page and found the content to be suitable, please remove this notice. 2020-12-06
</div>}}
{{BoxInfo|1=<span lang="en" dir="ltr" class="mw-content-ltr">Note</span>|
2=<div lang="en" dir="ltr" class="mw-content-ltr">
12-Feb-17 : We used to have to, but now we no longer need to, add consolefonts to the end of the HOOKS= line in our mkinitcpio.conf file.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As the collection of all the X.Org Server protocol headers formerly
distributed as separate, standalone packages have been rolled up into
Xorgproto: [https://www.phoronix.com/scan.php?page=news_item&px=Xorgproto-Debut-Release] So if you have used this how-to to enlarge your boot up/down
process fonts, you should edit your /etc/mkinitcpio.conf file & remove
consolefonts from the end of the HOOKS= line.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you don't make this suggested edit, it won't cause you any problems,
besides seeing an error message saying (roughly) that consolefonts can't
be found, whenever you upgrade your kernel via the terminal.
</div>}}

{{SectionTemplate|
1=<span lang="en" dir="ltr" class="mw-content-ltr">Introduction</span>|
2=<span lang="en" dir="ltr" class="mw-content-ltr">If you use a high DPI resolution '''&''' you want to more easily read your display during the boot process (both up & down), '''&''' you '''don't''' have an extremely fast booting system (use SSD & the like), then this page will show you how to make both the GRUB menu fonts larger & how to change the console font used in the display of the boot up/down processes. This is all primarily for those users that place some value in being able to see/read the boot up/down displays, when they are live. The how-to endeavors to cater to both SystemD & OpenRC users.</span>
}}

{{SectionTemplate|
1=<span lang="en" dir="ltr" class="mw-content-ltr">What are we going to do here</span>|
2=<div lang="en" dir="ltr" class="mw-content-ltr">
This how-to is really a two in one, as the first part is about enlarging the font used by the GRUB menu & the early phase of the boot process up until the GPU driver loads.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The second part is about first identifying the GPU module to load, & then using the Kernel Mode Setting (KMS) ability of the Linux kernel to instruct it to load modules extremely early in the boot process. Which is what we will do with the GPU module via the /etc/mkinitcpio.conf file. Then finishing off that process by rebuilding the initial ramdisk image.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
After that we need to find where the consolefonts directory is & if need be clone the /usr/share/kbd/consolefonts directory to /usr/share/consolefonts. After that we need to choose a font, though I'll endeavor to make that as quick & painless as possible. Then we need to tell the /etc/conf.d/consolefont file what that font is, save & reboot to a new situation where we are able to actually read the text as it goes by. That's the plan.
</div>
}}

{{SectionTemplate|
1=<span lang="en" dir="ltr" class="mw-content-ltr">Give GRUB & the boot process up to the GPU module load a larger font</span>|
2=<div lang="en" dir="ltr" class="mw-content-ltr">
This one requires you to choose a font that you like (mono fonts are easiest to read), I chose DejaVuSansMono20 & here is the command line that creates this font in a GRUB compatible format, in the size that you have chosen & places it in the newly created /boot/grub/fonts directory (its a long command & it is ALL on one line):
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
sudo grub-mkfont --output=/boot/grub/fonts/DejaVuSansMono20.pf2 \ --size=20 /usr/share/fonts/TTF/dejavu/DejaVuSansMono.ttf
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Then we need to open the /etc/default/grub file in our text editor as root (use sudo) & add the following line (or lines if your like me & have a bad memory):
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
##==========================_HANDY_==========================================
 # More readable font on high dpi screen, generated with the following
 # 2 lines on ONE line, terminal command (ignore the error messages it works!:
 # sudo grub-mkfont --output=/boot/grub/fonts/DejaVuSansMono24.pf2 \
 #    --size=24 /usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf
 ##===========================================================================
 
 GRUB_FONT=/boot/grub/fonts/DejaVuSansMono18.pf2
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Save the edited file & then enter the following at the Terminal prompt:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
sudo update-grub
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Having done that, if you reboot the GRUB menu will be bigger & so will a shortish portion of the boot process, up until the GPU driver kernel module is loaded, where you'll go back to the default console font.
</div>
}}

{{SectionTemplate|
1=<span lang="en" dir="ltr" class="mw-content-ltr">Use KMS to load the GPU kernel module early in the boot process</span>|
2=<div lang="en" dir="ltr" class="mw-content-ltr">
Use sudo & load /etc/mkinitcpio.conf into your text editor & find the '''MODULES=""''' line very near the top of file. Here you will have to put your GPU module name, the three choices that I can show you here are:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Intel on-board''' (at least all of the intel CPU's that carry a GPU/CPU):
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
MODULES=(i915)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
MODULES=(radeon/amdgpu)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''nVidia free''':
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
MODULES=(nouveau)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''nVidia proprietary''':
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If your MODULES= line has any other modules on it already, just add your new one with a space separating it from the previous one.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You can save & close the file.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For our next trick, we have to identify which kernel branch you are using. Most people will be using an older; more recent; or the most recent, version of the "normally" supported kernel. Such shows itself in the /boot directory like so:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
initramfs-6.1-x86_64-fallback.img
 initramfs-6.1-x86_64.img
 vmlinuz-6.1-x86_64
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
<font color="red">(this is for Kernel 6.1, it may be different for you)</font color></br >
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
& would therefore use the following command to rebuild their Init Ramdisk Image:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
sudo mkinitcpio -p linux61
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
<font color="red">(again for kernel version 6.1, replace the version with your)<font color>
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For those that are using the/a Linux Long Term Support kernel then their identifying /boot files will look like this:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
initramfs-linux-lts-fallback.img
 initramfs-linux-lts.img
 vmlinuz-linux-lts
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
& would therefore use the following command to rebuild their linux-lts Init Ramdisk Image:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
sudo mkinitcpio -p linux-lts
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For those using more exotic kernels, you already know how to modify the above command to suit.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For Manjaro users that are using multiple kernels, you are going to need to edit multiple mkinitcpio.conf files that are named to suit each of your kernels. I don't have to bother with that on Artix (Arch/OpenRC), for better & worse. Again, your /boot directory will tell you what to do (as shown in the differences in the examples above).
</div>
}}

{{SectionTemplate|
1=<span lang="en" dir="ltr" class="mw-content-ltr">Use the /usr/share/consolefonts directory to enlarge your boot up/down font</span>|
2=
{{BoxInfo|<span lang="en" dir="ltr" class="mw-content-ltr">note|I look forward to cleaning up this section.</span>}}
<div lang="en" dir="ltr" class="mw-content-ltr">
On Artix, I had to copy the /usr/share/kbd/consolefonts/ directory into /usr/share/consolefonts . Whether I could have used the /usr/share/kbd/consolefonts directory in place or not I don't know (I didn't try). The /etc/conf.d/consolefont file uses the /usr/share/consolefonts path, so I made one.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
So the first thing that you have to do (before I find out from someone in the Manjaro forum where the consolefonts directory exists) is see whether you have to clone the directory from /usr/share/kbd/ to /usr/share/ or not. After that is sorted, then you need to choose a font. You won't like doing that. Here is a link to an old page (far fewer suitable fonts & its still too many)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Take my advice & use '''ter-132b''' this is a font that is large enough for my 15" 1440p display. I expect that it would be great on a 24" 1080p display. If it is too big, you can use a smaller number as will be easily seen in your consolefonts directory.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To tell the kernel to use the chosen custom console font you will need to open the /etc/conf.d/consolefont file & comment out (use the '''#''' at the start of the line) any line that says:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
consolefont=
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
consolefont="ter-132b"
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You need to make no other edits to this file, so close it.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Now from what I can make out on the ArchWiki font page: [https://wiki.archlinux.org/index.php/Fonts#Console_fonts] The above how-to should work on SystemD, as is. I will check on the Manjaro forum & if & where needed modify this page (there shouldn't be much in it as both systemd & openrc use the same kernel).
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
For Artix (Arch/OpenRC) users, you would need to just once use the following command:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
sudo rc-update add consolefont boot
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Hopefully I haven't forgotten anything, as this is has been a multi-step process & I lost power & a good deal of the wiki page some time ago & had to do it twice! ;)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
This page is still a work in progress & will be polished up as soon
 as I'm given the info' that I need via the Manjaro forum. ;)
</div>
}}

[[Category:Contents Page{{#translation:}}]]
[[Category:Outdated Page{{#translation:}}]]