I've got a user with a legacy NVidia card. I've got kmod-nvidia. Last time I did an update, all I did was yum update --disableexcludes. This time, it fails, with Error: Package: nvidia-x11-drv-304xx-304.135-1.el7.elrepo.x86_64 (@elrepo) Requires: xorg-x11-server-Xorg <= 1.19.99 Removing: xorg-x11-server-Xorg-1.19.5-5.el7.x86_64 (@base) xorg-x11-server-Xorg = 1.19.5-5.el7 Updated By: xorg-x11-server-Xorg-1.20.1-5.1.el7.x86_64 (updates) xorg-x11-server-Xorg = 1.20.1-5.1.el7 Available: xorg-x11-server-Xorg-1.20.1-3.el7.x86_64 (base) xorg-x11-server-Xorg = 1.20.1-3.el7 Available: xorg-x11-server-Xorg-1.20.1-5.el7.x86_64 (updates) xorg-x11-server-Xorg = 1.20.1-5.el7
I'd appreciate any help understanding what this is telling me. It *looks* like it wants to update vidia-x11-drv-304xx-304.135-1.el7.elrepo.x86_64 with vidia-x11-drv-304xx-304.135-5.el7.elrepo.x86_64 (or maybe 135-6) and then it wants to replace the elrepo mods with base or updates.
Is this saying there's no update for the xorg-x11-server-Xorg (I don't see one) on elrepo? Does this mean I'll have to go back to the proprietary driver?
mark
On Tue, 18 Dec 2018, mark wrote:
I've got a user with a legacy NVidia card. I've got kmod-nvidia. Last time I did an update, all I did was yum update --disableexcludes. This time, it fails, with Error: Package: nvidia-x11-drv-304xx-304.135-1.el7.elrepo.x86_64 (@elrepo) Requires: xorg-x11-server-Xorg <= 1.19.99 Removing: xorg-x11-server-Xorg-1.19.5-5.el7.x86_64 (@base) xorg-x11-server-Xorg = 1.19.5-5.el7 Updated By: xorg-x11-server-Xorg-1.20.1-5.1.el7.x86_64 (updates) xorg-x11-server-Xorg = 1.20.1-5.1.el7 Available: xorg-x11-server-Xorg-1.20.1-3.el7.x86_64 (base) xorg-x11-server-Xorg = 1.20.1-3.el7 Available: xorg-x11-server-Xorg-1.20.1-5.el7.x86_64 (updates) xorg-x11-server-Xorg = 1.20.1-5.el7
I'd appreciate any help understanding what this is telling me. It *looks* like it wants to update vidia-x11-drv-304xx-304.135-1.el7.elrepo.x86_64 with vidia-x11-drv-304xx-304.135-5.el7.elrepo.x86_64 (or maybe 135-6) and then it wants to replace the elrepo mods with base or updates.
Is this saying there's no update for the xorg-x11-server-Xorg (I don't see one) on elrepo? Does this mean I'll have to go back to the proprietary driver?
You'd think kmod-nvidia-304xx-304.135-6.el7_6.elrepo.x86_64.rpm would put you into a happy place. Can you double check that you've got elrepo enabled and functional?
jh
John Hodrien wrote:
On Tue, 18 Dec 2018, mark wrote:
I've got a user with a legacy NVidia card. I've got kmod-nvidia. Last time I did an update, all I did was yum update --disableexcludes. This time, it fails, with Error: Package: nvidia-x11-drv-304xx-304.135-1.el7.elrepo.x86_64 (@elrepo) Requires: xorg-x11-server-Xorg <= 1.19.99 Removing: xorg-x11-server-Xorg-1.19.5-5.el7.x86_64 (@base) xorg-x11-server-Xorg = 1.19.5-5.el7 Updated By: xorg-x11-server-Xorg-1.20.1-5.1.el7.x86_64 (updates) xorg-x11-server-Xorg = 1.20.1-5.1.el7 Available: xorg-x11-server-Xorg-1.20.1-3.el7.x86_64 (base) xorg-x11-server-Xorg = 1.20.1-3.el7 Available: xorg-x11-server-Xorg-1.20.1-5.el7.x86_64 (updates) xorg-x11-server-Xorg = 1.20.1-5.el7
I'd appreciate any help understanding what this is telling me. It *looks* like it wants to update vidia-x11-drv-304xx-304.135-1.el7.elrepo.x86_64 with vidia-x11-drv-304xx-304.135-5.el7.elrepo.x86_64 (or maybe 135-6) and then it wants to replace the elrepo mods with base or updates.
Is this saying there's no update for the xorg-x11-server-Xorg (I don't see one) on elrepo? Does this mean I'll have to go back to the proprietary driver?
You'd think kmod-nvidia-304xx-304.135-6.el7_6.elrepo.x86_64.rpm would put you into a happy place. Can you double check that you've got elrepo enabled and functional?
I would have thought so, but yum list nvidia-x11* --disableexcludes=all
gives me Installed Packages nvidia-x11-drv-304xx.x86_64 304.135-1.el7.elrepo @elrepo Available Packages nvidia-x11-drv.x86_64 410.78-2.el7_6.elrepo elrepo nvidia-x11-drv-304xx-32bit.x86_64 304.135-1.el7.elrepo elrepo nvidia-x11-drv-32bit.x86_64 410.78-1.el7_6.elrepo elrepo nvidia-x11-drv-340xx.x86_64 340.107-1.el7.elrepo elrepo nvidia-x11-drv-340xx-32bit.x86_64 340.107-1.el7.elrepo elrepo nvidia-x11-drv-390xx.x86_64 390.87-1.el7_5.elrepo elrepo nvidia-x11-drv-390xx-32bit.x86_64 390.87-1.el7_5.elrepo elrepo nvidia-x11-drv-libs.i686 410.78-2.el7_6.elrepo elrepo nvidia-x11-drv-libs.x86_64 410.78-2.el7_6.elrepo elrepo
Also, as I think of it, I saw the same thing a week or so ago, trying to update another system.
Is there something missing?
mark
John Hodrien wrote:
On Tue, 18 Dec 2018, mark wrote:
Is there something missing?
An updated nvidia-x11-drv-304xx package. Have you queried this with elrepo? Is 304 a dead-end now given it's not had an update since September 2017?
(Please ignore mark, looking up the release date on the user's video card, beating his head on a desk, then going in to the team leader, and suggesting he consider buying new video cards, given cards that are > 10 years old....)
In the meantime, I need to support it. Oh, and I just tried to join the elrepo lists, and it told me my email address was banned. No clue, haven't tried that list for years, emailed the owners....
It starts to look like I need to go to proprietary....
mark
On Tue, 18 Dec 2018, mark wrote:
John Hodrien wrote:
On Tue, 18 Dec 2018, mark wrote:
Is there something missing?
An updated nvidia-x11-drv-304xx package. Have you queried this with elrepo? Is 304 a dead-end now given it's not had an update since September 2017?
(Please ignore mark, looking up the release date on the user's video card, beating his head on a desk, then going in to the team leader, and suggesting he consider buying new video cards, given cards that are > 10 years old....)
In the meantime, I need to support it. Oh, and I just tried to join the elrepo lists, and it told me my email address was banned. No clue, haven't tried that list for years, emailed the owners....
It starts to look like I need to go to proprietary....
I think you may need to do the opposite, and go nouveau.
jh
On 18/12/2018 16:26, mark wrote:
John Hodrien wrote:
On Tue, 18 Dec 2018, mark wrote:
Is there something missing?
An updated nvidia-x11-drv-304xx package. Have you queried this with elrepo? Is 304 a dead-end now given it's not had an update since September 2017?
(Please ignore mark, looking up the release date on the user's video card, beating his head on a desk, then going in to the team leader, and suggesting he consider buying new video cards, given cards that are > 10 years old....)
In the meantime, I need to support it. Oh, and I just tried to join the elrepo lists, and it told me my email address was banned. No clue, haven't tried that list for years, emailed the owners....
The elrepo mailing list receives a huge amount of spam attempts from .us tld, and as a consequence it is blocked. If you are using the same address you use for this list then you are collateral damage. I will whitelist your address for you.
Phil
On 18/12/2018 18:32, Phil Perry wrote:
On 18/12/2018 16:26, mark wrote:
John Hodrien wrote:
On Tue, 18 Dec 2018, mark wrote:
Is there something missing?
An updated nvidia-x11-drv-304xx package. Have you queried this with elrepo? Is 304 a dead-end now given it's not had an update since September 2017?
(Please ignore mark, looking up the release date on the user's video card, beating his head on a desk, then going in to the team leader, and suggesting he consider buying new video cards, given cards that are > 10 years old....)
In the meantime, I need to support it. Oh, and I just tried to join the elrepo lists, and it told me my email address was banned. No clue, haven't tried that list for years, emailed the owners....
The elrepo mailing list receives a huge amount of spam attempts from .us tld, and as a consequence it is blocked. If you are using the same address you use for this list then you are collateral damage. I will whitelist your address for you.
Hi Mark,
I tried to email you off list, and you rejected my mail, so looks like we're even now!
Looks like you tried to perform sender verification on a virtual role address and that's never going to end well, but hey, it's your server.
Phil Perry wrote:
On 18/12/2018 18:32, Phil Perry wrote:
On 18/12/2018 16:26, mark wrote:
John Hodrien wrote:
On Tue, 18 Dec 2018, mark wrote:
Is there something missing?
An updated nvidia-x11-drv-304xx package. Have you queried this with elrepo? Is 304 a dead-end now given it's not had an update since September 2017?
(Please ignore mark, looking up the release date on the user's video card, beating his head on a desk, then going in to the team leader, and suggesting he consider buying new video cards, given cards that are > 10 years old....)
In the meantime, I need to support it. Oh, and I just tried to join the elrepo lists, and it told me my email address was banned. No clue, haven't tried that list for years, emailed the owners....
The elrepo mailing list receives a huge amount of spam attempts from .us tld, and as a consequence it is blocked. If you are using the same address you use for this list then you are collateral damage. I will whitelist your address for you.
Hi Mark,
I tried to email you off list, and you rejected my mail, so looks like we're even now!
Looks like you tried to perform sender verification on a virtual role address and that's never going to end well, but hey, it's your server.
Say *what*? Let me assure you, I'm not doing that. I pay for hosting from HostMonster, so this suggests I need to talk to them....
mark
Phil Perry wrote:
On 18/12/2018 16:26, mark wrote:
John Hodrien wrote:
On Tue, 18 Dec 2018, mark wrote:
Is there something missing?
An updated nvidia-x11-drv-304xx package. Have you queried this with elrepo? Is 304 a dead-end now given it's not had an update since September 2017?
(Please ignore mark, looking up the release date on the user's video card, beating his head on a desk, then going in to the team leader, and suggesting he consider buying new video cards, given cards that are > 10 years old....)
In the meantime, I need to support it. Oh, and I just tried to join the elrepo lists, and it told me my email address was banned. No clue, haven't tried that list for years, emailed the owners....
The elrepo mailing list receives a huge amount of spam attempts from .us tld, and as a consequence it is blocked. If you are using the same address you use for this list then you are collateral damage. I will whitelist your address for you.
So... it blocked an *entire* legit TLD?! Why not just block .com...?
Thanks, Phil, much appreciated.
mark
John Hodrien wrote:
On Tue, 18 Dec 2018, mark wrote:
Is there something missing?
An updated nvidia-x11-drv-304xx package. Have you queried this with elrepo? Is 304 a dead-end now given it's not had an update since September 2017?
Ah, yes, my email address was blocked by elrepo, so I emailed list owners, and that bounced, because "known source of spam", and they don't even give me a link to find out about getting unblocked.
<rant> Blocking spam by blocking mailservers IS A 20 year old method that DOESN'T WORK ANY MORE, because most hosting providers host literally millions of domains. With that, no matter how big their staff is, it can't possibly keep up with all the people who create a burner account to send out spam, with the result that tens or hundreds of thousands of domains are blocked.
Go ahead, tell me what the hosting providers should do... or is it that everyone should pay for the expensive commercial hosting (when you're not a business site)....
No, the method is no good. Nor has it been good for almost 20 years. I'm pretty sure I've mentioned that one of them blocked that way... roadrunner for Chciago... which covered most of the home and SOHO users in all of Chicago, as they'd eaten all the smaller ISPs. </rant>
mark
Hi Mark,
On 18/12/2018 14:46, mark wrote:
I've got a user with a legacy NVidia card. I've got kmod-nvidia. Last time I did an update, all I did was yum update --disableexcludes. This time, it fails, with Error: Package: nvidia-x11-drv-304xx-304.135-1.el7.elrepo.x86_64 (@elrepo) Requires: xorg-x11-server-Xorg <= 1.19.99
I think the above is pretty clear. The legacy 304.xx nvidia driver only supports Xorg versions up to and including 1.19. EL7.6 ships with Xorg 1.20, so your old hardware is no longer supported on EL7 by nvidia.
Your choices are twofold:
1. Buy newer hardware that is supported. 2. Uninstall the proprietary nvidia packages and revert to using the nouveau driver.
Removing: xorg-x11-server-Xorg-1.19.5-5.el7.x86_64 (@base) xorg-x11-server-Xorg = 1.19.5-5.el7 Updated By: xorg-x11-server-Xorg-1.20.1-5.1.el7.x86_64 (updates) xorg-x11-server-Xorg = 1.20.1-5.1.el7 Available: xorg-x11-server-Xorg-1.20.1-3.el7.x86_64 (base) xorg-x11-server-Xorg = 1.20.1-3.el7 Available: xorg-x11-server-Xorg-1.20.1-5.el7.x86_64 (updates) xorg-x11-server-Xorg = 1.20.1-5.el7I'd appreciate any help understanding what this is telling me. It *looks* like it wants to update vidia-x11-drv-304xx-304.135-1.el7.elrepo.x86_64 with vidia-x11-drv-304xx-304.135-5.el7.elrepo.x86_64 (or maybe 135-6) and then it wants to replace the elrepo mods with base or updates.
Is this saying there's no update for the xorg-x11-server-Xorg (I don't see one) on elrepo? Does this mean I'll have to go back to the proprietary driver?
mark
-
John Hodrien -
mark -
Phil Perry