brooklynite
|
|
January 31, 2014, 03:58:36 AM |
|
Unofficial Mac binaries have been updated for v3.12.0 and are available here. These are precompiled universal binaries that support Mac OS X 10.5.8 through 10.9+. Thanks for that. I take it that means the new libusb included compiled ok on osx without a problem then which I was worried about. Why did you stop supporting GPU mining? I mean isn't that most of the miners? Those who bought thousands in ASIC hardware now have nothing to mine with it profitably except maybe CTM? While that is happening scrypt mining is very profitable. I think if ASIC for scrypt comes out, another version of coins will fork off that will be GPU only similar to what LTC started.
|
|
|
|
crazyates
Legendary
Offline
Activity: 952
Merit: 1000
|
|
January 31, 2014, 04:37:46 AM |
|
Were binaries removed for space reasons from your ftp, ckolivas? Noobs are going to flip.
I would assume it's because of the hundreds of downloads for the 3.7.2 version, taking up his bandwidth for an older version of the software that is no longer supported.
|
|
|
|
twindragon6
Newbie
Offline
Activity: 15
Merit: 0
|
|
January 31, 2014, 06:21:07 AM |
|
So how do I set a non default clock rate for an Antminer U1 with Cgminer? For example overclocking from 0781 to 0A81? in Bfgminer I would use this: bfgminer -o http://your.stratum.server:port/ -u worker.name -p password -S antminer:all --icarus-options 115200:2:2 --set-device antiminer:clock=x0781 --no-submit-stale In AntMain's version of Cgminer they use this: cgminer -o stratum+tcp://your.stratum.server:port/ -u worker.name -p password --bmsc-options 115200:20 --bmsc-freq 0781 --no-submit-stale How do I set a clock rate with Cgminer 3.12.0? Yes I am aware of the capabilities of Icarus. Is there a way to set the clock? Something undocumented? For example: --set-device antiminer:clock=x0781 and --bmsc-freq 0781 If not, will this feature be available in a future release?
|
|
|
|
Buchi-88
Legendary
Offline
Activity: 3962
Merit: 2639
|
|
January 31, 2014, 07:16:43 AM |
|
New version: 3.12.0, 29th January 2014
- Another even number, so it's gotta be stable!
Human readable changelog:
- Antminer U1 support - Numerous fixes for behaviour surrounding USB errors - pipe and IO errors, and no more attempting to reset the device since it's rarely helpful and occasionally harmful. - Libusb and libusbx have finally reconciled their differences and merged all their fixes together into a new official libusb release, so the main change in this version is updating the core code to include this latest libusb. Hopefully this might increase compatibility with some USB3 hubs on windows and make it more reliable (based on the changelogs I can see in libusb). This is the reason for the minor version number update to 12 as it's quite a substantial code change, hopefully only for the better! - Increased the hashfast overheat limit default to 90 after extensive discussions with the engineers who designed the devices. - Fixed a crash in the nanofury USB stick code. - Fixed the displayed diff shown being wrong when solo mining. - bab driver fixes courtesy of Kano.
Full changelog:
- Add support for AntminerU1 devices with the icarus driver. - Add antminer U1 to comment in udev rules. - Do away with usb resets entirely since we retry on both pipe and io errors now and they're of dubious value. - Retry on usb IO errors instead of faking success. - Check that we've cleared the pipe error after a clear request, not the err value which is unchanged. - Update to libusb-1.0.18 - Change hfa overheat limit to 90 degrees. - Relax timeout in hf get header to 500ms to match the usb timeout. - Minion - check/clear interrupts for all chips - Set info work to null after it is freed in nf1 after a restart to prevent double free later. - The second_run bool in libbitfury should be per device. Microoptimise its and job_switched usage, removing the unused results array for NF1 devices. - Fix displayed diff when solo mining at >2^32 diff. - bab - stop stale work accumulating - bab - set the default SPI speed back to 96000
Good day, I have follow problems with the Antminer and the new CgMiner! The run only at ~600 MH/s?? I install ICARUS: ./configure --enable-icarus
make Then i start: screen -S mine cd /usr/src/cgminer ./cgminer -c /home/pi/cgminer.conf --quiet --usb :10 I hope you can help me? greets
|
|
|
|
techman05
|
|
January 31, 2014, 12:45:21 PM |
|
Check the list of enabable's they are under icarus but they shown as "ANU" devices so maybe they is an enable-antminer to get them to work
|
|
|
|
techman05
|
|
January 31, 2014, 01:56:18 PM |
|
ckolivias, have you had any luck finding a problem from what I've given you. I've had my cgminer in debug mode with 80 lines shown with nothing helpfull to me other than knowing that when I start seeing a pool saying got a new block from pool about 8-10 times cgminer "dies" and brings everything else down with it.
The only other thing I'm seeing in verbatim is a was looking for x device and found this instead.
I'm going to hope it crashes while I have verbatim on so I can get some kind of error [I hope] ,but like being at a doctors office it hasn't crashed in verbatum mode yet ,but when it does it just doesn't.
Thanks
|
|
|
|
AlexeyK
|
|
January 31, 2014, 02:38:22 PM |
|
Unofficial Mac binaries have been updated for v3.12.0 and are available here. These are precompiled universal binaries that support Mac OS X 10.5.8 through 10.9+. Thanks for that. I take it that means the new libusb included compiled ok on osx without a problem then which I was worried about. Why did you stop supporting GPU mining? I mean isn't that most of the miners? Those who bought thousands in ASIC hardware now have nothing to mine with it profitably except maybe CTM? While that is happening scrypt mining is very profitable. I think if ASIC for scrypt comes out, another version of coins will fork off that will be GPU only similar to what LTC started. Ckolivas , any chances that gridseed solution will be supported by cgminer ? https://bitcointalk.org/index.php?topic=355268.0https://bitcointalk.org/index.php?topic=421921.0thanks
|
if you think that i deserve it 185h9KXxW2Efx6ynFM61ydUKsRNaVWUobs or GLC - GQjVzfk3k8gb3Cy65mBUf4ADkNNTRHgsx8
|
|
|
Buchi-88
Legendary
Offline
Activity: 3962
Merit: 2639
|
|
January 31, 2014, 03:05:11 PM |
|
Check the list of enabable's they are under icarus but they shown as "ANU" devices so maybe they is an enable-antminer to get them to work
Hello, yes the ICARUS is Enable, and the miners shows at ANU but the Hashing speed is about 600 MH/s? greets
|
|
|
|
fhh
Legendary
Offline
Activity: 1206
Merit: 1000
|
|
January 31, 2014, 03:06:39 PM |
|
don't think so - its altcoin bullshit;)
|
|
|
|
loshia
Legendary
Offline
Activity: 1610
Merit: 1000
|
|
January 31, 2014, 07:29:48 PM |
|
don't think so - its altcoin bullshit;) No it is not. If you want it sent him a precious device. Is that hard?
|
|
|
|
-ck (OP)
Legendary
Offline
Activity: 4256
Merit: 1645
Ruu \o/
|
|
January 31, 2014, 09:16:18 PM |
|
You wouldn't want me to write a driver for them for it would only do the bitcoin mining part.
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
techman05
|
|
January 31, 2014, 11:24:30 PM Last edit: January 31, 2014, 11:49:11 PM by techman05 |
|
Well hopefully if it comes down to an "I hate alt coin" standpoint on making a driver that you offer a good donation amount to make them work you could get a good collection going on something like kickstarter. I still want to get a good error pic for you before I start asking for special requests and finish my random crash party . Edit:: Hot off the pc and a link to the rest http://tinypic.com/a/34dw3/1
|
|
|
|
Viceroy
|
|
February 01, 2014, 05:13:16 AM |
|
You wouldn't want me to write a driver for them for it would only do the bitcoin mining part. Is there a legitimate reason you've abandoned all the people who supported you from day one with your silly notion to stop supporting scrypt and GPUs? Now I need to use Luke's software? You really let me down. Why don't you support the community anymore? Did Theymos pay you off?
|
|
|
|
Viceroy
|
|
February 01, 2014, 05:14:24 AM |
|
Who wants to fork this and reinstitute scrypt and GPU support?
|
|
|
|
kano
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
February 01, 2014, 06:00:52 AM |
|
You wouldn't want me to write a driver for them for it would only do the bitcoin mining part. Is there a legitimate reason you've abandoned all the people who supported you from day one with your silly notion to stop supporting scrypt and GPUs? Now I need to use Luke's software? You really let me down. Why don't you support the community anymore? Did Theymos pay you off? Dropping GPU support was well documented in this thread and even given about a years warning. Is there a legitimate reason why you can't read?
|
|
|
|
kano
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
February 01, 2014, 08:39:15 AM Last edit: February 01, 2014, 08:54:39 AM by kano |
|
My post Luke-Jr didn't want anyone to read in his thread so he deleted it He can't delete it from here. ... There's an interesting pedegree: cpuminer -> cgminer (GPU) -> BFGMiner (formerly released under the name cgminer) -> cgminer. ...
i.e. he's arguing that when he was on the cgminer team committing code to cgminer, he was a traitor and actually working on something else Much code comes from cgminer to the clone all the time. (The recent Klondike driver was all of my and BKKCoin's code copied directly from cgminer, but with replacement of our calls to our cgminer front end to libusb called usbutils, to direct calls to libusb, so his driver will be problematic on some systems due to all sorts of problems in libusb) Almost none has flowed from the clone to cgminer for a long time ... since the MMQ driver long ago that didn't work. even though he was paid for that to be included, but he didn't commit to cgminer all the changes necessary to make it work. 11-June-2013 14:58 <Luke-Jr> I put everything you guys do in by default, unless I have a good reason not to.
|
|
|
|
Luke-Jr
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
February 01, 2014, 09:42:44 AM |
|
Well it seems like he is a liar then.
Only because you're listening to a real liar.
|
|
|
|
kano
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
February 01, 2014, 10:23:21 AM |
|
Well it seems like he is a liar then.
Only because you're listening to a real liar. Not if he isn't listening to you
|
|
|
|
FalconFly
Sr. Member
Offline
Activity: 252
Merit: 250
Sentinel
|
|
February 01, 2014, 10:58:11 AM Last edit: February 01, 2014, 04:40:12 PM by FalconFly |
|
I'm having some odd issues since a while.
Running 3 BlueFuries and 1 BiFury USB miners (WinXP SP3), my cgminer started crashing every few days some weeks ago. Looking at the Task Manager, I found out its RAM usage is increasing all the time, presumably running into some kind of RAM limitations (it's an older centrino notebook with 1.5GB of RAM). After a day, I see it at about 60MB use of RAM, a day later it's at ~150MB, another day later roughly 350MB+ (which is about the area when it becomes very crash-prone, including using any of its basic menu functions that then can easily crash the application). Generally its RAM consumption increases at about 4KB/sec.
The BiFury firmware was updated to V1.3 90deg version, which didn't change anything basically. The cgminer directory and executable are manually excluded from any antivirus scan that could interfere.
Could it be recent cgminer versions have some form of memory leak when operating this combo? I remember running just the 3 BlueFury devices for weeks (cgminer 3.8.4) never had this issue. Only after adding the BiFury, I experienced this behaviour, so I think it's possible that it comes from the BiFury code portion running. (so far I ran 3.8.4, 3.8.5 (BiFury added), 3.9, 3.10 and now 3.12).
Since the notebook is old, however, and if noone else is seeing such issues.... Could be my hardware of course. It's running pretty cool and the Notebook hardware basically is mostly idling along, so at least it's clearly not running into heat issues. Miners are cooled with a big USB fan and operated off an external powered USB hub.
|
This forum signature is like its owner - it can't be bought
|
|
|
Viceroy
|
|
February 01, 2014, 01:00:11 PM |
|
Dropping GPU support was well documented in this thread and even given about a years warning. Is there a legitimate reason why you can't read?
Oh, that's a genius approach... attack me because I didn't read this 716 page thread. You are a jackass. (Actually I contributed somewhere in the first few pages of this thread and then supported cgminer as the miner of choice. No more, not with a jackass like Kano at the helm.) * Viceroy let down by an old friend who doesn't seem to recognize the future is NOT bitcoin. Just added to the top of my tutorial page: WARNING WARNING WARNING
THIS TUTORIAL WILL NOT WORK WITH CGMINER BECAUSE KANO AND ckolivas HAVE DECIDED TO ABANDON SUPPORT FOR THEIR PRODUCT INSTEAD ONLY CHOOSING TO SUPPORT ASIC BITCOIN MINERS. THEY HAVE ENDED ALL SUPPORT FOR GPU MINING AND ABANDONED THEIR COMMUNITY. DO NOT USE CGMINER AS THE AUTHORS ARE TRAITORS AND JACKASSES.
WANING WARNING WARNING NEW PREFERRED MINER IS BFGMINER Maybe you could change the FIRST PAGE to reflect the fact that you have RECENTLY abandoned GPU's and Scrypt? JACKASS!
|
|
|
|
|