New command-line tool for overclocking ATI cards (Linux) - page 4.

mjmvisser

newbie

Activity: 58

Merit: 0

Quote from: dishwara on July 27, 2011, 01:36:22 AM

Windows support?
How to run in windows? What other things required to run in windows?

You'll need to install Python, for starters. Unless you're writing your own Python tools for Windows, it's probably easier to use one of the GUI-based overclocking tools.

mjmvisser

newbie

Activity: 58

Merit: 0

Quote from: Tereska on July 26, 2011, 01:30:11 PM

mine looks like this:

...

Section "Monitor"
   Identifier "aticonfig-Monitor[0]-0"
   Option "VendorName" "ATI Proprietary Driver"
   Option "ModelName" "Generic Autodetecting Monitor"
   Option "DPMS" "true"
EndSection

...
what could be wrong?

I found X wouldn't initialize properly with those three options (VendorName, ModelName, DPMS) in the Monitor sections. I think it was trying to autodetect the monitors. Try commenting them out? Everything else looks fine.

coblee

donator

Activity: 1654

Merit: 1351

Creator of Litecoin. Cryptocurrency enthusiast.

Quote from: cicada on July 27, 2011, 03:12:09 PM

Maybe I missed while skimming the thread, but has anyone tried this on 69xx series hardware?

Curious if this gets around the 'memory clock must be >= gpu clock - 125mhz' issue..

Someone indicated in another thread they were able to use it successfully on a 6990, I'm more curious about 6950 / 6970's

I've tried this on my 6970 and no, it doesn't get around that issue. I still have to set memory clock >= gpu clock - 125.

But this tool is definitely easier to use than aticonfig.

cicada

full member

Activity: 196

Merit: 100

Maybe I missed while skimming the thread, but has anyone tried this on 69xx series hardware?

Curious if this gets around the 'memory clock must be >= gpu clock - 125mhz' issue..

Someone indicated in another thread they were able to use it successfully on a 6990, I'm more curious about 6950 / 6970's

dishwara

legendary

Activity: 1855

Merit: 1016

Quote from: mjmvisser on July 26, 2011, 01:27:23 PM

UPDATE: adl3 v0.4
sudo easy_install --upgrade adl3
Features:
- Windows support (thanks to Jakub Lekstan)

Windows support?
How to run in windows? What other things required to run in windows?

fitty

hero member

Activity: 728

Merit: 501

CryptoTalk.Org - Get Paid for every Post!

Quote from: mjmvisser on July 03, 2011, 06:12:59 PM

Hi everyone,

I'm not sure if it's a bug or mistake on my part. On Linux if you set the memory clock without a performance-level it works fine and appears to set all performance levels with the memory clock inputted. If you set the engine-clock without a performance level it crashes. When I add back the performance-level it then works (and doesn't crash). Anyway great job the tool is great. =)

gnar1ta$

donator

Activity: 798

Merit: 500

Quote from: cyrusfox on July 25, 2011, 09:47:25 PM

I love atitweak, simple and helps me custom set everything on my cards. Also lets me check what clocks actually stick. Great tool! The shortened syntax rocks(took me a sec to figure out though), saves time when I am testing out new cards or trying higher or lower clocks. Here is what I run right before I begin mining.

Quote

atitweak -m 725 -P 2 -A 0
atitweak -m 725 -P 1 -A 0
atitweak -e 850 -P 2 -A 0
atitweak -m 855 -P 2 -A 1
atitweak -m 855 -P 1 -A 1
atitweak -e 955 -P 2 -A 1
atitweak -f 83 -A 0
atitweak -f 70 -A 1

You know you can shorten this more (I'm lazy - less typing = more beer drinking)

Code:

atitweak -m 775 -e 850 -f 83 -A 0
atitweak -m 855 -e 995 -f 70 -A 1

Unless you have some need of running different settings for performance levels???

/donation sent

thanks for the work

Tereska

newbie

Activity: 17

Merit: 0

mine looks like this:

Code:

Section "ServerLayout"
   Identifier "aticonfig Layout"
   Screen 0 "aticonfig-Screen[0]-0" 0 0
   Screen "aticonfig-Screen[1]-0" RightOf "aticonfig-Screen[0]-0"
   Screen "aticonfig-Screen[2]-0" RightOf "aticonfig-Screen[1]-0"
   Screen "aticonfig-Screen[3]-0" RightOf "aticonfig-Screen[2]-0"
EndSection

Section "Module"
EndSection

Section "Monitor"
   Identifier "aticonfig-Monitor[0]-0"
   Option "VendorName" "ATI Proprietary Driver"
   Option "ModelName" "Generic Autodetecting Monitor"
   Option "DPMS" "true"
EndSection

Section "Monitor"
   Identifier "aticonfig-Monitor[1]-0"
   Option "VendorName" "ATI Proprietary Driver"
   Option "ModelName" "Generic Autodetecting Monitor"
   Option "DPMS" "true"
EndSection

Section "Monitor"
   Identifier "aticonfig-Monitor[2]-0"
   Option "VendorName" "ATI Proprietary Driver"
   Option "ModelName" "Generic Autodetecting Monitor"
   Option "DPMS" "true"

EndSection

Section "Monitor"
   Identifier "aticonfig-Monitor[3]-0"
   Option "VendorName" "ATI Proprietary Driver"
   Option "ModelName" "Generic Autodetecting Monitor"
   Option "DPMS" "true"
EndSection

Section "Device"
   Identifier "aticonfig-Device[0]-0"
   Driver "fglrx"
   BusID "PCI:11:0:0"
EndSection

Section "Device"
   Identifier "aticonfig-Device[1]-0"
   Driver "fglrx"
   BusID "PCI:10:0:0"
EndSection

Section "Device"
   Identifier "aticonfig-Device[2]-0"
   Driver "fglrx"
   BusID "PCI:5:0:0"
EndSection

Section "Device"
   Identifier "aticonfig-Device[3]-0"
   Driver "fglrx"
   BusID "PCI:4:0:0"
EndSection

Section "Screen"
   Identifier "aticonfig-Screen[0]-0"
   Device "aticonfig-Device[0]-0"
   Monitor "aticonfig-Monitor[0]-0"
   DefaultDepth 24
   SubSection "Display"
   Viewport 0 0
   Depth 24
   EndSubSection
EndSection

Section "Screen"
   Identifier "aticonfig-Screen[1]-0"
   Device "aticonfig-Device[1]-0"
   Monitor "aticonfig-Monitor[1]-0"
   DefaultDepth 24
   SubSection "Display"
   Viewport 0 0
   Depth 24
   EndSubSection
EndSection

Section "Screen"
   Identifier "aticonfig-Screen[2]-0"
   Device "aticonfig-Device[2]-0"
   Monitor "aticonfig-Monitor[2]-0"
   DefaultDepth 24
   SubSection "Display"
   Viewport 0 0
   Depth 24
   EndSubSection
EndSection

Section "Screen"
   Identifier "aticonfig-Screen[3]-0"
   Device "aticonfig-Device[3]-0"
   Monitor "aticonfig-Monitor[3]-0"
   DefaultDepth 24
   SubSection "Display"
   Viewport 0 0
   Depth 24
   EndSubSection
EndSection

------

atitweak -l

Code:

0. ATI Radeon HD 5800 Series ()
   engine clock range is 80 - 900MHz
   memory clock range is 150 - 1250MHz
   core voltage range is 0.95 - 1.195VDC
   performance level 0: engine clock 157MHz, memory clock 300MHz, core voltage 0.95VDC
   performance level 1: engine clock 600MHz, memory clock 900MHz, core voltage 1.063VDC
   performance level 2: engine clock 900MHz, memory clock 900MHz, core voltage 1.163VDC
   fan speed range: 0 - 100%, 800 - 5100 RPM
1. ATI Radeon HD 5800 Series ()
   engine clock range is 80 - 900MHz
   memory clock range is 150 - 1250MHz
   core voltage range is 0.95 - 1.195VDC
   performance level 0: engine clock 157MHz, memory clock 300MHz, core voltage 0.95VDC
   performance level 1: engine clock 600MHz, memory clock 900MHz, core voltage 1.063VDC
   performance level 2: engine clock 900MHz, memory clock 900MHz, core voltage 1.163VDC
   fan speed range: 0 - 100%, 800 - 5100 RPM
2. ATI Radeon HD 5800 Series ()
   engine clock range is 80 - 900MHz
   memory clock range is 150 - 1250MHz
   core voltage range is 0.95 - 1.195VDC
   performance level 0: engine clock 157MHz, memory clock 300MHz, core voltage 0.95VDC
   performance level 1: engine clock 600MHz, memory clock 900MHz, core voltage 1.063VDC
   performance level 2: engine clock 900MHz, memory clock 900MHz, core voltage 1.125VDC
   fan speed range: 0 - 100%, 800 - 5100 RPM

what could be wrong?

mjmvisser

newbie

Activity: 58

Merit: 0

UPDATE: adl3 v0.4

sudo easy_install --upgrade adl3

Features:

- Windows support (thanks to Jakub Lekstan)

Next version:

I haven't had a chance to mess around with ADL3's i2c API to set the voltage. If anyone wants to take a crack at that one, be my guest.

Donations are welcome: 1Kh3DsAhiu65EC7DFFHDGoGowAp5usQrCG

cheers,
-Mark

mjmvisser

newbie

Activity: 58

Merit: 0

Quote from: Tereska on July 23, 2011, 05:30:41 PM

this tool detects 3 of 4 my cards (one is missing)
...
also there is no information about DISPLAY -> empty brackets ()

I've never seen that behaviour before. atitweak is just printing information returned by the driver dso. Is it possible that your xorg.conf is incomplete? Mine looks like this:

Code:

Section "ServerLayout"
Identifier "aticonfig Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0
Screen "aticonfig-Screen[1]-0" RightOf "aticonfig-Screen[0]-0"
Screen "aticonfig-Screen[2]-0" RightOf "aticonfig-Screen[1]-0"
Screen "aticonfig-Screen[3]-0" RightOf "aticonfig-Screen[2]-0"
EndSection

Section "Module"
Load "glx"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
# Option "VendorName" "ATI Proprietary Driver"
# Option "ModelName" "Generic Autodetecting Monitor"
# Option "DPMS" "true"
HorizSync 30-70
VertRefresh 50-75
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[1]-0"
# Option "VendorName" "ATI Proprietary Driver"
# Option "ModelName" "Generic Autodetecting Monitor"
# Option "DPMS" "true"
HorizSync 30-70
VertRefresh 50-75
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[2]-0"
# Option "VendorName" "ATI Proprietary Driver"
# Option "ModelName" "Generic Autodetecting Monitor"
# Option "DPMS" "true"
HorizSync 30-70
VertRefresh 50-75
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[3]-0"
# Option "VendorName" "ATI Proprietary Driver"
# Option "ModelName" "Generic Autodetecting Monitor"
# Option "DPMS" "true"
HorizSync 30-70
VertRefresh 50-75
EndSection

Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:1:0:0"
EndSection

Section "Device"
Identifier "aticonfig-Device[1]-0"
Driver "fglrx"
BusID "PCI:2:0:0"
EndSection

Section "Device"
Identifier "aticonfig-Device[2]-0"
Driver "fglrx"
BusID "PCI:3:0:0"
EndSection

Section "Device"
Identifier "aticonfig-Device[3]-0"
Driver "fglrx"
BusID "PCI:5:0:0"
EndSection

Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "Screen"
Identifier "aticonfig-Screen[1]-0"
Device "aticonfig-Device[1]-0"
Monitor "aticonfig-Monitor[1]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "Screen"
Identifier "aticonfig-Screen[2]-0"
Device "aticonfig-Device[2]-0"
Monitor "aticonfig-Monitor[2]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "Screen"
Identifier "aticonfig-Screen[3]-0"
Device "aticonfig-Device[3]-0"
Monitor "aticonfig-Monitor[3]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

The commented out sections are to disable monitor auto-detection, since my cards are all running headless.

There should be one ServerLayout section and one Device/Screen/Monitor sections for each card. You can get the PCI addresses with lspci.

mjmvisser

newbie

Activity: 58

Merit: 0

Quote from: lodcrappo on July 26, 2011, 03:08:58 AM

very, very nice. I am converting BAMT (http://forum.bitcoin.org/index.php?topic=28967.0) to use atitweak rather than aticonfig for managing GPUs. Can I trust that the current output format will not change in future versions? Donation sent!

Thanks! The output format is pretty ad-hoc, but it should be stable for the time being. I was thinking a flag to output JSON would be useful, but I haven't had the time to implement it.

lodcrappo

hero member

Activity: 616

Merit: 506

very, very nice. I am converting BAMT (http://forum.bitcoin.org/index.php?topic=28967.0) to use atitweak rather than aticonfig for managing GPUs. Can I trust that the current output format will not change in future versions? Donation sent!

cyrusfox

newbie

Activity: 15

Merit: 0

I love atitweak, simple and helps me custom set everything on my cards. Also lets me check what clocks actually stick. Great tool! The shortened syntax rocks(took me a sec to figure out though), saves time when I am testing out new cards or trying higher or lower clocks. Here is what I run right before I begin mining.

Quote

atitweak -m 725 -P 2 -A 0
atitweak -m 725 -P 1 -A 0
atitweak -e 850 -P 2 -A 0
atitweak -m 855 -P 2 -A 1
atitweak -m 855 -P 1 -A 1
atitweak -e 955 -P 2 -A 1
atitweak -f 83 -A 0
atitweak -f 70 -A 1

krzynek1

newbie

Activity: 41

Merit: 0

Quote from: plantucha on July 19, 2011, 05:18:35 PM

Quote from: mjmvisser on July 19, 2011, 05:01:48 PM

Quote from: krzynek1 on July 19, 2011, 03:13:45 PM

i can overclock on 11.5, using amdoverdrivectrl to downclock mem outside bios limits, and gpu clock rise only to bios limits Sad

with 11.6 and 11.7 u can set whatever you want, but cpu usage bug forces me to rollback to 11.5

Bummer. What's the cpu usage bug? I haven't noticed any problems -- top reports about 5% cpu usage with 4 instances of phoenix running.

but he must using Windows
because high load is normal for win users 1 CPU core full load per 1 gpu
and because 11.7 for linux doesn't exist yet

no, im using linux

and it is well known bug with 11.6

Tereska

newbie

Activity: 17

Merit: 0

this tool detects 3 of 4 my cards (one is missing)
they are all 5830 sapphire

also there is no information about DISPLAY -> empty brackets ()
I'm using Ubuntu 10.10, loggin thru ssh from another computer

could you fix this? your tool is great!

miner1@miner1:~/bitcoin/adl3$ atitweak -s
0. ATI Radeon HD 5800 Series ()
engine clock 900MHz, memory clock 900MHz, core voltage 1.163VDC, performance level 2, utilization 99%
fan speed 100% (4013 RPM) (user-defined)
temperature 73.5 C
1. ATI Radeon HD 5800 Series ()
engine clock 900MHz, memory clock 900MHz, core voltage 1.163VDC, performance level 2, utilization 99%
fan speed 100% (4138 RPM) (user-defined)
temperature 69.5 C
2. ATI Radeon HD 5800 Series ()
engine clock 900MHz, memory clock 900MHz, core voltage 1.125VDC, performance level 2, utilization 99%
fan speed 100% (3595 RPM) (user-defined)
temperature 59.5 C
miner1@miner1:~/bitcoin/adl3$

mjmvisser

newbie

Activity: 58

Merit: 0

I'll have some time to work on it tomorrow, but since the i2c calls in the ADL api are virtually undocumented and may not actually do anything, I can't promise anything.

marcus_of_augustus

legendary

Activity: 3920

Merit: 2349

Eadem mutata resurgo

Quote from: TripHammer on July 20, 2011, 11:38:44 PM

Hows the next version coming? any luck with the i2c

Donations may speed your requests along?

TripHammer

newbie

Activity: 42

Merit: 0

Hows the next version coming? any luck with the i2c

plantucha

newbie

Activity: 56

Merit: 0

Quote from: mjmvisser on July 19, 2011, 05:01:48 PM

Quote from: krzynek1 on July 19, 2011, 03:13:45 PM

i can overclock on 11.5, using amdoverdrivectrl to downclock mem outside bios limits, and gpu clock rise only to bios limits Sad

with 11.6 and 11.7 u can set whatever you want, but cpu usage bug forces me to rollback to 11.5

Bummer. What's the cpu usage bug? I haven't noticed any problems -- top reports about 5% cpu usage with 4 instances of phoenix running.

but he must using Windows
because high load is normal for win users 1 CPU core full load per 1 gpu
and because 11.7 for linux doesn't exist yet

mjmvisser

newbie

Activity: 58

Merit: 0

Quote from: krzynek1 on July 19, 2011, 03:13:45 PM

i can overclock on 11.5, using amdoverdrivectrl to downclock mem outside bios limits, and gpu clock rise only to bios limits Sad

with 11.6 and 11.7 u can set whatever you want, but cpu usage bug forces me to rollback to 11.5

Bummer. What's the cpu usage bug? I haven't noticed any problems -- top reports about 5% cpu usage with 4 instances of phoenix running.

Topic: New command-line tool for overclocking ATI cards (Linux) - page 4. (Read 50928 times)