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

[os2sam]

both GPU, run OpenCL benchmark, no problem.

Latest test:


I read Diablo Readme for GPU vector size, and diablo return opencl worksize 256, and apply it here.
I try use other kernel, seem mining no respond at all, like null?

this one on Catalyst 13.4, OpenCL 1.2

Uh, I think the "-k diakgcn" is a diagnostic kernel that doesn't actually submit any shares.

try using "-k phatk -v 2 -w 256"

[SleeperUnit]

both GPU, run OpenCL benchmark, no problem.

...

I read Diablo Readme for GPU vector size, and diablo return opencl worksize 256, and apply it here.
I try use other kernel, seem mining no respond at all, like null?

this one on Catalyst 13.4, OpenCL 1.2

Uh, I think the "-k diakgcn" is a diagnostic kernel that doesn't actually submit any shares.

try using "-k phatk -v 2 -w 256"

"diakgcn" is the Diablo GCN kernel, it is designed for GPUs built on GCN technology (Radeon HD7000 serries)

CG miner auto-selects the best kernel for your hardware and rarely gets it wrong so just use the default kernel and you'll be fine.

[Anime4000]

other kernel give cgminer crash,
both my Overclocked Series GPU can't mining, but, normal GPU can mining and cgminer work with Catalyst 13.4. Why?
because overclocked GPU remove BFI_INT from hardware? I did try disable BFI_INT on phoenix.

[os2sam]

"diakgcn" is the Diablo GCN kernel, it is designed for GPUs built on GCN technology (Radeon HD7000 serries)

CG miner auto-selects the best kernel for your hardware and rarely gets it wrong so just use the default kernel and you'll be fine.

Ah, OK.  At one time there was a diagnostic kernel probably started with diag* instead of diak*.  Thanks for the correction.
Sam

[-ck]

"diakgcn" is the Diablo GCN kernel, it is designed for GPUs built on GCN technology (Radeon HD7000 serries)

CG miner auto-selects the best kernel for your hardware and rarely gets it wrong so just use the default kernel and you'll be fine.

Ah, OK.  At one time there was a diagnostic kernel probably started with diag* instead of diak*.  Thanks for the correction.
Sam

diakgcn is the Diapolo Kernel for GCN. It has nothing to do with diablo and pretty much never outperformed any other kernel so it is never selected automatically by cgminer.

[Karin]

[problem solved]

[bernard75]

3.1.1 doesn't use the WinUSB driver for 'Icarus' devices - it uses the serial-USB driver on windows.
3.2* uses WinUSB that Zadig will install for you.

(Icarus devices are: Icarus, Lancelot, Asicminer USB and Cairnsmore1)

[Anime4000]

By the way, currently I have 4670 GPU, run PCI-E 1.1 x16 (32MH/s with 750MHz > 800MHz clock using cgminer).
So, if I move GPU to motherboard that capable PCI-E 2.0 x16, dose Hash rate will increase? i think not

[Miner-TE]

By the way, currently I have 4670 GPU, run PCI-E 1.1 x16 (32MH/s with 750MHz > 800MHz clock using cgminer).
So, if I move GPU to motherboard that capable PCI-E 2.0 x16, dose Hash rate will increase? i think not

You are correct,  It would not.  Bandwidth on the PCI bus does not help hash rate.

[os2sam]

By the way, currently I have 4670 GPU, run PCI-E 1.1 x16 (32MH/s with 750MHz > 800MHz clock using cgminer).
So, if I move GPU to motherboard that capable PCI-E 2.0 x16, dose Hash rate will increase? i think not

I was getting 35Mhs on my AGP 4670.  So I would expect you should be getting higher than that already.

But no changing the slot/MB won't help.

[kano]

By the way, currently I have 4670 GPU, run PCI-E 1.1 x16 (32MH/s with 750MHz > 800MHz clock using cgminer).
So, if I move GPU to motherboard that capable PCI-E 2.0 x16, dose Hash rate will increase? i think not

You are correct,  It would not.  Bandwidth on the PCI bus does not help hash rate.

For BTC sha256 yes.

[Loft]

I can't change the voltage across the config file. I have 2 7950 MSI and 2 7870 Gigabyte, but with the help of MSIAfterburner I can't go to change the voltage. Tried using a bat file to change нaпpяeниe avail. Version CGminer 3.1.1, 3.2.1, 3.3.0
 What I should do?

[xgtele]

I have  2 7970 GPU in my system and they are required a different GPU threads: -g 1 for the first card and -g2 for the second card.

How I can set it correctly in cgminer bat file? Settings like -g 1,2 does not work

[Krak]

I have  2 7970 GPU in my system and they are required a different GPU threads: -g 1 for the first card and -g2 for the second card.

How I can set it correctly in cgminer bat file? Settings like -g 1,2 does not work

The only way you can do that is to set the GPU that requires 1 thread to dynamic intensity (-I d).

[xgtele]

I have  2 7970 GPU in my system and they are required a different GPU threads: -g 1 for the first card and -g2 for the second card.

How I can set it correctly in cgminer bat file? Settings like -g 1,2 does not work

The only way you can do that is to set the GPU that requires 1 thread to dynamic intensity (-I d).

Hashing speed is lowered 10 times.

I can simply do custom GPU threads for each cards in GUIminer and it is based on cgminer, so it should be solution somewhere around..

[-ck]

I have  2 7970 GPU in my system and they are required a different GPU threads: -g 1 for the first card and -g2 for the second card.

How I can set it correctly in cgminer bat file? Settings like -g 1,2 does not work

The only way you can do that is to set the GPU that requires 1 thread to dynamic intensity (-I d).

Hashing speed is lowered 10 times.

I can simply do custom GPU threads for each cards in GUIminer and it is based on cgminer, so it should be solution somewhere around..

I have  2 7970 GPU in my system and they are required a different GPU threads: -g 1 for the first card and -g2 for the second card.

How I can set it correctly in cgminer bat file? Settings like -g 1,2 does not work

You cannot set separate thread counts without running 2 instances.

However you can set an intensity for dynamic as well, with gpu-dyninterval.

[Anime4000]

both GPU, run OpenCL benchmark, no problem.

this one on Catalyst 13.4, OpenCL 1.2

Try catalyst 13.1
Uninstall any drivers you have cleanly with driversweep, including the opencl installed and start again with what 13.1 installs. Then start with a freshly extracted cgminer or delete any .bin files you have in your cgminer directory.

I did uninstall driver, what AMD Installer did, they also uninstall motherboard driver, and restart, blue screen.
I go safe mode, sweep left over driver, reboot, blue screen, go safe mode again, remove driver manually on Device Manager,

now, install back everything, and OpenCL have problem,

https://fbcdn-sphotos-e-a.akamaihd.net/hphotos-ak-ash3/q71/10346_10201359330448163_818314584_n.jpg

cgminer still crash on start.

[Anime4000]

Update~
Remove and Reinstall for 2nd time, now it works on version 13.1

https://fbcdn-sphotos-c-a.akamaihd.net/hphotos-ak-ash4/q71/s720x720/1004584_10201359511492689_135703871_n.jpg

weird... some card can work on 13.4... hmmm...

[bitpop]

Just wanted to say, 331 doesn't display all devices especially when detected right after startup.

[tew]

I am interested in trying my hand at creating yet another FPGA cluster hasher, with each cluster connected via a single USB connection to the host (rather than 1 per FPGA).

I've looked at the Cairnsmore 1, Ztex, and Icarus drivers; each one has hard-coded some of the idiosyncrasies of those particular devices.  I'm wondering if there is something like a generic CGminer driver skeleton I could fill in / develop against.

Is there a simple block of code that easily links with CGminer, passes up the relevant info from the device chain (estimated duration of one hash-cycle iteration, number of hashes completed per cycle) to the main miner program on initialization, downloads base header data and range to be hashed against from the miner to the device with each getwork or stratum fetch, receives proof of work from the device to send to the mining pool, and sends an interrupt to the device when assigned work becomes invalid?

Given the proliferation of mining devices, there's almost a need for a "miner driver" specification just like the old "packet driver" specification back in the days of Win32s enabling Win3.11 to connect to the internet, so that the people creating the new mining devices would be responsible for driver creation, rather than the mining stack software creators.

Thanks,
 -Tom