Can anyone help me with a lightening X6?
I can't get it running with CGMiner to save my life.
Thanks!
Whats a "lightening X6"? Don't see it in the list of supported hardware in the top post. |
|
|
|
Edit: So do think this is a fix or a preliminary test? Also what is the driver instance name for the --usb options?
Thanks a bunch, again.
This code should just become part of the next release. It's still all under the same device name for all bflsc driver devices so BAS. The code was never rewritten to account for variants detected after the fact and black/whitelist them (it would be a massive rewrite and manufacturers have all but made this venture worthless). -ck, Did this fix for the Monarch's make into the git tree yet? Thanks, Sam |
|
|
|
This pool uses clustering from its I7 core to load balance across multiple CPU cores which in turn earn you more bitcoin. Over the short term you will earn 30-40% more bitcoin then other pools.
O_o how are you magically generating 30% more bitcoins over the short term? what do you define as short term? It's all in the I7 man. That's awesome CPU you know.  |
|
|
|
I'm plugging into the back of my tower, so directly, should be USB 2.0, it's not blue so pretty sure not 3.0.
Ok, as a last straw you can try going through a USB 2.0 hub anyway and see what happens. What power supply are you using to power the miner? Are all the fans spinning up? I don't have a hub lying around so I'll have to get one and try. My PSU is an ULTRA X4 750W. 12V, 56A, all fans spinning up. dunno, sounds like bad hardware to me. You may want to contact the Manufacture's support. |
|
|
|
I'm plugging into the back of my tower, so directly, should be USB 2.0, it's not blue so pretty sure not 3.0.
Ok, as a last straw you can try going through a USB 2.0 hub anyway and see what happens. What power supply are you using to power the miner? Are all the fans spinning up? |
|
|
|
Is it supposed to be FTDI manufacturer?
No, its supposed to be WinUSB. Is CGMiner giving you an error message? If so why no post the text so we know what it is?  sorry had it as a link earlier in thread. Try this. I've had similar issues. In device manager un-install the USB devices, check the box delete the driver software for this device. Un-install all monarchs (if more than one you'll see). Then refresh your device manager and you will see the ftdi drivers come back. Now install WinUSB with zdiag. Try that. Still shows as FTDI manufacturer. Well, yeah, FTDI is the USB hardware manufacture. But does Zadig show it using the WinUSB driver as your previous screen shot showed? |
|
|
|
Is it supposed to be FTDI manufacturer?
No, its supposed to be WinUSB. Is CGMiner giving you an error message? If so why no post the text so we know what it is? sorry had it as a link earlier in thread. Are you plugging this directly into your PC's USB port? If so USB 1.1, 2.0 or 3.0? Or are you going through a Hub? It seems like a hardware issue like Kano said. Especially since it happens immediately. Oh, as for links I don't click on them. You can also copy and paste the text too. |
|
|
|
Is it supposed to be FTDI manufacturer?
No, its supposed to be WinUSB. Is CGMiner giving you an error message? If so why no post the text so we know what it is? |
|
|
|
Is this what you're asking for? C:\cgm491>CGMINER -D -T
[2015-03-21 17:30:07] Started cgminer 4.9.1
[2015-03-21 17:30:08] USB init - BAS device 5:1 usbver=0200 prod='BitFORCE SHA256 SC' manuf='BUTTERFLY LABS' serial='FTYM9T5M'
Yes that's it. Try this: http://ck.kolivas.org/apps/cgminer/temp/cgminer.exeI am having this same problem, I'm new to Monarch mining, had a Jalapeno. Do I have to compile my own cgminer or can I put that file into 4.9.1 folder and run from there? If your running M$ Windoze, like me, then just replace the executable with that one. If your running linux of some sort then you'll need to get the code that has this fix and compile it. |
|
|
|
How many times has this been asked? Maybe a hundred or two?
If it were only that many times. At least your asking what the best pools is instead of which pool makes you the most BTC with N hasrate. But still it's a subjective personal choice most of the time. But to attempt to be objective, not knowing what your goal or hashrate is, I would say BTC Guild. That is the most reliable pool going that I know of. Don't know much about Slush as I have never used it, except it is one of the first pools. If you want to solo mine then I would say ck's solo pool. Good Luck, and try to have fun. |
|
|
|
Does it matter if I use a 10/100 switch for mining or do I need a gigabit.
10Mb is more than enough. |
|
|
|
woke up this morning to see that the pool found 6 blocks, good stuff!
Yep an not too shabby yesterday either. Hoping for a few more today. You got your wish and the day is still not over =) Yep, definitely a good run today. |
|
|
|
woke up this morning to see that the pool found 6 blocks, good stuff!
Yep an not too shabby yesterday either. Hoping for a few more today. |
|
|
|
|
eleuthria,
What do you recommend for auto payouts? Is .1 BTC too dusty? or should it be higher? I don't want too many unexpected fee's when I try to use my BTC. Just wondering what you thought a good number was.
Thanks,
Sam
|
|
|
|
Try http:// before the IP address. cgminer.exe -o http://127.0.0.1:8332 -u (name) -p (password) --btc-address (address) Doh, thanks. Working. Glad to hear it. Happy solo mining. |
|
|
|
I am having a bit of difficulty getting solo mining to work. I run a full node (PIX >8.5), I can mine to pools no problem, so the problem is internal somewhere. My bitcoin.conf file looks like server=1
rpcuser=(name)
rpcpassword=(password)
rpcallowip=127.0.0.1
rpcport=8332
I start cgminer 4.9.0 with cgminer.exe -o 127.0.0.1:8332 -u (name) -p (password) --btc-address (address)
and I end up with  and never seem to "connect" and the program closes. Any ideas what I'm doing wrong? Try http:// before the IP address. cgminer.exe -o http://127.0.0.1:8332 -u (name) -p (password) --btc-address (address) |
|
|
|
There are lot of scam site are there on internet making people fool and get money and after few days get down in now a days few scam sites already down within just 3 or 4 months. If You wish to go for secure, trusted, honest and reliable platform for mining for free or even with investment then You must check here http://digitalbit.co.in/hashocean-cloud-mining/ They gives free 15GHS for every new user even they are from 2012 in the market They provides High earning power even High Returns. Even they are in this industry since 2012 you can check User with their registration date and returns they received. It website i first see , it website is reliable ? Nobody talking about this on website. I've never heard of it. Not that means anything I guess. |
|
|
|
thank you than i have a Long way, my "bestshare": 5551979194.5580816  Yep, a long way to go. But that is still a very nice share. What's your, approximate, hashrate? |
|
|
|
Is this what you're asking for? C:\cgm491>CGMINER -D -T
[2015-03-21 17:30:07] Started cgminer 4.9.1
[2015-03-21 17:30:08] USB init - BAS device 5:1 usbver=0200 prod='BitFORCE SHA256 SC' manuf='BUTTERFLY LABS' serial='FTYM9T5M'
Yes that's it. Try this: http://ck.kolivas.org/apps/cgminer/temp/cgminer.exeThat did it, it's hashing. Thanks, Sam Edit: So do think this is a fix or a preliminary test? Also what is the driver instance name for the --usb options? Thanks a bunch, again. |
|
|
|
They identify themselves to Windoze as BitFORCE SHA256 SC and CGMiner 4.9.1 identifies them as a BAS. What does the iManufacturer field list? Is this what your asking for? C:\cgm491>CGMINER -D -T
[2015-03-21 17:30:07] Started cgminer 4.9.1
snip
[2015-03-21 17:30:08] USB scan devices: checking for BAS devices
[2015-03-21 17:30:08] BAS looking for BAS 0403:6014 but found 8086:27ca instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27ca instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27ca instead
[2015-03-21 17:30:08] BAS looking for BAS 0403:6014 but found 8086:27c9 instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27c9 instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27c9 instead
[2015-03-21 17:30:08] BAS looking for BAS 0403:6014 but found 8086:27cb instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27cb instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27cb instead
[2015-03-21 17:30:08] BAS looking for BAS 0403:6014 but found 8086:27c8 instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27c8 instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27c8 instead
[2015-03-21 17:30:08] BAS looking for BAS 0403:6014 but found 8086:27cc instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27cc instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 8086:27cc instead
[2015-03-21 17:30:08] BAS looking for and found BAS 0403:6014
[2015-03-21 17:30:08] USB lock BitForceSC 5-1
[2015-03-21 17:30:08] RES: BitForceSC (5:1) lock=1
[2015-03-21 17:30:08] USB res lock BitForceSC 5-1
[2015-03-21 17:30:08] RES: BitForceSC (5:1) lock ok=1
[2015-03-21 17:30:08] USB init - BAS device 5:1 usbver=0200 prod='BitFORCE SHA256 SC' manuf='BUTTERFLY LABS' serial='FTYM9T5M'
[2015-03-21 17:30:08] BAS0: reset got err 0
[2015-03-21 17:30:08] BAS: cgid 0 SetLatency got err 0
[2015-03-21 17:30:08] BAS0: setdata got err 0
[2015-03-21 17:30:08] BAS0: setbaud got err 0
[2015-03-21 17:30:08] BAS0: setflowctrl got err 0
[2015-03-21 17:30:08] BAS0: setmodemctrl got err 0
[2015-03-21 17:30:08] BAS0: purgetx got err 0
[2015-03-21 17:30:08] BAS0: purgerx got err 0
[2015-03-21 17:30:08] BitForceSC detect (5:1) Warning unknown firmware ' 1.4.30x00' using Ver2
[2015-03-21 17:30:08] BAS: cgid 0 SetLatency got err 0
[2015-03-21 17:30:08] BitForceSC (5:1) identified as: 'BAS'
[2015-03-21 17:30:08] BAS looking for BAS 0403:6014 but found 058f:6377 instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 058f:6377 instead
[2015-03-21 17:30:08] BAS looking for BMA 0403:6014 but found 058f:6377 instead |
|
|
|
|
Show Posts
