Hello,
I am new here, and i was wondering if someone experience, runing cgminer under ubuntu 12.04/10/13.04/10 using both, the newly antminer u1 and block erupter's (on the same hub) and multiple cgminer instances.
You shouldn't need multiple instances of cgminer. The current version of cgminer works fine with both of these devices at the same time by default without any special flags or multiple instances. |
|
|
|
|
Completely useless in today's ASIC mining era, they would not remotely have any useful hashrate. No commodity hardware can possibly remotely compete with any ASIC ever again unless they add ASICs specific for bitcoin mining into the hardware itself.
|
|
|
|
lol, supposed attacker PM'd me yet again demanding ransom... this time 0.3 BTC/day.  Too bad he can't be traced... I'm pretty sure a lot of us would be willing to pay him a visit and give him a nice "cease and desist" order... Cuz it's real hard to operate a computer with crushed hands! If anyone cares to contact this forum's mods in an attempt, he's PM'ing me from this user: https://bitcointalk.org/index.php?action=profile;u=300889Only theymos has such superpowers. I suggest you PM him if you think it will help you in some way. |
|
|
|
Simply, dont allow self moderated topics in marketplace, selfmoderated topics are fine as long as money isn't involved.
Companies announcing hardware, software being announced, potential scams, trojans, viruses, unhappy customers being silenced, protocol development discussions... there's a lot more going on than just marketplace where there is potential for abuse of self moderation. |
|
|
|
|
Hmm what about overheads, money spent on mining hardware, electricity paid for, do these count as losses? Does that mean those mining at a loss can write it off on tax as a loss?
Surely bitcoin needs legitimacy and of course it will be impossible to trade in it and bypass every nations' laws (none of us expected to anyway), but there's so much to yet be defined...
|
|
|
|
PS:
Guy's
What about
cg_wlock(&control_lock);
.....local_work++;
.....total_work++;
cg_wunlock(&control_lock);
I think there is a need to lock them everywhere or ?
Thanks
Mostly harmless, but probably wouldn't hurt to protect them with the write lock for when mining at multiple different types of pools at once (eg GBT + stratum), yes, thanks. Super, If you can add local_work++ inside total_work_inc will be great  That's a purely cosmetic number and adding locking for it does not protect anything of any value. |
|
|
|
I've tried the following:
--hfa-options "NS1:600,NS2:550" - No devices found
This would be the correct set of options (as per the readme example I gave you). However it has no bearing on whether cgminer finds devices or not, it just tells cgminer what to set NS1 and NS2 clockspeeds to. If you're not finding devices, you are having other problems. |
|
|
|
Difficulty jump was just 18% to 5006860589, so the great flood of hyper-TH miners has not reached the shores yet...  Think exponential function. That amounts to adding about 7000TH. Are you sure you don't call this a lot? |
|
|
|
|
Antminer uses cgminer which includes the --rotate option to switch pools at regular intervals. Just set that pool strategy, specifying how long between each pool.
|
|
|
|
I think I have named them all individually but no matter what string I use for --hfa-options I can't get it to load. Can you write me an example?
Thanks
Shall I quote the docs again? --hfa-options <arg> Set hashfast options name:clock (comma separated)
This command allows you to set options for each discrete hashfast device by
its name (if the firmware has naming support, i.e. version 0.3+). Currently
this takes only one option, the clock speed, although future options may be
added.
e.g.:
--hfa-options "rabbit:650,turtle:550"
|
|
|
|
You seriously want to solo mine instead of pool mining? Do you have some amazing mining rig or what?
I for instance solo mine with a 300 MH USB Block Erupter, because "Pool Mining" is not profitable in my case  Solo mining with 300 mh/s? That doesn't really seem like much when you compare it to the +100 gh/s ASICs. It won't earn anything mining regular, so he uses it like a lottery. |
|
|
|
Hi Con,
Firstly thanks for all the updates aimed at Hashfast devices, 4.2 has helped a lot.
As all Sierra's are not born equal I need to run them at different clock speeds. I successfully used the '--hfa-name Slug --usb 4:42' to rename one device to later allow me to use '--hfa-options "rabbit:650,turtle:550"'
If I add more renaming to the string it simply doesn't find any device. Can you tell me what I have wrong with the below?
--hfa-name NS1 --usb 1:7 --hfa-name NS2 --usb 2:7 --hfa-name NS3 --usb 2:4
Thanks
--hfa-name <arg> Set a unique name for a single hashfast device specified with --usb or the first device found Name one at a time. You only need to name them once; the names should keep for ever more even with firmware updates. |
|
|
|
Wow, this link even got newer firmware then the official one. Thanks Yes I make it and maintain it to be in line with my cgminer releases. It's up to date with cgminer 4.2.1 |
|
|
|
|
There are a lot of cgminer fixes and stability improvements with the latest firmware. The hashrate demonstrated should match the pool now, and there are far more useful stats in the advanced->stats tab. I worked with them on coordinating the cgminer updates.
No, I doubt you'll ever see more than 1.6TH out of these devices, but I have nothing to do with that aspect.
|
|
|
|
For those of you on windows who have devices that don't show up on USB3 slots, you can try the following binary (it is otherwise identical to the 4.2.1 release): http://ck.kolivas.org/apps/cgminer/temp/cgminer.exeIf it turns out to fix the problems, I might just re-package 4.2.1 for windows. |
|
|
|
I have set up local mining with 6x Antminer U1 on bitcoin, hoping for the lottery ticket to come out.
Can I do something to lower the CPU usage ?
You can mine solo with cgminer on Antminer U1s directly to bitcoind which uses a lot less CPU without needing any pool software. |
|
|
|
After patching the cgminer 4.0.0 patch (HEX16 by Technobit) I tried to "make" my cgminer-4.0.0 with MinGW/MSYS-Shell for the HEX16B. But it failed! Would be awesome if anyone could help me! We do not support external patches on the cgminer code. Seek help from whoever provided those patches. Though it looks like you just need to do what it says: install a winusb driver. |
|
|
|
Hashfast per die clock rate setting: I have noticed that in driver-hashfast.c, there seems to be adaptive clock rate setting per die: applog(LOG_INFO, "%s %d: Die temp below range %.1f, increasing die %d clock to %d",
hashfast->drv->name, hashfast->device_id, info->die_data[die].temp, die, hdd->hash_clock);
hfa_send_frame(hashfast, HF_USB_CMD(OP_WORK_RESTART), hdata, (uint8_t *)&diebit, 4); Is there a way to set per die clock from command line or conf file? Reason I'm asking is one of my dies seems to work fine up to 150MHz then it completely stops working and I would like to clock dies 0-2 with normal clock and underclock die 3. Edit: By the looks of your comments and the code it seems that per die clock setting will be possible for FW 0.5 and up. Do you already got FW 0.5 from hashfast by any chance? Older firmware 0.3+ can do per die clockspeeds as well but when there is a large difference in the clocks it causes huge dips and peaks in the metering out of work which can present temperature and other issues. It is not possible to set clock speed per die on the command line yet but it is possible to add that feature. |
|
|
|
|
Show Posts
