And using Zadig to update drivers...
Ditch Zadig/libusb and install drivers from http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx then it will work.
Topic: Bitminter client (Windows/Linux/Mac) - page 33. (Read 654946 times)
Ditch Zadig/libusb and install drivers from http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx then it will work.
I'm trying to get bitminter v1.3.2 to work with block eruptor usb on windows 8 x64...
In bitminter, when I "probe all ports for FPGAs", I'm getting the error "Probe failed: No serial ports found" from Bitminter v1.3.2
I've installed Silabs CP2102 USB to UART Bridge Controller
And using Zadig to update drivers...
http://24.media.tumblr.com/ed80212ea3cd9c858ab4df03b30041dd/tumblr_mnw46d9mt91spis86o1_500.png
any idea why Bitminter can't find my eruptor?
In bitminter, when I "probe all ports for FPGAs", I'm getting the error "Probe failed: No serial ports found" from Bitminter v1.3.2
I've installed Silabs CP2102 USB to UART Bridge Controller
And using Zadig to update drivers...
http://24.media.tumblr.com/ed80212ea3cd9c858ab4df03b30041dd/tumblr_mnw46d9mt91spis86o1_500.png
any idea why Bitminter can't find my eruptor?
Dr Haribo -- I just wanted to confirm that indeed, running both the FTDI driver (for the FPGA Bitforce) and the SiLabs driver simultaneously on one OSX instance does in fact work.
Thanks, that's good to know
Would it be possible to run a mix of BFL FPGA Bitforce units alongside the USB Eruptors on a single OSX Machine using the Bitminter Miner?
I'm afraid if I use the SiLabs USB to UART Bridge VCP Drivers in lieu of the FTDI drivers, the Eruptors will be found but the BFL Units will disappear.
Dr. Haribo, any thoughts on this?
I'm afraid if I use the SiLabs USB to UART Bridge VCP Drivers in lieu of the FTDI drivers, the Eruptors will be found but the BFL Units will disappear.
Dr. Haribo, any thoughts on this?
I haven't tested that, but I believe it should work fine.
Dr Haribo -- I just wanted to confirm that indeed, running both the FTDI driver (for the FPGA Bitforce) and the SiLabs driver simultaneously on one OSX instance does in fact work.
To test this, I grabbed a few BFL FPGA Bitforce units, plugged them into a USB hub.
Then, I grabbed two USB eruptors, plugged them into a different hub.
Plugged both hubs into a test OSX machine which had both the FTDI and SiLabs drivers installed.
Probed specific port for the Eruptors as you instructed in a previous post.
Probed all ports to find the installed BFL FPGA units.
Like magic, they all appeared in the client. Started them all up, and they are happily mining away in harmony.
My only problem now is that it seems Bitminter is under DDOS attack. Darn.
Would it be possible to run a mix of BFL FPGA Bitforce units alongside the USB Eruptors on a single OSX Machine using the Bitminter Miner?
I'm afraid if I use the SiLabs USB to UART Bridge VCP Drivers in lieu of the FTDI drivers, the Eruptors will be found but the BFL Units will disappear.
Dr. Haribo, any thoughts on this?
I'm afraid if I use the SiLabs USB to UART Bridge VCP Drivers in lieu of the FTDI drivers, the Eruptors will be found but the BFL Units will disappear.
Dr. Haribo, any thoughts on this?
I haven't tested that, but I believe it should work fine.
Yep, that's exactly what I did. Worked perfectly. I'm currently using the beta client, BTW.
Awesome. Thanks for confirming. I'll get that and the hashrate issue fixed.
Would it be possible to run a mix of BFL FPGA Bitforce units alongside the USB Eruptors on a single OSX Machine using the Bitminter Miner?
I'm afraid if I use the SiLabs USB to UART Bridge VCP Drivers in lieu of the FTDI drivers, the Eruptors will be found but the BFL Units will disappear.
Dr. Haribo, any thoughts on this?
Yep, that's exactly what I did. Worked perfectly. I'm currently using the beta client, BTW.
Awesome. Thanks for confirming. I'll get that and the hashrate issue fixed.
I don't have any Block Erupter USB units to test with, but I'm starting to figure this out.
The hashrate currently shows 2x what it should be. This is because the Icarus device had 2 FPGAs which split the noncerange between them, while apparently the Block Erupter has 1 chip doing the nonce range from start to finish.
Did you have to "probe specific port" to get that working?
What I suspect to be the solution:
Instead of FTDI drivers, get Silabs drivers: http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx
On Mac OS X this gives serial ports with a different filename than the usual /dev/usbserial* from FTDI. With the current BitMinter client that won't work automatically, so you have to open a Terminal window and type
The hashrate currently shows 2x what it should be. This is because the Icarus device had 2 FPGAs which split the noncerange between them, while apparently the Block Erupter has 1 chip doing the nonce range from start to finish.
Just got my USB Block Erupter up and running on my Mac using BitMinter. Working great. Currently reporting 671.5 Mhps, so I guess it is running ~335 Mhps. 
Did you have to "probe specific port" to get that working?
What I suspect to be the solution:
Instead of FTDI drivers, get Silabs drivers: http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx
On Mac OS X this gives serial ports with a different filename than the usual /dev/usbserial* from FTDI. With the current BitMinter client that won't work automatically, so you have to open a Terminal window and type
Code:
ls /dev/cu.*
to find the name. Probably /dev/cu.SLAB_USBtoUART. If you have multiple units then they will also have a number at the end. Then click "devices" -> "probe specific port" in the menu, and type in the full path, /dev/cu.SLAB_USBtoUART - the device should be detected. Not confirmed to be working yet, so a confirmation would be useful.Yep, that's exactly what I did. Worked perfectly. I'm currently using the beta client, BTW.
I don't have any Block Erupter USB units to test with, but I'm starting to figure this out.
The hashrate currently shows 2x what it should be. This is because the Icarus device had 2 FPGAs which split the noncerange between them, while apparently the Block Erupter has 1 chip doing the nonce range from start to finish.
Did you have to "probe specific port" to get that working?
What I suspect to be the solution:
Instead of FTDI drivers, get Silabs drivers: http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx
On Mac OS X this gives serial ports with a different filename than the usual /dev/usbserial* from FTDI. With the current BitMinter client that won't work automatically, so you have to open a Terminal window and type
The hashrate currently shows 2x what it should be. This is because the Icarus device had 2 FPGAs which split the noncerange between them, while apparently the Block Erupter has 1 chip doing the nonce range from start to finish.
Just got my USB Block Erupter up and running on my Mac using BitMinter. Working great. Currently reporting 671.5 Mhps, so I guess it is running ~335 Mhps.
Did you have to "probe specific port" to get that working?
What I suspect to be the solution:
Instead of FTDI drivers, get Silabs drivers: http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx
On Mac OS X this gives serial ports with a different filename than the usual /dev/usbserial* from FTDI. With the current BitMinter client that won't work automatically, so you have to open a Terminal window and type
Code:
ls /dev/cu.*
to find the name. Probably /dev/cu.SLAB_USBtoUART. If you have multiple units then they will also have a number at the end. Then click "devices" -> "probe specific port" in the menu, and type in the full path, /dev/cu.SLAB_USBtoUART - the device should be detected. Not confirmed to be working yet, so a confirmation would be useful.
Just got my USB Block Erupter up and running on my Mac using BitMinter. Working great. Currently reporting 671.5 Mhps, so I guess it is running ~335 Mhps.
Is ASICMiner's USB erupter supported?
BitMinter's UI and ease of use would be perfect for a new miner with an inexpensive USB miner to get started.
I plan to gift some to family and friends to spread interest in Bitcoin, and BitMinter would be perfect as a headache-free way to get someone started.
BitMinter's UI and ease of use would be perfect for a new miner with an inexpensive USB miner to get started.
I plan to gift some to family and friends to spread interest in Bitcoin, and BitMinter would be perfect as a headache-free way to get someone started.
FWIW.. I am running 1.3.2 client on win7 x64 with 9 AsicMiner USB's. The client recognizes them as Icaruses.. The only odd thing is that the hash rate reported by the client seems to be 2x the actual hashrate. But they are mining just fine.
I also am runing an USB block erupter and it is mining just fine. But I also have the same problem where the client is reporting a hash rate much higher than the website is reporting it.
Help me, I start the client and when a click on the mining button (play), the client just crash and quit. How can I fix it ?
It probably leaves a hs_err_pid crash log on your desktop (could also be in a temporary folder, not easy to find), which says problematic frame: amdocl.dll - a crash in the AMD OpenCL driver.
AMD has been unable to create proper drivers in 2013 so far. They work for some people, but for many they either crash all miners or some miners.
You can try installing the latest beta, maybe they finally managed to do something right, or you could try a 2012 driver. Even if you get a proper driver the AMD uninstaller doesn't work (never has since AMD was founded), and it may leave behind files that will cause miners to still crash. You could try the cleanup utility at AMD website, or driver sweeper from guru3d, or manual cleanup as discussed here: http://forums.guru3d.com/showthread.php?t=359883
I just tested with an ASICminer USB erupter on OS X. Does not work.
Did you install the FTDI driver? In BitMinter client when you click "devices" -> "probe all ports" in the menu it will give you a link to download the drivers if no ASIC or FPGA is detected.
Would you consider a LiteCoin Java Miner when BTC difficulty goes through the roof?
Once I have the important BTC stuff under control, I will have a look at LTC and see if it makes sense.
also, my 2 GPUs seem to only run at about 89-90% of maximum on BitMinter (using GUIminer) - yet when I was on Slush's, one ran at a constant 99%, and the other at 93-98%.
Again, is there any way to tweak it to get maximum constant output?
Again, is there any way to tweak it to get maximum constant output?
There shouldn't be any difference there. I doubt this issue has to do with which pool you're mining with.
How do i get my friends to mine for me without them having to use my user. Of course i give them worker user and pass.
K.
K.
Worker user and pass are all you should need, could you please clarify?
Help me, I start the client and when a click on the mining button (play), the client just crash and quit. How can I fix it ?
I am having the same issue - Windows 8 64bit, fresh 64bit Java install (cleared Java cache too & re-installed latest version)
Any help would be appreciated.
also, my 2 GPUs seem to only run at about 89-90% of maximum on BitMinter (using GUIminer) - yet when I was on Slush's, one ran at a constant 99%, and the other at 93-98%.
Again, is there any way to tweak it to get maximum constant output?
Would you consider a LiteCoin Java Miner when BTC difficulty goes through the roof?
Is ASICMiner's USB erupter supported?
BitMinter's UI and ease of use would be perfect for a new miner with an inexpensive USB miner to get started.
I plan to gift some to family and friends to spread interest in Bitcoin, and BitMinter would be perfect as a headache-free way to get someone started.
BitMinter's UI and ease of use would be perfect for a new miner with an inexpensive USB miner to get started.
I plan to gift some to family and friends to spread interest in Bitcoin, and BitMinter would be perfect as a headache-free way to get someone started.
FWIW.. I am running 1.3.2 client on win7 x64 with 9 AsicMiner USB's. The client recognizes them as Icaruses.. The only odd thing is that the hash rate reported by the client seems to be 2x the actual hashrate. But they are mining just fine.
Is any one finding that they are getting less stales in windows 8?
So far I am up to 2750 accepted, and only 3 stales.
So far I am up to 2750 accepted, and only 3 stales.
Good work Dr. Thanks for making this miner/pool!
Is ASICMiner's USB erupter supported?
BitMinter's UI and ease of use would be perfect for a new miner with an inexpensive USB miner to get started.
I plan to gift some to family and friends to spread interest in Bitcoin, and BitMinter would be perfect as a headache-free way to get someone started.
BitMinter's UI and ease of use would be perfect for a new miner with an inexpensive USB miner to get started.
I plan to gift some to family and friends to spread interest in Bitcoin, and BitMinter would be perfect as a headache-free way to get someone started.
I just tested with an ASICminer USB erupter on OS X. Does not work.
I don't have my USB Erupter yet, so haven't been able to test, but did you try installing this OS X driver and then running Bitminter again?
http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx
Is ASICMiner's USB erupter supported?
BitMinter's UI and ease of use would be perfect for a new miner with an inexpensive USB miner to get started.
I plan to gift some to family and friends to spread interest in Bitcoin, and BitMinter would be perfect as a headache-free way to get someone started.
BitMinter's UI and ease of use would be perfect for a new miner with an inexpensive USB miner to get started.
I plan to gift some to family and friends to spread interest in Bitcoin, and BitMinter would be perfect as a headache-free way to get someone started.
I just tested with an ASICminer USB erupter on OS X. Does not work.
Jump to: