JBT
|
|
September 19, 2013, 05:44:25 PM |
|
ok maybe i read this wrong can i disable the gpu but autoscan for all the usb eruptors?
-S opencl:noauto -S erupter:all lol ty Luke
|
|
|
|
JBT
|
|
September 19, 2013, 06:36:15 PM |
|
i am getting loads of stratum connection to pool 0 interrupted errors
|
|
|
|
OtaconEmmerich
|
|
September 19, 2013, 06:38:34 PM |
|
3.1.4 seems stable, any reason why 3.2.0/1 is so fickle on my PC now? When I first got it it it was stable enough...Odd.
|
|
|
|
HellDiverUK
|
|
September 19, 2013, 08:39:36 PM |
|
Any news on BFG supporting the RedFury USB (2.5GH) miners, Luke? Andreas has provided some code, but I don't have a unit to test with. Just pushed a "bigpic" branch based on Andreas's code merged up, if you want to try it out. It looks like there's a lot of code in there that will be redundant with the metabank/littlefury code, so I should probably merge the two before it'll be 3.3-ready. I don't have one yet, there's a local group buy just starting, so maybe in a few weeks. I'll of course try it if/when the miner appears.
|
|
|
|
Xer0
|
|
September 19, 2013, 11:12:30 PM |
|
when to expect stratum proxy enabled for OpenWRT?
After I decide to write stratum proxy support (or someone else contributes it), at least i tought its already included in the general Linux and rPi source, is it so much different for OpenWRT?
|
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
September 19, 2013, 11:23:43 PM |
|
when to expect stratum proxy enabled for OpenWRT?
After I decide to write stratum proxy support (or someone else contributes it), at least i tought its already included in the general Linux and rPi source, is it so much different for OpenWRT? There is no stratum proxy support in BFGMiner at all right now, but it is a Planned Feature™.
|
|
|
|
2GOOD
|
|
September 20, 2013, 12:48:44 AM |
|
Luke, wanted to give it a try with one blade... on 7x64 I must use 32bit since blades are not supported in x64... but something's wrong with --http-port option, here's what I get: Failed to init bfd from (C:\bfgminer-3.2.1-win32\libplibc-1.dll) 0x6ef48397 : C:\bfgminer-3.2.1-win32\libplibc-1.dll : _win_SetHandleType 0x424eed : C:\bfgminer-3.2.1-win32\bfgminer.exe : /home/luke-jr/Projects/Educati on/Tonal/BitCoin/cgminer/make-release-tmp/bfgminer-3.2.1-tmp/miner.c (10331) : i n function (main) 0x4010bb : C:\bfgminer-3.2.1-win32\bfgminer.exe : crt1.c Failed to init bfd from (C:\Windows\SysWOW64\ntdll.dll) 0x77c39ed2 : C:\Windows\SysWOW64\ntdll.dll : RtlInitializeExceptionChain Failed to init bfd from (C:\Windows\SysWOW64\ntdll.dll) 0x77c39ea5 : C:\Windows\SysWOW64\ntdll.dll : RtlInitializeExceptionChain Without --http-port it is hashing away with one card
|
|
|
|
baby_ghost
Member
Offline
Activity: 89
Merit: 10
|
|
September 20, 2013, 01:47:38 AM |
|
Blade with bfgminer successfully, but I can run it on some seconds only, it started and mine, but when have som reject or another reasons which I don't know, bfgminer windows disappear and gone.
|
|
|
|
Beans
|
|
September 20, 2013, 06:04:16 AM |
|
I need to pick up a pc this week just to run my butterfly singles. LTC mining on the same rig is more trouble then its worth. I would like to get somthing I may have use for down the road. Has anyone been able to run bfgminer on a windows 8 tablet? Easyminer is the only thing I know for sure, that runs on a win tablet but it's complete garbage.
|
|
|
|
HellDiverUK
|
|
September 20, 2013, 07:30:38 AM |
|
Got 3.2.1 running on Windows 7 Enterprise x86 last night. As soon as the Blade connected to BFG, BFG just quit/disappeared. Upon reopening BFG everything worked perfectly. Connected the second Blade, and again BFG quits. I've rebooted etc several times, and BFG is happy now.
To me, it seems BFG quits on the very first instance on a Blade connecting to the HTTP port (perhaps something craps out creating the virtual device?).
3.2.1 works OK on Linux, on the same machine (Intel NUC DCCP847DYE) with 4GB RAM and 30GB Kingston SSD).
|
|
|
|
HellDiverUK
|
|
September 20, 2013, 07:33:58 AM |
|
I need to pick up a pc this week just to run my butterfly singles. LTC mining on the same rig is more trouble then its worth. I would like to get somthing I may have use for down the road. Has anyone been able to run bfgminer on a windows 8 tablet? Easyminer is the only thing I know for sure, that runs on a win tablet but it's complete garbage.
I wouldn't bother - you could pick up a "real" PC for less than a shitty tablet. That said, I don't see why it wouldn't work...
|
|
|
|
vulgartrendkill
|
|
September 20, 2013, 08:29:31 AM |
|
Got 3.2.1 running on Windows 7 Enterprise x86 last night. As soon as the Blade connected to BFG, BFG just quit/disappeared. Upon reopening BFG everything worked perfectly. Connected the second Blade, and again BFG quits. I've rebooted etc several times, and BFG is happy now.
To me, it seems BFG quits on the very first instance on a Blade connecting to the HTTP port (perhaps something craps out creating the virtual device?).
3.2.1 works OK on Linux, on the same machine (Intel NUC DCCP847DYE) with 4GB RAM and 30GB Kingston SSD).
Would you be able to give me an example of the code you used with BFG to get the blades working please? I've got mine at home to set up when I finish work and I7d love to get them up and running asap. Thanks
|
|
|
|
HellDiverUK
|
|
September 20, 2013, 08:51:14 AM |
|
Code? I added the --http-port 8330 command to the shortcut, and pointed the blades at the IP of the machine. As it says in the README.ASIC
|
|
|
|
HellDiverUK
|
|
September 20, 2013, 08:53:51 AM |
|
Luke, wanted to give it a try with one blade... on 7x64 I must use 32bit since blades are not supported in x64... but something's wrong with --http-port option, here's what I get:
It only works on 32-bit. As in, not on 64-bit. Why are you running it on 64-bit and expecting it to work?
|
|
|
|
HellDiverUK
|
|
September 20, 2013, 08:55:47 AM |
|
Got 3.2.1 running on Windows 7 Enterprise x86 last night. As soon as the Blade connected to BFG, BFG just quit/disappeared. Upon reopening BFG everything worked perfectly. Connected the second Blade, and again BFG quits. I've rebooted etc several times, and BFG is happy now.
To me, it seems BFG quits on the very first instance on a Blade connecting to the HTTP port (perhaps something craps out creating the virtual device?).
3.2.1 works OK on Linux, on the same machine (Intel NUC DCCP847DYE) with 4GB RAM and 30GB Kingston SSD).
Scratch that. First time the Blade connects at each reboot, BFG quits. It runs perfectly every time until the next reboot. Blades aren't being restarted, just using the Switch Server function (the backup server are to a stratum_proxy running on my WHS.
|
|
|
|
vulgartrendkill
|
|
September 20, 2013, 08:59:13 AM |
|
Code? I added the --http-port 8330 command to the shortcut, and pointed the blades at the IP of the machine. As it says in the README.ASIC So thats all you have to do for bfg to recognise the cards (excluding set up of blade config page?)
|
|
|
|
2GOOD
|
|
September 20, 2013, 10:12:09 AM |
|
Luke, wanted to give it a try with one blade... on 7x64 I must use 32bit since blades are not supported in x64... but something's wrong with --http-port option, here's what I get:
It only works on 32-bit. As in, not on 64-bit. Why are you running it on 64-bit and expecting it to work? Because x64 Win7 can run x86 apps
|
|
|
|
-Redacted-
|
|
September 20, 2013, 10:13:29 AM |
|
Luke, wanted to give it a try with one blade... on 7x64 I must use 32bit since blades are not supported in x64... but something's wrong with --http-port option, here's what I get:
It only works on 32-bit. As in, not on 64-bit. Why are you running it on 64-bit and expecting it to work? Because x64 Win7 can run x86 apps Unfortunately, even though the app is 32 bit, it's trying to connect to the 64 bit libraries because it's a 64 bit OS...
|
|
|
|
ghostintheshellprompt
Newbie
Offline
Activity: 38
Merit: 0
|
|
September 20, 2013, 10:20:46 AM |
|
Luke, wanted to give it a try with one blade... on 7x64 I must use 32bit since blades are not supported in x64... but something's wrong with --http-port option, here's what I get:
It only works on 32-bit. As in, not on 64-bit. Why are you running it on 64-bit and expecting it to work? Because x64 Win7 can run x86 apps Unfortunately, even though the app is 32 bit, it's trying to connect to the 64 bit libraries because it's a 64 bit OS... Oh yeah?! well i'd rather argue about pointless differences than ever discuss anything of serious merit.
|
|
|
|
-Redacted-
|
|
September 20, 2013, 10:23:20 AM |
|
They may seem pointless to you, but it's the reason it's not working...
|
|
|
|
|