MultiMiner: Any Miner, Any Where, on Any Device (Free, Open Source, Cross Platform) - page 77.

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: Blackbird0 on February 26, 2014, 11:58:55 PM

Hmm. Isn't there a restart command to tell BFG to try to re-initialize when it stops getting device feedback?

It will with some devices but the DualMiner driver is specifically flagged to not have BFGMiner restart it because it needs to have those initialization commands sent to it. It sounds like I'll need to make a few small changes once I have a device to test with again.

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: ManeBjorn on February 26, 2014, 10:54:58 PM

Sorry for the delay had another fall.
Here is the output.

Are you sure that is the build of BFGMiner that I posted? I posted both a build of MultiMiner and a build of BFGMiner. You need both.

Blackbird0

full member

Activity: 207

Merit: 100

Quote from: nwoolls on February 26, 2014, 10:14:30 PM

Quote from: Blackbird0 on February 26, 2014, 07:46:29 PM

I should add: happened second time: light on miner went out, no more accepted shares.

I'm currently on hold waiting for a replacement device.

My guess on this is that the device is getting disconnected somehow (maybe just USB interference) and then not being reinitialized. Without going into too much detail there's a whole initialization process when you start mining that sets the ASIC up for this much Scrypt, this much SHA, etc. It has to be setup each time before mining. My guess is that something is causing a disconnect there and I'm not reinitializing.

I appreciate the feedback. Hopefully I can resume work soon.

Hmm. Isn't there a restart command to tell BFG to try to re-initialize when it stops getting device feedback?

ManeBjorn

legendary

Activity: 1288

Merit: 1004

Sorry for the delay had another fall.
Here is the output.

Code:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\User>cd C:\Users\User\Downloads\MultiMiner-2.7.4\Miners\bfgminer

C:\Users\User\Downloads\MultiMiner-2.7.4\Miners\bfgminer>bfgminer -d? -S noauto
-S dualminer:all -D
[2014-02-26 22:53:15] setrlimit: Not supported by platform
[2014-02-26 22:53:15] Started bfgminer 3.10.0
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:004:001: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:002:001: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:006:001: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:005:001: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:003:001: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:001:001: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:008:001: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:007:001: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:008:011: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:008:013: LIBUS
B_ERROR_NOT_FOUND
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:008:007: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:007:002: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:008:002: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:008:004: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:008:008: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:008:009: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:008:010: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:008:012: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:008:003: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:008:005: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] usb_devinfo_scan: Error opening device usb:008:006: LIBUS
B_ERROR_NOT_SUPPORTED
[2014-02-26 22:53:16] hidapi_try_lib: Couldn't load libhidapi.dll: unknown

[2014-02-26 22:53:16] hidapi_try_lib: Successfully loaded libhidapi-0.dll

[2014-02-26 22:53:16] hid_devinfo_scan: Found "Microsoft 3-Button Mouse with In
telliEye(TM)" serial " "
[2014-02-26 22:53:16] hid_devinfo_scan: Found "EP1" serial " "

[2014-02-26 22:53:16] hid_devinfo_scan: Found "EP2" serial " "

[2014-02-26 22:53:16] hid_devinfo_scan: Found "EP2" serial " "

[2014-02-26 22:53:16] Failed to get PortName registry key value in lowl-vcom.c
_vcom_devinfo_scan_windows__hubport():447: The system cannot find the file speci
fied.
[2014-02-26 22:53:16] Failed to get PortName registry key value in lowl-vcom.c
_vcom_devinfo_scan_windows__hubport():447: The system cannot find the file speci
fied.
[2014-02-26 22:53:16] Failed to ioctl in lowl-vcom.c windows_usb_get_string():3
89: A device attached to the system is not functioning.
[2014-02-26 22:53:16] Failed to ioctl in lowl-vcom.c windows_usb_get_string():3
89: A device attached to the system is not functioning.
[2014-02-26 22:53:16] Failed to ioctl in lowl-vcom.c windows_usb_get_string():3
89: A device attached to the system is not functioning.
[2014-02-26 22:53:16] Failed to ioctl in lowl-vcom.c windows_usb_get_string():3
89: A device attached to the system is not functioning.
[2014-02-26 22:53:16] Failed to get PortName registry key value in lowl-vcom.c
_vcom_devinfo_scan_windows__hubport():447: The system cannot find the file speci
fied.
[2014-02-26 22:53:16] FTDI reports 3 devices
[2014-02-26 22:53:16] FT_GetComPortNumber(021d2b88 (2), 26)

[2014-02-26 22:53:17] FT_GetComPortNumber(021d2b98 (1), 28)

[2014-02-26 22:53:17] QueryDosDevice returned insufficent buffer error; enlargi
ng to 200
[2014-02-26 22:53:17] QueryDosDevice returned insufficent buffer error; enlargi
ng to 400
[2014-02-26 22:53:17] QueryDosDevice returned insufficent buffer error; enlargi
ng to 800
[2014-02-26 22:53:17] QueryDosDevice returned insufficent buffer error; enlargi
ng to 1000
[2014-02-26 22:53:17] QueryDosDevice returned insufficent buffer error; enlargi
ng to 2000
[2014-02-26 22:53:17] QueryDosDevice returned insufficent buffer error; enlargi
ng to 4000
[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:008:006 (path=(nul
l), vid=1a40, pid=0201, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:008:005 (path=(nul
l), vid=1a40, pid=0201, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:008:003 (path=(nul
l), vid=1a40, pid=0201, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:008:012 (path=(nul
l), vid=198c, pid=b1f1, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:008:010 (path=(nul
l), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:008:009 (path=(nul
l), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:008:008 (path=(nul
l), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:008:004 (path=(nul
l), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:008:002 (path=(nul
l), vid=1058, pid=1100, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:007:002 (path=(nul
l), vid=0644, pid=0200, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:006:002 (path=(nul
l), vid=05a4, pid=9760, manuf=ORTEK, prod=EP2, serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:006:004 (path=(nul
l), vid=045e, pid=0040, manuf=Microsoft, prod=Microsoft 3-Button Mouse with Inte
lliEye(TM), serial=(null))
[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:008:007 (path=(nul
l), vid=0403, pid=6014, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:008:013 (path=(nul
l), vid=0403, pid=6010, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:008:011 (path=(nul
l), vid=03eb, pid=204b, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:007:001 (path=(nul
l), vid=8086, pid=293a, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:008:001 (path=(nul
l), vid=8086, pid=293c, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:001:001 (path=(nul
l), vid=8086, pid=2934, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:003:001 (path=(nul
l), vid=8086, pid=2936, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:005:001 (path=(nul
l), vid=8086, pid=2938, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:006:001 (path=(nul
l), vid=8086, pid=2939, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:002:001 (path=(nul
l), vid=8086, pid=2935, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found usb device at usb:004:001 (path=(nul
l), vid=8086, pid=2937, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found hid device at hid:\\?\hid#vid_05a4&p
id_9760&mi_01&col02#7&21508b5&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} (pat
h=\\?\hid#vid_05a4&pid_9760&mi_01&col02#7&21508b5&0&0001#{4d1e55b2-f16f-11cf-88c
b-001111000030}, vid=05a4, pid=9760, manuf=ORTEK, prod=EP2, serial= )

[2014-02-26 22:53:17] lowlevel_scan: Found hid device at hid:\\?\hid#vid_05a4&p
id_9760&mi_01&col01#7&21508b5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} (pat
h=\\?\hid#vid_05a4&pid_9760&mi_01&col01#7&21508b5&0&0000#{4d1e55b2-f16f-11cf-88c
b-001111000030}, vid=05a4, pid=9760, manuf=ORTEK, prod=EP2, serial= )

[2014-02-26 22:53:17] lowlevel_scan: Found hid device at hid:\\?\hid#vid_05a4&p
id_9760&mi_00#7&154524f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} (path=\\?
\hid#vid_05a4&pid_9760&mi_00#7&154524f3&0&0000#{4d1e55b2-f16f-11cf-88cb-00111100
0030}, vid=05a4, pid=9760, manuf=ORTEK, prod=EP1, serial= )

[2014-02-26 22:53:17] lowlevel_scan: Found hid device at hid:\\?\hid#vid_045e&p
id_0040#6&27b06239&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} (path=\\?\hid#v
id_045e&pid_0040#6&27b06239&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vid=0
45e, pid=0040, manuf=Microsoft, prod=Microsoft 3-Button Mouse with IntelliEye(TM
), serial= )
[2014-02-26 22:53:17] lowlevel_scan: Found vcom device at com:6 (path=\\.\COM6,
vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found vcom device at com:3 (path=\\.\COM3,
vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found vcom device at com:27 (path=\\.\COM2
7, vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found vcom device at com:25 (path=\\.\COM2
5, vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found vcom device at com:21 (path=\\.\COM2
1, vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found vcom device at com:20 (path=\\.\COM2
0, vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))

[2014-02-26 22:53:17] lowlevel_scan: Found vcom device at com:28 (path=\\.\COM2
8, vid=0000, pid=0000, manuf=(null), prod=Dual RS232-HS B, serial=B)

[2014-02-26 22:53:17] lowlevel_scan: Found vcom device at com:26 (path=\\.\COM2
6, vid=0000, pid=0000, manuf=(null), prod=BitFORCE SHA256 SC, serial=FTWM8ZN9)

[2014-02-26 22:53:17] lowlevel_scan: Found vcom device at com:12 (path=\\.\COM1
2, vid=0000, pid=0000, manuf=c-scape, prod=biâ€¢fury, serial=1313ed1d0254310)

[2014-02-26 22:53:17] lowlevel_scan: Found vcom device at com:14 (path=\\.\COM1
4, vid=0000, pid=0000, manuf=BFMG, prod=Bitfury BF1, serial=6403636303935170B151
)
[2014-02-26 22:53:17] Devices detected:
[2014-02-26 22:53:17] Timers: Using QueryPerformanceCounter

[2014-02-26 22:53:17] Recalibrating timeofday offset (delta 1393447486.961096s)

0 devices listed

C:\Users\User\Downloads\MultiMiner-2.7.4\Miners\bfgminer>

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: thehulkk on February 26, 2014, 07:44:10 PM

Quote from: thehulkk on February 26, 2014, 04:01:24 PM

I have multiminer checking for straight profitability every 5 minutes from coinwarz, I know when it switches to a different coin it restarts the miner, does it restart every 5 minutes even if it's the same coin? also for the people that use multiminer for multiswitching, do you think coinchoose is a better option than coinwars in terms of profitabilility? I bought 50000 api calls from coinwarz, but I never compared it agains coinchoose which is free.

I'm bumping my post, also adding another question. What do you guys think works better in the long term when mining for profitability average profitability or straight profitability?

Mining is only restarted when the coins being mined change. I can't really comment on the profitability bits - maybe someone else can.

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: ManeBjorn on February 26, 2014, 08:36:01 PM

Ok I will try that in a little bit.
So this will need to be done each time I want to run MultiMiner until the final version comes out?

Nope this is just to try to diagnose why it is not being recognized.

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: Blackbird0 on February 26, 2014, 07:46:29 PM

I should add: happened second time: light on miner went out, no more accepted shares.

I'm currently on hold waiting for a replacement device.

My guess on this is that the device is getting disconnected somehow (maybe just USB interference) and then not being reinitialized. Without going into too much detail there's a whole initialization process when you start mining that sets the ASIC up for this much Scrypt, this much SHA, etc. It has to be setup each time before mining. My guess is that something is causing a disconnect there and I'm not reinitializing.

I appreciate the feedback. Hopefully I can resume work soon.

ManeBjorn

legendary

Activity: 1288

Merit: 1004

Ok I will try that in a little bit.
So this will need to be done each time I want to run MultiMiner until the final version comes out?

Quote from: nwoolls on February 26, 2014, 07:24:00 PM

Quote from: ManeBjorn on February 26, 2014, 06:31:20 PM

Do I put this in the scrypt line where I put my GPU settings in MultiMiner?

No - open a command prompt in the MultiMiner\Miners\bfgminer folder and type the command directly.

ManeBjorn

legendary

Activity: 1288

Merit: 1004

As Nate said not yet.
Thanks for reading it.

Quote from: Blackbird0 on February 26, 2014, 07:28:59 PM

Quote from: ManeBjorn on February 26, 2014, 06:31:20 PM

Yes cgminer still sees it.
Do I put this in the scrypt line where I put my GPU settings in MultiMiner?

Quote from: nwoolls on February 26, 2014, 06:00:47 PM

Quote from: ManeBjorn on February 26, 2014, 05:57:20 PM

I have those installed.
In fact they are what run the dual miner as well.
Do I need to fully uninstall it from the device manager and reinstall?

Nope - just need to run BFGMiner with -S dualminer:all and it should detect it. If not try running:

Code:

bfgminer -d? -S noauto -S dualminer:all -D

And paste the output.

Is cgminer still finding it?

Just read your review of the dualminer. Do your OC arguments work in the BFGMiner fork?

Blackbird0

full member

Activity: 207

Merit: 100

I should add: happened second time: light on miner went out, no more accepted shares.

thehulkk

member

Activity: 442

Merit: 10

Quote from: thehulkk on February 26, 2014, 04:01:24 PM

I have multiminer checking for straight profitability every 5 minutes from coinwarz, I know when it switches to a different coin it restarts the miner, does it restart every 5 minutes even if it's the same coin? also for the people that use multiminer for multiswitching, do you think coinchoose is a better option than coinwars in terms of profitabilility? I bought 50000 api calls from coinwarz, but I never compared it agains coinchoose which is free.

I'm bumping my post, also adding another question. What do you guys think works better in the long term when mining for profitability average profitability or straight profitability?

Blackbird0

full member

Activity: 207

Merit: 100

Quote from: nwoolls on February 26, 2014, 07:42:31 PM

Quote from: Blackbird0 on February 26, 2014, 07:28:59 PM

Just read your review of the dualminer. Do your OC arguments work in the BFGMiner fork?

No overclocking yet - going for stability first. Shouldn't be hard to add though.

Fair nuff.

*keeps testing stability*

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: Blackbird0 on February 26, 2014, 07:28:59 PM

Just read your review of the dualminer. Do your OC arguments work in the BFGMiner fork?

No overclocking yet - going for stability first. Shouldn't be hard to add though.

Blackbird0

full member

Activity: 207

Merit: 100

Quote from: ManeBjorn on February 26, 2014, 06:31:20 PM

Yes cgminer still sees it.
Do I put this in the scrypt line where I put my GPU settings in MultiMiner?

Quote from: nwoolls on February 26, 2014, 06:00:47 PM

Quote from: ManeBjorn on February 26, 2014, 05:57:20 PM

I have those installed.
In fact they are what run the dual miner as well.
Do I need to fully uninstall it from the device manager and reinstall?

Nope - just need to run BFGMiner with -S dualminer:all and it should detect it. If not try running:

Code:

bfgminer -d? -S noauto -S dualminer:all -D

And paste the output.

Is cgminer still finding it?

Just read your review of the dualminer. Do your OC arguments work in the BFGMiner fork?

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: ManeBjorn on February 26, 2014, 06:31:20 PM

Do I put this in the scrypt line where I put my GPU settings in MultiMiner?

No - open a command prompt in the MultiMiner\Miners\bfgminer folder and type the command directly.

ManeBjorn

legendary

Activity: 1288

Merit: 1004

Yes cgminer still sees it.
Do I put this in the scrypt line where I put my GPU settings in MultiMiner?

Quote from: nwoolls on February 26, 2014, 06:00:47 PM

Quote from: ManeBjorn on February 26, 2014, 05:57:20 PM

I have those installed.
In fact they are what run the dual miner as well.
Do I need to fully uninstall it from the device manager and reinstall?

Nope - just need to run BFGMiner with -S dualminer:all and it should detect it. If not try running:

Code:

bfgminer -d? -S noauto -S dualminer:all -D

And paste the output.

Is cgminer still finding it?

Blackbird0

full member

Activity: 207

Merit: 100

Quote from: nwoolls on February 26, 2014, 05:52:09 PM

Quote from: Blackbird0 on February 26, 2014, 04:49:19 PM

http://imgur.com/Uw9U6Vg

nwoolls: it looks like there's some sort of peculiar stat problem on the dualminer. You'll notice that it's not showing shares being accepted properly, nor the best share, nor a rejection percentage.

However, my pool is accepting shares, and I am getting blocks. So I think it must just be a stat issue?

You'll note that everything looks a-okay on the SHA-256 instance that is running along side it.

AFAIK this is just what Scrypt mining looks like in BFGMiner. If there is a bug it's not with the DualMiner. GPU mining Scrypt looks the same (Diff 0/0, R:0+0(none)), etc.

Ah. I didn't know that. I've never done scrypt mining in BFGMiner command line before.

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: ManeBjorn on February 26, 2014, 05:57:20 PM

I have those installed.
In fact they are what run the dual miner as well.
Do I need to fully uninstall it from the device manager and reinstall?

Nope - just need to run BFGMiner with -S dualminer:all and it should detect it. If not try running:

Code:

bfgminer -d? -S noauto -S dualminer:all -D

And paste the output.

Is cgminer still finding it?

ManeBjorn

legendary

Activity: 1288

Merit: 1004

I have those installed.
In fact they are what run the dual miner as well.
Do I need to fully uninstall it from the device manager and reinstall?

Quote from: nwoolls on February 26, 2014, 05:51:07 PM

Quote from: ManeBjorn on February 26, 2014, 04:17:56 PM

On the DualMiner support.
I cannot get it to detect the unit. It flashes the light on it and seems to know it's there but it never shows up in the device list. I even tried on my laptop.
Do I need to add something somewhere?

You need FTDI drivers installed:

http://www.ftdichip.com/Drivers/VCP.htm

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: Blackbird0 on February 26, 2014, 04:49:19 PM

http://imgur.com/Uw9U6Vg

nwoolls: it looks like there's some sort of peculiar stat problem on the dualminer. You'll notice that it's not showing shares being accepted properly, nor the best share, nor a rejection percentage.

However, my pool is accepting shares, and I am getting blocks. So I think it must just be a stat issue?

You'll note that everything looks a-okay on the SHA-256 instance that is running along side it.

AFAIK this is just what Scrypt mining looks like in BFGMiner. If there is a bug it's not with the DualMiner. GPU mining Scrypt looks the same (Diff 0/0, R:0+0(none)), etc.

Topic: MultiMiner: Any Miner, Any Where, on Any Device (Free, Open Source, Cross Platform) - page 77. (Read 827336 times)