Author

Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 347. (Read 5806015 times)

hero member
Activity: 896
Merit: 1000
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://bitcointalksearch.org/topic/announcement-block-erupter-usb-195004

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).
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
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.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
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://bitcointalksearch.org/topic/announcement-block-erupter-usb-195004

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.
hero member
Activity: 518
Merit: 500
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?
hero member
Activity: 535
Merit: 500
I think I might found a bug.

Can devs look at this thread?

https://bitcointalksearch.org/topic/solved-cgminer-keyboard-issues-197215
Try disabling the usb hotplug scanning. Various versions of windows can suck dicks that way.

--hotplug 0


works like a charm! Thank you.
hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
I think I might found a bug.

Can devs look at this thread?

https://bitcointalksearch.org/topic/solved-cgminer-keyboard-issues-197215
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.
sr. member
Activity: 302
Merit: 252
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
newbie
Activity: 41
Merit: 0

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
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
I think I might found a bug.

Can devs look at this thread?

https://bitcointalksearch.org/topic/solved-cgminer-keyboard-issues-197215
Try disabling the usb hotplug scanning. Various versions of windows can suck dicks that way.

--hotplug 0
hero member
Activity: 535
Merit: 500
legendary
Activity: 3586
Merit: 1099
Think for yourself
One question, if you launch your cgminer with "-s 5" what's meaning? I'm lokking in the readme file but i don't find nothing.

From the readme:  (lol)

--scan-time|-s Upper bound on time spent scanning current work, in seconds (default: 60)

Dafuq... thx you very much. I was reading scrypt-readme T_T

Reading the script-readme is great and I'm sure the author appreciates it.  But the other readme's and the top post have allot of general info that applies to mining generically.  So it's probably good to start with the generic and then move to the specific.

It's allot to digest I know.  I have gotten my share of RTFM suggestions too Smiley

Sam
legendary
Activity: 1792
Merit: 1008
/dev/null
Out of curiosity, what version was the last Linux binaries to support CPU mining before it was removed?

Thanks
CPUmining ist not welcome here, if you need a miner get the best one: https://github.com/pooler/cpuminer/
since u got ur tool, dont talk about CPUmining anymore in here Tongue

EDIT: ck, if you want il remove it Wink
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Out of curiosity, what version was the last Linux binaries to support CPU mining before it was removed?

Thanks
None available. I am actively doing whatever I can to discourage anyone from finding a way to CPU mine if I can help it. It's bad for bitcoin, it's bad for the reputation due to illegal botnet virus associations, and [insert lots of other reasons I can't be bothered repeating here]. Spending $1000 in electricity to earn 10 cents unless someone is getting ripped off is bad for someone.
newbie
Activity: 57
Merit: 0
Out of curiosity, what version was the last Linux binaries to support CPU mining before it was removed?

Thanks
newbie
Activity: 27
Merit: 0
One question, if you launch your cgminer with "-s 5" what's meaning? I'm lokking in the readme file but i don't find nothing.

From the readme:  (lol)

--scan-time|-s Upper bound on time spent scanning current work, in seconds (default: 60)

Dafuq... thx you very much. I was reading scrypt-readme T_T
sr. member
Activity: 378
Merit: 250
One question, if you launch your cgminer with "-s 5" what's meaning? I'm lokking in the readme file but i don't find nothing.

From the readme:  (lol)

--scan-time|-s Upper bound on time spent scanning current work, in seconds (default: 60)
newbie
Activity: 27
Merit: 0
One question, if you launch your cgminer with "-s 5" what's meaning? I'm lokking in the readme file but i don't find nothing.
legendary
Activity: 2912
Merit: 1060
sr. member
Activity: 448
Merit: 250

Doesn't everyone use that as their homepage? Smiley

Actually, I don't, but it is saved in my shortcuts/favorites bar.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
...
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.
Wow - that's overclocked Smiley

Apparently you can get ~370MH/s out of a 7850 but I'd wonder how long it would last ...

my bad, that's a 100Mhs card, i got confused. I haven't had the chance to memorize the entire Hardware comparison chart yet. i occasionally get things mixed up.
I simply go by this:
https://en.bitcoin.it/wiki/Mining_hardware_comparison
Jump to: