OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 144.

Zeronic

member

Activity: 243

Merit: 10

Quote from: Zeronic on July 30, 2013, 10:39:54 PM

I followed the README.FPGA but using the WinUSB (v6.1.7600.16385) no version of BFGMiner will detect the X6500.

Update: After a Software Update and a reboot, I now get "FTDI reports 1 devices". So from this point I need to add something like the -S X6500:auto to the command string?

Try the -S X6500:auto or just -S all and it still won't mine on the X6500.

Aahzman

hero member

Activity: 602

Merit: 500

Your *what* is itchy?

ah. ok. i'm on 3.1.3, so i'll do that -S thing.

Thanks

Taugeran

hero member

Activity: 658

Merit: 500

CCNA: There i fixed the internet.

Quote from: Aahzman on July 31, 2013, 09:18:43 AM

Quote from: Zeronic on July 31, 2013, 07:57:30 AM

Quote from: Aahzman on July 31, 2013, 05:22:57 AM

Howdy. program works great except for random crashing. I have two BFL 5Gh/s Jalapenos, mining on Slush's pool, Windows 7, 64bit. It'll hum along just fine for a while, and then randomly just stop working. After reading a few pages of this thread, i've restarted it with -D -T args to see if i can get any info about the crashing.

Also, by default it starts up detects/mines with both BFL devices and my GPU. i've looked at the --device|-d command not sure how to get it to do something useful like only enable the BFLs. The devices are listed as

OCL 0
BFL 0
BFL 1

so, would the numbering be as simple as 0, 1 and 2? so if i just want the BFL's used, i would add -d 1-2 to my command line?

I think if you add -G to the command string that will disable the GPU's.

Thanks. Will try that on next crash/restart. :-)

it depends on which version of bfgminer is in use.
3.1.2>= -G should work
3.1.3 forward will be -S OpenCL:noauto

Aahzman

hero member

Activity: 602

Merit: 500

Your *what* is itchy?

Quote from: Zeronic on July 31, 2013, 07:57:30 AM

Quote from: Aahzman on July 31, 2013, 05:22:57 AM

Howdy. program works great except for random crashing. I have two BFL 5Gh/s Jalapenos, mining on Slush's pool, Windows 7, 64bit. It'll hum along just fine for a while, and then randomly just stop working. After reading a few pages of this thread, i've restarted it with -D -T args to see if i can get any info about the crashing.

Also, by default it starts up detects/mines with both BFL devices and my GPU. i've looked at the --device|-d command not sure how to get it to do something useful like only enable the BFLs. The devices are listed as

OCL 0
BFL 0
BFL 1

so, would the numbering be as simple as 0, 1 and 2? so if i just want the BFL's used, i would add -d 1-2 to my command line?

I think if you add -G to the command string that will disable the GPU's.

Thanks. Will try that on next crash/restart. :-)

Zeronic

member

Activity: 243

Merit: 10

Quote from: Aahzman on July 31, 2013, 05:22:57 AM

Howdy. program works great except for random crashing. I have two BFL 5Gh/s Jalapenos, mining on Slush's pool, Windows 7, 64bit. It'll hum along just fine for a while, and then randomly just stop working. After reading a few pages of this thread, i've restarted it with -D -T args to see if i can get any info about the crashing.

Also, by default it starts up detects/mines with both BFL devices and my GPU. i've looked at the --device|-d command not sure how to get it to do something useful like only enable the BFLs. The devices are listed as

OCL 0
BFL 0
BFL 1

so, would the numbering be as simple as 0, 1 and 2? so if i just want the BFL's used, i would add -d 1-2 to my command line?

I think if you add -G to the command string that will disable the GPU's.

Aahzman

hero member

Activity: 602

Merit: 500

Your *what* is itchy?

Howdy. program works great except for random crashing. I have two BFL 5Gh/s Jalapenos, mining on Slush's pool, Windows 7, 64bit. It'll hum along just fine for a while, and then randomly just stop working. After reading a few pages of this thread, i've restarted it with -D -T args to see if i can get any info about the crashing.

Also, by default it starts up detects/mines with both BFL devices and my GPU. i've looked at the --device|-d command not sure how to get it to do something useful like only enable the BFLs. The devices are listed as

OCL 0
BFL 0
BFL 1

so, would the numbering be as simple as 0, 1 and 2? so if i just want the BFL's used, i would add -d 1-2 to my command line?

Zeronic

member

Activity: 243

Merit: 10

I followed the README.FPGA but using the WinUSB (v6.1.7600.16385) no version of BFGMiner will detect the X6500.

Update: After a Software Update and a reboot, I now get "FTDI reports 1 devices". So from this point I need to add something like the -S X6500:auto to the command string?

jml

full member

Activity: 238

Merit: 100

Quote from: jml on July 30, 2013, 06:14:16 PM

Quote from: Luke-Jr on July 30, 2013, 04:54:26 PM

Quote from: jml on July 30, 2013, 04:38:19 PM

Update: HUPed after 3 hours operation.

What do you mean by HUPed?
The HUP signal is sent when you close the terminal...

HUP happens because I use SSH to open a terminal. When I try to SSH back in, I can't. This is why I need to power it down and then back up again.

I recommend running BFGMiner inside GNU Screen.

I have been using GNU screen all along.

RoboCoder

sr. member

Activity: 388

Merit: 250

Save A Life, Adopt a Pet Today!

Quote from: Luke-Jr on July 30, 2013, 07:13:33 PM

Quote from: RoboCoder on July 30, 2013, 06:59:22 PM

I have exactly this same problem. If i run 3.11 they are reconized and work properly, but if i run 3.13 i get the same error. (so i am running

OH! I do have a fix for a X6500 regression slated for 3.1.4. Just didn't realize it manifested this way >_<

Stay tuned, probably just a few more days...

If you'd like to help test now, the latest git is always available from WeBisect.

I downloaded the win64 to test. It worked with both the x6500's and the ModMiners just fine. Yay! Thanks. Will let you know if i see any problems.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: Zeronic on July 30, 2013, 05:50:30 PM

Quote from: Luke-Jr on July 30, 2013, 01:24:24 PM

Quote from: Zeronic on July 30, 2013, 08:10:23 AM

Results of working on getting BFGMiner to work with X6500.

Using libusb-win32_1.2.6.0
http://sourceforge.net/projects/libusb-win32/?source=dlp

http://pastebin.com/bn8tecQT

Luke can we got a known working version or a better suggestion please?

All current versions are known working - I wouldn't release them if they didn't work.
There is no sign of a X6500 on your USB bus in the pastebin, with or without the correct driver.
X6500 is 0403:6001

http://tinypic.com/r/26126g5/5

I'm kind of lost at this point.

Be sure you're using Zadig the way described in README.FPGA

Quote from: jml on July 30, 2013, 06:14:16 PM

Quote from: Luke-Jr on July 30, 2013, 04:54:26 PM

Quote from: jml on July 30, 2013, 04:38:19 PM

Update: HUPed after 3 hours operation.

What do you mean by HUPed?
The HUP signal is sent when you close the terminal...

HUP happens because I use SSH to open a terminal. When I try to SSH back in, I can't. This is why I need to power it down and then back up again.

I recommend running BFGMiner inside GNU Screen.

Quote from: RoboCoder on July 30, 2013, 06:59:22 PM

I have exactly this same problem. If i run 3.11 they are reconized and work properly, but if i run 3.13 i get the same error. (so i am running

OH! I do have a fix for a X6500 regression slated for 3.1.4. Just didn't realize it manifested this way >_<

Stay tuned, probably just a few more days...

If you'd like to help test now, the latest git is always available from WeBisect.

RoboCoder

sr. member

Activity: 388

Merit: 250

Save A Life, Adopt a Pet Today!

Quote from: Zeronic on July 30, 2013, 05:50:30 PM

Quote from: Luke-Jr on July 30, 2013, 01:24:24 PM

Quote from: Zeronic on July 30, 2013, 08:10:23 AM

Results of working on getting BFGMiner to work with X6500.

Using libusb-win32_1.2.6.0
http://sourceforge.net/projects/libusb-win32/?source=dlp

http://pastebin.com/bn8tecQT

Luke can we got a known working version or a better suggestion please?

All current versions are known working - I wouldn't release them if they didn't work.
There is no sign of a X6500 on your USB bus in the pastebin, with or without the correct driver.
X6500 is 0403:6001

http://tinypic.com/r/26126g5/5

I'm kind of lost at this point.

I have exactly this same problem. If i run 3.11 they are reconized and work properly, but if i run 3.13 i get the same error. (so i am running

jml

full member

Activity: 238

Merit: 100

Quote from: Luke-Jr on July 30, 2013, 04:54:26 PM

Quote from: jml on July 30, 2013, 04:38:19 PM

Update: HUPed after 3 hours operation.

What do you mean by HUPed?
The HUP signal is sent when you close the terminal...

HUP happens because I use SSH to open a terminal. When I try to SSH back in, I can't. This is why I need to power it down and then back up again.

Zeronic

member

Activity: 243

Merit: 10

Quote from: Luke-Jr on July 30, 2013, 01:24:24 PM

Quote from: Zeronic on July 30, 2013, 08:10:23 AM

Results of working on getting BFGMiner to work with X6500.

Using libusb-win32_1.2.6.0
http://sourceforge.net/projects/libusb-win32/?source=dlp

http://pastebin.com/bn8tecQT

Luke can we got a known working version or a better suggestion please?

All current versions are known working - I wouldn't release them if they didn't work.
There is no sign of a X6500 on your USB bus in the pastebin, with or without the correct driver.
X6500 is 0403:6001

http://tinypic.com/r/26126g5/5

I'm kind of lost at this point.

Xer0

hero member

Activity: 826

Merit: 1000

°^°

runs very well on a TP-Link MR3020 (WR703N)

Thanks!

(now i just need come watchdog stuff for failsafe things)

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: jml on July 30, 2013, 04:38:19 PM

Update: HUPed after 3 hours operation.

What do you mean by HUPed?
The HUP signal is sent when you close the terminal...

jml

full member

Activity: 238

Merit: 100

Quote from: jml on July 30, 2013, 04:30:04 PM

Luke,

I have been running CM1's within a single USB channel and allowed ZTEX and BE's to run on another USB channel connected to the raspberry pi.

So here is the way they are connected:

Raspberry pi = 2 USB ports (a)

(a) 1 USB port has USB 4 port hub (1)
(a) 1 USB port has USB 4 port hub (2)

(1) 4 port hub has one ZTEX link and 2 DLINK 7 port hub links
(2) 4 port hub has 2 CM1's connected

I think the CM1's and BE's don't seem to like sharing the same USB hub channel. That is my theory for now.
I have had these running now for 3+ hours as the pi usually HUPs in about one hour.

Update: HUPed after 3 hours operation.

jml

full member

Activity: 238

Merit: 100

Luke,

I have been running CM1's within a single USB channel and allowed ZTEX and BE's to run on another USB channel connected to the raspberry pi.

So here is the way they are connected:

Raspberry pi = 2 USB ports (a)

(a) 1 USB port has USB 4 port hub (1)
(a) 1 USB port has USB 4 port hub (2)

(1) 4 port hub has one ZTEX link and 2 DLINK 7 port hub links
(2) 4 port hub has 2 CM1's connected

I think the CM1's and BE's don't seem to like sharing the same USB hub channel. That is my theory for now.
I have had these running now for 3+ hours as the pi usually HUPs in about one hour.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: Zeronic on July 30, 2013, 08:10:23 AM

Results of working on getting BFGMiner to work with X6500.

Using libusb-win32_1.2.6.0
http://sourceforge.net/projects/libusb-win32/?source=dlp

http://pastebin.com/bn8tecQT

Luke can we got a known working version or a better suggestion please?

All current versions are known working - I wouldn't release them if they didn't work.
There is no sign of a X6500 on your USB bus in the pastebin, with or without the correct driver.
X6500 is 0403:6001

jml

full member

Activity: 238

Merit: 100

I had running the ztex fpga with the BE and no problems; has been running for more than 12 hours.

Zeronic

member

Activity: 243

Merit: 10

Results of working on getting BFGMiner to work with X6500.

Using libusb-win32_1.2.6.0
http://sourceforge.net/projects/libusb-win32/?source=dlp

http://pastebin.com/bn8tecQT

Luke can we got a known working version or a better suggestion please?

Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 144. (Read 1193368 times)