| 1 |
Don't know whether this is even relevant. I was pulling my hair out trying |
| 2 |
to get the nvidia driver ("nvidia") working with kernel 2.6.12 for about |
| 3 |
three weeks. It worked ok with nv, but with nvidia it gave the same message |
| 4 |
you got. I was using the same nvidia-kernel version you are. I moved to |
| 5 |
kernel 2.6.13, and decided to run ~amd64 (what the heck). Nvidia kernel v. |
| 6 |
7676 installed neatly and worked. |
| 7 |
|
| 8 |
I don't recommend it, necessarily. It worked for me, but there seem to be |
| 9 |
many variables that can cause that message. |
| 10 |
|
| 11 |
Alan |
| 12 |
|
| 13 |
On 11/8/05, Hemmann, Volker Armin <volker.armin.hemmann@××××××××××××.de> |
| 14 |
wrote: |
| 15 |
> |
| 16 |
> On Tuesday 08 November 2005 00:21, David Corbin wrote: |
| 17 |
> > On Sunday 06 November 2005 11:13 pm, Norberto Bensa wrote: |
| 18 |
> > > Philip Webb wrote: |
| 19 |
> > > > Has anyone got Nvidia to work with Kernel 2.6.14 ? |
| 20 |
> > > |
| 21 |
> > > Yup. In /etc/conf.d/local.start |
| 22 |
> > > |
| 23 |
> > > /sbin/NVmakedevices.sh |
| 24 |
> > > |
| 25 |
> > > or |
| 26 |
> > > |
| 27 |
> > > mknod /dev/nvidia0 c 195 0 |
| 28 |
> > > mknod /dev/nvidiactl c 195 255 |
| 29 |
> > |
| 30 |
> > This doesn't work for me. If I have the nvidia FB compiled in, then |
| 31 |
> nvidia |
| 32 |
> > module fails to load long before local.start seems to be called. |
| 33 |
> > |
| 34 |
> |
| 35 |
> which is totally logical. |
| 36 |
> |
| 37 |
> You can not have two absolutly different drivers fight over the same piece |
| 38 |
> of |
| 39 |
> hardware. AFAIR it is even part of the README. |
| 40 |
> |
| 41 |
> But some people choose not to read it or think, but complain instead of |
| 42 |
> it. |
| 43 |
> -- |
| 44 |
> gentoo-user@g.o mailing list |
| 45 |
> |
| 46 |
> |
| 47 |
|
| 48 |
|
| 49 |
-- |
| 50 |
~/.signature |
Archives