[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: intel X driver for etch+1/2



On Tue, May  6, 2008 at 15:52:47 +0200, Erik Mouw wrote:

> On Mon, May 05, 2008 at 07:31:33PM +0200, Julien Cristau wrote:
> > On Mon, May  5, 2008 at 17:44:40 +0200, Erik Mouw wrote:
> > 
> > > Two issues over here:
> > > 
> > > 1) AIGLX doesn't work:
> > > 
> > > drmOpenDevice: node name is /dev/dri/card0
> > > drmOpenDevice: open result is 12, (OK)
> > > drmOpenByBusid: Searching for BusID pci:0000:00:02.0
> > > drmOpenDevice: node name is /dev/dri/card0
> > > drmOpenDevice: open result is 12, (OK)
> > > drmOpenByBusid: drmOpenMinor returns 12
> > > drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
> > > (EE) AIGLX error: drmMap of framebuffer failed (Invalid argument)
> > > (EE) AIGLX: reverting to software rendering
> > 
> > Yeah, this seems broken in all the testing reports so far.  I'm not sure
> > I'll have time to investigate soon, but this is a bit worrying.
> 
> It means no GL acceleration (glxgears complains about going back to
> software rendering) and no compiz :( Would be nice if we got that
> supported, otherwise 915resolution+xorg vesa server gives about the
> same results.

Honestly 3d accel is very very low on my priority list for etch+1/2.  We
won't update mesa, so the newer chipsets won't have any support anyway.
I'd just like to understand the drmMap() error.

> I have attached an Xorg log from my backup. I hope this is enough
> information to figure out what's going wrong. I'm not at home and the
> machine is switched off so I can't run additional commands till friday.
> 
Doesn't give any info about the modes it detects/chooses, unfortunately.

Cheers,
Julien


Reply to: