Re: after closing the lid and reopening it the screen remains blank

2010-09-10 Thread Andy Isaacson
On Sat, Sep 11, 2010 at 08:44:48AM +0900, Norbert Preining wrote: > On Fr, 10 Sep 2010, Andy Isaacson wrote: > > FWIW, 2.6.36-rc3-00396-gbe6200a suspend-to-ram works for me on GM45 > > I never said that it has anything to do with suspend to ram. Ah, sorry for misunderstanding. My

Re: after closing the lid and reopening it the screen remains blank

2010-09-10 Thread Andy Isaacson
On Fri, Sep 10, 2010 at 07:41:17AM +0900, Norbert Preining wrote: > running: 2.6.36-rc3+ (from git) on Integrated Graphics Chipset: Intel(R) GM45 > (Sony Vaio Z11) > Debian/unstable, so xserver 1.7.7, intel driver: 2.12.0 > > since some recent kernel I have the following problem: When closing the

[2.6.35-rc regression] i915: cursor corruption on Arrandale caused by 9b8c4a0b215e

2010-06-05 Thread Andy Isaacson
My x201s (Core i7 L640 according to /proc/cpuinfo) running -rc1 exhibits cursor corruption when changing the cursor image (such as when moving out of xterm onto the desktop). Bisection pointed to 9b8c4a0b215e and reverting that on top of 03cd373981 fixed the problem. I'm running fvwm2 with xterm

nouveau userspace bits for 2.6.34

2010-04-12 Thread Andy Isaacson
On Thu, Mar 04, 2010 at 10:18:03AM -0800, Linus Torvalds wrote: > (II) NOUVEAU(0): [drm] nouveau interface version: 0.0.16 > (EE) NOUVEAU(0): [drm] wrong version, expecting 0.0.15 > (EE) NOUVEAU(0): 879: So I've tried reading the thread and haven't found the answer to this questi

Re: [2.6.33-rc6-git regression] idr fix breaks Xorg

2010-02-03 Thread Andy Isaacson
On Wed, Feb 03, 2010 at 05:28:37PM -0800, Andy Isaacson wrote: > On my Dell Latitude e4300 commit 859ddf0974 ("idr: fix a critical > misallocation bug") causes Xorg to segfault with the following > backtrace: > > ... > (II) intel(0): Initializing HW Cursor > (II)

Re: [2.6.33-rc6-git regression] idr fix breaks Xorg

2010-02-03 Thread Andy Isaacson
On Thu, Feb 04, 2010 at 12:11:41PM +0900, Tejun Heo wrote: > On 02/04/2010 10:28 AM, Andy Isaacson wrote: > > On my Dell Latitude e4300 commit 859ddf0974 ("idr: fix a critical > > misallocation bug") causes Xorg to segfault with the following > > backtrace: > &

[2.6.33-rc6-git regression] idr fix breaks Xorg

2010-02-03 Thread Andy Isaacson
On my Dell Latitude e4300 commit 859ddf0974 ("idr: fix a critical misallocation bug") causes Xorg to segfault with the following backtrace: ... (II) intel(0): Initializing HW Cursor (II) intel(0): No memory allocations Backtrace: 0: /usr/bin/X11/X(xorg_backtrace+0x26) [0x4f00c6] 1: /usr/bin/X11/X

Re: BK for X11 development? (was Re: [Dri-devel] Re: Status of XFree86 4.4.0 integration?)

2004-03-09 Thread Andy Isaacson
[responding from my personal account to avoid the subscriber-only filter] On Tue, Mar 09, 2004 at 10:40:28PM +, Keith Whitwell wrote: > Andy Isaacson wrote: > > [perhaps DRI / fd.o should consider BitKeeper] > > For DRI at least, it's been discussed & rejected. My a

BK for X11 development? (was Re: [Dri-devel] Re: Status of XFree86 4.4.0 integration?)

2004-03-09 Thread Andy Isaacson
On Mon, Mar 08, 2004 at 12:29:05PM -0800, Keith Packard wrote: > Stablizing the tree and getting something shipping that people can > distribute is the first priority. I'm sure lots of people would like to > see Mesa/DRI development more closely tied to X driver development so that > there wasn

Re: [Dri-devel] New DRM design (was ATI I2C, MONID)

2004-02-09 Thread Andy Isaacson
On Tue, Feb 10, 2004 at 09:40:25AM +1100, Benjamin Herrenschmidt wrote: > bk clone bk://mesa3d.bkbits.net/drm > ERROR-Lock fail: possible permission problem. Oops. OK, fixed. Sorry for the inconvenience. (In the future, please let [EMAIL PROTECTED] know of such problems.) -andy -

Re: [Dri-devel] 32/64bit issues in ioctl struct passing

2003-03-04 Thread Andy Isaacson
On Tue, Mar 04, 2003 at 09:41:54AM -0800, Philip Brown wrote: > On Tue, Mar 04, 2003 at 01:27:28PM +, Alan Cox wrote: > > On Tue, 2003-03-04 at 08:22, Philip Brown wrote: > > > "unsigned long" is semi-unspecified, but is reasonably assumed to be > > > a 32-bit quantity. > > > > On all 64bit bi

Re: [Dri-devel] New ATI FireGL drivers announced

2002-11-22 Thread Andy Isaacson
On Fri, Nov 22, 2002 at 02:44:51PM +0100, Alexander Stohr wrote: > > What about support for other architectures, in particular PPC? > > The Apple as the #1 PPC platform (okay there might be several others) > does have an AGP slot and to my knowledge there is a nice ATI history > for the MacOS. Not

Re: [Dri-devel] NURBs + Autonormal peculiarity

2002-07-12 Thread Andy Isaacson
On Fri, Jul 12, 2002 at 07:54:11AM -0600, Brian Paul wrote: > Andy Isaacson wrote: > > On Thu, Jul 11, 2002 at 06:10:01PM -0400, Mike Westall wrote: > >>The attached program illustrates a shading anomaly > >>we have encountered while attempting to use autonormal &g

Re: [Dri-devel] NURBs + Autonormal peculiarity

2002-07-11 Thread Andy Isaacson
On Thu, Jul 11, 2002 at 06:10:01PM -0400, Mike Westall wrote: > The attached program illustrates a shading anomaly > we have encountered while attempting to use autonormal > in conjunction with nurbs. > > The shading of the sphere is seriously screwed up > while running with indirect renderin

Re: [Dri-devel] SIGSEGV on VT switch

2002-06-27 Thread Andy Isaacson
On Thu, Jun 27, 2002 at 11:48:40AM +0100, Sergey V. Udaltsov wrote: > > The problem is that stock gdb doesn't know about XFree86 modules. There > > are patched versions of gdb for that, but even so you can get more > > information by calling the LoaderPrintSymbol function for each of the > > addre

Re: [Dri-devel] GL_DECAL and texture corruption fixes for MGA driver

2001-06-14 Thread Andy Isaacson
On Wed, Jun 13, 2001 at 12:17:34PM -0400, Karl Lessard wrote: > Hi everybody, > > this patch fixes some problems in texturing in the mga driver. > > 1) It fixes a texture corruption problem, as the mga driver did not use > the right texture format in some case > ( I've seen that when an a

Re: [Dri-devel] linux drm version dont match

2001-06-04 Thread Andy Isaacson
On Sun, Jun 03, 2001 at 10:00:45AM +, Bobakitoo wrote: > hi, > Where do i get linux drm v3.0.? > dri as in xfree4.1.0 dont like drm in linux 2.4.5. > Is it the lates kernel... how can you all work on code > not yet aviable(until is somme where else) > > "[dri] mga.o kernel module versio

Re: [Dri-devel] DRI locking up on gears w/ mga

2001-05-31 Thread Andy Isaacson
On Thu, May 31, 2001 at 03:56:15AM -0500, Michael Ledet wrote: > I'm having problems with lockups while using dri with the mga driver. I > can easily reproduce the problems by doing any of the following: [snip] > In all cases I get the following message in syslog > >kernel: [drm:mga_fire_pri

[Dri-devel] -ldl seems to be required on latest Debian

2001-05-04 Thread Andy Isaacson
My development machine tracks debian unstable pretty closely (apt-get update && apt-get -u upgrade every few days), and recently when I had a chance to grab the latest DRI tree and built it, I had client programs failing to start with straum% gears gears: error while loading shared libraries: /da

Re: [Dri-devel] G400 and blending

2001-05-04 Thread Andy Isaacson
On Sat, May 05, 2001 at 01:32:07AM +1000, Gareth Hughes wrote: > Adam K Kirchhoff wrote: > > Speaking of which, I've been thinking about ordering Tribes2 and was > > wondering if there are any issues that we should be aware of? > > Go and buy this game. It rocks. Loki has done a great job, and

Re: [Dri-devel] Featurelist

2001-05-03 Thread Andy Isaacson
On Thu, May 03, 2001 at 04:26:00PM -0600, Brian Paul wrote: > Would it be better if the DRI User Guide were divided into a number of > separate HTML pages, instead of one long document? I could do that > with the sgml2html converter. I'm hesitant to create new documents > because that's more wor

Re: [Dri-devel] CVSUp access?

2001-05-03 Thread Andy Isaacson
On Thu, May 03, 2001 at 09:42:46AM -0700, Daryll Strauss wrote: > On Thu, May 03, 2001 at 10:09:46AM -0400, David Dawes wrote: > > On Wed, May 02, 2001 at 02:48:10PM -0500, Andy Isaacson wrote: > > > Does the DRI project offer CVSUp access? > > It doesn't, but I&#

[Dri-devel] CVSUp access?

2001-05-02 Thread Andy Isaacson
Does the DRI project offer CVSUp access? I'm collecting CVS trees in the interest of being able to do speedy local CVS operations, and CVSUp is the most efficient method of getting the repository. It would appear that the answer is no -- - there is no host cvsup.dri.sourceforge.net - cvs.dri.

Re: [Dri-devel] Anyone still using 2.3.x ?

2001-04-26 Thread Andy Isaacson
On Thu, Apr 26, 2001 at 04:10:00PM +0100, Alan Hourihane wrote: > I'm wondering if there is still anyone using Linux 2.3.x ? > > There's a bit of cruft still left in the drm kernel modules regarding > support for 2.3.x kernels and wondering whether I can remove this stuff. I say kill it. The ex