i915 DRI broken after upgrade to 7.0-Release

[Tom Evans]

On Wed, 2008-03-05 at 18:15 +0100, Oliver Fromme wrote:
> Tom Evans wrote:
>  > i810 driver is version 1.6.? 
>  > The next version of the driver is version 2.0, when it was renamed to
>  > intel. The latest 'intel' driver is the latest update of the i810
>  > driver.
> 
> OK, so that means the the "i810" driver is obsolete, right?
> So I deleted the i810 driver and re-installed the intel one.

	Yep

>  > I've attached my config for the intel driver, showing a dual screen
>  > setup for my laptop. The DRI has limits on the available virtual screen
>  > size, my two screens add up to a virtual of 2680x1050, which is above
>  > the maximum of 2048 in any dimension. Basically, if you want DRI, find
>  > the "Virtual" portion of the "Screen" and change it to "Virtual 2048
>  > 2048". If you need bigger, adjust it appropriately, but you will lose
>  > DRI.
> 
> My config is a lot simpler.  I don't have dual-screen,
> and I don't use a virtual screen (my window manager 
> already provides unlimited virtual desktops, which I
> think is more convenient than xorg's virtual screens).
> My resolution is 1400 x 1050.  It did work fine with
> pretty much the same configuration before the update.

	The advantage for me is that Virtual describes the total addressable
screen area. My laptop screen is 1400x1050, so this is all that is
configured in xorg. But by setting a larger Virtual, I can plug an
external monitor or projector into the VGA port, and enable it without
restarting X or interrupting any running X program simply by issuing
``xrandr --output VGA --mode 1280x1024 --left-of LVDS'' and then off
with ``xrandr --output VGA --off''. This is one of the main features of
the intel driver, xrandr 1.2 support and proper modesetting (so no more
915resolution hacks are required, if they were for you and the i810
driver).

> I've compared your config with mine, but I don't see
> any significant difference.  It still doesn't work.
> I tried various bit depths, but it only changes the
> number in the error message, now it is 0x7d:
> 
> libGL warning: 3D driver claims to not support visual 0x7d
> 
> which is, according to xdpyinfo:
> 
>     visual id:    0x7d
>     class:    TrueColor
>     depth:    32 planes
>     available colormap entries:    256 per subfield
>     red, green, blue masks:    0xff0000, 0xff00, 0xff
>     significant bits in color specification:    8 bits
> 

Yes, I also get this. I've not noticed any problems related to this
warning, and I also have seen this for my nvidia based linux box. I just
assumed it is informational, and wouldn't cause any major problems (I
may well be wrong :)

Cheers

Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20080305/a0a7d670/attachment.pgp