public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matthias Langer <mlangc@gmx.at>
To: gentoo-user@lists.gentoo.org
Subject: RE: [gentoo-user] Kernel 2.6.14 & Nvidia
Date: Tue, 08 Nov 2005 12:12:54 +0100	[thread overview]
Message-ID: <1131448374.10182.0.camel@sputnik886.ruz-net> (raw)
In-Reply-To: <FAEEIJPAOFEMBBLKPMJEOELBDGAA.BYoung@NuCORETech.com>

On Mon, 2005-11-07 at 17:58 -0800, Bob Young wrote:
> 
> -----Original Message-----
> From: David Corbin [mailto:gentoo.org@machturtle.com]
> Sent: Monday, November 07, 2005 3:21 PM
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] Kernel 2.6.14 & Nvidia
> 
> On Sunday 06 November 2005 11:13 pm, Norberto Bensa wrote:
> > Philip Webb wrote:
> > > Has anyone got Nvidia to work with Kernel 2.6.14 ?
> >
> > Yup. In /etc/conf.d/local.start
> >
> > /sbin/NVmakedevices.sh
> >
> > or
> >
> > mknod /dev/nvidia0 c 195 0
> > mknod /dev/nvidiactl c 195 255
> 
> 
> This doesn't work for me.  If I have the nvidia FB compiled in, then nvidia
> module fails to load long before local.start seems to be called.
> 
> 
> You can't have the nv driver providing the console frame buffer, then load
> the nvidia driver. If you do that, you have two different modules laying
> claim to control of the video hardware, thus causing the second one to fail
> to load.. If you want support for different video modes and boot splash etc,
> use the vesafb, then your nvidia driver should load.
> Bob Young

This link may be relevant:
http://bugs.gentoo.org/show_bug.cgi?id=104369
mlangc

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-11-08 11:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-07  2:37 [gentoo-user] Kernel 2.6.14 & Nvidia Philip Webb
2005-11-07  2:46 ` leloxias
2005-11-07  4:13 ` Norberto Bensa
2005-11-07  4:50   ` Ryan L
2005-11-07 23:21   ` David Corbin
2005-11-08  1:58     ` Bob Young
2005-11-08 11:12       ` Matthias Langer [this message]
2005-11-08 13:08     ` Hemmann, Volker Armin
2005-11-08 14:41       ` Alan E. Davis
2005-11-07  6:31 ` Luca Botti
2005-11-07  5:47   ` W.Kenworthy
2005-11-07  6:01     ` W.Kenworthy
2005-11-07  7:02 ` Cadaver
2005-11-07 13:00 ` Petteri Räty
2005-11-07 15:48   ` Philip Webb
2005-11-07 16:06     ` Catalin Grigoroscuta
2005-11-07 20:06       ` Philip Webb
2005-11-07 20:34         ` Bob Young
2005-11-07 22:31         ` Peper
2005-11-07 23:48           ` [gentoo-user] Kernel 2.6.14 & Nvidia [SOLVED] Philip Webb
2005-11-08  0:14           ` [gentoo-user] Kernel 2.6.14 & Nvidia Thierry de Coulon
2005-11-07 23:48         ` Nick Tzaperas

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=1131448374.10182.0.camel@sputnik886.ruz-net \
    --to=mlangc@gmx.at \
    --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