ATI or Nvidia?...

Main Page | Report this Page

Linux Forum Index » Linux Hardware » ATI or Nvidia?...

Page 1 of 2 Goto page 1, 2 Next

ATI or Nvidia?...

Author

Message

HamRadio...

Posted: Thu Oct 22, 2009 8:56 am

Guest

Hi,
I'm planning to buy a new graphic card fo my Debian Squeeze box (EM64T).
Until now I've always bought Nvidia cards because of their (fairly) good
Linux support, even though their drivers are proprietary.
I don't like too much having these proprietary drivers "tainting" my
kernel, so I'm guessing if it's time to switch to ATI cards because of
their releasing of open source drivers.
What should you suggest?
Where could I find some performance tests between those two kind of
drivers?
Thanks for answering.

--
toglimi.hamradio at (no spam) toglimi.quipo.it
ANTI-SPAM: please cut "toglimi." for my real e-mail address.
Pentium4 3.00GHz, Linux 2.6.30.8-2-x86_64 on Debian GNU/Linux squeeze/sid
Registered Linux user #291116 http://counter.li.org

ray...

Posted: Thu Oct 22, 2009 9:24 am

Guest

On Thu, 22 Oct 2009 14:56:37 +0000, HamRadio wrote:

Quote:

You're overlooking intel. The intel video drivers have really settled in
the last couple of years. And the via openchrome driver ain't bad either.

Dan C...

Posted: Thu Oct 22, 2009 9:27 am

Guest

On Thu, 22 Oct 2009 14:56:37 +0000, HamRadio wrote:

Quote:

I'd suggest staying with the Nvidia cards and their proprietary driver.
Why sacrifice performance and stability (both rock-solid) in some
idealistic attempt at staying "open"? Screw that. ATI drivers suck ass,
and always have.

Quote:

Where could I find some performance tests between those two kind of
drivers?

On any of thousands of sites found simply with a Google search.

Quote:

Thanks for answering.

Welcome.

--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as he garotted another passing Liberal.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/

philo...

Posted: Thu Oct 22, 2009 9:55 am

Guest

Dan C wrote:

Quote:

On Thu, 22 Oct 2009 14:56:37 +0000, HamRadio wrote:

Hi,
I'm planning to buy a new graphic card fo my Debian Squeeze box (EM64T).
Until now I've always bought Nvidia cards because of their (fairly) good
Linux support, even though their drivers are proprietary. I don't like
too much having these proprietary drivers "tainting" my kernel, so I'm
guessing if it's time to switch to ATI cards because of their releasing
of open source drivers. What should you suggest?

I'd suggest staying with the Nvidia cards and their proprietary driver.
Why sacrifice performance and stability (both rock-solid) in some
idealistic attempt at staying "open"? Screw that. ATI drivers suck ass,
and always have.

Where could I find some performance tests between those two kind of
drivers?

On any of thousands of sites found simply with a Google search.

Thanks for answering.

Welcome.

I also have had excellent result with Nvidia...
though I do use their drivers...I found that even without them, Debian
does a great job of probing the video...but with the proprietary drivers
you get additional adjustments and tweaks

As it turned out...all I needed was a few simple shell scripts for me to
easily change the brightness...
I have one preferred setting for graphics and another for text

Aragorn...

Posted: Thu Oct 22, 2009 11:33 am

Guest

On Thursday 22 October 2009 17:27 in comp.os.linux.hardware, somebody
identifying as Dan C wrote...

Quote:

On Thu, 22 Oct 2009 14:56:37 +0000, HamRadio wrote:

I'm planning to buy a new graphic card fo my Debian Squeeze box
(EM64T). Until now I've always bought Nvidia cards because of their
(fairly) good Linux support, even though their drivers are
proprietary. I don't like too much having these proprietary drivers
"tainting" my kernel, so I'm guessing if it's time to switch to ATI
cards because of their releasing of open source drivers. What should
you suggest?

I'd suggest staying with the Nvidia cards and their proprietary
driver. Why sacrifice performance and stability (both rock-solid) in
some idealistic attempt at staying "open"? Screw that. ATI drivers
suck ass, and always have.

We've actually been discussing this a few days ago in a Belgian
GNU/Linux newsgroup. The thing is that ATi has always had a smaller
team of developers for the Linux version of their drivers than nVidia
did, and while ATi cards were qualitywise as good as their nVidia
counterparts, their drivers were so bad that you couldn't even get a
decent color balance out of their cards.

Now that AMD has purchased ATi, they probably have access to the
proprietary driver code and they will be able to study it, which puts
them a step ahead of the kernel hackers who have to reverse-engineer
the hardware to come up with a driver, but as the code still contains
proprietary blobs which AMD cannot release even if they wanted to,
they'll have to rewrite the whole thing from scratch. The AMD/ATi
drivers which are out now as FOSS are still only at a very preliminary
stage and still don't offer the quality of the nVidia drivers.

I am all for FOSS, and I do have the political motivation, but being
idealistic is one thing, and being pragmatic and efficient is another.
At this stage, nVidia offers the best possible drivers and high quality
video adapters. The drivers are proprietary but they are offered
freely for download, so it's not like we'd be stealing anything by
using nVidia drivers. ;-)

--
*Aragorn*
(registered GNU/Linux user #223157)

Aragorn...

Posted: Thu Oct 22, 2009 11:37 am

Guest

On Thursday 22 October 2009 17:55 in comp.os.linux.hardware, somebody
identifying as philo wrote...

Quote:

Not just additional tweaks. Probing the video is one thing, but the
open source "nv" driver which will be automatically detected and set up
by your distribution cannot use the 3D acceleration of the graphics
card, while the proprietary driver can. So if you're going to run
Compiz or KDE 4 with all the eyecandy turned on, then you need the
proprietary driver either way.

--
*Aragorn*
(registered GNU/Linux user #223157)

ArameFarpado...

Posted: Thu Oct 22, 2009 11:46 am

Guest

Em Quinta 22 Outubro 2009 16:27, Dan C escreveu:

Quote:

I second that.

HamRadio...

Posted: Thu Oct 22, 2009 12:19 pm

Guest

Il Thu, 22 Oct 2009 15:24:59 +0000, ray ha scritto:

Quote:

You're overlooking intel.
No, I don't. In fact I do have an Intel "Cantiga" graphic chip on my

notebook and I'm very happy with it.
I'd like I could buy an Intel graphic card, but too bad their graphic
chips can only be found as integrated chips on motherboards/notebook...

--
toglimi.hamradio at (no spam) toglimi.quipo.it
ANTI-SPAM: please cut "toglimi." for my real e-mail address.
Pentium4 3.00GHz, Linux 2.6.30.8-2-x86_64 on Debian GNU/Linux squeeze/sid
Registered Linux user #291116 http://counter.li.org

Darren Salt...

Posted: Thu Oct 22, 2009 1:09 pm

Guest

I demand that Aragorn may or may not have written...

[snip]

Quote:

Now that AMD has purchased ATi, they probably have access to the
proprietary driver code

philo...

Posted: Thu Oct 22, 2009 2:16 pm

Guest

Aragorn wrote:

Quote:

On Thursday 22 October 2009 17:55 in comp.os.linux.hardware, somebody
identifying as philo wrote...

I also have had excellent result with Nvidia...
though I do use their drivers...I found that even without them, Debian
does a great job of probing the video...but with the proprietary
drivers you get additional adjustments and tweaks

Not just additional tweaks. Probing the video is one thing, but the
open source "nv" driver which will be automatically detected and set up
by your distribution cannot use the 3D acceleration of the graphics
card, while the proprietary driver can. So if you're going to run
Compiz or KDE 4 with all the eyecandy turned on, then you need the
proprietary driver either way.

OK

well, the first thing I do when I setup any of my own machines is turn
off all eye candy...

some people love it though...that's fine

General Schvantzkoph...

Posted: Thu Oct 22, 2009 3:00 pm

Guest

On Thu, 22 Oct 2009 19:37:17 +0200, Aragorn wrote:

Quote:

On Thursday 22 October 2009 17:55 in comp.os.linux.hardware, somebody
identifying as philo wrote...

I also have had excellent result with Nvidia... though I do use their
drivers...I found that even without them, Debian does a great job of
probing the video...but with the proprietary drivers you get additional
adjustments and tweaks

Not just additional tweaks. Probing the video is one thing, but the
open source "nv" driver which will be automatically detected and set up
by your distribution cannot use the 3D acceleration of the graphics
card, while the proprietary driver can. So if you're going to run
Compiz or KDE 4 with all the eyecandy turned on, then you need the
proprietary driver either way.

The NV driver has been replaced by the Nouveau driver which can do some
3D, however the proprietary NVidia drivers are still the best choice.

Baho Utot...

Posted: Thu Oct 22, 2009 3:03 pm

Guest

On Thu, 22 Oct 2009 15:27:18 +0000, Dan C wrote:

Quote:

On Thu, 22 Oct 2009 14:56:37 +0000, HamRadio wrote:

Hi,
I'm planning to buy a new graphic card fo my Debian Squeeze box
(EM64T). Until now I've always bought Nvidia cards because of their
(fairly) good Linux support, even though their drivers are proprietary.
I don't like too much having these proprietary drivers "tainting" my
kernel, so I'm guessing if it's time to switch to ATI cards because of
their releasing of open source drivers. What should you suggest?

I'd suggest staying with the Nvidia cards and their proprietary driver.
Why sacrifice performance and stability (both rock-solid) in some
idealistic attempt at staying "open"? Screw that. ATI drivers suck
ass, and always have.

Where could I find some performance tests between those two kind of
drivers?

On any of thousands of sites found simply with a Google search.

Thanks for answering.

Welcome.

Haven't heard of radeonhd have you

Running

1:00.0 VGA compatible controller: ATI Technologies Inc RV730XT [Radeon HD
4670]

with OSS drivers with 3D and I have also run catalyst drivers, both work
well both esay to setup and run

pacman -S catalyst
aticonf --inital

done

[scrat at (no spam) arch-64 ~]$ aticonfig --help
Usage: aticonfig [OPTION] ...
Parses an existing X-Server configuration file and modifies it to operate
with
ATI products.

The following command-line options can be invoked as parameters:

ATI Initial Configuration:
--initial
Generate a default ATI device section in the configuration file
which
is capable of loading the fglrx driver.
--initial=dual-head
Same as '--initial' but generate a basic dual head configuration
file.
--initial=check
Identifies if the fglrx driver is present in configuration file.

TV Options:
--tvf, --tv-format-type=STRING
Change the TV signal format. STRING can be one of:
NTSC-M
NTSC-JPN
NTSC-N
PAL-B
PAL-COMB-N
PAL-D
PAL-G
PAL-H
PAL-I
PAL-K
PAL-K1
PAL-L
PAL-M
PAL-N
PAL-SECAM-D
PAL-SECAM-K
PAL-SECAM-K1
PAL-SECAM-L
Note: Not all graphics cards support every mode. Regional
settings are applicable.
--tvs, --tv-standard-type=STRING
Change the TV standard for TV output. STRING can be one of:
VIDEO
SCART
YUV
--tv-overscan={on|off}
Enable or disable overscan mode for TVout
Note, not all tv-formats support overscan. Try to
toggle overscan off before changing tv-format if
and error occurs.
--tv-info
Print out the current tv geometry, tv format, and if the
tv is physically connected.
--tv-geometry=WIDTHxHEIGHT{+|-}X{+|-}Y
=WIDTHxHEIGHT
Change the size and position of the TVout display.
WIDTH and HEIGHT are in percentage units. Please note
that the valid range for WIDTH and HEIGHT depends on
the tv-format selected. However, as a rule of thumb
WIDTH and HEIGHT are valid in the range [1,100]
X and Y are pixels offsets from centre
of the screen. X and Y are have variable ranges dependant
on ASIC. Use tv-info to get valid X and Y ranges
If tv-geometry is invoked with just width and height
then X and Y are assumed to be 0
See example 5 below for a sample usage.

FireGL Workstation Board Features:
--app, --use-app-profile=STRING
Change the application profile for a FireGL workstation board.
STRING can be one of:
default
maya
softimage-xsi
softimage-3d
houdini4.0
houdini5.0
houdini5.5
Screen-Related Options:
--ovt, --overlay-type=STRING
Change the overlay for the X server. STRING can be one of:
opengl
disable
--ovon, --overlay-on={0|1}
Choose which head the hardware overlay should be visible on. The
hardware overlay can be used for either OpenGL, video, pseudo-
color
or stereo.
--lcd, --lcd-mode=STRING
Change the LCD mode. STRING can be one of:
center
full
--dtop, --desktop-setup=STRING
Change the desktop setup for multiple display adapters.
STRING can be one of:
single 1 screen, second dark
mirror 2 screens - same content, identical
refresh rate/resolution
Note: This option is NOT supported with
Avivo
clone 2 screens - same content, allows for
different refresh rates/resolutions
horizontal 2 screens - one framebuffer,
screen 1 right of screen 0
horizontal,reverse 2 screens - one framebuffer,
screen 1 left of screen 0
vertical 2 screens - one framebuffer,
screen 1 above of screen 0
vertical,reverse 2 screens - one framebuffer,
screen 1 below of screen 0
Note: This option is not valid if '--initial=dual-head' is
specified.
--vs, --sync-vsync={on|off}
Enable/disable sync buffer swaps with vsync. Enable this option
to
prevent tearing during 3D rendering.
--psc, --pseudo-color={on|off}
Enable/disable pseudo-color visuals. Enable this option to get
16-bit
color support.
--sm, --stereo-mode={active | horizontalInterleave | verticalInterleave
| off}
Enable/disable stereo support. Enable active option only for
applications that support the use of hardware 3D shutter glasses.
For the use of horizontalInterleave and verticalInterleave modes
specialized monitor equipment is required.
--resolution=Screen#,W1xH1,W2xH2,W3xH3,...
Set the modes for the specified screen. You may specify several
resolutions separated by commas.
Screens start at 0. You can use 1 for dual-head
--hsync=Screen#,LOW-HIGH
Change the horizontal sync range of the specified monitor. Make
sure
you know the capabilities of your monitor before changing this
option.
Screens start at 0. You can use 1 for dual-head
--vrefresh=Screen#,LOW-HIGH
Change the vertical refresh range of the specified monitor. Make
sure
you know the capabilities of your monitor before changing this
option.
Screens start at 0. You can use 1 for dual-head
--hsync2=LOW-HIGH
Change the horizontal sync range of the second display. Make
sure you
know the capabilities of your monitor before changing this option.
--vrefresh2=LOW-HIGH
Change the vertical refresh range of the second display. Make
sure you
know the capabilities of your monitor before changing this option.
--mode2=W1xH1,W2XH2,W3xH3,...
Change the modes for the second display. You may specify several
resolutions separated by commas. Only valid for clone and big
desktop
settings.
--screen-layout={left|right|above|below}
Set the secondary screen position for dual head.
--screen-overlap=NUM
Set the screen overlap region in big desktop mode to be NUM
pixels.
--force-monitor=STRING[,STRING...]
Describe all displays that are to be enabled and/or disabled
regardless
of physical connection. STRING can be one or more of the
following
set, separated by commas:
crt1
crt2
lvds
tv
cv
tmds1
tmds2
tmds2i
dfp3
dfp4
dfp5
dfp6
nocrt1
nocrt2
nolvds
notv
nocv
notmds1
notmds2
notmds2i
nodfp3
nodfp4
nodfp5
nodfp6

Advanced Options:
--sync-video={on|off}
Enable/disable sync to vsync for AVIVO video.
This option is enabled by default and is used to prevent
video tearing. By disabling this option video is free to
render as fast as the 3D engine can handle. In the case of
choppy video try to disable sync-video.
--tls={on|off}
Enable/disable fast thread local storage. Disable this option
when
virtual machines or WineX fail to work properly.
--sb, --signal-block={on|off}
Enable/disable signal blocking. Disable this option when
debugging a
multi-threaded OpenGL application.
--locked-userpages={on|off}
Enable/disable locked user pages. Disable this option if the
system
hangs when running fgl_glxgears.
User page lock is no longer available on AGP system now.
--max-gart-size=VALUE1,VALUE2
Set user-defined max total GART size(VALUE1) and cacheable gart
size(VALUE2) for non-AGP systems.
This option can combined with --adapter option to set the gart
size
for individual card.

Dynamic Display Management Options:
Following options will not change the config file. They are
used for querying driver, controller and adaptor information.
These options will be effective immediately. Other options on
the same command line will be ignored.
--enable-monitor=STRING,STRING
Setting current monitor to be enabled. Only 2 displays
can be enabled at the same time. Any displays
that are not on the list will be disabled.
STRING can be one of the following set, separated
by commas:
none
crt1
crt2
lvds
tv
cv
tmds1
tmds2
tmds2i
dfp3
dfp4
dfp5
dfp6
auto -- use default policy to enable the displays.
--query-monitor
This will return connected and enabled monitor information
--swap-monitor
This only works for big desktop setup. This will swap the
contents on the two monitors.
--swap-screens={on|off}
Enable/disable swap heads in dual-head mode.
This option works only in dual-head mode.

Pair mode options:
Following options are used for query add and remove pair modes.
These options will be effective immediately. Other options on
the same command line will be ignored.
--list-pairmode
list all the current existing pair modes the driver can use.
--add-pairmode=width0xheight0+width1xheight1
Add one pair mode to the list. width0 and height0 are the
size of primary display and width1 and height1 for the
secondary display.
--remove-pairmode=index
Remove one pair mode from the list. User can get index by
list-pairmode.

External Events Daemon Options:
Following options will not change the config file. They are
used to send commands to the atieventsd external events daemon.
--set-policy=STRING
Sets the event policy for the daemon to be STRING.
See the atieventsd( Cool

manpage for further details.

Display attribute options:
Following options are used for query and set adjustment of
specific attribute for specific display. These options will be
effective immediately. Other options on the same command line
will be ignored.
The DISPLAYTYPE in options can be one of the following strings:
crt1, lvds, tv, cv, tmds1, crt2,
tmds2, tmds2i, dfp3, dfp4, dfp5, dfp6 .
The ATTRIBTYPE in options can be one of the following strings:
brightness, contrast, saturation, hue, positionX,
positionY, sizeX, sizeY, overscan, videoStandard
--query-dispattrib=DISPLAYTYPE,ATTRIBTYPE
query the specific adjustment info of the specific display.
if ATTRIBTYPE is not specified, all supported attribute
information will be printed out.
--set-dispattrib=DISPLAYTYPE,ATTRIBTYPE:VALUE
set the attribute value of the specific display.

Connector type options:
Following options are used for query connector type
for specific display. These options will be
effective immediately. Other options on the same command line
will be ignored.
The DISPLAYTYPE in options can be one of the following strings:
crt1, lvds, tv, cv, tmds1, crt2,
tmds2, tmds2i, dfp3, dfp4, dfp5, dfp6 .
--query-connectortype=DISPLAYTYPE
query the connector type of the specific display.

Component video dongle options:
Following options are used for query and set dongles for a
component video. These options will be effective immediately.
Other options on the same command line will be ignored.
--query-cvdongle
query dongle setting informations of the component video.
--set-cvdongle=VALUE
set the custom override value of the CV dongle.
--reset-cvdongle
reset the custom override setting(to zero)of the CV dongle.

Component video customized mode options:
Following options are used for query and set customized mode for
component video. These options will be effective immediately.
Other options on the same command line will be ignored.
--query-cvmode
query customized modes for component video.
--add-cvmode=WIDTH,HEIGHT,FLAGS,BASEWIDTH,BASEDHEIGHT,REFRESH.
add a customized mode for component video.
--validate-cvmode=WIDTH,HEIGHT,FLAGS,BASEWIDTH,BASEHEIGHT,REFRESH.
validate a customized mode for component video.
--delete-cvmode=INDEX
delete one customized mode for component video.

Persistent Configuration Store (PCS) Options:
Following options will not change the config file. They are
used to manipulate the PCS database. Due to their nature, these.
commands may only be run by the root user. Note that the prefix
and key names are not case-sensitive.
--get-pcs-key=PREFIX,KEY
Prints out the specified prefix and key from the PCS
database. The type of data will be shown along with
the contents.
--set-pcs-val=PREFIX,KEY,VALUE
Sets an integer value at the specified prefix and key in
the PCS database. The value may be specified in hex by
prefixing it with 0x or in octal by prefixing it with 0,
otherwise the value is assumed to be in decimal.
--set-pcs-str=PREFIX,KEY,STRING
Sets a string value at the specified prefix and key in
the PCS database.
--set-pcs-raw=PREFIX,KEY,HEXSTRING
Sets a raw binary value at the specified prefix and key in
the PCS database. The value is specified as a series of
hex bytes with no 0x or spaces.
(e.g. --set-pcs-raw="TestSection,TestData,E84C0E" sets 3 bytes)
--del-pcs-key=PREFIX,KEY
Deletes the specified prefix and key from the PCS database.

Multiple display adapter options:
Following options are used for querying and setting up multiple
display adapters that are installed for multihead or Crossfire
configurations.
--lsa, --list-adapters
Lists all detected and supported display adapters.
The default adapter (used when --adapter is not specified)
will be indicated with a "*" next to it.
--adapter=ADAPTERLIST
Selects which adapters returned by --list-adapters should
be affected by other aticonfig options. ADAPTERLIST contains
either a comma-seperated sequence of the index numbers of the
adapters to be affected or else contains the keyword "all" to
select all the adapters. If --adapter is missing, only the
default adapter will be affected.
--lscc, --list-crossfire-candidates
Queries the driver to determine the pool of available devices
that can
can be chained together for CrossFire.
--lsch, --list-crossfire-chains
Lists the CrossFire chains that are currently defined along with
their
enabled state
--cfa, --add-crossfire-chain
Defines a new CrossFire chain. --adapter should contain the
adapter
chain definition, with the master adapter being the first entry
and
the slave adapters being the subsequent entries in order of
priority.
--cfd, --delete-crossfire-chain
Delete and existing defined CrossFire chain. --adapter should
list the
master adapters of the chains to be deleted. --adapter=all will
delete
all chain definitions.
--cf, --crossfire={on|off}
Enables/disables CrossFire support on the currently defined
CrossFire
chains. --adapter should list the master adapters to be enabled
or
disabled.
--cfl, --crossfire-logo={on|off}
Enables/disables the appearance of the CrossFire Logo when
rendering
in CrossFire mode

ATI Overdrive (TM) options:
The following options are used to get and set current and peak, core
and memory clock information as well as read the current temperature of
adapters. By using the "--adapter=" argument the ATI Overdrive (TM)
options can be targeted to a particular adapter in a multi-adapter
scenario.
If no adapter is explicitly targeted the commands will be run on the
Default
adapter as indicated by the "--list-adapters" command
--od-enable
Unlocks the ability to change core or memory clock values by
acknowledging that you have read and understood the ATI Overdrive
(TM)
disclaimer and accept responsibility for and recognize the
potential
dangers posed to your hardware by changing the default core or
memory
clocks
--od-disable
Disables ATI Overdrive(TM) set related aticonfig options.
Previously
commited core and memory clock values will remain, but will not
be set
on X Server restart.
--odgc, --od-getclocks
Lists various information regarding current core and memory clock
settings.
Including: current and peak clocks
the theoretical range clocks can be set to
the current load on the GPU
--odsc, --od-setclocks={NewCoreClock|0,NewMemoryClock|0}
Sets the core and memory clock to the values specified in MHz
The new clock values must be within the theoretical ranges
provided
by --od-getclocks. If a 0 is passed as either the NewCoreClock or
NewMemoryClock it will retain the previous value and not be
changed.
There is no guarantee that the attempted clock values will succeed
even if they lay inside the theoretical range. These newly set
clock values will revert to the default values if they are not
committed using the "--od-commitclocks" command before X is
restarted
--odrd, --od-restoredefaultclocks
Sets the core and memory clock to the default values.
Warning X needs to be restarted before these clock changes will
take
effect
--odcc, --od-commitclocks
Once the stability of a new set of custom clocks has been proven
this
command will ensure that the Adapter will attempt to run at these
new
values whenever X is restarted
--odgt, --od-gettemperature
Returns the temperature reported by any thermal sensors available
on
the adapter.

ACPI Options:
--acpi-services=on|off
Enable/disable ACPI services. In the case of BIOS or kernel ACPI
issues,
ACPI services in the driver can be disabled through this option.
The ACPI services are enabled by default.
--acpi-display-switch=on|off
Enable/disable display switching with ACPI methods on mobile
platforms.
This option is enabled by default.

Genlock/Framelock options:
The following options are used to control operation with GLSYNC module
in the system. By using the "--adapter=" argument --glsync-getconfig,
--glsync-setconfig, --glsync-getgenlock, --glsync-setgenlock options
can be targeted to a particular adapter in a multi-adapter scenario.
If no adapter is explicitly targeted the commands will be run on the
Default
adapter as indicated by the "--list-adapters" command
--glsync-getport={RJ45_1 | RJ45_2 | BNC}
Get configuration state for specified GLSync port.
Including: Number of LEDs
Scanned frequency
Signal Source for RJ45 port if it is configured as
output
Port state (Input or Output) for RJ45 port
Signal type for BNC port
--glsync-setport=port_type,cntl,sig_src
Set configuration for specified GLSync port
Parameters: port_type - RJ45_1 or RJ45_2
only RJ45 ports can be configured
cntl - 0 if port is configured as input or
1 if port is configured as output
sig_src - signal source for GL Sync port
if 0-3 - GPU port index
if RJ45_1, RJ45_2 or BNC - another GL Sync
port
if -1 - signal source is undefined
--glsync-getconfig
Get timing configuration for particular GL Sync connector
Including: Sync Delay in ms
Signal Source
Sample Rate
Sync field
Trigger Edge
Scan Rate multiplier
GPU port index this adapter connected to
--glsync-setconfig=delay,fr_cntl,sig_src,smpl_rate,fld,edge,coef
Set timing configuration for GL Sync connector
Parameters: delay - Sync Delay in ms
fr_cntl - Enable/Disable framlock control
0 Disable Framelock
1 Enable Framelock
sig_src - Signal Source for this adapter.
if 0-3 - GPU port index.
It can not be GPU port index of this
adapter
if RJ45_1, RJ45_2 or BNC - GL Sync port
if -1 - signal source is undefined
smpl_rate - Sample Rate for sampled sync signal.
0 for no sampling
fld - Sync field for interlaced sync signal.
0 if sync field is undefined
1 if synced to both field
2 if synced to field 1
edge - it is defined which signal edge
should trigger syncronization
0 if edge is undefined
1 if it is triggered by raising edge
2 if it is triggered by falling edge
3 if it is triggered by both edges
coef - Scan Rate multiplier applied to sync signal
0 if coef is undefined
1 if coef is 5
2 if coef is 4
3 if coef is 3
4 if coef is 2.5
5 if coef is 2
6 if coef is 1.33
7 if coef is 1.25
8 if coef is 1.
9 if coef is 0.8
10 if coef is 0.67
11 if coef is 0,5
12 if coef is 0.4
13 if coef is 0.33
14 if coef is 0.25
15 if coef is 0.2
Note: Some parameters may not be valid for manual configuration.
Please use --glsync-getconfig command to verify.
--glsync-getgenlock=disp_type
Get genlock mode for particular display
disp_type - Display Type. When RandR 1.2 and above is enabled
can be query by using xrandr -q command.
If RandR 1.2 is not enabled
aticonfig --query-monitor command should be used
to query this parameter
--glsync-setgenlock=disp_type,mode,timing_server
Set genlock mode for particular display
Parameters: disp_type - Display Type.
When RandR 1.2 and above is enabled
can be query by using xrandr -q command.
If RandR 1.2 is not enabled
aticonfig --query-monitor command
should be used to query this parameter.
mode - Enable/Disable Genlock
0 Disable Genlock
1 Enable Genlock
timing_server - Enable/Disable timing server
0 to configure display as free run
1 to configure display as a timing server
--glsync-restart
Reinitialized all genlock settings after power down system

X Server Options:
--xinerama={on|off}
Enable/disable Xinerama (MultiView) in the X Server configuration
file.
MultiView allows for the merging of independent desktop heads
into a
unified workspace allowing windows to freely cross X Screen
boundaries.

Miscellaneous Options:
-v, --verbose
Show what aticonfig is doing.
-q, --quiet
Disable all information output except for errors.
--effective={now,startup}
Choose when the requested changes should take effect.
now: Immediately. This change will affect the running X
session if applicable. Only 'set-powerstate' and
'overlay-on' are applicable for now.
startup: On future X server startups. This change will
modify the
X server configuration file if applicable.
The default is 'now,startup', i.e., do both as applicable.
--nobackup
Do not make an automatic backup of the configuration file.
-i, --input=FILE
Select a FILE to input as the configuration file. Set FILE to '-'
to
pipe from standard input. Without this option, aticonfig will
search
/etc/X11 for the default configuration file.
-o, --output=FILE
Select a FILE to output the new configuration file to. Set FILE
to '-'
to print to standard output. Without this option, aticonfig will
replace the input file with the newly generated file.
-h, --help
Display this help screen.
-f, --force
Only valid with 'initial' option. Force aticonfig to generate
default
Monitor, Device, and Screen sections even if the original
configuration
file has invalid settings in these sections.

Composite options:
--xv-pixmap-buffer-type=gartcacheable
Allocate pixmap buffer from GART cacheable heap.
--xv-pixmap-buffer-type=lfb
Allocate pixmap buffer from local framebuffer.
--xv-pixmap-buffer-type=gartuswc
Allocate pixmap buffer from GART USWC heap.

Examples:
1. Setting up fglrx for the first time.
Single head : aticonfig --initial --input=/etc/X11/xorg.conf
Dual head : aticonfig --initial=dual-head --screen-
layout=above
This command will generate a dual head
configuration
file with the second screen located above the
first
screen.
2. Setting up big desktop to horizontal and set overlay on secondary
display.
aticonfig --dtop=horizontal --overlay-on=1
3. Setting up modes for primary display.
aticonfig --
resolution=0,1600x1200,1280x1024,1024x768
4. Force primary CRT on and TV-out off.
aticonfig --force-monitor=crt1,notv
5. Change tv geometry
aticonfig --tv-geometry=85x90+10-10
This will set tv to 85% width (where 100% ==
overscan) 90% height and shift 10 pixels right of centre
and 10 pixels down of centre.
6. Multiple display adapters.
List adapters : aticonfig --list-adapters
Init 0 and 2 : aticonfig --adapter=0,2 --initial
Init all : aticonfig --adapter=all --initial
MultiView : aticonfig --xinerama=on
7. ATI Overdrive (TM).
List adapters : aticonfig --list-adapters
Get Clocks of 0 : aticonfig --adapter=0 --od-getclocks
Set new Clocks for 0 : aticonfig --adapter=0 --od-
setclocks=770,1126
Test out 3D : atiode -P60 -H localhost:0; echo $?
Check Temperature of 0 : aticonfig --adapter=0 --od-gettemperature
Commit changes for 0 : aticonfig --adapter=0 --od-commitclocks

***note***
atiode is a stress application you start with a required
parameter -P which specifies the test duration and the
optional
-H parameter to target a specific display to use. For
example
atiode -P 600 -H localhost:0 would test display 0 for 10
minutes
the return code from the application is the test result
0: Test successfully completed.
1: Invalid command-line parameters.
2: Test failed because of rendering errors.
3: Target adapter not found.
4: Test aborted due to unknown reason

8. Framelock/Genlock with GL Synck module
Set GL Sync connector parameters for p;articular adapter:
aticonfig --glsync-setconfig=0,0,2,0.0,3,8 --
adapter=1
Enable Genlock for particular display:
aticonfig --glsync-setgenlock=lvds,1,0 --adapter=1
Enable Timing Master:
aticonfig --glsync-setgenlock=dfp3,0,1 --adapter=1
Verify if the frequiency is locked for particular display:
aticonfig --glsync-getgenlock=crt1 --adapter=1
Set GL Sync output port RJ45_1:
aticonfig --glsync-setport=RJ45_1,1,BNC
Reinitialize all genlock settings for all displays and adapters:
aticonfig --glsync-restart

Please report bugs to http://support.ati.com

Is this enough options or do you need more?

--
GNU/Linux runs on IBM mainframes and on the world's fastest supercomputers
Windows supercomputers on the other hand are called botnets. <grin>

Dan C...

Posted: Thu Oct 22, 2009 9:47 pm

Guest

On Thu, 22 Oct 2009 17:03:33 -0400, Baho Utot wrote:

Quote:

Is that a question?

<snip useless manpage crap>

Quote:

Is this enough options or do you need more?

Whatever. As I said already, ATI cards/drivers suck ass, and lag far
behind Nvidia. Use them if you like. For some folks, second-rate isn't
good enough.

--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as he garotted another passing Liberal.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/

Baho Utot...

Posted: Fri Oct 23, 2009 2:59 am

Guest

On Fri, 23 Oct 2009 03:47:15 +0000, Dan C wrote:

Quote:

On Thu, 22 Oct 2009 17:03:33 -0400, Baho Utot wrote:

I'd suggest staying with the Nvidia cards and their proprietary
driver. Why sacrifice performance and stability (both rock-solid) in
some idealistic attempt at staying "open"? Screw that. ATI drivers
suck ass, and always have.

Haven't heard of radeonhd have you

Is that a question?

Can't you tell

Quote:

snip useless manpage crap

Wasn't a manpage

Quote:

Is this enough options or do you need more?

Whatever. As I said already, ATI cards/drivers suck ass, and lag far
behind Nvidia. Use them if you like. For some folks, second-rate isn't
good enough.

http://www.xbitlabs.com/news/video/
display/20090929095918_Nvidia_Reportedly_Limits_PhysX_Support_to_Nvidia_Only_Graphics_Sub_Systems.html

http://www.zdnetasia.com/news/software/0,39044164,62039536,00.htm

http://www.h-online.com/open/news/item/Nvidia-s-Linux-driver-cripples-
Fujitsu-Celsius-H270-notebooks-741259.html

Nvidia Linux driver: Closed source makes open source unsafe
http://www.linux.org/news/2006/10/18/0008.html

In the realm of good news, ATI has agreed to release open source drivers
for Linux, just like Intel did years ago. Yay! In the realm of bad news,
Nvidia still has not. We want to put pressure on Nvidia to rise to ATI's
and Intel's challenge, do we not?
http://ubuntulinuxtipstricks.blogspot.com/2008/03/ati-nvidia-resume-good-
news-bad-news.html

ATI is not second-rate.

--
GNU/Linux runs on IBM mainframes and on the world's fastest supercomputers
Windows supercomputers on the other hand are called botnets. <grin>

Dan C...

Posted: Fri Oct 23, 2009 7:06 am

Guest

On Fri, 23 Oct 2009 04:59:02 -0400, Baho Utot wrote:

Quote:

Nvidia Linux driver: Closed source makes open source unsafe

Bullshit.

Quote:

In the realm of good news, ATI has agreed to release open source drivers
for Linux, just like Intel did years ago. Yay! In the realm of bad news,
Nvidia still has not. We want to put pressure on Nvidia to rise to ATI's
and Intel's challenge, do we not?

No. We want drivers and hardware that *work*. Like Nvidia does. ATI
and Intel (LOL!) are not nearly as good.

Quote:

ATI is not second-rate.

Yes, they are. They always have been, and there's no reason to think
that will change because of the "openness" of their crappy drivers.

--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as he garotted another passing Liberal.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/

Page 1 of 2 Goto page 1, 2 Next

All times are GMT - 5 Hours The time now is Sun Nov 29, 2009 11:09 am Linux Forum Index