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

[Zich]

No. At the moment use the source and patch it , file driver-bitfury.c line 417

and what i have to edit in that line?

Code:

info->osc6_bits = 54;

you can change the frequency, default is 54

[SheepOnDrugs]

I get high HW when Intensity on 13

My settings:
./cgminer --scrypt -o stratum+tcp://world.wemineltc.com:3333 -u XXX -p XXXX -g 2 -w 256 -I 13 --lookup-gap 2 --thread-concurrency 8192,8192 --gpu-engine 1060,1060 --gpu-memclock 1500,1500 --auto-fan --temp-cutoff=95 --temp-target=80 --failover-only -o stratum+tcp://usa2.wemineltc.com:3335 -u XXX -p XXX

Tried lowering some settings, still getting high HW.
Without I13 I only get 500 khash on my r9 280x
What's the problem here?

[HellDiverUK]

How do I tell cgminer to ignore all devices that aren't running on WinUSB?

My Bitburners are running on cgminer and Antminers on bfgminer, but cgminer is spamming the "Install WinUSB" error constantly. 

The device I'm using identifies itself as BBF, and if I use the --usb BBF:0 command it doesn't help (drive not recognised or somesuch).

Any clues?

[os2sam]

How do I tell cgminer to ignore all devices that aren't running on WinUSB?

My Bitburners are running on cgminer and Antminers on bfgminer, but cgminer is spamming the "Install WinUSB" error constantly. 

The device I'm using identifies itself as BBF, and if I use the --usb BBF:0 command it doesn't help (drive not recognised or somesuch).

Any clues?

In the readme under Advances USB Options it says

--usb 1:2,1:3,1:4,1:*
allows you to select which devices to mine on with a list of USB
 bus_number:device_address
All other USB devices will be ignored

So if you know the bus number and address you can specify which devices you want to mine with explicitly.  I had trouble with Windoze using this method as the assignment seems to be a bit random.

[Portender]

  Just got the new version on cgminer (3.10.0) and I currently run 3 BFL jalapenos. I finally figured out how to get it to recognize the 3 jalapenos(old version I had used --disable-gpu, but now I have to use --usb :3), If there is another way like the old please let me know. Now my problem is that I can not figure out how to set the Intensity like I could in the old cgminer using --intensity d. Please help. Thanks in advance.

[Krak]

Just got the new version on cgminer (3.10.0) and I currently run 3 BFL jalapenos. I finally figured out how to get it to recognize the 3 jalapenos(old version I had used --disable-gpu, but now I have to use --usb :3), If there is another way like the old please let me know. Now my problem is that I can not figure out how to set the Intensity like I could in the old cgminer using --intensity d. Please help. Thanks in advance.

You can't set intensity because there's no GPU mining in 3.10.

[Portender]

Just got the new version on cgminer (3.10.0) and I currently run 3 BFL jalapenos. I finally figured out how to get it to recognize the 3 jalapenos(old version I had used --disable-gpu, but now I have to use --usb :3), If there is another way like the old please let me know. Now my problem is that I can not figure out how to set the Intensity like I could in the old cgminer using --intensity d. Please help. Thanks in advance.

You can't set intensity because there's no GPU mining in 3.10.

So how can I mine with GPUs now? Is it just CPU?

[HellDiverUK]

Just got the new version on cgminer (3.10.0) and I currently run 3 BFL jalapenos. I finally figured out how to get it to recognize the 3 jalapenos(old version I had used --disable-gpu, but now I have to use --usb :3), If there is another way like the old please let me know. Now my problem is that I can not figure out how to set the Intensity like I could in the old cgminer using --intensity d. Please help. Thanks in advance.

You can't set intensity because there's no GPU mining in 3.10.

So how can I mine with GPUs now? Is it just CPU?

Use the old version which did GPU mine (3.7.2 I think it was), or use bfgminer which still does GPU mining.  Your choice.

[os2sam]

Just got the new version on cgminer (3.10.0) and I currently run 3 BFL jalapenos. I finally figured out how to get it to recognize the 3 jalapenos(old version I had used --disable-gpu, but now I have to use --usb :3), If there is another way like the old please let me know. Now my problem is that I can not figure out how to set the Intensity like I could in the old cgminer using --intensity d. Please help. Thanks in advance.

You can't set intensity because there's no GPU mining in 3.10.

So how can I mine with GPUs now? Is it just CPU?

CGMiner is ASIC and Bitcoin only from now on.

[Portender]

Just got the new version on cgminer (3.10.0) and I currently run 3 BFL jalapenos. I finally figured out how to get it to recognize the 3 jalapenos(old version I had used --disable-gpu, but now I have to use --usb :3), If there is another way like the old please let me know. Now my problem is that I can not figure out how to set the Intensity like I could in the old cgminer using --intensity d. Please help. Thanks in advance.

You can't set intensity because there's no GPU mining in 3.10.

So how can I mine with GPUs now? Is it just CPU?

CGMiner is ASIC and Bitcoin only from now on.

Thank you for the info. It seems I am getting a lot more HW errors now. Is there a way to stop that or at least not have so many? I get a lot very fast 

[Krak]

Thank you for the info. It seems I am getting a lot more HW errors now. Is there a way to stop that or at least not have so many? I get a lot very fast 

Did you restart the Jalapenos recently? I know my Jalapeno spews out all kinds of hardware errors if it's too warm when it starts up or whatever. First think you could try is unplugging the power cords for about 10 minutes and then plug 'em back in.

[doctormandrake]

Just got the new version on cgminer (3.10.0) and I currently run 3 BFL jalapenos. I finally figured out how to get it to recognize the 3 jalapenos(old version I had used --disable-gpu, but now I have to use --usb :3), If there is another way like the old please let me know. Now my problem is that I can not figure out how to set the Intensity like I could in the old cgminer using --intensity d. Please help. Thanks in advance.

You can't set intensity because there's no GPU mining in 3.10.

So how can I mine with GPUs now? Is it just CPU?

CGMiner is ASIC and Bitcoin only from now on.

asic and sha256 or asic and bitcoin only?

[kano]

...

asic and sha256 or asic and bitcoin only?

Altcoin discussion in here gets your post removed or deleted.

[CustomDesigned]

Just a note that I installed Fedora 18 on a Pogoplug (256MB armv5tel w/ 4 USB2.0 ports), and compiled cgminer-0.8.4 with the SRPM from Fedora on Intel - and it worked perfectly!  The pogoplug has now taken over mining chores with my 4 block erupters.  My modest block erupter + hub investment has now paid for itself after 8 weeks at current BTC prices.  I sent a small donation to celebrate.  (The pogoplug was no longer needed for its previous role as VPN concentrator.)

I would highly recommend the pogoplug for USB mining - except that Fedora no longer supports ARM with software floating point (i.e. all the kirkwood systems like pogoplug, guruplug, etc).  There are other linux distros that continue to support kirkwood, however.  I like for "plug" formfactor because there is no video hardware, or anything extraneous.  Just USB ports (and a serial port for debugging booting problems) and an ethernet port.  Once your system is loaded on a USB memory stick, just plug it in and away it goes.  I used a USB hard drive for compiling, since memory sticks are somewhat slow.

[iano128]

Hi guys, I just added a mini rig to my setup and have been getting intermittent errors to do with usb I think. I have linked some screenshots of the output cgminer is giving. I am using the latest version on windows 7 x64. I already had a single and 50 Block Erupters running but when I added the mini rig cgminer kept crashing so I took one of the usb hubs out and connected the mini rig straight to the motherboard this stopped the crashes but I am now seeing the attached errors. Any help would be great.

Btw the hubs are all usb 3 and there are 7 of them with 6 miners each.

http://imgur.com/a/fHR6b/embed

One USB connection still appears to be flaky and one of the subdevices appears to be flat out frying. I know of people opening them up and replacing hubs and/or cables to fix them.

So how would i go about finding the bad hub or device?

Unplug each while it's running and see which gets unplugged in cgminer.

Solved the issue by removing the shitty unpowered 14 port hub bfl use for their mini rig and replaced with two usb3 powered hubs with 4 connections going to each no more usb errors in cgminer and much more consistent hashing rate.

Cheers ckolivas

[erk]

I have a Ubuntu Linux server with all the current updates, running a variety of miners plugged into it on cgminer 3.10.0

I plugged a nanofury NF1 into a usb hub that has a few block erupters in it and the NF1 would only mine at just less than1GH/s.

I removed the block erupters and the NF1 started mining at full speed. Even if I add just one block erupter the NF1 instantly halves it's speed. The block erupter mines at full speed only the NF1 is effected, neither reports any errors that I can see.The power pack for the hub is 2.1Amps so it should be able to handle that, so I think it might be a conflict of some sort.

Erupters run at usb1.1 speed and protocol and perhaps are having some communication interaction making everything work in the same crap manner - depends greatly on how usb hubs manage different speed devices. Try them on separate hubs.

Turns out that 3.10.0 is crashing on the nanofury after a random period of time. Even on a separate linux box with nothing else connected. Same setup runs bfgminer fine.

[HellDiverUK]

Turns out that 3.10.0 is crashing on the nanofury after a random period of time. Even on a separate linux box with nothing else connected. Same setup runs bfgminer fine.

I'm seeing the same.  2xNanofury and 1xBitburner Fury.  cgminer 3.10.0 just quits at random intervals.  Running on Debian Wheezy on BeagleBone Black, and same issue on Debian Wheezy on PC.  cgminer runs for days on the same machine when not running the Nanofurys.

[ipoomyself]

bfgminer wont overclock antminer u1 to 2.2gh/s

it works at 2gh/s using freq 0981

however

when i use freq 0A81 it defaults to 1.6gh/s WTF?

is it because i used a letter and the program doth not recognise it?

currently using bfg 3.10.0 software and antminer 1.6 (overclock 2.2) hardware.


should i invest more money into this or is this just another long term ponzi pyramid scheme that will be the death of us all i nee d input

[jedimstr]

bfgminer wont overclock antminer u1 to 2.2gh/s

it works at 2gh/s using freq 0981

however

when i use freq 0A81 it defaults to 1.6gh/s WTF?

is it because i used a letter and the program doth not recognise it?

currently using bfg 3.10.0 software and antminer 1.6 (overclock 2.2) hardware.


should i invest more money into this or is this just another long term ponzi pyramid scheme that will be the death of us all i nee d input

Well first things first, maybe you should ask this in the BFGMiner thread instead of the CGMiner thread.

It's like walking into a Church and asking where the Satanic Ritual is being held tonight.  Or vice versa.

[-ck]

Turns out that 3.10.0 is crashing on the nanofury after a random period of time. Even on a separate linux box with nothing else connected.

I'm seeing the same.  2xNanofury and 1xBitburner Fury.  cgminer 3.10.0 just quits at random intervals.  Running on Debian Wheezy on BeagleBone Black, and same issue on Debian Wheezy on PC.  cgminer runs for days on the same machine when not running the Nanofurys.

You see this comment earlier: ?

There's a bug in the 3.10.0 release that crashes when a device is (effectively) unplugged that was fixed immediately after in git, so grab a git tarball from master or build from git.