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

[Fiyasko]

Well as i was on my way to update to 2.3.6, I felt the desire to remove my current running drivers, Because i was getting 60mh/s less with the newer version of cgminer, Knowing that this was Not cgminers fault, And that it was a fault of the whole SDK .bin install compile= performance dealio, I ran into an issue where i can nolonger install ANY display drivers

Please help me! https://bitcointalk.org/index.php?topic=78479

[-ck]

got it ... thank you very much ... didn't realize you had to disable the gpu to get the bfl to work ... guess i'll have to run two instances ...thanks again

Wait where did you hear that? That was never said, and you can run GPUs with BFL. Gigavps runs 14 BFL with 2 GPUs getting 13GH on one machine.

[bombo999]

epoch indicated in his post that i needed to disable the gpu functionality then manually select the com port of the bfl ... that worked and i'm now able to run one instance of cgminer for the gpu and a separate instance for the bfl with gpu disabled

[-ck]

epoch indicated in his post that i needed to disable the gpu functionality then manually select the com port of the bfl ... that worked and i'm now able to run one instance of cgminer for the gpu and a separate instance for the bfl with gpu disabled

No, it is not necessary to disable the GPU functionality, but you do need to specify the com ports.

[bombo999]

I don't know what to tell you ... it didn't work before, now it works with gpu disabled.  Is there a reason why bfl's are not auto detected like they are in ufasoft's miner?

[-ck]

I don't know what to tell you ... it didn't work before, now it works with gpu disabled.  Is there a reason why bfl's are not auto detected like they are in ufasoft's miner?

Darn now I got mixed up. BFL should be autodetected, it's Icarus that doesn't sorry. See Kano's post.

edit, here: https://bitcointalk.org/index.php?topic=28402.msg874680#msg874680

[bombo999]

the post you linked to indicates that autodetect for bfl only works in linux ... not windows .... as I indicated, I am running windows

[-ck]

the post you linked to indicates that autodetect for bfl only works in linux ... not windows .... as I indicated, I am running windows

Oh, I'll shut up then 
If there's no autodetect in the windows code it's because it hasn't been done yet.

[bombo999]

no worries ... i'm just happy to have it running ... thanks to epoch for the advice

[Luke-Jr]

I don't know what to tell you ... it didn't work before, now it works with gpu disabled.  Is there a reason why bfl's are not auto detected like they are in ufasoft's miner?

Ufasoft doesn't really autodetect, it just spams every serial port with a probe every few seconds. I'm working on a proper autodetect for Windows.

[jddebug]

I don't know what to tell you ... it didn't work before, now it works with gpu disabled.  Is there a reason why bfl's are not auto detected like they are in ufasoft's miner?

Ufasoft doesn't really autodetect, it just spams every serial port with a probe every few seconds. I'm working on a proper autodetect for Windows.

That would be fantastic.

Possible to detect if one has throttled and/or a way to know which one is which? I have a number of them and one is running a bit hot. I have no way of figuring out which one it is except removing them all and trying them one at a time.

[kano]

...
Edit: for auto detection of course ZTX is always auto
ICA doesn't ever do auto
BFL does auto only in linux and only when you specify -S auto - however it has 2 methods:
 1) where it looks in /dev/serial/by-id (which can sometimes only show 1 BFL on some linux versions if you have more than 1 BFL)
 2) by libudev checking the USB Model when libudev is compiled in

I added that on to the end of my post at the bottom of the last page, but I guess I was slow doing it
So there it is again

Edit:
I'll be getting a BFL soon (bought it today from someone else here in the forum)

I can see a clear path to doing proper auto-detection so I'll do that after I get it.
Basically use nelisky's code in ZTX to detect BFL's the same way.

If Mr annoying wants to do it before me - feel free to do it
I'm just not sure if all BFL identify the same way so will need some feedback in that area when I get to it.

Then that would also be a neat way to do pseudo-auto detection on Icarus
(same way but it could get false positives so will still need to do the quick 0.1s Hash test also)

[bombo999]

Hey Kano, why the name calling?

[kano]

Hey Kano, why the name calling?

New around here I guess?
He is annoying - very.
That's my polite name calling

From: Kano the cry baby (<- as you called me before )

[bombo999]

makes you look like an immature whining fool ... completely devalues anything technical that you have to add

[miscreanity]

makes you look like an immature whining fool ...

Maybe to the uninitiated. Stick around for a while and you'll see, but please refrain from discouraging my daily entertainment. Thank you

[DutchBrat]

makes you look like an immature whining fool ...

Maybe to the uninitiated. Stick around for a while and you'll see, but please refrain from discouraging my daily entertainment. Thank you

Kano & Luke-JR are like Statler & Waldorf (2 grumpy old men from the Muppet show).... I think they would get along very well IRL

[check_status]

/**FPGA's will not take over once I release my Zero-Point Energy Generator. The enrergy it produces will be free, but the device is gonna cost you.  

Someone suggested using phatk2 with 5800 and 5900 cards but when I designate '-k phatk2' cgminer said 'you can't do that'.
Using search on this thread I noticed ckolivas states cgminer automatically chooses which phatk kerenl to use, because there are several available I guess. Also, when I check the config file after creating it while running, it isn't obvious which phatk is being used, it just lists 'phatk'.

Do I use '--verbose -T' to check which phatk kernel is in use?

When starting from the commandline (Not -c), can I specify which specific phatk kernel to use instead of letting automatic choose?

Does it matter which SDK is in use to get the benefeits suggested for phatk2?

I'd like to reduce stales/DOA for p2pool, rejected shares and Longpolling (hardware errors are zero). Is this more a combination of engine/mem, gpu threads, intensity, vectors, and worksize rather than a specific kernel?

[-ck]

/**FPGA's will not take over once I release my Zero-Point Energy Generator. The enrergy it produces will be free, but the device is gonna cost you.  

Someone suggested using phatk2 with 5800 and 5900 cards but when I designate '-k phatk2' cgminer said 'you can't do that'.
Using search on this thread I noticed ckolivas states cgminer automatically chooses which phatk kerenl to use, because there are several available I guess. Also, when I check the config file after creating it while running, it isn't obvious which phatk is being used, it just lists 'phatk'.

Do I use '--verbose -T' to check which phatk kernel is in use?

When starting from the commandline (Not -c), can I specify which specific phatk kernel to use instead of letting automatic choose?

Does it matter which SDK is in use to get the benefeits suggested for phatk2?

I'd like to reduce stales/DOA for p2pool, rejected shares and Longpolling (hardware errors are zero). Is this more a combination of engine/mem, gpu threads, intensity, vectors, and worksize rather than a specific kernel?

There is only one phatk in cgminer and it's called -k phatk, and it's actually phatk2.2 as you would know it. If you do not specify anything, it is chosen by default on pretty much all 5X and 6X cards with any SDK before 2.6. If you have 5X cards, STICK TO AN OLDER SDK, 2.1, 2.4 or 2.5 and let it choose phatk. To do the best with p2pool, read the readme.

[kano]

... and if anyone didn't realise:
If you use the api command "devdetails" it will tell you which "Kernel" it is using and the "Model" for each gpu