NVidia driver failure on new system

[Thomas Milne]

On Fri, Jun 3, 2011 at 11:06 AM, Lennart Sorensen <
lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org> wrote:

> On Thu, Jun 02, 2011 at 06:44:38PM -0400, Thomas Milne wrote:
> > On Thu, Jun 2, 2011 at 5:38 PM, Lennart Sorensen <
> > lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org> wrote:
> >
> > > On Thu, Jun 02, 2011 at 03:44:08PM -0400, Thomas Milne wrote:
> > > >  joehill at rebelone:~$ dpkg --list | grep linux-headers
> > > > ii  linux-headers-2.6-amd64                       2.6.39+35
> > > >         Header files for Linux 2.6-amd64 (meta-package)
> > > > ii  linux-headers-2.6.39-1-amd64                  2.6.39-1
> > > >        Header files for Linux 2.6.39-1-amd64
> > > > ii  linux-headers-2.6.39-1-common                 2.6.39-1
> > > >        Common header files for Linux 2.6.39-1
> > > >
> > > > but
> > > >
> > > > joehill at rebelone:~$ uname -r
> > > > 2.6.32-5-686
> > > >
> > > > So...I either need linux-headers 2.6.32-5 or kernel 2.6.39-1 right?
> > >
> > > Yes.  unstable should be running 2.6.39-1.  2.6.32-5 is not the right
> > > kernel.
> > >
> > > linux-image-2.6-amd64 should depend on the current one for you.
> > > Upgrade and reboot.
> > >
> > >
> > What's weird though is that previously I was running 2.6.32-5-686. So
> > shouldn't I now be running 2.6.39-1-686? not amd64?
> >
> > The only one close to that though is 2.6.39-1-686-pae, and that doesn't
> boot
> > either. I am TOTALLY confused.
>
> What does 'dpkg --print-architecture' tell you?
>
>
joehill at rebelone:~$ dpkg --print-architecture
i386

On a number of systems I use that would say i386, meaning it is a
> 32bit install.  I still run the amd64 kernel to take advantage of more
> than 3GB ram efficiently (the bigmem/pae kernel does it inefficiently,
> and the regular 686 kernel doesn't do it at all).  I would run an amd64
> kernel on any system that can wether the user space is 32 or 64bit.
> It is the best choice either way.


Is it possible this is happening because of the missing firmware issue? ie.
the failed boots/ stack trace? When I installed the newer kernels it warned
me about that, so I installed firmware-debian. Is there another step after
installing the firmware?

-- 
Thomas Milne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gtalug.org/pipermail/legacy/attachments/20110603/76f6a51e/attachment.html>