xorg7.2 upgrade and glxgears

2007-05-12 Thread vehemens
I have the following error when running glxgears using the ATI driver: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 158 (DAMAGE) Minor opcode of failed request: 4 () Serial number of failed request: 37 Current

Re: xorg7.2 upgrade and glxgears

2007-05-12 Thread vehemens
On Saturday 12 May 2007 12:53:00 pm vehemens wrote: I have the following error when running glxgears using the ATI driver: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 158 (DAMAGE) Minor opcode of failed request: 4

is somebody working on a xorg 7.1 port to FreeBSD ?

2006-07-30 Thread vehemens
IMHO you should wait until we are ready to do a test-run on pointyhat. Otherwise you are going to be finding problems one-at-a-time that we can otherwise find out in bulk. How does one get access to the port code? To reiterate: there is very active work to get us to xorg7. It's not as trivial

is somebody working on a xorg 7.1 port to FreeBSD ?

2006-08-03 Thread vehemens
ssedov at mbsd.msk.ru wrote: You can install X.org from GIT repository - it works fine out-of-the-box on freebsd. Just install it under the different PREFIX (e.g. /usr/x11r7) and you will not have problems with uninstall. I don't appear to have the same luck as I'm having problems with several

Re: [is somebody working on a xorg 7.1 port to FreeBSD ?]

2006-08-05 Thread vehemens
On Thursday 03 August 2006 23:12, [EMAIL PROTECTED] wrote: What error message exactly you have got? The build procedure should look like this (assume we're installing in /work/x11r7: 1) downlod Xorg source, unpack 2) download mesa src 2) install devel/gnu-autoconf, devel/gnu-automake 3)

Re: Unhappy Xorg upgrade

2009-01-31 Thread vehemens
On Fri Jan 30 11:53:16 PST 2009, Peter Jeremy wrote: As a general note, this is the second time in a row that an X.org upgrade broke X for a significant number of people. IMO, this suggests that our approach to X.org upgrades needs significant changes (see below). X11 is a critical component for

Re: Unhappy Xorg upgrade

2009-01-31 Thread vehemens
On Saturday 31 January 2009 01:25:21 pm Alex Goncharov wrote: ,--- You/vehemens (Sat, 31 Jan 2009 11:53:58 -0800) * | In general when upgrading, you take your chances. If a port upgrade | fails, you should fall back to what worked. So, a *fundamental* (practically an OS component) port

Re: Unhappy Xorg upgrade

2009-02-01 Thread vehemens
On Saturday 31 January 2009 04:20:26 pm Alex Goncharov wrote: ,--- You/vehemens (Sat, 31 Jan 2009 13:54:42 -0800) * | On Saturday 31 January 2009 01:25:21 pm Alex Goncharov wrote: | So, a *fundamental* (practically an OS component) port is brought in | -- and it disables my system

Re: Unhappy Xorg upgrade

2009-02-01 Thread vehemens
On Sunday 01 February 2009 11:22:52 am Alex Goncharov wrote: | This has nothing to do with Linux. The issue is that that while src | has a stable versus current branch, there is no stable branch for | ports. The result is major updates are almost always problematic. Any data points to