[arch-general] xorg 1.9 breaks

newer
Re: [arch-general] Xorg 1.9 - This...

older
[arch-general] Booting Arch under...

kurrata

30 Sep 2010 30 Sep '10

9:41 p.m.

latest xorg update (1.9) breaks it with nvidia-173xx drivers (173.14.27-3). Easy fix, just install previouse xorg

Show replies by date

Stefan Erik Wilkens

30 Sep 30 Sep

10:27 p.m.

2010/9/30 kurrata :

...

latest xorg update (1.9) breaks it with nvidia-173xx drivers (173.14.27-3). Easy fix, just install previouse xorg

AFAIK, current nvidia xorg support is as such: 96.xx range -> up to xserver 1.7, no mention of updating. 173xx range -> up to xserver 1.8, 1.9 support is in the pipeline nvidia range -> * yesterday, nvidia has confirmed that the 173xx range's support for xserver 1.9x is currently in the testing phase: http://www.nvnews.net/vbulletin/showthread.php?p=2325998 so perhaps wait for the 173 range to actually support the new xserver :)

kurrata

1 Oct 1 Oct

1:43 a.m.

On 10/01/10 01:27, Stefan Erik Wilkens wrote:

...

2010/9/30 kurrata:

...
latest xorg update (1.9) breaks it with nvidia-173xx drivers (173.14.27-3). Easy fix, just install previouse xorg

AFAIK, current nvidia xorg support is as such: 96.xx range -> up to xserver 1.7, no mention of updating. 173xx range -> up to xserver 1.8, 1.9 support is in the pipeline nvidia range -> *

yesterday, nvidia has confirmed that the 173xx range's support for xserver 1.9x is currently in the testing phase: http://www.nvnews.net/vbulletin/showthread.php?p=2325998

so perhaps wait for the 173 range to actually support the new xserver :)

Or we could just add conflict in pacman output if person has nvidia driver and stoping the upgrade. Or just write warning message that the new xorg doesn't support nvidia 173xx drivers and will result with break. That way others could upgrade to the new xorg and nvidia users wouldn't break their machine

Matthew Monaco

2:04 a.m.

On 09/30/2010 09:43 PM, kurrata wrote:

...

On 10/01/10 01:27, Stefan Erik Wilkens wrote:

...
2010/9/30 kurrata:

...
latest xorg update (1.9) breaks it with nvidia-173xx drivers (173.14.27-3). Easy fix, just install previouse xorg

AFAIK, current nvidia xorg support is as such: 96.xx range -> up to xserver 1.7, no mention of updating. 173xx range -> up to xserver 1.8, 1.9 support is in the pipeline nvidia range -> *

yesterday, nvidia has confirmed that the 173xx range's support for xserver 1.9x is currently in the testing phase: http://www.nvnews.net/vbulletin/showthread.php?p=2325998

so perhaps wait for the 173 range to actually support the new xserver :)

Or we could just add conflict in pacman output if person has nvidia driver and stoping the upgrade. Or just write warning message that the new xorg doesn't support nvidia 173xx drivers and will result with break. That way others could upgrade to the new xorg and nvidia users wouldn't break their machine

Typically how this has been handled is that the old nvidia-* drivers where removed from the repos after an xserver upgrade (nVidia lags the xserver every single time with the legacy drivers...) I'm not sure why the nvidia drivers are still in there with xserver 1.9.

Jan de Groot

7:42 a.m.

On Fri, 2010-10-01 at 04:43 +0300, kurrata wrote:

...

Or we could just add conflict in pacman output if person has nvidia driver and stoping the upgrade. Or just write warning message that the new xorg doesn't support nvidia 173xx drivers and will result with break. That way others could upgrade to the new xorg and nvidia users wouldn't break their machine

I removed that from xorg-server 1.9, simply because it's unmaintainable that way. I can't remember each and every driver that doesn't work with a new xorg-server version, and I don't have all the hardware to try that either. When we dropped catalyst, we added a versioned conflict on the released driver at that time. That appeared to work fine... until AMD released a newer version that STILL doesn't support the new Xorg server. The same thing will happen with Nvidia if we start doing that.

Stefan Erik Wilkens

11:09 a.m.

2010/10/1 kurrata :

...

On 10/01/10 01:27, Stefan Erik Wilkens wrote:

...
2010/9/30 kurrata:

...
latest xorg update (1.9) breaks it with nvidia-173xx drivers (173.14.27-3). Easy fix, just install previouse xorg

AFAIK, current nvidia xorg support is as such: 96.xx range -> up to xserver 1.7, no mention of updating. 173xx range -> up to xserver 1.8, 1.9 support is in the pipeline nvidia range -> *

yesterday, nvidia has confirmed that the 173xx range's support for xserver 1.9x is currently in the testing phase: http://www.nvnews.net/vbulletin/showthread.php?p=2325998

so perhaps wait for the 173 range to actually support the new xserver :)

Or we could just add conflict in pacman output if person has nvidia driver and stoping the upgrade. Or just write warning message that the new xorg doesn't support nvidia 173xx drivers and will result with break. That way others could upgrade to the new xorg and nvidia users wouldn't break their machine

breakage is expected with arch, we've been lucky that nvidia has been keeping legacy drivers up to date with xsever over the last few major changes and we'll simply have to wait for them to catch up now :) As said on the link I gave previously, the legacy driver is undergoing testing for 1.9, it can't be too long now. it seems non-arch to hold the user by the hand while the answer to possible breakage was literally one google away. and then there's the obvious issues this will bring when somebody forgets to properly update the list of excludes.. added man hours, more breakage due to improper lists and mass confusion about the state of drivers... though that may sound a little more apocalyptic than intended.

4964

Age (days ago)

4965

Last active (days ago)

List overview

Download

5 comments

4 participants

participants (4)

Jan de Groot
kurrata
Matthew Monaco
Stefan Erik Wilkens