Re: -CURRENT intel(4) problem

2009-03-05 Thread Nigel J. Taylor
I just encountered what looks like the same issue. Worked with OpenBSD v4.4, has been working since OpenBSD v3.2. I will try some of the suggestions. I also noticed that the /dev/drm0 is being removed, and then complaining it's not there any longer. Running MAKEDEV recreates /dev/drm0. Attached i

Re: -CURRENT intel(4) problem

2009-02-25 Thread J.C. Roberts
On Tue, 24 Feb 2009 23:38:43 + Owain Ainsworth wrote: > > I just singed up for freedesktop.org this morning, and I'm > > collecting the needed Xorg.0.log's with full debug info, > > descriptions and whatnot. It's going to take quite a while > > experiment with it and write up all the buggy be

Re: -CURRENT intel(4) problem

2009-02-24 Thread Owain Ainsworth
On Mon, Feb 23, 2009 at 08:21:35AM -0800, J.C. Roberts wrote: > On Mon, 23 Feb 2009 08:27:08 -0600 Marco Peereboom > wrote: > > > You are not the one paying the fixers unfortunately. The only > > influence you have is what Matthieu suggested. > > Thanks Marco. If I'm reading Mathieu and you cor

Re: -CURRENT intel(4) problem

2009-02-23 Thread Theo de Raadt
> After watching the old i810(4) driver work fine for me, and seeing > all the bug reports on the new intel(4) driver, I've got this bad > feeling that nobody cared to test it on the older chipsets... i.e. they > are not getting paid to care about "legacy" support. > > Would this be a correct asse

Re: -CURRENT intel(4) problem

2009-02-23 Thread J.C. Roberts
On Mon, 23 Feb 2009 08:27:08 -0600 Marco Peereboom wrote: > You are not the one paying the fixers unfortunately. The only > influence you have is what Matthieu suggested. Thanks Marco. If I'm reading Mathieu and you correctly, I have to take this upstream to get it fixed, and of course, this me

Re: -CURRENT intel(4) problem

2009-02-23 Thread Marco Peereboom
You are not the one paying the fixers unfortunately. The only influence you have is what Matthieu suggested. On Mon, Feb 23, 2009 at 06:10:39AM -0800, J.C. Roberts wrote: > On Mon, 23 Feb 2009 08:35:58 +0100 Matthieu Herrb > wrote: > > > On Sun, Feb 22, 2009 at 10:56 AM, J.C. Roberts > > wrote

Re: -CURRENT intel(4) problem

2009-02-23 Thread J.C. Roberts
On Mon, 23 Feb 2009 08:35:58 +0100 Matthieu Herrb wrote: > On Sun, Feb 22, 2009 at 10:56 AM, J.C. Roberts > wrote: > > > > > Is there anything else I could do to help fix this instability bug? > > > > Fill a bug to bugs.freedesktop.org (product Xorg) with as many details > as posslbe, and pray

Re: -CURRENT intel(4) problem

2009-02-22 Thread Matthieu Herrb
On Sun, Feb 22, 2009 at 10:56 AM, J.C. Roberts wrote: > > Is there anything else I could do to help fix this instability bug? > Fill a bug to bugs.freedesktop.org (product Xorg) with as many details as posslbe, and pray that the intel guys eventually take support for their older chips seriously.

Re: -CURRENT intel(4) problem

2009-02-22 Thread J.C. Roberts
On Sun, 22 Feb 2009 09:11:28 +0100 Matthieu Herrb wrote: > > I don't know much about X driver internals, but on the majority of > > failures to start, it seems the new intel(4) driver is failing to > > map memory properly. > > > > If you've got any ideas, or if there is something specific that yo

Re: -CURRENT intel(4) problem

2009-02-22 Thread Matthieu Herrb
On Sun, Feb 22, 2009 at 8:27 AM, J.C. Roberts wrote: > Hi list, > > I'm a having few issues with the new intel(4) driver in X on -CURRENT > using the snapshot from two days ago. > > The system is an IBM Netvista 8310-XXS and uses an integrated Intel > 82845G. The dmesg is below. The hardware itsel

-CURRENT intel(4) problem

2009-02-21 Thread J.C. Roberts
Hi list, I'm a having few issues with the new intel(4) driver in X on -CURRENT using the snapshot from two days ago. The system is an IBM Netvista 8310-XXS and uses an integrated Intel 82845G. The dmesg is below. The hardware itself is fine, and it previously ran 4.4-stable perfectly, albeit on