Hey Cyper, What script and/or miner are you using in that one pic showing PuTTy?
Autominer - very handy.
|
|
|
I have 4x XFX 5870 clocked @ 960Mhz Core and 300Mhz Memory = 4x437Mhash/s = 1748Mhash/s absolutely stable speed.
|
|
|
Did you leave a VNC on overnight?
Hm, good question. I closed the VNC Viewer window and then put the machine to sleep. But this morning I found 2 vnc processes in the Task Manager, which apparently did not close. Would that matter when the machine is sleeping? Is it still maintaining a connection to the Ubuntu machine? Also when using putty and after screen -x amm -p 0 how do I get back to the terminal so I can write commands? Also is this a bug with Putty, screen or your script? It was fine 2 minutes ago, but now it does not show the temp of the 4th card.
|
|
|
Do you think you can help with THIS? I left my machine running during the night using your script and when I woke up it has stopped mining. I tried connecting using VNC but I couldn't, so I connected via SSH and did sudo reboot. So the machine was responsive, but it stopped mining for some reason. Any ideas?
|
|
|
So I just started mining using: 4x XFX 5870 @ 960Mhz Core = 434 Mhash/s = 70 degrees maximum temp. Gigabyte GA-770T-D3L, AMD 770, AM3 AMD Athlon II X2 250 Ubuntu 11.04 32bit SDK 2.1 Latest Phoenix using phatk kernel I left the machine mining at 5am and went to bed. When I woke up it wasn't mining so I tried to connect unsuccessfully using VNC. I then connected using SSH successfully and did sudo reboot. I checked the logs after the reboot they indicated that it stopped 2 hours earlier. Here are the kern.log and syslogIs this normal? Jul 1 09:40:32 Woody kernel: [17160.748408] INFO: task phoenix.py:3170 blocked for more than 120 seconds. If you need any other logs please ask. How can I find out why it stopped mining?
|
|
|
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
|
|
|
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.
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.
|
|
|
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?
|
|
|
Do screen -ls
cyper@Woody:~/Autominer$ screen -ls No 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.
|
|
|
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
|
|
|
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.
|
|
|
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.
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?
|
|
|
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.
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.
|
|
|
Well I got it working and now I'm fighting the SSH thing. Also I managed to start it and then running stopmining.sh does not seem to kill all instances - one card continued working no matter how many times and executed the stopmining script. Regarding SSH am I supposed to see the same fancy window as when ran locally? I ran: sudo DISPLAY=:0 ./startmining.sh /home/cyper/Autominer And get this: Autominer Initialization... Starting in /home/cyper/Autominer If this is the wrong directory, run "./startmining /path/to/Autominer" instead! If the script fails, check the log file (default: /var/log/Autominer.log) for details of why. Most likely, you haven't configured Autominer correctly. If you can't work it out, don't give up, post at http://forum.bitcoin.org/index.php?topic=19861.0 and I'll try to help!
|
|
|
Well I fixed it and now it does not want to start mining: Latest cards.lib file: http://paste.ubuntu.com/636058/Also which part of the GUI/Desktop Environment do I need to stop when using SSH? Is it Gnome and then I just login in the console?
|
|
|
Ok I got them working then I closed the console, but they continued working. Well I used stopmining.sh which worked. Is that the only way to stop them?
And the main problem - the speeds are half of what I should get. ~210 Mhash/s compared to 435 Mhash/s
I just found out phoenixQueueSize[0]="256" and I'm absolutely certain I pressed 1 as default during setup.
|
|
|
Additionally on my initial setup I answer 0 to this question: Which Phoenix device number is this card? (default: 0) But now when I though about it I think it should be 1, as phoenix sees my CPU as device 0 and my 4 cards as 1,2,3,4
|
|
|
Wow that you for your quick replies. I'm make sure to send you some coins when I mine some Btw is this relevant to me? My rig will be in the next room in headless mode (no monitor) and I'll control it using Ubuntu Remote Desktop + Windows VNC Viewer. Do you want to use headless mode? This will NOT load Xterm at script open.
|
|
|
|