Latest NVIDIA graphics driver

[Len Lawrence]

Have just downloaded the 190.42 driver for 64bit Linux under Mandriva
2009.1.  I installed from the run file in console mode but ended up with
a black screen.  Trying startx tells me that there is a mismatch between
the kernel headers and the precompiled kernel interface.  That seems to
be the problem.  In the past, the installation procedure offered to
recompile the kernel interface against the system's kernel headers at
install time.  Now you are almost bound to end up with a mismatch.  So
how does one proceed from here?

The good thing about this driver is that it now includes support for
Xorg 1.7.0.rc1 aka 1.6.1.99 so it should match up with Mandriva 2009.1.

Len

[Len Lawrence]

Len Lawrence wrote:

> Have just downloaded the 190.42 driver for 64bit Linux under Mandriva
> 2009.1.  I installed from the run file in console mode but ended up
> with a black screen.  Trying startx tells me that there is a mismatch
> between the kernel headers and the precompiled kernel interface.  That
> seems to be the problem.  In the past, the installation procedure
> offered to recompile the kernel interface against the system's kernel
> headers at install time.  Now you are almost bound to end up with a
> mismatch.  So how does one proceed from here?
>
> The good thing about this driver is that it now includes support for
> Xorg 1.7.0.rc1 aka 1.6.1.99 so it should match up with Mandriva 2009.1.
>
> Len
>

It seems that I was wrong about something.  Another couple of attempts
and success!  The real problem is the console screen.  All the messages
overwite the previous text without clearing the screen which leads to a
confusing mess.  The yes/no buttons litter the screen until you cannot
tell which to press so it was more by  luck than judgement that the
installation succeeded.

The native resolution of the laptop screen is detected fine and glxgears
is back up to speed at 11000 fps or 660 fps in fullscreen mode.

Now I can install 2009.1 on the desktop machine.  Mandriva probably
already knows about this development so one hopes that they will provide
190.42 in 2010.0.

Len

[Anssi Hannula-3]

Len Lawrence wrote:

> Len Lawrence wrote:
>> Have just downloaded the 190.42 driver for 64bit Linux under Mandriva
>> 2009.1.  I installed from the run file in console mode but ended up
>> with a black screen.  Trying startx tells me that there is a mismatch
>> between the kernel headers and the precompiled kernel interface.  That
>> seems to be the problem.  In the past, the installation procedure
>> offered to recompile the kernel interface against the system's kernel
>> headers at install time.  Now you are almost bound to end up with a
>> mismatch.  So how does one proceed from here?
>>
>> The good thing about this driver is that it now includes support for
>> Xorg 1.7.0.rc1 aka 1.6.1.99 so it should match up with Mandriva 2009.1.
>>
>> Len
>>
> It seems that I was wrong about something.  Another couple of attempts
> and success!  The real problem is the console screen.  All the messages
> overwite the previous text without clearing the screen which leads to a
> confusing mess.  The yes/no buttons litter the screen until you cannot
> tell which to press so it was more by  luck than judgement that the
> installation succeeded.
>
> The native resolution of the laptop screen is detected fine and glxgears
> is back up to speed at 11000 fps or 660 fps in fullscreen mode.
>
> Now I can install 2009.1 on the desktop machine.  Mandriva probably
> already knows about this development so one hopes that they will provide
> 190.42 in 2010.0.

The release candidate version 190.42 was introduced so late that it
won't be integrated into 2010.0 in order to avoid regressions.
2010.0 will have the latest official release, 185.18.36. The release
candidate will be provided in the backports repository.

--
Anssi Hannula

[Charles A Edwards]

On Thu, 29 Oct 2009 15:20:47 +0200
Anssi Hannula wrote:

> The release candidate version 190.42 was introduced so late that it
> won't be integrated into 2010.0 in order to avoid regressions.
> 2010.0 will have the latest official release, 185.18.36. The release
> candidate will be provided in the backports repository.


As of Oct 27 190.42 Is the Official release.


    Charles


--
Cure the disease and kill the patient.
                -- Francis Bacon
----------------------
Mandriva Linux release 2010.0 (Cooker) for x86_64$
On SuperSize....http://www.eslrahc.com
Registered Linux user #182463
2.6.31.5-tmb-server-1mdv AMD Athlon(tm) 64 X2 Dual Core Processor 6400+
----------------------

[Anssi Hannula-3]

Charles A Edwards wrote:

> On Thu, 29 Oct 2009 15:20:47 +0200
> Anssi Hannula wrote:
>
>> The release candidate version 190.42 was introduced so late that it
>> won't be integrated into 2010.0 in order to avoid regressions.
>> 2010.0 will have the latest official release, 185.18.36. The release
>> candidate will be provided in the backports repository.
>
>
> As of Oct 27 190.42 Is the Official release.

Well, http://www.nvnews.net/vbulletin/showthread.php?t=122606 was
updated only a few hours ago, after my earlier reply ;)

In any case, what I said above still applies.

--
Anssi Hannula

[Len Lawrence]

Charles A Edwards wrote:

> On Thu, 29 Oct 2009 15:20:47 +0200
> Anssi Hannula wrote:
>
>> The release candidate version 190.42 was introduced so late that it
>> won't be integrated into 2010.0 in order to avoid regressions.
>> 2010.0 will have the latest official release, 185.18.36. The release
>> candidate will be provided in the backports repository.
>
>
> As of Oct 27 190.42 Is the Official release.
>

OK folks.  Thanks for your comments.  I am changing the subject in
thread because it seems pertinent.  So what is up with the install
screen?  Is there a fault with ncurses or might there be something
missing in the install script?  Does anybody else see this problem?

Len

[Brian Schroeder]

Len Lawrence wrote:

> OK folks.  Thanks for your comments.  I am changing the subject in
> thread because it seems pertinent.  So what is up with the install
> screen?  Is there a fault with ncurses or might there be something
> missing in the install script?  Does anybody else see this problem?
>
> Len

Yes, I see it every time.  It is a real pain!

Brian.

[Anssi Hannula-3]

Len Lawrence wrote:

> Charles A Edwards wrote:
>> On Thu, 29 Oct 2009 15:20:47 +0200
>> Anssi Hannula wrote:
>>
>>> The release candidate version 190.42 was introduced so late that it
>>> won't be integrated into 2010.0 in order to avoid regressions.
>>> 2010.0 will have the latest official release, 185.18.36. The release
>>> candidate will be provided in the backports repository.
>>
>> As of Oct 27 190.42 Is the Official release.
>>
> OK folks.  Thanks for your comments.  I am changing the subject in
> thread because it seems pertinent.  So what is up with the install
> screen?  Is there a fault with ncurses or might there be something
> missing in the install script?  Does anybody else see this problem?

Ncurses changed the binary interface on x86_64 few years back in version
5.5, without changing the SONAME. This results in that programs compiled
for ncurses < 5.5 do not work correctly with ncurses >= 5.5 and vice
versa, on x86_64. NVIDIA installer is apparently compiled with the older
interface.

Also, there is a compile-time option in ncurses to use the older
interface (--with-chtype=long). Apparently at least Fedora, Debian,
Ubuntu, Opensuse build ncurses with this flag, so their ncurses is
compatible with applications using the older interface only.

CC'ing Eugeni, the maintainer of Mandriva ncurses package. Eugeni, do
you think it would be wise to compile our ncurses with this flag as well
(when cooker reopens, of course), for cross-distribution and backward
compatibility?

You can also install upstream NVIDIA drivers with a simple commandline
interface instead of the ncurses interface by using --ui=none
commandline option for the installer.

(I'd like to remind everyone here that if you have installed NVIDIA
drivers manually, the drivers will break when kernel, mesa, or
x11-server is updated and you'll need to reinstall them; this does not
happen with the Mandriva provided packages, which is why they are the
recommended method)

--
Anssi Hannula

[Eugeni Dodonov]

On 10/29/2009 10:20 PM, Anssi Hannula wrote:
> Also, there is a compile-time option in ncurses to use the older
> interface (--with-chtype=long). Apparently at least Fedora, Debian,
> Ubuntu, Opensuse build ncurses with this flag, so their ncurses is
> compatible with applications using the older interface only.
>
> CC'ing Eugeni, the maintainer of Mandriva ncurses package. Eugeni, do
> you think it would be wise to compile our ncurses with this flag as well
> (when cooker reopens, of course), for cross-distribution and backward
> compatibility?

I think we should do it. ArchLinux also had this issue
(http://bbs.archlinux.org/viewtopic.php?id=65562), and Slackware and
Gentoo too. So I think we should enable it as well as it could
potentially fix other issues.

> (I'd like to remind everyone here that if you have installed NVIDIA
> drivers manually, the drivers will break when kernel, mesa, or
> x11-server is updated and you'll need to reinstall them; this does not
> happen with the Mandriva provided packages, which is why they are the
> recommended method)

I second that. I used to install nvidia drivers manually, but every
kernel update screwed the install, so I had to reinstall it manually. It
 was useful back when newest nvidia drivers were horrible broken, so I
did a small script to automatically reinstall it, but with latest
drivers I haven't had any issues for a long time. Updated drivers
usually arrive to the repos quickly after they appear on nvidia site.

Is there any specific reason for you to install nvidia drivers manually?

--
Eugeni Dodonov

[Len Lawrence]

Eugeni Dodonov wrote:

> On 10/29/2009 10:20 PM, Anssi Hannula wrote:
>  
>> Also, there is a compile-time option in ncurses to use the older
>> interface (--with-chtype=long). Apparently at least Fedora, Debian,
>> Ubuntu, Opensuse build ncurses with this flag, so their ncurses is
>> compatible with applications using the older interface only.
>>
>> CC'ing Eugeni, the maintainer of Mandriva ncurses package. Eugeni, do
>> you think it would be wise to compile our ncurses with this flag as well
>> (when cooker reopens, of course), for cross-distribution and backward
>> compatibility?
>>    
>
> I think we should do it. ArchLinux also had this issue
> (http://bbs.archlinux.org/viewtopic.php?id=65562), and Slackware and
> Gentoo too. So I think we should enable it as well as it could
> potentially fix other issues.
>
>  
>> (I'd like to remind everyone here that if you have installed NVIDIA
>> drivers manually, the drivers will break when kernel, mesa, or
>> x11-server is updated and you'll need to reinstall them; this does not
>> happen with the Mandriva provided packages, which is why they are the
>> recommended method)
>>    
>
> I second that. I used to install nvidia drivers manually, but every
> kernel update screwed the install, so I had to reinstall it manually. It
>  was useful back when newest nvidia drivers were horrible broken, so I
> did a small script to automatically reinstall it, but with latest
> drivers I haven't had any issues for a long time. Updated drivers
> usually arrive to the repos quickly after they appear on nvidia site.
>
> Is there any specific reason for you to install nvidia drivers manually?
>
>  

Thanks guys for all that information.

Speaking for myself, the reason I wanted this latest driver was because
69xx seemed a step backward when moving from 2008.1 to 2009.1.  Manual
installation was the only option as the new driver had only just been
released (I get reminders from nVidia).  I wished to confirm that 190.42
would set up the monitor in 1920x1200 and provide the full range of
capabilities.  You all gave me help to get past the problems I had with
the 69xx driver initially - with 190.42 there are none.

Len

[Eugeni Dodonov]

On 10/30/2009 06:14 AM, Len Lawrence wrote:

>> Is there any specific reason for you to install nvidia drivers manually?
>>
>>  
> Thanks guys for all that information.
>
> Speaking for myself, the reason I wanted this latest driver was because
> 69xx seemed a step backward when moving from 2008.1 to 2009.1.  Manual
> installation was the only option as the new driver had only just been
> released (I get reminders from nVidia).  I wished to confirm that 190.42
> would set up the monitor in 1920x1200 and provide the full range of
> capabilities.  You all gave me help to get past the problems I had with
> the 69xx driver initially - with 190.42 there are none.

That's good to know! 190.42 should be available in 2009.1 backports by
now, it is nice to know that it fixes some issues that older drivers had :).

--
Eugeni Dodonov

[Anssi Hannula-3]

Len Lawrence wrote:
> Speaking for myself, the reason I wanted this latest driver was because
> 69xx seemed a step backward when moving from 2008.1 to 2009.1.  Manual
> installation was the only option as the new driver had only just been
> released (I get reminders from nVidia).  I wished to confirm that 190.42
> would set up the monitor in 1920x1200 and provide the full range of
> capabilities.  You all gave me help to get past the problems I had with
> the 69xx driver initially - with 190.42 there are none.

Hmm, there is no 69xx driver. Do you mean 96xx? If so, that seems like a
bug of some kind. as nvidia-current should be used with newish cards.
What is your "lspcidrake -v | grep VGA" output?

--
Anssi Hannula

[Len Lawrence]

Anssi Hannula wrote:

> Len Lawrence wrote:
>> Speaking for myself, the reason I wanted this latest driver was because
>> 69xx seemed a step backward when moving from 2008.1 to 2009.1.  Manual
>> installation was the only option as the new driver had only just been
>> released (I get reminders from nVidia).  I wished to confirm that 190.42
>> would set up the monitor in 1920x1200 and provide the full range of
>> capabilities.  You all gave me help to get past the problems I had with
>> the 69xx driver initially - with 190.42 there are none.
>
> Hmm, there is no 69xx driver. Do you mean 96xx? If so, that seems like a
> bug of some kind. as nvidia-current should be used with newish cards.
> What is your "lspcidrake -v | grep VGA" output?
>

Sorry, typo; 61xx.

Card: NVIDIA GeForce 6100 and later: nVidia Corporation| GeForce 8700M
GT [DISPLAY_VGA]
(vendor:10de device:0409 subv:1028 subd:019b)

[Anssi Hannula-3]

Len Lawrence wrote:

> Anssi Hannula wrote:
>> Len Lawrence wrote:
>>> Speaking for myself, the reason I wanted this latest driver was because
>>> 69xx seemed a step backward when moving from 2008.1 to 2009.1.  Manual
>>> installation was the only option as the new driver had only just been
>>> released (I get reminders from nVidia).  I wished to confirm that 190.42
>>> would set up the monitor in 1920x1200 and provide the full range of
>>> capabilities.  You all gave me help to get past the problems I had with
>>> the 69xx driver initially - with 190.42 there are none.
>>
>> Hmm, there is no 69xx driver. Do you mean 96xx? If so, that seems like a
>> bug of some kind. as nvidia-current should be used with newish cards.
>> What is your "lspcidrake -v | grep VGA" output?
>>
> Sorry, typo; 61xx.
>
> Card: NVIDIA GeForce 6100 and later: nVidia Corporation| GeForce 8700M
> GT [DISPLAY_VGA]
> (vendor:10de device:0409 subv:1028 subd:019b)

Ah, ok. This means the nvidia-current indeed, so no bug :)

--
Anssi Hannula