[Linux] Autominer v0.3.2.6 - GPU Monitor, Downtime Swapper, New Interface - page 3.

mrpeterc

newbie

Activity: 11

Merit: 0

That did it, thank you for the help....

CYPER

hero member

Activity: 812

Merit: 502

Quote from: mrpeterc on July 06, 2011, 03:22:41 PM

I am on the local machine and it popped up the Autominer screen and is mining, I checked the cores both are running 99%, I guess it most be the way I display in ssh? Thank you, I am glad the software is running....if you could help me with the ssh part that would be great...

The important thing is that it works

Try

Code:

sudo DISPLAY=:0 ./startmining.sh

or

Code:

DISPLAY=:0 sudo ./startmining.sh

I'm not sure of the exact structure.

I have the same problem, but it does not bother me, as I'm using VNC to connect to the machine and start the miner locally and then I just connect via SSH to monitor it using sudo screen -x amm -p 0

I'd prefer mining instead of troubleshooting it Wink

mrpeterc

newbie

Activity: 11

Merit: 0

I am on the local machine and it popped up the Autominer screen and is mining, I checked the cores both are running 99%, I guess it most be the way I display in ssh? Thank you, I am glad the software is running....if you could help me with the ssh part that would be great...

CYPER

hero member

Activity: 812

Merit: 502

First try to run it locally to make sure everything is working as it should. Can you do that?

mrpeterc

newbie

Activity: 11

Merit: 0

Thank you for your responese,

autoOpenXterm=1, I am running this via ssh, is there another screen I need activate?

CYPER

hero member

Activity: 812

Merit: 502

The text you are getting doesn't indicate an error as it appears everytime, even if everything works fine

When you write sudo ./startmining.sh does an additional window open?

Also did you configure autoOpenXterm=1 or autoOpenXterm=0 in common.lib?

mrpeterc

newbie

Activity: 11

Merit: 0

Thank you for your script, everything I read it is wonderful. I have tried several different ways to start this but I keep getting the same error, I check for a log and no log exists. Cany you help me...btw I am very new at this so please be patient.

This is a copy of the message I get: I have 2 Radeon 6950, connecting to bitcoinpool.com, my miners work fine and that part I know works.

miningrig3@miningrig3-MS-7599:~/Autominer$ sudo ./startmining.sh
Autominer Initialization...
Starting in /home/miningrig3/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!

Reikoku

full member

Activity: 140

Merit: 100

firstbits: 1kwc1p

Quote from: CYPER on July 04, 2011, 11:17:40 PM

When I start the miner locally everything is fine, but it does not start via SSH.
I connect and then I write:

Code:

cd Autominer
sudo ./startmining.sh
write my password

Try doing sudo DISPLAY=:0 ./startmining.sh (or that might be DISPLAY=:0 sudo ./startmining.sh). It can only open over ssh if you set DISPLAY variable.

Quote from: CYPER on July 05, 2011, 10:07:18 PM

Is it very difficult to implement manual switching between pools?
Currently I have created different common.lib and cards.lib files for each set of pools such as:

Deepbit and Slush
Deepbit and BTC Guild
Slush and BTC Guild

But it would be awesome if there is an easy way to quickly switch to a different pool manually when desired and not just when the pool is down.

Thank you.

I don't think it would be very difficult to do this if you know some bash script. You'd just make a new script that cycles through all devices, kills active processes then starts new miners up on the pool passed to it as an argument.

CYPER

hero member

Activity: 812

Merit: 502

Is it very difficult to implement manual switching between pools?
Currently I have created different common.lib and cards.lib files for each set of pools such as:

Deepbit and Slush
Deepbit and BTC Guild
Slush and BTC Guild

But it would be awesome if there is an easy way to quickly switch to a different pool manually when desired and not just when the pool is down.

Thank you.

wonderbread

newbie

Activity: 11

Merit: 0

Works well, saved me hacking one together myself.

Flawless so far.

CYPER

hero member

Activity: 812

Merit: 502

I've noticed that when the terminal or any other windows are open at the Ubuntu machine then the speed is playing, but when I close all windows the speed is rock solid, so I disabled xterm. That is not a problem/bug, just an observation on my part

But I do have a problem:

When I start the miner locally everything is fine, but it does not start via SSH.
I connect and then I write:

Code:

cd Autominer
sudo ./startmining.sh
write my password

So for now I connect using VNC, start it locally, close the Terminal and any other windows, close the VNC viewer and then connect using SSH and proceed with sudo screen -x amm -p 0
But I would like to be able to start it remotely via SSH and not use VNC if possible.

Any ideas?

Reikoku

full member

Activity: 140

Merit: 100

firstbits: 1kwc1p

Quote from: M4v3R on July 04, 2011, 02:03:01 AM

@Reikoku: You were right. It works now. I have one bug report though:

The startmining.sh script works from any directory and this is good. But the stopmining.sh works only from Autominer dir. I just copied and pasted the lines that get directory from paratemer and sets it to current directory to stopmining.sh and now it works ok

. I need that, because for some reason when I want to start my miners at boot, this doesn't work:

cd ~/Autominer
sh startmining.sh

But this works:

cp ~/Autominer/startmining.sh /usr/bin/startmining
...
startmining

Not sure why the first doesn't work. Try cd ~/Autominer && ./startmining.sh instead.

M4v3R

hero member

Activity: 607

Merit: 500

@Reikoku: You were right. It works now. I have one bug report though:

The startmining.sh script works from any directory and this is good. But the stopmining.sh works only from Autominer dir. I just copied and pasted the lines that get directory from paratemer and sets it to current directory to stopmining.sh and now it works ok

. I need that, because for some reason when I want to start my miners at boot, this doesn't work:

cd ~/Autominer
sh startmining.sh

But this works:

cp ~/Autominer/startmining.sh /usr/bin/startmining
...
startmining

Reikoku

full member

Activity: 140

Merit: 100

firstbits: 1kwc1p

Try changing card identifier names in cards.lib to start with a letter instead of a number.

It's an awkward convention of screen that session names must start with a letter.

M4v3R

hero member

Activity: 607

Merit: 500

First of all, thanks for the Autominer. It's really great! I have a (small) problem with it though:

The GPU* screens do not attach correctly, as shown above. The miner is working and it mines fine, but the status windows don't work. Any ideas why?

Reikoku

full member

Activity: 140

Merit: 100

firstbits: 1kwc1p

That's a bug with aticonfig, I assume, since all the script is doing is passing 'aticonfig --adapter=all --odgt' every 15 seconds.

To get out of screen, just hit Ctrl-A, then D.

I'm not sure about the VNC windows, even having the VNC server open may be a memory issue if it's caching.

CYPER

hero member

Activity: 812

Merit: 502

Quote from: Reikoku on July 01, 2011, 08:46:13 AM

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.

Reikoku

full member

Activity: 140

Merit: 100

firstbits: 1kwc1p

Quote from: CYPER on July 01, 2011, 08:28:16 AM

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?

Usually that issue is related to running out of free memory. :S

Did you leave a VNC on overnight?

CYPER

hero member

Activity: 812

Merit: 502

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?

m3ta

sr. member

Activity: 435

Merit: 250

Quote from: Reikoku on 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.

2.4.
Tried both 2.1 and 2.4. I now consider the speed decrease a deserved "price" for a so-handy script. Nicely done!

Quote from: Reikoku on July 01, 2011, 07:12:16 AM

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.

I confirm Phoenix runs on Mac, and screen is easily installed through MacPorts.

Topic: [Linux] Autominer v0.3.2.6 - GPU Monitor, Downtime Swapper, New Interface - page 3. (Read 23494 times)