Pages:
Author

Topic: Bitminter client (Windows/Linux/Mac) - page 20. (Read 654946 times)

newbie
Activity: 6
Merit: 0
December 02, 2013, 10:52:35 PM
BitMinter client version 1.4.3 is out.

Changes from 1.4.2 to 1.4.3:
  • Disabled CPU mining
  • Preliminary support for Big Picture Mining BF1 devices (aka red/blue fury)
  • Untested: add support for Chili devices
  • Improved log messages when probing for external devices
  • Added Application-Name to manifest, to get rid of errors in java console
      when the application starts under the latest Java version.

Blue/red fury support isn't quite right yet. This is mainly a release to get a version out without CPU mining.

If anyone has a Chili ASIC device, please let me know if this version works with it.

Try it out:
https://bitminter.com/images/start.png

If you have issues with 1.4.3 then you can still get the previous release (1.4.2) at https://bitminter.com/client/1.4.2/bitminter.jnlp



Hi,

I updated but both my Jalapenos stopped working with a "ran out of work. Idling..." message.

Restarted with V1.4.2 and both are working again.

Will there be a logfiles on my system I can send to you to help with the debugging?

Phil
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
December 02, 2013, 06:14:37 PM
BitMinter client version 1.4.3 is out.

Changes from 1.4.2 to 1.4.3:
  • Disabled CPU mining
  • Preliminary support for Big Picture Mining BF1 devices (aka red/blue fury)
  • Untested: add support for Chili devices
  • Improved log messages when probing for external devices
  • Added Application-Name to manifest, to get rid of errors in java console
      when the application starts under the latest Java version.

Blue/red fury support isn't quite right yet. This is mainly a release to get a version out without CPU mining.

If anyone has a Chili ASIC device, please let me know if this version works with it.

Try it out:


If you have issues with 1.4.3 then you can still get the previous release (1.4.2) at https://bitminter.com/client/1.4.2/bitminter.jnlp
legendary
Activity: 4326
Merit: 8899
'The right to privacy matters'
November 30, 2013, 05:53:01 AM
i had issues on Osx Mountain Lion with java (could have been something i was doing wrong) i updated to mavericks and it works fine with the bluefury usb. I was using the beta client on a macbook air.


I had issues on OSX ML     the java client would report timeout for a red fury/

this also happened on windows 7.  but pointing  bfgminer I have 3 sticks (red fury)  they all add up to 7.7gh and my big stats page give me 7.7gh.  this is with beta client
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
November 29, 2013, 07:49:42 AM
i had issues on Osx Mountain Lion with java (could have been something i was doing wrong) i updated to mavericks and it works fine with the bluefury usb. I was using the beta client on a macbook air.

Thanks, that's useful info. I was testing on OS X Mavericks from the start.
hero member
Activity: 630
Merit: 501
Miner Setup And Reviews. WASP Rep.
November 29, 2013, 07:41:54 AM
i had issues on Osx Mountain Lion with java (could have been something i was doing wrong) i updated to mavericks and it works fine with the bluefury usb. I was using the beta client on a macbook air.
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
November 28, 2013, 04:28:33 PM
When you use an api reference tool it gives you all the data available via the api. I was thinking something similar to that, with the sleekness of the tool you have already made.

Ah I see. I'll look into adding something like that in the future. It will be a ways down on the TODO list though.

how does one properly uninstall the app on Mac? can't be as simple as deleting the jnlp

Look under "tools" -> "bitminter client" -> "uninstall" on the website.
sr. member
Activity: 516
Merit: 283
November 28, 2013, 04:26:00 PM
how does one properly uninstall the app on Mac? can't be as simple as deleting the jnlp
newbie
Activity: 42
Merit: 0
November 25, 2013, 01:25:53 PM
When you use an api reference tool it gives you all the data available via the api. I was thinking something similar to that, with the sleekness of the tool you have already made.

Michael
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
November 25, 2013, 12:54:27 PM
Is it possible to tweak the interface so it can be used as a reference tool. I know there are API programs available, but not to many for mac, and being java it's cross platform already. I like to interface and sleekness, it would just be nice to be able to monitor what's going on, especially for the ones who use hardware like the blades.

Just a thought.

Michael

What kind of reference tool?
newbie
Activity: 42
Merit: 0
November 24, 2013, 03:25:24 PM
Is it possible to tweak the interface so it can be used as a reference tool. I know there are API programs available, but not to many for mac, and being java it's cross platform already. I like to interface and sleekness, it would just be nice to be able to monitor what's going on, especially for the ones who use hardware like the blades.

Just a thought.

Michael
newbie
Activity: 40
Merit: 0
November 22, 2013, 08:50:43 AM
Just throwing it out there would be nice to have... is to be able to use the program to remotely view/control another computer running the software on the same network. Kind of like how you can login twice with BOINC or add another computer with Folding@home to both control and view. Not sure if that is a huge pain and I can remotely monitor the computer in question. I guess this is the downfall of running something like this in a graphical environment, because if I was running a Raspberry Pi I could SSH and view/control it way easier. Just a thought.

Something like this is planned. But it will take a while before I get to it.


I assumed it would be lower down on the list, thank you!!
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
November 21, 2013, 06:31:08 PM
Just throwing it out there would be nice to have... is to be able to use the program to remotely view/control another computer running the software on the same network. Kind of like how you can login twice with BOINC or add another computer with Folding@home to both control and view. Not sure if that is a huge pain and I can remotely monitor the computer in question. I guess this is the downfall of running something like this in a graphical environment, because if I was running a Raspberry Pi I could SSH and view/control it way easier. Just a thought.

Something like this is planned. But it will take a while before I get to it.
newbie
Activity: 40
Merit: 0
November 20, 2013, 02:19:50 PM
Just throwing it out there would be nice to have... is to be able to use the program to remotely view/control another computer running the software on the same network. Kind of like how you can login twice with BOINC or add another computer with Folding@home to both control and view. Not sure if that is a huge pain and I can remotely monitor the computer in question. I guess this is the downfall of running something like this in a graphical environment, because if I was running a Raspberry Pi I could SSH and view/control it way easier. Just a thought.
legendary
Activity: 4326
Merit: 8899
'The right to privacy matters'
November 19, 2013, 08:46:35 PM
if you hit probe too fast the device has not popped up yet you bomb if you hit probe too slow after it reappears on the screen you time out.

Wow, really? Does it behave this way consistently?

yes pretty much and the second problem was even worse the guy for the bit fury would be about 4 x 2.2 or

8.8 -8.9 gh  yet the shifts read 7.2- 7.5  for 8 hours.  so a 15% leak of hash happens with the java client and the furies.  runing the same sticks on bfgminer and they match 8.8 = 8.8 on the guy and on the stats page.

that is a lot of hash to go poof .  i just have 4 sticks all around 2.2 on bfg and on java.  but bfg shows 2.2 on the stats page and java shows 1.5-1.6 .  idi a lot of tests to be sure.  i only have aam sticks and red furies.  am sticks are fine on both clients not the red furies.

the bfg does better at finding the sticks if you do them one at a time.
full member
Activity: 158
Merit: 100
November 19, 2013, 06:04:49 PM
ok stupid question lately when I try and start Bitminter I get a "Failed to Validate certificate. The application will not be executed" error.

Could you see if it helps to flush the Java cache?

http://www.java.com/en/download/help/plugin_cache.xml
Nope Flushing cache didn't seem to do anything Sad

Which Java version is this, and which operating system?



Windows 7 sp1 32bit
Java 7 update 45 build 1.7.0_45-b18

OK figured out what the  "Failed to Validate certificate. The application will not be executed" error was. Paarently the old trusted certifiates conflict with the new ones.
had to follow this to get rid of them.

http://weirdwindowsfixes.blogspot.com/2011/10/java-error-to-validate-certificate.html
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
November 19, 2013, 12:52:25 PM
if you hit probe too fast the device has not popped up yet you bomb if you hit probe too slow after it reappears on the screen you time out.

Wow, really? Does it behave this way consistently?
legendary
Activity: 1358
Merit: 1001
https://gliph.me/hUF
November 19, 2013, 09:41:37 AM
I have not read the whole thread.

Wondering if you ever got a BF1 for testing?

I just tried the beta on Fedora without any luck (and also without much poking around).

Not sure yet why it is not working for many people.

Try starting the client, then unplug the BF1. Plug it back in, wait a couple seconds, then probe all ports.

Make sure your user has access to serial ports. On Ubuntu: "sudo usermod -a -G dialout USERNAME" then log out and back in


I have tried the above (it was mentioned in the "official" support thread too), but no joy.
legendary
Activity: 4326
Merit: 8899
'The right to privacy matters'
November 19, 2013, 09:28:02 AM
the beta program has the following bug.  it reads the correct hash about 10gh 4 red furies each read about 2.3 gh and 3 block eruptors read .333 mh/s  total of about 10gh  .  yet my stats read 7.7 gh.  so your program seems to lose about ¼ of each red fury.  I will post photos later.
legendary
Activity: 4326
Merit: 8899
'The right to privacy matters'
November 18, 2013, 09:44:00 PM
I have not read the whole thread.

Wondering if you ever got a BF1 for testing?

I just tried the beta on Fedora without any luck (and also without much poking around).

Not sure yet why it is not working for many people.

Try starting the client, then unplug the BF1. Plug it back in, wait a couple seconds, then probe all ports.

Make sure your user has access to serial ports. On Ubuntu: "sudo usermod -a -G dialout USERNAME" then log out and back in


I got all 4 to work with windows 7 and your new beta.  even had 19 Am sticks working with it.   it is very tricky to get them to start.

speed speed speed.  just do 1 stick hit  reset then click  probe all miners.  don't wait long.  under 1 second.  if you have windows 7 like i do call up your devices and printers window.  you see the device I have 4 bit fury com546 com594 com595 com596.  I have high com numbers due to the hundreds of be sticks I have tested heats inked and sold.  look at one of your bit fury in the devices window hit reset hold 1 -2 seconds let go you will see the device disappear when you press and hold reset.  when you let go of reset you will see the device pop back on the device + printer screen.  you have under 2 seconds to hit probe ports  once the device comes back on the screen.   timing is the key.

if you hit probe too fast the device has not popped up yet you bomb if you hit probe too slow after it reappears on the screen you time out.

basically it is a timing issue .  I am assuming you got the drivers loaded correctly.
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
November 18, 2013, 04:36:50 PM
I have not read the whole thread.

Wondering if you ever got a BF1 for testing?

I just tried the beta on Fedora without any luck (and also without much poking around).

Not sure yet why it is not working for many people.

Try starting the client, then unplug the BF1. Plug it back in, wait a couple seconds, then probe all ports.

Make sure your user has access to serial ports. On Ubuntu: "sudo usermod -a -G dialout USERNAME" then log out and back in
Pages:
Jump to: