how can I can to take all my BTC?
I want to change of pool
Login to your account, go to settings and request a payout..
|
|
|
Without writing to the i2c interface on the various cards (see radeonvolt for Linux tool) you cannot jump above the BIOS limits, I like how easy this tool is to use, grab the radeonvolt code for reference and merge the two and there is a good path towards a tool getting closer to those available on Windows.
|
|
|
Hey, am I the only one having some problems on this pool? Get some miner is idle once in a while. Is longpolling broken or something? Have a lot of rejects after LP Push, see: [11/07/2011 07:31:57] LP: New work pushed [11/07/2011 07:32:09] Warning: work queue empty, miner is idle [11/07/2011 07:32:12] Result: 98e9f4be rejected [11/07/2011 07:32:12] Result: 1f885fed rejected [11/07/2011 07:32:12] Result: ee558687 rejected [11/07/2011 07:32:13] Result: 13e77eec rejected
[11/07/2011 08:10:46] LP: New work pushed [11/07/2011 08:10:55] Result: 78353884 rejected [11/07/2011 08:10:58] Result: 9510d9f5 rejected [11/07/2011 08:11:01] Result: 4dc4d6fe rejected [11/07/2011 08:11:04] Result: f039908e rejected [11/07/2011 08:11:04] Result: 7d7d58ec rejected [11/07/2011 08:11:04] Result: 8d6ba15d rejected [11/07/2011 08:11:08] Result: acd6240e accepted
It's improved some over the last few days but it's still an issue, I noticed an improvement with the switch made over the weekend. His pool is picking up and he is working hard to fix things but it's still a problem from time to time and is reflected with some of what you see, I decided a little while ago to just hold out and keep my 5GH/s on his pool, it's caused some downtime and lost BTC (variance, I know, this is for discussion purposes) but he looks like he's on the right track.
|
|
|
Are changes underway, reject rate went through the roof for me in the last 30 minutes or so...
|
|
|
Is here any reason why Automatic profile mining 20 Mhash/sec more? is it just rounding in formula or dbase distributing load better? Rejection rate with automatic profile is horrible, more workers, more rejections, maybe it is compensation for higher hashrate. I have found that I get a slight increase in hashing with multiple instances. I have seen the explanation that multiple instances help fill in very small times where the CPU might be waiting for the GPU before sending it new work, hence the slight increase in hashing with multiple instances as the CPU always has somewhere to send work to without waiting. I don't get any rejection rate problems, no matter how many instances I happen to be running. I have tested this up to 6 instances per card with no real affect on rejections. I have found, however that worksize is very important when it comes to multiple instances and rejection rate. Could you go to configure miners->edit and edit the phoenix launch string, changing the work size from 128 to 256, then restart smartcoin. I'd be interested to hear if it fixes your rejection rate problems (i run worksize 256 and I'm always below 1%). I've been thinking about changing the default launch string to 256, your confirmation on this could help me make that decision. The worksize will affect performance depending on your memory clock generally speaking a worksize of 256 will be best with a memory clock around 300Mhz. I actually run that way because you don't need your GPU memory for much while hashing and this keeps the power consumption and heat lower.
|
|
|
Against a bogus store with bait and switch tactics.. Wait give me 10 minutes and I'll put up my own store you can compare against..
|
|
|
By default it uses your GPU as others have indicated, add the flag "-g no" to the arguments and it will force no GPU and then run CPU only. Your own screenshot shows what devices are being used so you have proven to everyone it's CPU & GPU and I can confirm with no arguments the miner will attempt to use both.
|
|
|
Seeing all of this downtime with no apparent update on what's happening makes it hard to stay on the pool, I've been here from almost the beginning but maybe it's time to move.
|
|
|
I am running 2x 5970 on a crap mobo with a 1000watt coolermaster silent pro psu, rock solid OCed to 800mhz at 70degrees. You can easily OC it to 850 with a bit more work and trial/error and I seen people got it to run at 900 with voltage increase. One thing i notice is those cards do NOT like low memory clock, when I set it to 300mhz-400mhz as many people are suggesting they would constantly hang, once I set it to 500mhz no issues (same clock speed etc..)
What OS are you running, asking because I have Win 7 64-bit and Ubuntu 11.04 both running 5970s are 300Mhz memory with no issues.
|
|
|
- Does anybody know whether the Chassis Model A1 'case' is custom build by Cablesaurus? - If not, does anybody know where I can buy this in Europe? - If it is, are there alternatives (open case with a place to 'hang' GPU's) available in Europe?
Make your own, stop wasting money on this sort of thing. I have both and can say the Cablesaurus is well made and not a waste of money for what you get from it. With that said I have compacted my operation and have an extra A1 chassis available, it's heavy but would consider shipping it there if interested.
|
|
|
I use 1x and 16x in mine no difference, all 8 GPUs run at full speed. One note through is that with the extenders try and get some with external power (4 pin molex) since most any board cannot deliver that kind of wattage unless specifically designed to do so...
|
|
|
Jine, any comments on what's happening with the pool, hours and hours of poor connectivity with stats reflecting some troubles (hash rate bouncing). Are you getting hammered still or is something else up?
|
|
|
Pool having issues? my miners are having trouble getting work..
|
|
|
8 GPUs in one box, I can't say exactly what causes it be it pool downtime, etc. but I was seeing OOM errors after a few hours, changed maximum heap from 16 to 32mb and haven't seen an OOM since.
|
|
|
Also, I should add that, while the summary page lists connection problems the miner's tab says "Verification failed, check hardware!"
That indicates a hardware problem, assuming with your other rig working you understand the basics I would assume this 6990 has a bad core or VRMs.
|
|
|
The collective hashrate seems to bounce up and down randomly.
For example it was at 500ghash/s for hours, then suddenly, it dropped to 410. Too big of a swing happening to everyone at once to be pure variance IMO.
I checked my total hash rate and it went down about 20% for no reason Edit: It happened again, all miners suddenly went down 50%, not a coincidence because total pool rate also halved
The stats on the web page don't mean much, they only show approximate values. I think it's because sometimes the pool website takes a 50 second long snapshot and sometimes a 70 second one, but calls them all mhash per minute. Stats are also randomly delayed, so that having good stats available can't be used against the pool. If you are mining and sending in accepted shares, then you get paid accurately for your work. Things are summarized but even with time variable the stats for a time t are still going to average to be the same. With that said while this is happening my miners do report connection problems so there are some reoccurring issues. Some people jump to a backup pool when this happens, other miners may not recover, some recover fine but when it happens the pools hash rate will drop and take some time to recover.
|
|
|
I manage a bunch of ESX and ESXi clusters. What the OP wants to do is... for lack of a better word, useless. If you have GPU cards in a server/workstation then you should just install LinuxCoin on that box and run your miners. Installing ESX/i doesn't give you any benefit, even if it were possible to get the drivers to work with the GPUs, because the whole point of ESX is to virtualize hardware. Since by definition you cannot virtualize GPU resources, and even then miners use 100% of the GPU resources anyway, there's NO REASON TO USE VIRTUALIZATION TO MINE.
Let's step through the BS in your post 1. "useless"? I have numerous VMs across multiple ESXi systems and need to keep them running, that is high power readily available hardware prime for GPUs. I need to keep ESXi running so why wouldn't I try and leverage the hardware on hand and do what the OP is looking to do. 2. You can virtualize GPU resources at varying levels between hypervisors however at this time not OpenCL. In this case pass that GPU directly to the VM itself using VT-d or IOMMU letting the VM execute whatever it wants on the GPU. break break... To address the OPs question, I have a couple of ESXi systems myself and was thinking the same thing since it's hardware. The primary issue is the stack of software you need to talk to the card, one can hack some packages into ESXi but you need X windows running with the fglrx driver. That requirement means you will need a large stack of packages to get it moving and would need to start hacking in a big way, start by researching whether or not it's even possible to get X running on ESXi itself. Sadly my ESXi systems do not support VT-d/IOMMU or I would install my GPUs, map them to a VM and run my miners there.
|
|
|
He's posing a good question, sure it happens a lot but your "blah blah blah" post and your post count shows an immaturity much more so then the original poster.
|
|
|
I used separate workers because bitcoin.lc has issues with a single worked (username and password) handling all of my GPUs. This is actually the reason I decided to move from Diablo to smartcoin, I needed something to setup a separate worker per GPU and smartcoin is really slick.
Really? I just set up one worker for bitcoins.lc and it runs like a charm. Equally split with the first worker. I haven't dug in real deep on it yet but with 8 GPUs it's a mess with about 15% rejects, with 4 GPUs I manage 10-12% rejects. One worker per and I'm down to 1.19% rejects, I haven't tried to narrow down exactly what the split is at this point.
|
|
|
|