Last share 10 hours, 2 minutes ago  ?!!!!!!!!! really? so my Miners have only been pretending? I'm getting this too, yet miners are working. Anyone else seeing this issue? Now the web site went into 'maintenance mode' so that they can fix those mix-ups.... It will get sorted.... the mining continues, it is just in the reporting (we hope). Cheers |
|
|
|
According to https://blockchain.info/blocks/Slush there are 3 blocks found by Slush: 286275, 286296 and 286308 These are not reported in the stats page (similar to the issue with 286209 that took 'ages' to be acknowledged by Slush... Is our pool admin asleep again? (and if these 3 blocks are actually ours, then our luck and rewards are not as bad as it seems...  yeah this is not a 13 hour block. we found at least 4 during that time. Slush will fix it when he gets "back" from "x". Raised a ticket on this, now something is happening on the stats page. 286275 is there after 7:51 hours (with a strange Slush #21935), but the 2 other blocks are still missing. |
|
|
|
According to https://blockchain.info/blocks/Slush there are 3 blocks found by Slush: 286275, 286296 and 286308 These are not reported in the stats page (similar to the issue with 286209 that took 'ages' to be acknowledged by Slush... Is our pool admin asleep again? (and if these 3 blocks are actually ours, then our luck and rewards are not as bad as it seems... yeah this is not a 13 hour block. we found at least 4 during that time. Slush will fix it when he gets "back" from "x". yeah i can see slush in my mind now.....in a silk robe with all the hotties in the room (he does get 2% fee on the pool funds what is the $$$ of that?) telling them 'alas i have to take a break for 20min and fix the 'serfs' pool stats' i'll be back warm up w/o me the poor guy heh Searing you can have a vivid imagination about Slush's situation... I believe that he has some assistance in the 'boiler room', so that he no longer fixes every hiccup in person Cheers |
|
|
|
According to https://blockchain.info/blocks/Slush there are 3 blocks found by Slush: 286275, 286296 and 286308 These are not reported in the stats page (similar to the issue with 286209 that took 'ages' to be acknowledged by Slush... Is our pool admin asleep again? (and if these 3 blocks are actually ours, then our luck and rewards are not as bad as it seems... |
|
|
|
|
Good riddance Rotten Apple.....
over priced, over hyped and rolling down....
|
|
|
|
|
Barn,
Welcome back. Looking forward to exciting new mining stuff!
Cheers
|
|
|
|
Have you been able to overclock with minepeon? If so can you provide instructions/command that is needed
I used bfgminer as the default miner in minepeopn latest 2.5.0 pr1 pre-release, with the same parameters as shown in this thread in the settings page and it seemed to be overclocking to similar rates as in Windows. I don't have minepeon running now, so can't quote the exact command, however I basically copied it from my win settings. Cheers Ran minepeon again, using bfgminer as the default miner, and this is the entry in Settings (line added just before the bfgminer command line which was already there) --set-device antminer:clock=x0981 /usr/bin/screen -dmS miner /opt/minepeon/bin/bfgminer -S all -c /opt/minepeon/etc/miner.conf You'll need to change the x0981 to your desired clock value as posted elsewhere in this thread. Cheers Did you set your clock value to the max. I'm debating should I set it to the max. No, I did not do that on the minepeon. I tried a higher setting (0A01) on my Win7 rig, but it just had a much higher HW error rate, with minimal benefit in hash rate. I guess that you have to change the resistors as per the U1 manual to get any greater overclocking going without a huge increase in HW errors. Cheers |
|
|
|
 received the u1 and begin mining now. so far no problem. Looks good. Are you running with 'default settings'? I use clock=x0981, getting about 2 GH/sec. Tried a higher setting but there was an increase in HW errors without a real benefit in hash rate, so am staying with x0981. Using bfgminer 3.10. Cheers yeap, default settings, I never overclocked it since I havent get any cooler for it. So far din't found any error. I use a simple USB fan, and the HW error rate is very low at x0981. It pushes it to a long term average of about 2 GH/sec per device. I measured the temp with an IR thermometer and there was no drama. The power supply used needs to have enough juice to support it as well. Cheers |
|
|
|
received the u1 and begin mining now. so far no problem. Looks good. Are you running with 'default settings'? I use clock=x0981, getting about 2 GH/sec. Tried a higher setting but there was an increase in HW errors without a real benefit in hash rate, so am staying with x0981. Using bfgminer 3.10. Cheers |
|
|
|
Have you been able to overclock with minepeon? If so can you provide instructions/command that is needed
I used bfgminer as the default miner in minepeopn latest 2.5.0 pr1 pre-release, with the same parameters as shown in this thread in the settings page and it seemed to be overclocking to similar rates as in Windows. I don't have minepeon running now, so can't quote the exact command, however I basically copied it from my win settings. Cheers Ran minepeon again, using bfgminer as the default miner, and this is the entry in Settings (line added just before the bfgminer command line which was already there) --set-device antminer:clock=x0981 /usr/bin/screen -dmS miner /opt/minepeon/bin/bfgminer -S all -c /opt/minepeon/etc/miner.conf You'll need to change the x0981 to your desired clock value as posted elsewhere in this thread. Cheers |
|
|
|
had some issues with my newly bought bitfurys.
just wanted to share this experience:
cgminer 3.8.4 did not work well with these things, i use bfgminer 3.10 right now. so far my HW Error rate dropped from 65%(!) to 3.2% (still dropping)
Do you mean the USB Blue Fury or Red Fury or the bitfury based boards (there are quite a few of those including Drillbit and others)? Both the latest cgminer and bfgminer support the USB miners, and some of the boards. I also use bfgminer 3.10 with some of these and cgminer 3.10 with others. What sort of hash rate are you getting? There is a support thread for for the Blue/Red Fury at https://bitcointalk.org/index.php?topic=319419.0Cheers oh, sorry. to clarify: Red Fury, right now at 2.3 GH/s each (along some Block eruptors, but they work great and without any hassle). i found that i had this problem in combination with slush's pool, those Red Furys and the aforementioned cgminer version. a litecoin pool i tested worked better, still had around 20% HW Error rate. i just wanted to mention this because it seemed like it was a problem that occured with the Red Fury/cgminer/slush setup. and i am pretty sure this is a common setup. thank you for the link It looks like the latest versions of both cgminer and bfgminer provide a similar level of support for the Red Fury. The main difference in the setup is that the device drivers used are completely different. I have been mining on Slush with Blue/Red Fury devices using mostly bfgminer, but am using cgminer for other devices. If it is working fine for you on bfgminer, perhaps you should stay there. If you are interested in getting slightly higher performance from your RF miner(s) check out the thread mentioned before, as it has a lot of inputs from other users who over-clocked these devices. There is a simple 'pencil mod' which gets something like 2.6 GH/sec. If you want to explore this you should probably shift this to the Blue Fury support thread, as it is probably not unique to Slush's pool. Cheers |
|
|
|
Hi guys, just quick question for people who do have some of those new 200+gh avalon units. I am not sure if I do have miner count set correctly it is at 16 right now. Second thing I do not know what HW means, number is sometimes equal, or higher, but mostly at one third of accepted number.  I don't know the miner count for these (check mining support threads, and https://en.bitcoin.it/wiki/Avalon#Cgminer_status_page), however HW should be the hardware error count. A small percentage (say less than 5%) is probably ok, but if it is high than too many of your shares are not effective and you need to find out why (power supply issues? cooling? settings?). |
|
|
|
had some issues with my newly bought bitfurys.
just wanted to share this experience:
cgminer 3.8.4 did not work well with these things, i use bfgminer 3.10 right now. so far my HW Error rate dropped from 65%(!) to 3.2% (still dropping)
Do you mean the USB Blue Fury or Red Fury or the bitfury based boards (there are quite a few of those including Drillbit and others)? Both the latest cgminer and bfgminer support the USB miners, and some of the boards. I also use bfgminer 3.10 with some of these and cgminer 3.10 with others. What sort of hash rate are you getting? There is a support thread for for the Blue/Red Fury at https://bitcointalk.org/index.php?topic=319419.0Cheers |
|
|
|
|
Just noticed that network difficulty rose to 2193847870, which is about 23%.
Cheers
|
|
|
|
Have you been able to overclock with minepeon? If so can you provide instructions/command that is needed
I used bfgminer as the default miner in minepeopn latest 2.5.0 pr1 pre-release, with the same parameters as shown in this thread in the settings page and it seemed to be overclocking to similar rates as in Windows. I don't have minepeon running now, so can't quote the exact command, however I basically copied it from my win settings. Cheers |
|
|
|
To switch from cgminer to bfgminer you need to do following:
System=> printer and devices=> find your miners, right click=>Properties>>> uninstall drivers.
Do this for each device.
Reboot.
Then reinstall SiliconLabs drivers and you are in.
Sometimes you need o replug miners in order to run them.
In some cases you also need to tick the 'delete the driver software for this device' when you uninstall the WinUSB driver, otherwise it will be re-applied or take priority over the serial Com driver. Cheers |
|
|
|
Try using bfgminer 3.10.0. Install that silicon labs driver first though. Also make sure you uninstall all the zadig bullshit. It should run with the following batch file just fine: bfgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -u 19gu3jok7czATPb5TR8EMMuQu8qrQ5e34B_2 -p x --no-opencl-binaries -S antminer:all --set-device antminer:clock=x0981
pause An explanation for the above code, as I hate it when someone posts something, but doesn't explain why they did something some way: 'bfgminer -o stratum+tcp://stratum.mining.eligius.st:3334' starts bfgminer and connects it to the eligius mining pool. '-u 19gu3jok7czATPb5TR8EMMuQu8qrQ5e34B_2' is the username, with eligius, your payout address is your username. '-p x' is the password. On eligius anything works for a password. '--no-opencl-binaries' keeps it from trying to mine with my GPU. '-S antminer:all' tells bfgminer to scan for the antminers upon startup, otherwise you would have to hit "m""+""all" to add them. '--set-device antminer:clock=x0981' sets the clockspeed of the hashing chip, using some kind of internal lookup table. x0981 sets it to 2GHs, the clockspeed of which is derived by dividing your hashrate by the number of cores on the chip (unknown.) What is the best way to uninstall the zadig bullshit? Zadig doesn't seem to give the option. The following works for Win7. Assumptions: Windows Update search for drivers is disabled. Rationale: It is very unlikely that Windows Update would have the correct drivers for this situation. Also you need to have sufficient privileges to create directories and change system settings. 1. Remove the WinUSB driver, typically installed with the zadig utility a. Close your miner(s), open Device Manager (Control Panel, System, Device Manager) and navigate to the USB devices area until you see the device device(s) that you want to run under BFGMiner. b. Uninstall the current WinUSB driver: make sure that you tick the box 'delete the driver software for this device' (otherwise it will resurrect itself when you plug the same device and it looks for a driver) c. Repeat for all USB devices that you wish to move from CGMiner to BFGMiner 2. Install the serial USB driver a. Re-plug the first device into a USB port. When the message that a driver cannot be found, open Device Manager again, navigate to the region that shows the device b. Right-click on the device icon in Device Manager, select Update Driver, then click on “Let me pick from a list of device drivers on my computer” Select ‘Show All Devices’ and click ‘Have Disk’ c. Browse or enter the path to the driver (or re-install the Silabs drivers in case of Antminer/BE). d. If the driver is 'unsigned', acknowledge the warning that the driver is not signed (I suspect that in some versions of Windows it is difficult/impossible to install unsigned drivers, but this is beyond the scope of this procedure) by clicking ‘Next’. f. Open Device Manager, navigate to the Ports (Com and LPT) area, make sure that com ports are assigned to the required device(s). Cheers PS. I use bfgminer.exe -S antminer:all --set-device antminer:clock=x0981 Some people had also this --icarus-options 115200:2:2 --icarus-timing 2.5=90, but it only distorts the first 2 stat values in bfgminer and can be omitted (these can be either in a batch file or within the conf file) |
|
|
|
|
For the Antminer U1's suggest to check the 2 allen screws holding the heatsink to the PCB, as some of them are quite loose. Measuring the temp of the ASIC and the heatsink produces a range of results.
All of these are set to antminer:clock=x0981, which should hash at about 2 GH/sec. Under similar cooling conditions, measuring with an IR thermometer the ASIC temps are 45C, 44.8, 47.6, 44.7, 48.3, 48.2, 45.7, 48.7 (amb= 28.9C), after tightening (finger tight) the Allen screws.
The average hash rate on bfgminer 3.10 is 16 GH/sec for 8 devices.
Cheers
|
|
|
|
Received my AntMiner U1's... Hashing at about 2 GH/s each using bfgminer 3.10 Cheers |
|
|
|
|
Show Posts
