Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Assistance Unsupported Software
  • Search

Xgl and i810

This forum covers all Gentoo-related software not officially supported by Gentoo. Ebuilds/software posted here might harm the health and stability of your system(s), and are not supported by Gentoo developers. Bugs/errors caused by ebuilds from overlays.gentoo.org are covered by this forum, too.
Post Reply
Advanced search
228 posts
  • Page 2 of 10
    • Jump to page:
  • Previous
  • 1
  • 2
  • 3
  • 4
  • 5
  • …
  • 10
  • Next
Author
Message
alanic
n00b
n00b
User avatar
Posts: 41
Joined: Fri Jan 13, 2006 3:43 am

  • Quote

Post by alanic » Mon Feb 27, 2006 10:34 pm

~~drolls on that xgl overlay
I'll get back to you in a couple of days after trying stuff.

I had had Xgl working flickery back in the day with mesa cvs. Later updating from cvs gave me a bunch of different errors, in the end that error you wrote "
BadLength (poly request too large or internal Xlib length error)" was the one closest to success for me.

DRM in 2.6.15 works for me but not many people, that was how I was able to run Xgl in the beginning. But it doesn't help anymore. I'll try 2.6.16, with the DRM inside or with x11-drm. As I said, a couple of days since I'm very busy these days.

Which ebuild is the one you maintain? Are you talking about the overlay in your sig?
Top
CoffeeBuzz
Apprentice
Apprentice
User avatar
Posts: 269
Joined: Wed Jun 15, 2005 7:11 pm
Location: Canada Eh.
Contact:
Contact CoffeeBuzz
Website

  • Quote

Post by CoffeeBuzz » Tue Feb 28, 2006 2:34 am

alanic wrote: Which ebuild is the one you maintain? Are you talking about the overlay in your sig?
correct
HP Pavilion zd7260us
Xgl Overlay: http://svn.xgl-coffee.org/xgl-coffee/trunk
Xgl Forums: http://forums.xgl-coffee.org
Top
RoninTT
n00b
n00b
Posts: 7
Joined: Tue Feb 28, 2006 7:17 am

  • Quote

Post by RoninTT » Tue Feb 28, 2006 8:28 am

Well I finally got XGL to work on my ASUS S52 laptop, with a i915 card.

The method that i used was first installing the stable version of Mesa. The copying the i915 driver from:

Code: Select all

/usr/lib/xorg/modules/dri/
Then I installed the Mesa version from the xgl-coffee overlay. With this version there is no DRI in X, but I'll get back to this. When the Mesa has compiled I copy the old i915 driver back and the dri works again. This solution works with XGL and compiz, all effect are there, but is very slow, so slow at the moment that I don't want to use it.

The problem with the new unstable Mesa version it that the driver for i915 is broken, at least for me. When I try to start glxgears with debugging on:

Code: Select all

LIBGL_DEBUG=verbose glxgears
I get this error:

Code: Select all

libGL: XF86DRIGetClientDriverName: 1.4.1 i915 (screen 0)
libGL: OpenDriver: trying /usr/lib/xorg/modules/dri/i915_dri.so
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 4, (OK)
drmOpenByBusid: drmOpenMinor returns 4
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
libGL error:
i915 DRI driver expected DDX version 1-1.5.x but got version 1.4.1
libGL warning: 3D driver returned no fbconfigs.
libGL error: InitDriver failed
libGL error: reverting to (slow) indirect rendering
I have also tried to get the newest snapshot from ?????? and run with this instead but I get the same error. If I run with the old driver then I down to about 400-500 FPS on glxgears. And some progs as mplayer can't be run. So I'm hoping that someone has a solution to this problem. It can't be true that FPS goes down when running XGL. One of my friends has XGL running with a ATI card, and he gets 2000 FPS more when in XGL.

I'm running with 2.6.16-rc1-nitro kernel, and have disabled dri in the kernel and loaded the newest snapshot instead. Hope this can help someone the a solution.
Top
the_mk
n00b
n00b
Posts: 28
Joined: Mon Feb 27, 2006 7:53 pm
Location: Italian and Proud

  • Quote

Post by the_mk » Tue Feb 28, 2006 1:14 pm

I make as RoninTT suggests, but when I start normal xorg+gnome (startx), glxinfo says I use DRI, but when i start
xgl+compiz+gnome I use software driver, no DRI, and It's slow.

945g, kernel: vanilla-2.6.16-r5 with 915driver statically copiled in

xorg.conf:

# File generated by xorgconfig.

#
# Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
#

# **********************************************************************
# Refer to the xorg.conf(5x) man page for details about the format of
# this file.
# **********************************************************************

# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the font modules
# Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"

# This loads the GLX module
Load "glx"
# This loads the DRI module
Load "dri"

EndSection

# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.

RgbPath "/usr/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
#

FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
# FontPath "/usr/lib/X11/fonts/local/"
# FontPath "/usr/lib/X11/fonts/misc/"
# FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/Speedo/"
# FontPath "/usr/lib/X11/fonts/Type1/"
# FontPath "/usr/lib/X11/fonts/TrueType/"
# FontPath "/usr/lib/X11/fonts/freefont/"
# FontPath "/usr/lib/X11/fonts/75dpi/"
# FontPath "/usr/lib/X11/fonts/100dpi/"

# The module search path. The default path is shown here.

# ModulePath "/usr/lib/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

# Option "NoTrapSignals"

# Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.

# Option "DontVTSwitch"

# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

# Option "DontZap"

# Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.

# Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

# Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

# Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

# Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

# Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

Identifier "Keyboard1"
Driver "kbd"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

# Option "Protocol" "Xqueue"

Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"

# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"

# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

# Option "XkbDisable"

Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "it"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "PS/2" # PS/2 Mouse
Option "Device" "/dev/psaux"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

# Option "Protocol" "Xqueue"

# Mouse-speed setting for PS/2 mouse.

# Option "Resolution" "256"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

# Option "BaudRate" "9600"
# Option "SampleRate" "150"

# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.

Option "ZAxisMapping" "4 5 6 7"

# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"

# ChordMiddle is an option for some 3-button Logitech mice

# Option "ChordMiddle"

EndSection


# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

Identifier "samsung"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync 31.5 - 64.3

# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 50-70

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"

# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.

# Chipset "generic"

# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.

# BusID "PCI:0:10:0"

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# Device configured by xorgconfig:

Section "Device"
Identifier "intel"
Driver "i810"
VideoRam 131072
#VideoRam 8192
# Insert Clocks lines here if appropriate
Option "NoAccel" "false"
Option "DRI" "true"
EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "intel"
Monitor "samsung"
DefaultDepth 24

Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
Identifier "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.

Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"

EndSection

Section "DRI"
Mode 0666
EndSection





To tun xgl+copiz I use the script described in wiki


Thanks.
Top
zapata
Tux's lil' helper
Tux's lil' helper
User avatar
Posts: 82
Joined: Sun Jun 26, 2005 9:51 am
Location: Hamburg / Germany

  • Quote

Post by zapata » Tue Feb 28, 2006 4:35 pm

Can someone post the Xgl command for i810?

when I start this from a term

Code: Select all

[root@zapatta] /root(9,6G free) # Xgl :1 -ac -accel glx:pbuffer -accel xv:pbuffer
I resive following message:

Code: Select all

No matching visual for __GLcontextMode with visual class = 4 (32770), nplanes = 24
No matching visual for __GLcontextMode with visual class = 4 (32770), nplanes = 24
Could not init font path element /usr/share/fonts/OTF, removing from list!
Could not init font path element /usr/share/fonts/CID/, removing from list!
Top
the_mk
n00b
n00b
Posts: 28
Joined: Mon Feb 27, 2006 7:53 pm
Location: Italian and Proud

  • Quote

Post by the_mk » Tue Feb 28, 2006 4:46 pm

zapata wrote:Can someone post the Xgl command for i810?

when I start this from a term

Code: Select all

[root@zapatta] /root(9,6G free) # Xgl :1 -ac -accel glx:pbuffer -accel xv:pbuffer
I resive following message:

Code: Select all

No matching visual for __GLcontextMode with visual class = 4 (32770), nplanes = 24
No matching visual for __GLcontextMode with visual class = 4 (32770), nplanes = 24
Could not init font path element /usr/share/fonts/OTF, removing from list!
Could not init font path element /usr/share/fonts/CID/, removing from list!

use 24 bit color depth
I use Xgl :1 -ac -accel glx:pbuffer -accel xv
Top
Peregrine
n00b
n00b
User avatar
Posts: 67
Joined: Mon Jun 16, 2003 11:10 am
Contact:
Contact Peregrine
Website

  • Quote

Post by Peregrine » Tue Feb 28, 2006 5:30 pm

I've also been looking into the messages reported by glxinfo. I would guess that the CVS version of Mesa is looking for the CVS version of the i810 xorg driver - from the changelog for that driver, they've moved up from v1.4.1.3 to v1.5.0.0.
Top
alanic
n00b
n00b
User avatar
Posts: 41
Joined: Fri Jan 13, 2006 3:43 am

  • Quote

Post by alanic » Thu Mar 02, 2006 12:22 am

with drm from 2.6.15,
CoffeeBuzz wrote: So let me get this straight, no one here has had Xgl working with mesa 6.4.3 (cvs)?

All you get is this:

X Error of failed request: BadLength (poly request too large or internal Xlib length error)
Major opcode of failed request: 159 (GLX)
Minor opcode of failed request: 1 (X_GLXRender)
Serial number of failed request: 93
Current serial number in output stream: 94
yes.
CoffeeBuzz wrote: But if you use mesa 6.4.2-r1 it works? Because DRM in 2.6.15 or xorg7 isnt up to snuff. ?
No, then it gives:

Code: Select all

 ~ $ LD_LIBRARY_PATH=/usr/lib/opengl/xorg-x11/lib/ DISPLAY=:1 compiz gconf
compiz: GLX_EXT_texture_from_pixmap is missing
compiz: Failed to manage screen: 0
compiz: No managable screens found on display :1

~ $ LD_LIBRARY_PATH=/usr/lib/opengl/xorg-x11/lib/ DISPLAY=:1 glxcompmgr
glxcompmgr: GLX_MESA_render_texture is missing
glxcompmgr: Failed to manage screen: 0
glxcompmgr: No managable screens found on display :1
I read the wiki and reemerged, but it didn't help. Btw, I have only xorg-x11 in eselect opengl list. I guess that is not a problem.

I'll give a shot to 2.6.16 nitro-sources.
Top
alanic
n00b
n00b
User avatar
Posts: 41
Joined: Fri Jan 13, 2006 3:43 am

  • Quote

Post by alanic » Thu Mar 02, 2006 1:29 am

YAY FOR RoninTT!

Copying the old drivers made xgl work again as he said. And I didn't have to upgrade my kernel, I'm stlill on 2.6.15:) And it seem like it's not flickering now in windowed mode(800x600). I'll try fullscreen and see how it goes.

Btw, kde-window-decorator does not work yet, I use glxcompmgr. (I don't have gnome)

Edit: It's still darn flickery in fullscreen mode(1024x768). I guess we'll have to wait till they fix the driver. But still, it's cool:)
Top
monrad
n00b
n00b
Posts: 1
Joined: Thu Mar 02, 2006 2:49 am

  • Quote

Post by monrad » Thu Mar 02, 2006 2:56 am

I tried to make a cvs build of x11-drivers/xf86-video-i810 and after 30 mins of work i had it check out the code and compiled with a couple of tricks but when i try to use it with xorg or xgl it just freezes the screen, maybe because of some randr changes maybe because of other stuff.
I hope we get this working soon on the i810 that could just be cool.
Top
alanic
n00b
n00b
User avatar
Posts: 41
Joined: Fri Jan 13, 2006 3:43 am

  • Quote

Post by alanic » Thu Mar 02, 2006 5:56 am

CoffeeBuzz wrote:If you use 2.6.16, mesa 6.4.3 works with xgl?
Yes, I just confirmed it. Although it was even more flickery.
Top
RoninTT
n00b
n00b
Posts: 7
Joined: Tue Feb 28, 2006 7:17 am

  • Quote

Post by RoninTT » Thu Mar 02, 2006 1:46 pm

I still haven't gotten a Mesa cvs working with my card :( all the versions I have tried have broken drivers.

So I've started looking into the AIGLX also, but when I follow this guide:

http://gentoo-wiki.com/HOWTO_AIGLX

And I compile the new xorg-server I get a compiler error, just wanted to hear if any of you guys have tried this?

Also Coffee if there is any info you need to build a working Mesa for us Intel guys don't heasitate to ask.[/url]
Top
kanttu
n00b
n00b
Posts: 58
Joined: Wed Aug 31, 2005 8:45 pm

  • Quote

Post by kanttu » Thu Mar 02, 2006 3:20 pm

I would like to try XGL on my Fujitsu-Siemens S6010 laptop. It's got i810 or i830 gfx adapter but I get only 600fps from glxgears with DRI enabled, though I know glxgears isn't a real benchmark. But what do you think, is it even worth to try?
AMD Athlon64 3500+
ASUS A8N-SLI deluxe
PNY GeForce 6800GT
Top
stable
n00b
n00b
Posts: 5
Joined: Sun Mar 05, 2006 8:37 am

Ah... the black windows won't go away...

  • Quote

Post by stable » Sun Mar 05, 2006 10:22 am

Greetings!

I've been having trouble getting past the black windows problem. I'm using coffeebuzz's overlay on Linux 2.6.15-suspend2-r6 which compiled cleanly after using the vanilla 2.6.16-rc4's i915_drm.h header and replacing the new mesa DRI drivers with their elder counterparts. The problem now is that opengl applications are all rendered as solid black windows, which means that when I run compiz, the whole screen turns black and the only visible thing is the mouse pointer. While I can't see a thing, glxgears still reports a frame rate 50% higher than usual.

My current xorg.conf file follows:

Code: Select all

Section "Files"
  FontPath      "/usr/share/fonts/misc/"
  FontPath      "/usr/share/fonts/TTF/"
  FontPath      "/usr/share/fonts/Type1/"
  FontPath      "/usr/share/fonts/CID/"
  FontPath      "/usr/share/fonts/75dpi/"
  FontPath      "/usr/share/fonts/100dpi/"
  FontPath      "/usr/share/fonts/truetype/"
  ModulePath    "/usr/lib/xorg/modules"
EndSection

Section "Module"
  Load  "record"
  Load  "extmod"
  Load  "dbe"
  Load  "glx"
  Load  "dri"
  Load  "GLcore"
  Load  "xtrap"
  Load  "freetype"
  Load  "type1"
EndSection

Section "DRI"
  Mode          0660
EndSection

Section "InputDevice"
  Identifier            "Keyboard"
  Driver                "kbd"
  Option  "AutoRepeat"  "250 30"
  Option  "LeftAlt"     "Meta"
  Option  "RightAlt"    "ModeShift"
  Option  "XkbModel"    "microsoft"
  Option  "XkbLayout"   "pt"
EndSection

Section "InputDevice"
  Identifier              "Mouse"
  Driver                  "mouse"
  Option  "Protocol"      "IMPS/2"
  Option  "Device"        "/dev/input/mice"
  Option  "ZAxisMapping"  "4 5"
EndSection

Section "Monitor"
  Identifier    "CRT"
  VendorName    "Monitor Vendor"
  ModelName     "Monitor Model"
  HorizSync     31.5 - 80.5
  VertRefresh   50 - 60
  Option        "NoDDC"
  Option        "DPMS"
EndSection

Section "Device"
  Identifier    "CRTHead"
  Driver        "i810"
  VendorName    "Intel"
  BoardName     "Intel i915"
  VideoRam      65536
  BusID         "PCI:0:2:0"
  Screen        0
  Option        "DevicePresence" "yes"
EndSection

Section "Screen"
  Identifier "CRTScreen"
  Device     "CRTHead"
  Monitor    "CRT"
  DefaultDepth  24
  SubSection "Display"
    Virtual     1024 768
    Depth       24
  EndSubSection
EndSection

Section "ServerLayout"
  Identifier      "Layout"
  Screen          "CRTScreen" 0 0
  InputDevice     "Mouse" "CorePointer"
  InputDevice     "Keyboard" "CoreKeyboard"
EndSection

Section "Extensions"
  Option "Composite" "true"
EndSection
And below are the warning and error messages from the Xorg log file:

Code: Select all

(WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found
(WW) I810(0): Bad V_BIOS checksum
(WW) I810(0): Bad V_BIOS checksum
(WW) I810(0): Bad V_BIOS checksum
(WW) I810(0): Extended BIOS function 0x5f05 failed.
(WW) I810(0): Successfully set original devices
(WW) I810(0): Setting the original video mode instead of restoring
(WW) I810(0): Extended BIOS function 0x5f05 failed.
(WW) I810(0): Successfully set original devices (2)
Nevermind the "No matching Device section for instance" warning, it's referring to a video device whose functionality I'm yet to discover (the dual head setup on this chip uses two framebuffers on the same BusID).

Any clues?

Thanks in advance.

EDIT

Looking at the original poster's lspci output I can see that there are at least two different Intel chips using the i915 driver, which may lead to confusion.
I have an Intel chipset on my laptop and I use the i810 driver with the i915 kernel module. Here is the output of lspci:

Code: Select all

00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
My lspci outputs the following:

Code: Select all

00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
EDIT

I have a fully functional and accelerated Xgl+compiz installation now. The black windows problem is in fact a glitch, it appears that the driver is not redrawing the screen as often as it should, but it's easy to get over this problem: passing a terminal window over Xgl will force it to redraw its contents correctly. If you switch to Xgl+compiz permanently (which I did), the gnome panels and the wallpaper will force Xgl to redraw the whole screen, so the glitch will be gone while your desktop loads.

Glxgears' frame rate information varies drastically from 1300+fps to 300+fps depending on how many programs I have running (and I guess that's to be expected). Notice however that there ARE slowdowns when dragging, scrolling, or playing with the wobbly effect on large windows, which is particularly noticeable while browsing since that requires a lot of scrolling (hint: disabling smooth scrolling on firefox helps a lot).
Last edited by stable on Sat Mar 11, 2006 7:55 am, edited 1 time in total.
Top
plesho
n00b
n00b
User avatar
Posts: 10
Joined: Tue Dec 27, 2005 10:43 am
Contact:
Contact plesho
Website

  • Quote

Post by plesho » Tue Mar 07, 2006 9:34 pm

I can also confirm that the installation that RoninTT proposed is working, but it is extremely show, as it was allready mentioned...
I was able to get 80FPS with XGL on fullscreen with glxgears on a P4 2.8GHz. The CoffeeBuzz's overlay was used - thank you for that CoffeeBuzz ;)

Still waiting for an at least partial hardware openGL support on that card
Top
zapata
Tux's lil' helper
Tux's lil' helper
User avatar
Posts: 82
Joined: Sun Jun 26, 2005 9:51 am
Location: Hamburg / Germany

  • Quote

Post by zapata » Tue Mar 07, 2006 11:28 pm

I receive a error-message by trying to install mesa-6.4.3_alpha20060216 from coffee-overlay:

Code: Select all

i686-pc-linux-gnu-gcc -c -I. -I../../../../../src/mesa/drivers/dri/common -Iserver -I../../../../../../drm/shared-core -I../../../../../include -I../../../../../include/GL/internal -I../../../../../src/mesa -I../../../../../src/mesa/main -I../../../../../src/mesa/glapi -I../../../../../src/mesa/math -I../../../../../src/mesa/transform -I../../../../../src/mesa/shader -I../../../../../src/mesa/swrast -I../../../../../src/mesa/swrast_setup -I../../../../../src/egl/main -I../../../../../src/egl/drivers/dri  `pkg-config --cflags libdrm` -Wall -Wmissing-prototypes -march=pentium3 -O3 -pipe -g -fPIC -m32 -D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_SVID_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING -DHAVE_ALIAS -DDEFAULT_DRIVER_DIR='"/usr/lib/xorg/modules/dri"' -DUSE_X86_ASM -DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM -std=c99 -ffast-math  -D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_SVID_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING -DHAVE_ALIAS -DDEFAULT_DRIVER_DIR='"/usr/lib/xorg/modules/dri"' intel_ioctl.c -o intel_ioctl.o
intel_ioctl.c: In function `intelGetLastFrame':
intel_ioctl.c:49: Fehler: »I915_PARAM_LAST_DISPATCH« nicht deklariert (erste Benutzung in dieser Funktion)
intel_ioctl.c:49: Fehler: (Jeder nicht deklarierte Bezeichner wird nur einmal aufgeführt
intel_ioctl.c:49: Fehler: für jede Funktion in der er auftritt.)
make[6]: *** [intel_ioctl.o] error 1
make[6]: Leaving directory `/var/tmp/portage/mesa-6.4.3_alpha20060225/work/Mesa/src/mesa/drivers/dri/i915'
make[5]: *** [subdirs] error 1
make[5]: Leaving directory `/var/tmp/portage/mesa-6.4.3_alpha20060225/work/Mesa/src/mesa/drivers/dri'
make[4]: *** [linux-solo] error 2
make[4]: Leaving directory `/var/tmp/portage/mesa-6.4.3_alpha20060225/work/Mesa/src/mesa'
make[3]: *** [default] error 2
make[3]: Leaving directory `/var/tmp/portage/mesa-6.4.3_alpha20060225/work/Mesa/src/mesa'
make[2]: *** [subdirs] error 1
make[2]: Leaving directory `/var/tmp/portage/mesa-6.4.3_alpha20060225/work/Mesa/src'
make[1]: *** [default] error 1
make[1]: Leaving directory `/var/tmp/portage/mesa-6.4.3_alpha20060225/work/Mesa'
make: *** [linux-dri-x86] error 2

!!! ERROR: media-libs/mesa-6.4.3_alpha20060225 failed.
Call stack:
  ebuild.sh, line 1894:   Called dyn_compile
  ebuild.sh, line 941:   Called src_compile

!!! Build failed
!!! If you need support, post the topmost build error, and the call stack if relevant.

make.conf:

Code: Select all

VIDEO_CARDS="i810"
lspci:

Code: Select all

00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
xorg.conf:

Code: Select all

Section "Module"
    Load        "dbe"  	# Double buffer extension
    Load       "extmod"
    Load       "type1"
    Load       "synaptics"
    Load       "freetype"
    Load       "glx"
    Load       "dri"
#   Load       "ddc"

EndSection

Section "Files"
	RgbPath		"/usr/share/X11/rgb"
#	FontPath	"/usr/share/fonts/local/"
	FontPath	"/usr/share/fonts/misc/"
	FontPath	"/usr/share/fonts/75dpi/:unscaled"
	FontPath	"/usr/share/fonts/100dpi/:unscaled"
	FontPath	"/usr/share/fonts/Type1/"
	FontPath	"/usr/share/fonts/CID/"
#	FontPath	"/usr/share/fonts/Speedo/"
	FontPath	"/usr/share/fonts/75dpi/"
	FontPath	"/usr/share/fonts/100dpi/"
#	FontPath	"/usr/share/fonts/terminus"
#	FontPath	"/usr/share/fonts/mathematica-fonts"
#	FontPath	"unix/:-1"
EndSection

Section "ServerFlags"

EndSection

Section "InputDevice"
   	Identifier  "Keyboard1"
   	Driver      "kbd"
	Option      "XkbKeycodes" "xfree86+aliases(qwerty)"
        Option      "XkbTypes" "complete"
        Option      "XkbCompat" "complete"
   	Option       "XkbModel" "pc105"
        Option      "XkbSymbols" "en_US(pc105)+de"
        Option      "XkbGeometry" "pc(pc105)"
        Option      "XkbOption" ""
        Option      "XkbLayout" "de"
EndSection 

Section "InputDevice"
	Identifier  "trackpoint"
	Driver      "mouse"
	Option      "CorePointer"
	Option      "Protocol" "IMPS/2"
	Option      "ZAxisMapping"          "4 5"
	Option      "Device" "/dev/input/mouse0"
	Option      "Emulate3Buttons" "true"
	Option      "Emulate3Timeout" "70"	
	Option	    "SendCoreEvents"  "true"
	Option      "EmulateWheel" "on"
	Option      "EmulateWheelButton" "2"
EndSection

Section "Monitor"

    VertRefresh     50-70
    Identifier      "LCD"
    HorizSync       28-49
    VertRefresh     43-72
    Option          "DPMS"
				    
EndSection

Section "Monitor"
    Identifier      "External Monitor"
    HorizSync       31-64
    VertRefresh     56-75
    Option          "DPMS"
EndSection
				
Section "Device"
    Identifier  "Intel0"
    Driver      "i810"
    #VideoRam    131072
    Option "DRI" "true"
    #Option "VBERestore" "true"
    #Option "Clone" "true"
    Option "MonitorLayout" "CRT,LFP"
    Option "DevicePresence" "true"
    # Insert Clocks lines here if appropriate
#    Screen 0
EndSection

Section "Device"
        Identifier      "Intel1"
        Driver          "i810"
        Option "DRI"	"true"
	Option          "VBERestore" "no"
        Option          "MonitorLayout" "CRT,LFP"
        Option          "DevicePresence"        "true"
        BusID           "PCI:0:2:0"
        Option          "AGPMode" "4"
        Screen          1
EndSection

Section "Screen"
        Identifier      "LCD"
        Device          "Intel0"
        Monitor         "LCD"
        DefaultDepth    16
        SubSection "Display"
                Depth           1
                Modes           "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Depth           4
                Modes           "1024x768" "800x600" "640x480"
        EndSubSection
	SubSection "Display"
                Depth           8
                Modes           "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Depth           15
                Modes           "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Depth           16
                Modes           "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Depth           24
                Modes           "1024x768" "800x600" "640x480"
        EndSubSection

EndSection

Section "Screen"
        Identifier      "VGA"
        Device          "Intel1"
        Monitor         "External Monitor"
        DefaultDepth    16
        SubSection "Display"
                Depth           16
                Modes           "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
EndSection

Section "ServerLayout"

    Identifier  "Simple Layout"

        Screen 0 "LCD"
        Screen 1 "VGA" LeftOf "LCD"

	InputDevice	"trackpoint"
	InputDevice	"Keyboard1" "CoreKeyboard"
EndSection

Section "DRI"
    Group "video"
    Mode 0660
EndSection
kernel-2.6.16-rc3-nitro1:

Code: Select all

# Ftape, the floppy tape device driver
#
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=y
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
CONFIG_DRM_I915=m
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
# CONFIG_MWAVE is not set
# CONFIG_CS5535_GPIO is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HPET is not set
# CONFIG_HANGCHECK_TIMER is not set
I try this on a IBM X40 notebook with Intel chipset and VGA.

Can someone help?
Top
CoffeeBuzz
Apprentice
Apprentice
User avatar
Posts: 269
Joined: Wed Jun 15, 2005 7:11 pm
Location: Canada Eh.
Contact:
Contact CoffeeBuzz
Website

  • Quote

Post by CoffeeBuzz » Wed Mar 08, 2006 4:44 am

mesa-6.4.3_alpha20060216 ?

should be mesa-6.5.0_alpha20060301 if you're using xgl-coffee (maybe update it with svn up?)
If you have VIDEO_CARDS="i810" with that version of mesa, the source should compile clean.
HP Pavilion zd7260us
Xgl Overlay: http://svn.xgl-coffee.org/xgl-coffee/trunk
Xgl Forums: http://forums.xgl-coffee.org
Top
RoninTT
n00b
n00b
Posts: 7
Joined: Tue Feb 28, 2006 7:17 am

  • Quote

Post by RoninTT » Wed Mar 08, 2006 8:19 am

I got XGL runing a little better than before. This time I used the i810 driver and libshadow module from here:

http://www.fairlite.demon.co.uk/intel.html

Then I can start XGL without copying the old mesa driver back. And if I copy that driver back it won't work.

Now comes the strange part, even though XGL runs as good as it ever has on my laptop. When I run glxinfo it says that there is on DRI??

I get about 600-700 FPS in glxgears without any warnings of any kind and all the effect are working.

So I just wanted to see if any you could get the same result or maybe better than me.
Top
plesho
n00b
n00b
User avatar
Posts: 10
Joined: Tue Dec 27, 2005 10:43 am
Contact:
Contact plesho
Website

  • Quote

Post by plesho » Wed Mar 08, 2006 9:46 am

And what about the i915_drv.so?
I 'm using i945 chipset, so I suppose the i915_drv.so driver is used and I can not confirm your tests

EDIT:
My mistake - i810_drv.so is the Xorg driver located in

Code: Select all

/usr/lib/xorg/modules/drivers/i810_drv.so
not the mesa dri module

Code: Select all

/usr/lib/xorg/modules/dri/i810_dri.so
That way - I tried to reproduce the RoninTT solution and it is not working with mesa_6.5.0_alpha20060308
Will continue experimenting :lol:
Last edited by plesho on Thu Mar 09, 2006 8:37 am, edited 1 time in total.
Top
x.para
Apprentice
Apprentice
Posts: 174
Joined: Sun May 22, 2005 4:22 pm
Location: CZ

  • Quote

Post by x.para » Wed Mar 08, 2006 11:43 am

Hi guys, I'd also like to share my experiences on Xgl running with I810.

My current situation is that, I have Xgl working as some of you terribly slow so it looks that all rendering is done by CPU. Currently I end up with module i810_drv.so from

http://dri.freedesktop.org/snapshots/

but before I used the one from

http://www.fairlite.demon.co.uk/intel.html

My Xgl starts OK, compiz also and I also can start run KDE without window decorations under Xgl.

I think there still something bad about the driver and its direct rendering and this is the reason why Xgl is like working but still not usable for me.

I run it on IBM R31. As I don't have computer with me now, I can't post all versions details but I use

xgl-coffee overlay ver. 44
2.6.15-r6
also tested on 2.6.16-rc1 with the same result.
Top
zapata
Tux's lil' helper
Tux's lil' helper
User avatar
Posts: 82
Joined: Sun Jun 26, 2005 9:51 am
Location: Hamburg / Germany

  • Quote

Post by zapata » Wed Mar 08, 2006 1:12 pm

hi, I have update the coffee-xgl-overlay (svn up), but I reveice the same error by retrying to install mesa:

Code: Select all

dules/dri"' -DUSE_X86_ASM -DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM -std=c99 -ffast-math  -D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_SVID_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING -DHAVE_ALIAS -DDEFAULT_DRIVER_DIR='"/usr/lib/xorg/modules/dri"' intel_ioctl.c -o intel_ioctl.o
intel_ioctl.c: In function `intelGetLastFrame':
intel_ioctl.c:49: Fehler: »I915_PARAM_LAST_DISPATCH« not declaired(first use in this function)
intel_ioctl.c:49: Fehler: (Jeder nicht deklarierte Bezeichner wird nur einmal aufgeführt
intel_ioctl.c:49: Fehler: für jede Funktion in der er auftritt.)
make[6]: *** [intel_ioctl.o] Fehler 1
make[6]: Leaving directory `/var/tmp/portage/mesa-6.5.0_alpha20060301/work/Mesa/src/mesa/drivers/dri/i915'
make[5]: *** [subdirs] Fehler 1
make[5]: Leaving directory `/var/tmp/portage/mesa-6.5.0_alpha20060301/work/Mesa/src/mesa/drivers/dri'
make[4]: *** [linux-solo] Fehler 2
make[4]: Leaving directory `/var/tmp/portage/mesa-6.5.0_alpha20060301/work/Mesa/src/mesa'
make[3]: *** [default] Fehler 2
make[3]: Leaving directory `/var/tmp/portage/mesa-6.5.0_alpha20060301/work/Mesa/src/mesa'
make[2]: *** [subdirs] Fehler 1
make[2]: Leaving directory `/var/tmp/portage/mesa-6.5.0_alpha20060301/work/Mesa/src'
make[1]: *** [default] Fehler 1
make[1]: Leaving directory `/var/tmp/portage/mesa-6.5.0_alpha20060301/work/Mesa'
make: *** [linux-dri-x86] Fehler 2

!!! ERROR: media-libs/mesa-6.5.0_alpha20060301 failed.
Call stack:
  ebuild.sh, line 1894:   Called dyn_compile
  ebuild.sh, line 941:   Called src_compile

!!! Build failed
!!! If you need support, post the topmost build error, and the call stack if relevant.
has someone an idea?
Top
x.para
Apprentice
Apprentice
Posts: 174
Joined: Sun May 22, 2005 4:22 pm
Location: CZ

  • Quote

Post by x.para » Wed Mar 08, 2006 3:32 pm

zapata wrote:hi, I have update the coffee-xgl-overlay (svn up), but I reveice the same error by retrying to install mesa:

Code: Select all

dules/dri"' -DUSE_X86_ASM -DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM -std=c99 -ffast-math  -D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_SVID_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING -DHAVE_ALIAS -DDEFAULT_DRIVER_DIR='"/usr/lib/xorg/modules/dri"' intel_ioctl.c -o intel_ioctl.o
intel_ioctl.c: In function `intelGetLastFrame':
intel_ioctl.c:49: Fehler: »I915_PARAM_LAST_DISPATCH« not declaired(first use in this function)
intel_ioctl.c:49: Fehler: (Jeder nicht deklarierte Bezeichner wird nur einmal aufgeführt
intel_ioctl.c:49: Fehler: für jede Funktion in der er auftritt.)
make[6]: *** [intel_ioctl.o] Fehler 1
make[6]: Leaving directory `/var/tmp/portage/mesa-6.5.0_alpha20060301/work/Mesa/src/mesa/drivers/dri/i915'
make[5]: *** [subdirs] Fehler 1
make[5]: Leaving directory `/var/tmp/portage/mesa-6.5.0_alpha20060301/work/Mesa/src/mesa/drivers/dri'
make[4]: *** [linux-solo] Fehler 2
make[4]: Leaving directory `/var/tmp/portage/mesa-6.5.0_alpha20060301/work/Mesa/src/mesa'
make[3]: *** [default] Fehler 2
make[3]: Leaving directory `/var/tmp/portage/mesa-6.5.0_alpha20060301/work/Mesa/src/mesa'
make[2]: *** [subdirs] Fehler 1
make[2]: Leaving directory `/var/tmp/portage/mesa-6.5.0_alpha20060301/work/Mesa/src'
make[1]: *** [default] Fehler 1
make[1]: Leaving directory `/var/tmp/portage/mesa-6.5.0_alpha20060301/work/Mesa'
make: *** [linux-dri-x86] Fehler 2

!!! ERROR: media-libs/mesa-6.5.0_alpha20060301 failed.
Call stack:
  ebuild.sh, line 1894:   Called dyn_compile
  ebuild.sh, line 941:   Called src_compile

!!! Build failed
!!! If you need support, post the topmost build error, and the call stack if relevant.
has someone an idea?

Here is the solution:

http://gentoo-wiki.com/HOWTO_XGL#I915_P ... RM_headers
Top
alanic
n00b
n00b
User avatar
Posts: 41
Joined: Fri Jan 13, 2006 3:43 am

  • Quote

Post by alanic » Wed Mar 08, 2006 4:53 pm

As far as I know, there is no direct rendering for other programs that run under Xgl.

How much better is it? Worth a try?
RoninTT wrote:I got XGL runing a little better than before. This time I used the i810 driver and libshadow module from here:

http://www.fairlite.demon.co.uk/intel.html

Then I can start XGL without copying the old mesa driver back. And if I copy that driver back it won't work.

Now comes the strange part, even though XGL runs as good as it ever has on my laptop. When I run glxinfo it says that there is on DRI??

I get about 600-700 FPS in glxgears without any warnings of any kind and all the effect are working.

So I just wanted to see if any you could get the same result or maybe better than me.
Top
plesho
n00b
n00b
User avatar
Posts: 10
Joined: Tue Dec 27, 2005 10:43 am
Contact:
Contact plesho
Website

  • Quote

Post by plesho » Thu Mar 09, 2006 9:36 am

After updating the CoffeeBuzz overlay [ 55 revision ] - DRI stopped working for me.

Changing the i810_drv.so to the one from
http://www.fairlite.demon.co.uk/intel.html
didn't helped much

I also tried the latest snapshot from
http://dri.freedesktop.org/snapshots/ as x.para proposed - still no go
Top
RoninTT
n00b
n00b
Posts: 7
Joined: Tue Feb 28, 2006 7:17 am

  • Quote

Post by RoninTT » Thu Mar 09, 2006 11:36 am

It's better and now I would at least consider using it everyday. But there is still some big problems. Firefox runs very slow and makes all effect of XGL run very slow. So I would say that this is the best solution I have seen so far. But still not good enough. And if it really runs of the CPU and not the GPU it's no go for my laptop. Runing XGL will lower my total runing time on the battery and thats not something I can live with.
alanic wrote:As far as I know, there is no direct rendering for other programs that run under Xgl.

How much better is it? Worth a try?
RoninTT wrote:I got XGL runing a little better than before. This time I used the i810 driver and libshadow module from here:

http://www.fairlite.demon.co.uk/intel.html

Then I can start XGL without copying the old mesa driver back. And if I copy that driver back it won't work.

Now comes the strange part, even though XGL runs as good as it ever has on my laptop. When I run glxinfo it says that there is on DRI??

I get about 600-700 FPS in glxgears without any warnings of any kind and all the effect are working.

So I just wanted to see if any you could get the same result or maybe better than me.
Top
Post Reply

228 posts
  • Page 2 of 10
    • Jump to page:
  • Previous
  • 1
  • 2
  • 3
  • 4
  • 5
  • …
  • 10
  • Next

Return to “Unsupported Software”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy

 

 

magic