Any chance of a download mirror for the file?
I'd sorely like to, but I don't have anywhere to ftp dump it to right now. Check back in 30 mins or so and Dropbox should be back up (they're migrating to another datacentre).
Topic: [Linux] Autominer v0.3.2.6 - GPU Monitor, Downtime Swapper, New Interface - page 5. (Read 23494 times)
June 30, 2011, 07:41:19 PM
I'd sorely like to, but I don't have anywhere to ftp dump it to right now. Check back in 30 mins or so and Dropbox should be back up (they're migrating to another datacentre).
June 30, 2011, 07:39:43 PM
Any chance of a download mirror for the file?
June 30, 2011, 07:37:41 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.
June 30, 2011, 07:35:41 PM
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!
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!
June 30, 2011, 07:13:37 PM
Your GPU load is 0 apparently.
Can you grab the latest version and run the new checkphoenix.sh script?
Edit: Issue with Dropbox's server right now apparently. Joy.
Edit2: Apparently they're migrating data and should be about 1 hour of downtime. This is where I really need a mirror.
Can you try Phoenix with the following options from the command line? (you need to be in phoenix dir)
./phoenix.py -q 1 -v -u http://CYPER_GPU1:password@nl.btcguild.com:8332 -k phatk PLATFORM=0 DEVICE=1 WORKSIZE=256 AGGRESSION=11 BFI_INT FASTLOOP=false VECTORS
If this works, double check your phoenix directory (in common.lib) is correct, as that's the exact command the script is sending.
Can you grab the latest version and run the new checkphoenix.sh script?
Edit: Issue with Dropbox's server right now apparently. Joy.
Edit2: Apparently they're migrating data and should be about 1 hour of downtime. This is where I really need a mirror.
Can you try Phoenix with the following options from the command line? (you need to be in phoenix dir)
./phoenix.py -q 1 -v -u http://CYPER_GPU1:password@nl.btcguild.com:8332 -k phatk PLATFORM=0 DEVICE=1 WORKSIZE=256 AGGRESSION=11 BFI_INT FASTLOOP=false VECTORS
If this works, double check your phoenix directory (in common.lib) is correct, as that's the exact command the script is sending.
June 30, 2011, 05:48:13 PM
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?
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?
June 30, 2011, 05:40:13 PM
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.
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.
Try changing it to 1 and retry. That bit was an issue with the code which I will fix now and upload a new version, thanks.
Edit: Fixed in 0.3.2.4.
Running stopmining.sh is the only way to get them to stop, this is by design intent, because it means if you're remote monitoring and your ssh session dies, your miners keep working.
June 30, 2011, 05:31:18 PM
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.
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.
June 30, 2011, 05:19:02 PM
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.
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.
Quote
Do you want to use headless mode? This will NOT load Xterm at script open.
You might find it easier to control it with screen. Just install sshd on Ubuntu, then download Putty on Windows and open a terminal session. Type:
ssh username@ipaddressofminer
Once you're logged in, you can just do screen -x amm -p 0 to open up your screen session.
The reason why I say this is because Phoenix really reduces your computer's graphical responsiveness, and this can make it very slow over VNC. However, if you want to use VNC, you probably want Xterm to keep opening. It won't prevent you working headlessly if xterm does open, but it makes the screens look a bit uglier (they're restricted to the size of your xterm in terms of amount of space they can take up).
If you want to donate, feel free to test donateMode.
It gives me 0.5% of your mining capability.On the device, if Phoenix sees your GPUs as 1/2/3/4 you should choose 1/2/3/4. My phoenix sees my CPU as 3, GPUs as 0/1/2.
June 30, 2011, 05:14:33 PM
Additionally on my initial setup I answer 0 to this question:
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
Quote
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
June 30, 2011, 05:12:49 PM
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.
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.
Quote
Do you want to use headless mode? This will NOT load Xterm at script open.
June 30, 2011, 05:10:30 PM
During setup with ./configure.sh I used "y" instead of "yes" to answer the questions.
Is that a problem?
Is that a problem?
Yes, it only accepts 'yes' or 'no'. Anything else will go to the default (whichever is in caps).
With re: the first user/pass prompt: You can put anything in that part because those usernames and passwords will never be used by Autominer if you specify workers.
It first looks for worker details, then if it can't find those, it looks for common usernames & passwords.
June 30, 2011, 05:09:05 PM
Ok so this is the question where I just wrote some random stuff:
It asks the same questions for the main and backup pools.
Do I leave that blank?
Quote
If your cards use individual workers on this pool, just put anything here because it won't be used
Quote
What's your Password on the main pool you use? (default: x)
If you use workers, just put anything, it won't be used.
If you use workers, just put anything, it won't be used.
It asks the same questions for the main and backup pools.
Do I leave that blank?
June 30, 2011, 05:06:54 PM
During setup with ./configure.sh I used "y" instead of "yes" to answer the questions.
Is that a problem?
Is that a problem?
June 30, 2011, 05:04:37 PM
It's not related to screen, that just means phoenix didn't work, probably because you have no workers set up.
I suggest running the configure script again, don't power through it, look out for the part where it asks if you have workers and type 'yes'.
Not having XML-RPC wouldn't cause this issue, but enabling it allows you to see all your hash rates in the main window (see post 1 for details). I'd suggest ignoring this until everything else is working.
I suggest running the configure script again, don't power through it, look out for the part where it asks if you have workers and type 'yes'.
Not having XML-RPC wouldn't cause this issue, but enabling it allows you to see all your hash rates in the main window (see post 1 for details). I'd suggest ignoring this until everything else is working.
June 30, 2011, 04:57:10 PM
Thank you for your reply, but I think the problem is somehow related to screen judging by this image:
Also missing XML-RPC - is that a problem?
I've fixed the 4 instances of phoenixQueueSize to 1
Should I run the configure script again?
Also missing XML-RPC - is that a problem?
I've fixed the 4 instances of phoenixQueueSize to 1
Should I run the configure script again?
June 30, 2011, 04:41:30 PM
Change phoenixQueueSize to 1 for each card in cards.lib, then try again.
I think that parameter only supports values from 1-10.
Also, unless you removed them, your cards don't have workers attached in this cards.lib file.
It will ask you during configuration something like "Do you use workers for this card on main pool?"
Just type yes, then it'll take you through questions to set up usernames and passwords. Same for backup pool.
Don't use a password which matters for workers, they are sent across the net in plaintext.
I'm also not sure why it's put donateMode=0 four times instead of once, but that won't be causing the issue.
I think that parameter only supports values from 1-10.
Also, unless you removed them, your cards don't have workers attached in this cards.lib file.
It will ask you during configuration something like "Do you use workers for this card on main pool?"
Just type yes, then it'll take you through questions to set up usernames and passwords. Same for backup pool.
Don't use a password which matters for workers, they are sent across the net in plaintext.
I'm also not sure why it's put donateMode=0 four times instead of once, but that won't be causing the issue.
June 30, 2011, 04:35:06 PM
http://paste.ubuntu.com/636029/
http://paste.ubuntu.com/636030/
Also during setup it said that if I use workers I should enter anything in the username/password fields and so I did.
But then where do I enter my real username/passwords? I use 4x Ati 5870 and 4x workers = 1 for each card.
http://paste.ubuntu.com/636030/
Also during setup it said that if I use workers I should enter anything in the username/password fields and so I did.
But then where do I enter my real username/passwords? I use 4x Ati 5870 and 4x workers = 1 for each card.
June 30, 2011, 03:51:13 PM
Cyper, can you give me the contents of common.lib and cards.lib?
June 30, 2011, 03:23:49 PM
Jump to: