It's been quite a challenge, as I have to do this headless over an iPad vnc and ssh connection, all my hardware is being shipped here an should arrive in two weeks or so...
Topic: Bitminter client (Windows/Linux/Mac) - page 42. (Read 654946 times)
I was able to get cgminer compiled under Ubuntu 12 via vm (parallels) but when I forward the USB devices over I can't connect to them (no devices) even though lsusb shows them.
It's been quite a challenge, as I have to do this headless over an iPad vnc and ssh connection, all my hardware is being shipped here an should arrive in two weeks or so...
It's been quite a challenge, as I have to do this headless over an iPad vnc and ssh connection, all my hardware is being shipped here an should arrive in two weeks or so...
Am I supposed to install drivers for these? I'm kind of at a loss...
On Windows it should install the necessary drivers automatically when you plug it in. Not sure about Mac and Linux yet. It's just a standard virtual-serial-port-over-USB kind of thing.
I'm looking into the issue with crashing under Mac OS X. If you have access to a Windows machine you could try that so they don't sit around idle.
I just got my BFLs yesterday, and I spent most of the night trying to compile ufasoft and cgminer to try and get it to work. From what I can piece together, OSX isn't assigning them ttyUSBn locations (when I ls /dev/*USB* I only get the bluetooth devices mentioned, although they all show up under the system report tool)
Am I supposed to install drivers for these? I'm kind of at a loss...
Am I supposed to install drivers for these? I'm kind of at a loss...
In theory it should be faster than cgminer and the other miners, because of faster work dispatch. In practice the difference is negligible (less than 1 Mhps per BFL single). This may prove more useful with the rig boxes.
Instead of checking whether the device is done with 10 ms pauses in between checks, it will first leave the device in peace until it gets close to done (cgminer does the same), then start 10 ms polling, and when it gets very close to done it starts 1 ms polling. This allows quick reaction pushing out new work once the device is idle. Right after it goes "ok, I'm all done, I think I'll just read the newspaper now" you have to detect that situation quickly and put it back to work. You can click the wrench and change the 10 ms and 1 ms values. You could even change the 1 ms to 0 ms. Running with 0 ms might be ok. It won't hog the CPU as much as the AMD drivers do/did.
I just thought it might be a bit brutal for a default setting.
Cool, looking forward to giving it a try! Instead of checking whether the device is done with 10 ms pauses in between checks, it will first leave the device in peace until it gets close to done (cgminer does the same), then start 10 ms polling, and when it gets very close to done it starts 1 ms polling. This allows quick reaction pushing out new work once the device is idle. Right after it goes "ok, I'm all done, I think I'll just read the newspaper now" you have to detect that situation quickly and put it back to work. You can click the wrench and change the 10 ms and 1 ms values. You could even change the 1 ms to 0 ms. Running with 0 ms might be ok. It won't hog the CPU as much as the AMD drivers do/did.
I just thought it might be a bit brutal for a default setting.Trying it out on OSX Lion (10.7.3) Server w/ 3x BitForce singles. When I try to scan for FPGAs, it just crashes. After it gets through with trying the Bluetooth modem (which fails), it dies. Mooing to try rebooting and giving it another shot.
The whole app crashes, and possibly Java leaves a crash log on the desktop? Probably the RXTX library (for Java access to serial ports) that's doing it. I'm starting to hate that buggy thing.
Could you try adding them one by one using the menu to probe a specific port?
Trying it out on OSX Lion (10.7.3) Server w/ 3x BitForce singles. When I try to scan for FPGAs, it just crashes. After it gets through with trying the Bluetooth modem (which fails), it dies. Mooing to try rebooting and giving it another shot.
In theory it should be faster than cgminer and the other miners, because of faster work dispatch. In practice the difference is negligible (less than 1 Mhps per BFL single). This may prove more useful with the rig boxes.
Instead of checking whether the device is done with 10 ms pauses in between checks, it will first leave the device in peace until it gets close to done (cgminer does the same), then start 10 ms polling, and when it gets very close to done it starts 1 ms polling. This allows quick reaction pushing out new work once the device is idle. Right after it goes "ok, I'm all done, I think I'll just read the newspaper now" you have to detect that situation quickly and put it back to work. You can click the wrench and change the 10 ms and 1 ms values. You could even change the 1 ms to 0 ms. Running with 0 ms might be ok. It won't hog the CPU as much as the AMD drivers do/did. I just thought it might be a bit brutal for a default setting.
Instead of checking whether the device is done with 10 ms pauses in between checks, it will first leave the device in peace until it gets close to done (cgminer does the same), then start 10 ms polling, and when it gets very close to done it starts 1 ms polling. This allows quick reaction pushing out new work once the device is idle. Right after it goes "ok, I'm all done, I think I'll just read the newspaper now" you have to detect that situation quickly and put it back to work. You can click the wrench and change the 10 ms and 1 ms values. You could even change the 1 ms to 0 ms. Running with 0 ms might be ok. It won't hog the CPU as much as the AMD drivers do/did.
I just thought it might be a bit brutal for a default setting.
Very cool! Will definitely be giving this a shot when I receive mine...
How is the hashrate on the BFL's compared to cgminer?
How is the hashrate on the BFL's compared to cgminer?
seems to be the same. I get about 825 Mh for both miners.
Very cool! Will definitely be giving this a shot when I receive mine...
How is the hashrate on the BFL's compared to cgminer?
How is the hashrate on the BFL's compared to cgminer?
v1.2.0 beta1 just released.
New in this release: support for BFL BitFORCE FPGA devices!
A big thanks to Fefox for lending me his BFL singles for testing and his participation in the testing!
If you have one or more such devices, please help test this beta. It has only been tested on 64 bit Windows. That leaves 32 bit Windows, 32/64 bit Linux, 32/64 bit Mac OS X.
How to use it:
It doesn't probe the serial ports by default. There is a new menu "devices" with two possible actions: checking all serial ports for BitFORCE devices, or a specific one. Also there is a new FPGA tab in the options (Settings -> Options in the menus). Here you can set how to detect FPGAs on startup and whether to scan for added/removed devices at intervals. There are also some settings you can change on each device. Click the wrenches to change these settings.
Please try it out:
If the device reaches max temp it will stop. Click the wrench to change the max temp. Is 75 C a good default max temperature?
Any feedback appreciated.
New in this release: support for BFL BitFORCE FPGA devices!
A big thanks to Fefox for lending me his BFL singles for testing and his participation in the testing!
If you have one or more such devices, please help test this beta. It has only been tested on 64 bit Windows. That leaves 32 bit Windows, 32/64 bit Linux, 32/64 bit Mac OS X.
How to use it:
It doesn't probe the serial ports by default. There is a new menu "devices" with two possible actions: checking all serial ports for BitFORCE devices, or a specific one. Also there is a new FPGA tab in the options (Settings -> Options in the menus). Here you can set how to detect FPGAs on startup and whether to scan for added/removed devices at intervals. There are also some settings you can change on each device. Click the wrenches to change these settings.
Please try it out:
If the device reaches max temp it will stop. Click the wrench to change the max temp. Is 75 C a good default max temperature?
Any feedback appreciated.
I have gotten a few reports that the miner runs very fast on 7970s.
Has anyone compared directly against DiabloMiner? I don't have a 7970 to test on.
Has anyone compared directly against DiabloMiner? I don't have a 7970 to test on.
The easy solution for Ubuntu: open Ubuntu software center, search for "IcedTea Java 6 web start". Install it. Done .
.
When you click the "engine start" button on the website Firefox should open a small window saying "You have chosen to open bitminter.jnlp which is a: JNLP File (2.7 KB)".
Below this, on one of my computers the top option (which is the default) says "Open with Java(TM) Web Start Launcher (default)". On another computer it says "Open with Sun Java 6 Web Start (default)", but the second option "Save File" comes up as the default (pre-selected) option. As long as you get an option to open with web start, choose that and click OK - you're good to go.
Something else may show up as the default "open with" choice. Click the combo box and see if web start is listed. If not, click "Other..." which will list many applications you could use to open the file. If Java web start is on the list, choose that. If you check "do this automatically for files like this from now on" then Firefox will remember your choice for next time.
If Java web start doesn't show up as an option then there's probably something wrong with the file type associations and Firefox doesn't know what to do with a JNLP file. Firefox (unlike some browsers) gets this information from the operating system. Normally there should be a JNLP file type associated with Java web start after you install Java. Not sure what would cause that to fail.
You should have a file under /usr/share/applications/ with javaws in the name.
Ubuntu 11.10 example, /usr/share/applications/icedtea-netx-javaws.desktop
Below this, on one of my computers the top option (which is the default) says "Open with Java(TM) Web Start Launcher (default)". On another computer it says "Open with Sun Java 6 Web Start (default)", but the second option "Save File" comes up as the default (pre-selected) option. As long as you get an option to open with web start, choose that and click OK - you're good to go.
Something else may show up as the default "open with" choice. Click the combo box and see if web start is listed. If not, click "Other..." which will list many applications you could use to open the file. If Java web start is on the list, choose that. If you check "do this automatically for files like this from now on" then Firefox will remember your choice for next time.
If Java web start doesn't show up as an option then there's probably something wrong with the file type associations and Firefox doesn't know what to do with a JNLP file. Firefox (unlike some browsers) gets this information from the operating system. Normally there should be a JNLP file type associated with Java web start after you install Java. Not sure what would cause that to fail.
You should have a file under /usr/share/applications/ with javaws in the name.
Ubuntu 11.10 example, /usr/share/applications/icedtea-netx-javaws.desktop
Code:
[Desktop Entry]
Name=IcedTea Java 6 Web Start
Name[fi]=IcedTea Java 6 - Web Start
Comment=IcedTea Java 6 Web Start
Comment[fi]=IcedTea Java 6 - Web Start
Exec=/usr/lib/jvm/java-6-openjdk/bin/javaws %u
Terminal=false
Type=Application
Icon=openjdk-6
Categories=Application;Network;
MimeType=application/x-java-jnlp-file;
NoDisplay=true
Thanks so much for your reply.
Starting BitMinter from that command line as suggested above works great, so it is a very effective workaround for me;
however it will not start from the browser even after deleting Bitminter from the cache.
Starting BitMinter from that command line as suggested above works great, so it is a very effective workaround for me;
however it will not start from the browser even after deleting Bitminter from the cache.
Could you try starting it from the command line and see if that works better?
Also you could try "javaws -viewer" and delete bitminter from the cache. Next time you start it, it will be downloaded anew, which might help.
Code:
javaws http://bitminter.com/client/bitminter.jnlp
Also you could try "javaws -viewer" and delete bitminter from the cache. Next time you start it, it will be downloaded anew, which might help.
After upgrading from Ubuntu 10.04 to 11.10 Bitminter will not start at all. I have tried it with both Oracle java and icetea. I currently have Oracle Java version: Version 6 Update 30. When launching Bitminter using Firefox it prompts to open the jre with Firefox and then launches a new tab. i have verified Java on the Oracle site and it says "Your Java version: Version 6 Update 30" Thanks
Quick update today. Version 1.1.2.
Only one change: Recognize FirePro M5950 (Toucan) and enable BFI_INT patching for it.
This was unfortunately broken by the recent GCN changes. Please let me know if you have other GPUs that are not recognized (or CPUs).
Only one change: Recognize FirePro M5950 (Toucan) and enable BFI_INT patching for it.
This was unfortunately broken by the recent GCN changes. Please let me know if you have other GPUs that are not recognized (or CPUs).
Runs well on 7970 and no reports of any problems. So v1.1.1 final is now out. Changes are as described in the previous post.
v1.1.1 beta is out.
Changes:
Can someone with a 7970 see how it runs? I don't have one to test it on myself.
Changes:
- Improved long polling
- Cache less work, to reduce server load
- Show reason for rejected proofs of work (X-Reject-Reason getwork extension)
- Cache DNS lookups max 15 minutes (so you won't have to restart if we switch server again)
- AMD GCN support: use bitselect() for BFI_INT instead of patching
- Recognize more CPUs/GPUs. Corrected expected hash rates for some devices.
Can someone with a 7970 see how it runs? I don't have one to test it on myself.
AFAIK, Java JRE is written in C. If you dont like installing Oracle software, bitminter works fine on IcedTea on linux.
Jump to: