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
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 156. (Read 5805527 times)
December 15, 2013, 11:46:54 AM
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
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
December 15, 2013, 11:20:45 AM
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
Edit: also tried again to use -d 1 or -d 2 but just nothing
December 15, 2013, 11:06:33 AM
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...
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
December 15, 2013, 10:45:53 AM
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...
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...
December 15, 2013, 10:44:01 AM
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?
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?
December 15, 2013, 10:29:38 AM
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?
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?
December 15, 2013, 09:47:48 AM
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
--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
December 15, 2013, 09:41:56 AM
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.
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.
December 15, 2013, 09:41:07 AM
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...?
December 15, 2013, 12:37:12 AM
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://bitcointalksearch.org/topic/m.3970326
To reproduce:
The output will repeatedly read:
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:
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!
https://bitcointalksearch.org/topic/m.3970326
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:
Quote
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)
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!
December 14, 2013, 02:43:19 PM
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
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
anyone capable could add a function to get your wallet details.
December 14, 2013, 02:30:34 PM
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 ?
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
December 13, 2013, 08:30:05 PM
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.
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://bitcointalksearch.org/topic/m.3956204
You may get away with just running CGMiner with sudo privileges to get it working for you.
December 13, 2013, 02:57:52 PM
anyway to use cgminer with blades yet?
December 13, 2013, 09:19:12 AM
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://bitcointalksearch.org/topic/m.3943685
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 Details on what I did here: https://bitcointalksearch.org/topic/m.3943685
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.
December 13, 2013, 07:31:01 AM
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://bitcointalksearch.org/topic/m.3943685
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.
Details on what I did here: https://bitcointalksearch.org/topic/m.3943685
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.
December 13, 2013, 01:03:30 AM
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.
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:
Quote
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
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.
December 13, 2013, 12:59:22 AM
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.
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:
Quote
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
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.
December 12, 2013, 11:39:40 PM
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.
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:
Quote
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
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
December 12, 2013, 11:28:42 PM
Since you're running BAMT, you may want to check out the latest Scrypt version of BAMT 1.2 that bee is working on (posts in reddit and Litecoin forums). He's updated the AMD Drivers for the new R9 cards.
Thanks, I'll give it a whirl.
Jump to: