 Show Posts
|
|
Pages: « 1 2 3 4 [5] 6 »
|
|
thanks, this really helped my 6970s (~ 10% more Mhash/s)
|
|
|
|
|
how would one disable powertune in linux console (ssh) only?
|
|
|
|
Good job!
You could redirect your miner script output to something like /tmp/miner if you want to recall it later.
And Ctrl-A S will do horizontal split screen.
yeah, i figured out how to split the screen, but not how to view the second session in the split view... |
|
|
|
I got fed up with the upstart script/conf, so I managed another way to automatically start the miners. here's the solution, in case it helps someone else. in /etc/rc.local #!/bin/sh -e
#
# ... comments removed ...
#
# Wait 30 seconds to make sure X is started.
sleep 30
su LOGINNAME -c "/home/LOGINNAME/runminers.sh" >/dev/null 2>&1
exit 0
and in runminers /home/LOGINNAME /ati899.sh
/home/LOGINNAME /atifan80.sh
/usr/bin/screen -dmS gpu0 /home/LOGINNAME /startminerloop.sh 0
/usr/bin/screen -dmS gpu1 /home/LOGINNAME /startminerloop.sh 1
to set core clock, fan speed and then start an instance of each miner with screen. screen -r gpu0/1 to view each session. would be nice to be able to view both (or more) in screen split screen view... but I haven't figured out how to display the second session in the other window half yet. for now i'm happy that the miners finally start up automatically  |
|
|
|
for running headless follow the instructions at http://developer.amd.com/support/KnowledgeBase/Lists/KnowledgeBase/DispForm.aspx?ID=19that works just fine for me. I have another problem with the automatic miner startup though. my /etc/init/btcminer.conf file: description "Start BTC Mining"
start on runlevel [2345]
stop on runlevel [!2345]
kill timeout 30
script
LOGIN=xxx
#Wait 30 seconds to make sure X is started.
sleep 30
exec /home/tom/ati899.sh
exec /home/tom/atifan80.sh
exec /usr/bin/screen -dmS gpu0 su -c '/home/tom/startminerloop.sh 0' ${LOGIN}
exec /usr/bin/screen -dmS gpu1 su -c '/home/tom/startminerloop.sh 1' ${LOGIN}
end script
when I run the 4 commands after exec manually in ssh they work just fine, but somehow not from the startup script. i guess there are some peculiarities to ubuntu upstart that I'm not familiar with |
|
|
|
After running AMDOverDriveCtrl (you can do this from ssh - export DISPLAY=0:0 ; AMDOverDriveCtrl &) and not touching it in the GUI, my memory floor becomes 150.
Trying to use aticonfig --odsc 1005,225 works.
thanks for your patience, but it's still not working for me... I run it from ssh just like you showed, and it outputs the following: INF: Adapter index 0 choosen.
INF: Nr. of Performance Levels: 3
INF: Perf Level 0: GPU 250MHz Memory 150MHz Voltage 0.9V
INF: Perf Level 1: GPU 500MHz Memory 1375MHz Voltage 1V
INF: Perf Level 2: GPU 899MHz Memory 1375MHz Voltage 1.175V
ACT: Set fan speed to default
INF: Nr. of Displays to check 6
WRN: color temperature setting not supported.
resets fan speed to default, which I then change back to my fixed setting, but there is no change in the allowed clock speeds for me at all, whether it's running or not. which brings me back to one of my earlier questions: do I need to configure something (profiles?) in the gui first for it to work? never had a screen attached to the box after the initial ubuntu setup, everything done in ssh, so i've not run AMDOverDriveCtrl or any other utility in the gui. |
|
|
|
@dudel42 - Once AMDOverDriveCtrl is running, you're free to use aticonfig to adjust clocks. If you decide to use AMDOverDriveCtrl, make sure you hit the "set" button. When the miner starts cranking away, it should automatically switch to whatever you've set the "High" profile to.
I guess I'm not quite getting something here Do I have to run AMDOverDriveCtrl in the GUI and configure in the GUI before I can use it? I can get access to the gui, but I'm basically ssh only, and when calling it there it just resets fan speed to default and nothing else... |
|
|
|
For the people asking for an AMDOverDriveCtrl howto - if you look at the sourceforge project, I believe they have prebuilt .deb packages. No reason to rebuild it unless you're trying to set it up on Fedora or some other distro.
found the deb, thanks that worked just fine. now I just need to find some info on how to use it from the command line... calling it with --help shows me the adapter indexes to use, but not much more, and the pdf documentation only shows the gui. what commands would I use on a 6970 to raise the limit (I guess it throttles, because when I set the clock higher with aticonfig it actually slows down)? |
|
|
|
go to the terminal (once AMDOverdriveCtrl is installed) and type
AMDOverdriveCtrl -i0 <- for adapter 0
AMDOverdriveCtrl -ix <- for adapter x
AMDOverdriveCtrl is case-sensitive. You can get the index from the terminal output of any of them, use the index of those that are marked 'active'
Is there a how to install AMDOverdriveCtrl? I tried building from source, but it wouldn't compile? binaries somewhere or docs on how to build yourself? thanks. |
|
|
|
|
I got two asus 6970 running in ubuntu 11.04 x64.
phoenix and hashkill both work fine at stock clock (880).
however, as soon as I go above 895 the hashrate goes up for a fraction of a second and then drops about 50%, which is due to power throttling I'm guessing. Temperatures are fine, ~75C with fans at 70%.
any idea what commands can be used to raise the power limit and increase clocks/hashrate of the 6970 in linux?
thanks.
|
|
|
|
you could get it narrower if you use that timeago plugin, just edit the text to make it shorter Thanks, it's much better.  would you share your version pls? |
|
|
|
Here is a data point for you. Not sure if it is useful.
I have been using poclbm (up-to-date from git). I decided to try hashkill for 24 hours to compare. Here is what I found.
* The hash rate shown on screen was in fact higher with hashkill vs poclbm. Close to 8% higher.
* % stale was not significantly better or worse (my pool supposes LP). It was good with both (about 0.5%).
* However, the submitted share rate was significantly lower. I understand that rate at which shares are found is driven somewhat by luck, but I feel like 24 hours of share data is long enough that a comparison is fair. I collected data from two different machines running ubuntu:
Over two 24 hour periods:
Machine 1, 6850. poclbm: 3974 shares, 195MH/s displayed. hashkill: 3630 shares 201MH/s displayed.
Machine 2, 2x6970. poclbm: 13256 shares, 670 MH/s displayed. hashkill: 12270 shares, 710 MH/s displayed.
I can't explain this data. But the reality is that I earned less on my PPS pool with hashkill.
I've noticed the exact same behavior, just haven't had time to conduct long time tests yet. hashkill had more hashes/s displayed, but just watching the pool statistics online it always had less hashrate registered by the pool than phoenix. that's why I switched back to phoenix for the time being, even though I really like hashkill (and expecially the fact that one process supports multiple gpus). |
|
|
|
|
I recently set up a triple 5850 system with a i7, 4gb ram, asus p55 board (I know it's a waste, but just had that around), and at full mining power I measure a total power consumption of ~560W.
I also bought an 850W PSU, just to be on the safe side, but from the figures (and with a more efficient mabo/cpu), I'd guess a 650-700 one would also suffice.
|
|
|
|
|
hmm, running guiminer on a another (windows) machine results in less then 1% stales on slush.
so hashkill could be more efficient when running on pools with lp support (more of my hashing power actually registering with the pool)?
|
|
|
|
Still having some problems with stale numbers here: [proc: 1096] [subm: 1000] [stale: 63] [eff: 91%] maybe this field could be separated, so we know whether it's actually a hw calculation error or a real stale share with the pool? the number also varies over time for me, no stales for a long time, then several in a short amount of time, then stable again. But I have no idea if this is my hw's fault or not. |
|
|
|
great info, thx, will change that on the next reboot. my problem right now lies with the following: [proc: 1464] [subm: 553] [stale: 499] [eff: 37%] this doesn't look all that good... edit: i had it started with -D -G4 for experimenting with different parameters, guess that was causing it.. with -G2 things look much better. |
|
|
|
how can one run hashkill without being logged on the desktop?
I want to move the system somewhere without a monitor attached, and I can't start hashkill in the ssh session when I'm not also logged in on the console...
You need to have X Windows started, and be logged in (in the case of say GDM). Then you can export your DISPLAY settings and start the app as that user. Hope that helps. yeah, that's what I'm doing now.. setup ubuntu to autologin on startup. just thought there was a way of using it without being logged in on the console, like with aticonfig. |
|
|
|
|
how can one run hashkill without being logged on the desktop?
I want to move the system somewhere without a monitor attached, and I can't start hashkill in the ssh session when I'm not also logged in on the console...
|
|
|
|
Run sudo aticonfig --initial --adapter=all and reboot. Will solve the problem if you didn't do that already  great, thx! I already did that before, but from within ssh... Now when I did it from the console it worked! still trying to figure out the right combination.. it seems certain things can only be done from the console, or only work in ssh when also logged in on the console.. confusing |
|
|
|
|
