Pages:
Author

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

newbie
Activity: 43
Merit: 0
June 10, 2012, 04:41:37 AM
Running Windows 8. But that was no problem for beta 9.

Beta 9 was using synchronous network I/O. Beta 11 has asynchronous I/O. Apparently when doing an asynchronous connect Java will call getsockname() before the connection is established. This works on every operating system except Windows 8.

Are you using the latest, Java 7, update 4?

This could become an annoying issue. There's no workaround either.


Yes i have Java 7 update 4.

Guess i have to use the non Beta Miner. If there is no workaround you might want to consider an option to switch back to synchronous networking.

Let's hope the final version of Windows 8 or the next Java update fixes it.
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
June 10, 2012, 04:36:30 AM
Running Windows 8. But that was no problem for beta 9.

Beta 9 was using synchronous network I/O. Beta 11 has asynchronous I/O. Apparently when doing an asynchronous connect Java will call getsockname() before the connection is established. This works on every operating system except Windows 8.

Are you using the latest, Java 7, update 4?

This could become an annoying issue. There's no workaround either.
newbie
Activity: 43
Merit: 0
June 10, 2012, 04:21:12 AM
I get this error with beta 11:
Connection failed: Invalid argument: getsockname

Do you have a firewall blocking the program? Are you running on Windows 8?


Running Windows 8. But that was no problem for beta 9.
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
June 10, 2012, 04:19:50 AM
One problem found in beta 11. On some systems (high hash rate?) after running for some time the CPU usage goes up and it starts running out of work. Investigating this now.

Question - would that new version help stale proof of work at all?  I have 4 BFL's running, and don't ever get a lack of work, but do get stale proof of work from time to time.

Yeah, it can use multiple connections and it gives priority to uploading proofs of work over downloading more work, so it might reduce rejects a bit.

I get this error with beta 11:
Connection failed: Invalid argument: getsockname

Do you have a firewall blocking the program? Are you running on Windows 8?
newbie
Activity: 43
Merit: 0
June 10, 2012, 03:30:59 AM
I get this error with beta 11:
Connection failed: Invalid argument: getsockname
legendary
Activity: 1400
Merit: 1005
June 09, 2012, 02:08:53 PM
Question - would that new version help stale proof of work at all?  I have 4 BFL's running, and don't ever get a lack of work, but do get stale proof of work from time to time.
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
June 09, 2012, 01:49:23 PM
I just uploaded beta 11. It fixes a thread scheduling bug in beta 10 that could cause devices to run out of work when there was still work in the queue.

Beta 11 seems to run fine on 6 BFL singles, 5.2 GH/s, with low stales. Looking good so far. Smiley
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
June 09, 2012, 11:27:55 AM
I.m testing your v1.2.0 beta10 with one Bit Force and I get: batch acquisition of 0 triggers.

What does it mean?

It's just the scheduling subsystem (see the automation part of the options) that is a bit chatty. It's nothing to worry about and you should only see it if you have verbose logging turned on.
member
Activity: 66
Merit: 10
June 09, 2012, 10:10:31 AM
Hi,

I.m testing your v1.2.0 beta10 with one Bit Force and I get: batch acquisition of 0 triggers.

What does it mean?

Is it bad?

Regards


v1.2.0 beta10 is out.

This version can download work much faster, using multiple pipelined connections to the server. This should prevent running out of work when you have a high hash rate on the computer, like 9-10 BFL singles or more. All the network code has been rewritten completely. I've been running this a few days myself, but it needs some more testing before finalizing v1.2.0. Please check it out, especially interesting if you can try it on high latency connections (maybe big file transfers running that slow down your internet connection) or an unstable network where the connection comes and goes.

Let me know how it runs. Smiley



legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
June 09, 2012, 07:15:10 AM
v1.2.0 beta10 is out.

This version can download work much faster, using multiple pipelined connections to the server. This should prevent running out of work when you have a high hash rate on the computer, like 9-10 BFL singles or more. All the network code has been rewritten completely. I've been running this a few days myself, but it needs some more testing before finalizing v1.2.0. Please check it out, especially interesting if you can try it on high latency connections (maybe big file transfers running that slow down your internet connection) or an unstable network where the connection comes and goes.

Let me know how it runs. Smiley


hero member
Activity: 910
Merit: 1004
buy silver!
show off
full member
Activity: 168
Merit: 100


Video I made showing the singles power usage with stock PSU's and with a Corsair AX1200..  and of course bitminter running the 8 BFL singles

http://vimeo.com/42438781
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
Am I the only one that can't get this miner to detect the bitforce singles? I should mention that I did install the FTDI drivers, but I did _not_ reboot yet. Both miners work fine in MPBM though.

You clicked "devices->probe all ports" in the menus? Which OS are you on?
legendary
Activity: 3080
Merit: 1080
Am I the only one that can't get this miner to detect the bitforce singles? I should mention that I did install the FTDI drivers, but I did _not_ reboot yet. Both miners work fine in MPBM though.

sr. member
Activity: 369
Merit: 250
well i removed the GPUs and put em back on cgminer and kept my bitforce running on your client. seems to be in better order like that so Il keep it as is Smiley
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
Left 4 x 6970's mining and a BFL single mining overnight.

2781 accepted.
9440 rejected.

never has this issue with any other miner before.

I never heard of anyone having such an issue with this miner either. Is there anything in the log (text part of the window) to give a clue as to what went wrong? Perhaps network problems?

Currently on my computer I have 317609 accepted and 46 rejected. That's 4 GPUs. BFL units seem to run a bit higher, roughly 0.3% rejected.
sr. member
Activity: 369
Merit: 250
Left 4 x 6970's mining and a BFL single mining overnight.

2781 accepted.
9440 rejected.

never has this issue with any other miner before.

legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
Do you have an overview, how many singles and mini rigs are/will be there in the BitMinter network?

At least 4 mini rigs and a whole bunch of singles. There are also users mining with other FPGA devices and several people ordered the new Cairnsmore. I intend to add support for more FPGA devices in the future. First I would just like to get v1.2.0 out with BFL support.
newbie
Activity: 27
Merit: 0
I ordered a mini rig today, let's see how fast they will get it to me.
Is Bitminter ready for such a device? shure hope so, otherwise I think we will make it work somehow.
Ready for testing...

There's one issue I'm still working on with the beta. It seems to not grab new work from the server fast enough. This will surely be a problem with a mini rig. But it will be fixed long before your mini rig arrives. Smiley

Currently observed: Windows 7 with 8 singles shows slow work queue buildup but runs ok. Mac OS X with 10 singles ends up with an utterly depleted work queue and devices idling. A fix for this should be coming soon.

Congrats on getting a mini rig! I think it's awesome that so many in the pool are getting singles and mini rigs. I aim to make the miner run as smoothly on them as possible.

Thanks, that sound's good.
Do you have an overview, how many singles and mini rigs are/will be there in the BitMinter network?
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
I ordered a mini rig today, let's see how fast they will get it to me.
Is Bitminter ready for such a device? shure hope so, otherwise I think we will make it work somehow.
Ready for testing...

There's one issue I'm still working on with the beta. It seems to not grab new work from the server fast enough. This will surely be a problem with a mini rig. But it will be fixed long before your mini rig arrives. Smiley

Currently observed: Windows 7 with 8 singles shows slow work queue buildup but runs ok. Mac OS X with 10 singles ends up with an utterly depleted work queue and devices idling. A fix for this should be coming soon.

Congrats on getting a mini rig! I think it's awesome that so many in the pool are getting singles and mini rigs. I aim to make the miner run as smoothly on them as possible.
Pages:
Jump to: