OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[-ck]

WARNING:  There may be a problem with cgminer 3.12.1 that makes it stop retrieving work. I will investigate further and possibly release a fix in the next 24 hours. In the meantime I suggest users do not upgrade.

Sigh.

The Antminer U1 support isn't very stable either, mine all crapped out after an hour or so, I ended up with 50-odd as they dropped out and came back on.  I have 10 of them on a Anker hub, running off a PC running Debian Wheezy.

I'll update the error messages when they happen again, I'm on an intermittent SSH connection through my phone from work at the moment.

Hmm I can try reinstating the attempted reset but I'm not sure it's going to fix that... How much were you overclocking them?

Sorry, only got back to this thread.  2GH, which they've been stable with.  They do run basically OK with BFG at 2.2GH (one or two of them run at 10% HW error as reported by BFG), but I tried knocking them down to 2GH to see if that would help.

Overnight I now have 20 ANU devices reported by the API, when I actually only have 10. 

But they're still mining right? So the die - zombie - hotplug is just an ugly cosmetic issue, not that they have failed and stopped mining indefinitely. I've been running mine at 275 (2.2GH) which has been stable but I doubt they're all stable at that speed.

[fastcore]

Trend identified cgminer.exe as a virus and wiped it off my computer, blah!

[Dunkelheit667]

First of all, thanks a bunch for the Antminer U1 support.

3.12.3 running stable for two hours on my rpi. So far so good.

Just a thought, would be nice to have 12.5 MHz increments, allowing more specific fine tuning with +/- 100 GHash/s steps. Guess it's not that difficult implementing those values into the freq. table?

freq_hex freq_mhz ghash_s
0781   200.0   1.600
0801   212.5   1.700
0881   225.0   1.800
0901   237.5   1.900
0981   250.0   2.000
0A01   262.5   2.100
0A81   275.0   2.200

etc.

[Karin]

Unofficial Mac binaries have been updated for v3.12.3 and are available here.

These are precompiled universal binaries that support Mac OS X 10.5.8 through 10.9+.

[-ck]

First of all, thanks a bunch for the Antminer U1 support.

3.12.3 running stable for two hours on my rpi. So far so good.

Just a thought, would be nice to have 12.5 MHz increments, allowing more specific fine tuning with +/- 100 GHash/s steps. Guess it's not that difficult implementing those values into the freq. table?

freq_hex freq_mhz ghash_s
0781   200.0   1.600
0801   212.5   1.700
0881   225.0   1.800
0901   237.5   1.900
0981   250.0   2.000
0A01   262.5   2.100
0A81   275.0   2.200

etc.

The documentation specifies only certain numbers, have you seen anywhere the values you mention? It's easy to hack the code if you wish to try them and report back

[Dunkelheit667]

First of all, thanks a bunch for the Antminer U1 support.

3.12.3 running stable for two hours on my rpi. So far so good.

Just a thought, would be nice to have 12.5 MHz increments, allowing more specific fine tuning with +/- 100 GHash/s steps. Guess it's not that difficult implementing those values into the freq. table?

freq_hex freq_mhz ghash_s
0781   200.0   1.600
0801   212.5   1.700
0881   225.0   1.800
0901   237.5   1.900
0981   250.0   2.000
0A01   262.5   2.100
0A81   275.0   2.200

etc.

The documentation specifies only certain numbers, have you seen anywhere the values you mention? It's easy to hack the code if you wish to try them and report back

Below the freq. table there is some additional information how to 'build your own' freq. hex values. Played around with the formular and found these values. Can confirm the additional mentioned 0801, 0901 and 0A01 working fine with Bitmain's cgminer fork, at least on my Antminers. Would be a pleasure testing a modified version (on a rpi or Windows PC) and reporting back.

[loshia]

No more locking issues works perfect
Thank you Con!

[Buchi-88]

@ckolivas

as promised my impression, the new cgminer runs very well but the hardware error remain at approximately around 1%, the clock rate does not matter if 1.6 or 2.0!



greets

[HellDiverUK]

But they're still mining right? So the die - zombie - hotplug is just an ugly cosmetic issue, not that they have failed and stopped mining indefinitely. I've been running mine at 275 (2.2GH) which has been stable but I doubt they're all stable at that speed.

Yeah, they are still mining OK, it's just filling up the API with zombie miners.  I'll try upgrading to the latest version and see if it's any better.

[loshia]

@ckolivas

as promised my impression, the new cgminer runs very well but the hardware error remain at approximately around 1%, the clock rate does not matter if 1.6 or 2.0!



greets

1% and you are not happy wired
It is absolutely normal dude. You are golden. Hw errors are always there no matter what you do.

[PSL]

Information from ASIC-README:

--anu-freq <arg>    Set AntminerU1 frequency in hex, range 150-500 (default: 200)

This is not correct. Your parameter Frequency is in MHz.
Frequency in hex for 200 MHz is 0x0781 and AntMinerU1 has hash rate 1600 MHash/s at that frequency...

Could be a table with frequencies added to the ASIC-README?

[Krak]

Updated my Pi to 3.12.3 and it's not recognizing my U1s. My Jalapeño is still mining fine on the same USB hub, but the U1s are just giving me green lights every few seconds at the same time. They're not showing up in cgminer at all. Switched 'em back to my desktop and they're mining nicely, even at 275MHz.

[HellDiverUK]

Upgraded to 3.12.3, and seems to be running fine now.

[PSL]

First of all, thanks a bunch for the Antminer U1 support.

3.12.3 running stable for two hours on my rpi. So far so good.

Just a thought, would be nice to have 12.5 MHz increments, allowing more specific fine tuning with +/- 100 GHash/s steps. Guess it's not that difficult implementing those values into the freq. table?

freq_hex freq_mhz ghash_s
0781   200.0   1.600
0801   212.5   1.700
0881   225.0   1.800
0901   237.5   1.900
0981   250.0   2.000
0A01   262.5   2.100
0A81   275.0   2.200

etc.

The documentation specifies only certain numbers, have you seen anywhere the values you mention? It's easy to hack the code if you wish to try them and report back

Below the freq. table there is some additional information how to 'build your own' freq. hex values. Played around with the formular and found these values. Can confirm the additional mentioned 0801, 0901 and 0A01 working fine with Bitmain's cgminer fork, at least on my Antminers. Would be a pleasure testing a modified version (on a rpi or Windows PC) and reporting back.

That is COOL! It means that "HEX frequency" 0x1305 configures AntMinerU1 clock to run at 243.75 MHz and hash rate is about 1950 MHash/s! Tested with bfgminer that works with HEX frequency...

AntMiner clock can be tuned in 0.12 MHz steps, hashrate increased by 25 MHash/s.

[-ck]

Information from ASIC-README:

--anu-freq <arg>    Set AntminerU1 frequency in hex, range 150-500 (default: 200)

This is not correct. Your parameter Frequency is in MHz.
Frequency in hex for 200 MHz is 0x0781 and AntMinerU1 has hash rate 1600 MHash/s at that frequency...

Could be a table with frequencies added to the ASIC-README?

Yes that's a typo, it's meant to be MHz and I accidentally wrote hex. Why do you need a table when it's a single meaningful value in MHz ? The whole point was to move away from the needlessly complex configuration involving hex values and just type in a value that means something.

Below the freq. table there is some additional information how to 'build your own' freq. hex values. Played around with the formular and found these values. Can confirm the additional mentioned 0801, 0901 and 0A01 working fine with Bitmain's cgminer fork, at least on my Antminers. Would be a pleasure testing a modified version (on a rpi or Windows PC) and reporting back.

Thanks I didn't know that. I meant for you to modify it and report back lol, but I will eventually get around to adding some more frequencies.

[kano]

Updated my Pi to 3.12.3 and it's not recognizing my U1s. My Jalapeño is still mining fine on the same USB hub, but the U1s are just giving me green lights every few seconds at the same time. They're not showing up in cgminer at all. Switched 'em back to my desktop and they're mining nicely, even at 275MHz.

Will most likely require a powered USB3 hub.
(when things don't show up it is usually not enough power to them)
 lsusb
and
 ./cgminer -n
Will list everything connected that it could possibly hotplug

[aleksei85m]

Hi
Can i use BitBurner(BTC) and video cards(LTC) together?
Best regards.

[Krak]

Updated my Pi to 3.12.3 and it's not recognizing my U1s. My Jalapeño is still mining fine on the same USB hub, but the U1s are just giving me green lights every few seconds at the same time. They're not showing up in cgminer at all. Switched 'em back to my desktop and they're mining nicely, even at 275MHz.

Will most likely require a powered USB3 hub.
(when things don't show up it is usually not enough power to them)
 lsusb
and
 ./cgminer -n
Will list everything connected that it could possibly hotplug

I'm using the same hub in both locations. It's a Plugables USB 2.0 hub with a 3 amp power supply.

[Drivetotherise]

Can some one go on teamviewer and help me set up GPU mining

[HellDiverUK]

Can some one go on teamviewer and help me set up GPU mining

Well, you'll want to post in a different thread, because cgminer doesn't GPU any more.  Check the Alternative Currencies forum.