public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: uvesafb - does it require use of  initramfs/initrd?
Date: Sat, 17 Jan 2009 21:27:04 -0600	[thread overview]
Message-ID: <58965d8a0901171927q12cac290ocead4eb8409d9cc8@mail.gmail.com> (raw)
In-Reply-To: <58965d8a0901171920y46962113p920c25d90df17e73@mail.gmail.com>

On Sat, Jan 17, 2009 at 9:20 PM, Paul Hartman
<paul.hartman+gentoo@gmail.com> wrote:
> On Sat, Jan 17, 2009 at 6:32 PM, »Q« <boxcars@gmx.net> wrote:
>> On Fri, 16 Jan 2009 01:42:30 -0600
>> Paul Hartman <paul.hartman+gentoo@gmail.com> wrote:
>>
>>> On Thu, Jan 15, 2009 at 11:49 PM, Paul Hartman
>>> <paul.hartman+gentoo@gmail.com> wrote:
>>> > Hi,
>>> >
>>> > Does anyone here use uvesafb? I followed the instructions to install
>>> > uvesafb from this page:
>>> >
>>> > http://dev.gentoo.org/~spock/projects/uvesafb/
>>> >
>>> > However, it does not work. Is it required to use initrd in order to
>>> > use uvesafb? (because I don't use it...)
>>> >
>>> > the 80x25 looks absolutely horrible and I'd love to have something
>>> > usable without needing to be in X. I have an nvidia geforce 9600GT
>>> > card using the latest nvidia-drivers, and am on amd64 if it matters.
>>>
>>> I'm ashamed to admit I made the most basic mistake. I compiled uvesafb
>>> as a module. Oops! Compiled it as "Y" instead of "M" and now I have a
>>> pair of Tux sitting atop my kernel boot screen and no more 80x25
>>> horror. :)
>>
>> You mean you are now successfully using uvesafb *without* an
>> initrd or initramfs?  Spock's site says you need v86d, and I don't know
>> how else to get it.  If I boot a kernel without it, uvesafb doesn't
>> work for me.
>
> Well you need the initramfs stuff is configured in the kernel as
> stated in the instructions at his website, but I'm not (not have I
> ever) used the initrd. My grub config (possibly wordwrapped by gmail)
> is:
>
> default 0
> timeout 10
> splashimage=(hd0,0)/grub/splash.xpm.gz
>
> title=Gentoo Linux 2.6
> root (hd0,0)
> kernel /vmlinuz root=/dev/sda5 doscsi dodmraid nmi_watchdog=0
> rootfstype=ext4 video=uvesafb:1280x720p-59,mtrr:3,ywrap
>

I forgot to specify: the kernel setting

CONFIG_INITRAMFS_SOURCE="/usr/share/v86d/initramfs"

compiled v86d into the kernel, so it doesn't need to execute the /sbin/v86d



  reply	other threads:[~2009-01-18  3:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16  5:49 [gentoo-user] uvesafb - does it require use of initramfs/initrd? Paul Hartman
2009-01-16  6:33 ` [gentoo-user] " Nikos Chantziaras
2009-01-16  6:47   ` Paul Hartman
2009-01-16  7:42 ` Paul Hartman
2009-01-16 18:33   ` reader
2009-01-16 19:27     ` Paul Hartman
2009-01-17 15:32       ` Peter Humphrey
2009-01-18  0:25         ` »Q«
2009-01-18 10:43           ` Peter Humphrey
2009-01-18 22:10             ` »Q«
2009-01-18  3:25         ` Paul Hartman
2009-01-17 13:43     ` Nikos Chantziaras
2009-01-17 14:47       ` Harry Putnam
2009-01-19 10:21         ` Nikos Chantziaras
2009-01-18  0:32   ` »Q«
2009-01-18  3:20     ` Paul Hartman
2009-01-18  3:27       ` Paul Hartman [this message]
2009-01-18  4:08         ` »Q«

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=58965d8a0901171927q12cac290ocead4eb8409d9cc8@mail.gmail.com \
    --to=paul.hartman+gentoo@gmail.com \
    --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