From: AlifiChiganjati <AlifiChiganjati@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Unable to load such font with such kernel version
Date: Fri, 03 Nov 2023 01:16:42 +0100 [thread overview]
Message-ID: <20231103001642.wfU6cwrOvZuNcchx7M6dnPZq-He5NDYnqlGeoYHx7s0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45216@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
New comment by AlifiChiganjati on void-packages repository
https://github.com/void-linux/void-packages/issues/45216#issuecomment-1791731596
Comment:
> @et-rnal the solution is in the issue @classabbyamp posted, or at least was for me.
>
> in /etc/default/grub, append "fbcon=nodefer" to your kernel boot parameter, mine looks like this: GRUB_CMDLINE_LINUX_DEFAULT="init_on_free=1 net.ifnames=0 rd.auto=1 loglevel=0 delayacct rd.luks.allow-discards hpet=force i915.i915_enable_rc6=1 fbcon=nodefer"
>
> Then update-grub.
>
> This parameter explained: If the kernel is compiled with deferred fbcon takeover support, normally the framebuffer contents, left in place by the firmware/bootloader, will be preserved until there actually is some text is output to the console. This option causes fbcon to bind immediately to the fbdev device.
it's work, thanks mate
next prev parent reply other threads:[~2023-11-03 0:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 8:25 [ISSUE] " Sqvid
2023-07-25 18:22 ` justinesmithies
2023-07-28 0:40 ` classabbyamp
2023-07-31 3:15 ` superiums
2023-07-31 3:23 ` classabbyamp
2023-07-31 6:46 ` superiums
2023-09-12 21:54 ` et-rnal
2023-09-12 21:57 ` classabbyamp
2023-09-12 22:06 ` et-rnal
2023-09-19 7:56 ` wastemans
2023-09-19 7:58 ` wastemans
2023-09-19 8:11 ` superiums
2023-09-19 13:38 ` wastemans
2023-09-24 10:36 ` superiums
2023-11-03 0:16 ` AlifiChiganjati [this message]
2023-12-07 3:45 ` [ISSUE] [CLOSED] " ahesford
2023-12-22 23:24 ` don-dolarson
2023-12-25 18:13 ` don-dolarson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231103001642.wfU6cwrOvZuNcchx7M6dnPZq-He5NDYnqlGeoYHx7s0@z \
--to=alifichiganjati@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).