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

[VexusMalius]

Just bought an Antminer U3. Cannot get it to run more than 30 seconds before the hash rate drops from 45Gh to about 6Gh. I'm using the latest build, as it seems to be the only one that works with it. my batch file is this:

cgminer -o http://us-east01.miningrigrentals.com:3333 -u  -p --icarus-timing=short --anu-freq 200


I change any of that and CGminer doesn't even open. I've tried using the basic bmsc lines that were in the user manual, but still nothing works.


What am I doing wrong here   Pretend I'm 5 when explaining.

[1540136263]

1540136263

[1540136263]

1540136263

[1540136263]

1540136263

[1540136263]

1540136263

[-ck]

Just bought an Antminer U3. Cannot get it to run more than 30 seconds before the hash rate drops from 45Gh to about 6Gh. I'm using the latest build, as it seems to be the only one that works with it. my batch file is this:

cgminer -o http://us-east01.miningrigrentals.com:3333 -u  -p --icarus-timing=short --anu-freq 200


I change any of that and CGminer doesn't even open. I've tried using the basic bmsc lines that were in the user manual, but still nothing works.


What am I doing wrong here   Pretend I'm 5 when explaining.

Don't use icarus timing or anu freq in your batch file as they're useless for the U3. If you want to change the frequency use --au3-freq instead, however try first without any options.

Second - the U3 is a steaming pile of shit and there is only so much software can do to work around it. The least worst you can make it work is by using a different power supply to the brick that it comes with, and get a high quality USB cable instead of the one it comes with and then try again, plugging it into a USB2 port only, not a USB 3 port. It's not uncommon these things die off once a day as ZOMBIE even under those conditions and you need to unplug them and plug them back in again to get them running again.

[Mikestang]

[snip]I'm using the latest build, [snip] I've tried using the basic bmsc lines that were in the user manual, but still nothing works.

Read the cgminer ASIC readme, not the antminer user manual, and use the correct config parameters for the U3 as ck has mentioned.

See the various U3 support threads and see what a piece of crap machine they are.  Mine are currently paper weights.  Good luck!

[WBF1]

Just bought an Antminer U3. Cannot get it to run more than 30 seconds before the hash rate drops from 45Gh to about 6Gh. I'm using the latest build, as it seems to be the only one that works with it. my batch file is this:

cgminer -o http://us-east01.miningrigrentals.com:3333 -u  -p --icarus-timing=short --anu-freq 200


I change any of that and CGminer doesn't even open. I've tried using the basic bmsc lines that were in the user manual, but still nothing works.


What am I doing wrong here   Pretend I'm 5 when explaining.

Don't use icarus timing or anu freq in your batch file as they're useless for the U3. If you want to change the frequency use --au3-freq instead, however try first without any options.

Second - the U3 is a steaming pile of shit and there is only so much software can do to work around it. The least worst you can make it work is by using a different power supply to the brick that it comes with, and get a high quality USB cable instead of the one it comes with and then try again, plugging it into a USB2 port only, not a USB 3 port. It's not uncommon these things die off once a day as ZOMBIE even under those conditions and you need to unplug them and plug them back in again to get them running again.

anecdotally, I've had mine running for 5 days now without becoming a ZOMBIE. It has disconnected twice along the way somewhere because it's now showing as "AU3 2" instead of "AU3 0", but luckily it hasn't hit ZOMBIE.

I'm using the power brick it came with but a better USB cable. I got a replacement power brick but it failed in less than a day. Im also not overclocking at all. When I tried pushing it even slightly harder it would ZOMBIE pretty regularly (in less than a day).

Seems to me the biggest problem with the U3 is quality control. Mine SEEMS to be relatively stable whereas others have had nothing but trouble.

[VexusMalius]

Were you guys using the batch 2s? Great to know I just dropped $50 on a potential shit heap.... Thanks. I'll play around with it.

[WBF1]

Were you guys using the batch 2s? Great to know I just dropped $50 on a potential shit heap.... Thanks. I'll play around with it.

Mine has the wire cage, not the dome.

[bgibso01]

"the U3 is a steaming pile of shit and there is only so much software can do to work around it."

I wish CK would just say what he thinks and quit beating around the bush. 

[studysession]

Having a little trouble please advise

AU3 0 attempted reset got error:(0) LIBUSB_SUCCESS

What is it doing when I get that error and do I need to do anything to fix it?

Thanks -
Keith

[Mikestang]

Having a little trouble please advise

AU3 0 attempted reset got error:(0) LIBUSB_SUCCESS

What is it doing when I get that error and do I need to do anything to fix it?

Thanks -
Keith

Does it keep mining?  Does it change to AU3 1?

I think that's the software resetting the miner.

[kano]

I've put an AntS3 update archive in my binaries git hub of latest 4.9.2 cgminer.
For details and installing: https://github.com/kanoi/cgminer-binaries/tree/master/AntS3

This has been tested and run on both an old AntS3 and one of the later AntS3

I don't have an AntS3+ but I suspect it should work fine there also.

The menu frequency settings in the "Miner Configuration" "Advanced Settings" web interface includes default settings for both S3 and S3+

I've, of course, tested it on my pool https://kano.is/

It should also be OK on p2pool since it's the same code related to p2pool as in my AntS1 and AntS2 releases

Please give it a try and let me know if anyone has any trouble with it on AntS3 or AntS3+

[pekatete]

cgminer for S3 looking good with the all new webui and the extras there.... just a few gremlins thus far.
1. Seems like the API has been changed a bit as I can not get any values from it (using my own monitor ... I'll check later to see where!)
2. If I save & apply from the miner configuration tab, it does not start hashing on its own, I have to go into System -> Startup and restart cgminer from there.
3. Tried restarting via cgminer-api restart but that does not seem to restart hashing (though it echoes pid ..... etc)

EDIT Otherwise ... WOW! thanks to the coder and funder of this upgrade, what a makeover both in settings and UI data candy!

[kano]

cgminer for S3 looking good with the all new webui and the extras there.... just a few gremlins thus far.
1. Seems like the API has been changed a bit as I can not get any values from it (using my own monitor ... I'll check later to see where!)
2. If I save & apply from the miner configuration tab, it does not start hashing on its own, I have to go into System -> Startup and restart cgminer from there.
3. Tried restarting via cgminer-api restart but that does not seem to restart hashing (though it echoes pid ..... etc)

API allow is now shown in the web settings so you can see and change it there

The S3 checks every 3 minutes - so restart can take up to 3 minutes.
Though once I'd updated mine and had them mining, restart worked as expected.
Also note that as mentioned you should check your settings.

I did remove a 'glitch' that Xiangfu put in there for Avalon (that Bitmain copied over) and I doubt that's the cause, but if it keeps doing that for you I'll look into it tomorrow (it's 00:45 here now)

Also, never use cgminer API restart

[pekatete]

API allow is now shown in the web settings so you can see and change it there

Yep I notcied that (which is part of my belated WOW!)

I did remove a 'glitch' that Xiangfu put in there for Avalon (that Bitmain copied over) and I doubt that's the cause, but if it keeps doing that for you I'll look into it tomorrow (it's 00:45 here now)

I assume this is in reference to the API ... I'll look at my polling code later (possibly nearer to your wake up time) and see what the new API returns to my poll. Off my head I think I use a json encoded stats+devs command with 0 as a parameter, but will confirm this later.

Also, never use cgminer API restart

Ooops-a-daisy! Do tell ..... why's that as I use it very often?

[kano]

...

I did remove a 'glitch' that Xiangfu put in there for Avalon (that Bitmain copied over) and I doubt that's the cause, but if it keeps doing that for you I'll look into it tomorrow (it's 00:45 here now)

I assume this is in reference to the API ... I'll look at my polling code later (possibly nearer to your wake up time) and see what the new API returns to my poll. Off my head I think I use a json encoded stats+devs command with 0 as a parameter, but will confirm this later.

No, that's with regards to the restart delay.
I don't think it could cause it, and in your case it was probably just that it can take up to 3 minutes?

While talking to a Bitmain person he seems to think that Bitmain hacked the API to make it give read access even if you don't set it that way.
I've not looked at their recent code hacks in the API - so who knows what crap they did in there ...
The API allow value says in master cgminer what access is allowed - no hidden back doors.

Also, never use cgminer API restart

Ooops-a-daisy! Do tell ..... why's that as I use it very often?

2 reasons:
1) a restart wont get new settings, it just restarts with the settings it was first started with.
2) restart isn't 100% reliable - processes can lock up while trying to do that under rare circumstances.
quit works fine

[pekatete]

Ooops-a-daisy! Do tell ..... why's that as I use it very often?

2 reasons:
1) a restart wont get new settings, it just restarts with the settings it was first started with.
2) restart isn't 100% reliable - processes can lock up while trying to do that under rare circumstances.
quit works fine

I use it in the knowledge it won't get new settings (can set those before if I wanted though) and reliability has not (touch wood) been an issue for me thus far .... (big sigh!)

Will post about the other 2 issues later (though you seem to have quashed the restart one). Just noticed with the API that the type has changed to AS3 ... so that may be the issue (though have not looked at the returned data from the poll just yet)

I'll leave you get your kip ...

[Mikestang]

I've put an AntS3 update archive in my binaries git hub of latest 4.9.2 cgminer.
For details and installing: https://github.com/kanoi/cgminer-binaries/tree/master/AntS3

This has been tested and run on both an old AntS3 and one of the later AntS3

I don't have an AntS3+ but I suspect it should work fine there also.

The menu frequency settings in the "Miner Configuration" "Advanced Settings" web interface includes default settings for both S3 and S3+

I've, of course, tested it on my pool https://kano.is/

It should also be OK on p2pool since it's the same code related to p2pool as in my AntS1 and AntS2 releases

Please give it a try and let me know if anyone has any trouble with it on AntS3 or AntS3+

Most excellent, will update my S3+ tonight!

[studysession]

Just left it alone over night and seemed to corrected itself. All 3 seem to be mining fine now thank you.

[luthermarcus]

Please give it a try and let me know if anyone has any trouble with it on AntS3 or AntS3+
[/quote]

AntS3+ working good on my miners. Running 30 mins with no problems.
Thank You

[Mikestang]

However, wget on the AntS3 won't allow https by default so I've copied it
to my link specified in the wget above

Am I understanding this correctly, that by following the basic update instructions, cgminer-monitor is updated as well; there are no additional step like there is for the S1?  Thanks.

[kano]

However, wget on the AntS3 won't allow https by default so I've copied it
to my link specified in the wget above

Am I understanding this correctly, that by following the basic update instructions, cgminer-monitor is updated as well; there are no additional step like there is for the S1?  Thanks.

Yes just the steps shown at the top to do it - the tar extract and the cgset do everything
The rest below just explains what's going on.
Of course you should check your settings as it suggests.

... have you ever tried the U3 on cgminer? (latest 4.9.2)
We use proper USB access to devices, not 30 year old filtered serial access that hides important information
(and cgminer has since I first changed it to use USB long ago)
Direct USB has many advantages over the filtered serial access.
... though of course the U3 itself is pretty shoddy