Re: Sandy Bridge problems

2012-02-17 Thread Matthieu Herrb
On Fri, Feb 17, 2012 at 09:28:16PM +1100, Rod Whitworth wrote: > > If you missed my post on misc@ you can find i > at: > http://old.nabble.com/Lenovo-E320%3A-strange-things-happen-with-X-td3332 > 0989.html > > It is really wierd trying to find where the bug lies in the E320. I > have found that t

Re: Sandy Bridge problems

2012-02-17 Thread Rod Whitworth
Heavily chopped to provide less clutter for busy people On Fri, 17 Feb 2012 10:29:11 +0100, Matthieu Herrb wrote: >> I did some reading about UMS vs KMS and noted a Phoronix page showing >> that for many of their benchmarks ran faster in UMS. Not that it will >> help us if we can't get UMS dri

Re: Sandy Bridge problems

2012-02-17 Thread Matthieu Herrb
On Fri, Feb 17, 2012 at 10:23:59AM +1100, Rod Whitworth wrote: > On Thu, 16 Feb 2012 10:43:28 -0800, Mike Larkin wrote: > > >Intel drivers later than 2.10 are KMS only, which OpenBSD does not support. > >The version in tree, based from CVS logs, is 2.9.1 with various backports > >added from later

Re: Sandy Bridge problems

2012-02-16 Thread Tomas Bodzar
On Fri, Feb 17, 2012 at 12:23 AM, Rod Whitworth wrote: > On Thu, 16 Feb 2012 10:43:28 -0800, Mike Larkin wrote: > >>Intel drivers later than 2.10 are KMS only, which OpenBSD does not support. >>The version in tree, based from CVS logs, is 2.9.1 with various backports >>added from later versions, a

Re: Sandy Bridge problems

2012-02-16 Thread Rod Whitworth
On Thu, 16 Feb 2012 10:43:28 -0800, Mike Larkin wrote: >Intel drivers later than 2.10 are KMS only, which OpenBSD does not support. >The version in tree, based from CVS logs, is 2.9.1 with various backports >added from later versions, and some one-off work done to support the >later Intel chips in

Re: Sandy Bridge problems

2012-02-16 Thread Mike Larkin
On Thu, Feb 16, 2012 at 10:59:03AM +1100, Rod Whitworth wrote: > Hi, > I ran into a problem with X in a new Lenovo E320 so I put out a query > on misc and got a rapid response from David Coppa which pointed out > that my problem was caused by the Intel Sandy Bridge stuff. I didn't > need to bug tec

Sandy Bridge problems

2012-02-15 Thread Rod Whitworth
Hi, I ran into a problem with X in a new Lenovo E320 so I put out a query on misc and got a rapid response from David Coppa which pointed out that my problem was caused by the Intel Sandy Bridge stuff. I didn't need to bug tech@ with that and misc answered me well enough. Why I am posting on tech