public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: blank consoles after X starts
Date: Sun, 27 Jul 2008 13:15:01 +0300	[thread overview]
Message-ID: <g6hhr8$96n$1@ger.gmane.org> (raw)
In-Reply-To: <28da1bb0807270242u526b8f02gbce2e50bca0fd161@mail.gmail.com>

Jorge Martínez López wrote:
> Hello!
> 
> 2008/7/27 Nikos Chantziaras <realnc@arcor.de>:
> [...]
>> I was always getting that one too, but other than this message, it was
>> working.
>>
>> I switched from uvesafb to vesafb at some point (to have the boot splash
>> enabled right at boot without any delay).  If you're on x86 or AMD64 you
>> might want to try that one (compile in-kernel, not as module).
> 
> I installed the klibc and v86d versions mentioned in the bug report
> and it seems to work again.
> 
> uvesafb was working perfectly for me, without any delays at boot. It
> has been included in the mainline kernel and it seems to be "The Way
> to Go" (TM).

I never got it to work without delay.  I could see kernel messeges for 1 
or 2 seconds.  That is not acceptable, I need the bootsplash in 0.01 
nanoseconds.

(lol)




  reply	other threads:[~2008-07-27 10:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-26 23:37 [gentoo-user] blank consoles after X starts William Kenworthy
2008-07-27  0:50 ` [gentoo-user] " Nikos Chantziaras
2008-07-27  2:19   ` William Kenworthy
2008-07-27  2:50     ` Nikos Chantziaras
2008-07-27  6:30       ` Jorge Martínez López
2008-07-27  7:08         ` Jorge Martínez López
2008-07-27  7:43           ` Jorge Martínez López
2008-07-27  7:58           ` Nikos Chantziaras
2008-07-27  9:42             ` Jorge Martínez López
2008-07-27 10:15               ` Nikos Chantziaras [this message]
2008-07-27 10:24               ` William Kenworthy
2008-07-28 20:28               ` Nikos Chantziaras
2008-07-29 14:05                 ` Jorge Martínez López

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='g6hhr8$96n$1@ger.gmane.org' \
    --to=realnc@arcor.de \
    --cc=gentoo-user@lists.gentoo.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