|
2084
|
Bitcoin / Mining software (miners) / Re: BFGMiner 4.2.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, RockMiner R-BOX
|
on: June 25, 2014, 06:00:03 AM
|
Hey folks! I'm bumping this because it's still a problem. Can someone please give me a hand in fixing this? Thanks! I'm having a problem with bfgminer (both the new 4.2.0 version and the 4.1.99 jstefanop fork) with failover for both gridseed and zeus (GAWMiner fury) rigs. Because it's happening with both versions I'm sure it's something dumb. so I thought I'd seek help here. What's happening is that failover works going from pool 1 to pool 0 when pool 0 becomes active, but it doesn't work when pool 0 goes dead. Bfgminer reports that it has switched back to pool 1 but the pool doesn't show any hashrate. As well, my external monitor (CgminerMonitor version 0.7.0) shows the rig as still connected to pool 0. Finally, I'm getting the following messages displayed in bfgminer: [2014-06-16 19:26:49] Pool 0 slow/down or URL or credentials invalid
[2014-06-16 19:27:02] Network difficulty changed to 792 ( 5.68G)
When it's doing this, it sometimes changes the network difficulty several times, then give the "pool 0 slow/down" message again, but it's not accepting shares. Here's how I'm running bfgminer for the furys: /root/bfgminer/bfgminer --scrypt -S zeus:/dev/ttyUSB0 --nocheck-golden --chips-count 6 --ltc-clk 328 --config=/opt/cgminer/cgminer_conf/cgminer-ttyUSB0.conf and here's the config file: {
"pools" : [
{
"url" : "stratum+tcp://r6284.g21.rigs.eu.betarigs.com:9116",
"user" : "chrison999-6284",
"pass" : "x"
},
{
"url" : "stratum+tcp://pool.ipominer.com:3333",
"user" : "corion49.USB0",
"pass" : "x"
}
]
,
"failover-only" : true,
"failover-switch-delay" : "240",
"api-listen" : true,
"api-mcast-port" : "4035",
"api-port" : "4035",
"expiry" : "120",
"hotplug" : "5",
"log" : "5",
"no-pool-disable" : true,
"queue" : "1",
"scan-time" : "30",
"scrypt" : true,
"shares" : "0",
"kernel-path" : "/usr/local/bin",
"api-allow" : "W:127.0.0.1",
"usb" : ":1",
"request-diff" : "512",
"cmd-sick" : "pkill -9 bfgminer0",
"cmd-dead" : "pkill -9 bfgminer0",
"gridseed-options" : "baud=115200,freq=838,chips=40,modules=1,usefifo=0"
}
Can anyone see any errors in this or offer any suggestions on how to fix this problem? Thanks! Regards, Chris I'm actually having the exact same issue and trying to figure out what the problem is... |
|
|
|
|
2085
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Fury/Blizzard tuning and mods
|
on: June 24, 2014, 08:23:46 PM
|
|
BTW to people asking questions on the read count, I have done a bit of research in the driver with this and it really won't do much.
Read count is the amount of time before the driver requests new work (in milliseconds, so 300 RC = 30 seconds), so the chips don't sit idle. As long as you keep it under the amount of time it takes to cover a full nonce ranges (which is roughly 200k/chip_count), which for a blizzard is like 3,000 seconds so it would never run out of work before a block is found anyway. You also want it over 10 seconds because of the overhead in processing new work requests in the miner.
Read count would only have a performance impact if zeus decided to put like 500 chips on one machine.
|
|
|
|
|
2087
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Fury/Blizzard tuning and mods
|
on: June 18, 2014, 06:05:32 PM
|
We need this damn datasheet for the Zeus chip.
The last thing that I see could have an effect is the resistor connected to MODESEL pin (pin 40), but without the datasheet, there is no way we can figure what it's supposed to do.
they could have a few multipliers/dividers for frequency that are related to the value of the resistor.
If I had a board with a single chip on it, it would be easier to try this kind of things.
If the chips were at any time able to hash 300Kh/s each, there must be a way to activate it, and if they claimed 300 Kh/s, it also means that the chips were able of more.
I know Terry(CEO zeusminer) has offered on the litecointalk forums chip samples for anyone that wants to give a shot at designing a better board. I can arrange to have a few bare chips with their test board shipped with my next order if anyone is interested in playing around. |
|
|
|
|
2088
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Fury/Blizzard tuning and mods
|
on: June 17, 2014, 07:14:43 PM
|
I'm also almost sure that the BPCLK pin on the chip is there for something related, directly or not, to the 382 clk limit
Back-Plane-Clock? Google wasn't very helpful. Is it an input or an output? It might only be enabled in testmode/bypass. A full datasheet for the chip would be very helpful, without that we're stumbling in the dark. It does look like Zeus did not design the device with much scope for overclocking in mind, given the poor use of the 8 bit clock speed configuration field of the command packet (why didn't they scale the clock by a factor of 2, rather than 2/3?). Here is a pretty detailed schematic of the blizzard board and zeus chip pinouts http://zeusminer.com/wp-content/uploads/2014/06/BLIZZARD_X6Chips.pdf |
|
|
|
|
2089
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Fury/Blizzard tuning and mods
|
on: June 16, 2014, 03:48:21 AM
|
|
Hey good work hardware side of things here! Hopefully you guys can do the same for the blades in the larger machines (they have the same voltage regulator chip so I'm assuming it will be very similar).
If you guys want ill take off the over clock limit on the driver.
|
|
|
|
|
2091
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN][X11] X11 (Darkcoin etc) miner (based on sph-sgminer)
|
on: May 26, 2014, 09:00:21 PM
|
I have to say the Devs + friends of Darkcoin are true geniuses...They have been mining this version of SGminer since day one with their farms, while they initial released it as "only" a CPU coin, then released a GPU friendly version that mined at half the hash rate to gain even more adoption and drive the price up, and finally release the version they all have been mining on after the hard fork (even if this is the version the Devs are running on...they probably still have an even more optimized version). My hats off to you guys  |
|
|
|
|
Show Posts
