Re: anyone installed nvidia drivers on etch recently?

[Adam Hardy <adam.ant@cyberspaceroad.com>]

Jack Schneider on 04/10/08 16:15, wrote:
> On Sat, 04 Oct 2008 15:24:16 +0100
> Adam Hardy <adam.ant@cyberspaceroad.com> wrote:
>
> > Jack Schneider on 04/10/08 03:46, wrote:
> > > On Fri, 03 Oct 2008 18:21:18 +0100
> > > Adam Hardy <adam.ant@cyberspaceroad.com> wrote:
> > > > I'm using "nv", so I thought I'd try the proprietary nvidia driver.
> > > >
> > > > Following any of the methods on
> > > > http://wiki.debian.org/NvidiaGraphicsDrivers just leads me down the
> > > > same path to the point where I find "nvidia.ko failed to build" in
> > > > the logs.
> > > >
> > > > I'm using the stock kernel 2.6.26-bpo.1-686 from apt, and trying to
> > > > get the nvidia-glx-legacy nvidia-kernel-common
> > > > nvidia-kernel-legacy-2.6-686 packages from non-free to install, but
> > > > using the instruction:
> > > >
> > > > m-a auto-install nvidia
> > > >
> > > > leads to the error "nvidia.ko failed build", as I mentioned above.
> > > Take a look at this link:
> > >
> > > --
> > > http://tinyplanet.ca/~lsorense/debian/debian-nvidia-dri-howto.html
> > I followed those instructions to the letter with no success. It was
> > good in that it was definitive about whether I should be using legacy
> > or not, however the only other main difference from the wiki article
> > was the m-a command:
> >
> > m-a a-i -i -t -f nvidia-kernel-source
> >
> > which made no difference to the end result of the nvidia.ko build.
> >
> > I think it's something to do with v 2.6.26-bpo.1-686

OK my mistake - forgot I had etch-backports in my sources.list and so never
meant to install 2.6.26

I removed 2.6.26 and went back to 2.6.18 and the nvidia drivers compiled at once.

Now the problem though is that X doesn't come up - the screen stays black and
then drops back to the command prompt.

This is after the first time, directly after I compiled the nvidia driver, when
it all worked nicely - but not now that I've turned the machine off and back on
again.

No problem is mentioned in the log, just 'Initializing extension GLX' on the
last line, and the command line after failure just says


XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 0 requests (0 known processed) with 0 events remaining.


Seems from random results from google that the config is bad, but it works fine 
with 'nv'.

Any ideas?

Thanks
Adam