Find out. Many (though mostly older) PSU's need a minimum load on the 5v or they dont regulate properly. This can cause severe issues, like high fluctuations on the 12V.Just connect a cdrom drive, light bulb, hdd or whatever to put a minimum load on the 5V and see if it makes a difference. If it doesnt help, its not going to hurt either.

This worked fine when load on all three rails was relatively balanced but efficiency is generally low and when the rails are out of balance efficiency suffers even more.

Two things occurs in roughly that last decade. The first is that 3.3VDC and 5VDC isn't really used for any significant load. At one time they were used to directly power CPU, memory, motherboard logic, etc. However the operating voltage of modern components (including ASICS) is <1 VDC. The power requirement for a motherboard also increased significantly. A high end CPU, memory, and motherboard can pull 200W+. On multi-CPU servers with large banks of memory this can be 500W or more. 500W @ 5VDC = 100A. You would need a cable the size that connects to your car battery to handle that safely. So motherboards contain their own DC to DC regulators. The powersupply pumps in 12VDC the motherboard converts it to whatever it needs.

The second was the "80Plus" program and it became a big marketing campaign. People began buying more efficient PSU and it became increasingly hard to design a PSU thatcould deliver massive current on the 12V rail, operate with minimal or no load on 3.3V, and still remain very efficient.

Today almost all high end (500W+) PSU use a concept call direct DC conversion. Since the majority of the load is on the 12V rail ALL the power is converted to 12VDC. Then the small 3.3V and 5V loads are converted off the 12V rail.

There are several different types of Bitcoin clients. Hybrid server-assisted clients like Electrum get a lot of their network information from centralized servers, but they also check the server's results using blockchain header data. This is perhaps somewhat more secure than either server-assisted clients or header-only clients.

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.

For anyone that has been running overclocked 4 VRM boards (since that was the only firmware we had to choose from) then you might want to really think before switching to .95

If you have a new miner without a lot of HW errors (cores turning off) you may be fine with .95 but just know you are stuck with a substandard miner compared to one with 8 VRMs

overclocking?.... how are you doing that?

4 VRM boards with pre-.95 firmware FORCED us to overclock by running high voltage/amps from our VRMs. The reason I was able to get to 520Gh stable on my miner with .93 was that the overclocking compensated for the HW errors and that .93 restarts often if you miner starts to drop performance.

You can notice overclocking by the WU value you have compared to the number of cores you have running. When you run .95 on a 4 VRM miner you will see a big decrease in WU

Since I am stuck with running .94 I will try putting a cgminer restart in the cron for every 30mins or hour to keep performance up

Hey If you can make that work please post how you added that to cron. crontab -e is not working

so if anyone has saved settings from cgminer, and just hit enter for the default config file... and experienced a gui glitch afterwards... this is the fix: after all the settings in cg are as you want them...when you save by hitting "S"for settings, then "W" for (write config file)in CGMiner don't hit "Enter", instead, type "/config/cgminer.conf", Then hit enter. Until I figured this out, I had to ssh into the miner, and start a second instance of cgminer to get mining, because KNC had added "HTTP://" to the stratum address, and entered my workername info incorrectly. The result, was a dead instance of cgminer, and a broken GUI, which was stopping me from changing the settings in a catch-22 situation. I inadvertantly used the cgminer default config file name in an attempt to fix the problem, not knowing that knc is using a custom location to store the config file. Seeking it in linux and typing it in the cgminer save field cured the problems. I now am able to assign the ip adress and save it as well now, where it wouldn't before, which means now, i dont have to sniff the ip either to ssh into the machine, or access the gui, because its all booting perfectly now, and connecting automatically to the pool, and hashing away by the time I can ssh in and do a screen -r.... no ip sniffing necessary. What a relief! p.s... 0.95 is working fast as any I've had loaded now too.

so if anyone has saved settings from cgminer, and just hit enter for the default config file... and experienced a gui glitch afterwards... this is the fix: after all the settings in cg are as you want them...when you save by hitting "S"for settings, then "W" for (write config file)in CGMiner don't hit "Enter", instead, type "/config/cgminer.conf", Then hit enter. Until I figured this out, I had to ssh into the miner, and start a second instance of cgminer to get mining, because KNC had added "HTTP://" to the stratum address, and entered my workername info incorrectly. The result, was a dead instance of cgminer, and a broken GUI, which was stopping me from changing the settings in a catch-22 situation. I inadvertantly used the cgminer default config file name in an attempt to fix the problem, not knowing that knc is using a custom location to store the config file. Seeking it in linux and typing it in the cgminer save field cured the problems. I now am able to assign the ip adress and save it as well now, where it wouldn't before, which means now, i dont have to sniff the ip either to ssh into the machine, or access the gui, because its all booting perfectly now, and connecting automatically to the pool, and hashing away by the time I can ssh in and do a screen -r.... no ip sniffing necessary. What a relief! p.s... 0.95 is working fast as any I've had loaded now too.

do I need to remove http://and if I remove it what is the difference, since I have the "http:// "showing and it's mining ..would it increase the mining speed

so if anyone has saved settings from cgminer, and just hit enter for the default config file... and experienced a gui glitch afterwards... this is the fix: after all the settings in cg are as you want them...when you save by hitting "S"for settings, then "W" for (write config file)in CGMiner don't hit "Enter", instead, type "/config/cgminer.conf", Then hit enter. Until I figured this out, I had to ssh into the miner, and start a second instance of cgminer to get mining, because KNC had added "HTTP://" to the stratum address, and entered my workername info incorrectly. The result, was a dead instance of cgminer, and a broken GUI, which was stopping me from changing the settings in a catch-22 situation. I inadvertantly used the cgminer default config file name in an attempt to fix the problem, not knowing that knc is using a custom location to store the config file. Seeking it in linux and typing it in the cgminer save field cured the problems. I now am able to assign the ip adress and save it as well now, where it wouldn't before, which means now, i dont have to sniff the ip either to ssh into the machine, or access the gui, because its all booting perfectly now, and connecting automatically to the pool, and hashing away by the time I can ssh in and do a screen -r.... no ip sniffing necessary. What a relief! p.s... 0.95 is working fast as any I've had loaded now too.

do I need to remove http://and if I remove it what is the difference, since I have the "http:// "showing and it's mining ..would it increase the mining speed

so if anyone has saved settings from cgminer, and just hit enter for the default config file... and experienced a gui glitch afterwards... this is the fix: after all the settings in cg are as you want them...when you save by hitting "S"for settings, then "W" for (write config file)in CGMiner don't hit "Enter", instead, type "/config/cgminer.conf", Then hit enter. Until I figured this out, I had to ssh into the miner, and start a second instance of cgminer to get mining, because KNC had added "HTTP://" to the stratum address, and entered my workername info incorrectly. The result, was a dead instance of cgminer, and a broken GUI, which was stopping me from changing the settings in a catch-22 situation. I inadvertantly used the cgminer default config file name in an attempt to fix the problem, not knowing that knc is using a custom location to store the config file. Seeking it in linux and typing it in the cgminer save field cured the problems. I now am able to assign the ip adress and save it as well now, where it wouldn't before, which means now, i dont have to sniff the ip either to ssh into the machine, or access the gui, because its all booting perfectly now, and connecting automatically to the pool, and hashing away by the time I can ssh in and do a screen -r.... no ip sniffing necessary. What a relief! p.s... 0.95 is working fast as any I've had loaded now too.

do I need to remove http://and if I remove it what is the difference, since I have the "http:// "showing and it's mining ..would it increase the mining speed

wow, mine wouldnt work that way...your call.. it should be: stratum.bitcoin.cz:3333 exactly like that.

edit: Now the date is correct in cgminer too, among other thingsNow I feel I'm ready for the other two saturns that have been "In Progress" all week... ship them badboyz already!I'll send Darkrider to pick them up....hope he has a jet

The only stat that really worked before was the 5s avg.... now that all the other stuff is working, i can see myy real average is only about 268, which matches slush's stats. I'm just glad to have one up & running for now

Careful WU includes all shares including those rejected. You only get paid for valid shares. In your case you probably are still coming out ahead just didn't want someone else to think higher WU is always better. Higher WU with same or lower reject is always better.

wow, mine wouldnt work that way...your call.. it should be: stratum.bitcoin.cz:3333 exactly like that.

edit: Now the date is correct in cgminer too, among other thingsNow I feel I'm ready for the other two saturns that have been "In Progress" all week... ship them badboyz already!I'll send Darkrider to pick them up....hope he has a jet

The only stat that really worked before was the 5s avg.... now that all the other stuff is working, i can see myy real average is only about 268, which matches slush's stats. I'm just glad to have one up & running for now

slush's avg is over the last ten rounds, including restarts & down time

I am looking at the Mhash/s* number and that is very far off from the speed of cgminer, how is yours like.

almost exactly like yours...right now cgminer says 270 average, while slush says 254639 Mhash/s, which is about 16Gh/s different, but I've had the system down a few times sorting things out, so that seems accurate

Yes, in chrome you need to do a ctrl refresh once you hit check status or it appears to loop. If it doesn't load the full page keep doing ctrl+refresh and it'll pull the data once its finishes polling all the asics.

Yes, in chrome you need to do a ctrl refresh once you hit check status or it appears to loop. If it doesn't load the full page keep doing ctrl+refresh and it'll pull the data once its finishes polling all the asics.

Saturn ...1.3 btc in 48 hours, even with all the problems I had **I'm not liking slush's "Varidiff" function... Its a tad low at times, and Id like to try another pool... **What other pool is best at this point?

Careful WU includes all shares including those rejected. You only get paid for valid shares. In your case you probably are still coming out ahead just didn't want someone else to think higher WU is always better. Higher WU with same or lower reject is always better.

It would be nice if cgminer had a WA (work accepted / min).

I do not go on WU alone however it is a metric that I use to gauge stability and performance overall.

I compared the 12 hour 13 hour and 24 hour results between firmware v0.9.4 and firmware v0.9.5 and found that by 24 hours I lost out on 200,000 potential accepted shares if I had gone with firmware v0.9.4 over v0.9.5

Yet I am doing a few final tests to see if that loss is worth it as firmware v0.9.4 needs ambient temps to be below 21°C in order to not start to take a performance hit.

And yes these tests were done in the same environmental conditions including network connectivity results from the pool.