Actually went from 0.3 to 0.3.2.1 so never tried it...
Definitely seems to not be detecting correctly - I went back to the 0.3 I made a backup of and it runs fine, yet still with the "ATI Overdrive is not loaded" error line. That error started showing up after I upgraded the ATI drivers to 11.6 yesterday and I haven't been able to get rid of it. (ran the -od -enable commands, etc. maybe there is more I need to do)
Anyways figured with the new version today with hashrate monitoring this wouldn't matter, but having the issue as I described above. Thanks
OD not enabled issue is when aticonfig --adapter=all --odgc doesn't work, so it can't work out your GPU load. When you fire up 0.3.2.1 does it say 'Hashrate-based pool monitoring is enabled', or not? If so, can you give me the contents of your common.defaults.lib and common.lib (blank out passwords if you use them)? |
|
|
|
Was working great for me until 0.3.2.1 update today.
It's not detecting my hashrate and killing and restarting the miners over and over again. I can verify in the miner windows that they are working correctly until killed by the script. Any help would be greatly appreciated. I have really enjoyed using this.
Log:
[28-Jun-2011 15:23.42] Checking for updated versions...
[28-Jun-2011 15:23.42] You are running the latest version of Autominer already.
[28-Jun-2011 15:23.42] GPU-load pool monitoring for card0 could not be enabled. ATI Overdrive is not loaded.
[28-Jun-2011 15:23.42] GPU-load pool monitoring for card1 could not be enabled. ATI Overdrive is not loaded.
[28-Jun-2011 15:23.42] Hashrate-based pool monitoring for card0 enabled.
[28-Jun-2011 15:23.42] Hashrate-based pool monitoring for card1 enabled.
[28-Jun-2011 15:23.42] Firing up the miner on card card0 using pool 1!
[28-Jun-2011 15:23.42] Connecting to XXX@uswest.btcguild.com:8332...
[28-Jun-2011 15:23.42] Firing up the miner on card card1 using pool 1!
[28-Jun-2011 15:23.42] Connecting to XXX@uswest.btcguild.com:8332...
[28-Jun-2011 15:23.42] Rechecking status...
[28-Jun-2011 15:24.03] card0 is not hashing, waiting 15 seconds and deciding whether to change pools.
[28-Jun-2011 15:24.18] The hash rate after 15 seconds is
[28-Jun-2011 15:24.18] Still not hashing, pool or net has dropped...
[28-Jun-2011 15:24.18] Killing PID: 5153
[28-Jun-2011 15:24.18] Trying to kill 5153: 0 (should be 0)
[28-Jun-2011 15:24.18] card1 is not hashing, waiting 15 seconds and deciding whether to change pools.
[28-Jun-2011 15:24.33] The hash rate after 15 seconds is
[28-Jun-2011 15:24.33] Still not hashing, pool or net has dropped...
[28-Jun-2011 15:24.33] Killing PID: 5164
[28-Jun-2011 15:24.33] Trying to kill 5164: 0 (should be 0)
[28-Jun-2011 15:24.38] Card card0 is not currently mining.
[28-Jun-2011 15:24.38] Card card1 is not currently mining.
[28-Jun-2011 15:24.38] Rechecking status...
Was 0.3.2 monitoring your hashes correctly? It could be that for some reason it thinks hashrate monitoring is working, but it's not. |
|
|
|
Welcome to the Bitcoin Lottery!
... the last character of the last transaction hash.
So how is it the people with 10-16 would win? Am I missing something because those are 2 characters... 10 would be 0, 11 = a, 12 = b, 13 = c, 14 = d, 15 = e, 16 = f I assume. |
|
|
|
|
The house lost its' first bet today as the Cubs were beaten by the Giants.
|
|
|
|
|
0.3.2.1 is up, I found a pretty major bug for people with GPU Based & XML-RPC based monitoring enabled (tl;dr: pool switching didn't work).
Get this update to fix it.
|
|
|
|
|
I have implemented this in Autominer 0.3.2, see sig.
|
|
|
|
thanks! tried them, and with 128, i get 194.7 as my highest result what does this do exactly? edit: found another setting: -v -w128 -f0 gives me 198 max keeps getting better and better  two days ago i thought all i would get was 140Mhash/s edit2: *dances* using the phoenix miner now, and i broke the 200Mhash/s barrier, doing 208.2Mhash/s now wich is pretty damn good imo using: VECTORS BFI_INT FASTLOOP=false AGGRESSION=12 -k phatk WORKSIZE=128 thanks for pushing me in this direction, 40~50Mhash/s for free thanks to you I get just over that on my 5770 at 950MHz/333MHz on Phoenix with very similar options. |
|
|
|
|
You should probably correct the title of your thread as Linux is quite clearly seeing both GPUs.
Your issue is more like 'OpenCL only seeing one GPU whilst using Multi-Desktop'. Whilst I don't know the fix, using the correct title will probably attract the attention of the people who will know and/or be able to test solutions for you.
|
|
|
|
|
What settings are you using and what miner?
|
|
|
|
Reikoku I have ~100bil in ISK/PLEX/SCaps/Chars to get rid of. Would you be interested in buying the whole lot? Hit me up on PM  I would have been if I could get Eve working.  |
|
|
|
1.) Will I be able to find drivers for the 6790 in Ubuntu, and how difficult will it be to find software to get them online and mining? (My concern is that setting up the cards/miner will be a repeat of my effort to get my old D-Link wireless card working with Ubuntu ... i.e. 12 hours of frustration ending in defeat) The drivers are really easy, Ubuntu is very user-friendly and it'll ask you when you boot into it whether you want to install proprietary drivers. If it doesn't, it's a quick search through their software repo. I've only used Arch (another Linux distribution) so I can't comment on how easy AMD APP SDK is to get, but that's the main other thing you need. 2.) Is it difficult to get both cards mining simultaneously, or is that a standard feature in most mining software packages? Some (diablominer et al.) run all your cards on one instance of the miner. Others (phoenix) require you to launch an instance for each card. I've written some software (Autominer, in my sig) which you can configure once and it'll fire up all of your miners in a nice user-friendly window whenever you run it. 3.) Does constant mining wear out the cards really quickly? How long can I expect them to last? It will do if they run too hot, or very high voltage. I think otherwise you're looking at years, graphics cards aren't known for dying early and if they do, you should be able to get them replaced under warranty assuming you didn't flash the BIOS. |
|
|
|
|
Can you provide long-term viewer statistics and earnings history? It's hard to go off a single day's predicted earnings and one set of viewing stats that could have been bought traffic, no offense.
I'm just trying to work out why you're selling a $250/mo website for $500 when you could easily borrow $500 on a credit card, pay it off in 2 months and still have the site.
|
|
|
|
|
I figured no one's doing it, and I can do it (used to work at a bookie) so I'll shoot for it.
How it Works
- You PM me the bet you want to make and your receiving address, and wait for my reply confirming the odds and the payout if you win.
- I will generate an address for you to send to, and you will send me the BTC you want to bet.
- I will generate a PM for you confirming your bet, with a reference number which you can quote when you win.
- You are anonymous, but I certainly won't complain if you post here and vouch for me.
- Odds are subject to change, nothing is final until I *PM* you odds. I will try to keep the thread up to date but obviously things can change when I'm asleep or out or whatever.
Rules
- Maximum bet 1 BTC. I don't want to go broke and don't want to make anyone broke.
- Minimum bet 0.02 BTC. Don't want to be hit with a bunch of microtransactions and not be able to pay fees.
- Winnings must be claimed within 30 days of a bet being won.
- If there's a bet you want to make which isn't here, just ask for some odds and I'll offer or not.
- You can place aggregate bets, for example a bet at 2/1 and one at 3/1, if both win you get the combined winnings (6/1) but if only one or neither wins, you get nothing.
- It is your responsibility to confirm that you are legally allowed to bet.
The Odds
Odds are given in the English format of X/Y. You will bet Y, and if you win, you get X back plus your bet of Y. For example, if the odds are 7/2, you can bet 0.2 BTC. If you win you get 0.9 back, 0.7 plus the 0.2 you bet in the first place.
For MLB, NBA, NFL, Ice Hockey, Soccer... whatever, just ask for odds and we'll work something out.
|
|
|
|
|
Up to 0.3.1 now with screen-based interface, finally starting to look something like the product I wanted!
EDIT: Nearly instantly released 0.3.2 as well, has hashrate-based pool monitoring.
|
|
|
|
you can't underclock the memory more than 100mhz of the core clocks, 910/840 produces good hash rate without flicking the OC switch to second position... you will also need AMDOverdriveCtrl installed  I was on linux with 3 x 6990's moved back to windows now 11.6 drivers support more than GPU's much easier to control the clocks... also running headless on windows by using vnc.. If you flick the switch you should be able to set memclocks as low as you want, I have some 5850s running at 180 mem. |
|
|
|
|
I'm very impressed with this, and would love to see addition of accepted/declined shares.
I am planning to implement your script in Autominer v0.3.1 to add miner hashrates to the main screen.
|
|
|
|
|
Only works with phoenix, but phoenix supports poclbm mining kernel so if you want to try it, install phoenix & just select poclbm kernel.
|
|
|
|
|
Just under 1% on phoenix/phatk/mineco.in.
|
|
|
|
|
Is there a patch for phoenix 1.50 yet?
|
|
|
|
6) what overclock procedure do you feel to suggest for this GPU? I'm reading here that default values for the 6990 are: GPU: 830 MHz GDDR5: 1250 MHz but here it looks like users tend to heavily downclock RAM and heavily overclock core... I wouldn't feel comfortable to overclock core at 1010 MHz as from one of the 6990x2 rows, but would it be ok to overclock core, let's say, around 900-950 MHz if the temperature doesn't rise too high? Or would it be more advisable to not overclock at all? First off, thanks for the donation. ^^ Always appreciated. Second, for overclocking, slow and steady wins the race. Don't be afraid of it, but don't rush it. First try overclocking to 866 core, 300 memory (aticonfig --adapter=all --odsc 866,300). If that's stable, try 900,300. If that's stable, try 933,300. When you find something which has uncomfortable temps (> 80) or freezes, try a few MHz lower on core until you get something stable. When you've got something you like, do aticonfig --adapter=all --odcc. |
|
|
|
|
Show Posts
