My "confirmed reward" has gone negative.... Slush, do I owe you any bitcoins?
Confirmed reward: -0.01298504 BTC Your confirmed balance from valid blocks
I didn't even think this was possible and am myself curious as to whats up. Edit: Anyone able to help with: https://bitcointalk.org/index.php?topic=327410.0The mystery was partially solved, as my account page now contains this message: Notice: The last payment to you was sent twice by a mistake. This has caused that your confirmed reward is temporarily below 0 BTC. We're sorry for the inconvenience. Strange, but I hope that it is correct. |
|
|
|
|
My "confirmed reward" has gone negative.... Slush, do I owe you any bitcoins?
Confirmed reward: -0.01298504 BTC Your confirmed balance from valid blocks
Edit: later the following message appeared on my account: "Notice: The last payment to you was sent twice by a mistake. This has caused that your confirmed reward is temporarily below 0 BTC. We're sorry for the inconvenience."
Not sure how to audit the payments (the payout history uses rounded values and UTC, but I guess that with some effort that should be possible)
|
|
|
|
|
This is probably not unique to the Pi.... you need to get all your settings on the client correct to be able to connect to wifi: same encryption type (usually WPA these days, as WEP is obsolete and unsafe), same key or passphrase, same wifi channel, correct mac address entry if you filter mac addresses.... breaking it is easier, but will not get you connected....
|
|
|
|
So... Slushs pool ALSO moves onto the next block found on the network and 10 hours mining a block is actually 10 hours since it found one (others have been and gone since)
Is this right?
If you observe your mining software or the Slush stats page you'll see that this pool moves to the next block if the current block was solved by someone (could be another pool). It keeps moving until it solves a block. If we are extremely lucky we'll solve 2 blocks in a row, but usually it takes hours and quite a few blocks between successful blocks by Slush. |
|
|
|
When I try this:
D:\[your file path]\bfgminer-3.5.1-win32\bfgminer-3.5.1-win32\bfgminer.exe -o [your pool and port] -u [your username] -p [your password] -G -S bigpic:all --icarus-options 115200:1:1 --icarus-timing 3.0=100''
I get "All devices disabled, cannot mine!" My Bitfury shows correctly as COM5. Bit lost. My Erupter is working fine.
Do not run icarus options with your bf1 D:\[your file path]\bfgminer-3.5.1-win32\bfgminer-3.5.1-win32\bfgminer.exe -o [your pool and port] -u [your username] -p [your password] -G -S bigpic:\\,\comN -S erupter:\\.\comN Where N=the com port number You can not run any instance of -S all or -S bigpic:all I run bfgminer.exe -o Stratum+tcp://nl1.ghash.io:3333 -u WhoFlippinCares.1 -p 12345 -G -S bigpic:\\.\com118 -S erupter:\\.\com3 -S erupter:\\.\com119 -S erupter:\\.\com120 -S erupter:\\.\com121 -S erupter:\\.\com122 -S erupter:\\.\com123 -S erupter:\\.\com124 -S erupter:\\.\com125 -S erupter:\\.\com127 -S erupter:\\.\com128 -S erupter:\\.\com129 -S erupter:\\.\com130 -S erupter:\\.\com131 -S erupter:\\.\com132 -S erupter:\\.\com133 -S erupter:\\.\com134 -S erupter:\\.\com135 -S erupter:\\.\com136 -S erupter:\\.\com137 -S erupter:\\.\com138 -S erupter:\\.\com139 -S erupter:\\.\com140 -S erupter:\\.\com141 -S erupter:\\.\com142 -S erupter:\\.\com143 -S erupter:\\.\com144 -S erupter:\\.\com145 -S erupter:\\.\com146 -S erupter:\\.\com147 -S erupter:\\.\com148 -S erupter:\\.\com149 this makes it possible to run a single instance of bfgminer with erupters and fury's running side by side......Good Luck! I disagree in regard to running -S bigpic:all. I am running my single BF with bfgminer 3.5.1, with the 'alfa driver' provided by Beastlymac, through a batch file called #MINE.bat on Win7 64, the content of this batch file is bfgminer.exe -S bigpic:all -o [pool url] -u [user name] -p [password] Agree that there is no need for Icarus options for the BF. Cheers |
|
|
|
Does Slush still pay out every 15 minutes? How does that actually work now? I have my payout set at 0.1 and I have 0.11057241 reward sitting there, when will it be paid? Am I missing something here? Obviously I want to sell why it's high...
The FAQ on Slush'e web site https://mining.bitcoin.cz/faq/#payouts says "Pool is sending payouts automatically every 15 minutes". In my experience it tends to happen every whole hour, but not always. Eventually you'll get your payout, the delay is frustrating, but we learn to cope with that... |
|
|
|
Hi all,
I am running Windows 8.1 x64 and bfgminer 3.5.1 but I cannot get the computer to install the driver. I have included screenshots.
I followed the directions at the beginning of this thread. Can anyone provide me with any assistance?
It is greatly appreciated.
Thanks.
Since Vista SP1 Windows x64 requires drivers to be signed and you cannot permanently set testing mode. If reinstalling some other OS isn't an option I'd use VirtualBox and pass the USB devices through to either some linux distro or a 32bit windows guest OS. Question though. People with Windows 7 are able to install it i'm seeing. Is there something that can be done to disable the driver signing check or is there more advance driver check mechanisms in place in Windows8.1? Thanks. I don't have Win8, however a web search shows that it should be possible to install unsigned drivers see http://windows8-drivers.com/windows-8-help-2/how-to-install-unsigned-drivers-in-windows-8/ |
|
|
|
what does the first number in bfg miner mean?
11.2/ 7.20/ 7.20gh/s that first one
the README.txt of bfgminer says "5 second exponentially decaying average hash rate" |
|
|
|
I have 50 running at 90Gh/s total. Two throw tons of hardware errors. Shares found on same two are very low even though hashrate is reported normal.
These things run very cool. Begging to to overclocked. Hoping to be able to tweak in the future.
Pictures?  I posted above how it is possible to hardware overclock. Firmware over clocking might be available in the future I just don't want to cause more issues that would then need to be fixed. I went back and reread this whole thread. Maybe I'm just blind, but could you help out with a link to where you have the OC info? Back in https://bitcointalk.org/index.php?topic=319419.msg3486886#msg3486886 you wrote "Edit. It is possible to overclock the units and push them to potentially 2.7 by replacing the 22k resistor with a 10k one." but a little more info would be helpful... BTW: I'm currently running 7 (thanks ssinc) with w7x64, cgminer 3.7.2; 10 port cheap powered hub with max of 4 units in each hub RESULTS: avg 2.3 per unit ~nh Anyone that *should* be over-clocking these, would have the knowledge to look at the board and see which resistors are 10k; However, with that being said there are two resistors on the board at 10k, R8 & R11 (R8 next to PRG button, R11 next to RST button), so I'm assuming by Beastlymac's statement that both 10k resistors would need to be swapped out to 22k, but would like confirmation that it would be both, if not both which, R8 or R11? EDIT: Also, you would be replacing it with a SMD 1206 22k ohm 1/8w resistor (Beastlymac, correct me if I'm wrong please), which seem to be pricey at DigiKey at the moment due to stock shortages it looks like. However Mouser does have a good amount in stock at the moment and are much cheaper than DigiKey. Beastlymac said "replacing the 22k resistor with a 10k one", you are suggesting "that both 10k resistors would need to be swapped out to 22k" - didn't you get 'your resistors crossed'? |
|
|
|
are you going thru a hub? If so find a USB port directly on your tower that's not being used and give that a try
It should recognize a new device install a driver and be a fresh port
also post your command line
Yeah I'm going through a rosewell 10 port hub atm Main problem is that once I launch the BAT file it say the program stopped working and I either have to debug the program or close it. You can edit the BAT file (right-click, select Edit). The content of my BAT file for bfg 3.5.1, is: bfgminer.exe -S bigpic:all -o [pool] -u [user] -p [password] I'm using the 'alfa driver' provided by BeastlyMac (and the older serial drivers for the BE's running on the same pc, did not try the WinUSB ones for the BE's so far). Note that the driver is installed through the file 'driver.inf' and not 'driver.ini' as incorrectly written in the instructions on the first page of this thread. Good luck |
|
|
|
|
Again there is an issue with reward payouts.... not happening.... (confirmed, above the threshold, should have been paid once every whole hour)
Slush, please send those coins....
|
|
|
|
For those of you that want to run both BE's and BF on same pc (Win 7):
BE's (Block Eruptors) running under an instance of bfgminer 3.2.1, with the following shortcut (text in Target field of shortcut)
C:\temp\bfgminer-3.2.0-win64\bfgminer.exe -o [pool url] -u [user name] -p [password] -G -S erupter:all --icarus-options 115200:1:1 --icarus-timing 3.0=100
(change to suit the location of your executable)
Once the BE's are running, run a separate instance of bfgminer for BF. I used
either bfgminer 3.2.0 ('special', with the BF driver installed per the support thread)
using bfgminer32 ver 3.2.0 and the batch file of the style
bfgminer.exe -S "BF1:all" -o [pool url] -u [user name] -p [password]
(this works ok w/o H errors)
or 3.5.1, using a batch file with the content:
bfgminer.exe -S bigpic:all -o [pool url] -u [user name] -p [password]
(works ok but with increasing H errors)
Had both running on the same old laptop for a few days now (with BF going on and off for different tests and s/w configurations).
Cheers
Sir, this post was most helpful! I'm still waiting for my BF's to arrive, but when they do I'm planning to run them together with my current BE setup. I was already looking for information to prepare it so they could be up and running as soon as they arrived. So thanks to you I can make sure I have the right miners and command lines ready. Thank you! You are welcome, good luck Let us know what performance are your BF's getting Cheers |
|
|
|
|
For those of you that want to run both BE's and BF on same pc (Win 7):
BE's (Block Eruptors) running under an instance of bfgminer 3.2.1, with the following shortcut (text in Target field of shortcut)
C:\temp\bfgminer-3.2.0-win64\bfgminer.exe -o [pool url] -u [user name] -p [password] -G -S erupter:all --icarus-options 115200:1:1 --icarus-timing 3.0=100
(change to suit the location of your executable)
Once the BE's are running, run a separate instance of bfgminer for BF. I used
either bfgminer 3.2.0 ('special', with the BF driver installed per the support thread)
using bfgminer32 ver 3.2.0 and the batch file of the style
bfgminer.exe -S "BF1:all" -o [pool url] -u [user name] -p [password]
(this works ok w/o H errors)
or 3.5.1, using a batch file with the content:
bfgminer.exe -S bigpic:all -o [pool url] -u [user name] -p [password]
(works ok but with increasing H errors)
Had both running on the same old laptop for a few days now (with BF going on and off for different tests and s/w configurations).
Cheers
|
|
|
|
The main aim of 3.5.1 is to correct the hw error count. It will give a tiny bit extra hash rate but nothing overly significant.
The ever increasing HW error rate may still be a concern (and reduces the submitted shares...) |
|
|
|
NEW VERSION 3.5.1, NOVEMBER 7 2013Human readable changelog:Full changelog:- Bugfix: make-release: Add README.GPU document
- Demote USB string fetch failure to LOG_DEBUG since it is rather common
- Bugfix: RPC: devscan shouldn't be available to read-only access
- Bugfix: bigpic: Ignore the bitfury chip's counter as best we can
- Bugfix: bigpic: Accept other delimiters in Bitfury BF1 product string in autodetection
- Bugfix: Fix VCOM/fpgautils build check
- Bugfix: Only include VCOM code when VCOM/fpgautils support is being built
- Bugfix: Reimplement scan-serial "all" keyword
- Bugfix: bitforce detect: Close device after ZGX failure
- Bugfix: Define lowl_usb even if libusb support is omitted, since VCOM and HID drivers check against it for warnings
Tried bfgminer 3.5.1 on Win 7 64:  The hashing performance is similar to previous tests. Also tried to increase the port speed to 115200 as suggested earlier, it works but the benefit is unclear. With bfgminer 3.5.1 there is no display of the BF serial number (this is fine), but the HW error seems to creep higher and higher (maybe this is the 'truth' which was previously 'masked out'?) Performance over time: Time ####/####/#### A R HW 06:00 2.26/2.26/2.22 173 5 9 00:08 2.26/2.26/2.21 247 8 11/3.6% 00:10 2.26/2.26/2.17 282 8 14/4.3% 00:14 2.27/2.26/2.17 397 8/2.7% 23/4.8% 00:20 2.27/2.26/2.16 585 8/1.9% 32/4.8% This is running with a batch file: bfgminer.exe -S bigpic:all -o (pool url) -u (user name) -p (password) Cheers Edit: Later, after restart had quite a lower submitted shares average, changed the Com port speed setting back to the original 9600, and the rate restored to about 2.14 GH/sec (2.26/2.26/2.14 on bfgminer 3.5.1) |
|
|
|
Stats after more than 24 hours on Win7, bfgminer 3.2.0  Average hash rate is 2.26 GH/sec, actual submitted average is a bit lower. Consistent with prior results. |
|
|
|
|
@Beastlymac
Any chance of a firmware release to improve the performance of these Blue Fury devices? It seems like the consensus from actual buyers of those is that the average hash rate is close to 2.2 GH/sec, and with a high error rate (that seems to be 'cosmetically masked' by some of the mining software, as per Con Kolivas' comments). These perhaps might be improved with some controller tweaking.
There are also a few users who seem to have a small number of BF's with a much lower hash rate, you probably need to come to some agreement about how their case is rectified.
Cheers
|
|
|
|
If there is some 'spare' time because we are waiting for Atmel components, perhaps it could be used to verify the Bitfury ASICs before assembly? I'm one of those that recently got a BlueFury USB miner, based on the same chip, some of the people report significantly lower hash rates ( https://bitcointalk.org/index.php?topic=319419.100), suggesting either assembly issues or marginal chips. Similar issues are reported on the other Bitfury thread ( https://bitcointalk.org/index.php?topic=287590.0) (multiple chips per board). Weeding out the 'duds' now might save aggravation/disappointment later... |
|
|
|
Tried cgminer 3.7.0, got lower hash rate than bfgminer32-3.2.0  At least now the BF1 is detected, however the sign that something is not right is that instead of alternating between red and orange, the LED flashes red/off. Stop cgminer Hit the rst button then restart cgminer. Tried this, the LED lights up in orange briefly, but after being re-detected by cgminer it flashes red/off, and the hash rate remains as before... |
|
|
|
Tried cgminer 3.7.0, got lower hash rate than bfgminer32-3.2.0 At least now the BF1 is detected, however the sign that something is not right is that instead of alternating between red and orange, the LED flashes red/off. |
|
|
|
|
Show Posts
