nvidia mess, Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-25 Thread Konstantin Olchanski
On Thu, Jan 24, 2013 at 06:32:10PM +, Alan Bartlett wrote:
 
 It seems jdow has screwed up.
 


I am not buying this. I shall bite the hand that feeds me and elaborate.

Look at it from my side.

As a small part of my job, I manage 20-30 machines with random ATI and NVIDIA 
video cards.

I love ELREPO and I install the nvidia drivers the usual way:
yum install elrepo-release;
yum install nvidia-driver-blah;
reboot, everything works great.

Then on a nice sunny day, I read the post by jdow about elrepo having pushed
out drivers with support for her video card removed, and she is clearly unhappy
about it (who would be happy?).

Well, bad things happen to good people, could happen even to me, right?

But wait, it did happen to me just now. These new drivers have been pushed
into every one of my computers! Some of them have a supported video card, some 
not,
but in any case, now I have to deal with this, happy or not.

So where is here my fault, where is here jdow's fault? We did not do anything
and our computers are broken now and we have to spend time fixing them.

Before assigning the blame, let me list the evident problems:

1) yum install elrepo-release enables automatic updates from the repository,
   so any updated packages will be installed automatically. 
(elrepo-release-6-5.el6,
   [elrepo] enabled=1).

2) nvidia removes support for some video cards from their driver

3) nvidia and elrepo make a mess of the information on which cards are 
supported by which drivers.
   Quickly, GeForce210 is supported by which driver? Hint: 
http://elrepo.org/tiki/kmod-nvidia
   does not have a link to a list of supported cards.

4) elrepo pushes out the new driver under the old name, messing up all the 
unlucky machines.

5) elrepo tells us but you should have followed our mailing lists and converted
   those machine to the legacy driver, we gave you N days to do so!
   (even if you are on vacation, or busy with another project, or have the 
affected
machines in inaccessible locations).

Without assigning blame, I can suggest some solutions:

a) yum install elrepo-release should have automatic updates disabled, for 
nvidia drivers
   or for all packages (through yum-autoupdate magic, through enabled=0, 
whatever).

b) elrepo should have used a different name for the new incompatible driver 
(kmod-nvidia-310).

c) elrepo should add a big warning any future update of this driver may remove 
support for your video card,
   please follow our mailing lists closely in 
http://elrepo.org/tiki/kmod-nvidia.

As it stands now, I cannot even tell from the available documentation which 
driver
I should be using for the GeForce210 cards I have on most machines.

What a mess.


-- 
Konstantin Olchanski
Data Acquisition Systems: The Bytes Must Flow!
Email: olchansk-at-triumf-dot-ca
Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada


Re: nvidia mess, Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-25 Thread Konstantin Olchanski
On Fri, Jan 25, 2013 at 12:19:14PM -0800, Konstantin Olchanski wrote:
 
 3) nvidia and elrepo make a mess of the information on which cards are 
 supported by which drivers.


To elaborate:

http://elrepo.org/tiki/kmod-nvidia

The grand total of information on supported video cards is this:

Supported Chipsets
This driver is the current release and supports the most recent NVIDIA graphics 
cards (GeForce 8 series GPUs onwards, as well as Quadro series). Users of cards 
based on older chipsets should use one of the following legacy drivers.

This is not helpful information. GeForce210 cards I bought in December are 
recent or not? Are
they 8 series and onward or not? They are not listed in the legacy lists, is 
it an omission
or have I dodged a bullet today or not?

-- 
Konstantin Olchanski
Data Acquisition Systems: The Bytes Must Flow!
Email: olchansk-at-triumf-dot-ca
Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada


Re: [SCIENTIFIC-LINUX-USERS] nvidia mess, Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-25 Thread Pat Riehecky

On 01/25/2013 02:28 PM, Konstantin Olchanski wrote:

On Fri, Jan 25, 2013 at 12:19:14PM -0800, Konstantin Olchanski wrote:

3) nvidia and elrepo make a mess of the information on which cards are 
supported by which drivers.


To elaborate:

http://elrepo.org/tiki/kmod-nvidia

The grand total of information on supported video cards is this:

Supported Chipsets
This driver is the current release and supports the most recent NVIDIA graphics 
cards (GeForce 8 series GPUs onwards, as well as Quadro series). Users of cards 
based on older chipsets should use one of the following legacy drivers.

This is not helpful information. GeForce210 cards I bought in December are 
recent or not? Are
they 8 series and onward or not? They are not listed in the legacy lists, is 
it an omission
or have I dodged a bullet today or not?



Nvidia has a helpful compatibility page (google result #2 for nvidia 
linux drivers):


http://www.nvidia.com/Download/index.aspx?lang=en-us

Please don't hold the ELRepo folks accountable for changes NVidia makes.

They are graciously donating their time to make these packages.

Pat

--
Pat Riehecky
Scientific Linux Developer


Re: nvidia mess, Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-25 Thread jdow

On 2013/01/25 12:28, Konstantin Olchanski wrote:

On Fri, Jan 25, 2013 at 12:19:14PM -0800, Konstantin Olchanski wrote:


3) nvidia and elrepo make a mess of the information on which cards are 
supported by which drivers.



To elaborate:

http://elrepo.org/tiki/kmod-nvidia

The grand total of information on supported video cards is this:

Supported Chipsets
This driver is the current release and supports the most recent NVIDIA graphics 
cards (GeForce 8 series GPUs onwards, as well as Quadro series). Users of cards 
based on older chipsets should use one of the following legacy drivers.

This is not helpful information. GeForce210 cards I bought in December are 
recent or not? Are
they 8 series and onward or not? They are not listed in the legacy lists, is 
it an omission
or have I dodged a bullet today or not?


To a degree I can sympathize with the elrepo people. Nvidia has screwed up.
After getting disgusted with ATI I abandoned them for Nvidia. Now maybe I
need to figure out how good the support for Intel cards is these days.

But, still, the gentlemen at elrepo could have handled this a little more
gracefully, methinks. It's a shame they're stuck in the middle here. They
seem to be basically very good folks.

{^_^}


Re: nvidia mess, Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-25 Thread Akemi Yagi
On Fri, Jan 25, 2013 at 12:57 PM, jdow j...@earthlink.net wrote:

  the gentlemen at elrepo .
  They seem to be basically very good folks.

s/basically//

;-)

By the way there is more than gentlemen on the ELRepo team... but
that's not important.

Akemi


Re: [SCIENTIFIC-LINUX-USERS] nvidia mess, Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-25 Thread Konstantin Olchanski
On Fri, Jan 25, 2013 at 02:35:27PM -0600, Pat Riehecky wrote:

 Nvidia has a helpful compatibility page (google result #2 for nvidia
 linux drivers):
 
 http://www.nvidia.com/Download/index.aspx?lang=en-us
 


Not so helpful as to provide the actual list of supported products. Since I 
have nothing
better to do today, I eventually found the actual list at:

http://www.nvidia.com/object/linux-display-amd64-310.32-driver.html

By luck, it's the list for the same version of the driver as was helpfully
pushed into my computers by elrepo:

iris01:~$ rpm -q kmod-nvidia
kmod-nvidia-310.32-1.el6.elrepo.x86_64

I vote to have it linked from http://elrepo.org/tiki/kmod-nvidia


 Please don't hold the ELRepo folks accountable for changes NVidia makes.
 
 They are graciously donating their time to make these packages.
 

Yes, as I said, one bites the hand that feeds us. Not the hand of the nice 
people where this yummy dogfood ultimately comes from.


-- 
Konstantin Olchanski
Data Acquisition Systems: The Bytes Must Flow!
Email: olchansk-at-triumf-dot-ca
Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada


Re: nvidia mess, Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-25 Thread jdow

On 2013/01/25 13:04, Akemi Yagi wrote:

On Fri, Jan 25, 2013 at 12:57 PM, jdow j...@earthlink.net wrote:


  the gentlemen at elrepo .
  They seem to be basically very good folks.


s/basically//

;-)

By the way there is more than gentlemen on the ELRepo team... but
that's not important.

Akemi


I had a strong suspicion that was the case. However, as used Gentlemen
was generic human based. I gave up on the him/her or himer kind of
nonsense about the time people started thinking it'd be a good idea. I
embraced it for all of a week, maybe. If you male guys want some good
male only pronouns and nouns go generate your own new ones for referring
to men. All the others are generic now.

As for the textual substitution I stick with the way I phrased it. Remember
that one Aw S***! wipes out 1000 attaboys.

{^_-}


Re: nvidia mess, Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-25 Thread Lamar Owen
On Jan 25, 2013, at 3:57 PM, jdow wrote:
 To a degree I can sympathize with the elrepo people. Nvidia has screwed up.

This is not the first time nvidia cards have gone 'legacy'.  There are now 
three supported legacy nvidia driver versions (304.xx, 173.xx, and 96.xx).  
Prior to 310.xx, there were but two.

 After getting disgusted with ATI I abandoned them for Nvidia. Now maybe I
 need to figure out how good the support for Intel cards is these days.
 

Yeah, good luck with that.  

 But, still, the gentlemen at elrepo could have handled this a little more
 gracefully, methinks. It's a shame they're stuck in the middle here. They
 seem to be basically very good folks.
 

They handled it as gracefully as it could have been handled, since the heads-up 
was posted on the elrepo list quite a while ago.  I do think that if one uses 
third party packages, one should follow at least the announcement lists for 
each such repo.


Re: nvidia mess, Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-25 Thread jdow

On 2013/01/25 13:31, Lamar Owen wrote:

On Jan 25, 2013, at 3:57 PM, jdow wrote:

To a degree I can sympathize with the elrepo people. Nvidia has screwed up.


This is not the first time nvidia cards have gone 'legacy'.  There are now 
three supported legacy nvidia driver versions (304.xx, 173.xx, and 96.xx).  
Prior to 310.xx, there were but two.


After getting disgusted with ATI I abandoned them for Nvidia. Now maybe I
need to figure out how good the support for Intel cards is these days.



Yeah, good luck with that.


But, still, the gentlemen at elrepo could have handled this a little more
gracefully, methinks. It's a shame they're stuck in the middle here. They
seem to be basically very good folks.



They handled it as gracefully as it could have been handled, since the heads-up 
was posted on the elrepo list quite a while ago.  I do think that if one uses 
third party packages, one should follow at least the announcement lists for 
each such repo.


It seems there should have been some way to cozen yum into sending the
administrator email regarding the process that needs to be taken. Better
yet would be a test for cards gone legacy. This could be added to the
install for a 304.65 driver update that is basically the same as 304.64
with the addition of a test program.

In the post processing the test program is run.

At best that test program should setup a sequence of yum steps to remove
the newly installed 305 drivers and install the 304xx legacy drivers. I
suspect it would take fairly little script-fu to do either just the email
or the full reinstall magilla. For the emailing this line should work:

mail -v -s Your Nvidia graphics card is going legacy root msg /dev/null

Just install a batch file with that line and the msg text then run it
if the test program reports the board is unsupported. That message could
have the update script embedded within it for easy reinstallation.

{^_^}


Re: nvidia mess, Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-25 Thread Akemi Yagi
On Fri, Jan 25, 2013 at 2:48 PM, jdow j...@earthlink.net wrote:

 It seems there should have been some way to cozen yum into sending the
 administrator email regarding the process that needs to be taken.
snip

I ask once again that all elrepo-related talks be taken to the elrepo
mailing list. The SL list is the place where SL-specific topics are
handled. But more importantly, users who are concerned (this includes
RHEL and CentOS users) can join the discussion on the elrepo M/L. In
fact, there is already one post/idea by Nux:

http://lists.elrepo.org/pipermail/elrepo/2013-January/001620.html

And by now everyone is subscribed to the elrepo list, right? Right?

Akemi


Re: nvidia mess, Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-25 Thread jdow

On 2013/01/25 15:04, Akemi Yagi wrote:

On Fri, Jan 25, 2013 at 2:48 PM, jdow j...@earthlink.net wrote:


It seems there should have been some way to cozen yum into sending the
administrator email regarding the process that needs to be taken.

snip

I ask once again that all elrepo-related talks be taken to the elrepo
mailing list. The SL list is the place where SL-specific topics are
handled. But more importantly, users who are concerned (this includes
RHEL and CentOS users) can join the discussion on the elrepo M/L. In
fact, there is already one post/idea by Nux:

http://lists.elrepo.org/pipermail/elrepo/2013-January/001620.html

And by now everyone is subscribed to the elrepo list, right? Right?


You ask too much, perhaps.


Akemi


{^_^}


Re: nvidia mess, Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-25 Thread jdow

It looks like Nux has it under control if people listen.

I figure there should be some people around ElRepo at least as smart
and clever as a roughly 70 year old woman who's too dumb to retire
and keeps pushing her work, which is not system administration. And
I figure at my age I've earned the right to be cranky.

(Or are you telling me old age and guile beat youth and enthusiasm
yet again.)

{^_-}

On 2013/01/25 15:04, Akemi Yagi wrote:

On Fri, Jan 25, 2013 at 2:48 PM, jdow j...@earthlink.net wrote:


It seems there should have been some way to cozen yum into sending the
administrator email regarding the process that needs to be taken.

snip

I ask once again that all elrepo-related talks be taken to the elrepo
mailing list. The SL list is the place where SL-specific topics are
handled. But more importantly, users who are concerned (this includes
RHEL and CentOS users) can join the discussion on the elrepo M/L. In
fact, there is already one post/idea by Nux:

http://lists.elrepo.org/pipermail/elrepo/2013-January/001620.html

And by now everyone is subscribed to the elrepo list, right? Right?

Akemi



Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-24 Thread jdow

On 2013/01/23 23:55, Phil Perry wrote:


Here is the announcement I made back in November that the 310.xx series nvidia
drivers were dropping support for older 6xxx and 7xxx based hardware:

http://lists.elrepo.org/pipermail/elrepo/2012-November/001525.html


And how was I to know that and how was I to prevent 310 being placed
on a no longer supported brand new system? It's rather a bummer you know.



No, this is the nvidia driver telling you that your hardware is no longer
supported. It even tells you that you need the NVIDIA 304.xx Legacy drivers.


That's not obvious. And I feel I have a rather perfect right to presume
the board should be supported. It is a brand new machine as of May last
year.


That's correct - you need to stay at the 304.xx driver as this is the *last*
driver that will support your older hardware (7xxx based chipset). We released
the legacy kmod-nvidia-304xx and nvidia-x11-drv-304xx packages to aid in this
(see the thread linked above) and pushed them out to the main repo *before* we
released the updated 310.xx series drivers.

Please uninstall the kmod-nvidia driver and install the kmod-nvidia-304xx and
then you can continue to receive updates from elrepo.


I've just tried to downgrade and see what happens.


Nothing screwed up, nvidia simply decided it was time to move on from supporting
aging hardware (~8 years old?) in the current driver release.


Nvidia screwed up. The hardware was brand new about 8 months ago. So I feel
I have a perfect right to be annoyed.

Now, how do I stop new stuff from coming in? If there is a change in what
is supported then it behooves somebody to provide an automated test to
make sure the systems keep running by not downloading updates that do not
fit the particular system. After all lspci exists, reports this line
00:0d.0 VGA compatible controller: nVidia Corporation C61 [GeForce 7025 /
nForce 630a] (rev a2), and the install could be aborted when that is
found and the administrator notified.

{o.o}


Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-24 Thread Phil Perry

On 24/01/13 08:08, jdow wrote:

On 2013/01/23 23:55, Phil Perry wrote:


Here is the announcement I made back in November that the 310.xx
series nvidia
drivers were dropping support for older 6xxx and 7xxx based hardware:

http://lists.elrepo.org/pipermail/elrepo/2012-November/001525.html


And how was I to know that and how was I to prevent 310 being placed
on a no longer supported brand new system? It's rather a bummer you know.



Did you read the release notes for the new driver? That's how I found 
out. Did you read my discussion thread on the issue? That's how other 
elrepo users found out and suggested the solution.


I really don't know what you expect me to say. We have set up an email 
list to communicate with our users and we use it. We use our IRC channel 
too. Many thousands of people use the software we package. Only a very 
small percentage subscribe to the lists. There will be many people in 
exactly the same position as you. I guess when things break for them 
they will come looking for answers as you did, and we do our best to 
provide them. In this case we knew of the issue, we had documented the 
issue and we had a solution prepared and waiting for you. I'm really not 
sure what more you expect me to do for you, for free in my own 
volunteered time? I'm really sorry if you feel it's a bummer.


As I said before, if you subscribe to the elrepo mailing list (or even 
hang out in #elrepo on IRC) we *will* highlight important issues that 
affect the software that we release as we did above in a discussion 
thread that ran for 2 months.




No, this is the nvidia driver telling you that your hardware is no longer
supported. It even tells you that you need the NVIDIA 304.xx Legacy
drivers.


That's not obvious. And I feel I have a rather perfect right to presume
the board should be supported. It is a brand new machine as of May last
year.


That's correct - you need to stay at the 304.xx driver as this is the
*last*
driver that will support your older hardware (7xxx based chipset). We
released
the legacy kmod-nvidia-304xx and nvidia-x11-drv-304xx packages to aid
in this
(see the thread linked above) and pushed them out to the main repo
*before* we
released the updated 310.xx series drivers.

Please uninstall the kmod-nvidia driver and install the
kmod-nvidia-304xx and
then you can continue to receive updates from elrepo.


I've just tried to downgrade and see what happens.


Nothing screwed up, nvidia simply decided it was time to move on from
supporting
aging hardware (~8 years old?) in the current driver release.


Nvidia screwed up. The hardware was brand new about 8 months ago. So I feel
I have a perfect right to be annoyed.



You'd need to take that up with nvidia, or maybe even your hardware 
vendor why they are using old chipsets.



Now, how do I stop new stuff from coming in? If there is a change in what
is supported then it behooves somebody to provide an automated test to
make sure the systems keep running by not downloading updates that do not
fit the particular system. After all lspci exists, reports this line
00:0d.0 VGA compatible controller: nVidia Corporation C61 [GeForce 7025 /
nForce 630a] (rev a2), and the install could be aborted when that is
found and the administrator notified.



Yes, we had that discussion and if we knew of a way to technically 
implement that we would have seriously considered it.


Please, if you can suggest a mechanism for an RPM package to know what 
hardware is present *before* it installs itself, and then prevent itself 
from installing if the correct hardware isn't present, and do all this 
from within a yum transaction, them I'm all ears. You can run such tests 
in %pre or %post scripts but by then the yum transaction is already 
underway and the package is set to be installed or is already installed. 
At which point the best you can do is log the issue to warn the user, 
which is *exactly* what the nvidia driver does - even then you didn't 
understand what the log entry was telling you. We didn't see any need to 
replicate that.


If you are using an installer script then it's doable, but then you also 
lose all the advancements and convenience of a package manager with 
automatic updates, not to mention kABI-tracking RPM packaged drivers 
that survive kernel updates. Nvidia uses an installer script - feel free 
to use that if it better suits your requirements.


Anyway, this isn't an SL issue so lets please not clutter the SL list 
any further. I'm happy to continue the discussion on the elrepo lists or 
on IRC.


Regards,

Phil


Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-24 Thread jdow

On 2013/01/24 01:12, Phil Perry wrote:

On 24/01/13 08:08, jdow wrote:

On 2013/01/23 23:55, Phil Perry wrote:


Here is the announcement I made back in November that the 310.xx
series nvidia
drivers were dropping support for older 6xxx and 7xxx based hardware:

http://lists.elrepo.org/pipermail/elrepo/2012-November/001525.html


And how was I to know that and how was I to prevent 310 being placed
on a no longer supported brand new system? It's rather a bummer you know.



Did you read the release notes for the new driver? That's how I found out. Did
you read my discussion thread on the issue? That's how other elrepo users found
out and suggested the solution.


Chicken, please meet Mr. Egg. Mr. Egg, please meet Ms. Chicken. I have the
release note before an automatic update happens?


I really don't know what you expect me to say. We have set up an email list to
communicate with our users and we use it. We use our IRC channel too. Many
thousands of people use the software we package. Only a very small percentage
subscribe to the lists. There will be many people in exactly the same position
as you. I guess when things break for them they will come looking for answers
as you did, and we do our best to provide them. In this case we knew of the
issue, we had documented the issue and we had a solution prepared and waiting
for you. I'm really not sure what more you expect me to do for you, for free in
my own volunteered time? I'm really sorry if you feel it's a bummer.

As I said before, if you subscribe to the elrepo mailing list (or even hang out
in #elrepo on IRC) we *will* highlight important issues that affect the software
that we release as we did above in a discussion thread that ran for 2 months.



No, this is the nvidia driver telling you that your hardware is no longer
supported. It even tells you that you need the NVIDIA 304.xx Legacy
drivers.


That's not obvious. And I feel I have a rather perfect right to presume
the board should be supported. It is a brand new machine as of May last
year.


That's correct - you need to stay at the 304.xx driver as this is the
*last*
driver that will support your older hardware (7xxx based chipset). We
released
the legacy kmod-nvidia-304xx and nvidia-x11-drv-304xx packages to aid
in this
(see the thread linked above) and pushed them out to the main repo
*before* we
released the updated 310.xx series drivers.

Please uninstall the kmod-nvidia driver and install the
kmod-nvidia-304xx and
then you can continue to receive updates from elrepo.


I've just tried to downgrade and see what happens.


Nothing screwed up, nvidia simply decided it was time to move on from
supporting
aging hardware (~8 years old?) in the current driver release.


Nvidia screwed up. The hardware was brand new about 8 months ago. So I feel
I have a perfect right to be annoyed.



You'd need to take that up with nvidia, or maybe even your hardware vendor why
they are using old chipsets.


Now, how do I stop new stuff from coming in? If there is a change in what
is supported then it behooves somebody to provide an automated test to
make sure the systems keep running by not downloading updates that do not
fit the particular system. After all lspci exists, reports this line
00:0d.0 VGA compatible controller: nVidia Corporation C61 [GeForce 7025 /
nForce 630a] (rev a2), and the install could be aborted when that is
found and the administrator notified.



Yes, we had that discussion and if we knew of a way to technically implement
that we would have seriously considered it.

Please, if you can suggest a mechanism for an RPM package to know what hardware
is present *before* it installs itself, and then prevent itself from installing
if the correct hardware isn't present, and do all this from within a yum
transaction, them I'm all ears. You can run such tests in %pre or %post scripts
but by then the yum transaction is already underway and the package is set to be
installed or is already installed. At which point the best you can do is log the
issue to warn the user, which is *exactly* what the nvidia driver does - even
then you didn't understand what the log entry was telling you. We didn't see any
need to replicate that.


Hm, this might be an issue to be bumped into the RPM maintainers.

There is a trick I used with (much) older redhat versions that might apply.
I built a dummy rpm for spamassassin with a high version number so that it
would be perpetually happy with what I had and not overwrite versions I was
working with via direct downloads.

Suppose you pushed a kmod 309 version that was really a test. Within
the test if it detects an incompatible board it sets up a download for
the 304 versions, if applicable, plus some along side dummy versions
numbered 500 or something. Otherwise it does nothing and allows the
310 version to load a week later.


If you are using an installer script then it's doable, but then you also lose
all the advancements and convenience of a package manager with 

Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-24 Thread Phil Perry

On 24/01/13 09:37, jdow wrote:


Agreed. I figure I'll drop it. Please drop me a brief note directly how to
prevent simply automatically downloading 310 again.



yum erase kmod-nvidia nvidia-x11-drv
yum install kmod-nvidia-304xx nvidia-x11-drv-304xx

and reboot your system.

Then you will stay on the legacy 304.xx release and only get updates to 
the legacy driver.


Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-24 Thread Alan Bartlett
 On 24 January 2013 02:52, jdow j...@earthlink.net wrote:

 Um, 4 weeks is a trifle long for no Gnome or KDE. Ah well, I guess
 I wait. I seldom use the machine from a GUI anyway.

 It seems ElRepo may have screwed up.

 {^_^}

Appliction of sed 's/ElRepo may have/jdow has/' to the above will
result in a correct statement.

That statement is --

It seems jdow has screwed up.

@Connie  Pat -- As this is your product's main mailing list, would
you please take charge and advise the subscriber concerned, jdow, what
is  what is not acceptable behaviour.

Regards,
Alan.


Is there a kernel update for SL 6.2 coming up soon?

2013-01-23 Thread jdow

Is there a kernel update for SL 6.2 coming up soon?

It seems elrepo released a new set of nvidia modules that don't work
with the 2.6.32-279.19.1.el6.x86_64 kernel. That one only supports
through nvidia 304 and the download is 310.

{^_^}


Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-23 Thread Jamie Duncan
Red Hat is releasing RHEL 6.3 in approximately 4 weeks.


On Wed, Jan 23, 2013 at 11:20 AM, jdow j...@earthlink.net wrote:

 Is there a kernel update for SL 6.2 coming up soon?

 It seems elrepo released a new set of nvidia modules that don't work
 with the 2.6.32-279.19.1.el6.x86_64 kernel. That one only supports
 through nvidia 304 and the download is 310.

 {^_^}




-- 
Thanks,

Jamie Duncan
@jamieeduncan


Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-23 Thread Akemi Yagi
On Wed, Jan 23, 2013 at 8:20 AM, jdow j...@earthlink.net wrote:
 Is there a kernel update for SL 6.2 coming up soon?

 It seems elrepo released a new set of nvidia modules that don't work
 with the 2.6.32-279.19.1.el6.x86_64 kernel. That one only supports
 through nvidia 304 and the download is 310.

Copying a note from Phil Perry on the ELRepo list:

Just a quick note to say kmod-nvidia-304xx and nvidia-x11-drv-304xx
legacy packages have now been released to the main repositories for
both el5 and el6.

These packages support 6xxx and 7xxx based graphics cards.

http://elrepo.org/tiki/kmod-nvidia-304xx 

So, you'd need to install kmod-nvidia-304xx to stay with the 304 series.

Akemi


Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-23 Thread Nico Kadel-Garcia
On Wed, Jan 23, 2013 at 11:21 AM, Jamie Duncan jamie.e.dun...@gmail.com wrote:
 Red Hat is releasing RHEL 6.3 in approximately 4 weeks.


 On Wed, Jan 23, 2013 at 11:20 AM, jdow j...@earthlink.net wrote:

 Is there a kernel update for SL 6.2 coming up soon?

 It seems elrepo released a new set of nvidia modules that don't work
 with the 2.6.32-279.19.1.el6.x86_64 kernel. That one only supports
 through nvidia 304 and the download is 310.

 {^_^}

Don't you mean Red Hat is releasing RHEL 6.4 in a few weeks? They just
released 5.9  It's not clear how long it will take our fearless
leaders at Scientific Linux to update the base installation media and
OS repository to match, but if you stay up-to-date with the 6x
packages, you should be close enough to up-to-date that the 6.4
release will be pretty pain free. Even withing 6.3, SL has been very
good about keeping the kernels updated.


Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-23 Thread Jamie Duncan
s/6.3/6.4/g

sorry for the typo.


On Wed, Jan 23, 2013 at 1:51 PM, Nico Kadel-Garcia nka...@gmail.com wrote:

 On Wed, Jan 23, 2013 at 11:21 AM, Jamie Duncan jamie.e.dun...@gmail.com
 wrote:
  Red Hat is releasing RHEL 6.3 in approximately 4 weeks.
 
 
  On Wed, Jan 23, 2013 at 11:20 AM, jdow j...@earthlink.net wrote:
 
  Is there a kernel update for SL 6.2 coming up soon?
 
  It seems elrepo released a new set of nvidia modules that don't work
  with the 2.6.32-279.19.1.el6.x86_64 kernel. That one only supports
  through nvidia 304 and the download is 310.
 
  {^_^}

 Don't you mean Red Hat is releasing RHEL 6.4 in a few weeks? They just
 released 5.9  It's not clear how long it will take our fearless
 leaders at Scientific Linux to update the base installation media and
 OS repository to match, but if you stay up-to-date with the 6x
 packages, you should be close enough to up-to-date that the 6.4
 release will be pretty pain free. Even withing 6.3, SL has been very
 good about keeping the kernels updated.




-- 
Thanks,

Jamie Duncan
@jamieeduncan


Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-23 Thread jdow

Um, 4 weeks is a trifle long for no Gnome or KDE. Ah well, I guess
I wait. I seldom use the machine from a GUI anyway.

It seems ElRepo may have screwed up.

{^_^}

On 2013/01/23 08:21, Jamie Duncan wrote:

Red Hat is releasing RHEL 6.3 in approximately 4 weeks.


On Wed, Jan 23, 2013 at 11:20 AM, jdow j...@earthlink.net
mailto:j...@earthlink.net wrote:

Is there a kernel update for SL 6.2 coming up soon?

It seems elrepo released a new set of nvidia modules that don't work
with the 2.6.32-279.19.1.el6.x86_64 kernel. That one only supports
through nvidia 304 and the download is 310.

{^_^}




--
Thanks,

Jamie Duncan
@jamieeduncan



Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-23 Thread jdow

On 2013/01/23 08:51, Akemi Yagi wrote:

On Wed, Jan 23, 2013 at 8:20 AM, jdow j...@earthlink.net wrote:

Is there a kernel update for SL 6.2 coming up soon?

It seems elrepo released a new set of nvidia modules that don't work
with the 2.6.32-279.19.1.el6.x86_64 kernel. That one only supports
through nvidia 304 and the download is 310.


Copying a note from Phil Perry on the ELRepo list:

Just a quick note to say kmod-nvidia-304xx and nvidia-x11-drv-304xx
legacy packages have now been released to the main repositories for
both el5 and el6.

These packages support 6xxx and 7xxx based graphics cards.

http://elrepo.org/tiki/kmod-nvidia-304xx 

So, you'd need to install kmod-nvidia-304xx to stay with the 304 series.

Akemi


So I have to downgrade all four upgraded modules?
kmod-nvidia, both nvidia*, and vino modules?

I can do it. But they released 310 modules rather than 304 modules
yesterday.

{^_-}


Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-23 Thread Alan Bartlett
On 24 January 2013 02:52, jdow j...@earthlink.net wrote:
 Um, 4 weeks is a trifle long for no Gnome or KDE. Ah well, I guess
 I wait. I seldom use the machine from a GUI anyway.

 It seems ElRepo may have screwed up.

 {^_^}

I fail to see the significance -- or relevance -- of your last sentence.

Please remember this is the main support channel for Scientific Linux.

Alan.


Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-23 Thread jdow

On 2013/01/23 19:27, Alan Bartlett wrote:

On 24 January 2013 02:52, jdow j...@earthlink.net wrote:

Um, 4 weeks is a trifle long for no Gnome or KDE. Ah well, I guess
I wait. I seldom use the machine from a GUI anyway.

It seems ElRepo may have screwed up.

{^_^}


I fail to see the significance -- or relevance -- of your last sentence.

Please remember this is the main support channel for Scientific Linux.

Alan.


It's not this channel's support issue. I understand that. This is why
I wondered if 6.2 was going to have a kernel update.

ElRepo pushed the newer 310 NVidia modules before any appropriate kernel
appeared on SL2. So I have to back off. I simply wondered if waiting for
a new kernel was practical or not.

And that's been answered. ElRepo messed up pushing updates. (Or else
there should be a more recent kernel for 6.2 than what I am running,
2.6.32-279.19.1.el6.x86_64.)

{^_^}


Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-23 Thread Akemi Yagi
On Wed, Jan 23, 2013 at 8:04 PM, jdow j...@earthlink.net wrote:
 On 2013/01/23 19:27, Alan Bartlett wrote:

 I fail to see the significance -- or relevance -- of your last sentence.

 Please remember this is the main support channel for Scientific Linux.

 Alan.


 It's not this channel's support issue. I understand that. This is why
 I wondered if 6.2 was going to have a kernel update.

 ElRepo pushed the newer 310 NVidia modules before any appropriate kernel
 appeared on SL2. So I have to back off. I simply wondered if waiting for
 a new kernel was practical or not.

 And that's been answered. ElRepo messed up pushing updates. (Or else
 there should be a more recent kernel for 6.2 than what I am running,
 2.6.32-279.19.1.el6.x86_64.)

Let me post once again the link I provided for you earlier in this
thread. I'm afraid you missed it.

http://elrepo.org/tiki/kmod-nvidia-304xx

That page has a list of supported GPUs. This is all about the hardware
you have and the version of Nvidia's driver that supports it. Which
kernel version is _not_ relevant.

You may also want to check out this post on the ELRepo's mailing list:

http://lists.elrepo.org/pipermail/elrepo/2013-January/001587.html

I quoted an essential part of it in my earlier post as well. I
strongly suggest you subscribe to the ELRepo general mailing list. If
you still have questions about the Nvidia-related packages offered by
ELRepo, please ask on the ELRepo's list.

Akemi


Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-23 Thread jdow

On 2013/01/23 20:33, Akemi Yagi wrote:

On Wed, Jan 23, 2013 at 8:04 PM, jdow j...@earthlink.net wrote:

On 2013/01/23 19:27, Alan Bartlett wrote:



I fail to see the significance -- or relevance -- of your last sentence.

Please remember this is the main support channel for Scientific Linux.

Alan.



It's not this channel's support issue. I understand that. This is why
I wondered if 6.2 was going to have a kernel update.

ElRepo pushed the newer 310 NVidia modules before any appropriate kernel
appeared on SL2. So I have to back off. I simply wondered if waiting for
a new kernel was practical or not.

And that's been answered. ElRepo messed up pushing updates. (Or else
there should be a more recent kernel for 6.2 than what I am running,
2.6.32-279.19.1.el6.x86_64.)


Let me post once again the link I provided for you earlier in this
thread. I'm afraid you missed it.

http://elrepo.org/tiki/kmod-nvidia-304xx

That page has a list of supported GPUs. This is all about the hardware
you have and the version of Nvidia's driver that supports it. Which
kernel version is _not_ relevant.

You may also want to check out this post on the ELRepo's mailing list:

http://lists.elrepo.org/pipermail/elrepo/2013-January/001587.html

I quoted an essential part of it in my earlier post as well. I
strongly suggest you subscribe to the ELRepo general mailing list. If
you still have questions about the Nvidia-related packages offered by
ELRepo, please ask on the ELRepo's list.


With all due respect, Akemi, I'd like you to note two details.

First the message you point to is for version 304. ElRepo pushed 310.
Before that program load I was up to date with nVidia as well as kernel.
I'm not sure if I had 304 or earlier. Given the date, that is the version
I had loaded as of yesterday when 310 replaced it.

Second I get this message in the dmesg log from a reboot this morning.
===8---
nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
NVRM: The NVIDIA GeForce 7025 / nForce 630a GPU installed in this system is
NVRM:  supported through the NVIDIA 304.xx Legacy drivers. Please
NVRM:  visit http://www.nvidia.com/object/unix.html for more
NVRM:  information.  The 310.32 NVIDIA driver will ignore
NVRM:  this GPU.  Continuing probe...
NVRM: No NVIDIA graphics adapter found!
===8---

Apparently the kernel or something does NOT supported with 310. So pushing
the 310 was apparently an error of overoptimism for this system. I'd have
expected the RPM to take this into account. But this is an ElRepo issue
not one from here. So I've tried to be brief. I see I had to give up that
effort.

That said it appears I have to go back to 304 and turn off elrepo updates,
which is moderately inconvenient. The Nvidia 7025 is embedded on the
motherboard that is less than  a year old. So I figure SOMETHING screwed
up if it's no longer supported.

{^_^}


Re: Is there a kernel update for SL 6.2 coming up soon?

2013-01-23 Thread Phil Perry

On 24/01/13 06:04, jdow wrote:

On 2013/01/23 20:33, Akemi Yagi wrote:

On Wed, Jan 23, 2013 at 8:04 PM, jdow j...@earthlink.net wrote:

On 2013/01/23 19:27, Alan Bartlett wrote:



I fail to see the significance -- or relevance -- of your last
sentence.

Please remember this is the main support channel for Scientific Linux.

Alan.



It's not this channel's support issue. I understand that. This is why
I wondered if 6.2 was going to have a kernel update.

ElRepo pushed the newer 310 NVidia modules before any appropriate kernel
appeared on SL2. So I have to back off. I simply wondered if waiting for
a new kernel was practical or not.

And that's been answered. ElRepo messed up pushing updates. (Or else
there should be a more recent kernel for 6.2 than what I am running,
2.6.32-279.19.1.el6.x86_64.)


Not true.



Let me post once again the link I provided for you earlier in this
thread. I'm afraid you missed it.

http://elrepo.org/tiki/kmod-nvidia-304xx

That page has a list of supported GPUs. This is all about the hardware
you have and the version of Nvidia's driver that supports it. Which
kernel version is _not_ relevant.

You may also want to check out this post on the ELRepo's mailing list:

http://lists.elrepo.org/pipermail/elrepo/2013-January/001587.html

I quoted an essential part of it in my earlier post as well. I
strongly suggest you subscribe to the ELRepo general mailing list. If
you still have questions about the Nvidia-related packages offered by
ELRepo, please ask on the ELRepo's list.


With all due respect, Akemi, I'd like you to note two details.



With all due respect you are not listening to what people are telling 
you. Akemi is right and you are wrong.



First the message you point to is for version 304. ElRepo pushed 310.
Before that program load I was up to date with nVidia as well as kernel.
I'm not sure if I had 304 or earlier. Given the date, that is the version
I had loaded as of yesterday when 310 replaced it.



Here is the announcement I made back in November that the 310.xx series 
nvidia drivers were dropping support for older 6xxx and 7xxx based hardware:


http://lists.elrepo.org/pipermail/elrepo/2012-November/001525.html

We've been planning this migration for 2 months. May I suggest that if 
you are going to use elrepo packages then you subscribe to the elrepo 
mailing list where you will find out such important information first 
hand. It really is very low volume.



Second I get this message in the dmesg log from a reboot this morning.
===8---
nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
NVRM: The NVIDIA GeForce 7025 / nForce 630a GPU installed in this system is
NVRM: supported through the NVIDIA 304.xx Legacy drivers. Please
NVRM: visit http://www.nvidia.com/object/unix.html for more
NVRM: information. The 310.32 NVIDIA driver will ignore
NVRM: this GPU. Continuing probe...
NVRM: No NVIDIA graphics adapter found!
===8---

Apparently the kernel or something does NOT supported with 310. So pushing
the 310 was apparently an error of overoptimism for this system. I'd have
expected the RPM to take this into account. But this is an ElRepo issue
not one from here. So I've tried to be brief. I see I had to give up that
effort.



No, this is the nvidia driver telling you that your hardware is no 
longer supported. It even tells you that you need the NVIDIA 304.xx 
Legacy drivers.


The elrepo-packaged nvidia driver currently supports all kernels from 
SL6.1 through SL6.3.



That said it appears I have to go back to 304 and turn off elrepo updates,
which is moderately inconvenient. The Nvidia 7025 is embedded on the
motherboard that is less than a year old. So I figure SOMETHING screwed
up if it's no longer supported.



That's correct - you need to stay at the 304.xx driver as this is the 
*last* driver that will support your older hardware (7xxx based 
chipset). We released the legacy kmod-nvidia-304xx and 
nvidia-x11-drv-304xx packages to aid in this (see the thread linked 
above) and pushed them out to the main repo *before* we released the 
updated 310.xx series drivers.


Please uninstall the kmod-nvidia driver and install the 
kmod-nvidia-304xx and then you can continue to receive updates from elrepo.


Nothing screwed up, nvidia simply decided it was time to move on from 
supporting aging hardware (~8 years old?) in the current driver release.


Regards,

Phil