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

[-ck]

OS: Mac OS X
Hardware: Bi•Fury ASIC

Has anyone successfully configured cgminer on Mac to see their Bi•Fury? If so, what did you do to get it recognized?

Thanks in advance.

Straight from README:

OSX:

On OSX, like Linux, no drivers need to be installed. However some devices
like the bitfury USB sticks automatically load a driver thinking they're a
modem and the driver needs to be unloaded for cgminer to work:

sudo kextunload -b com.apple.driver.AppleUSBCDC
sudo kextunload -b com.apple.driver.AppleUSBCDCACMData

Saw that and did it...without any luck. Was wondering first if anyone will actually confirm they are running a Bi•fury on mac successfully...otherwise I'll send it back.

Hrm those were the instructions for the bluefury. The bi*fury is something else. Not sure what driver it tries to install for those nor how to look it up on a mac etc.

[1638277805]

1638277805

[1638277805]

1638277805

[1638277805]

1638277805

[1638277805]

1638277805

[1638277805]

1638277805

[1638277805]

1638277805

[jedimstr]

I couldn't get my Bi*Fury on the Mac working either, and the only way to get it working for me on one of my Raspberry Pi's/Minepeon was to edit the /etc/udev/rules.d/01-miner.rules with sudo privileges and add an entry for the Bi*Fury with data from lsusb.

Details on what I did here: https://bitcointalk.org/index.php?topic=309918.msg3943685#msg3943685

The errors looked like a permissions issue in trying to access the device on both the Pi and the Mac and I didn't try running CGMiner under sudo on the Mac.  That could help.

[-ck]

I couldn't get my Bi*Fury on the Mac working either, and the only way to get it working for me on one of my Raspberry Pi's/Minepeon was to edit the /etc/udev/rules.d/01-miner.rules with sudo privileges and add an entry for the Bi*Fury with data from lsusb.

Details on what I did here: https://bitcointalk.org/index.php?topic=309918.msg3943685#msg3943685

The errors looked like a permissions issue in trying to access the device on both the Pi and the Mac and I didn't try running CGMiner under sudo on the Mac.  That could help.

...there's a udev rules file included with cgminer already

[xzempt]

anyway to use cgminer with blades yet?   

[jedimstr]

OS: Mac OS X
Hardware: Bi•Fury ASIC

Has anyone successfully configured cgminer on Mac to see their Bi•Fury? If so, what did you do to get it recognized?

Thanks in advance.

Got it working finally with a Mac... switched from using a RPi...but I didn't use CGMiner to get it working with all the other devices I had on the Mac.
https://bitcointalk.org/index.php?topic=309918.msg3956204#msg3956204

You may get away with just running CGMiner with sudo privileges to get it working for you.

[cunixion]

How to disable Icarus while using Blue furys as had to use blues in cgminer and erupters in bfgminer.

Is their any way to get both working in cgminer ?

It must be a bug if you compiled with --enable-icarus --enable-bitfury and are unable to use both

[cunixion]

http://ck.kolivas.org/apps/cgminer/cgminer-3.8.5-windows.zip
website down 

maybe add you could add a mirror here docs.google.com
and please include to checksum just to make sure it's not modified after it got upload

Or just stick it on a Google Drive (or SkyDrive), set it to share to everyone, job done.

Bad idea.  I wouldn't trust an app placed on a google or skydrive.

M

why?

anyone capable could add a function to get your wallet details.

[nwoolls]

Hi there. I am here to report what looks to be a bug in cgminer. This bug manifests itself if you run cgminer pointed at the stratum port of the bfgminer proxy. This has been reported by numerous users, usually trying to point their KnC miner at the bfgminer proxy:

https://bitcointalk.org/index.php?topic=370365.msg3970326#msg3970326

To reproduce:

Code:

bfgminer --stratum-port 4444 -o some.miningpool.com -u worker -p password
cgminer --o 127.0.0.1:4444 -u doesnt -p matter

The output will repeatedly read:

Code:

Rejected a18df423 Diff 2/1 GPU 1  (H-not-zero)

I worked with Luke to debug both bfgminer and cgminer and he was able to make a few changes in the cgminer source to get accepted shares. Here is a summary of what he had to say:

cgminer is broken if nonce2_size is anything other than 4 (32-bit)
A proxy must always reduce the nonce2_size from the upstream server
BFGMiner always uses 2 (16-bit)
cgminer is memcpy-ing nonce2 with a fixed 32-bit size, even if nonce2_size is smaller
If you were to just memcpy the nonce2 with an adjusted size, it will fix little endian but break on big endian (to confirm the bug)

I'd really like to keep this civil and hopefully get a legitimate look at this bug as I am getting numerous users reporting it as I mentioned before. Thanks Con!

[firelizard]

hi guys, im new at the sport and i need some info, my screen is connected to an onboard graphic card and i have an r9 290 connected on the pcie slot, my question is how can i make the cgminer to target and mine only with the r9 card? i guess it must be something like --device 1 or --gpu 1 or...?

[litepool.ru]

Hello. My question is: hot to change cgminer layout?

On the 1 screen I can see devices, temperature, accepts/rejects.

OS: BAMT

On the 2 screen there's no such information.

OS: Debian squeeze

As I know, such layout must be if key -T used when starting cgminer.
But it's started just with ./cgminer -o pool -u user -p pass

So both cgminer's on different systems launched the same way but I have different layout. The only differense is: different cgminer versions and devices. On 1 screen there's GPU and on the 2 screen is BAJ.

[os2sam]

hi guys, im new at the sport and i need some info, my screen is connected to an onboard graphic card and i have an r9 290 connected on the pcie slot, my question is how can i make the cgminer to target and mine only with the r9 card? i guess it must be something like --device 1 or --gpu 1 or...?

--device|-d <arg>   Select device to use, one value, range and/or comma separated (e.g. 0-2,4) default: all
--remove-disabled   Remove disabled devices entirely, as if they didn't exist

So if you don't want to use device 0 and do use device 1 use:

-d 0 --remove-disabled

[firelizard]

by adding   -d 0 --remove-disabled   just makes the cg miner to intantly close, like when it has en error in its command line...

my whole bat now is

cgminer --scrypt -o wk3.botpool.net:3599 -u user -p pass -d 0 --remove-disabled --shaders 2560 --thread-concurrency 24550 --intensity 20 --worksize 512 -g 1 --gpu-fan 85

whats wrong with it?

[os2sam]

by adding   -d 0 --remove-disabled   just makes the cg miner to intantly close, like when it has en error in its command line...

my whole bat now is

cgminer --scrypt -o wk3.botpool.net:3599 -u user -p pass -d 0 --remove-disabled --shaders 2560 --thread-concurrency 24550 --intensity 20 --worksize 512 -g 1 --gpu-fan 85

whats wrong with it?

First make sure what CGMiner identifies your GPU's as.  I just guessed at the "0".  Then make the proper -d x --remove-disabled immediately after cgminer.exe and before everything else.

It took me a little trial and error when I used it, way back when.

Edit: You are using CGMiner 3.7.2 or earlier? Right?

[firelizard]

and how do i see which gpus it identifies?

no im using a 2.11 ver, does it actually matter?

edit: ok updated to 3.8.5 and the disable command is now just after cgminer.exe in the line, also used -d 1 and -d 2 but nothing changed...

[mdude77]

and how do i see which gpus it identifies?

no im using a 2.11 ver, does it actually matter?

edit: ok updated to 3.8.5 and the disable command is now just after cgminer.exe in the line, also used -d 1 and -d 2 but nothing changed...

You want 2.7.2 for scrypt mining.  3.8.5 doesn't have GPU, and hence scrypt support.

M

[firelizard]

ok then im back to my 2.11 ver that used to work just fine, i set up the command line as it should be and now before cgminer instantly closes i can see an error popping in it: command line options set a device that doesnt exist

Edit: also tried again to use -d 1 or -d 2 but just nothing

[Aurum]

1. I'm trying to get an MSI Z87-G45 mb running Win8.1 to mine with 7 cards but it only mines with 5.  Windows Device Manager recognizes all 7 cards.  Any ideas on how I can get cards 6 and 7 to mine  

2. I cannot get a single 5970 to mine on that setup. I've tried Catalyst 12.8, 13.1 and 13.9 with all the driver stripping steps in between.  Is there a fundamental reason a 5970 will not mine under Windows 8.1  

[os2sam]

and how do i see which gpus it identifies?

--ndevs|-n          Enumerate number of detected GPUs and exit

There are readme and GPU-readme files with the software, among others.

Those have allot of good info in them.

[dadach]

i guess my previous post got deleted, but i cannot overemphasize how much of a bullshit this program is when you have two different cards

to change settings of GPU 0, you have to modify the settings of GPU 1, and god knows what else gets turned around selectively...stay away from it if you are running different cards

[HellDiverUK]

1. I'm trying to get an MSI Z87-G45 mb running Win8.1 to mine with 7 cards but it only mines with 5.  Windows Device Manager recognizes all 7 cards.  Any ideas on how I can get cards 6 and 7 to mine  

Use Linux, Windows doesn't support 7 GPUs.