“Cannot open font file True” in Fedora

When you start the fedora 16/17, it will show you an message “Cannot open font file True” in boot screen for few seconds. To fix this, we need to change the sysfont to default.
Steps :
1) Open the grub configuration
** sudo vi /etc/default/grub
2) Update the SYSFONT to latarcyrheb-sun16 and save the file.
** Look for "SYSFONT=True" and replace it with "SYSFONT=latarcyrheb-sun16"
3) Generate the grub configuration
** sudo grub2-mkconfig -o /boot/grub2/grub.cfg

Bugzilla URL : https://bugzilla.redhat.com/show_bug.cgi?id=799401


10 thoughts on ““Cannot open font file True” in Fedora

  1. There is no SYSFONT entry in my /etc/defaults/grub (there is, however, already SYSFONT=True in the line) but still I see the message even after running grub2-mkconfig.

  2. Doing the opposite of what is above in your instructions gets rid of the error message, e.g.:

    ** Look for “SYSFONT=True” and replace it with “SYSFONT=latarcyrheb-sun16” in GRUB_CMDLINE_LINUX.

    Do the same in the /etc/sysconfig/i18n file.

    Then run sudo grub2-mkconfig -o /boot/grub2/grub.cfg afterward and you should not see this error anymore.

  3. I think you have it backwards… it can’t find “True”, that’s what needs to be taken out, replaced with latarcyrheb-sun16 (or another of your choosing).

  4. Yes, We have to replace ‘True’ font with ‘latarcyrheb-sun16’ font in (sysfont) grub.cfg. I just made a little mistake while blogging. Thanks guys for pointing it out. I’ve updated my blog entry with this.

  5. hi everyone! I had the same problem so i followed this tutorial but now after the loading screen appears an error: “Failed to get maximum backlight value” and “no caching mode page present””assuming drive cache: write through” what’s my mistake? can anybody helps me? i thank you and i’m sorry if my english isn’t too good!

  6. Fabrizio,
    There was bug in the kernel (3.6.1-1) driver (mesa-dri-drivers) which causes the “Failed to get maximum backlight value” problem.
    To fix this, you need to update your kernel and mesa-dri-drivers package to the latest one.

    Moreover, this is not exposed by the change/fix mentioned in this blog post. I think, you updated the kernel to version which introduced this problem (only in certain cases).

    Refer :

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s