Topic: Phoenix 2 Miner v2.0.0 - page 3. (Read 201581 times)
Does anyone know the current status of this project?
I maintain a usb based linux distro tailored for mining farms. We have always used phoenix as the preferred miner, and added support for phoenix 2 long ago. Both are great clients, they do one thing and they do it very well.
However, it seems like nothing is happening over here... am I wrong? I hope so. Any plans to do FPGA/asic support? That's become a much requested feature.
Thanks for any guidance. We are releasing a new version shortly so need to make some decisions on miners to include and how to present them.
is there any way to set the gpu/mem clock and the voltage via some flag/command?
cant find a way to overclock under win7 without tools..
cant find a way to overclock under win7 without tools..
Not with phoenix. Phoenix is strictly a miner. No eyecandy or extras. Just a miner.
is there any way to set the gpu/mem clock and the voltage via some flag/command?
cant find a way to overclock under win7 without tools..
cant find a way to overclock under win7 without tools..
how exactly do I configure this? Using ubuntu 10.10 (or was it 10.04 - can't remember) LTS; download the source, extract it to my directory. Navigate to the folder with ./phoenix.py with terminal. Issue command ./phoenix.py -u .... like my previous version 1.75. Came back with an error saying missing -u
thks!
thks!
Any plans to support FPGA boards?
Also, when I try to start CPU mining, I get a "Fatal Error: Failed to load OpenCL kernel" I checked and it's there in the plugins folder.
Thanks! Love the software!
Also, when I try to start CPU mining, I get a "Fatal Error: Failed to load OpenCL kernel" I checked and it's there in the plugins folder.
Thanks! Love the software!
I'm not sure this is supported anymore.
M
Any plans to support FPGA boards?
Also, when I try to start CPU mining, I get a "Fatal Error: Failed to load OpenCL kernel" I checked and it's there in the plugins folder.
Thanks! Love the software!
Also, when I try to start CPU mining, I get a "Fatal Error: Failed to load OpenCL kernel" I checked and it's there in the plugins folder.
Thanks! Love the software!
Wrote the config file based on the example DOC and the main phoenix 2 thread and still not working, starts up and shows [DISCONNECTED]
phoenix is very confusing imho. unless you have the 5000 series, I wouldn't bother with it.
M
Not really... i pretty much copy pasted the config and made a few changes based on how i want to mine, voila, runs fine..
config for one of my miners. user/pass is redacted
I'm using phoenix 2.0 successfully with four 5870s. It took a bit to work as the sample config didn't work and the documentation is lacking. Plus the output is horrible.. gives you very little info. cgminer is worlds better imho. The only reason I'm using phoenix is it appears to give me a better hashrate than cgminer does on my 5870s, although I'm not convinced it's not lying to me. Every pool I've pointed it to gives me a lower reading thatn phoenix does.
M
Wrote the config file based on the example DOC and the main phoenix 2 thread and still not working, starts up and shows [DISCONNECTED]
phoenix is very confusing imho. unless you have the 5000 series, I wouldn't bother with it.
M
Not really... i pretty much copy pasted the config and made a few changes based on how i want to mine, voila, runs fine..
config for one of my miners. user/pass is redacted
Code:
[general]
backend = http://z:[email protected]:8337
backups = http://z:[email protected]:8337
verbose = true
[cl:1:1]
name = GPU 1 5870 980
kernel = phatk2
AGGRESSION = 6
VECTORS = true
BFI_INT = true
WORKSIZE = 128
[cl:1:2]
name = GPU 2 5830 880
kernel = phatk2
AGGRESSION = 14
VECTORS = true
BFI_INT = true
WORKSIZE = 128
[web]
disable = true
Wrote the config file based on the example DOC and the main phoenix 2 thread and still not working, starts up and shows [DISCONNECTED]
phoenix is very confusing imho. unless you have the 5000 series, I wouldn't bother with it.
M
Wrote the config file based on the example DOC and the main phoenix 2 thread and still not working, starts up and shows [DISCONNECTED]
Does 2.0.0 offer any hashing improvements over 1.7.x?
Can someone who has it working answer this? Is it worth the upgrade?
thanks.
It was worth it for me. I'm getting between 20-25 Mhash/s more with a 6870, depending on aggression.
Does 2.0.0 offer any hashing improvements over 1.7.x?
Can someone who has it working answer this? Is it worth the upgrade?
thanks.
No news on this? Am I the only one getting this? I've tried other pools and it still happens. Connection/pool issues seem to trigger it though.
Is Phoenix 2 even actively maintained/developed anymore?
Is Phoenix 2 even actively maintained/developed anymore?
I just found all of my phoenix 2.0.0 miners at 0 Khash/s, and this was on multiple machines.
They were mining Eligius with p2pool as fallback. Here is a sample of the log output. Restarting the program fixed the problem. Could this be a bug in Phoenix?
In Windows this happens:
It's a bit different in Linux, I actually get a stack trace:
They were mining Eligius with p2pool as fallback. Here is a sample of the log output. Restarting the program fixed the problem. Could this be a bug in Phoenix?
In Windows this happens:
Code:
[18:48:43] [cl:0:0] Result 00000000d3149da4... REJECTED
[18:48:43] LP: New work pushed
[18:48:43] Server gave new work; passing to WorkQueue
[18:48:43] [cl:0:0] Result 00000000cf3ee5c4... REJECTED
[18:48:46] Reject reason: bad-prevblk
[18:48:46] [cl:0:0] Result 00000000606afd88... REJECTED
[18:53:46] Warning: work queue empty, miner is idle
[18:58:33] [cl:0:0] Result 000000002a9c5347... REJECTED
[18:58:33] [cl:0:0] Result 000000009d0e76a8... REJECTED
[18:58:42] [cl:0:0] Result 0000000025bc2abc... REJECTED
[18:58:43] Reject reason: bad-prevblk
[18:58:43] [cl:0:0] Result 0000000041eb0e5c... REJECTED
[18:58:44] [cl:0:0] Result 00000000a3622a2f... REJECTED
[19:08:34] [cl:0:0] Result 00000000ebf906a8... REJECTED
[19:08:42] [cl:0:0] Result 000000005abb5555... REJECTED
[19:08:45] Reject reason: bad-prevblk
[19:08:45] [cl:0:0] Result 000000000a14e39e... REJECTED
[19:08:46] [cl:0:0] Result 0000000030b3bc31... REJECTED
[19:18:05] Disconnected from server
[0 Khash/s] [122136 Accepted] [469 Rejected] [DISCONNECTED]
It's a bit different in Linux, I actually get a stack trace:
Code:
[03:55:27] [cl:0:2] Result 0000000071f774c9... ACCEPTED
[03:55:36] LP: New work pushed
[03:55:36] Server gave new work; passing to WorkQueue
[03:55:36] New block (WorkQueue)
[03:55:37] LP: New work pushed
[03:55:37] Server gave new work; passing to WorkQueue
[03:55:37] Server gave work from the previous block, ignoring.
[03:55:38] Server gave new work; passing to WorkQueue
[03:55:38] Server gave work from the previous block, ignoring.
[03:55:40] Server gave new work; passing to WorkQueue
[03:55:40] Server gave work from the previous block, ignoring.
[03:55:42] Server gave new work; passing to WorkQueue
[03:55:42] Server gave work from the previous block, ignoring.
[03:55:44] Server gave new work; passing to WorkQueue
[03:55:44] Server gave work from the previous block, ignoring.
[03:55:49] Disconnected from server
[03:55:51] [cl:0:2] Result 00000000be43fc34... REJECTED
[03:55:59] Warning: work queue empty, miner is idle
[03:56:00] Connected to server
[03:56:00] Server gave new work; passing to WorkQueue
[03:56:00] Server gave work from the previous block, ignoring.
[03:56:00] Server gave new work; passing to WorkQueue
[03:56:00] Server gave work from the previous block, ignoring.
[03:56:01] Server gave new work; passing to WorkQueue
[03:56:01] Server gave work from the previous block, ignoring.
[03:56:02] Server gave new work; passing to WorkQueue
[03:56:02] Server gave work from the previous block, ignoring.
[03:56:07] Disconnected from server
[03:56:22] Couldn't connect to server, switching backend...
[0 Khash/s] [1033 Accepted] [71 Rejected] [DISCONNECTED]Unhandled error in Deferred:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1076, in gotResult
_inlineCallbacks(r, g, deferred)
File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1066, in _inlineCallbacks
deferred.errback()
File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 388, in errback
self._startRunCallbacks(fail)
File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 455, in _startRunCallbacks
self._runCallbacks()
------
File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 542, in _runCallbacks
current.result = callback(current.result, *args, **kw)
File "/home/bitcoin/bitcoin/phoenix-2.0.0/phoenix2/backend/RPCProtocol.py", line 149, in errback
self.root._failure()
File "/home/bitcoin/bitcoin/phoenix-2.0.0/phoenix2/backend/RPCProtocol.py", line 483, in _failure
self.runCallback('failure')
File "/home/bitcoin/bitcoin/phoenix-2.0.0/phoenix2/backend/ClientBase.py", line 51, in runCallback
func(*args)
File "/home/bitcoin/bitcoin/phoenix-2.0.0/phoenix2/core/PhoenixCore.py", line 449, in onFailure
self.switchURL(nextBackend)
File "/home/bitcoin/bitcoin/phoenix-2.0.0/phoenix2/core/PhoenixCore.py", line 266, in switchURL
self.connection.disconnect()
File "/home/bitcoin/bitcoin/phoenix-2.0.0/phoenix2/backend/RPCProtocol.py", line 321, in disconnect
self.poller.closeConnection()
File "/home/bitcoin/bitcoin/phoenix-2.0.0/phoenix2/backend/RPCProtocol.py", line 56, in closeConnection
self.connection.sock._sock.shutdown(socket.SHUT_RDWR)
socket.error: [Errno 107] Transport endpoint is not connected
^CTraceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1158, in run
self.mainLoop()
File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1167, in mainLoop
self.runUntilCurrent()
File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 811, in runUntilCurrent
self.fireSystemEvent("shutdown")
File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 628, in fireSystemEvent
event.fireEvent()
------
File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 407, in fireEvent
result = callable(*args, **kwargs)
File "/home/bitcoin/bitcoin/phoenix-2.0.0/phoenix2/core/PhoenixCore.py", line 106, in _shutdown
self.switchURL(None)
File "/home/bitcoin/bitcoin/phoenix-2.0.0/phoenix2/core/PhoenixCore.py", line 266, in switchURL
self.connection.disconnect()
File "/home/bitcoin/bitcoin/phoenix-2.0.0/phoenix2/backend/RPCProtocol.py", line 321, in disconnect
self.poller.closeConnection()
File "/home/bitcoin/bitcoin/phoenix-2.0.0/phoenix2/backend/RPCProtocol.py", line 56, in closeConnection
self.connection.sock._sock.shutdown(socket.SHUT_RDWR)
socket.error: [Errno 107] Transport endpoint is not connected
^\Quit
Thanks.
My 5970's are giving a lower hashrate with unit4 vectors, but i didnt tested only with my 6850 yet.
I'm going to test it tomorrow.
My 5970's are giving a lower hashrate with unit4 vectors, but i didnt tested only with my 6850 yet.
I'm going to test it tomorrow.
For my 5970s, I use unit2 vectors. I seem to remember testing unit4 vectors when it was first added to the kernel and getting a lower hash rate. I could be wrong, but I think unit4 vectors were introduced to take advantage of the 6000 series architecture.
Test both of the vectors out for a few minutes. You should be able to easily tell which one will give you the best hash rate for each of your cards.
Test both of the vectors out for a few minutes. You should be able to easily tell which one will give you the best hash rate for each of your cards.
Hi!
I just started using this miner, because i continued mining after 6 months.
I figured out almost all the settings (the documentation needs to be more detailed, i think).
With a HD5970 and a HD6850 wich "vectors" should i use?
Sorry about my english
I just started using this miner, because i continued mining after 6 months.
I figured out almost all the settings (the documentation needs to be more detailed, i think).
With a HD5970 and a HD6850 wich "vectors" should i use?
Sorry about my english
This probably won't help, but here's what I know.
For one of my rigs running LinuxCoin, which has three 5970s (6 GPUs total), the OpenCL devices (GPUs) are identified as follows:
[cl:0:0]
[cl:0:1]
[cl:0:2]
[cl:0:3]
[cl:0:4]
[cl:0:5]
I do not know what the first number after "cl" means or how it could be anything other than 0. See, I told you this might not help.
For one of my rigs running LinuxCoin, which has three 5970s (6 GPUs total), the OpenCL devices (GPUs) are identified as follows:
[cl:0:0]
[cl:0:1]
[cl:0:2]
[cl:0:3]
[cl:0:4]
[cl:0:5]
I do not know what the first number after "cl" means or how it could be anything other than 0. See, I told you this might not help.
I always thought the first digit after the "cl" refered to the platform of GPU you have. Like you'd see different numbers in there if your rig had 5XXX series cards mixed in with 6XXX series cards. iono for sure though.
Nope. AMD APP isn't the only OpenCL computing platform. There is also ATI Stream (also known as SDK 2.1, and yes it IS a seperate platform from AMD APP which is SDK 2.4 and higher), and Intel opencl, and probably many others. I have 2.1 and 2.6 installed on the same computer. Platform 0 for me is SDK 2.6, and platform 1 is SDK 2.1. I have both installed because 2.1 is faster, but isn't normally detected by some miners unless AMD APP is installed too.
This probably won't help, but here's what I know.
For one of my rigs running LinuxCoin, which has three 5970s (6 GPUs total), the OpenCL devices (GPUs) are identified as follows:
[cl:0:0]
[cl:0:1]
[cl:0:2]
[cl:0:3]
[cl:0:4]
[cl:0:5]
I do not know what the first number after "cl" means or how it could be anything other than 0. See, I told you this might not help.
For one of my rigs running LinuxCoin, which has three 5970s (6 GPUs total), the OpenCL devices (GPUs) are identified as follows:
[cl:0:0]
[cl:0:1]
[cl:0:2]
[cl:0:3]
[cl:0:4]
[cl:0:5]
I do not know what the first number after "cl" means or how it could be anything other than 0. See, I told you this might not help.
I always thought the first digit after the "cl" refered to the platform of GPU you have. Like you'd see different numbers in there if your rig had 5XXX series cards mixed in with 6XXX series cards. iono for sure though.
Yeah, that sounds like the right idea to me.
This probably won't help, but here's what I know.
For one of my rigs running LinuxCoin, which has three 5970s (6 GPUs total), the OpenCL devices (GPUs) are identified as follows:
[cl:0:0]
[cl:0:1]
[cl:0:2]
[cl:0:3]
[cl:0:4]
[cl:0:5]
I do not know what the first number after "cl" means or how it could be anything other than 0. See, I told you this might not help.
For one of my rigs running LinuxCoin, which has three 5970s (6 GPUs total), the OpenCL devices (GPUs) are identified as follows:
[cl:0:0]
[cl:0:1]
[cl:0:2]
[cl:0:3]
[cl:0:4]
[cl:0:5]
I do not know what the first number after "cl" means or how it could be anything other than 0. See, I told you this might not help.
I always thought the first digit after the "cl" refered to the platform of GPU you have. Like you'd see different numbers in there if your rig had 5XXX series cards mixed in with 6XXX series cards. iono for sure though.
Jump to: