Bitcoin Forum
May 25, 2018, 01:10:44 PM *
News: Latest stable version of Bitcoin Core: 0.16.0  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 [585] 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 ... 847 »
  Print  
Author Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.10.0  (Read 5755638 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.
lastbit
Full Member
***
Offline Offline

Activity: 206
Merit: 100


View Profile
August 01, 2013, 01:54:28 PM
 #11681

Temperatures are normal, 21,65,50.
Are you sure? 65 is chip max I think and also standard cutoff in cgminer?
Default target was 70, cutoff 90. I have put them at 65 and 85.

My batch#2 Avalons make problems with 55+. Try 50 as target and you will have no issues.
in batch#3 they moved the temperature sensor to the board. 50 @batch#2 is roughly equiv. to 70 @batch#3. So I'm actually 5 degrees lower.
Transactions must be included in a block to be properly completed. When you send a transaction, it is broadcast to miners. Miners can then optionally include it in their next blocks. Miners will be more inclined to include your transaction if it has a higher transaction fee.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1527253844
Hero Member
*
Offline Offline

Posts: 1527253844

View Profile Personal Message (Offline)

Ignore
1527253844
Reply with quote  #2

1527253844
Report to moderator
crazyates
Legendary
*
Offline Offline

Activity: 952
Merit: 1000



View Profile
August 01, 2013, 03:20:41 PM
 #11682

I'm having an issue (sort of) in Win8x64 with CGMiner 3.3.1. CGMiner stops updating it's stats, and acts like it's frozen. Key commands don't do anything, and if I didn't know otherwise, I'd think it had frozen. It's still using CPU time, using network activity, and my pools keep getting shares, so I know it's working.

It happened again today. I checked my miner tonight (~1am on the 1st), and it had frozen ~10:15am on the 31st. So it sat for almost 15 hours acting like it had frozen, but it was running all day. I minimized and opened it again, and now it's working just fine, and even showing the shares that should have been going by when it was "frozen".

I'm assuming you're going to say this is a curses issue? I really have no idea I'm not a programmer. Tongue

Other than that issue, it's working great on my BFL equipment. Thanks! Cheesy
I have also seen this happen with 3.3.1 on low-powered CPUs (Atom class) on both Windows 7 and 8.
Its a 990FXA board with a FX-8120, CPU so its not underpowered. And yes, I only minimized it, I did not close and reopen.

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

Activity: 2464
Merit: 1042


Linux since 1997 RedHat 4


View Profile
August 01, 2013, 07:58:47 PM
 #11683

My GPU was SICK for several days and I missed that because monitoring script reading API port 4028 reported OK. Is there a way to detect SICK card through API?

cgminer 3.2.2 reported:
Code:
[2013-07-28 11:29:54] Stratum from pool 1 detected new block
[2013-07-28 11:29:55] Pool 1 stale share detected, discarding
[2013-07-28 11:29:56] Accepted 876fa488 Diff 4/2 GPU 0 pool 1
[2013-07-28 11:31:28] Stratum connection to pool 1 interrupted
[2013-07-28 11:31:28] Lost 517 shares due to stratum disconnect on pool 1
[2013-07-28 11:31:30] Pool 1 stratum share submission failure
[2013-07-28 11:32:00] Pool 1 communication resumed, submitting work
[2013-07-28 11:32:00] Rejected acc5c400 Diff 3/2 GPU 0 pool 1
[2013-07-28 11:32:32] GPU0: Idle for more than 60 seconds, declaring SICK!
[2013-07-28 11:32:32] GPU0: Attempting to restart
[2013-07-28 11:32:32] Thread 0 still exists, killing it off
[2013-07-28 11:32:32] Thread 0 restarted

"devs" report for SICK card:
Code:
echo '{"command" : "devs"}' | nc localhost 4028 | tr -d '\0' | python -mjson.tool
{
    "DEVS": [
        {
            "Accepted": 694192,
            "Diff1 Work": 2380127,
            "Difficulty Accepted": 1360131.0,
            "Difficulty Rejected": 436120.0,
            "Enabled": "Y",
            "Fan Percent": 56,
            "Fan Speed": -1,
            "GPU": 0,
            "GPU Activity": 0,
            "GPU Clock": 157,
            "GPU Voltage": 1.1,
            "Hardware Errors": 0,
            "Intensity": "18",
            "Last Share Difficulty": 2.0,
            "Last Share Pool": 1,
            "Last Share Time": 1375003796,
            "Last Valid Work": 1375003890,
            "MHS 5s": 0.0,
            "MHS av": 0.17,
            "Memory Clock": 300,
            "Powertune": 0,
            "Rejected": 222954,
            "Status": "Alive",
            "Temperature": 40.0,
            "Total MH": 156195.3567,
            "Utility": 44.85
        }
    ],
    "STATUS": [
        {
            "Code": 9,
            "Description": "cgminer 3.2.2",
            "Msg": "1 GPU(s) - ",
            "STATUS": "S",
            "When": 1375361725
        }
    ],
    "id": 1
}

I am not sure but this could be a bug. I can try to detect SICK state from several parameters (MHS 5s, GPU Activity, Temperature) but is it correct way? If it is, what parameter should be used for detection?
BTW, reported parameter "MHS av" is wrong, it was 0.00, because card was sick for several days...

Firstly, "When" - "Last Share Time" was 357929s ago ... so yeah that explains the rejects - it's spitting out crap Tongue
357929s = 99h 25m 29s
Probably scrypt mining on too high settings?

The best one to use there would be "Last Valid Work" ... that says 357835s ago or 99h 23m 55s ...

The MH av will take a long time to get to 0 since it is the av since it started and it obviously did 'some' work.
It says you did "Total MH": 156195.3567, so it would take a long time for that to average out to less than 10kH/s (more than 180 days)

The device isn't SICK when you did the API command it was "Status": "Alive"

The notify command would say when it last has a problem and also how many times it was SICK.

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: 2534
Merit: 1072


Ruu \o/


View Profile WWW
August 01, 2013, 08:34:22 PM
 #11684

I have an Avalon batch3 4 modules, firmware 20130723.
After a few hours of hashing, some of the modules stops (once all stopped, once three of them, once two of them). The other(s) continue hashing.
Temperatures are normal, 21,65,50.
It happened @300 and @282MHz, although unit can hash @350MHz at least for some time.
I have measured power consumption at the wall and it's in normal PSU parameters.
When module(s) stop, there's this error in System Log:
Code:
usb 1-1: clear tt 1 (0030) error -71
Any ideas?
I did not create that firmware...

However that looks like a usb connectivity issue which happens quite often on avalon because of the terrible hardware that it's run on (the wrt703n router). If you can connect to it via ethernet and fully disable wifi, you will find it more reliable.

(Remember I'm providing generic support for firmware I did not create though).

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
PSL
Member
**
Offline Offline

Activity: 152
Merit: 10


View Profile
August 01, 2013, 11:16:47 PM
 #11685

Firstly, "When" - "Last Share Time" was 357929s ago ... so yeah that explains the rejects - it's spitting out crap Tongue
357929s = 99h 25m 29s
Probably scrypt mining on too high settings?

I don't comply about rejects. These are OK, it was mining against p2pool. Problem is that HASHRATE of this card was 0 for few days and API didn't indicate that card is SICK and AVG rate was not updated. Other problem is that cgminer had no data for few seconds, marked card SICK and never tried to restart mining. Two or three different issues.

I am not sure what is the trigger of this situation, maybe that PC running p2pool was rebooted to apply security updates, so p2pool was offline for few minutes.

The best one to use there would be "Last Valid Work" ... that says 357835s ago or 99h 23m 55s ...

This can work when mining against pool but cannot be used for solo mining at higher diff; in that situation you can mine several days without block or share and Last valid work cannot be used.

The MH av will take a long time to get to 0 since it is the av since it started and it obviously did 'some' work. It says you did "Total MH": 156195.3567, so it would take a long time for that to average out to less than 10kH/s (more than 180 days)

The device isn't SICK when you did the API command it was "Status": "Alive"

Card was running ok for several days and in one moment card was marked as SICK, hashrate changed to 0, temperature and GPU engine frequency were set low; card was marked sick for several days and status was ALIVE all the time, otherwise monitoring script will highlight the problem. And this is why I thing there is a bug... Is it expected that SICK card is reported in API as DEAD?

The notify command would say when it last has a problem and also how many times it was SICK.

I don't have "notify" report for sick card; next time...

           TWITTER ◣                        ☆☆☆✩✩✩✩ IAME ☆✩✩✩✩☆☆                        ◢ WHITEPAPERJOIN
                     WEBSITE ◣                         ☆✩✩Fragmented☆✩✩                         ◢ MEDIUM            ◢ AIRDROP
         TELEGRAM ◣                        ☆☆☆Identity☆☆☆                        ◢ FACEBOOK     ◢ NOW
kano
Legendary
*
Offline Offline

Activity: 2464
Merit: 1042


Linux since 1997 RedHat 4


View Profile
August 02, 2013, 01:18:25 AM
 #11686

...
The best one to use there would be "Last Valid Work" ... that says 357835s ago or 99h 23m 55s ...

This can work when mining against pool but cannot be used for solo mining at higher diff; in that situation you can mine several days without block or share and Last valid work cannot be used.
...
Nope.

I really did say that coz it is correct ...

I added "Last Valid Work" to cgminer coz it is the best way to determine something is wrong.

It has nothing to do with shares or difficulty.

It is the last time a valid hash was returned by the device.

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!
PSL
Member
**
Offline Offline

Activity: 152
Merit: 10


View Profile
August 02, 2013, 06:45:56 AM
 #11687

What about API and blocks found by cgminer? It looks like noone is really interested in blocks, all effort is focused to shares reporting... The only API command "summary" reports blocks found. I can manually display blocks found for a pool. Could by API command "pools" extended to report blocks found for a pool?

           TWITTER ◣                        ☆☆☆✩✩✩✩ IAME ☆✩✩✩✩☆☆                        ◢ WHITEPAPERJOIN
                     WEBSITE ◣                         ☆✩✩Fragmented☆✩✩                         ◢ MEDIUM            ◢ AIRDROP
         TELEGRAM ◣                        ☆☆☆Identity☆☆☆                        ◢ FACEBOOK     ◢ NOW
PSL
Member
**
Offline Offline

Activity: 152
Merit: 10


View Profile
August 02, 2013, 07:36:08 AM
 #11688

...
The best one to use there would be "Last Valid Work" ... that says 357835s ago or 99h 23m 55s ...

This can work when mining against pool but cannot be used for solo mining at higher diff; in that situation you can mine several days without block or share and Last valid work cannot be used.
...
Nope.

I really did say that coz it is correct ...

I added "Last Valid Work" to cgminer coz it is the best way to determine something is wrong.

It has nothing to do with shares or difficulty.

It is the last time a valid hash was returned by the device.

Tested and it doesn't work for solo mining. I calculated "timeout" from devs data, like
devs.STATUS.When-devs.DEVS(x).Last Valid Work; I see that timeout can be high even for healthy card...

           TWITTER ◣                        ☆☆☆✩✩✩✩ IAME ☆✩✩✩✩☆☆                        ◢ WHITEPAPERJOIN
                     WEBSITE ◣                         ☆✩✩Fragmented☆✩✩                         ◢ MEDIUM            ◢ AIRDROP
         TELEGRAM ◣                        ☆☆☆Identity☆☆☆                        ◢ FACEBOOK     ◢ NOW
kano
Legendary
*
Offline Offline

Activity: 2464
Merit: 1042


Linux since 1997 RedHat 4


View Profile
August 02, 2013, 08:05:06 AM
 #11689

...
The best one to use there would be "Last Valid Work" ... that says 357835s ago or 99h 23m 55s ...

This can work when mining against pool but cannot be used for solo mining at higher diff; in that situation you can mine several days without block or share and Last valid work cannot be used.
...
Nope.

I really did say that coz it is correct ...

I added "Last Valid Work" to cgminer coz it is the best way to determine something is wrong.

It has nothing to do with shares or difficulty.

It is the last time a valid hash was returned by the device.

Tested and it doesn't work for solo mining. I calculated "timeout" from devs data, like
devs.STATUS.When-devs.DEVS(x).Last Valid Work; I see that timeout can be high even for healthy card...
Try again ... it works ... I wrote it Tongue

Code:
[STATUS] =>
(
   [STATUS] => S
   [When] => 1375430059
   [ Code] => 9
   [Msg] => 0 GPU(s) - 3 ASC(s) - 6 PGA(s) -
   [Description] => Subaru
)
[ASC0] =>
(
   [ASC] => 0
   [Name] => BAS
   [ID] => 0
   [Enabled] => Y
   [Status] => Alive
   [Temperature] => 67.00
   [MHS av] => 61520.46
   [MHS 5s] => 61445.47
   [Accepted] => 5040
   [Rejected] => 30
   [Hardware Errors] => 19392
   [Utility] => 3.35
   [Last Share Pool] => 0
   [Last Share Time] => 1375430055
   [Total MH] => 5561359878.0407
   [Diff1 Work] => 1292409
   [Difficulty Accepted] => 1271115.00000000
   [Difficulty Rejected] => 7680.00000000
   [Last Share Difficulty] => 256.00000000
   [No Device] => false
   [Last Valid Work] => 1375430059
)

1375430059-1375430059=0

Yep a BAS (61.5GH/s) will average >14 results a second so will usually be 0

For an AMU as it says 335MH/s
Code:
[STATUS] =>
(
   [STATUS] => S
   [When] => 1375430228
   [ Code] => 9
   [Msg] => 0 ASC(s) - 3 PGA(s) -
   [Description] => Pi
)
[PGA0] =>
(
   [PGA] => 0
   [Name] => AMU
   [ID] => 0
   [Enabled] => Y
   [Status] => Alive
   [Temperature] => 0.00
   [MHS av] => 335.97
   [MHS 5s] => 335.36
   [Accepted] => 35
   [Rejected] => 0
   [Hardware Errors] => 90
   [Utility] => 0.02
   [Last Share Pool] => 0
   [Last Share Time] => 1375428250
   [Total MH] => 37978409.3286
   [Frequency] => 0.00
   [Diff1 Work] => 8761
   [Difficulty Accepted] => 7430.00000000
   [Difficulty Rejected] => 0.00000000
   [Last Share Difficulty] => 256.00000000
   [No Device] => false
   [Last Valid Work] => 1375430227
)
1375430228-1375430227=1
It will average 12.8 seconds
Variance of up to 8 times is not rare so 102 would not be unexpected
(My script that checks it for my old Icarus that sometimes stops working uses a factor of 21.2 to restart cgminer)
Of course if you get a hardware error, that won't count - so consider that like doubling the time ... then a few HW in a row ... and ...

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!
Lucko
Hero Member
*****
Offline Offline

Activity: 826
Merit: 1000



View Profile
August 02, 2013, 08:42:05 AM
 #11690

I'm sure this was answered but can't find it using search and reading all is out of the question...

Jalapeno

 [2013-08-02 09:57:22] USB init, open device failed, err -12, you need to install a WinUSB driver for - BFL device 7:2

I'm googling and the only solution that work was use BFGminer... Now I'm sure it is possible to use cgminer but have no idea how... Where do I get that driver?

I found one on net but didn't work... And according to Jalapeno how-to it should be plug and play...
kano
Legendary
*
Offline Offline

Activity: 2464
Merit: 1042


Linux since 1997 RedHat 4


View Profile
August 02, 2013, 09:13:30 AM
 #11691

Read any of README, ASIC-README or even FPGA-README that tells you how to setup the windows driver ...
FPGA-README also has the link to download it rather than typing the name Zadig into google Smiley

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!
PSL
Member
**
Offline Offline

Activity: 152
Merit: 10


View Profile
August 02, 2013, 09:20:25 AM
 #11692

Try again ... it works ... I wrote it Tongue

PWC solo & 5750 (about 80 kHash), Last Valid Work is 1751 seconds old just now and still growing. I already noticed that this value was higher than 2000 seconds. On the other side, faster card (7950) and different scrypt coin has lower values but I see 244 seconds timeout just now... These values are related to coin and GPU hashrate.

           TWITTER ◣                        ☆☆☆✩✩✩✩ IAME ☆✩✩✩✩☆☆                        ◢ WHITEPAPERJOIN
                     WEBSITE ◣                         ☆✩✩Fragmented☆✩✩                         ◢ MEDIUM            ◢ AIRDROP
         TELEGRAM ◣                        ☆☆☆Identity☆☆☆                        ◢ FACEBOOK     ◢ NOW
Lucko
Hero Member
*****
Offline Offline

Activity: 826
Merit: 1000



View Profile
August 02, 2013, 09:29:07 AM
 #11693

You really need to make this README more dumber friendly...

I have no idea that this refers to my problem:
When mining on windows, the driver being used will determine if mining will work.

If the driver doesn't allow mining, you will get a "USB init," error message
i.e. one of:
 open device failed, err %d, you need to install a Windows USB driver for the device
or
 claim interface %d failed, err %d


And why is then saying WinUSB not Zadig?

And why dose it work on a BFGminer?

EDIT: Zagid doesn't detect my device...  And please don't send me to another readme... I will say BFGminer is fine in this case...
os2sam
Legendary
*
Offline Offline

Activity: 2436
Merit: 1001


Think for yourself


View Profile
August 02, 2013, 10:53:44 AM
 #11694

You really need to make this README more dumber friendly...

Doesn't seem too difficult to me.  Could be worded better I guess

-----------------------ASIC Readme-------------------------
WINDOWS:

On windows, the direct USB support requires the installation of a WinUSB
driver (NOT the ftdi_sio driver), and attach it to the Butterfly labs device.
The easiest way to do this is to use the zadig utility which will install the
drivers for you and then once you plug in your device you can choose the
"list all devices" from the "option" menu and you should be able to see the
device as something like: "BitFORCE SHA256 SC". Choose the install or replace
driver option and select WinUSB. You can either google for zadig or download
it from the cgminer directoy in the DOWNLOADS link above.
-------------------------------------------------------------

Here is my interpretation of the above paragraph and the steps I took

1. Unplug all Erupters
2. Run Zadig - Install WinUSB (I may have rebooted, can't remember for sure) - I could not install WinUSB while Erupters were plugged in.
3. Plug in one Erupter, verify that it is set to WinUSB.  If not set it to WinUSB.
4. Close Zadig, plug in the rest of the Erupters, run CGMiner.
Done

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?
kano
Legendary
*
Offline Offline

Activity: 2464
Merit: 1042


Linux since 1997 RedHat 4


View Profile
August 02, 2013, 11:43:46 AM
 #11695

You really need to make this README more dumber friendly...

I have no idea that this refers to my problem:
When mining on windows, the driver being used will determine if mining will work.

If the driver doesn't allow mining, you will get a "USB init," error message
i.e. one of:
 open device failed, err %d, you need to install a Windows USB driver for the device
or
 claim interface %d failed, err %d


And why is then saying WinUSB not Zadig?

And why dose it work on a BFGminer?

EDIT: Zagid doesn't detect my device...  And please don't send me to another readme... I will say BFGminer is fine in this case...

OK ... how is this not obvious?

Quote
USB init, open device failed, err -12, you need to install a WinUSB driver for - BFL device 7:2

I know I updated the message to match it exactly recently, but sheesh, it was pretty close before ...

Edit: also note that the READMEs even tell you what to do if it doesn't see your device ...

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!
Lucko
Hero Member
*****
Offline Offline

Activity: 826
Merit: 1000



View Profile
August 02, 2013, 11:57:21 AM
 #11696

You really need to make this README more dumber friendly...

I have no idea that this refers to my problem:
When mining on windows, the driver being used will determine if mining will work.

If the driver doesn't allow mining, you will get a "USB init," error message
i.e. one of:
 open device failed, err %d, you need to install a Windows USB driver for the device
or
 claim interface %d failed, err %d


And why is then saying WinUSB not Zadig?

And why dose it work on a BFGminer?

EDIT: Zagid doesn't detect my device...  And please don't send me to another readme... I will say BFGminer is fine in this case...

OK ... how is this not obvious?

Quote
USB init, open device failed, err -12, you need to install a WinUSB driver for - BFL device 7:2

I know I updated the message to match it exactly recently, but sheesh, it was pretty close before ...

Edit: also note that the READMEs even tell you what to do if it doesn't see your device ...

It is obvious to you I guess but not to me... To me this looks like sjldjlashfioedclas slojndalen siposajkdakl sjkdsjowm

And it is the last version so this is what you get out...

And it might be in README but it is not in English that I understand... The only thing that I find it that you need to run it as admin and I did...

EDIT: This is the part I should be reading right in ASIC readme?

WINDOWS:

On windows, the direct USB support requires the installation of a WinUSB
driver (NOT the ftdi_sio driver), and attach it to the Butterfly labs device.
The easiest way to do this is to use the zadig utility which will install the
drivers for you and then once you plug in your device you can choose the
"list all devices" from the "option" menu and you should be able to see the
device as something like: "BitFORCE SHA256 SC". Choose the install or replace
driver option and select WinUSB. You can either google for zadig or download
it from the cgminer directory in the DOWNLOADS link above.

When you first switch a device over to WinUSB with zadig and it shows that
correctly on the left of the zadig window, but it still gives permission
errors, you may need to unplug the USB miner and then plug it back in

And this in FPGA...

When mining on windows, the driver being used will determine if mining will work.

If the driver doesn't allow mining, you will get a "USB init," error message
i.e. one of:
 open device failed, err %d, you need to install a Windows USB driver for the device
or
 claim interface %d failed, err %d

The best solution for this is to use a tool called Zadig to set the driver:
 http://sourceforge.net/projects/libwdi/files/zadig/

This allows you set the driver for the device to be WinUSB which is usually
required to make it work if you're having problems

With Zadig, you may need to run it as administrator and if your device is
plugged in but you cannot see it, use the Menu: Options -> List All Devices

You must also make sure you are using the latest libusb-1.0.dll supplied
with cgminer (not the libusbx version)

When you first switch a device over to WinUSB with Zadig and it shows that
correctly on the left of the Zadig window, but it still gives permission
errors, you may need to unplug the USB miner and then plug it back in

Doesn't work or I don't understand it... But after doing that BFGminer stop working...
Lucko
Hero Member
*****
Offline Offline

Activity: 826
Merit: 1000



View Profile
August 02, 2013, 12:14:21 PM
 #11697

You really need to make this README more dumber friendly...

Doesn't seem too difficult to me.  Could be worded better I guess

-----------------------ASIC Readme-------------------------
WINDOWS:

On windows, the direct USB support requires the installation of a WinUSB
driver (NOT the ftdi_sio driver), and attach it to the Butterfly labs device.
The easiest way to do this is to use the zadig utility which will install the
drivers for you and then once you plug in your device you can choose the
"list all devices" from the "option" menu and you should be able to see the
device as something like: "BitFORCE SHA256 SC". Choose the install or replace
driver option and select WinUSB. You can either google for zadig or download
it from the cgminer directoy in the DOWNLOADS link above.
-------------------------------------------------------------

Here is my interpretation of the above paragraph and the steps I took

1. Unplug all Erupters
2. Run Zadig - Install WinUSB (I may have rebooted, can't remember for sure) - I could not install WinUSB while Erupters were plugged in.
3. Plug in one Erupter, verify that it is set to WinUSB.  If not set it to WinUSB.
4. Close Zadig, plug in the rest of the Erupters, run CGMiner.
Done
I don't see BitFORCE SHA256 SC if it is unplugged...
kano
Legendary
*
Offline Offline

Activity: 2464
Merit: 1042


Linux since 1997 RedHat 4


View Profile
August 02, 2013, 12:41:06 PM
 #11698

Tell you what - since you clearly can't understand what is written in the README, come visit IRC, send me 1 BTC and I'll help you.
Wasting space in here repeating what's in the READMEs is ... a waste of space.
A lot of effort has gone into the READMEs by ckolivas and myself and I wrote all the original version of the USB code and README for USB so I've no idea what's difficult about it for anyone who knows a bit about using a computer.
Since it will obviously take some time to tell you all the keys to press - come to IRC (in my sig)

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!
Lucko
Hero Member
*****
Offline Offline

Activity: 826
Merit: 1000



View Profile
August 02, 2013, 01:13:24 PM
 #11699

Figure it out... Readme is missing restart computer...

EDIT: And just to let you know. This is the second time I come hire ready to make a donation and second time thinking why... First time I was pointed in every but the right direction(most of the time reading README) not to waist anyone time and it end up probably being a bug in cgminer that I found workaround since none took me seriously thinking that I just doing something wrong since this is impossible... I bet it was never investigated since new version still have it... and I did post what happens and how did I solve it.

This time first anser did help me to understand that BFL instructions aren't correct but didn't help much understanding what is wrong that it still doesn't work only disable my workaround. And what I figure out then. Missing instruction in README that I was send to read and use... Will it be fixed?
kano
Legendary
*
Offline Offline

Activity: 2464
Merit: 1042


Linux since 1997 RedHat 4


View Profile
August 02, 2013, 01:47:46 PM
 #11700

Try again ... it works ... I wrote it Tongue

PWC solo & 5750 (about 80 kHash), Last Valid Work is 1751 seconds old just now and still growing. I already noticed that this value was higher than 2000 seconds. On the other side, faster card (7950) and different scrypt coin has lower values but I see 244 seconds timeout just now... These values are related to coin and GPU hashrate.
The time will of course relate to the speed of the device.

Until you find a nonce, the device has done nothing successfully.

How long on average ... well that of course will directly relate to the hash rate and how many hashes are required on average per nonce.

For BTC sha256 you need to do on average 2^32 hashes per nonce - so for 100MH/s that's 43seconds for 2^32 hashes.
21 times that is 15 minutes - so yeah if a 100MH/s device finds no valid shares in 15 minutes then you can be pretty sure something is wrong.

Until a device actually returns a valid nonce, you can't be sure it really is working properly.

I guess on scrypt you have a problem coz it may take months minutes to do any work, so I guess you can't really be sure there is something wrong very quickly. However, in your case you went way, way past the point where "Last Valid Work" would definitely mean something is wrong.
I will also add that with scrypt, if you try to push the performance up too much, you could easily get exactly what you said, where the device might keep returning invalid nonces but still appear to be OK from cgminer's point of view - send work, get reply.
The problem there of course is that you'd have to keep a history of HW errors since if it works OK for 3 days and then starts spitting out constant HW errors due to whatever is the cause, the HW error rate won't increase very fast.

I've never bother to scrypt GPU mine ... I prefer to have my GPUs idle or playing Minecraft for my kids - they use so much energy mining ...

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!
Pages: « 1 ... 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 [585] 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 ... 847 »
  Print  
 
Jump to:  

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!