[suggest] Newer driver version in dkms-nvidia-x11-drv?

[Toralf Lund]

A newer version of the NVIDIA driver would be nice.

I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

- Toralf

This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dkms-nvidia-x11-drv.spec
Url: http://lists.repoforge.org/pipermail/users/attachments/20100629/8ad5716a/attachment.pl

[Yury V. Zaytsev]

Hi!

Post by Toralf Lund
I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

You should migrate to

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

Post by Toralf Lund
This e-mail, including any attachments and response string, may
contain proprietary information which is confidential and may be
legally privileged. It is for the intended recipient only. If you are
not the intended recipient or transmission error has misdirected this
e-mail, please notify the author by return e-mail and delete this
message and any attachment immediately. If you are not the intended
recipient you must not use, disclose, distribute, forward, copy, print
or rely on this e-mail in any way except as permitted by the author.

Very appropriate for a public mailing list, I have to say.

[Toralf Lund]

Post by Yury V. Zaytsev
Hi!

Post by Toralf Lund
I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

You should migrate to
http://elrepo.org/tiki/kmod-nvidia

Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch
to kmod packages? Not something I care to have an opinion about, really.

Post by Yury V. Zaytsev

Post by Toralf Lund
This e-mail, including any attachments and response string, may
contain proprietary information which is confidential and may be
legally privileged. It is for the intended recipient only. If you are
not the intended recipient or transmission error has misdirected this
e-mail, please notify the author by return e-mail and delete this
message and any attachment immediately. If you are not the intended
recipient you must not use, disclose, distribute, forward, copy, print
or rely on this e-mail in any way except as permitted by the author.

Very appropriate for a public mailing list, I have to say.

You don't seriously think that I inserted that text? It's silly
automatic stuff at the server side, obviously.

- T


This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Dag Wieers]

Post by Toralf Lund

Post by Yury V. Zaytsev

Post by Toralf Lund
I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

You should migrate to
http://elrepo.org/tiki/kmod-nvidia

Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch to
kmod packages? Not something I care to have an opinion about, really.

On RHEL-based distributions kernel-agnostic kmod packages have a few
important advantages. RPMforge and the ELRepo project work together and we
converted all the dkms-packages to kmod-package in ELRepo.

I know there still is interest for dkms packages (especially from people
using custom kernels on top of RHEL/SL/CentOS) so I think it makes sense
to also provide/update dkms packages on demand.

[Yury V. Zaytsev]

Post by Dag Wieers
I know there still is interest for dkms packages (especially from
people using custom kernels on top of RHEL/SL/CentOS) so I think it
makes sense to also provide/update dkms packages on demand.

So the bottom line policy is still to update the old dkms stuff on
demand? Will you update this particular package or I do it for you?

Either way, it would be nicer to have a diff against:

http://svn.rpmforge.net/svn/trunk/rpms/dkms-nvidia-x11-drv/

[Yury V. Zaytsev]

Post by Dag Wieers
I know there still is interest for dkms packages (especially from
people using custom kernels on top of RHEL/SL/CentOS) so I think it
makes sense to also provide/update dkms packages on demand.

So the bottom line policy is still to update the old dkms stuff on
demand? Will you update this particular package or I do it for you?

Either way, it would be nicer to have a diff against:

http://svn.rpmforge.net/svn/trunk/rpms/dkms-nvidia-x11-drv/

[Yury V. Zaytsev]

Post by Dag Wieers
I know there still is interest for dkms packages (especially from
people using custom kernels on top of RHEL/SL/CentOS) so I think it
makes sense to also provide/update dkms packages on demand.

So the bottom line policy is still to update the old dkms stuff on
demand? Will you update this particular package or I do it for you?

Either way, it would be nicer to have a diff against:

http://svn.rpmforge.net/svn/trunk/rpms/dkms-nvidia-x11-drv/

[Yury V. Zaytsev]

Post by Dag Wieers
I know there still is interest for dkms packages (especially from
people using custom kernels on top of RHEL/SL/CentOS) so I think it
makes sense to also provide/update dkms packages on demand.

So the bottom line policy is still to update the old dkms stuff on
demand? Will you update this particular package or I do it for you?

Either way, it would be nicer to have a diff against:

http://svn.rpmforge.net/svn/trunk/rpms/dkms-nvidia-x11-drv/

[Yury V. Zaytsev]

Post by Dag Wieers
I know there still is interest for dkms packages (especially from
people using custom kernels on top of RHEL/SL/CentOS) so I think it
makes sense to also provide/update dkms packages on demand.

So the bottom line policy is still to update the old dkms stuff on
demand? Will you update this particular package or I do it for you?

Either way, it would be nicer to have a diff against:

http://svn.rpmforge.net/svn/trunk/rpms/dkms-nvidia-x11-drv/

[Yury V. Zaytsev]

Post by Toralf Lund
Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch
to kmod packages? Not something I care to have an opinion about, really.

Well, I wouldn't say it's off-topic, because it was spinned off awhile
ago by Dag (who is the primary guy behind RPMForge) and a bunch of other
packagers with a very narrow focus of only providing high-quality kABI
tracking kernel modules.

Since then RPMForge dkms packages have been deprecated, however, right
now they are kept as is, mainly for the reason that some packages have
not been migrated as of and few users might have some very compelling
reasons to stick to the old stuff which was used to be provided here. Of
course at some point this is something that has to be dealt with...

Therefore, unless you have a very important reason for using RPMForge
dkms packages you really ought to migrate to ELRepo kmod packages
instead.

Post by Toralf Lund
You don't seriously think that I inserted that text? It's silly
automatic stuff at the server side, obviously.

Wow, I was always under impression that people put this legalese junk in
their signatures on purpose, probably thinking that it actually does
have some value...

[Steve Huff]

Post by Yury V. Zaytsev
Therefore, unless you have a very important reason for using RPMForge
dkms packages you really ought to migrate to ELRepo kmod packages
instead.

cf. http://dag.wieers.com/blog/improved-rhel-centos-and-scientific-linux-hardware-support

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
http://five.sentenc.es

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20100629/994a976c/attachment.bin

[Toralf Lund]

Post by Toralf Lund
Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch
to kmod packages? Not something I care to have an opinion about, really.

[ ... ]
Since then RPMForge dkms packages have been deprecated, however, right
now they are kept as is, mainly for the reason that some packages have
not been migrated as of and few users might have some very compelling
reasons to stick to the old stuff which was used to be provided here. Of
course at some point this is something that has to be dealt with...

Well, if the dkms packages are deprecated, they should at least be
marked as such in some way. I mean, as far as I know, there is no direct
way to do this in the repository setup, but it might at least be
mentioned in informational texts. Right now, even the ElRepo
documentation for kmod-nvidia doesn't really say this in so many words.

Also, a somewhat smoother transition would probably be nice. It should
for instance not be necessary to uninstall dkms-nvidia, or deal with
repository conflicts. Not that I have encountered any of those, but
http://elrepo.org/tiki/kmod-nvidia suggests that they might exist...

--
- Toralf


This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Yury V. Zaytsev]

Post by Toralf Lund
Also, a somewhat smoother transition would probably be nice. It should
for instance not be necessary to uninstall dkms-nvidia, or deal with
repository conflicts. Not that I have encountered any of those, but
http://elrepo.org/tiki/kmod-nvidia suggests that they might exist...

As I mentioned, there might very well be a reason why you would
absolutely want to use DKMS instead of KMOD. I don't see a way of making
it possible to use both dkms-nvidia and kmod-nvidia at the same time. On
the other hand, kmod-nvidia should not obsolete dkms-nvidia for the
reason above.

What you can do right now is to uninstall dkms modules manually and then
install kmod modules you want to have. I don't see a problem with this,
other than that it's scarcely documented, which will be fixed at some
point.

[Toralf Lund]

Post by Yury V. Zaytsev

Post by Toralf Lund
Also, a somewhat smoother transition would probably be nice. It should
for instance not be necessary to uninstall dkms-nvidia, or deal with
repository conflicts. Not that I have encountered any of those, but
http://elrepo.org/tiki/kmod-nvidia suggests that they might exist...

As I mentioned, there might very well be a reason why you would
absolutely want to use DKMS instead of KMOD. I don't see a way of making
it possible to use both dkms-nvidia and kmod-nvidia at the same time. On
the other hand, kmod-nvidia should not obsolete dkms-nvidia for the
reason above.

One question, though, is will the kmod package come into the equation at
all if you have decided if you want to use DKMS? (Or will you just
forget about ELRepo, then?)

But yes, improved documentation would probably "fix" most issues. And
that should be documentation for RPMForge rather than (or in addition
to) ELRepo, I think.

Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one. Maybe it's new enough for my purpose, but I'm not able to test
right now. - I need an updated driver only for a specific
card/adapter/monitor combo on a different machine; the "old" dkms
release otherwise works just fine...

- Toralf



This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Yury V. Zaytsev]

Post by Toralf Lund
One question, though, is will the kmod package come into the equation at
all if you have decided if you want to use DKMS? (Or will you just
forget about ELRepo, then?)

Yes, just forget about ELRepo.

Post by Toralf Lund
But yes, improved documentation would probably "fix" most issues. And
that should be documentation for RPMForge rather than (or in addition
to) ELRepo, I think.

This is what I meant.

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one.

You can ping them and they will update it.

[Toralf Lund]

Post by Yury V. Zaytsev

Post by Toralf Lund
One question, though, is will the kmod package come into the equation at
all if you have decided if you want to use DKMS? (Or will you just
forget about ELRepo, then?)

Yes, just forget about ELRepo.

Well, if that's what people to in general, then it might be OK to let
kmod-nvidia or nvidia-x11-drv obsolete dkms-nvidia. Although you can
perhaps argue that the transition is somewhat too radical for an
automatic update...

Post by Yury V. Zaytsev

Post by Toralf Lund
But yes, improved documentation would probably "fix" most issues. And
that should be documentation for RPMForge rather than (or in addition
to) ELRepo, I think.

This is what I meant.

Good ;-)

Post by Yury V. Zaytsev

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one.

You can ping them and they will update it.

I was just told that it's being updated already, as in there is a
version in "elrepo-testing" (which I ought to have checked) that will
probably me moved to "elrepo" soon...

- Toralf



This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one.

You can ping them and they will update it.

I was just told that it's being updated already, as in there is a version in
"elrepo-testing" (which I ought to have checked) that will probably me moved
to "elrepo" soon...

Yes, ELRepo has a more professional approach to package-promotion. They
introduce new packages in testing, and promote them to stable after
sufficient testing (or after sufficient time).

But it requires people use testing and provide feedback, which is the most
difficult part in this setting.

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one.

You can ping them and they will update it.

I was just told that it's being updated already, as in there is a version in
"elrepo-testing" (which I ought to have checked) that will probably me moved
to "elrepo" soon...

Yes, ELRepo has a more professional approach to package-promotion. They
introduce new packages in testing, and promote them to stable after
sufficient testing (or after sufficient time).

But it requires people use testing and provide feedback, which is the most
difficult part in this setting.

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one.

You can ping them and they will update it.

I was just told that it's being updated already, as in there is a version in
"elrepo-testing" (which I ought to have checked) that will probably me moved
to "elrepo" soon...

Yes, ELRepo has a more professional approach to package-promotion. They
introduce new packages in testing, and promote them to stable after
sufficient testing (or after sufficient time).

But it requires people use testing and provide feedback, which is the most
difficult part in this setting.

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one.

You can ping them and they will update it.

I was just told that it's being updated already, as in there is a version in
"elrepo-testing" (which I ought to have checked) that will probably me moved
to "elrepo" soon...

Yes, ELRepo has a more professional approach to package-promotion. They
introduce new packages in testing, and promote them to stable after
sufficient testing (or after sufficient time).

But it requires people use testing and provide feedback, which is the most
difficult part in this setting.

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one.

You can ping them and they will update it.

I was just told that it's being updated already, as in there is a version in
"elrepo-testing" (which I ought to have checked) that will probably me moved
to "elrepo" soon...

Yes, ELRepo has a more professional approach to package-promotion. They
introduce new packages in testing, and promote them to stable after
sufficient testing (or after sufficient time).

But it requires people use testing and provide feedback, which is the most
difficult part in this setting.

[Toralf Lund]

Post by Yury V. Zaytsev

Post by Toralf Lund
One question, though, is will the kmod package come into the equation at
all if you have decided if you want to use DKMS? (Or will you just
forget about ELRepo, then?)

Yes, just forget about ELRepo.

Well, if that's what people to in general, then it might be OK to let
kmod-nvidia or nvidia-x11-drv obsolete dkms-nvidia. Although you can
perhaps argue that the transition is somewhat too radical for an
automatic update...

Post by Yury V. Zaytsev

Post by Toralf Lund
But yes, improved documentation would probably "fix" most issues. And
that should be documentation for RPMForge rather than (or in addition
to) ELRepo, I think.

This is what I meant.

Good ;-)

Post by Yury V. Zaytsev

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one.

You can ping them and they will update it.

I was just told that it's being updated already, as in there is a
version in "elrepo-testing" (which I ought to have checked) that will
probably me moved to "elrepo" soon...

- Toralf



This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Toralf Lund]

Post by Yury V. Zaytsev

Post by Toralf Lund
One question, though, is will the kmod package come into the equation at
all if you have decided if you want to use DKMS? (Or will you just
forget about ELRepo, then?)

Yes, just forget about ELRepo.

Well, if that's what people to in general, then it might be OK to let
kmod-nvidia or nvidia-x11-drv obsolete dkms-nvidia. Although you can
perhaps argue that the transition is somewhat too radical for an
automatic update...

Post by Yury V. Zaytsev

Post by Toralf Lund
But yes, improved documentation would probably "fix" most issues. And
that should be documentation for RPMForge rather than (or in addition
to) ELRepo, I think.

This is what I meant.

Good ;-)

Post by Yury V. Zaytsev

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one.

You can ping them and they will update it.

I was just told that it's being updated already, as in there is a
version in "elrepo-testing" (which I ought to have checked) that will
probably me moved to "elrepo" soon...

- Toralf



This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Toralf Lund]

Post by Yury V. Zaytsev

Post by Toralf Lund
One question, though, is will the kmod package come into the equation at
all if you have decided if you want to use DKMS? (Or will you just
forget about ELRepo, then?)

Yes, just forget about ELRepo.

Well, if that's what people to in general, then it might be OK to let
kmod-nvidia or nvidia-x11-drv obsolete dkms-nvidia. Although you can
perhaps argue that the transition is somewhat too radical for an
automatic update...

Post by Yury V. Zaytsev

Post by Toralf Lund
But yes, improved documentation would probably "fix" most issues. And
that should be documentation for RPMForge rather than (or in addition
to) ELRepo, I think.

This is what I meant.

Good ;-)

Post by Yury V. Zaytsev

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one.

You can ping them and they will update it.

I was just told that it's being updated already, as in there is a
version in "elrepo-testing" (which I ought to have checked) that will
probably me moved to "elrepo" soon...

- Toralf



This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Toralf Lund]

Post by Yury V. Zaytsev

Post by Toralf Lund
One question, though, is will the kmod package come into the equation at
all if you have decided if you want to use DKMS? (Or will you just
forget about ELRepo, then?)

Yes, just forget about ELRepo.

Well, if that's what people to in general, then it might be OK to let
kmod-nvidia or nvidia-x11-drv obsolete dkms-nvidia. Although you can
perhaps argue that the transition is somewhat too radical for an
automatic update...

Post by Yury V. Zaytsev

Post by Toralf Lund
But yes, improved documentation would probably "fix" most issues. And
that should be documentation for RPMForge rather than (or in addition
to) ELRepo, I think.

This is what I meant.

Good ;-)

Post by Yury V. Zaytsev

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one.

You can ping them and they will update it.

I was just told that it's being updated already, as in there is a
version in "elrepo-testing" (which I ought to have checked) that will
probably me moved to "elrepo" soon...

- Toralf



This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Akemi Yagi]

Apart from that, I notice that kmod-nvidia doesn't quite have the latest and
greatest release, either, although it's newer than the dkms-nvidia one.
Maybe it's new enough for my purpose, but I'm not able to test right now. -
I need an updated driver only for a specific card/adapter/monitor combo on a
different machine; the "old" dkms release otherwise works just fine...

You can find the latest and greatest release from ELRepo. Currently,
that latest and greatest version (256.35) is in elrepo-testing. It
will be promoted to the main repo shortly unless some problem is
identified.
Testing the stuff in the testing repo is strongly encouraged. More
testers, the faster the release. ?:-)
Akemi

I actually meant to post to the list rather than a PM...

Some amazing story... Phil Perry, who maintains the kmod-nvidia
package put the latest 256.35 into the testing repo within half an
hour of the release by Nvidia. This was possible because Nvidia had
this version as a release candidate and Phil had already packaged it
and we went through internal testing. As soon as he saw Nvidia making
it an official version, he published it and sent out the announcement
to the ELRepo M/L.

So, if you with to be current with ELRepo, please join the ELRepo mailing list.

Akemi

[Ned Slider]

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one. Maybe it's new enough for my purpose, but I'm not able to test
right now. - I need an updated driver only for a specific
card/adapter/monitor combo on a different machine; the "old" dkms
release otherwise works just fine...

Yes it does - 256.35 is in the testing repository and was released 2
hours after the release announcement was made upstream.

ELRepo releases the first official release of each major version update
to the testing repo while subsequent updates will go to the main
repository. Given the limited amount of public testing these drivers
have received upon release, we feel this is appropriate for an
Enterprise Linux distribution such as RHEL. That way more cautious users
can stay with a more proven driver series (195.36.31 in this case)
whilst those wanting the latest and greatest can always have the very
latest official release.

[Yury V. Zaytsev]

Post by Toralf Lund
One question, though, is will the kmod package come into the equation at
all if you have decided if you want to use DKMS? (Or will you just
forget about ELRepo, then?)

Yes, just forget about ELRepo.

Post by Toralf Lund
But yes, improved documentation would probably "fix" most issues. And
that should be documentation for RPMForge rather than (or in addition
to) ELRepo, I think.

This is what I meant.

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one.

You can ping them and they will update it.

[Akemi Yagi]

Apart from that, I notice that kmod-nvidia doesn't quite have the latest and
greatest release, either, although it's newer than the dkms-nvidia one.
Maybe it's new enough for my purpose, but I'm not able to test right now. -
I need an updated driver only for a specific card/adapter/monitor combo on a
different machine; the "old" dkms release otherwise works just fine...

You can find the latest and greatest release from ELRepo. Currently,
that latest and greatest version (256.35) is in elrepo-testing. It
will be promoted to the main repo shortly unless some problem is
identified.
Testing the stuff in the testing repo is strongly encouraged. More
testers, the faster the release. ?:-)
Akemi

I actually meant to post to the list rather than a PM...

Some amazing story... Phil Perry, who maintains the kmod-nvidia
package put the latest 256.35 into the testing repo within half an
hour of the release by Nvidia. This was possible because Nvidia had
this version as a release candidate and Phil had already packaged it
and we went through internal testing. As soon as he saw Nvidia making
it an official version, he published it and sent out the announcement
to the ELRepo M/L.

So, if you with to be current with ELRepo, please join the ELRepo mailing list.

Akemi

[Ned Slider]

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one. Maybe it's new enough for my purpose, but I'm not able to test
right now. - I need an updated driver only for a specific
card/adapter/monitor combo on a different machine; the "old" dkms
release otherwise works just fine...

Yes it does - 256.35 is in the testing repository and was released 2
hours after the release announcement was made upstream.

ELRepo releases the first official release of each major version update
to the testing repo while subsequent updates will go to the main
repository. Given the limited amount of public testing these drivers
have received upon release, we feel this is appropriate for an
Enterprise Linux distribution such as RHEL. That way more cautious users
can stay with a more proven driver series (195.36.31 in this case)
whilst those wanting the latest and greatest can always have the very
latest official release.

[Yury V. Zaytsev]

Post by Toralf Lund
One question, though, is will the kmod package come into the equation at
all if you have decided if you want to use DKMS? (Or will you just
forget about ELRepo, then?)

Yes, just forget about ELRepo.

Post by Toralf Lund
But yes, improved documentation would probably "fix" most issues. And
that should be documentation for RPMForge rather than (or in addition
to) ELRepo, I think.

This is what I meant.

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one.

You can ping them and they will update it.

[Akemi Yagi]

Apart from that, I notice that kmod-nvidia doesn't quite have the latest and
greatest release, either, although it's newer than the dkms-nvidia one.
Maybe it's new enough for my purpose, but I'm not able to test right now. -
I need an updated driver only for a specific card/adapter/monitor combo on a
different machine; the "old" dkms release otherwise works just fine...

You can find the latest and greatest release from ELRepo. Currently,
that latest and greatest version (256.35) is in elrepo-testing. It
will be promoted to the main repo shortly unless some problem is
identified.
Testing the stuff in the testing repo is strongly encouraged. More
testers, the faster the release. ?:-)
Akemi

I actually meant to post to the list rather than a PM...

Some amazing story... Phil Perry, who maintains the kmod-nvidia
package put the latest 256.35 into the testing repo within half an
hour of the release by Nvidia. This was possible because Nvidia had
this version as a release candidate and Phil had already packaged it
and we went through internal testing. As soon as he saw Nvidia making
it an official version, he published it and sent out the announcement
to the ELRepo M/L.

So, if you with to be current with ELRepo, please join the ELRepo mailing list.

Akemi

[Ned Slider]

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one. Maybe it's new enough for my purpose, but I'm not able to test
right now. - I need an updated driver only for a specific
card/adapter/monitor combo on a different machine; the "old" dkms
release otherwise works just fine...

Yes it does - 256.35 is in the testing repository and was released 2
hours after the release announcement was made upstream.

ELRepo releases the first official release of each major version update
to the testing repo while subsequent updates will go to the main
repository. Given the limited amount of public testing these drivers
have received upon release, we feel this is appropriate for an
Enterprise Linux distribution such as RHEL. That way more cautious users
can stay with a more proven driver series (195.36.31 in this case)
whilst those wanting the latest and greatest can always have the very
latest official release.

[Yury V. Zaytsev]

Post by Toralf Lund
One question, though, is will the kmod package come into the equation at
all if you have decided if you want to use DKMS? (Or will you just
forget about ELRepo, then?)

Yes, just forget about ELRepo.

Post by Toralf Lund
But yes, improved documentation would probably "fix" most issues. And
that should be documentation for RPMForge rather than (or in addition
to) ELRepo, I think.

This is what I meant.

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one.

You can ping them and they will update it.

[Akemi Yagi]

Apart from that, I notice that kmod-nvidia doesn't quite have the latest and
greatest release, either, although it's newer than the dkms-nvidia one.
Maybe it's new enough for my purpose, but I'm not able to test right now. -
I need an updated driver only for a specific card/adapter/monitor combo on a
different machine; the "old" dkms release otherwise works just fine...

You can find the latest and greatest release from ELRepo. Currently,
that latest and greatest version (256.35) is in elrepo-testing. It
will be promoted to the main repo shortly unless some problem is
identified.
Testing the stuff in the testing repo is strongly encouraged. More
testers, the faster the release. ?:-)
Akemi

I actually meant to post to the list rather than a PM...

Some amazing story... Phil Perry, who maintains the kmod-nvidia
package put the latest 256.35 into the testing repo within half an
hour of the release by Nvidia. This was possible because Nvidia had
this version as a release candidate and Phil had already packaged it
and we went through internal testing. As soon as he saw Nvidia making
it an official version, he published it and sent out the announcement
to the ELRepo M/L.

So, if you with to be current with ELRepo, please join the ELRepo mailing list.

Akemi

[Ned Slider]

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one. Maybe it's new enough for my purpose, but I'm not able to test
right now. - I need an updated driver only for a specific
card/adapter/monitor combo on a different machine; the "old" dkms
release otherwise works just fine...

Yes it does - 256.35 is in the testing repository and was released 2
hours after the release announcement was made upstream.

ELRepo releases the first official release of each major version update
to the testing repo while subsequent updates will go to the main
repository. Given the limited amount of public testing these drivers
have received upon release, we feel this is appropriate for an
Enterprise Linux distribution such as RHEL. That way more cautious users
can stay with a more proven driver series (195.36.31 in this case)
whilst those wanting the latest and greatest can always have the very
latest official release.

[Yury V. Zaytsev]

Post by Toralf Lund
One question, though, is will the kmod package come into the equation at
all if you have decided if you want to use DKMS? (Or will you just
forget about ELRepo, then?)

Yes, just forget about ELRepo.

Post by Toralf Lund
But yes, improved documentation would probably "fix" most issues. And
that should be documentation for RPMForge rather than (or in addition
to) ELRepo, I think.

This is what I meant.

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one.

You can ping them and they will update it.

[Akemi Yagi]

Apart from that, I notice that kmod-nvidia doesn't quite have the latest and
greatest release, either, although it's newer than the dkms-nvidia one.
Maybe it's new enough for my purpose, but I'm not able to test right now. -
I need an updated driver only for a specific card/adapter/monitor combo on a
different machine; the "old" dkms release otherwise works just fine...

You can find the latest and greatest release from ELRepo. Currently,
that latest and greatest version (256.35) is in elrepo-testing. It
will be promoted to the main repo shortly unless some problem is
identified.
Testing the stuff in the testing repo is strongly encouraged. More
testers, the faster the release. ?:-)
Akemi

I actually meant to post to the list rather than a PM...

Some amazing story... Phil Perry, who maintains the kmod-nvidia
package put the latest 256.35 into the testing repo within half an
hour of the release by Nvidia. This was possible because Nvidia had
this version as a release candidate and Phil had already packaged it
and we went through internal testing. As soon as he saw Nvidia making
it an official version, he published it and sent out the announcement
to the ELRepo M/L.

So, if you with to be current with ELRepo, please join the ELRepo mailing list.

Akemi

[Ned Slider]

Post by Toralf Lund
Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one. Maybe it's new enough for my purpose, but I'm not able to test
right now. - I need an updated driver only for a specific
card/adapter/monitor combo on a different machine; the "old" dkms
release otherwise works just fine...

Yes it does - 256.35 is in the testing repository and was released 2
hours after the release announcement was made upstream.

ELRepo releases the first official release of each major version update
to the testing repo while subsequent updates will go to the main
repository. Given the limited amount of public testing these drivers
have received upon release, we feel this is appropriate for an
Enterprise Linux distribution such as RHEL. That way more cautious users
can stay with a more proven driver series (195.36.31 in this case)
whilst those wanting the latest and greatest can always have the very
latest official release.

[Toralf Lund]

Post by Yury V. Zaytsev

Post by Toralf Lund
Also, a somewhat smoother transition would probably be nice. It should
for instance not be necessary to uninstall dkms-nvidia, or deal with
repository conflicts. Not that I have encountered any of those, but
http://elrepo.org/tiki/kmod-nvidia suggests that they might exist...

As I mentioned, there might very well be a reason why you would
absolutely want to use DKMS instead of KMOD. I don't see a way of making
it possible to use both dkms-nvidia and kmod-nvidia at the same time. On
the other hand, kmod-nvidia should not obsolete dkms-nvidia for the
reason above.

One question, though, is will the kmod package come into the equation at
all if you have decided if you want to use DKMS? (Or will you just
forget about ELRepo, then?)

But yes, improved documentation would probably "fix" most issues. And
that should be documentation for RPMForge rather than (or in addition
to) ELRepo, I think.

Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one. Maybe it's new enough for my purpose, but I'm not able to test
right now. - I need an updated driver only for a specific
card/adapter/monitor combo on a different machine; the "old" dkms
release otherwise works just fine...

- Toralf



This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Toralf Lund]

Post by Yury V. Zaytsev

Post by Toralf Lund
Also, a somewhat smoother transition would probably be nice. It should
for instance not be necessary to uninstall dkms-nvidia, or deal with
repository conflicts. Not that I have encountered any of those, but
http://elrepo.org/tiki/kmod-nvidia suggests that they might exist...

As I mentioned, there might very well be a reason why you would
absolutely want to use DKMS instead of KMOD. I don't see a way of making
it possible to use both dkms-nvidia and kmod-nvidia at the same time. On
the other hand, kmod-nvidia should not obsolete dkms-nvidia for the
reason above.

One question, though, is will the kmod package come into the equation at
all if you have decided if you want to use DKMS? (Or will you just
forget about ELRepo, then?)

But yes, improved documentation would probably "fix" most issues. And
that should be documentation for RPMForge rather than (or in addition
to) ELRepo, I think.

Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one. Maybe it's new enough for my purpose, but I'm not able to test
right now. - I need an updated driver only for a specific
card/adapter/monitor combo on a different machine; the "old" dkms
release otherwise works just fine...

- Toralf



This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Toralf Lund]

Post by Yury V. Zaytsev

Post by Toralf Lund
Also, a somewhat smoother transition would probably be nice. It should
for instance not be necessary to uninstall dkms-nvidia, or deal with
repository conflicts. Not that I have encountered any of those, but
http://elrepo.org/tiki/kmod-nvidia suggests that they might exist...

As I mentioned, there might very well be a reason why you would
absolutely want to use DKMS instead of KMOD. I don't see a way of making
it possible to use both dkms-nvidia and kmod-nvidia at the same time. On
the other hand, kmod-nvidia should not obsolete dkms-nvidia for the
reason above.

One question, though, is will the kmod package come into the equation at
all if you have decided if you want to use DKMS? (Or will you just
forget about ELRepo, then?)

But yes, improved documentation would probably "fix" most issues. And
that should be documentation for RPMForge rather than (or in addition
to) ELRepo, I think.

Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one. Maybe it's new enough for my purpose, but I'm not able to test
right now. - I need an updated driver only for a specific
card/adapter/monitor combo on a different machine; the "old" dkms
release otherwise works just fine...

- Toralf



This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Toralf Lund]

Post by Yury V. Zaytsev

Post by Toralf Lund
Also, a somewhat smoother transition would probably be nice. It should
for instance not be necessary to uninstall dkms-nvidia, or deal with
repository conflicts. Not that I have encountered any of those, but
http://elrepo.org/tiki/kmod-nvidia suggests that they might exist...

As I mentioned, there might very well be a reason why you would
absolutely want to use DKMS instead of KMOD. I don't see a way of making
it possible to use both dkms-nvidia and kmod-nvidia at the same time. On
the other hand, kmod-nvidia should not obsolete dkms-nvidia for the
reason above.

One question, though, is will the kmod package come into the equation at
all if you have decided if you want to use DKMS? (Or will you just
forget about ELRepo, then?)

But yes, improved documentation would probably "fix" most issues. And
that should be documentation for RPMForge rather than (or in addition
to) ELRepo, I think.

Apart from that, I notice that kmod-nvidia doesn't quite have the latest
and greatest release, either, although it's newer than the dkms-nvidia
one. Maybe it's new enough for my purpose, but I'm not able to test
right now. - I need an updated driver only for a specific
card/adapter/monitor combo on a different machine; the "old" dkms
release otherwise works just fine...

- Toralf



This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Yury V. Zaytsev]

Post by Toralf Lund
Also, a somewhat smoother transition would probably be nice. It should
for instance not be necessary to uninstall dkms-nvidia, or deal with
repository conflicts. Not that I have encountered any of those, but
http://elrepo.org/tiki/kmod-nvidia suggests that they might exist...

As I mentioned, there might very well be a reason why you would
absolutely want to use DKMS instead of KMOD. I don't see a way of making
it possible to use both dkms-nvidia and kmod-nvidia at the same time. On
the other hand, kmod-nvidia should not obsolete dkms-nvidia for the
reason above.

What you can do right now is to uninstall dkms modules manually and then
install kmod modules you want to have. I don't see a problem with this,
other than that it's scarcely documented, which will be fixed at some
point.

[Yury V. Zaytsev]

Post by Toralf Lund
Also, a somewhat smoother transition would probably be nice. It should
for instance not be necessary to uninstall dkms-nvidia, or deal with
repository conflicts. Not that I have encountered any of those, but
http://elrepo.org/tiki/kmod-nvidia suggests that they might exist...

As I mentioned, there might very well be a reason why you would
absolutely want to use DKMS instead of KMOD. I don't see a way of making
it possible to use both dkms-nvidia and kmod-nvidia at the same time. On
the other hand, kmod-nvidia should not obsolete dkms-nvidia for the
reason above.

What you can do right now is to uninstall dkms modules manually and then
install kmod modules you want to have. I don't see a problem with this,
other than that it's scarcely documented, which will be fixed at some
point.

[Yury V. Zaytsev]

Post by Toralf Lund
Also, a somewhat smoother transition would probably be nice. It should
for instance not be necessary to uninstall dkms-nvidia, or deal with
repository conflicts. Not that I have encountered any of those, but
http://elrepo.org/tiki/kmod-nvidia suggests that they might exist...

As I mentioned, there might very well be a reason why you would
absolutely want to use DKMS instead of KMOD. I don't see a way of making
it possible to use both dkms-nvidia and kmod-nvidia at the same time. On
the other hand, kmod-nvidia should not obsolete dkms-nvidia for the
reason above.

What you can do right now is to uninstall dkms modules manually and then
install kmod modules you want to have. I don't see a problem with this,
other than that it's scarcely documented, which will be fixed at some
point.

[Yury V. Zaytsev]

Post by Toralf Lund
Also, a somewhat smoother transition would probably be nice. It should
for instance not be necessary to uninstall dkms-nvidia, or deal with
repository conflicts. Not that I have encountered any of those, but
http://elrepo.org/tiki/kmod-nvidia suggests that they might exist...

As I mentioned, there might very well be a reason why you would
absolutely want to use DKMS instead of KMOD. I don't see a way of making
it possible to use both dkms-nvidia and kmod-nvidia at the same time. On
the other hand, kmod-nvidia should not obsolete dkms-nvidia for the
reason above.

What you can do right now is to uninstall dkms modules manually and then
install kmod modules you want to have. I don't see a problem with this,
other than that it's scarcely documented, which will be fixed at some
point.

[Steve Huff]

Post by Yury V. Zaytsev
Therefore, unless you have a very important reason for using RPMForge
dkms packages you really ought to migrate to ELRepo kmod packages
instead.

cf. http://dag.wieers.com/blog/improved-rhel-centos-and-scientific-linux-hardware-support

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
http://five.sentenc.es

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20100629/994a976c/attachment-0001.bin

[Toralf Lund]

Post by Toralf Lund
Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch
to kmod packages? Not something I care to have an opinion about, really.

[ ... ]
Since then RPMForge dkms packages have been deprecated, however, right
now they are kept as is, mainly for the reason that some packages have
not been migrated as of and few users might have some very compelling
reasons to stick to the old stuff which was used to be provided here. Of
course at some point this is something that has to be dealt with...

Well, if the dkms packages are deprecated, they should at least be
marked as such in some way. I mean, as far as I know, there is no direct
way to do this in the repository setup, but it might at least be
mentioned in informational texts. Right now, even the ElRepo
documentation for kmod-nvidia doesn't really say this in so many words.

Also, a somewhat smoother transition would probably be nice. It should
for instance not be necessary to uninstall dkms-nvidia, or deal with
repository conflicts. Not that I have encountered any of those, but
http://elrepo.org/tiki/kmod-nvidia suggests that they might exist...

--
- Toralf


This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Steve Huff]

Post by Yury V. Zaytsev
Therefore, unless you have a very important reason for using RPMForge
dkms packages you really ought to migrate to ELRepo kmod packages
instead.

cf. http://dag.wieers.com/blog/improved-rhel-centos-and-scientific-linux-hardware-support

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
http://five.sentenc.es

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20100629/994a976c/attachment-0002.bin

[Toralf Lund]

Post by Toralf Lund
Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch
to kmod packages? Not something I care to have an opinion about, really.

[ ... ]
Since then RPMForge dkms packages have been deprecated, however, right
now they are kept as is, mainly for the reason that some packages have
not been migrated as of and few users might have some very compelling
reasons to stick to the old stuff which was used to be provided here. Of
course at some point this is something that has to be dealt with...

Well, if the dkms packages are deprecated, they should at least be
marked as such in some way. I mean, as far as I know, there is no direct
way to do this in the repository setup, but it might at least be
mentioned in informational texts. Right now, even the ElRepo
documentation for kmod-nvidia doesn't really say this in so many words.

Also, a somewhat smoother transition would probably be nice. It should
for instance not be necessary to uninstall dkms-nvidia, or deal with
repository conflicts. Not that I have encountered any of those, but
http://elrepo.org/tiki/kmod-nvidia suggests that they might exist...

--
- Toralf


This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Steve Huff]

Post by Yury V. Zaytsev
Therefore, unless you have a very important reason for using RPMForge
dkms packages you really ought to migrate to ELRepo kmod packages
instead.

cf. http://dag.wieers.com/blog/improved-rhel-centos-and-scientific-linux-hardware-support

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
http://five.sentenc.es

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20100629/994a976c/attachment-0003.bin

[Toralf Lund]

Post by Toralf Lund
Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch
to kmod packages? Not something I care to have an opinion about, really.

[ ... ]
Since then RPMForge dkms packages have been deprecated, however, right
now they are kept as is, mainly for the reason that some packages have
not been migrated as of and few users might have some very compelling
reasons to stick to the old stuff which was used to be provided here. Of
course at some point this is something that has to be dealt with...

Well, if the dkms packages are deprecated, they should at least be
marked as such in some way. I mean, as far as I know, there is no direct
way to do this in the repository setup, but it might at least be
mentioned in informational texts. Right now, even the ElRepo
documentation for kmod-nvidia doesn't really say this in so many words.

Also, a somewhat smoother transition would probably be nice. It should
for instance not be necessary to uninstall dkms-nvidia, or deal with
repository conflicts. Not that I have encountered any of those, but
http://elrepo.org/tiki/kmod-nvidia suggests that they might exist...

--
- Toralf


This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Steve Huff]

Post by Yury V. Zaytsev
Therefore, unless you have a very important reason for using RPMForge
dkms packages you really ought to migrate to ELRepo kmod packages
instead.

cf. http://dag.wieers.com/blog/improved-rhel-centos-and-scientific-linux-hardware-support

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
http://five.sentenc.es

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
URL: <http://lists.repoforge.org/pipermail/users/attachments/20100629/994a976c/attachment.sig>

[Toralf Lund]

Post by Toralf Lund
Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch
to kmod packages? Not something I care to have an opinion about, really.

[ ... ]
Since then RPMForge dkms packages have been deprecated, however, right
now they are kept as is, mainly for the reason that some packages have
not been migrated as of and few users might have some very compelling
reasons to stick to the old stuff which was used to be provided here. Of
course at some point this is something that has to be dealt with...

Well, if the dkms packages are deprecated, they should at least be
marked as such in some way. I mean, as far as I know, there is no direct
way to do this in the repository setup, but it might at least be
mentioned in informational texts. Right now, even the ElRepo
documentation for kmod-nvidia doesn't really say this in so many words.

Also, a somewhat smoother transition would probably be nice. It should
for instance not be necessary to uninstall dkms-nvidia, or deal with
repository conflicts. Not that I have encountered any of those, but
http://elrepo.org/tiki/kmod-nvidia suggests that they might exist...

--
- Toralf


This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Dag Wieers]

Post by Toralf Lund

Post by Yury V. Zaytsev

Post by Toralf Lund
I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

You should migrate to
http://elrepo.org/tiki/kmod-nvidia

Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch to
kmod packages? Not something I care to have an opinion about, really.

On RHEL-based distributions kernel-agnostic kmod packages have a few
important advantages. RPMforge and the ELRepo project work together and we
converted all the dkms-packages to kmod-package in ELRepo.

I know there still is interest for dkms packages (especially from people
using custom kernels on top of RHEL/SL/CentOS) so I think it makes sense
to also provide/update dkms packages on demand.

[Yury V. Zaytsev]

Post by Toralf Lund
Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch
to kmod packages? Not something I care to have an opinion about, really.

Well, I wouldn't say it's off-topic, because it was spinned off awhile
ago by Dag (who is the primary guy behind RPMForge) and a bunch of other
packagers with a very narrow focus of only providing high-quality kABI
tracking kernel modules.

Since then RPMForge dkms packages have been deprecated, however, right
now they are kept as is, mainly for the reason that some packages have
not been migrated as of and few users might have some very compelling
reasons to stick to the old stuff which was used to be provided here. Of
course at some point this is something that has to be dealt with...

Therefore, unless you have a very important reason for using RPMForge
dkms packages you really ought to migrate to ELRepo kmod packages
instead.

Post by Toralf Lund
You don't seriously think that I inserted that text? It's silly
automatic stuff at the server side, obviously.

Wow, I was always under impression that people put this legalese junk in
their signatures on purpose, probably thinking that it actually does
have some value...

[Dag Wieers]

Post by Toralf Lund

Post by Yury V. Zaytsev

Post by Toralf Lund
I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

You should migrate to
http://elrepo.org/tiki/kmod-nvidia

Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch to
kmod packages? Not something I care to have an opinion about, really.

On RHEL-based distributions kernel-agnostic kmod packages have a few
important advantages. RPMforge and the ELRepo project work together and we
converted all the dkms-packages to kmod-package in ELRepo.

I know there still is interest for dkms packages (especially from people
using custom kernels on top of RHEL/SL/CentOS) so I think it makes sense
to also provide/update dkms packages on demand.

[Yury V. Zaytsev]

Post by Toralf Lund
Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch
to kmod packages? Not something I care to have an opinion about, really.

Well, I wouldn't say it's off-topic, because it was spinned off awhile
ago by Dag (who is the primary guy behind RPMForge) and a bunch of other
packagers with a very narrow focus of only providing high-quality kABI
tracking kernel modules.

Since then RPMForge dkms packages have been deprecated, however, right
now they are kept as is, mainly for the reason that some packages have
not been migrated as of and few users might have some very compelling
reasons to stick to the old stuff which was used to be provided here. Of
course at some point this is something that has to be dealt with...

Therefore, unless you have a very important reason for using RPMForge
dkms packages you really ought to migrate to ELRepo kmod packages
instead.

Post by Toralf Lund
You don't seriously think that I inserted that text? It's silly
automatic stuff at the server side, obviously.

Wow, I was always under impression that people put this legalese junk in
their signatures on purpose, probably thinking that it actually does
have some value...

[Dag Wieers]

Post by Toralf Lund

Post by Yury V. Zaytsev

Post by Toralf Lund
I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

You should migrate to
http://elrepo.org/tiki/kmod-nvidia

Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch to
kmod packages? Not something I care to have an opinion about, really.

On RHEL-based distributions kernel-agnostic kmod packages have a few
important advantages. RPMforge and the ELRepo project work together and we
converted all the dkms-packages to kmod-package in ELRepo.

I know there still is interest for dkms packages (especially from people
using custom kernels on top of RHEL/SL/CentOS) so I think it makes sense
to also provide/update dkms packages on demand.

[Yury V. Zaytsev]

Post by Toralf Lund
Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch
to kmod packages? Not something I care to have an opinion about, really.

Well, I wouldn't say it's off-topic, because it was spinned off awhile
ago by Dag (who is the primary guy behind RPMForge) and a bunch of other
packagers with a very narrow focus of only providing high-quality kABI
tracking kernel modules.

Since then RPMForge dkms packages have been deprecated, however, right
now they are kept as is, mainly for the reason that some packages have
not been migrated as of and few users might have some very compelling
reasons to stick to the old stuff which was used to be provided here. Of
course at some point this is something that has to be dealt with...

Therefore, unless you have a very important reason for using RPMForge
dkms packages you really ought to migrate to ELRepo kmod packages
instead.

Post by Toralf Lund
You don't seriously think that I inserted that text? It's silly
automatic stuff at the server side, obviously.

Wow, I was always under impression that people put this legalese junk in
their signatures on purpose, probably thinking that it actually does
have some value...

[Dag Wieers]

Post by Toralf Lund

Post by Yury V. Zaytsev

Post by Toralf Lund
I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

You should migrate to
http://elrepo.org/tiki/kmod-nvidia

Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch to
kmod packages? Not something I care to have an opinion about, really.

On RHEL-based distributions kernel-agnostic kmod packages have a few
important advantages. RPMforge and the ELRepo project work together and we
converted all the dkms-packages to kmod-package in ELRepo.

I know there still is interest for dkms packages (especially from people
using custom kernels on top of RHEL/SL/CentOS) so I think it makes sense
to also provide/update dkms packages on demand.

[Yury V. Zaytsev]

Post by Toralf Lund
Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch
to kmod packages? Not something I care to have an opinion about, really.

Well, I wouldn't say it's off-topic, because it was spinned off awhile
ago by Dag (who is the primary guy behind RPMForge) and a bunch of other
packagers with a very narrow focus of only providing high-quality kABI
tracking kernel modules.

Since then RPMForge dkms packages have been deprecated, however, right
now they are kept as is, mainly for the reason that some packages have
not been migrated as of and few users might have some very compelling
reasons to stick to the old stuff which was used to be provided here. Of
course at some point this is something that has to be dealt with...

Therefore, unless you have a very important reason for using RPMForge
dkms packages you really ought to migrate to ELRepo kmod packages
instead.

Post by Toralf Lund
You don't seriously think that I inserted that text? It's silly
automatic stuff at the server side, obviously.

Wow, I was always under impression that people put this legalese junk in
their signatures on purpose, probably thinking that it actually does
have some value...

[Toralf Lund]

Post by Yury V. Zaytsev
Hi!

Post by Toralf Lund
I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

You should migrate to
http://elrepo.org/tiki/kmod-nvidia

Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch
to kmod packages? Not something I care to have an opinion about, really.

Post by Yury V. Zaytsev

Post by Toralf Lund
This e-mail, including any attachments and response string, may
contain proprietary information which is confidential and may be
legally privileged. It is for the intended recipient only. If you are
not the intended recipient or transmission error has misdirected this
e-mail, please notify the author by return e-mail and delete this
message and any attachment immediately. If you are not the intended
recipient you must not use, disclose, distribute, forward, copy, print
or rely on this e-mail in any way except as permitted by the author.

Very appropriate for a public mailing list, I have to say.

You don't seriously think that I inserted that text? It's silly
automatic stuff at the server side, obviously.

- T


This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Toralf Lund]

Post by Yury V. Zaytsev
Hi!

Post by Toralf Lund
I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

You should migrate to
http://elrepo.org/tiki/kmod-nvidia

Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch
to kmod packages? Not something I care to have an opinion about, really.

Post by Yury V. Zaytsev

Post by Toralf Lund
This e-mail, including any attachments and response string, may
contain proprietary information which is confidential and may be
legally privileged. It is for the intended recipient only. If you are
not the intended recipient or transmission error has misdirected this
e-mail, please notify the author by return e-mail and delete this
message and any attachment immediately. If you are not the intended
recipient you must not use, disclose, distribute, forward, copy, print
or rely on this e-mail in any way except as permitted by the author.

Very appropriate for a public mailing list, I have to say.

You don't seriously think that I inserted that text? It's silly
automatic stuff at the server side, obviously.

- T


This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Toralf Lund]

Post by Yury V. Zaytsev
Hi!

Post by Toralf Lund
I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

You should migrate to
http://elrepo.org/tiki/kmod-nvidia

Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch
to kmod packages? Not something I care to have an opinion about, really.

Post by Yury V. Zaytsev

Post by Toralf Lund
This e-mail, including any attachments and response string, may
contain proprietary information which is confidential and may be
legally privileged. It is for the intended recipient only. If you are
not the intended recipient or transmission error has misdirected this
e-mail, please notify the author by return e-mail and delete this
message and any attachment immediately. If you are not the intended
recipient you must not use, disclose, distribute, forward, copy, print
or rely on this e-mail in any way except as permitted by the author.

Very appropriate for a public mailing list, I have to say.

You don't seriously think that I inserted that text? It's silly
automatic stuff at the server side, obviously.

- T


This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Toralf Lund]

Post by Yury V. Zaytsev
Hi!

Post by Toralf Lund
I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

You should migrate to
http://elrepo.org/tiki/kmod-nvidia

Hmmm... That's a completely different repository. Mentioning it here is
off-topic, don't you think? Or did you mean that rpmforge should switch
to kmod packages? Not something I care to have an opinion about, really.

Post by Yury V. Zaytsev

Post by Toralf Lund
This e-mail, including any attachments and response string, may
contain proprietary information which is confidential and may be
legally privileged. It is for the intended recipient only. If you are
not the intended recipient or transmission error has misdirected this
e-mail, please notify the author by return e-mail and delete this
message and any attachment immediately. If you are not the intended
recipient you must not use, disclose, distribute, forward, copy, print
or rely on this e-mail in any way except as permitted by the author.

Very appropriate for a public mailing list, I have to say.

You don't seriously think that I inserted that text? It's silly
automatic stuff at the server side, obviously.

- T


This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.

[Toralf Lund]

A newer version of the NVIDIA driver would be nice.

I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

- Toralf

This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dkms-nvidia-x11-drv.spec
Url: http://lists.repoforge.org/pipermail/users/attachments/20100629/8ad5716a/attachment-0001.pl

[Yury V. Zaytsev]

Hi!

Post by Toralf Lund
I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

You should migrate to

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

Post by Toralf Lund
This e-mail, including any attachments and response string, may
contain proprietary information which is confidential and may be
legally privileged. It is for the intended recipient only. If you are
not the intended recipient or transmission error has misdirected this
e-mail, please notify the author by return e-mail and delete this
message and any attachment immediately. If you are not the intended
recipient you must not use, disclose, distribute, forward, copy, print
or rely on this e-mail in any way except as permitted by the author.

Very appropriate for a public mailing list, I have to say.

[Toralf Lund]

A newer version of the NVIDIA driver would be nice.

I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

- Toralf

This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dkms-nvidia-x11-drv.spec
Url: http://lists.repoforge.org/pipermail/users/attachments/20100629/8ad5716a/attachment-0002.pl

[Yury V. Zaytsev]

Hi!

Post by Toralf Lund
I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

You should migrate to

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

Post by Toralf Lund
This e-mail, including any attachments and response string, may
contain proprietary information which is confidential and may be
legally privileged. It is for the intended recipient only. If you are
not the intended recipient or transmission error has misdirected this
e-mail, please notify the author by return e-mail and delete this
message and any attachment immediately. If you are not the intended
recipient you must not use, disclose, distribute, forward, copy, print
or rely on this e-mail in any way except as permitted by the author.

Very appropriate for a public mailing list, I have to say.

[Toralf Lund]

A newer version of the NVIDIA driver would be nice.

I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

- Toralf

This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dkms-nvidia-x11-drv.spec
Url: http://lists.repoforge.org/pipermail/users/attachments/20100629/8ad5716a/attachment-0003.pl

[Yury V. Zaytsev]

Hi!

Post by Toralf Lund
I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

You should migrate to

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

Post by Toralf Lund
This e-mail, including any attachments and response string, may
contain proprietary information which is confidential and may be
legally privileged. It is for the intended recipient only. If you are
not the intended recipient or transmission error has misdirected this
e-mail, please notify the author by return e-mail and delete this
message and any attachment immediately. If you are not the intended
recipient you must not use, disclose, distribute, forward, copy, print
or rely on this e-mail in any way except as permitted by the author.

Very appropriate for a public mailing list, I have to say.

[Toralf Lund]

A newer version of the NVIDIA driver would be nice.

I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

- Toralf

This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dkms-nvidia-x11-drv.spec
URL: <http://lists.repoforge.org/pipermail/users/attachments/20100629/8ad5716a/attachment.ksh>

[Yury V. Zaytsev]

Hi!

Post by Toralf Lund
I have a spec file that I've used to build a replacement of my own -
it's attached here. Note that I haven't really tested the x64 version,
but the 32-bit variant appears to work rather well.

You should migrate to

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

Post by Toralf Lund
This e-mail, including any attachments and response string, may
contain proprietary information which is confidential and may be
legally privileged. It is for the intended recipient only. If you are
not the intended recipient or transmission error has misdirected this
e-mail, please notify the author by return e-mail and delete this
message and any attachment immediately. If you are not the intended
recipient you must not use, disclose, distribute, forward, copy, print
or rely on this e-mail in any way except as permitted by the author.

Very appropriate for a public mailing list, I have to say.