public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alan E. Davis" <lngndvs@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel 2.6.14 & Nvidia
Date: Wed, 9 Nov 2005 00:41:18 +1000	[thread overview]
Message-ID: <7bef1f890511080641u32f6985eqd9e2a5a94b0ed5c2@mail.gmail.com> (raw)
In-Reply-To: <200511081408.23929.volker.armin.hemmann@tu-clausthal.de>

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

Don't know whether this is even relevant. I was pulling my hair out trying
to get the nvidia driver ("nvidia") working with kernel 2.6.12 for about
three weeks. It worked ok with nv, but with nvidia it gave the same message
you got. I was using the same nvidia-kernel version you are. I moved to
kernel 2.6.13, and decided to run ~amd64 (what the heck). Nvidia kernel v.
7676 installed neatly and worked.

I don't recommend it, necessarily. It worked for me, but there seem to be
many variables that can cause that message.

Alan

On 11/8/05, Hemmann, Volker Armin <volker.armin.hemmann@tu-clausthal.de>
wrote:
>
> On Tuesday 08 November 2005 00:21, David Corbin wrote:
> > 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.
> >
>
> which is totally logical.
>
> You can not have two absolutly different drivers fight over the same piece
> of
> hardware. AFAIR it is even part of the README.
>
> But some people choose not to read it or think, but complain instead of
> it.
> --
> gentoo-user@gentoo.org mailing list
>
>


--
~/.signature

[-- Attachment #2: Type: text/html, Size: 2019 bytes --]

  reply	other threads:[~2005-11-08 14:55 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
2005-11-08 13:08     ` Hemmann, Volker Armin
2005-11-08 14:41       ` Alan E. Davis [this message]
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=7bef1f890511080641u32f6985eqd9e2a5a94b0ed5c2@mail.gmail.com \
    --to=lngndvs@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