With effort this could run on Mac, as Mac is compatible with bash script, you'd just have to get screen working.
I'm not sure if Phoenix runs on Mac though.
As far as I know, to make it run on Windows would require switching to another programming language and forgoing the core of the program (GNU Screen).
Topic: [Linux] Autominer v0.3.2.6 - GPU Monitor, Downtime Swapper, New Interface - page 4. (Read 23494 times)
July 01, 2011, 07:12:16 AM
July 01, 2011, 06:32:00 AM
can this gr8 script be run on mac/windows? As I have 2 computers (1 PC-now upgraded to radeon HD 6950 GPU and my macBook Pro used for backup mining).
Can a GUI version be made as well for these 2 platforms (Win/Mac)?
Is it possible for there to be a feature where the GUI loads initially until you start mining and then it goes to terminal so as to kill overhead running a GUI all day long would create?
Thank you
Can a GUI version be made as well for these 2 platforms (Win/Mac)?
Is it possible for there to be a feature where the GUI loads initially until you start mining and then it goes to terminal so as to kill overhead running a GUI all day long would create?
Thank you
July 01, 2011, 12:58:33 AM
Are you on SDK 2.1 or 2.4? If you're on 2.1 modify back to poclbm kernel instead of phatk.
I'll fix .screenrc for the next release, thanks.
I'll fix .screenrc for the next release, thanks.
June 30, 2011, 11:56:57 PM
Tested working in Debian Squeeze and Ubuntu Natty.
For anyone having trouble with screen terminating repeatedly, add this to your ~/.screenrc
Plus one of the following:
For 64-bit SDK 2.4:
For 32-bit SDK 2.4:
For 64-bit SDK 2.1:
For 32-bit SDK 2.1:
For anyone having trouble with screen terminating repeatedly, add this to your ~/.screenrc
Quote
setenv DISPLAY ":0"
Plus one of the following:
For 64-bit SDK 2.4:
Quote
setenv LD_LIBRARY_PATH "/opt/AMD-APP-SDK-v2.4-lnx64/lib/x86_64"
For 32-bit SDK 2.4:
Quote
setenv LD_LIBRARY_PATH "/opt/AMD-APP-SDK-v2.4-lnx32/lib/x86"
For 64-bit SDK 2.1:
Quote
setenv LD_LIBRARY_PATH "/opt/ati-stream-sdk-v2.1-lnx64/lib/x86_64/"
For 32-bit SDK 2.1:
Quote
setenv LD_LIBRARY_PATH "//opt/ati-stream-sdk-v2.1-lnx32/lib/x86/"
This was a lifesaver! Thank you.
@Reikoku: the .screenrc has a small typo on -k k6: it says "kindkey" instead of "bindkey".
Phoenix 1.50 gives me 13Mhash/sec less than the r101 i used with the same settings... i wonder if the XML-RPC is worth the speed decrease...
June 30, 2011, 08:52:29 PM
Ctrl-A then release and press the number.
June 30, 2011, 08:38:01 PM
Is it Ctrl + A + Number all simultaneously
or
Ctrl + A then release and press the number
Btw I'm going for a shower and something to eat after that. If you are still around later on I will write again
Thank you again for being so helpful
or
Ctrl + A then release and press the number
Btw I'm going for a shower and something to eat after that. If you are still around later on I will write again
Thank you again for being so helpful
June 30, 2011, 08:31:36 PM
Ctrl-A then number should work flawlessly. :/
You have to press Ctrl-A every time you want to press a number.
You have to press Ctrl-A every time you want to press a number.
June 30, 2011, 08:28:23 PM
Try ctrl-a, then the screen number (will be 0,1,2,3 etc).
The next release will really help you as it has a dedicated Phoenix diagnostic tool, but Dropbox is being a nightmare.
The next release will really help you as it has a dedicated Phoenix diagnostic tool, but Dropbox is being a nightmare.
This SSH thing is driving me crazy, maybe I should stick with running it locally using Gnome even if it eats some resources.
It does not want to connect + Ctrl+A + numbers works erratically or just using Ctrl+A switches between 2 screens.
June 30, 2011, 08:21:07 PM
Try ctrl-a, then the screen number (will be 0,1,2,3 etc).
The next release will really help you as it has a dedicated Phoenix diagnostic tool, but Dropbox is being a nightmare.
The next release will really help you as it has a dedicated Phoenix diagnostic tool, but Dropbox is being a nightmare.
June 30, 2011, 08:19:27 PM
try sudo screen -x amm -p 0
Ok, got the fancy screen under SSH, but it does not connect + F7-F8 doesn not work so how do I change screens?
June 30, 2011, 08:11:29 PM
Do screen -ls
cyper@Woody:~/Autominer$ screen -lsNo Sockets found in /var/run/screen/S-cyper.
Also this is my attempt at running it via SSH:
I connect, enter my username, then password and then I can change directories, so I'm definitely connected.
screen -x amm -p 0 will produce There is no screen to be attached matching amm and I can hear the machine does not start mining.
try sudo screen -x amm -p 0
I'm not an expert on sudo but I think it would attach the screen to root's session so you might have to be root to use it.
June 30, 2011, 08:08:17 PM
Do screen -ls
cyper@Woody:~/Autominer$ screen -lsNo Sockets found in /var/run/screen/S-cyper.
Also this is my attempt at running it via SSH:
I connect, enter my username, then password and then I can change directories, so I'm definitely connected.
screen -x amm -p 0 will produce There is no screen to be attached matching amm and I can hear the machine does not start mining.
June 30, 2011, 08:05:06 PM
If so, try stopmining.sh, then change common.lib and set autoOpenXterm=0, then startmining.sh, then open a terminal, make it big and do screen -x amm -p 0.
I did that and my machine started mining without the fancy window popping out.
then screen -x amm -p 0 said:
There is no screen to be attached matching amm
Do screen -ls
June 30, 2011, 08:03:19 PM
If so, try stopmining.sh, then change common.lib and set autoOpenXterm=0, then startmining.sh, then open a terminal, make it big and do screen -x amm -p 0.
I did that and my machine started mining without the fancy window popping out.
then screen -x amm -p 0 said:
There is no screen to be attached matching amm
June 30, 2011, 07:59:04 PM
Oh, that's an issue with screen, I get the same sometimes when on my 3 GPU machine, the only fix I've found is restarting startmining.sh but it's in my bugs to fix list.
June 30, 2011, 07:57:58 PM
On a second attempt it connected immediately.
Here is what I mean by missing GPUs (the black line at the bottom):
and cycling through the screens does not show the missing GPUs.
Here is what I mean by missing GPUs (the black line at the bottom):
and cycling through the screens does not show the missing GPUs.
June 30, 2011, 07:52:46 PM
Have you successfully connected via ssh, or are you in a local terminal?
Try doing 'screen -x amm -p 0' on your local machine (the one running the miner), as that's the exact command that's being run on the local terminal.
If by the information row you mean where it shows the hashes on my screenshot, you have to enable xmlRPC to make that work. See first post for details.
Try doing 'screen -x amm -p 0' on your local machine (the one running the miner), as that's the exact command that's being run on the local terminal.
If by the information row you mean where it shows the hashes on my screenshot, you have to enable xmlRPC to make that work. See first post for details.
Yes I have successfully connected to the machine.
And yes the xmlRPC was enabled and working, apart from not showing all GPUs screens, but it was correctly showing the total speed.
I just restarted and it tries to connect to dropbox to check for newer version but as the site is down it won't. Will it start mining in that case?
Should do after some failed attempts.
Can you show me what it looks like when it doesn't show all GPUs? Is it because your xterm is too small?
If so, try stopmining.sh, then change common.lib and set autoOpenXterm=0, then startmining.sh, then open a terminal, make it big and do screen -x amm -p 0.
June 30, 2011, 07:51:46 PM
Have you successfully connected via ssh, or are you in a local terminal?
Try doing 'screen -x amm -p 0' on your local machine (the one running the miner), as that's the exact command that's being run on the local terminal.
If by the information row you mean where it shows the hashes on my screenshot, you have to enable xmlRPC to make that work. See first post for details.
Try doing 'screen -x amm -p 0' on your local machine (the one running the miner), as that's the exact command that's being run on the local terminal.
If by the information row you mean where it shows the hashes on my screenshot, you have to enable xmlRPC to make that work. See first post for details.
Yes I have successfully connected to the machine.
And yes the xmlRPC was enabled and working, apart from not showing all GPUs screens, but it was correctly showing the total speed.
I just restarted and it tries to connect to dropbox to check for newer version but as the site is down it won't. Will it start mining in that case?
June 30, 2011, 07:45:03 PM
Re: stopmining.sh not killing, try running the following:
killall screen
killall phoenix.py
It could be that when you changed a card identifier, it lost one or something. Usually it kills everything.
On ssh, you should get the exact same screen, when you do 'screen -x amm -p 0'. The screenshot in the first post (which is down thanks to Dropbox) was taken in ssh.
killall screen
killall phoenix.py
It could be that when you changed a card identifier, it lost one or something. Usually it kills everything.
On ssh, you should get the exact same screen, when you do 'screen -x amm -p 0'. The screenshot in the first post (which is down thanks to Dropbox) was taken in ssh.
I'll try these commands next time I can't stop it.
I haven't forgotten 'screen -x amm -p 0 but it says:
There is no screen to be attached matching amm.
The first command does not work, cause I can hear when it starts mining
Locally everything works great apart from the information row where it does not display all GPUs.
Have you successfully connected via ssh, or are you in a local terminal?
Try doing 'screen -x amm -p 0' on your local machine (the one running the miner), as that's the exact command that's being run on the terminal which you say works by this code:
# Load Xterm if not running headless
if [ "$autoOpenXterm" -eq "1" ]; then
xterm -T "Autominer" -e screen -x amm -p 0 &
fi
As long as this works, your ssh is probably not connected.
If by the information row you mean where it shows the hashes on my screenshot, you have to enable xmlRPC to make that work. See first post for details.
June 30, 2011, 07:42:21 PM
Re: stopmining.sh not killing, try running the following:
killall screen
killall phoenix.py
It could be that when you changed a card identifier, it lost one or something. Usually it kills everything.
On ssh, you should get the exact same screen, when you do 'screen -x amm -p 0'. The screenshot in the first post (which is down thanks to Dropbox) was taken in ssh.
killall screen
killall phoenix.py
It could be that when you changed a card identifier, it lost one or something. Usually it kills everything.
On ssh, you should get the exact same screen, when you do 'screen -x amm -p 0'. The screenshot in the first post (which is down thanks to Dropbox) was taken in ssh.
I'll try these commands next time I can't stop it.
I haven't forgotten 'screen -x amm -p 0 but it says:
There is no screen to be attached matching amm.
The first command does not work, cause I can hear when it starts mining
Locally everything works great apart from the information row where it does not display all GPUs.
Jump to: