Bitcoin Forum
June 25, 2017, 10:23:59 AM *
News: Latest stable version of Bitcoin Core: 0.14.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 [13] 14 15 16 17 18 19 20 »  All
  Print  
Author Topic: Modular Python Bitcoin Miner - Official Thread  (Read 71218 times)
TheSeven
Hero Member
*****
Offline Offline

Activity: 504


FPGA Mining LLC


View Profile WWW
April 06, 2012, 11:58:23 AM
 #241

TheSeven, any ideas when we can expect a non beta release?

When enough people have tested it and we can consider it bug-free. Oh, the UI also still needs some improvements (IE/firefox/opera compatibility, highlighting in the stats table to make that more readable, description tooltips for some elements, ...), and it should also be documented better.

There are currently some experimental fixes and improvements in the testing branch, which I'd like to apply to master soon. This version has been running for like a week here without any issues, however I might have broken compatibility with some python/pyusb version and board type combinations by accident, so some more people should test this.

BTW, a non-beta of 0.0.x was never released, and I'd say that 0.1.0beta should outperform that on most aspects.

My tip jar: 13kwqR7B4WcSAJCYJH1eXQcxG5vVUwKAqY
1498386239
Hero Member
*
Offline Offline

Posts: 1498386239

View Profile Personal Message (Offline)

Ignore
1498386239
Reply with quote  #2

1498386239
Report to moderator
1498386239
Hero Member
*
Offline Offline

Posts: 1498386239

View Profile Personal Message (Offline)

Ignore
1498386239
Reply with quote  #2

1498386239
Report to moderator
1498386239
Hero Member
*
Offline Offline

Posts: 1498386239

View Profile Personal Message (Offline)

Ignore
1498386239
Reply with quote  #2

1498386239
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1498386239
Hero Member
*
Offline Offline

Posts: 1498386239

View Profile Personal Message (Offline)

Ignore
1498386239
Reply with quote  #2

1498386239
Report to moderator
1498386239
Hero Member
*
Offline Offline

Posts: 1498386239

View Profile Personal Message (Offline)

Ignore
1498386239
Reply with quote  #2

1498386239
Report to moderator
1498386239
Hero Member
*
Offline Offline

Posts: 1498386239

View Profile Personal Message (Offline)

Ignore
1498386239
Reply with quote  #2

1498386239
Report to moderator
freshzive
Sr. Member
****
Offline Offline

Activity: 447


View Profile
April 06, 2012, 03:40:57 PM
 #242

Any idea what causes this? It seems to crash python.

Code:
2012-04-06 08:40:00.470180 [100]: Core: Starting up...
2012-04-06 08:40:00.490875 [200]: Core: Startup completed
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

Edit: It actually starts up, but all of my x6500s show this:

Code:
X6500 board AH00WOVX: Proxy: Exception caught: Traceback (most recent call last):
  File "/Users/christian/modular/modules/fpgamining/x6500/boardproxy.py", line 77, in run
    else: self.device = FT232R(FT232R_PyUSB(self.serial, self.takeover))
  File "/Users/christian/modular/modules/fpgamining/x6500/util/ft232r.py", line 315, in __init__
    for bus in usb.busses():
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/legacy.py", line 333, in busses
    return (Bus(),)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/legacy.py", line 329, in __init__
    self.devices = [Device(d) for d in core.find(find_all=True)]
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/core.py", line 851, in find
    return [d for d in device_iter(k, v)]
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/core.py", line 821, in device_iter
    for dev in backend.enumerate_devices():
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/backend/libusb10.py", line 457, in enumerate_devices
    return _DevIterator()
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/backend/libusb10.py", line 445, in __init__
    byref(self.dev_list))
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/backend/libusb10.py", line 403, in _check
    raise USBError(_str_error[ret], ret, _libusb_errno[ret])
USBError: [Errno None] Unknown error
2012-04-06 08:45:34.453529 [100]: X6500 board AH00WOVX: Traceback (most recent call last):
  File "/Users/christian/modular/modules/fpgamining/x6500/x6500worker.py", line 212, in main
    elif data[0] == "dying": raise Exception("Proxy died!")
Exception: Proxy died!

I take it the ztex200mhz file doesn't work? I tried loading firmware using program.py and still get these errors on all devices. This is on Mac OS X with Python 2.7.2

TheSeven
Hero Member
*****
Offline Offline

Activity: 504


FPGA Mining LLC


View Profile WWW
April 06, 2012, 06:04:11 PM
 #243

Any idea what causes this? It seems to crash python.

Code:
2012-04-06 08:40:00.470180 [100]: Core: Starting up...
2012-04-06 08:40:00.490875 [200]: Core: Startup completed
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

Edit: It actually starts up, but all of my x6500s show this:

Code:
X6500 board AH00WOVX: Proxy: Exception caught: Traceback (most recent call last):
  File "/Users/christian/modular/modules/fpgamining/x6500/boardproxy.py", line 77, in run
    else: self.device = FT232R(FT232R_PyUSB(self.serial, self.takeover))
  File "/Users/christian/modular/modules/fpgamining/x6500/util/ft232r.py", line 315, in __init__
    for bus in usb.busses():
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/legacy.py", line 333, in busses
    return (Bus(),)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/legacy.py", line 329, in __init__
    self.devices = [Device(d) for d in core.find(find_all=True)]
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/core.py", line 851, in find
    return [d for d in device_iter(k, v)]
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/core.py", line 821, in device_iter
    for dev in backend.enumerate_devices():
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/backend/libusb10.py", line 457, in enumerate_devices
    return _DevIterator()
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/backend/libusb10.py", line 445, in __init__
    byref(self.dev_list))
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/usb/backend/libusb10.py", line 403, in _check
    raise USBError(_str_error[ret], ret, _libusb_errno[ret])
USBError: [Errno None] Unknown error
2012-04-06 08:45:34.453529 [100]: X6500 board AH00WOVX: Traceback (most recent call last):
  File "/Users/christian/modular/modules/fpgamining/x6500/x6500worker.py", line 212, in main
    elif data[0] == "dying": raise Exception("Proxy died!")
Exception: Proxy died!

I take it the ztex200mhz file doesn't work? I tried loading firmware using program.py and still get these errors on all devices. This is on Mac OS X with Python 2.7.2

Now that's very odd. Haven't seen something like this before.
Which python/pyusb/libusb version is showing that behavior?

My tip jar: 13kwqR7B4WcSAJCYJH1eXQcxG5vVUwKAqY
hashking
Sr. Member
****
Offline Offline

Activity: 308


View Profile
April 07, 2012, 01:05:25 PM
 #244

Anyone using the program to work with GPUMAX.  I can't get mine to connect.  What are your settings for source?
TheSeven
Hero Member
*****
Offline Offline

Activity: 504


FPGA Mining LLC


View Profile WWW
April 07, 2012, 08:42:04 PM
 #245

Anyone using the program to work with GPUMAX.  I can't get mine to connect.  What are your settings for source?


I didn't get a GPUMAX invite yet, so I can't tell you the exact configuration, but other people said it's pretty much straightforward.

My tip jar: 13kwqR7B4WcSAJCYJH1eXQcxG5vVUwKAqY
Garr255
Legendary
*
Offline Offline

Activity: 952


What's a GPU?


View Profile
April 07, 2012, 10:28:15 PM
 #246

Anyone using the program to work with GPUMAX.  I can't get mine to connect.  What are your settings for source?

I haven't tried it yet, but when I do I'll post back here.

“First they ignore you, then they laugh at you, then they fight you, then you win.”  -- Mahatma Gandhi

Average time between signing on to bitcointalk: Two weeks. Please don't expect responses any faster than that!
coblee
Donator
Legendary
*
Offline Offline

Activity: 1204


Creator of Litecoin. Director of Eng at Coinbase.


View Profile
April 09, 2012, 03:20:02 AM
 #247

I just got latest code and everything stopped working. I couldn't get either my x6500 or my Icarus working. I'm getting the proxy died error for x6500 and "device reports readiness to read but returned no data (device disconnected?)" on my Icarus.

This is quite frustrating. Anyway I can switch back to the previous version?

I'm running this on my Mac. Python 2.7.2.

coretechs
Donator
Sr. Member
*
Offline Offline

Activity: 362



View Profile
April 09, 2012, 03:46:19 AM
 #248

I'm still having issues with 0.1.0beta on linux (fresh install, ubuntu 64-bit) as well.  I was able to get it to the point where it loads the firmware on all the boards, but as soon as it hits 100% and completes it throws the following error and restarts the firmware load:

Code:
2012-04-08 23:40:17.763066 [100]: X6500 board AH00WOWB: Proxy: Exception caught: Traceback (most recent call last):
  File "/home/xxxxx/Modular-Python-Bitcoin-Miner/modules/fpgamining/x6500/boardproxy.py", line 123, in run
    if self.error: raise self.error
TypeError: 'int' object is not iterable
2012-04-08 23:40:17.765450 [100]: X6500 board AH00WOWB: Traceback (most recent call last):
  File "/home/xxxxx/Modular-Python-Bitcoin-Miner/modules/fpgamining/x6500/x6500worker.py", line 212, in main
    elif data[0] == "dying": raise Exception("Proxy died!")
Exception: Proxy died!

I have no problems running the same version with the x6500s on windows.  I've tried using the worker and the hotplug worker using the linux install steps on fpgamining.com with no luck.  All the boards detect and load the firmware, then error and repeat.

http://bitcoindoc.com - The Rise and Rise of Bitcoin | http://nxtportal.org - Nxt blockchain explorer
Garr255
Legendary
*
Offline Offline

Activity: 952


What's a GPU?


View Profile
April 09, 2012, 04:40:19 AM
 #249

Try the testing branch. It seems to fix that error.

“First they ignore you, then they laugh at you, then they fight you, then you win.”  -- Mahatma Gandhi

Average time between signing on to bitcointalk: Two weeks. Please don't expect responses any faster than that!
fizzisist
Hero Member
*****
Offline Offline

Activity: 720



View Profile WWW
April 09, 2012, 04:53:52 AM
 #250

Try the testing branch. It seems to fix that error.

Yes, I'm not sure about the details of the error, but the testing branch has a fix for this bug already. If you're running from a git clone, just run

Code:
git checkout testing

then restart MPBM.

I hope that fixes coblee and coretechs' problems! I'm sure TheSeven can explain the problem tomorrow, but he's asleep right now.

coblee
Donator
Legendary
*
Offline Offline

Activity: 1204


Creator of Litecoin. Director of Eng at Coinbase.


View Profile
April 09, 2012, 05:48:15 AM
 #251

Try the testing branch. It seems to fix that error.

Yes, I'm not sure about the details of the error, but the testing branch has a fix for this bug already. If you're running from a git clone, just run

Code:
git checkout testing

then restart MPBM.

I hope that fixes coblee and coretechs' problems! I'm sure TheSeven can explain the problem tomorrow, but he's asleep right now.

After getting the testing branch
Code:
git checkout origin/testing
I'm now getting this exception:
Code:
X6500 worker - AH00WI18: Traceback (most recent call last):
  File "/Users/charlie/Modular-Python-Bitcoin-Miner/modules/fpgamining/x6500/x6500worker.py", line 208, in main
    data = self.rxconn.recv()
EOFError

Garr255
Legendary
*
Offline Offline

Activity: 952


What's a GPU?


View Profile
April 09, 2012, 06:23:28 AM
 #252

Make a new directory and do a
Code:
git clone -b testing https://github.com/TheSeven/Modular-Python-Bitcoin-Miner.git

Then try running it from there. Remember to copy over a bitstream and your config.

“First they ignore you, then they laugh at you, then they fight you, then you win.”  -- Mahatma Gandhi

Average time between signing on to bitcointalk: Two weeks. Please don't expect responses any faster than that!
hashking
Sr. Member
****
Offline Offline

Activity: 308


View Profile
April 09, 2012, 08:19:30 PM
 #253

X6500 board A40146TT: Proxy: Exception caught: Traceback (most recent call last):
  File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\boardproxy.py", line 77, in run
    else: self.device = FT232R(FT232R_PyUSB(self.serial, self.takeover))
  File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\util\ft232r.py", line 346, in __init__
    raise Exception("Can not open the specified device, possibly because it is already in use")
Exception: Can not open the specified device, possibly because it is already in use
2012-04-09 15:16:51.118   [100]   X6500 board A40146TT: Traceback (most recent call last):
  File "C:\Users\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\x6500worker.py", line 211, in main
    elif data[0] == "dying": raise Exception("Proxy died!")
Exception: Proxy died!

I get this error on two of my boards.  The rest work fine.  Not sure why.
fizzisist
Hero Member
*****
Offline Offline

Activity: 720



View Profile WWW
April 09, 2012, 08:58:12 PM
 #254

X6500 board A40146TT: Proxy: Exception caught: Traceback (most recent call last):
  File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\boardproxy.py", line 77, in run
    else: self.device = FT232R(FT232R_PyUSB(self.serial, self.takeover))
  File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\util\ft232r.py", line 346, in __init__
    raise Exception("Can not open the specified device, possibly because it is already in use")
Exception: Can not open the specified device, possibly because it is already in use
2012-04-09 15:16:51.118   [100]   X6500 board A40146TT: Traceback (most recent call last):
  File "C:\Users\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\x6500worker.py", line 211, in main
    elif data[0] == "dying": raise Exception("Proxy died!")
Exception: Proxy died!

I get this error on two of my boards.  The rest work fine.  Not sure why.


I think this is the error you get when the USB interface was not properly closed by MPBM. Try checking "Reset board if it appears to be in use" under the worker config, then right click the worker and click Restart Worker.

hashking
Sr. Member
****
Offline Offline

Activity: 308


View Profile
April 09, 2012, 09:03:07 PM
 #255

X6500 board A40146TT: Proxy: Exception caught: Traceback (most recent call last):
  File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\boardproxy.py", line 77, in run
    else: self.device = FT232R(FT232R_PyUSB(self.serial, self.takeover))
  File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\util\ft232r.py", line 346, in __init__
    raise Exception("Can not open the specified device, possibly because it is already in use")
Exception: Can not open the specified device, possibly because it is already in use
2012-04-09 15:16:51.118   [100]   X6500 board A40146TT: Traceback (most recent call last):
  File "C:\Users\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\x6500worker.py", line 211, in main
    elif data[0] == "dying": raise Exception("Proxy died!")
Exception: Proxy died!

I get this error on two of my boards.  The rest work fine.  Not sure why.


I think this is the error you get when the USB interface was not properly closed by MPBM. Try checking "Reset board if it appears to be in use" under the worker config, then right click the worker and click Restart Worker.

All my boards all work fine on 0.4a.  I will try this.  Thanks.
TheSeven
Hero Member
*****
Offline Offline

Activity: 504


FPGA Mining LLC


View Profile WWW
April 09, 2012, 09:38:43 PM
 #256

X6500 board A40146TT: Proxy: Exception caught: Traceback (most recent call last):
  File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\boardproxy.py", line 77, in run
    else: self.device = FT232R(FT232R_PyUSB(self.serial, self.takeover))
  File "C:\Users\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\util\ft232r.py", line 346, in __init__
    raise Exception("Can not open the specified device, possibly because it is already in use")
Exception: Can not open the specified device, possibly because it is already in use
2012-04-09 15:16:51.118   [100]   X6500 board A40146TT: Traceback (most recent call last):
  File "C:\Users\Desktop\X6500_Easy_Package_For_Windows\mpbm-v0.1.0beta\modules\fpgamining\x6500\x6500worker.py", line 211, in main
    elif data[0] == "dying": raise Exception("Proxy died!")
Exception: Proxy died!

I get this error on two of my boards.  The rest work fine.  Not sure why.

This might also be a remnant of a previously running MPBM instance that didn't shut down all board proxys properly (e.g. because they were uploading a bitstream when MPBM was shutting down). You might want to look for stray python processes and kill them.

My tip jar: 13kwqR7B4WcSAJCYJH1eXQcxG5vVUwKAqY
coblee
Donator
Legendary
*
Offline Offline

Activity: 1204


Creator of Litecoin. Director of Eng at Coinbase.


View Profile
April 10, 2012, 12:29:18 AM
 #257

Using the testing branch, I get this error on my Mac:

Quote
2012-04-09 17:26:20.918   [100]   X6500 worker - AH00WI18: Traceback (most recent call last):
  File "/Users/charlie/Modular-Python-Bitcoin-Miner/modules/fpgamining/x6500/x6500worker.py", line 208, in main
    data = self.rxconn.recv()
EOFError

Any ideas?

coretechs
Donator
Sr. Member
*
Offline Offline

Activity: 362



View Profile
April 10, 2012, 05:01:10 AM
 #258

Try the testing branch. It seems to fix that error.

Switching to the test branch fixed the int/iterate error.  Running perfectly now, thanks.


On a separate note I wanted to mention an observation and see if anyone else is noticing the same behavior.  It seems that mixing different flavor FPGAs in a single instance of MPBM has will cause more frequent invalids across all FPGAs for both version 0.0.4a and 0.1.0b.  If I separate the x6500s from Icarus units and run each in it's own instance of MPBM, I get significantly fewer invalids.  I know ngzhang had mentioned that Icarus had some minor protocol bugs that account for some invalids, but the x6500s really seem to highlight the problem.  If I run them alone, I can run the 200mhz bitstream for 24+ hours with 0 invalids, but if I add some Icarus units to the same config, the x6500s start throwing intermittent invalids ( %0.3-%0.8 ) and the Icarus units seem to throw a greater amount.  Has anyone noticed similar behavior?

I haven't yet tried running 2 instances of version 0.1.0b and I wanted to ask where to specify the log/monitoring port for a second instance.  I didn't see any reference to the port in the config file. Port settings are in the UI for the frontend, I will give it a try.

http://bitcoindoc.com - The Rise and Rise of Bitcoin | http://nxtportal.org - Nxt blockchain explorer
TheSeven
Hero Member
*****
Offline Offline

Activity: 504


FPGA Mining LLC


View Profile WWW
April 10, 2012, 10:30:16 AM
 #259

Using the testing branch, I get this error on my Mac:

Quote
2012-04-09 17:26:20.918   [100]   X6500 worker - AH00WI18: Traceback (most recent call last):
  File "/Users/charlie/Modular-Python-Bitcoin-Miner/modules/fpgamining/x6500/x6500worker.py", line 208, in main
    data = self.rxconn.recv()
EOFError

Any ideas?

The real error message is probably a couple of lines above that.
This one just means that the board proxy connection closed unexpectedly. The proxy should have reported an error before dying.

My tip jar: 13kwqR7B4WcSAJCYJH1eXQcxG5vVUwKAqY
TheSeven
Hero Member
*****
Offline Offline

Activity: 504


FPGA Mining LLC


View Profile WWW
April 10, 2012, 10:32:34 AM
 #260

Try the testing branch. It seems to fix that error.

Switching to the test branch fixed the int/iterate error.  Running perfectly now, thanks.


On a separate note I wanted to mention an observation and see if anyone else is noticing the same behavior.  It seems that mixing different flavor FPGAs in a single instance of MPBM has will cause more frequent invalids across all FPGAs for both version 0.0.4a and 0.1.0b.  If I separate the x6500s from Icarus units and run each in it's own instance of MPBM, I get significantly fewer invalids.  I know ngzhang had mentioned that Icarus had some minor protocol bugs that account for some invalids, but the x6500s really seem to highlight the problem.  If I run them alone, I can run the 200mhz bitstream for 24+ hours with 0 invalids, but if I add some Icarus units to the same config, the x6500s start throwing intermittent invalids ( %0.3-%0.8 ) and the Icarus units seem to throw a greater amount.  Has anyone noticed similar behavior?

I haven't yet tried running 2 instances of version 0.1.0b and I wanted to ask where to specify the log/monitoring port for a second instance.  I didn't see any reference to the port in the config file.

I have no explanation for that kind of behavior. A couple more stales maybe, but invalids just don't make sense. I'm tempted to blame variance...

To run multiple v0.1.x instances, start up one instance and move its WebUI to a different port number in its frontend settings. Then start another one, etc.

My tip jar: 13kwqR7B4WcSAJCYJH1eXQcxG5vVUwKAqY
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 [13] 14 15 16 17 18 19 20 »  All
  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!