public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Yuval Hager <yuval@avramzon.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: Botting with vesafb under 2.6.22-gentoo-r2
Date: Sat, 5 Jan 2008 19:56:03 +0200	[thread overview]
Message-ID: <200801051956.03503.yuval@avramzon.net> (raw)
In-Reply-To: <200708180942.14756.yuval@avramzon.net>

[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]

On Saturday 18 August 2007, Yuval Hager wrote:
> Hi,
>
> I've just upgraded to gentoo-sources-2.6.22-r2, and found that the vesafb I
> used to have with my 2.6.18 does not work anymore. The boot line I had
> before had '...vga=791 video=vesafb', but now it does'nt work at all (gives
> my a blank screen at boot).
>
> I googled it up a little but found no definitive answer. I've done all as
> written in the guides and wiki, but it still doesn't work. I must be
> missing something, since I guess it's quite basic...
>
> Thanks,
>
> --yuval

Replying to my own post..

I am using Nvidia card and VESA support has to NOT be compiled in the kernel 
according to all nvidia gentoo guides, if I want to use nvidia driver for 
X11. Using this settings, it is quite obvious why I could not get it to work. 
I am not sure why it worked for 2.6.18, but it is not for 2.6.22.

I finally solved this using the latest kernel 2.6.23-gentoo-r3, and uvesafb 
(http://dev.gentoo.org/~spock/projects/uvesafb/). I followed the installation 
instructions in the above link, and it worked without a flaw.

Thanks!

-- 
Yuval Hager
[T] +972-77-341-4155
[@] yuval@avramzon.net

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

           reply	other threads:[~2008-01-05 17:58 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200708180942.14756.yuval@avramzon.net>]

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=200801051956.03503.yuval@avramzon.net \
    --to=yuval@avramzon.net \
    --cc=gentoo-amd64@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