Bitcoin Forum
February 18, 2019, 03:35:36 PM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 [497] 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 ... 844 »
  Print  
Author Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1  (Read 5776449 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic. (2 posts by 2 users deleted.)
unvoid
Hero Member
*****
Offline Offline

Activity: 535
Merit: 500



View Profile
May 06, 2013, 11:17:40 PM
 #9921

I think I might found a bug.

Can devs look at this thread?

https://bitcointalk.org/index.php?topic=197215.0

BTC: 1CMgHWx4wkAaAy2FfeCyPdedUExmhGhfi5
XEL: XEL-HCM8-KB6E-YFLK-8BWMF
1550504136
Hero Member
*
Offline Offline

Posts: 1550504136

View Profile Personal Message (Offline)

Ignore
1550504136
Reply with quote  #2

1550504136
Report to moderator
Your Bitcoin transactions
The Ultimate Bitcoin mixer
made truly anonymous.
with an advanced technology.
Mix coins
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2786
Merit: 1154


Ruu \o/


View Profile WWW
May 06, 2013, 11:38:58 PM
 #9922

I think I might found a bug.

Can devs look at this thread?

https://bitcointalk.org/index.php?topic=197215.0
Try disabling the usb hotplug scanning. Various versions of windows can suck dicks that way.

--hotplug 0

Developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org, 1% Fee Solo mining at solo.ckpool.org
-ck
dbabo
Newbie
*
Offline Offline

Activity: 41
Merit: 0


View Profile
May 07, 2013, 01:56:33 AM
 #9923

<cut off>
well, the intensity was set a -1 on the little machine that i am playing with. moving it to 5 raised the hash rate from 6Mhash to 10Mhash. moving it to 6 looked like it  caused the rate to drop a little, so 5 it is.

10Mhash/s? how do you get the Mhash ? ty

Did i mislabel? isn't Mhs, Mega Hashes? I've only been into this for about 2 weeks so it would be easy for me to mispeak.
eee, stop and reload..
you are talking litecoin? you are talking GPU mining?
may i ask how a tiny rig gives you Mega Hash/s? the top listed here is 7970(x2) in low megashas/s...
// i'm obviously missing something obvious. sorry about it.


heh, we are talking bitcoin GPU mining. If a good  video card can give 600+Mhs ( like a 7850), then a small rig churning 10Mhs isn't all that impressive. I'm not sure what you consider "low megahashes". everything is relative.
AHA! that was what i was missing. Yup makes total sense. TY for clarification. Since i'm looking into litecoin mining, then (apparently) the whole world can only talk about that %) only.Smiley
Tesla71
Sr. Member
****
Offline Offline

Activity: 302
Merit: 252



View Profile
May 07, 2013, 12:04:41 PM
 #9924

still running 2.10.5, with 3.1.0 I am getting only HW errors at the same setting as with 2.10.5. If I set intensity down to alevel where I am getting no HW errros, Hasrate got very low.
Any ideas?

Example: C:\coin\cgminer-2.10.5-win32\cgminer --scrypt -o "http://mine.pool-x.eu:8080" -u xx.x -p x -g 1 -I 19,19,19 --worksize 256 --auto-fan --temp-target 75

Cards are 5970 and 5870
PatMan
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1000


Watch out for the "Neg-Rep-Dogie-Police".....


View Profile WWW
May 07, 2013, 12:09:50 PM
 #9925

I think I might found a bug.

Can devs look at this thread?

https://bitcointalk.org/index.php?topic=197215.0
Try disabling the usb hotplug scanning. Various versions of windows can suck dicks that way.

--hotplug 0


 Cheesy Cheesy Cheesy Cheesy

I remember I was having usb problems, that --hotplug 0 comment cured it.

"When one person is deluded it is called insanity - when many people are deluded it is called religion" - Robert M. Pirsig.  I don't want your coins, I want change.
Amazon UK BTC payment service - https://bitcointalk.org/index.php?topic=301229.0 - with FREE delivery!
http://www.ae911truth.org/ - http://rethink911.org/ - http://rememberbuilding7.org/
unvoid
Hero Member
*****
Offline Offline

Activity: 535
Merit: 500



View Profile
May 07, 2013, 12:17:24 PM
 #9926

I think I might found a bug.

Can devs look at this thread?

https://bitcointalk.org/index.php?topic=197215.0
Try disabling the usb hotplug scanning. Various versions of windows can suck dicks that way.

--hotplug 0


works like a charm! Thank you.

BTC: 1CMgHWx4wkAaAy2FfeCyPdedUExmhGhfi5
XEL: XEL-HCM8-KB6E-YFLK-8BWMF
Beans
Hero Member
*****
Offline Offline

Activity: 517
Merit: 500



View Profile
May 07, 2013, 12:22:43 PM
 #9927

The past few weeks it seems like I always have a miner that is reporting all shares being rejected. Seems to only happen when I'm using slush's proxy. The proxy reports that share was above target.. Soon as I restart cgminer on the effected pc it goes away. I updated to the newest proxy and my miners are just using windows. Anyone know what can cause this?



     ▄██    ▐███████▄▄▄       ▄▄█████▄▄      ▄██▄      ▐██▄    ▒▓▓▄      ▄▓▓▒
     ███    ▐██▌▀▀▀▀▀███▄    ███▀▀▀▀▀███▄    ████▄     ▐██▌  ▐▓▄ ▀▓▓▄  ▄▓▓▀ ▄▓▌
     ███    ▐██▌      ███   ███▌      ███▌   ██████    ▐██▌   ▀▓▓▄ ▀▓▓▓▓▀ ▄▓▓▀
     ███    ▐██▌    ▄████  ▐███▌      ▐██▌   ███ ███▄  ▐██▌     ▀▓▓▄ ▀▀ ▄▓▓▀
     ███    ▐█████████▀▀   ▐███▌      ▐██▌   ███  ▀███ ▐██▌      ▓▓▓    ▓▓▓
     ███    ▐██▌   ▀███     ███▌      ███▌   ███    ██████▌   ▄▓▓▀ ▄▓▓▓▓▄ ▓▓▓▄
     ███    ▐██▌     ███    ▀███▄▄▄▄▄████    ███     ▀████▌  ▐▓▀ ▄▓▓▀  ▀▓▓▄ ▀▓▌
     ███    ▐██▌      ███     ▀▀██████▀▀     ███       ███▌    ▄▓▓▀      ▀▓▓▄
                  ▄▄▄█████▄▄▄▄
             ▄▄█▓▓▓▓▓█▀▀▀▀█▓▓▓▓▓█▄
           ▄▓▓▓█▀▀            ▀▀█▓▓█▄
         ▓▓▓█▀                    ▀▓▓█▄
       ▄▓▓▓▀                        ▀▓▓█
      ▄▓▓█                            █▓▓
      ▓▓▓                    ▄██▄     ▐▓▓█
     ▓▓▓                   ▄█▓▓▀       ▐▓▓▌
     ▓▓▓                 ▄█▓▓▀          ▓▓▓
     ▓▓▓       ▓▓▓▄    ▓▓▓▓▀            ▓▓▓
     ▓▓▓        ▀▓▓▓▄█▓▓▓▀             ▐▓▓▌
     ▀▓▓▓         ▀█▓▓█▀               █▓▓
      ▓▓▓▄                            ▓▓▓▌
       ▓▓▓█                         ▄█▓▓▀
        ▀▓▓█▄                     ▄▓▓▓█▀
          ▀▓▓▓█▄               ▄▄█▓▓█▀
            ▀▀█▓▓▓█▄▄▄▄▄▄▄▄▄▄█▓▓▓█▀
                ▀▀██▓▓▓▓▓▓▓███▀▀
kano
Legendary
*
Online Online

Activity: 2730
Merit: 1103


Linux since 1997 RedHat 4


View Profile
May 07, 2013, 12:30:44 PM
 #9928

It seems the ASICMINER 300MH/s USB devices are Icarus look-a-likes (as far as cgminer sees them) and apparently I'll be sent one soon.
These things: https://bitcointalk.org/index.php?topic=195004.0

So ... this means I should get around to converting the last old driver to direct USB - the Icarus driver - so that then all the old drivers are direct USB.

Could anyone with a Lancelot or a Cairnsmore1 post a linux "sudo lsusb -v" of either of them for me please?
Thus when I have the code ready I can simply add the small definition required to detect each of them also.
Would also be good if (in a week or two when it's done) someone with each of the boards would be around to test the modified code.
I may also require a little more help with each if the USB chips are unusual in them or different to the Icarus (to get the correct initialisation commands) since I don't have either of those cards ...
Thanks to any who can help with this.

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2786
Merit: 1154


Ruu \o/


View Profile WWW
May 07, 2013, 12:41:55 PM
 #9929

The past few weeks it seems like I always have a miner that is reporting all shares being rejected. Seems to only happen when I'm using slush's proxy. The proxy reports that share was above target.. Soon as I restart cgminer on the effected pc it goes away. I updated to the newest proxy and my miners are just using windows. Anyone know what can cause this?
Blame the proxy? There are no reports like this for anyone pool mining directly.

Developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org, 1% Fee Solo mining at solo.ckpool.org
-ck
gyverlb
Hero Member
*****
Offline Offline

Activity: 896
Merit: 1000



View Profile
May 07, 2013, 03:03:28 PM
 #9930

It seems the ASICMINER 300MH/s USB devices are Icarus look-a-likes (as far as cgminer sees them) and apparently I'll be sent one soon.
These things: https://bitcointalk.org/index.php?topic=195004.0

So ... this means I should get around to converting the last old driver to direct USB - the Icarus driver - so that then all the old drivers are direct USB.

Could anyone with a Lancelot or a Cairnsmore1 post a linux "sudo lsusb -v" of either of them for me please?
Thus when I have the code ready I can simply add the small definition required to detect each of them also.
Would also be good if (in a week or two when it's done) someone with each of the boards would be around to test the modified code.
I may also require a little more help with each if the USB chips are unusual in them or different to the Icarus (to get the correct initialisation commands) since I don't have either of those cards ...
Thanks to any who can help with this.

For a Cairnsmore1:
Code:
Device Descriptor: 
  bLength                18 
  bDescriptorType         1 
  bcdUSB               2.00 
  bDeviceClass            0 (Defined at Interface level) 
  bDeviceSubClass         0   
  bDeviceProtocol         0   
  bMaxPacketSize0        64 
  idVendor           0x0403 Future Technology Devices International, Ltd 
  idProduct          0x8350   
  bcdDevice            8.00 
  iManufacturer           1 FTDI 
  iProduct                2 Cairnsmore1 
  iSerial                 3 FTVIUPKW 
  bNumConfigurations      1 
  Configuration Descriptor: 
    bLength                 9 
    bDescriptorType         2 
    wTotalLength          101 
    bNumInterfaces          4 
    bConfigurationValue     1 
    iConfiguration          0   
    bmAttributes         0x80 
      (Bus Powered) 
    MaxPower              100mA 
    Interface Descriptor: 
      bLength                 9 
      bDescriptorType         4 
      bInterfaceNumber        0 
      bAlternateSetting       0 
      bNumEndpoints           2 
      bInterfaceClass       255 Vendor Specific Class 
      bInterfaceSubClass    255 Vendor Specific Subclass 
      bInterfaceProtocol    255 Vendor Specific Protocol 
      iInterface              2 Cairnsmore1 
      Endpoint Descriptor: 
        bLength                 7 
        bDescriptorType         5 
        bEndpointAddress     0x81  EP 1 IN 
        bmAttributes            2 
          Transfer Type            Bulk 
          Synch Type               None 
          Usage Type               Data 
        wMaxPacketSize     0x0200  1x 512 bytes 
        bInterval               0 
      Endpoint Descriptor: 
        bLength                 7 
        bDescriptorType         5 
        bEndpointAddress     0x02  EP 2 OUT 
        bmAttributes            2 
          Transfer Type            Bulk 
          Synch Type               None 
          Usage Type               Data 
        wMaxPacketSize     0x0200  1x 512 bytes 
        bInterval               0 
    Interface Descriptor:
      bLength                 9 
      bDescriptorType         4 
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2 Cairnsmore1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4 
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2 Cairnsmore1
      Endpoint Descriptor:
        bLength                 7 
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7 
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2 Cairnsmore1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x87  EP 7 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x08  EP 8 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)

You might want to check for the code supporting dynamic clocking for Cairnsmore1 in bfgminer or the Modular-Python-Bitcoin-Miner. Cairnsmore1 with the dynamic clock firmware (maybe the most used out there) defaults at 150MHz although most of them can run between 210 and 220MHz (bfgminer limits it to 210 Sad ). You probably don't want to allow more than 230MHz in the code to protect the hardware and might want to have a lower configurable max with a warning in the FPGA-README.

Cairnsmore1 have USB stability problems (seems really picky about the voltage stability from what I could understand): occasionally they disappear from the USB chain to reappear moments later (I have 2 here one does that less than once per week, the other several times per day).
bfgminer tries repeatedly to reopen the dev file (probably similar/same code that is in cgminer) until it reappears, MPBM regularly polls the USB chain for hotplugging new devices so it doesn't have any specific code to circumvent that.

bfgminer doesn't work correctly on p2pool with Cairnsmore1 (doesn't seem to restart work when asked to) and gets less hashes out of my 4xIcarus (compared to both cgminer and MPBM), so I use ModularPythonBitcoinMiner for all my FPGAs currently.

I'll pledge 1BTC for dynamic clocking support and the ability to reactivate a board that disappear and reappear (I probably won't get much out of my 2x Cairnsmore1, but it would simplify all my scripts if I could only use cgminer for all my rigs).

P2pool tuning guide
Trade BTC for €/$ at bitcoin.de (referral), it's cheaper and faster (acts as escrow and lets the buyers do bank transfers).
Tip: 17bdPfKXXvr7zETKRkPG14dEjfgBt5k2dd
CumpsD
Sr. Member
****
Offline Offline

Activity: 476
Merit: 250


View Profile
May 07, 2013, 03:39:25 PM
 #9931

Any possibility of integrating the work of CUDAMiner into cgminer?

https://bitcointalk.org/index.php?topic=167229.0

He managed to get nVidia cards to an "acceptable" (not as sucking as before) speed on scrypt mining.

It would be nice to have the same benefit in the cgminer architecture (since cgminer has a lot of extra features)
os2sam
Legendary
*
Offline Offline

Activity: 2562
Merit: 1003


Think for yourself


View Profile
May 07, 2013, 04:03:32 PM
 #9932

Any possibility of integrating the work of CUDAMiner into cgminer?

https://bitcointalk.org/index.php?topic=167229.0

He managed to get nVidia cards to an "acceptable" (not as sucking as before) speed on scrypt mining.

It would be nice to have the same benefit in the cgminer architecture (since cgminer has a lot of extra features)

I think ckolivas said he would do it for donations.

A donation that starts at 1000 BTC and goes up from there, that is.

Here's the context.

https://bitcointalk.org/index.php?topic=28402.msg1399226#msg1399226

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
reb0rn21
Legendary
*
Offline Offline

Activity: 1582
Merit: 1000


View Profile
May 07, 2013, 06:43:01 PM
 #9933

I have MSI 7950 TF3 OC, gpu/memory/fan setting are working, but now GPU voltage, it still stay at default, I am trying to set
"gpu-vddc" : "1.013"

Have to use afterburner to set it right
lastest cgminer 3.1.0, windows 7 64bit, catalist 13.5 beta

Bitrated user: reb0rn.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2786
Merit: 1154


Ruu \o/


View Profile WWW
May 07, 2013, 08:35:44 PM
 #9934

Any possibility of integrating the work of CUDAMiner into cgminer?

https://bitcointalk.org/index.php?topic=167229.0

He managed to get nVidia cards to an "acceptable" (not as sucking as before) speed on scrypt mining.

It would be nice to have the same benefit in the cgminer architecture (since cgminer has a lot of extra features)

I think ckolivas said he would do it for donations.

A donation that starts at 1000 BTC and goes up from there, that is.

Here's the context.

https://bitcointalk.org/index.php?topic=28402.msg1399226#msg1399226
That's what's known as the "I don't want to do it price". I have done cross platform code in CUDA before so I know what's involved. Plus you still pay more in electricity than you earn in coins mining with Nvidia GPUs, so it's a less extreme version of what happens with CPU mining. I'm sorry but cgminer need not support everything.

Developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org, 1% Fee Solo mining at solo.ckpool.org
-ck
crazyates
Legendary
*
Offline Offline

Activity: 952
Merit: 1000



View Profile
May 07, 2013, 09:17:08 PM
 #9935

That's what's known as the "I don't want to do it price". I have done cross platform code in CUDA before so I know what's involved. Plus you still pay more in electricity than you earn in coins mining with Nvidia GPUs, so it's a less extreme version of what happens with CPU mining.
I'm totally for keeping CGMiner as simple as possible. I actually wonder if one day you will drop GPU support for strictly ASIC support. However, the higher performance of native cuda seems to be pushing the cards into the realm of slightly profitable. A 580 seems to push 280KH/s, which is about $1.25/day profit.

Tips? 1crazy8pMqgwJ7tX7ZPZmyPwFbc6xZKM9
Previous Trade History - Sale Thread
bitpop
Legendary
*
Offline Offline

Activity: 2436
Merit: 1045


https://keybase.io/bitpop


View Profile WWW
May 07, 2013, 09:27:59 PM
 #9936

Maybe if cudaminer supported Bitcoin but no so fuq them

Reputation  |  PGP  |  DigitalOcean  |  TorGuard  |  Ethereum Classic
Bitcoin: 3DSh6AnmvBpDJFUz2mnLirMLmTMcFs9nDm
Bitmessage: BM-2cXN9j8NFT2n1FxDVQ6HQq4D4MZuuaBFyb
kano
Legendary
*
Online Online

Activity: 2730
Merit: 1103


Linux since 1997 RedHat 4


View Profile
May 07, 2013, 09:31:33 PM
 #9937

It seems the ASICMINER 300MH/s USB devices are Icarus look-a-likes (as far as cgminer sees them) and apparently I'll be sent one soon.
These things: https://bitcointalk.org/index.php?topic=195004.0

So ... this means I should get around to converting the last old driver to direct USB - the Icarus driver - so that then all the old drivers are direct USB.

Could anyone with a Lancelot or a Cairnsmore1 post a linux "sudo lsusb -v" of either of them for me please?
Thus when I have the code ready I can simply add the small definition required to detect each of them also.
Would also be good if (in a week or two when it's done) someone with each of the boards would be around to test the modified code.
I may also require a little more help with each if the USB chips are unusual in them or different to the Icarus (to get the correct initialisation commands) since I don't have either of those cards ...
Thanks to any who can help with this.

For a Cairnsmore1:
Code:
Device Descriptor: 
  bLength                18 
  bDescriptorType         1 
  bcdUSB               2.00 
  bDeviceClass            0 (Defined at Interface level) 
  bDeviceSubClass         0   
  bDeviceProtocol         0   
  bMaxPacketSize0        64 
  idVendor           0x0403 Future Technology Devices International, Ltd 
  idProduct          0x8350   
  bcdDevice            8.00 
  iManufacturer           1 FTDI 
  iProduct                2 Cairnsmore1 
  iSerial                 3 FTVIUPKW 
  bNumConfigurations      1 
  Configuration Descriptor: 
    bLength                 9 
    bDescriptorType         2 
    wTotalLength          101 
    bNumInterfaces          4 
    bConfigurationValue     1 
    iConfiguration          0   
    bmAttributes         0x80 
      (Bus Powered) 
    MaxPower              100mA 
    Interface Descriptor: 
      bLength                 9 
      bDescriptorType         4 
      bInterfaceNumber        0 
      bAlternateSetting       0 
      bNumEndpoints           2 
      bInterfaceClass       255 Vendor Specific Class 
      bInterfaceSubClass    255 Vendor Specific Subclass 
      bInterfaceProtocol    255 Vendor Specific Protocol 
      iInterface              2 Cairnsmore1 
      Endpoint Descriptor: 
        bLength                 7 
        bDescriptorType         5 
        bEndpointAddress     0x81  EP 1 IN 
        bmAttributes            2 
          Transfer Type            Bulk 
          Synch Type               None 
          Usage Type               Data 
        wMaxPacketSize     0x0200  1x 512 bytes 
        bInterval               0 
      Endpoint Descriptor: 
        bLength                 7 
        bDescriptorType         5 
        bEndpointAddress     0x02  EP 2 OUT 
        bmAttributes            2 
          Transfer Type            Bulk 
          Synch Type               None 
          Usage Type               Data 
        wMaxPacketSize     0x0200  1x 512 bytes 
        bInterval               0 
    Interface Descriptor:
      bLength                 9 
      bDescriptorType         4 
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2 Cairnsmore1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4 
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2 Cairnsmore1
      Endpoint Descriptor:
        bLength                 7 
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7 
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2 Cairnsmore1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x87  EP 7 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x08  EP 8 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)

You might want to check for the code supporting dynamic clocking for Cairnsmore1 in bfgminer or the Modular-Python-Bitcoin-Miner. Cairnsmore1 with the dynamic clock firmware (maybe the most used out there) defaults at 150MHz although most of them can run between 210 and 220MHz (bfgminer limits it to 210 Sad ). You probably don't want to allow more than 230MHz in the code to protect the hardware and might want to have a lower configurable max with a warning in the FPGA-README.

Cairnsmore1 have USB stability problems (seems really picky about the voltage stability from what I could understand): occasionally they disappear from the USB chain to reappear moments later (I have 2 here one does that less than once per week, the other several times per day).
bfgminer tries repeatedly to reopen the dev file (probably similar/same code that is in cgminer) until it reappears, MPBM regularly polls the USB chain for hotplugging new devices so it doesn't have any specific code to circumvent that.

bfgminer doesn't work correctly on p2pool with Cairnsmore1 (doesn't seem to restart work when asked to) and gets less hashes out of my 4xIcarus (compared to both cgminer and MPBM), so I use ModularPythonBitcoinMiner for all my FPGAs currently.

I'll pledge 1BTC for dynamic clocking support and the ability to reactivate a board that disappear and reappear (I probably won't get much out of my 2x Cairnsmore1, but it would simplify all my scripts if I could only use cgminer for all my rigs).
Thanks for the lsusb - that makes the device identification part easy to get right Smiley

FTDI with: idProduct 0x8350
That's gonna mean that the initialisation code is probably gonna need some help from you to get the correct settings.

Heh I have never gone near changing the clock on the Cairnsmore1 coz I don't have one.

I have an MMQ and thus did end up writing my own clocking for it - that took quite a bit of testing to get it where it is now where it keeps the HW error % under 1% and seems to handle bad environments pretty well also (but not bad hardware - nothing you can really do with that Tongue)
The MMQ code was pretty much a complete rewrite anyway coz it didn't work and the clocking/timing code in it was pitiful - the devices can't be stopped without effectively wiping the bitstream. cgminer is the only one that actually waits for the work to finish and allows it to go idle when it overheats.

Anyone else willing to throw more BTC at me to add clocking? Smiley
(or has anyone yet given up of their CM1's and wanna give me one Tongue)
Getting someone else to test is a painful way to develop code ... and no I wont copy the code from the clone even though it was built on top of my own code ... all that timing code in icarus to allow different performance devices and different FPGA counts was written completely by me (but not the clock change code)

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2786
Merit: 1154


Ruu \o/


View Profile WWW
May 07, 2013, 09:33:39 PM
 #9938

I actually wonder if one day you will drop GPU support for strictly ASIC support.
Yes well I'd like to but some crazy nut decided to code up scrypt support for cgminer for a fee he thought was "I don't want to do it" price, and that will keep GPU mining alive in cgminer. That's why I've raised my "I don't want to do it" price. I'm quite sure nvidia miners can't afford that fee. That and the ASIC hardware is far from being "available" just yet...  Roll Eyes

Developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org, 1% Fee Solo mining at solo.ckpool.org
-ck
CumpsD
Sr. Member
****
Offline Offline

Activity: 476
Merit: 250


View Profile
May 07, 2013, 09:48:18 PM
 #9939

No problem Smiley

I'll stick to cudaminer with this nvidia card, and keep the ati's on cgminer
FiatKiller
Sr. Member
****
Offline Offline

Activity: 378
Merit: 250


View Profile
May 07, 2013, 10:48:11 PM
 #9940

I actually wonder if one day you will drop GPU support for strictly ASIC support.
Yes well I'd like to but some crazy nut decided to code up scrypt support for cgminer for a fee he thought was "I don't want to do it" price, and that will keep GPU mining alive in cgminer. That's why I've raised my "I don't want to do it" price. I'm quite sure nvidia miners can't afford that fee. That and the ASIC hardware is far from being "available" just yet...  Roll Eyes

How much would it cost to have a flashing "Generating $1000 per hour." at the top just to fool the wives?  lol

LTC: LdxgJQLUdr8hZ79BV5AYbxkBUdaXctXAPi
MoonCoin Gambling: https://coin-horse.com/MON/
Pages: « 1 ... 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 [497] 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 ... 844 »
  Print  
 
Jump to:  

Bitcointalk.org is not available or authorized for sale. Do not believe any fake listings.
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!