• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

TPU's F@H Team

@NastyHabits What clocks on the 750ti? I have an Asus AM1I-A with the open ended PCI-e x4 slot. Since the AM1 boards are limited to to x4 in the PCI lanes, I wonder if this would affect a high end card like a GTX970? If it would work, were looking at alot of PPD from approx 170 watts.
 
Last edited:
@NastyHabits What clocks on the 750ti? I have an Asus AM1I-A with the open ended PCI-e x4 slot. Since the AM1 boards are limited to to x4 in the PCI lanes, I wonder if this would affect a high end card like a GTX970? If it would work, were looking at alot of PPD from approx 170 watts.
It would suffer from the same problem he had now. He would be getting core 18wu's getting, higher ppd than a 750ti, but not the amazing ppd a 970 can provide.
 
@NastyHabits What clocks on the 750ti? I have an Asus AM1I-A with the open ended PCI-e x4 slot. Since the AM1 boards are limited to to x4 in the PCI lanes, I wonder if this would affect a high end card like a GTX970? If it would work, were looking at alot of PPD from approx 170 watts.

The clocks on my particular ASUS 750 Ti are limited to 1200 GPU 1505 Memory.

According to Wizzard "GPU overclocking works well, but is constrained by NVIDIA's power limiter. Once you exceed a certain clock frequency, the card will drop down to base clock to avoid drawing too much power."

In addition, the Nvidia driver assumes the AM1 and Kabini APU are too weak for gaming, and therefore will not output anything to the HDMI port. In other words, I can't display streaming video such as Amazon prime to my TV.

I put together this PC basically because I got the case, MB and CPU from Newegg for $99. My only other expenses were a memory stick and the 750 Ti. (Got that from a guy on TPU). In retrospect, I would have been better off with an Intel based Mini-ITX board and a low power i3. The two biggest draw backs to the AM1 were the PCIx4 slot and no USB 3.0 connections on the board.

At any rate, I'm getting decent PPD (55K) at less than 85 watts on core 0x17's, and I can leave it on 24/7/365 without going up a level on my electric bill.
 
The clocks on my particular ASUS 750 Ti are limited to 1200 GPU 1505 Memory.

According to Wizzard "GPU overclocking works well, but is constrained by NVIDIA's power limiter. Once you exceed a certain clock frequency, the card will drop down to base clock to avoid drawing too much power."

In addition, the Nvidia driver assumes the AM1 and Kabini APU are too weak for gaming, and therefore will not output anything to the HDMI port. In other words, I can't display streaming video such as Amazon prime to my TV.

I put together this PC basically because I got the case, MB and CPU from Newegg for $99. My only other expenses were a memory stick and the 750 Ti. (Got that from a guy on TPU). In retrospect, I would have been better off with an Intel based Mini-ITX board and a low power i3. The two biggest draw backs to the AM1 were the PCIx4 slot and no USB 3.0 connections on the board.

At any rate, I'm getting decent PPD (55K) at less than 85 watts on core 0x17's, and I can leave it on 24/7/365 without going up a level on my electric bill.
I have tested, and with my 750ti I use about 50w for each card while folding. So that would mean you have about 35w usage on everything else which is pretty nice. This falls in line with w1zzards average power usage numbers. I also am able to overclock mine to 1375 core folding stable and get closer to 75k ppd. For me I am not running into the power limiter. Mine also runs on a intel celeron.
 
It would suffer from the same problem he had now. He would be getting core 18wu's getting, higher ppd than a 750ti, but not the amazing ppd a 970 can provide.
I would run it in Linux, so Core_17 all the way. I'm going to move one of the GTX970's over to the AM1 rig and see what production I get with Kabini OC'd to 2.6Ghz.
 
I would run it in Linux. So Core_17 all the way.
I just got both my 750ti's on linux, loosely following your guide. It took me awhile, but I didn't realize I had to install all 3 packages... ha ha ha. Once I did that I didn't have any problems.

Did you ever figure out a way to overclock multiple gpu's?

Too bad I run my 970 on windows for gaming purposes, or else I might consider linux.
 
Turned the 680 on earlier today since it's dummy cold. Loaded at 32C, that'll do water cooling, that'll do.
 
Did you ever figure out a way to overclock multiple gpu's?
Yes, you must connect a physical monitor to both GPU's to for X-Server to allow fan and overclocking for both GPU's. Several re-starts are required.
 
Yes, you must connect a physical monitor to both GPU's to for X-Server to allow fan and overclocking for both GPU's. Several re-starts are required.
I guess I will just have to rely on having consistant core 17 wu's for ppd than overclocking. They do give me far higher net ppd than overclocking and core 18 or core 15 wu's.
 
Yes, you must connect a physical monitor to both GPU's to for X-Server to allow fan and overclocking for both GPU's. Several re-starts are required.

Will 2 feeds to a single monitor work for that? My Dell ones can switch from vga to DVI with the controls on the front panel
 
Will 2 feeds to a single monitor work for that? My Dell ones can switch from vga to DVI with the controls on the front panel
Probably. I do not even have the second monitor power cable plugged in. You could prob trick x-server into seeing a "second" monitor.
 
What about the dummy plug? Once upon a time people were sticking resistors in DVI/VGA adapters to trick graphics cards into thinking a monitor was there.
 
Probably. I do not even have the second monitor power cable plugged in. You could prob trick x-server into seeing a "second" monitor.
Do you have to have the 2nd monitor plugged in to keep the 2nd card overclocked, or once overclocked will it stay at the desired clocks. I could lug a monitor over to my folding rig, I just don't want to leave it there.
 
@Norton @BUCK NASTY

Is this going correct and now part of the TPU F@H Team ?

Capture154.jpg


Capture155.jpg
 
What about the dummy plug? Once upon a time people were sticking resistors in DVI/VGA adapters to trick graphics cards into thinking a monitor was there.
Tried it with the dummy plug. Did not work. X-server needs to see the make/model of the monitor for it to work.

Do you have to have the 2nd monitor plugged in to keep the 2nd card overclocked, or once overclocked will it stay at the desired clocks. I could lug a monitor over to my folding rig, I just don't want to leave it there.
Yes, 2nd monitor is constantly attached to the card with a DVI cable, but not powered. I will test out a KVM when I get my other 970 cards in the next week.
 
Last edited:
Supposedly this is an example of a multi gpu 750 ti overclocked config. From cryptocoin mining, got a love them miners. They were very incentivised to figure this all out. I have not tried it or looked at it in depth, I am too busy gaming.

Code:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 337.19  (buildmeister@swio-display-x64-rhel04-03)  T$


Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    Screen      1  "Screen1" 0 0
    Screen      2  "Screen2" 0 0
    Screen      3  "Screen3" 0 0
    Screen      4  "Screen4" 0 0
    Screen      5  "Screen5" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor1"
    HorizSync      30-94
    VertRefresh    48-85
EndSection

Section "Monitor"
    Identifier     "Monitor2"
    HorizSync      30-94
    VertRefresh    48-85
EndSection

Section "Monitor"
    Identifier     "Monitor3"
    HorizSync      30-94
    VertRefresh    48-85
EndSection

Section "Monitor"
    Identifier     "Monitor4"
    HorizSync      30-94
    VertRefresh    48-85
EndSection

Section "Monitor"
    Identifier     "Monitor5"
    HorizSync      30-94
    VertRefresh    48-85
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:1:0:0"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:2:0:0"
EndSection

Section "Device"
    Identifier     "Device2"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:3:0:0"
EndSection

Section "Device"
    Identifier     "Device3"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:4:0:0"
EndSection

Section "Device"
    Identifier     "Device4"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:5:0:0"
EndSection

Section "Device"
    Identifier     "Device5"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:6:0:0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Coolbits" "12"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "Coolbits" "12"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen2"
    Device         "Device2"
    Monitor        "Monitor2"
    DefaultDepth    24
    Option         "Coolbits" "12"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen3"
    Device         "Device3"
    Monitor        "Monitor3"
    DefaultDepth    24
    Option         "Coolbits" "12"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen4"
    Device         "Device4"
    Monitor        "Monitor4"
    DefaultDepth    24
    Option         "Coolbits" "12"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen5"
    Device         "Device5"
    Monitor        "Monitor5"
    DefaultDepth    24
    Option         "Coolbits" "12"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection
 
Supposedly this is an example of a multi gpu 750 ti overclocked config. From cryptocoin mining, got a love them miners. They were very incentivised to figure this all out. I have not tried it or looked at it in depth, I am too busy gaming.

Code:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 337.19  (buildmeister@swio-display-x64-rhel04-03)  T$


Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    Screen      1  "Screen1" 0 0
    Screen      2  "Screen2" 0 0
    Screen      3  "Screen3" 0 0
    Screen      4  "Screen4" 0 0
    Screen      5  "Screen5" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor1"
    HorizSync      30-94
    VertRefresh    48-85
EndSection

Section "Monitor"
    Identifier     "Monitor2"
    HorizSync      30-94
    VertRefresh    48-85
EndSection

Section "Monitor"
    Identifier     "Monitor3"
    HorizSync      30-94
    VertRefresh    48-85
EndSection

Section "Monitor"
    Identifier     "Monitor4"
    HorizSync      30-94
    VertRefresh    48-85
EndSection

Section "Monitor"
    Identifier     "Monitor5"
    HorizSync      30-94
    VertRefresh    48-85
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:1:0:0"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:2:0:0"
EndSection

Section "Device"
    Identifier     "Device2"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:3:0:0"
EndSection

Section "Device"
    Identifier     "Device3"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:4:0:0"
EndSection

Section "Device"
    Identifier     "Device4"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:5:0:0"
EndSection

Section "Device"
    Identifier     "Device5"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:6:0:0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Coolbits" "12"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "Coolbits" "12"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen2"
    Device         "Device2"
    Monitor        "Monitor2"
    DefaultDepth    24
    Option         "Coolbits" "12"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen3"
    Device         "Device3"
    Monitor        "Monitor3"
    DefaultDepth    24
    Option         "Coolbits" "12"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen4"
    Device         "Device4"
    Monitor        "Monitor4"
    DefaultDepth    24
    Option         "Coolbits" "12"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen5"
    Device         "Device5"
    Monitor        "Monitor5"
    DefaultDepth    24
    Option         "Coolbits" "12"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection
I tried editing the X-servers config file. It did not work for me. Could not save the edited configuration. Let me know if you get anywhere with it.
 
I should of linked the source with that. Upon reviewing the source, it seems they followed this guide. I am trying it now and will provide an update if successful.

http://blog.cryptohaze.com/2011/02/nvidia-fan-speed-control-for-headless.html
As it reads, it sounds like you can configure linux to think you have multiple monitors through software. No need for KVM or dummy plugs.

I FIGURED IT OUT!!!:clap: I should now net about 200k ppd a day at the lowest, and if my 970 on windows gets a few core 17's I might even go over 400k.
 
Last edited:
Double posting, I know, but I thought it would be nicer to make a small guide on how to do multiple gpu overclocking in linux. You can take what you want from here and add this to your guide @BUCK NASTY
You are going to have to edit your xorg.conf file, manually editing in a fake monitor. Xorg.conf is a read only file so you will have to edit in the terminal as a root user.

So...
  1. Open a terminal
  2. type the command: lspci | grep VGA
  3. Note the pci device id for each card you want to overclock.
  4. type the command: sudo nano /etc/X11/xorg.conf
  5. Edit as need based on example below
  6. Press "Cnrl O" (O as in the letter) to write the edits when done.
Basically in Xorg.conf you are making up a monitor for each gpu you have. I only have 2 gpu's in this sytem so I only needed to add 1 fake monitor. Buck in his 4 card GTX 970 system will have to add 3 fake monitors. In the example below I will bold the edits I made on top of the default xorg.conf file.

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 343.36 (buildmeister@swio-display-x86-rhel47-09) Mon Dec 1 16:47:14 PST 2014


Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"

# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "HP"
ModelName "W17q"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection

Section "Monitor"
Identifier "Monitor1"
VendorName "Fake"
ModelName "Monitor"
HorizSync 30-94
VertRefresh 48-85
EndSection


Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BusID "PCI:1:0:0"
EndSection

Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BusID "PCI:2:0:0"
EndSection


Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "Coolbits" "12"
SubSection "Display"
Depth 24
EndSubSection
EndSection

Section "Screen"
Identifier "Screen1"
Device "Device1"
Monitor "Monitor1"
DefaultDepth 24
Option "Coolbits" "12"
SubSection "Display"
Depth 24
EndSubSection
EndSection



Note that in the above example anything bold is something I added to the default xorg.conf file. In Section "Device" the bus id should match the gpu you have in your system.

If you have more than 2 gpu's you can look at this other example below.

Code:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 337.19  (buildmeister@swio-display-x64-rhel04-03)  T$


Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    Screen      1  "Screen1" 0 0
    Screen      2  "Screen2" 0 0
    Screen      3  "Screen3" 0 0
    Screen      4  "Screen4" 0 0
    Screen      5  "Screen5" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor1"
    HorizSync      30-94
    VertRefresh    48-85
EndSection

Section "Monitor"
    Identifier     "Monitor2"
    HorizSync      30-94
    VertRefresh    48-85
EndSection

Section "Monitor"
    Identifier     "Monitor3"
    HorizSync      30-94
    VertRefresh    48-85
EndSection

Section "Monitor"
    Identifier     "Monitor4"
    HorizSync      30-94
    VertRefresh    48-85
EndSection

Section "Monitor"
    Identifier     "Monitor5"
    HorizSync      30-94
    VertRefresh    48-85
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:1:0:0"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:2:0:0"
EndSection

Section "Device"
    Identifier     "Device2"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:3:0:0"
EndSection

Section "Device"
    Identifier     "Device3"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:4:0:0"
EndSection

Section "Device"
    Identifier     "Device4"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:5:0:0"
EndSection

Section "Device"
    Identifier     "Device5"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:6:0:0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Coolbits" "12"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "Coolbits" "12"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen2"
    Device         "Device2"
    Monitor        "Monitor2"
    DefaultDepth    24
    Option         "Coolbits" "12"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen3"
    Device         "Device3"
    Monitor        "Monitor3"
    DefaultDepth    24
    Option         "Coolbits" "12"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen4"
    Device         "Device4"
    Monitor        "Monitor4"
    DefaultDepth    24
    Option         "Coolbits" "12"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen5"
    Device         "Device5"
    Monitor        "Monitor5"
    DefaultDepth    24
    Option         "Coolbits" "12"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection




My little guide here was a summary of this guide here.
 
Do all the cards have to be the same to run in linux on 1 system? Is it possible to mix cards, say a 780 ti and a 780, or a 680 and a 660ti?
 
Just ordered the last 2 GTX 970 Strix's that I need from Fry's.com:(. Didn't want to go that route, but had no choice. Should have them Wednesday along with the open air mining case. Hopefully I'll have this beast up and running by Friday night.

Do all the cards have to be the same to run in linux on 1 system? Is it possible to mix cards, say a 780 ti and a 780, or a 680 and a 660ti?
As long as they are all supported by the same Nvidia/Linux driver, it should not be an issue.
 
Last edited:
Thanks i wonder if the Keplers are held down by the later Linux drivers as much as windows?
 
production_day.phpsu658658

That is what I like to see! Core 17 wu's all around!

If I haven't been gaming so much it would probably be higher.
 
Capture.PNG



I think its gonna blow.... lol
 
Back
Top