Bitcoin Forum
December 10, 2016, 03:13:11 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   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] 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 »
  Print  
Author Topic: (OLD) BFGMiner: modular FPGA/GPU, GBT, Stratum, RPC, Avalon/Lnx/OpnWrt/PPA/W64  (Read 245121 times)
HolyScott
Full Member
***
Offline Offline

Activity: 160



View Profile WWW
October 31, 2012, 04:29:22 PM
 #381

2.9.1 Mining nicely on a Raspberry Pi, however I do get Comm Error disconnects randomly with 4x BFL Singles. Google search lead me to the issue board, and post discussing that this is due to the usb problems on the raspberry pi. I have a 512 MB RPi on order to see if the new reversion fixes the issue.

1481382791
Hero Member
*
Offline Offline

Posts: 1481382791

View Profile Personal Message (Offline)

Ignore
1481382791
Reply with quote  #2

1481382791
Report to moderator
1481382791
Hero Member
*
Offline Offline

Posts: 1481382791

View Profile Personal Message (Offline)

Ignore
1481382791
Reply with quote  #2

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

Posts: 1481382791

View Profile Personal Message (Offline)

Ignore
1481382791
Reply with quote  #2

1481382791
Report to moderator
creativex
Sr. Member
****
Offline Offline

Activity: 420



View Profile
October 31, 2012, 04:36:52 PM
 #382

New version(2.9.1) does NOT crash windows 7 x64 for me. Current uptime with new version approximately 12hrs on W8x64 & 8hrs on W7x64. Previous version(2.8.2) crashed windoze within minutes. Whatever ya done, TY! Donation inbound.

https://bitcointalk.org/index.php?topic=130982.msg1401799#msg1401799 - [BTC-TC]bASIC-MINING
http://forum.litecoin.net/index.php/topic,886.0.html - [LTC-GLOBAL]LTC-DMF
http://forum.litecoin.net/index.php/topic,817.msg3279.html#msg3279 - [CRYPTOSTOCKS]AGLTC

BTC: 1Hfp99tugY4H5FYEoM3hj4JDLzShzZ9ifB

You have zero chance of changing others and only a slim chance at changing yourself. Be the change you want to see and others may follow.
Luke-Jr
Legendary
*
Offline Offline

Activity: 2100



View Profile
October 31, 2012, 06:22:20 PM
 #383

2.9.1 Mining nicely on a Raspberry Pi, however I do get Comm Error disconnects randomly with 4x BFL Singles. Google search lead me to the issue board, and post discussing that this is due to the usb problems on the raspberry pi. I have a 512 MB RPi on order to see if the new reversion fixes the issue.
As I understand it, there's a way to upgrade the firmware on old revisions too.

BitMinerN8
Hero Member
*****
Offline Offline

Activity: 626


Mining since May 2011.


View Profile
October 31, 2012, 07:20:18 PM
 #384

2.9.1 Mining nicely on a Raspberry Pi, however I do get Comm Error disconnects randomly with 4x BFL Singles. Google search lead me to the issue board, and post discussing that this is due to the usb problems on the raspberry pi. I have a 512 MB RPi on order to see if the new reversion fixes the issue.
As I understand it, there's a way to upgrade the firmware on old revisions too.

Raspberry Pi Update Tool
https://github.com/Hexxeh/rpi-update

And there is a newer Raspbian build posted on 10/28.
http://www.raspberrypi.org/downloads
HolyScott
Full Member
***
Offline Offline

Activity: 160



View Profile WWW
November 01, 2012, 04:34:31 AM
 #385



Raspberry Pi Update Tool
https://github.com/Hexxeh/rpi-update

And there is a newer Raspbian build posted on 10/28.
http://www.raspberrypi.org/downloads

[/quote]

I should have the newest build as I update / upgrade  / dist-upgrade on a regular basis.

 I thought the USB problem was hardware, not fixable with firmware, and was address on the new 512 MB memory RPi?

DiCE1904
Legendary
*
Offline Offline

Activity: 925


View Profile
November 01, 2012, 07:52:26 PM
 #386

2.9.1 fixed all the errors I was getting with 9.0

thank you!

ExchangeD.I2p  First Ever Darknet CryptoCurrency Exchange. Trade altcoins anonymously.
http://ylmulgfskl6uiwac4hw4ecwqdzd3oxtwaemzj25zc6k5q4rkexra.b32.i2p
Official Thead: https://bitcointalk.org/index.php?topic=1092682.0
HolyScott
Full Member
***
Offline Offline

Activity: 160



View Profile WWW
November 02, 2012, 02:02:19 AM
 #387

I've switched off the RPi to a Dell Mini 9 Netbook running Lubuntu and all Comm Errors are gone, so still thinking it is a RPi issue.

thirdchance57
Full Member
***
Offline Offline

Activity: 195


★Bitvest.io★ Play Plinko or Invest!


View Profile
November 04, 2012, 09:13:49 PM
 #388

2.9.1 working great on win7 x64
cgminer=problems
guiminer=problems

thanks

Luke-Jr
Legendary
*
Offline Offline

Activity: 2100



View Profile
November 07, 2012, 07:05:25 PM
 #389

NEW VERSION 2.9.2, NOVEMBER 7 2012

I've also bumped the stable release to 2.8.5 including the fixes relevant to the 2.8.x versions.

Human readable changelog:
  • modminer & x6500: New bitstream, improving functional performance by about 10 Mh/s on average. You'll need to power cycle your device, or use the new --force-dev-init option to upload the new bitstream. (thanks wizkid057!)
  • x6500: Support for temperature sensors, including --temp-target & co.
  • x6500: Extended per-FPGA details in RPC API.
  • x6500: Support for older X6500 devices by manually specifying their serial numbers as --scan-serial x6500:serialnumber.
  • Some basic stratum transparency checks to help keep pools accountable using new mining.get_transactions method.

Full changelog
  • Add endian swap defines for where missing.
  • Only retarget stratum shares to new pool diff if diff has dropped.
  • Bugfix: x6500: Use json_object_set_new to correctly count references to per-FPGA RPC data
  • Bugfix: modminer: Use json_object_set_new to correctly count references to per-FPGA RPC data
  • Bugfix: Only append newline when printing protocol data
  • Bugfix: Use memchr to look for newlines in socket line data, since the buffer isn't null terminated
  • Bugfix: Ensure GETWORK_MODE_GBT isn't replaced with GETWORK_MODE_POOL
  • Count lost stratum share submits and increase message priority to warning.
  • Show which pool untracked share messages have come from.
  • Sleep 5 seconds before retrying submit.
  • Changes to build prototypes to support building on FreeBSD 9.1-RC2 amd64
  • Count lost shares with stratum as submit stale lost.
  • Discard record of stratum shares sent and report lost shares on disconnection since they will never be reported back.
  • Check that count of transactions received via stratum is reasonable
  • Use realloc'd data_buffer to support stratum lines longer than 8 KB, and parse stratum responses during auth
  • Use mining.get_transactions to check for stratum pool transparency (actual response ignored for now)
  • ztex: Silence false "unexpected" hardware errors, and don't count them as hw errors
  • README: Update build instructions to reflect current reality
  • x6500: Expose per-FPGA details to RPC API
  • x6500: Implement support for --temp-target
  • x6500: Increase default clock frequency to 200 Mhz, now that new bitstream seems to run well around that
  • x6500: Flush nonces in FPGA buffer at initialization to avoid false hw errors on restart
  • x6500: Release device lock sooner during initialization, before logging initial frequency info
  • x6500: Read temperature sensors after sending work, when enabled
  • Bugfix: jtag: Fix optimized register reading code (it was reading an extra bit before the last, corrupting outside the buffer)
  • Implement new --force-dev-init option to force bitstream upload to modminer and x6500 devices
  • Bugfix: x6500: Include --scan-serial option even for x6500-only builds
  • Bugfix: ztex: Include --scan-serial option even for ztex-only builds, so it can be used to disable autodetect if needed
  • FPGA-README: Discuss X6500 --scan-serial usage of cases where it may be needed
  • ft232r: If we are searching for a specific serial, pay no attention to the product id
  • x6500: Try a more flexible approach to applying dynclock logic
  • Bugfix: dynclock: Use standard C struct initializer to handle initialization, instead of memsetting memory to nulls
  • x6500: Whenever we get a hardware error, purge buffers just in case of read/write desync
  • Bugfix: x6500: When purging ft232r buffers (during bitstream upload), also clear JTAG delayed read counter to avoid any potential desync
  • Bugfix: ft232r: Always flush writes before purging buffers, and empty local read buffer when flushing ftdi read buffer
  • There is no need for addrinfo any more.
  • Fix filename for x6500 bitstream to match previous commit's rename
  • Rename x6500 bitstream to match existing licensing naming setup
  • x6500 dual temp sensor support
  • x6500 is far more stable with its own bitstream

creativex
Sr. Member
****
Offline Offline

Activity: 420



View Profile
November 07, 2012, 07:23:37 PM
 #390

2.9.2 up and running on W8x64 w/o incident.

https://bitcointalk.org/index.php?topic=130982.msg1401799#msg1401799 - [BTC-TC]bASIC-MINING
http://forum.litecoin.net/index.php/topic,886.0.html - [LTC-GLOBAL]LTC-DMF
http://forum.litecoin.net/index.php/topic,817.msg3279.html#msg3279 - [CRYPTOSTOCKS]AGLTC

BTC: 1Hfp99tugY4H5FYEoM3hj4JDLzShzZ9ifB

You have zero chance of changing others and only a slim chance at changing yourself. Be the change you want to see and others may follow.
vitruvio
Sr. Member
****
Offline Offline

Activity: 467



View Profile
November 07, 2012, 08:13:11 PM
 #391

Same issues with hashrate as version 2.9.0 and 2.9.1.

It happens only to me?

Regards
abracadabra
Hero Member
*****
Offline Offline

Activity: 946



View Profile
November 08, 2012, 12:15:31 AM
 #392

Trying to use bfgminer 2.9.2 with an x6500

Have installed WinUSB driver (v6.1.7600.16385)

I will usually get the following upon a bfgminer start:

Code:
5s:  0.0 avg:  0.0 u:  0.0 kh/s | A:0  R:0  HW:0  E:0%  U:0.0/m
 TQ: 0  ST: 11  SS: 0  DW: 5  NB: 2  GW: 6  LW: 28  GF: 0  RF: 0
 Connected to us.ozco.in with LP as user abracadabra.xxx
 Block: 0000024c01b18842d9142711...  Started: [18:11:31]  Best share: 0
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 OCL 0:                | OFF  /  0.0/  0.0kh/s | A:0 R:0 HW:0 U:0.00/m
 XBS 0:                |   0.0/  0.0/  0.0kh/s | A:0 R:0 HW:0 U:0.00/m
--------------------------------------------------------------------------------

 [2012-11-07 18:08:58] XBS 0.0: FPGA not programmed
 [2012-11-07 18:08:58] XBS 0: Programming AH00WPJ0...
 [2012-11-07 18:09:14] XBS 0: Programming AH00WPJ0... 25% complete...
 [2012-11-07 18:09:30] XBS 0: Programming AH00WPJ0... 50% complete...
 [2012-11-07 18:09:46] XBS 0: Programming AH00WPJ0... 75% complete...
 [2012-11-07 18:10:01] XBS 0: Programming AH00WPJ0... 100% complete...
 [2012-11-07 18:10:02] XBS 0: Done programming AH00WPJ0
 [2012-11-07 18:11:31] LONGPOLL from pool 0 detected new block
 [2012-11-07 18:11:36] XBS 0.0: Flushed 2251 nonces from buffer at init
 [2012-11-07 18:11:36] XBS 0.0: Frequency set to 200 Mhz (range: 2-250)
 [2012-11-07 18:11:36] XBS 0: JTAG detect returned -1
 [2012-11-07 18:11:36] Thread 3 failure, exiting

then sometimes:

Code:
bfgminer version 2.9.2 - Started: [2012-11-07 18:12:31] - [  0 days 00:00:09]
--------------------------------------------------------------------------------
 5s:  0.0 avg:  0.0 u:  0.0 kh/s | A:0  R:0  HW:0  E:0%  U:0.0/m
 TQ: 0  ST: 5  SS: 0  DW: 0  NB: 1  GW: 1  LW: 8  GF: 0  RF: 0
 Connected to us.ozco.in with LP as user abracadabra.yiannaki
 Block: 0000024c01b18842d9142711...  Started: [18:12:31]  Best share: 0
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 OCL 0:                | OFF  /  0.0/  0.0kh/s | A:0 R:0 HW:0 U:0.00/m
 XBS 0:                |   0.0/  0.0/  0.0kh/s | A:0 R:0 HW:0 U:0.00/m
--------------------------------------------------------------------------------

 [2012-11-07 18:12:30] Probing for an alive pool
 [2012-11-07 18:12:31] Long-polling activated for http://us.ozco.in:8332/LP (get
work)
 [2012-11-07 18:12:31] Disabling extra threads due to dynamic mode.
 [2012-11-07 18:12:31] Tune dynamic intensity with --gpu-dyninterval
 [2012-11-07 18:12:31] XBS 0: JTAG error reading user code
 [2012-11-07 18:12:31] Thread 2 failure, exiting
 [2012-11-07 18:12:31] XBS 0: JTAG detect returned -2
 [2012-11-07 18:12:31] Thread 3 failure, exiting


after a power cycle I'll sometimes get:
Code:
bfgminer version 2.9.2 - Started: [2012-11-07 18:13:38] - [  0 days 00:00:15]
--------------------------------------------------------------------------------
 5s:  0.0 avg:  0.0 u:  0.0 kh/s | A:0  R:0  HW:0  E:0%  U:0.0/m
 TQ: 0  ST: 5  SS: 0  DW: 0  NB: 1  GW: 1  LW: 8  GF: 0  RF: 0
 Connected to us.ozco.in with LP as user abracadabra.yiannaki
 Block: 0000024c01b18842d9142711...  Started: [18:13:38]  Best share: 0
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 OCL 0:                | OFF  /  0.0/  0.0kh/s | A:0 R:0 HW:0 U:0.00/m
 XBS 0:                |   0.0/  0.0/  0.0kh/s | A:0 R:0 HW:0 U:0.00/m
--------------------------------------------------------------------------------

 [2012-11-07 18:13:38] Probing for an alive pool
 [2012-11-07 18:13:38] Long-polling activated for http://us.ozco.in:8332/LP (get
work)
 [2012-11-07 18:13:39] Disabling extra threads due to dynamic mode.
 [2012-11-07 18:13:39] Tune dynamic intensity with --gpu-dyninterval
 [2012-11-07 18:13:39] XBS 0: JTAG detect returned -1
 [2012-11-07 18:13:39] Thread 2 failure, exiting
 [2012-11-07 18:13:39] XBS 0: JTAG detect returned -1
 [2012-11-07 18:13:39] Thread 3 failure, exiting


then after multiple restarts of bfgminer I'll get:

Code:
bfgminer version 2.9.2 - Started: [2012-11-07 18:14:06] - [  0 days 00:00:39]
--------------------------------------------------------------------------------
 5s:  0.0 avg:  0.0 u:  0.0 kh/s | A:0  R:0  HW:0  E:0%  U:0.0/m
 TQ: 0  ST: 5  SS: 0  DW: 0  NB: 1  GW: 1  LW: 8  GF: 0  RF: 0
 Connected to us.ozco.in with LP as user abracadabra.yiannaki
 Block: 0000024c01b18842d9142711...  Started: [18:14:06]  Best share: 0
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 OCL 0:                | OFF  /  0.0/  0.0kh/s | A:0 R:0 HW:0 U:0.00/m
 XBS 0:   60%          |   0.0/  0.0/  0.0kh/s | A:0 R:0 HW:0 U:0.00/m
--------------------------------------------------------------------------------

 [2012-11-07 18:14:06] Probing for an alive pool
 [2012-11-07 18:14:06] Long-polling activated for http://us.ozco.in:8332/LP (get
work)
 [2012-11-07 18:14:06] Disabling extra threads due to dynamic mode.
 [2012-11-07 18:14:06] Tune dynamic intensity with --gpu-dyninterval
 [2012-11-07 18:14:06] XBS 0: JTAG detect returned -1
 [2012-11-07 18:14:06] Thread 2 failure, exiting
 [2012-11-07 18:14:06] XBS 0.1: FPGA not programmed
 [2012-11-07 18:14:06] XBS 0: Programming AH00WPJ0...
 [2012-11-07 18:14:23] XBS 0: Programming AH00WPJ0... 25% complete...
 [2012-11-07 18:14:39] XBS 0: Programming AH00WPJ0... 50% complete...
 [2012-11-07 18:14:50] LONGPOLL from pool 0 requested work restart
 [2012-11-07 18:14:54] XBS 0: Programming AH00WPJ0... 75% complete...
 [2012-11-07 18:15:09] XBS0: Idle for more than 60 seconds, declaring SICK!
 [2012-11-07 18:15:09] XBS0: Attempting to restart
 [2012-11-07 18:15:10] XBS 0: Programming AH00WPJ0... 100% complete...
 [2012-11-07 18:15:11] Thread 3 failure, exiting
 [2012-11-07 18:15:12] XBS0: Idle for more than 60 seconds, declaring SICK!
 [2012-11-07 18:15:12] XBS0: Attempting to restart


Any help?

HolyScott
Full Member
***
Offline Offline

Activity: 160



View Profile WWW
November 08, 2012, 04:00:11 PM
 #393

Git hub still compiling as 2.9.1

Luke-Jr
Legendary
*
Offline Offline

Activity: 2100



View Profile
November 08, 2012, 06:36:23 PM
 #394

Git hub still compiling as 2.9.1
It's important to re-run autogen.sh

purelithium
Hero Member
*****
Offline Offline

Activity: 504



View Profile
November 10, 2012, 08:10:51 PM
 #395

After running 2.9.2 for a little over 2 days, I haven't noticed any hashing improvement with my MMQ.

Like my post? 1H7bfRYh7F89mfmFgsRCdn4awDaUHQmYqY
Luke-Jr
Legendary
*
Offline Offline

Activity: 2100



View Profile
November 10, 2012, 08:22:24 PM
 #396

After running 2.9.2 for a little over 2 days, I haven't noticed any hashing improvement with my MMQ.
Did you reprogram it? You need to either power cycle the MMQ (to clear the programming) or use --force-dev-init

purelithium
Hero Member
*****
Offline Offline

Activity: 504



View Profile
November 10, 2012, 10:48:49 PM
 #397

Yeah I did. It's still hashing at 840mhash, my U is at about 11.4/min It was in that area before, too.

Like my post? 1H7bfRYh7F89mfmFgsRCdn4awDaUHQmYqY
Luke-Jr
Legendary
*
Offline Offline

Activity: 2100



View Profile
November 10, 2012, 10:53:44 PM
 #398

Yeah I did. It's still hashing at 840mhash, my U is at about 11.4/min It was in that area before, too.
Maybe it only works up to a point. I've never seen 840 Mh/s myself.

purelithium
Hero Member
*****
Offline Offline

Activity: 504



View Profile
November 10, 2012, 11:06:05 PM
 #399

Hmm... interesting. I've never had an issue getting it to clock up to 210mhz. The u is usually around 816-817mhash though.

Like my post? 1H7bfRYh7F89mfmFgsRCdn4awDaUHQmYqY
Luke-Jr
Legendary
*
Offline Offline

Activity: 2100



View Profile
November 10, 2012, 11:13:05 PM
 #400

Hmm... interesting. I've never had an issue getting it to clock up to 210mhz. The u is usually around 816-817mhash though.
Well, I let it get rather hot here too; usually at least 80 F.

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 [20] 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 »
  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!