Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Xorg 7.0 w/ tcl and tk problem
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on AMD64
View previous topic :: View next topic  
Author Message
avieth
Veteran
Veteran


Joined: 17 Sep 2004
Posts: 1945
Location: Canada

PostPosted: Wed Jan 04, 2006 8:43 pm    Post subject: Xorg 7.0 w/ tcl and tk problem Reply with quote

Just realized there was a new xorg. Should I bother upgrading? It seems every damned package for this new release is masked for amd64. Does it fix anything relating to composite and transparency?

Is there anything I need to know about installing it and getting it working? Or is it just as simple as anything else?


Last edited by avieth on Thu Jan 05, 2006 4:15 am; edited 1 time in total
Back to top
View user's profile Send private message
Sm1
Apprentice
Apprentice


Joined: 02 Dec 2003
Posts: 251
Location: Ames, IA

PostPosted: Wed Jan 04, 2006 9:17 pm    Post subject: Reply with quote

http://gentoo-wiki.com/HOWTO_Modular_Xorg

There are various improvements across the board from my understanding. The big composite improvements come from the new nvidia driver however.
Back to top
View user's profile Send private message
mariux2
Apprentice
Apprentice


Joined: 16 Sep 2003
Posts: 242

PostPosted: Wed Jan 04, 2006 9:26 pm    Post subject: Reply with quote

What gfx-card do you have?

If you have a ati card older than 9250 or an nvidia card i would recommend it.
If you have a recent ati card its not a big difference.
Back to top
View user's profile Send private message
avieth
Veteran
Veteran


Joined: 17 Sep 2004
Posts: 1945
Location: Canada

PostPosted: Wed Jan 04, 2006 11:37 pm    Post subject: Reply with quote

Got an nvidia geforce 6600 gt. I went ahead and upgraded, it seems like it worked, but I guess i forgot to emerge the cursor themes, they arn't there. And aMsn won't open for some reason, it gives me this error
Code:

Application initialization failed: this isn't a Tk applicationunknown color name "Black"
Error in startup script: this isn't a Tk applicationunknown color name "Black"
    (default value for "-highlightcolor" in widget ".")
    invoked from within
"load /usr/lib/tk8.4/../libtk8.4.so Tk"
    ("package ifneeded" script)
    invoked from within
"package require Tk"
    (file "/usr/bin/amsn" line 46)

So how do I fix this?

I remerged tcl and tk, but it still doesn't work.
Back to top
View user's profile Send private message
VValdo
Guru
Guru


Joined: 08 Jan 2005
Posts: 395

PostPosted: Thu Jan 05, 2006 1:19 am    Post subject: Reply with quote

avieth wrote:
Got an nvidia geforce 6600 gt. I went ahead and upgraded, it seems like it worked, but I guess i forgot to emerge the cursor themes, they arn't there. And aMsn won't open for some reason, it gives me this error
So how do I fix this?

I remerged tcl and tk, but it still doesn't work.


Not sure if you use gnome, but I had a problem with gnome-settings-daemon crashing w/modular x and the "evdev" driver, which required a patch. Also, eselect weirdness with /lib64 which made compiling xorg-server give me problems that had to be addressed. Had to do some changes to xorg.conf to get glx working, and finally, even once everything was up and working, I notice a weird stuttering when I have a jpg or svg desktop background.

W
Back to top
View user's profile Send private message
avieth
Veteran
Veteran


Joined: 17 Sep 2004
Posts: 1945
Location: Canada

PostPosted: Thu Jan 05, 2006 1:24 am    Post subject: Reply with quote

No, I'm running KDE.
Back to top
View user's profile Send private message
zietbukuel
l33t
l33t


Joined: 30 Dec 2005
Posts: 606
Location: /dev/peru/lima

PostPosted: Thu Feb 16, 2006 8:41 pm    Post subject: Reply with quote

I have this problem too, anyone has a solution/fix? :?

I'm using GNOME.

Thanks!
_________________
AMD FX 8350 8-core CPU
16GB Corsair Vengeance DDR3 RAM
ASUS M5A97 Motherboard
1TB (Gentoo) + 500GB (Windows 7 for games) HDDs
Nvidia 550 GTX Ti 1Gb Ram DDR5
Cooler Master CM690 Case
Back to top
View user's profile Send private message
Voyageur
Developer
Developer


Joined: 06 Mar 2005
Posts: 342
Location: Paris, France

PostPosted: Fri Feb 17, 2006 11:18 am    Post subject: Reply with quote

A few files have changed places with this new xorg, and I had trouble with urxvt not finding colours "black", "blue", ... anymore.
The faulty file was /usr/lib/X11/rgb.txt, that is now /usr/share/X11/rgb.txt

You could try as a temporary hack to do
Code:
ln -s /usr/share/X11/rgb.txt /usr/lib/X11/rgb.txt
to see if it works (I have to admit, I have not fixed it yet in a proper way, the link works fine for now :wink: )
_________________
Routinely breaking NX, GNUstep, net-ftp, miscellaneous (llvm, filezilla, rdesktop, chromium, ...) packages
Back to top
View user's profile Send private message
EzInKy
Veteran
Veteran


Joined: 11 Oct 2002
Posts: 1734
Location: Kentucky

PostPosted: Fri Feb 17, 2006 12:10 pm    Post subject: Reply with quote

Voyageur wrote:
A few files have changed places with this new xorg, and I had trouble with urxvt not finding colours "black", "blue", ... anymore.
The faulty file was /usr/lib/X11/rgb.txt, that is now /usr/share/X11/rgb.txt

You could try as a temporary hack to do
Code:
ln -s /usr/share/X11/rgb.txt /usr/lib/X11/rgb.txt
to see if it works (I have to admit, I have not fixed it yet in a proper way, the link works fine for now :wink: )


Editing your xorg.conf files section like this...

Code:

RgbPath   "/usr/share/X11/rgb"


...fixes the problem.
_________________
Time is what keeps everything from happening all at once.
Back to top
View user's profile Send private message
Aggamemnon
Tux's lil' helper
Tux's lil' helper


Joined: 04 Mar 2004
Posts: 99
Location: Bristol, UK

PostPosted: Fri Feb 17, 2006 12:34 pm    Post subject: Reply with quote

I am having massive problems with ATi and glx when I went to xorg-7. It was all working before (honest)

Whenever I attempt to run glxinfo or to do any glx operation, I get this error:
Code:
rob@Shodan ~ $ glxinfo
name of display: :0.0
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  142 (GLX)
  Minor opcode of failed request:  5 (X_GLXMakeCurrent)
  Serial number of failed request:  18
  Current serial number in output stream:  18


I have tried many things, including rebuilding xorg-server, rebuilding xorg-x11 and farting about with symlinks (thinking that this may be an eselect problem). I can avoid this issue if I change from fglrx to radeon in my xorg.conf and commenting out the Load glx line. Then I can run glxinfo and am informed that I have indirect rendering.

Please help!
Back to top
View user's profile Send private message
EzInKy
Veteran
Veteran


Joined: 11 Oct 2002
Posts: 1734
Location: Kentucky

PostPosted: Fri Feb 17, 2006 12:50 pm    Post subject: Reply with quote

Aggamemnon wrote:
I am having massive problems with ATi and glx when I went to xorg-7. It was all working before (honest)

Whenever I attempt to run glxinfo or to do any glx operation, I get this error:
Code:
rob@Shodan ~ $ glxinfo
name of display: :0.0
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  142 (GLX)
  Minor opcode of failed request:  5 (X_GLXMakeCurrent)
  Serial number of failed request:  18
  Current serial number in output stream:  18


I have tried many things, including rebuilding xorg-server, rebuilding xorg-x11 and farting about with symlinks (thinking that this may be an eselect problem). I can avoid this issue if I change from fglrx to radeon in my xorg.conf and commenting out the Load glx line. Then I can run glxinfo and am informed that I have indirect rendering.

Please help!


What kind of errors are you seeing in your Xorg.log file?
_________________
Time is what keeps everything from happening all at once.
Back to top
View user's profile Send private message
Aggamemnon
Tux's lil' helper
Tux's lil' helper


Joined: 04 Mar 2004
Posts: 99
Location: Bristol, UK

PostPosted: Fri Feb 17, 2006 12:56 pm    Post subject: Reply with quote

Code:
grep -e EE -e WW /var/log/Xorg.0.log
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) fglrx(0): Specified desktop setup not supported: 8
(EE) fglrx(0): === [R200DALSetControllerConfigForRemap] === CWDDC ControllerSetConfig failed: 6 - 0
(EE) fglrx(0): === [R200DALSetControllerConfigForRemap] === CWDDC ControllerSetConfig failed: 6 - 0
(EE) fglrx(0): === [R200DALSetControllerConfigForRemap] === CWDDC ControllerSetConfig failed: 6 - 0
(EE) fglrx(0): === [R200DALSetControllerConfigForRemap] === CWDDC ControllerSetConfig failed: 6 - 0
Back to top
View user's profile Send private message
EzInKy
Veteran
Veteran


Joined: 11 Oct 2002
Posts: 1734
Location: Kentucky

PostPosted: Fri Feb 17, 2006 1:35 pm    Post subject: Reply with quote

Aggamemnon wrote:
Code:
grep -e EE -e WW /var/log/Xorg.0.log
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) fglrx(0): Specified desktop setup not supported: 8
(EE) fglrx(0): === [R200DALSetControllerConfigForRemap] === CWDDC ControllerSetConfig failed: 6 - 0
(EE) fglrx(0): === [R200DALSetControllerConfigForRemap] === CWDDC ControllerSetConfig failed: 6 - 0
(EE) fglrx(0): === [R200DALSetControllerConfigForRemap] === CWDDC ControllerSetConfig failed: 6 - 0
(EE) fglrx(0): === [R200DALSetControllerConfigForRemap] === CWDDC ControllerSetConfig failed: 6 - 0


I've never seen that one so I searched Rage3D.com forums and the only reference I could find for those errors was related to TV out.
_________________
Time is what keeps everything from happening all at once.
Back to top
View user's profile Send private message
Voyageur
Developer
Developer


Joined: 06 Mar 2005
Posts: 342
Location: Paris, France

PostPosted: Fri Feb 17, 2006 1:39 pm    Post subject: Reply with quote

EzInKy wrote:

Editing your xorg.conf files section like this...

Code:

RgbPath   "/usr/share/X11/rgb"


...fixes the problem.


Ah ok... I had understood from the migration guide that the ModulePath and RgbPath lines needed to be completely eradicated. I'll put the rgbpath back in its correct form tonight, thanks for the tip!
_________________
Routinely breaking NX, GNUstep, net-ftp, miscellaneous (llvm, filezilla, rdesktop, chromium, ...) packages
Back to top
View user's profile Send private message
Aggamemnon
Tux's lil' helper
Tux's lil' helper


Joined: 04 Mar 2004
Posts: 99
Location: Bristol, UK

PostPosted: Fri Feb 17, 2006 1:52 pm    Post subject: Reply with quote

I think the problem is related to the GLX module becuase...
Code:

rob@Shodan ~ $ grep -i direct  /var/log/Xorg.0.log
(II) fglrx(0): Direct rendering enabled
Back to top
View user's profile Send private message
EzInKy
Veteran
Veteran


Joined: 11 Oct 2002
Posts: 1734
Location: Kentucky

PostPosted: Fri Feb 17, 2006 2:13 pm    Post subject: Reply with quote

Aggamemnon wrote:
I think the problem is related to the GLX module becuase...
Code:

rob@Shodan ~ $ grep -i direct  /var/log/Xorg.0.log
(II) fglrx(0): Direct rendering enabled


It very well may be, I've been having trouble with fglrx and 32bit apps, but I do have 64bit hardware rendering using modular xorg and the latest ~amd64 ati-drivers with my X800 XL PCIe card...

Code:

$ glxgears
47308 frames in 5.0 seconds = 9461.551 FPS
47835 frames in 5.0 seconds = 9566.932 FPS
47836 frames in 5.0 seconds = 9567.094 FPS
47827 frames in 5.0 seconds = 9565.208 FPS
47832 frames in 5.0 seconds = 9566.279 FPS


...though I'd gladly take half that if I could ever get the r300 driver working with my card.
_________________
Time is what keeps everything from happening all at once.
Back to top
View user's profile Send private message
Aggamemnon
Tux's lil' helper
Tux's lil' helper


Joined: 04 Mar 2004
Posts: 99
Location: Bristol, UK

PostPosted: Fri Feb 17, 2006 2:17 pm    Post subject: Reply with quote

May I see your xorg.conf, and the location of your libgl* please?
Back to top
View user's profile Send private message
dusty0
n00b
n00b


Joined: 15 Feb 2006
Posts: 7

PostPosted: Fri Feb 17, 2006 5:20 pm    Post subject: Reply with quote

If we use the NVidia proprietary drivers is there any reason to upgrade from 6.8.2 to 7 ?
Or should we wait a bit for thing to stabilize..

Are there any serious security holes patched in 7.0 ?
Back to top
View user's profile Send private message
EzInKy
Veteran
Veteran


Joined: 11 Oct 2002
Posts: 1734
Location: Kentucky

PostPosted: Fri Feb 17, 2006 10:49 pm    Post subject: Reply with quote

Aggamemnon wrote:
May I see your xorg.conf, and the location of your libgl* please?


Sure:

Code:

# **********************************************************************
# DRI Section
# **********************************************************************
Section "dri"
# Access to OpenGL ICD is allowed for all users:
    Mode 0666
# Access to OpenGL ICD is restricted to a specific user group:
#    Group 100    # users
#    Mode 0660
EndSection

# **********************************************************************
# 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 Type1 and FreeType font modules
    Load        "type1"
    Load        "freetype"

# This loads the GLX module
    Load        "glx"   # libglx.a
    Load        "dri"   # libdri.a

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/share/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)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#

FontPath    "/usr/share/fonts/misc:unscaled"
   FontPath    "/usr/share/fonts/Type1"
   FontPath    "/usr/share/fonts/TTF"
   FontPath    "/usr/share/fonts/corefonts"
   FontPath    "/usr/share/fonts/freefont"
   FontPath    "/usr/share/fonts/sharefonts"
   FontPath    "/usr/share/fonts/terminus"
   FontPath    "/usr/share/fonts/ttf-bitstream-vera"
   FontPath    "/usr/share/fonts/unifont"
   FontPath    "/usr/share/fonts/75dpi:unscaled"
   FontPath    "/usr/share/fonts/100dpi:unscaled"
   FontPath    "/usr/share/fonts/artwiz"

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

ModulePath "/usr/lib/xorg/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 <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option "DontZap"

# Uncomment this to disable the <Crtl><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"

#   Option "DontVTSwitch" "false"

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"   "pc102"
# 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 XFree86
#    Option "XkbRules"   "xfree86"
#    Option "XkbModel"   "pc104"
#    Option "XkbLayout"  "us"
#    Option "XkbVariant" ""
#    Option "XkbOptions" ""

#    Option "XkbDisable"

    Option "XkbRules"   "xorg"
    Option "XkbModel"   "pc104"
    Option "XkbLayout"   "us"

EndSection


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

Section "InputDevice"

# Identifier and driver

    Identifier   "Mouse1"
    Driver "mouse"
    Option "Protocol"   "ImPS/2"
    Option "ZAxisMapping"   "4 5"
    Option "Device"     "/dev/input/mice"

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

#    Option "Protocol"   "Xqueue"

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

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

# Emulate3Buttons is an option for 2-button Microsoft 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 XF86Config 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  "Monitor0"
    HorizSync   31.5 - 91.1
    VertRefresh 60-160
    Option "DPMS" "off"
    DisplaySize 381 238

# === mode lines based on GTF ===
# VGA @ 100Hz
# Modeline "640x480@100" 43.163 640 680 744 848 480 481 484 509 +hsync +vsync
# SVGA @ 100Hz
# Modeline "800x600@100" 68.179 800 848 936 1072 600 601 604 636 +hsync +vsync
# XVGA @ 100Hz
# Modeline "1024x768@100" 113.309 1024 1096 1208 1392 768 769 772 814 +hsync +vsync
# 1152x864 @ 60Hz
# Modeline "1152x864@60" 81.642 1152 1216 1336 1520 864 865 868 895 +hsync +vsync
# 1152x864 @ 85Hz
# Modeline "1152x864@85" 119.651 1152 1224 1352 1552 864 865 868 907 +hsync +vsync
# 1152x864 @ 100Hz
# Modeline "1152x864@100" 143.472 1152 1232 1360 1568 864 865 868 915 +hsync +vsync
# 1280x960 @ 75Hz
# Modeline "1280x960@75" 129.859 1280 1368 1504 1728 960 961 964 1002 +hsync +vsync
# 1280x960 @ 100Hz
# Modeline "1280x960@100" 178.992 1280 1376 1520 1760 960 961 964 1017  +hsync +vsync
# SXGA @ 100Hz
# Modeline "1280x1024@100" 190.960 1280 1376 1520 1760 1024 1025 1028 1085 +hsync +vsync
# SPEA GDM-1950 (60Hz,64kHz,110MHz,-,-): 1280x1024 @ V-freq: 60.00 Hz, H-freq: 63.73 KHz
# Modeline "GDM-1950"  109.62  1280 1336 1472 1720  1024 1024 1026 1062 -hsync -vsync
# 1600x1000 @ 60Hz
# Modeline "1600x1000" 133.142 1600 1704 1872 2144 1000 1001 1004 1035 +hsync +vsync
# 1600x1000 @ 75Hz
# Modeline "1600x1000" 169.128 1600 1704 1880 2160 1000 1001 1004 1044 +hsync +vsync
# 1600x1000 @ 85Hz
# Modeline "1600x1000" 194.202 1600 1712 1888 2176 1000 1001 1004 1050 +hsync +vsync
# 1600x1000 @ 100Hz
# Modeline "1600x1000" 232.133 1600 1720 1896 2192 1000 1001 1004 1059 +hsync +vsync
# 1600x1024 @ 60Hz
# Modeline "1600x1024" 136.385 1600 1704 1872 2144 1024 1027 1030 1060 +hsync +vsync
# 1600x1024 @ 75Hz
# Modeline "1600x1024" 174.416 1600 1712 1888 2176 1024 1025 1028 1069 +hsync +vsync
# 1600x1024 @ 76Hz
# Modeline "1600x1024" 170.450 1600 1632 1792 2096 1024 1027 1030 1070 +hsync +vsync
# 1600x1024 @ 85Hz
# Modeline "1600x1024" 198.832 1600 1712 1888 2176 1024 1027 1030 1075 +hsync +vsync
# 1920x1080 @ 60Hz
# Modeline "1920x1080" 172.798 1920 2040 2248 2576 1080 1081 1084 1118 -hsync -vsync
# 1920x1080 @ 75Hz
# Modeline "1920x1080" 211.436 1920 2056 2264 2608 1080 1081 1084 1126 +hsync +vsync
# 1920x1200 @ 60Hz
# Modeline "1920x1200" 193.156 1920 2048 2256 2592 1200 1201 1203 1242 +hsync +vsync
# 1920x1200 @ 75Hz
# Modeline "1920x1200" 246.590 1920 2064 2272 2624 1200 1201 1203 1253 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 1400x1050 @ 60Hz M9 Laptop mode
# ModeLine "1400x1050" 122.000 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync
# 1920x2400 @ 25Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@25" 124.620 1920 1928 1980 2048 2400 2401 2403 2434 +hsync +vsync
# 1920x2400 @ 30Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@30" 149.250 1920 1928 1982 2044 2400 2402 2404 2434 +hsync +vsync

Modeline "1440x900@60"  106.47  1440 1520 1672 1904  900 901 904 932  -HSync +Vsync
Modeline "1280x800@60"  83.46  1280 1344 1480 1680  800 801 804 828  -HSync +Vsync
Modeline "1152x864@60"  81.62  1152 1216 1336 1520  864 865 868 895  -HSync +Vsync
Modeline "1024x768@60"  64.11  1024 1080 1184 1344  768 769 772 795  -HSync +Vsync
Modeline "800x600@60"  38.22  800 832 912 1024  600 601 604 622  -HSync +Vsync
Modeline "640x480@60"  23.86  640 656 720 800  480 481 484 497  -HSync +Vsync

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
# installed.

#    BusID       "PCI:0:10:0"

#    VideoRam    256

#    Clocks      25.2 28.3

EndSection

# === ATI device section ===

Section "Device"
    Identifier                          "ATI Graphics Adapter"
    Driver                              "fglrx"
# ### generic DRI settings ###
# === disable PnP Monitor  ===
    #Option                              "NoDDC"
# === disable/enable XAA/DRI ===
    Option "no_accel"                   "no"
    Option "no_dri"                     "no"
# === misc DRI settings ===
    Option "mtrr"                       "off" # disable DRI mtrr mapper, driver has its own code for mtrr
# ### FireGL DDX driver module specific settings ###
# === Screen Management ===
    Option "DesktopSetup"               "0x00000000"
    Option "MonitorLayout"              "TMDS, NONE"
    Option "IgnoreEDID"                 "off"
    Option "HSync2"                     "unspecified"
    Option "VRefresh2"                  "unspecified"
    Option "ScreenOverlap"              "0"
# === TV-out Management ===
    Option "NoTV"                       "yes"     
    Option "ForceMonitors"      "notv"
#    Option "TVStandard"                 "NTSC-M"     
#    Option "TVHSizeAdj"                 "0"     
#    Option "TVVSizeAdj"                 "0"     
#    Option "TVHPosAdj"                  "0"     
#    Option "TVVPosAdj"                  "0"     
#    Option "TVHStartAdj"                "0"     
#    Option "TVColorAdj"                 "0"     
#    Option "GammaCorrectionI"           "0x00000000"
#    Option "GammaCorrectionII"          "0x00000000"
# === OpenGL specific profiles/settings ===
    Option "Capabilities"               "0x00000000"
# === Video Overlay for the Xv extension ===
    Option "VideoOverlay"               "on"
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
#       will be disabled automatically
    Option "OpenGLOverlay"              "off"
# === Center Mode (Laptops only) ===
    Option "CenterMode"                 "off"
# === Pseudo Color Visuals (8-bit visuals) ===
    Option "PseudoColorVisuals"         "off"
# === QBS Management ===
    Option "Stereo"                     "off"
    Option "StereoSyncEnable"           "1"
# === FSAA Management ===
    Option "FSAAEnable"                 "no"
    Option "FSAAScale"                  "1"
    Option "FSAADisableGamma"           "no"
    Option "FSAACustomizeMSPos"         "no"
    Option "FSAAMSPosX0"                "0.000000"
    Option "FSAAMSPosY0"                "0.000000"
    Option "FSAAMSPosX1"                "0.000000"
    Option "FSAAMSPosY1"                "0.000000"
    Option "FSAAMSPosX2"                "0.000000"
    Option "FSAAMSPosY2"                "0.000000"
    Option "FSAAMSPosX3"                "0.000000"
    Option "FSAAMSPosY3"                "0.000000"
    Option "FSAAMSPosX4"                "0.000000"
    Option "FSAAMSPosY4"                "0.000000"
    Option "FSAAMSPosX5"                "0.000000"
    Option "FSAAMSPosY5"                "0.000000"
# === Misc Options ===
    Option "UseFastTLS"                 "2"
    Option "BlockSignalsOnLock"         "on"
    Option "UseInternalAGPGART"         "no"
    Option "ForceGenericCPU"            "no"
    BusID "PCI:1:0:0"    # no device found at config time
    Screen 0
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  "Screen0"
    Device      "ATI Graphics Adapter"
    Monitor     "Monitor0"
    DefaultDepth 24
    #Option "backingstore"

    Subsection "Display"
        Depth       24
        Modes       "1440x900" "1280x800" "1152x864" "1024x768" "800x600" "640x480"
        ViewPort    0 0  # initial origin if mode is smaller than desktop
#       Virtual     1440 900
    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  "Server 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.

    Screen "Screen0"

# 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

### EOF ###


Sorry about not deleting the comments, I just woke up and have to get to work soon.
_________________
Time is what keeps everything from happening all at once.
Back to top
View user's profile Send private message
Aggamemnon
Tux's lil' helper
Tux's lil' helper


Joined: 04 Mar 2004
Posts: 99
Location: Bristol, UK

PostPosted: Fri Feb 17, 2006 11:23 pm    Post subject: Reply with quote

Thanks and where do your libGL.* live?
Back to top
View user's profile Send private message
EzInKy
Veteran
Veteran


Joined: 11 Oct 2002
Posts: 1734
Location: Kentucky

PostPosted: Sat Feb 18, 2006 10:32 pm    Post subject: Reply with quote

Code:

/emul/linux/x86/usr/lib/libGLU.so.1.3
/emul/linux/x86/usr/lib/libGLU.so
/emul/linux/x86/usr/lib/opengl/xorg-x11/lib/libGL.so.1.2
/emul/linux/x86/usr/lib/opengl/xorg-x11/lib/libGL.so
/emul/linux/x86/usr/lib/opengl/xorg-x11/lib/libGL.so.1
/emul/linux/x86/usr/lib/libGLU.so.1
/emul/linux/x86/usr/lib/libGLw.so.1.0
/emul/linux/x86/usr/lib/libGLw.so.1
/emul/linux/x86/usr/lib/libGLw.so
/usr/lib64/opengl/xorg-x11/lib/libGL.so.1.2
/usr/lib64/opengl/xorg-x11/lib/libGL.la
/usr/lib64/opengl/xorg-x11/lib/libGL.so
/usr/lib64/opengl/xorg-x11/lib/libGL.so.1
/usr/lib64/opengl/ati/lib/libGL.so.1.2
/usr/lib64/opengl/ati/lib/libGL.so.1
/usr/lib64/opengl/ati/lib/libGL.so
/usr/lib64/opengl/ati/lib/libGL.la
/usr/lib64/libGLU.la
/usr/lib64/libGLw.so.1.0.0
/usr/lib64/xorg/modules/extensions/libGLcore.so
/usr/lib64/xorg/modules/extensions/libGLcore.la
/usr/lib64/libGLw.so.1.0
/usr/lib64/libGLU.so.1
/usr/lib64/libGLw.so.1
/usr/lib64/libGLU.so
/usr/lib64/libGLw.so
/usr/lib64/libGL.la
/usr/lib64/libGL.so
/usr/lib64/libGLU.so.1.3.060402
/usr/lib32/opengl/ati/lib/libGL.so.1.2
/usr/lib32/opengl/ati/lib/libGL.so.1
/usr/lib32/opengl/ati/lib/libGL.so
/usr/lib32/opengl/ati/lib/libGL.la
/usr/lib32/libGL.so
/usr/lib32/libGL.la
/usr/src/r300/Mesa/lib64/libGL.so.1.2
/usr/src/r300/Mesa/lib64/libGL.so.1
/usr/src/r300/Mesa/lib64/libGL.so
/usr/src/r300/Mesa/lib64/libGLU.so.1.3.060500
/usr/src/r300/Mesa/lib64/libGLU.so.1
/usr/src/r300/Mesa/lib64/libGLU.so
/usr/src/r300/Mesa/lib64/libGLw.so.1.0.0
/usr/src/r300/Mesa/lib64/libGLw.so.1
/usr/src/r300/Mesa/lib64/libGLw.so
/usr/portage/media-libs/mesa/files/lib/libGLU.la
/usr/portage/media-libs/mesa/files/lib/libGL.la
/usr/portage/media-video/nvidia-glx/files/libGL.la

_________________
Time is what keeps everything from happening all at once.
Back to top
View user's profile Send private message
Aggamemnon
Tux's lil' helper
Tux's lil' helper


Joined: 04 Mar 2004
Posts: 99
Location: Bristol, UK

PostPosted: Sun Feb 19, 2006 10:17 pm    Post subject: Reply with quote

Thanks, mine are at:
Code:

/emul/linux/x86/usr/lib/libglib-2.0.so.0.600.5
/emul/linux/x86/usr/lib/libglib-1.2.so.0.0.10
/emul/linux/x86/usr/lib/libglib-1.2.so.0
/emul/linux/x86/usr/lib/libglib-2.0.so.0
/emul/linux/x86/usr/lib/libglib.so
/emul/linux/x86/usr/lib/libglib-2.0.so
/emul/linux/x86/usr/lib/opengl/xorg-x11/extensions/libglx.a
/emul/linux/x86/usr/lib/libglut.so.3.7.1
/emul/linux/x86/usr/lib/libglut.so.3
/emul/linux/x86/usr/lib/libglut.so
/usr/src/r300/Mesa/lib64/libglut.so.3.7.1
/usr/src/r300/Mesa/lib64/libglut.so.3
/usr/src/r300/Mesa/lib64/libglut.so
/usr/lib64/pkgconfig/libglade-2.0.pc
/usr/lib64/opengl/xorg-x11/extensions/libglx.la
/usr/lib64/opengl/xorg-x11/extensions/libglx.so
/usr/lib64/xorg/modules/extensions/libglx.so
/usr/lib64/xorg/modules/extensions/libglx.la
/usr/lib64/libglib-2.0.so.0
/usr/lib64/libglib-2.0.so
/usr/lib64/libglib-2.0.la
/usr/lib64/libglib-1.2.so.0.0.10
/usr/lib64/libglib-1.2.so.0
/usr/lib64/libglib.so
/usr/lib64/libglib.la
/usr/lib64/libglib.a
/usr/lib64/libglade-2.0.so.0.0.7
/usr/lib64/libglade-2.0.so.0
/usr/lib64/libglade-2.0.so
/usr/lib64/libglade-2.0.la
/usr/lib64/libglade-2.0.a
/usr/lib64/libglut.la
/usr/lib64/libglut.so.3.7.1
/usr/lib64/libglut.so
/usr/lib64/libglut.so.3
/usr/lib64/libglib-2.0.so.0.800.5
/usr/lib64/libgle.so.3.0.0
/usr/lib64/libgle.so.3
/usr/lib64/libgle.so
/usr/lib64/libgle.la
/usr/lib64/libgle.a
/usr/lib32/modules/extensions/libglx.a
/usr/lib32/xorg/modules/extensions/libglx.a
Back to top
View user's profile Send private message
Aggamemnon
Tux's lil' helper
Tux's lil' helper


Joined: 04 Mar 2004
Posts: 99
Location: Bristol, UK

PostPosted: Sat Feb 25, 2006 1:29 pm    Post subject: Reply with quote

I managed to fix this by going back to the closed source drivers.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on AMD64 All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum