[gentoo-amd64] accelerated X 7.1 & ATI card

[gentoo-amd64] accelerated X 7.1 & ATI card

[p.pruszczak]

Hi,

I just have a simple question : could anybody who uses xorg-x11 7.1 (~amd64 arch) && have accelerated display on OPEN drivers (NOT ATI) send to me the xorg.conf file ??

I would  be very happy to see "what am I doing wrong ??" ;))

here is what lspci says about my video card:

"VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]"

thanks a lot,

Piotr
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: accelerated X 7.1 & ATI card

[Duncan]

p.pruszczak@pro.onet.pl posted
20060819202354Z1439334-16412+8@kps7.test.onet.pl, excerpted below, on 
Sat, 19 Aug 2006 22:23:40 +0200:

> I just have a simple question : could anybody who uses xorg-x11 7.1
> (~amd64 arch) && have accelerated display on OPEN drivers (NOT ATI) send
> to me the xorg.conf file ??
> 
> I would  be very happy to see "what am I doing wrong ??" ;))
> 
> here is what lspci says about my video card:
> 
> "VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300
> (PCIE)]"

Support for the RV300 series is /very/ new and still somewhat
experimental.  You may get 2D but not 3D support.  You are also likely to
have better luck with the latest xorg 7.2, which may still be masked, I'm
not sure (I loaded it when it was).

I'm still running a 200 series card (Radeon 9200), and it works well, but
your 300 series card support is enough newer that results aren't likely to
be the same.

I'm on my way to work now, but will send my Radeon  driver and xorg-server
numbers after work, so you can compare.  Or just look and unmask
accordingly.  Note that the latest xorg-server and drivers need unmasked
in parallel, as the ABI changed and you can't run an old/new mix.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: accelerated X 7.1 & ATI card

[Reinhard Kotucha]

Hi, please apologize that I hijack the thread but it seems that I have
the same problem as Piotr.

The output of lspci is the same as described by Piotr.  So I think
that we have the same cards.

>>>>> "Duncan" == Duncan  <1i5t5.duncan@cox.net> writes:

  > Support for the RV300 series is /very/ new and still somewhat
  > experimental.  You may get 2D but not 3D support.  You are also
  > likely to have better luck with the latest xorg 7.2, which may
  > still be masked, I'm not sure (I loaded it when it was).

I don't think that the RV300 cards are too new.  I bought it end of
last year and it worked very well with the xorg-6.8 radeon server.

It doesn't work after the latest system update (which switched to
xorg-7.0.0.).

I suppose that I did not install X11 completely.  I renamed /etc/X11
to /etc/X11-backup and re-emerged xorg-x11 in the hope I get a new
/etc/X11 directory.  But this did not happen.  /etc/X11 contains a lot
of files and I assume that many things had been changed there.

I followed the instructions given in

  http://gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml

but I'm not sure that everything I did was correct.

Here is my xorg.conf with all comments removed.  Piotr, does it work
for you?  It's what I used with xorg-6.8.

If it's more convenient for you to download the file instead of
extracting it from this mail, download:

  http://ms25.ath.cx/xorg.conf

This file contains all comments.

__________________________________________________________________

Section "ServerLayout"
	Identifier     "Main Layout"
	Screen      0  "Screen 0" 0 0
	InputDevice    "Mouse1" "CorePointer"
	InputDevice    "Keyboard1" "CoreKeyboard"
EndSection

Section "Files"
	FontPath     "/usr/local/share/fonts/75dpi/"
	FontPath     "/usr/local/share/fonts/75dpi/:unscaled"
	FontPath     "/usr/local/share/fonts/100dpi/"
	FontPath     "/usr/local/share/fonts/100dpi/:unscaled"
	FontPath     "/usr/share/fonts/misc/"
	FontPath     "/usr/share/fonts/urwvn-fonts/"
	FontPath     "/usr/share/fonts/75dpi/:unscaled"
	FontPath     "/usr/share/fonts/100dpi/:unscaled"
	FontPath     "/usr/share/fonts/Type1/"
	FontPath     "/usr/share/fonts/TTF/"
	FontPath     "/usr/share/fonts/75dpi/"
	FontPath     "/usr/share/fonts/100dpi/"
	FontPath     "/usr/share/fonts/intlfonts/"
	FontPath     "/usr/local/share/fonts/lm/"
EndSection

Section "Module"
	Load  "dbe"
	SubSection "extmod"
	Option	    "omit xfree86-dga"
	EndSubSection
	Load  "type1"
	Load  "freetype"
EndSection

Section "ServerFlags"
	Option	    "blank time" "30"	# 10 minutes
	Option	    "standby time" "20"
	Option	    "suspend time" "30"
	Option	    "off time" "60"
EndSection

Section "InputDevice"
	Identifier  "Keyboard1"
	Driver      "kbd"
	Option	    "AutoRepeat" "0 0"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "de"
	Option	    "XkbVariant" "nodeadkeys"
EndSection

Section "InputDevice"
	Identifier  "Mouse1"
	Driver      "mouse"
	Option	    "Protocol" "PS/2"
	Option	    "Device" "/dev/input/mouse0"
EndSection

Section "Monitor"
	Identifier   "Monitor0"
	HorizSync    30.0 - 121.0 # Warning: This may fry old Monitors
	VertRefresh  50.0 - 150.0 # Very conservative. May flicker.

	DisplaySize 400 300

	ModeLine "1856x1392" 288.0 1856 1984 2208 2560   1392 1393 1396 1500 -hsync +vsync
	ModeLine "1920x1440" 234.0 1920 2048 2256 2600   1440 1441 1444 1500 -hsync +vsync
	ModeLine "1920x1440" 297.0 1920 2064 2288 2640   1440 1441 1444 1500 -hsync +vsync
	ModeLine "1800x1440"  230    1800 1896 2088 2392  1440 1441 1444 1490 +HSync +VSync
	ModeLine "1800x1440"  250    1800 1896 2088 2392  1440 1441 1444 1490 +HSync +VSync
EndSection

Section "Device"
	Identifier  "ATI Graphics Adapter 0"
	Driver      "radeon"
	Option      "NoAccel" "no"
	Option      "MergedFB" "off"
	Option      "UseFBDev" "off"
	Option      "BusType" "PCIE"
	Option      "MonitorLayout" "CRT"
EndSection

Section "Screen"
	Identifier "Screen 0"
	Device     "ATI Graphics Adapter 0"
	Monitor    "Monitor 0"
	DefaultDepth     24
    Subsection "Display"
        Depth       8
        Modes       "1800x1440" "1280x1024" "1600x1200"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1800x1440" "1280x1024" "1600x1200"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1800x1440" "1280x1024" "1600x1200"
        ViewPort    0 0
    EndSubsection
EndSection
__________________________________________________________________


Here is the server log:

__________________________________________________________________
xauth:  creating new authority file /root/.serverauth.9354

X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.16-gentoo-r9 x86_64
Current Operating System: Linux zaphod 2.6.16-gentoo-r9 #1 Sun Jun 18 02:52:53 CEST 2006 x86_64
Build Date: 16 August 2006
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Aug 20 04:40:55 2006
(==) Using config file: "/etc/X11/xorg.conf"

(WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found
(**) RADEON(0): RADEONPreInit
(**) RADEON(0): RADEONScreenInit d0000000 0
(**) RADEON(0): Map: 0xd0000000, 0x08000000
(**) RADEON(0): RADEONSave
(**) RADEON(0): RADEONSaveMode(0x708620)
(**) RADEON(0): Read: 0x001c0007 0x00060065 0x00000000
(**) RADEON(0): Read: rd=7, fd=101, pd=6
(**) RADEON(0): RADEONSaveMode returns 0x708620
(**) RADEON(0): RADEONInitMemoryMap() : 
(**) RADEON(0):   mem_size         : 0x08000000
(**) RADEON(0):   agp_size         : 0x00000381
(**) RADEON(0):   agp_base         : 0x006d4540
(**) RADEON(0):   MC_FB_LOCATION   : 0xd7ffd000
(**) RADEON(0):   MC_AGP_LOCATION  : 0xffffffc0
(**) RADEON(0): RADEONModeInit()
1800x1440     250.00  1800 1896 2088 2392  1440 1441 1444 1490 (24,32) +H +V
1800x1440     250.00  1800 1896 2088 2392  1440 1441 1444 1490 (24,32) +H +V
(**) RADEON(0): Pitch = 15204584 bytes (virtualX = 1800, displayWidth = 1856)
(**) RADEON(0): dc=25000, of=25000, fd=111, pd=1
(**) RADEON(0): RADEONInit returns 0x708fd0
(**) RADEON(0): RADEONRestoreMode()
(**) RADEON(0): RADEONRestoreMode(0x708fd0)
(**) RADEON(0): RADEONRestoreMemMapRegisters() : 
(**) RADEON(0):   MC_FB_LOCATION   : 0xd7ffd000
(**) RADEON(0):   MC_AGP_LOCATION  : 0xffffffc0
(**) RADEON(0):   Map Changed ! Applying ...
(**) RADEON(0):   Map applied, resetting engine ...
(**) RADEON(0): Updating display base addresses...
(**) RADEON(0): Memory map updated.
(**) RADEON(0): Programming CRTC1, offset: 0x00000000
(**) RADEON(0): Wrote: 0x0000000c 0x0000006f 0x00000000 (0x0000bf00)
(**) RADEON(0): Wrote: rd=12, fd=111, pd=0
(**) RADEON(0): GRPH_BUFFER_CNTL from 30004c4c to 20577c7c
(**) RADEON(0): RADEONSaveScreen(0)
(**) RADEON(0): Setting up initial surfaces
(**) RADEON(0): Initializing fb layer
(**) RADEON(0): Setting up accel memmap
(**) RADEON(0): Initializing backing store
(**) RADEON(0): Setting up final surfaces
(**) RADEON(0): Initializing Acceleration
(**) RADEON(0): EngineInit (32/32)
(**) RADEON(0): Pitch for acceleration = 232
(**) RADEON(0): EngineRestore (32/32)
(**) RADEON(0): Initializing DPMS
(**) RADEON(0): Initializing Cursor
(**) RADEON(0): Initializing color map
(**) RADEON(0): Initializing DGA
(**) RADEON(0): Initializing Xv
(**) RADEON(0): RADEONScreenInit finished

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Backtrace:
0: X(xf86SigHandler+0x94) [0x478a64]
1: /lib/tls/libc.so.6 [0x2b44e11ec7f0]
2: /usr/lib64/xorg/modules/input/kbd_drv.so [0x2b44e1e17e93]
3: X(InitInput+0x18f) [0x4602df]
4: X(main+0x353) [0x4329e3]
5: /lib/tls/libc.so.6(__libc_start_main+0xe4) [0x2b44e11da644]
6: X(FontFileCompleteXLFD+0xa2) [0x4320ea]

Fatal server error:
Caught signal 8.  Server aborting

(**) RADEON(0): RADEONLeaveVT
(**) RADEON(0): RADEONRestore
(**) RADEON(0): RADEONRestoreMode()
(**) RADEON(0): RADEONRestoreMode(0x708620)
(**) RADEON(0): RADEONRestoreMemMapRegisters() : 
(**) RADEON(0):   MC_FB_LOCATION   : 0x1fff0000
(**) RADEON(0):   MC_AGP_LOCATION  : 0x27ff2000
(**) RADEON(0):   Map Changed ! Applying ...
(**) RADEON(0):   Map applied, resetting engine ...
(**) RADEON(0): Updating display base addresses...
(**) RADEON(0): Memory map updated.
(**) RADEON(0): Programming CRTC1, offset: 0x00000000
(**) RADEON(0): Wrote: 0x001c0007 0x00060065 0x00000000 (0x0000bf00)
(**) RADEON(0): Wrote: rd=7, fd=101, pd=6
(**) RADEON(0): Ok, leaving now...
XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"

      after 0 requests (0 known processed) with 0 events remaining.

__________________________________________________________________

The output of

    strace -f -eopen startx

is at:

   http://ms25.ath.cx/strace_x.log
   http://ms25.ath.cx/strace_x.log.bz2

The log file is 800kB while the bz2 version is only 9kB.

Any ideas what is going wrong?

Regards,
  Reinhard

-- 
----------------------------------------------------------------------------
Reinhard Kotucha			              Phone: +49-511-4592165
Marschnerstr. 25
D-30167 Hannover	                      mailto:reinhard.kotucha@web.de
----------------------------------------------------------------------------
Microsoft isn't the answer. Microsoft is the question, and the answer is NO.
----------------------------------------------------------------------------

-- 
gentoo-amd64@gentoo.org mailing list

Re: Re: [gentoo-amd64] Re: accelerated X 7.1 & ATI card

[p.pruszczak]

[-- Attachment #1: Type: text/plain, Size: 256 bytes --]

Richard, take a look @ :

1. make.conf - radeon line
2. xorg.conf

emerge xorg-x11 x11-drm opengl (?? & mesa??)

eselect-opengl set xorg-x11

glxgears give me now 1000 fps

Duncan - where is masked xorg 7.2 ?? I do not see it in my /usr/portage/profiles ??

[-- Attachment #2: xorg.conf --]
[-- Type: text/plain, Size: 15955 bytes --]

# 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"
	Load  "dbe"
#	    Load  "extmod"
		Load  "fbdevhw"
    Load        "drm"   # libdrm.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.


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


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"	"pl"

EndSection


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

Section "InputDevice"

# Identifier and driver

    Identifier	"Mouse1"
    Driver	"mouse"
    Option "Protocol"    "Auto"	# Auto detect
    Option "Device"      "/dev/input/mice"

# 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  "fe770"

# 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-90

EndSection


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

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
    Identifier	"rv370"
    VendorName	"ATI"
    BoardName	"RV370"

# 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	"radeon"

# 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     "radeon"
    
#    Option "AGPMode" "1"              # 1-8 Does not affect PCIE models.
    Option "AGPFastWrite" "1"         # 1/0 Does not affect PCIE models.
  #  Option "AGPFastwrite" "on"
#    Option "BusType" "PCIE"

Option          "AGPMode" "4" 
          Option          "RenderAccel" "on" 
	            # This two lines are needed to prevent fonts from being scrambled 
		              Option "XaaNoScanlineImageWriteRect" 
			                Option "XaaNoScanlineCPUToScreenColorExpandFill" 
					          # Misc 
     
    Option "EnablePageFlip" "1"       # 1/0 Increases 3D performance substantially 
                                         # seemingly in XAA mode only
					 
     Option "ColorTiling" "1"          # 1/0 Increases 3D performance substantially 
                                         # affected stability only positively on my system
# 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  "rv370"
    Driver      "r300"
    VideoRam    131072
    # Insert Clocks lines here if appropriate
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      "rv370"
    Monitor     "fe770"
    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


[-- Attachment #3: make.conf --]
[-- Type: text/plain, Size: 1660 bytes --]

# These settings were set by the catalyst build script that automatically built this stage
# Please consult /etc/make.conf.example for a more detailed example
USE="X multilib jpeg jpeg2k jp2 lzw lzw-tiff yv12 zlib radeon caps nptl nptlonly jack-tmpfs gtk gnome qt kde alsa jack dvd cdr jpeg ogg opengl readline sdl directfb tiff truetype unicode vorbis xine xml xml2 xvid ieee1394 gtk2 ffmpeg fftw divx4linux dvdr dvdread avi a52 aac 3dnow sse cdparanoia dv ffmpeg gphoto2 multilib perl python portaudio ruby sndfile usb vorbis win32codecs wxwindows dri hal"
CFLAGS="-march=k8 -O2 -pipe "
CHOST="x86_64-pc-linux-gnu"
CXXFLAGS="${CFLAGS}"
MAKEOPTS="-j2"

PORTDIR_OVERLAY=/usr/local/portage

FEATURES="buildpkg ccache"
CCACHE_SIZE="2G"
ACCEPT_KEYWORDS="~amd64"
INPUT_DEVICES="keyboard mouse"
VIDEO_CARDS="ati vesa fbdev"
LANG="en_US"
LINGUAS="pl,en"
ALSA_CARDS="ice1712"




GENTOO_MIRRORS="rsync://distro.ibiblio.org/pub/linux/distributions/gentoo/ http://distro.ibiblio.org/pub/linux/distributions/gentoo/ http://gentoo.osuosl.org/  ftp://ftp.oss.cc.gatech.edu/pub/linux ftp://sunsite.icm.edu.pl/pub/Linux/sunsite.unc.edu/ ftp://gentoo.arcticnetwork.ca/pub/gentoo/ ftp://ftp.tu-dresden.de/pub/Linux/sunsite/ http://distro.ibiblio.org/pub/linux/distributions/gentoo/ ftp://ftp.dtiltas.lt/mirror/gentoo/ http://mirror.uni-c.dk/pub/gentoo/ http://mirror.usu.edu/mirrors/gentoo/  ftp://cs.ubishops.ca/pub/gentoo  http://gd.tuwien.ac.at/opsys/linux/gentoo/ http://ftp.linux.ee/pub/gentoo/distfiles/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://src.gentoo.pl http://gentoo.prz.rzeszow.pl http://gentoo.zie.pg.gda.pl ftp://cs.ubishops.ca/pub/gentoo  "

[gentoo-amd64] Re: accelerated X 7.1 & ATI card

[Duncan]

Reinhard Kotucha <reinhard.kotucha@web.de> posted
17639.58433.905934.461579@zarniwoop.ms25.local, excerpted below, on  Sun,
20 Aug 2006 06:25:37 +0200:

> Hi, please apologize that I hijack the thread but it seems that I have
> the same problem as Piotr.
> 
> The output of lspci is the same as described by Piotr.  So I think
> that we have the same cards.
> 
>>>>>> "Duncan" == Duncan  <1i5t5.duncan@cox.net> writes:
> 
>   > Support for the RV300 series is /very/ new and still somewhat
>   > experimental.  You may get 2D but not 3D support.  You are also
>   > likely to have better luck with the latest xorg 7.2, which may
>   > still be masked, I'm not sure (I loaded it when it was).
> 
> I don't think that the RV300 cards are too new.  I bought it end of
> last year and it worked very well with the xorg-6.8 radeon server.

The cards aren't new, and they've had 2D support for awhile (AFAIK), but
the 3D support is what's new and experimental...  Checking, 3D for
your card isn't yet in what I'm running, either (xf86-video-ati-6.6.1,
xorg-server-1.1.1).  It must be only in CVS/SVN.

> It doesn't work after the latest system update (which switched to
> xorg-7.0.0.).
> 
> I suppose that I did not install X11 completely.  I renamed /etc/X11
> to /etc/X11-backup and re-emerged xorg-x11 in the hope I get a new
> /etc/X11 directory.  But this did not happen.  /etc/X11 contains a lot
> of files and I assume that many things had been changed there.

There's a lot of stuff that has been switching to more standardized
system locations, instead of the old xf86 specific locations.  However,
most of that is in /usr.  Checking here, xorg-server doesn't have anything
in /etc/X11 at all.

FWIW, here's an equery showing all packages I have merged with files in
/etc/X11.  In particular, you'll want to check xinit and if you use it,
xfs (but your fonts section doesn't have a listing for it so you
apparently don't).

$equery b -f /etc/X11/.*
[ Searching for file(s) /etc/X11/.,/etc/X11/.. in *... ]
media-gfx/xloadimage-4.1-r4 (/etc/X11/xloadimagerc)
x11-base/xorg-x11-7.1 (/etc/X11/xorg.conf)
media-sound/xmms-1.2.10-r16 (/etc/X11/wmconfig)
media-sound/xmms-1.2.10-r16 (/etc/X11/wmconfig/xmms)
x11-apps/xfs-1.0.2 (/etc/X11/fs)
x11-apps/xfs-1.0.2 (/etc/X11/fs/config)
x11-apps/xinit-1.0.2-r6 (/etc/X11/Sessions/Xsession)
x11-apps/xinit-1.0.2-r6 (/etc/X11/chooser.sh)
x11-apps/xinit-1.0.2-r6 (/etc/X11/xinit/xinitrc)
x11-apps/xinit-1.0.2-r6 (/etc/X11/Sessions)
x11-apps/xinit-1.0.2-r6 (/etc/X11/xinit)
x11-apps/xinit-1.0.2-r6 (/etc/X11/startDM.sh)
sys-apps/groff-1.19.2-r1 (/etc/X11/app-defaults/GXditview)
sys-apps/groff-1.19.2-r1 (/etc/X11/app-defaults)
x11-libs/motif-config-0.10 (/etc/X11/mwm)
x11-libs/motif-config-0.10 (/etc/X11/mwm/system.mwmrc)
x11-libs/motif-config-0.10 (/etc/X11/app-defaults)
x11-libs/motif-config-0.10 (/etc/X11/app-defaults/Mwm.defaults)
kde-base/kdebase-startkde-3.5.4 (/etc/X11/Sessions)
kde-base/kdebase-startkde-3.5.4 (/etc/X11/Sessions/kde-3.5)

> I followed the instructions given in
> 
>   http://gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml
> 
> but I'm not sure that everything I did was correct.

Good following the instructions, not good of course that you aren't sure
you followed them correctly.

> Here is my xorg.conf with all comments removed. 

[much snippage in file]
 
> Section "Monitor"
> 	Identifier   "Monitor0"
> 	HorizSync    30.0 - 121.0 # Warning: This may fry old Monitors
> 	VertRefresh  50.0 - 150.0 # Very conservative. May flicker.
> 
> 	DisplaySize 400 300

Hmm... nice size monitor size! =8^)  I'm running two that size, @
1600x1200 stacked for 1600x2400.  (I used to run them at 2048x1536 for
2048x3072, but decided that was a bit much.)


> Section "Device"
> 	Identifier  "ATI Graphics Adapter 0"
> 	Driver      "radeon"
> 	Option      "NoAccel" "no"
> 	Option      "MergedFB" "off"
> 	Option      "UseFBDev" "off"
> 	Option      "BusType" "PCIE"
> 	Option      "MonitorLayout" "CRT"
> EndSection
> 
> Section "Screen"
> 	Identifier "Screen 0"
> 	Device     "ATI Graphics Adapter 0"
> 	Monitor    "Monitor 0"

Note that the monitor section above may not be used -- here the ID
specified has a space.  Above, no space.  Does xorg ignore the space and
treat them the same?

> Here is the server log:

> (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1)
> found

This is the only indication of problems there, but as you probably already
know, this is often normal on chips that can have two outputs (whether
your card does or not), with the second instance only auxiliary and not
needed/used under normal circumstances, even when both outputs are used.

The only other thing of note here is how short the log file is.  Mine has
far more stuff about setting up the memory and DMA space and the like, and
about detecting the monitor.  However, I believe 7.1/7.2 are more verbose
in their log, part of that is 3D stuff only and you only have 2D drivers
for that chip, and it may be also be less verbose when you don't have a
direct monitor entry (as I said, it doesn't appear the monitor entry will
be used, due to the space in one place, no-space in the other).

> __________________________________________________________________
> 
> The output of
> 
>     strace -f -eopen startx
> 
> is at:
> 
>    http://ms25.ath.cx/strace_x.log
>    http://ms25.ath.cx/strace_x.log.bz2
> 
> The log file is 800kB while the bz2 version is only 9kB.
> 
> Any ideas what is going wrong?

I checked the strace output.  I'm /not/ an expert in such things and don't
claim to be, but the following caught my eye:

(**) RADEON(0): RADEONScreenInit finished
[pid  9421] open("/proc/bus/pci/devices", O_RDONLY) = 6
[pid  9421] open("/proc/bus/pci/devices", O_RDONLY) = 6
[pid  9421] open("/proc/bus/pci/devices", O_RDONLY) = 6
[pid  9421] open("/proc/bus/pci/devices", O_RDONLY) = 6
[pid  9421] open("/proc/bus/pci/devices", O_RDONLY) = 6
[pid  9421] open("/proc/bus/pci/devices", O_RDONLY) = 6
[pid  9421] open("/proc/bus/pci/devices", O_RDONLY) = 6
[pid  9421] open("/proc/bus/pci/devices", O_RDONLY) = 6
[pid  9421] open("/proc/bus/pci/devices", O_RDONLY) = 6
[pid  9421] open("/proc/bus/pci/devices", O_RDONLY) = 6
[pid  9421] open("/usr/lib64/xserver/SecurityPolicy", O_RDONLY) = 6
[pid  9421] open("/dev/input/mouse0", O_RDWR|O_NONBLOCK) = 6
[pid  9421] --- SIGFPE (Floating point exception) @ 0 (0) ---

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

It looks like it finishes ScreenInit (it /says/ it does <g>), then crashes
just a bit later.  To my inexpert eye anyway, it /appears/ this crash is
right after, thus likely related to, either the SecurityPolicy read, or
the mouse initialization.

Now, that security file is part of xorg-server (according to equery
belongs), which you tried rebuilding, so that /shouldn't/ be the problem. 
Still, double-check it manually.  Open it in an editor and verify that
it's all normal text and looks "clean".  Sometimes a file system
corruption can stick a big block of binary trash in the config file, and
unsurprisingly, coming upon a bunch of binary garbage unexpectedly when
the app expects a nice text configuration can cause a crash! (Yes, I know
I'm stating the obvious. <g>)

The more likely issue from my viewpoint is the mouse config. 
/dev/input/mouse0 exists, right?  I notice in your xorg.conf, in the
ServerFlags section, you don't have an Option "AllowMouseOpenFail" entry.
Try adding that and see what happens.  I don't expect it to work however
because it will still try the mouse and that might be causing the crash. 
Next, try commenting out the mouse device section entirely.  Maybe it will
work then?

Here's what earch (a script I picked up off of the dev list) has to say
about the available mouse drivers:

earch xf86-input-mouse
xf86-input-mouse-1.0.4[0]: amd64 hppa x86 ~x86-fbsd
xf86-input-mouse-1.1.1[0]: alpha ~amd64 arm ~hppa ia64 mips ppc ppc64 sh sparc ~x86 ~x86-fbsd

So 1.0.4 is marked stable amd64, 1.1.1 is ~amd64.  You appear to be on
stable, so should have 1.0.4.  Try remerging it, but just in case, try
remerging x11-proto/inputproto first, /then/ the mouse driver.

Next suggestion if that doesn't work...

Here, in my xorg log, immediately after the RADEONScreenInit finished
entry, I have this:


(**) RADEON(0): RADEONScreenInit finished
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
drmOpenDevice: node name is /dev/dri/card0

Thus, it's possible one of your extensions is causing the crash.  I'd try
remerging all your x11-proto/* packages, then anything owning
/usr/lib64/xorg/proto/.  For reference, here's what an equery belongs
turns up here:

$equery b /usr/lib64/xorg/modules
[ Searching for file(s) /usr/lib64/xorg/modules in *... ]
x11-drivers/xf86-input-keyboard-1.1.0 (/usr/lib64/xorg/modules)
x11-drivers/xf86-video-ati-6.6.1 (/usr/lib64/xorg/modules)
x11-drivers/xf86-input-mouse-1.1.1 (/usr/lib64/xorg/modules)
x11-base/xorg-server-1.1.1 (/usr/lib64/xorg/modules)

You will have remerged most of these above, but if the protos were screwed
up, that may not have fixed it, so after remerging them, hopefully
remerging these fixes the problem.

If you are still having issues after that... it's time to consider filing
a bug and seeing if the Gentoo xorg team can help.  I'm sure they have
more experience looking at those files for problems than most of us do. 
(I have a great respect for them.  It must be a big job dealing with all
the various xorg issues for all of Gentoo, even more so than most
distribs, given Gentoo's every user compiles from sources strategy, with
the immense variety in local
environments/compilers/kernels/binutils/glibcs/etc people have.  It's not
a job I'd want, but they actually volunteer for it!  As I said, a very
great respect!)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: accelerated X 7.1 & ATI card

[Duncan]

p.pruszczak@pro.onet.pl posted
20060820155956Z11036-13481+218@kps2.test.onet.pl, excerpted below, on Sun,
20 Aug 2006 18:03:51 +0200:

> Duncan - where is masked xorg 7.2 ?? I do not see it in my
> /usr/portage/profiles ??

As best I know, what happened is that xorg-7.2 is very similar to 7.1, a
bugfix release with only some files updated.  As Gentoo now has modular-X,
what that means for Gentoo is that they didn't have to upgrade everything,
only some of the packages.  Note that the xorg-x11 package itself is a
meta-package, consisting almost entirely of dependencies.  Since all the
updates were bug fixes, they didn't put out an xorg-7.2 metapackage but
simply updated all the modular dependencies, which then got pulled in
under the xorg-7.1 metapackage as soon as they were unmasked.

What I do know is that very shortly after the public xorg-7.2 announcement,
several of the Gentoo xorg modules including xf86-video-ati and xorg-server
were updated.  I've always believed that group of updates were what
constituted xorg-7.2, for binary and non-modular distributions.

Anyway, that's what I'm referring to when I say xorg 7.2.  Maybe I've been
deluding myself.  =8^)

It was in an earlier reply but that one was long, so I'll repeat it here
where it's easy to find.  I'm running:

xf86-video-ati-6.6.1
xorg-server-1.1.1

I had thought that xorg now included 3D for the r300 series.  However, it
looks like it's still only 2D with the 6.6.1 I have (presumably xorg 7.2).
The new 3D support must still be upcoming, repository only at this point,
but I'd assume coming for 7.3.

Hope that clears things up.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: accelerated X 7.1 & ATI card

[Andrei Slavoiu]

--- Duncan <1i5t5.duncan@cox.net> wrote:

> p.pruszczak@pro.onet.pl posted
> 20060820155956Z11036-13481+218@kps2.test.onet.pl,
> excerpted below, on Sun,
> 20 Aug 2006 18:03:51 +0200:
> 
> > Duncan - where is masked xorg 7.2 ?? I do not see
> it in my
> > /usr/portage/profiles ??
> 
> As best I know, what happened is that xorg-7.2 is
> very similar to 7.1, a
> bugfix release with only some files updated.
This bugfix release is called 7.1.1, 7.2 is planned
for November.

> I had thought that xorg now included 3D for the r300
> series.  However, it
> looks like it's still only 2D with the 6.6.1 I have
> (presumably xorg 7.2).
3D acceleration for r300 is included since 7.0. It's
still not complete, but it's allready usable in 7.1
for most applications (at least on my Radeon 9550).


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: accelerated X 7.1 & ATI card

[Piotr Pruszczak]

By the way - do you have DRM working ??

Unfortunately, doing everything step-by-step like is described on gentoo 
forum in topic related to drm under FREE drivers - I have not DRM due to 
  missing libGL.so.1 --->> when switching openGL to mesa-cvs..

when switching to xorg-x11 I have NOT drm enabled (??why??) and I have 
some acceleration - 1000 fps is "almost usable for games.."



Best regards,
Piotr
> 
>> I had thought that xorg now included 3D for the r300
>> series.  However, it
>> looks like it's still only 2D with the 6.6.1 I have
>> (presumably xorg 7.2).
> 3D acceleration for r300 is included since 7.0. It's
> still not complete, but it's allready usable in 7.1
> for most applications (at least on my Radeon 9550).
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: accelerated X 7.1 & ATI card

[Andrei Slavoiu]

--- Piotr Pruszczak <p.pruszczak@pro.onet.pl> wrote:

> By the way - do you have DRM working ??
Yes I have. I use the DRM drivers in kernel 2.6.17,
not the separate ebuild which is recommended in the
HOWTO because it works and it's easier to update if
it's in kernel.
> 
> Unfortunately, doing everything step-by-step like is
> described on gentoo 
> forum in topic related to drm under FREE drivers - I
> have not DRM due to 
>   missing libGL.so.1 --->> when switching openGL to
> mesa-cvs..
I don't know what guide you followed but if you are
using the cvs version of mesa it sounds a little
extreme to me :) I suggest you get rid of all the
experimental stuff you installed following that guide
then use the official Gentoo HOWTO
http://gentoo-wiki.com/HOWTO_DRI_with_ATi_Open-Source_Drivers
> 
> when switching to xorg-x11 I have NOT drm enabled
> (??why??) and I have 
> some acceleration - 1000 fps is "almost usable for
> games.."
So you want to say that glxinfo reports: "direct
rendering: No" but you still get 1000 fps in glxgears?
I find it hard to believe you can get so many fps
without hardware acceleration.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: accelerated X 7.1 & ATI card

[Duncan]

Andrei Slavoiu <ansla80@yahoo.com> posted
20060820220038.46514.qmail@web31611.mail.mud.yahoo.com, excerpted below,
on  Sun, 20 Aug 2006 15:00:38 -0700:

> --- Duncan <1i5t5.duncan@cox.net> wrote:
> 
>> p.pruszczak@pro.onet.pl posted
>> 20060820155956Z11036-13481+218@kps2.test.onet.pl, excerpted below, on
>> Sun,
>> 20 Aug 2006 18:03:51 +0200:
>> 
>> > Duncan - where is masked xorg 7.2 ?? I do not see
>> it in my
>> > /usr/portage/profiles ??
>> 
>> As best I know, what happened is that xorg-7.2 is very similar to 7.1,
>> a
>> bugfix release with only some files updated.
> This bugfix release is called 7.1.1, 7.2 is planned for November.
> 
>> I had thought that xorg now included 3D for the r300 series.  However,
>> it
>> looks like it's still only 2D with the 6.6.1 I have (presumably xorg
>> 7.2).
> 3D acceleration for r300 is included since 7.0. It's still not complete,
> but it's allready usable in 7.1 for most applications (at least on my
> Radeon 9550).

Hmm...  I /thought/ it was there, but the manpage said no...

SUPPORTED HARDWARE
   The radeon driver supports PCI and AGP video cards based on the
   following ATI chips
   [snip]
   RV370       Radeon X300, M22 (2d only)
[snip]
Version 11            xf86-video-ati 6.6.1              RADEON(4x)

So that's the current manpage.  <shrug>  That's why I recanted and said it
wasn't there yet, once I looked at the manpage.  Maybe the manpage is
wrong?  I know it had /some/ updates for 6.6.1, as the options tweaked a
bit.  Maybe they updated the options but forgot to upgrade the supported
hardware status?

You are absolutely right on the xorg version, 7.1.1 not 7.2, I just
verified. I had read the site and seen the release schedule and that the
next (major) release was 7.2, but that was before 7.1.1, so I got
confused.  The x.y.1 version numbers make rather more sense, now!

Now I'm wondering how many people I ended up steering wrong, saying 7.2,
when it was 7.1.1.  Oh, well, at least I'm straight now. =8^%  I hope I
didn't mix up anyone /too/ badly. <sigh>

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: accelerated X 7.1 & ATI card

[Andrei Slavoiu]

--- Duncan <1i5t5.duncan@cox.net> wrote:
> Hmm...  I /thought/ it was there, but the manpage
> said no...
[snip]
> Maybe the manpage is
> wrong?  I know it had /some/ updates for 6.6.1, as
> the options tweaked a
> bit.  Maybe they updated the options but forgot to
> upgrade the supported
> hardware status?
Well, it looks like it was intentionally omitted from
the man page to not raise people's expectations too
much... at least according to this bug report
https://bugs.freedesktop.org/show_bug.cgi?id=6457
which contains no comment from an actual developer...

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: accelerated X 7.1 & ATI card

[Duncan]

Andrei Slavoiu <ansla80@yahoo.com> posted
20060821110100.64385.qmail@web31610.mail.mud.yahoo.com, excerpted below,
on  Mon, 21 Aug 2006 04:01:00 -0700:

> --- Duncan <1i5t5.duncan@cox.net> wrote:
>> Hmm...  I /thought/ it was there, but the manpage said no...
> [snip]
>> Maybe the manpage is
>> wrong?  I know it had /some/ updates for 6.6.1, as the options tweaked a
>> bit.  Maybe they updated the options but forgot to upgrade the supported
>> hardware status?
> Well, it looks like it was intentionally omitted from the man page to not
> raise people's expectations too much... at least according to this bug
> report https://bugs.freedesktop.org/show_bug.cgi?id=6457 which contains no
> comment from an actual developer...

Makes sense... but they /could/ put (2D support, 3D experimental) instead
of (2D only).  Thanks.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: Re: [gentoo-amd64] Re: accelerated X 7.1 & ATI card

[Reinhard Kotucha]

Hi Piotr,
thank you for sending me your xorg.conf.  It works for me.  I have no
time to find out what was wrong with mine.  But maybe it has something
to do with the mouse:  You have

  Option "Device" "/dev/input/mice"

and I had

  Option "Device" "/dev/input/mouse0"
.

I now adopted your file for my needs and I'm happy.

Thanks again,
  Reinhard

-- 
----------------------------------------------------------------------------
Reinhard Kotucha			              Phone: +49-511-4592165
Marschnerstr. 25
D-30167 Hannover	                      mailto:reinhard.kotucha@web.de
----------------------------------------------------------------------------
Microsoft isn't the answer. Microsoft is the question, and the answer is NO.
----------------------------------------------------------------------------



-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: accelerated X 7.1 & ATI card

[Reinhard Kotucha]

Hi Duncan,

I solved my problem by using Piotr's xorg.conf.

>>>>> "Duncan" == Duncan  <1i5t5.duncan@cox.net> writes:

  > The cards aren't new, and they've had 2D support for awhile
  > (AFAIK), but the 3D support is what's new and experimental...

at the moment I'm happy with 2D support.  I don't have any game
installed deliberately (besides "M-x tetris" in Emacs).  

  >> Section "Monitor" Identifier "Monitor0" HorizSync 30.0 - 121.0 #
  >> Warning: This may fry old Monitors VertRefresh 50.0 - 150.0 #
  >> Very conservative. May flicker.
  >> 
  >> DisplaySize 400 300

  > Hmm... nice size monitor size! =8^) I'm running two that size, @
  > 1600x1200 stacked for 1600x2400.  (I used to run them at 2048x1536
  > for 2048x3072, but decided that was a bit much.)

I spent a lot of money for the monitor.  But I spend most of the time
with TeX and beautiful fonts.  Hence I think it's worth the money,
especially because it's now 8 years old and still works properly.
And every craftsman will tell you that the most important thing is to
have good tools.  That was my thought when I bought it.

  > Note that the monitor section above may not be used -- here the ID
  > specified has a space.  Above, no space.  Does xorg ignore the
  > space and treat them the same?

Hmm, at least xorg-6.8 didn't complain.

  >> (WW) RADEON: No matching Device section for instance (BusID
  >> PCI:1:0:1) found

  > This is the only indication of problems there, but as you probably
  > already know, this is often normal on chips that can have two
  > outputs (whether your card does or not), with the second instance
  > only auxiliary and not needed/used under normal circumstances,
  > even when both outputs are used.

I got this warning in the past and I assumed that it has to do with
the second channel.  So I decided to ignore this message.

  > I checked the strace output.  I'm /not/ an expert in such things
  > and don't claim to be, but the following caught my eye:

  >> open("/usr/lib64/xserver/SecurityPolicy", O_RDONLY) = 6 [pid 9421]
  >> open("/dev/input/mouse0", O_RDWR|O_NONBLOCK) = 6 [pid 9421] ---
  >> SIGFPE (Floating point exception) @ 0 (0) ---

  > The more likely issue from my viewpoint is the mouse config.
  > /dev/input/mouse0 exists, right?

This worked in the past.  I'm using /dev/input/mice from Piotr's
config file now.  But note that I didn't update X11 only but the
whole system.  Maybe something changed somewhere else.

Regards, and many thanks for your response,
  Reinhard

-- 
----------------------------------------------------------------------------
Reinhard Kotucha			              Phone: +49-511-4592165
Marschnerstr. 25
D-30167 Hannover	                      mailto:reinhard.kotucha@web.de
----------------------------------------------------------------------------
Microsoft isn't the answer. Microsoft is the question, and the answer is NO.
----------------------------------------------------------------------------


-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: accelerated X 7.1 & ATI card

[Duncan]

Reinhard Kotucha <reinhard.kotucha@web.de> posted
17642.11592.908814.99989@zarniwoop.ms25.local, excerpted below, on  Tue,
22 Aug 2006 00:01:44 +0200:

> Hi Piotr,
> thank you for sending me your xorg.conf.  It works for me.  I have no time
> to find out what was wrong with mine.  But maybe it has something to do
> with the mouse:  You have
> 
>   Option "Device" "/dev/input/mice"
> 
> and I had
> 
>   Option "Device" "/dev/input/mouse0"
> .
> 
> I now adopted your file for my needs and I'm happy.

Replying here rather than to my subthread...

Indeed, I strongly suspect it /is/ mouse related.  As I mentioned in the
other subthread, you can set an option to ignore mouse errors and use only
keyboard in that case.  Setting that in your old xorg.conf and seeing if X
would then start would at least confirm whether it was mouse related or not.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list