Check to be sure it's not throttling because of temp
It's actually running cooler than the card that is giving the higher hash rate. Bizzarre, there doesn't seem to be anything wrong with the card.
Topic: Ubuntu Natty Narwhal 11.04 Mining Guide / HOWTO - page 5. (Read 281372 times)
It's actually running cooler than the card that is giving the higher hash rate. Bizzarre, there doesn't seem to be anything wrong with the card.
Check to be sure it's not throttling because of temp
Nope crossfire is disabled.
Is crossfire enabled for some reason?
Thanks for the guide, I built my first rig using linuxcoin with 2 x 6970s, and it worked great, but I bought 2 x 6950s and just couldn't get it to work with those cards for some reason. Got it up and running with Ubuntu thanks to your instructions, but for some reason on one of my 6950s I am getting a hash rate of around 330 MH/s which is about what I'd expect, but only about 200 MH/s on the second one. Any help would be greatly appreciated.
step 15.
svn checkout http://svn.json-rpc.org/trunk/python-jsonrpc
the site has been down for a while. Is there a alternative?
Thanks
svn checkout http://svn.json-rpc.org/trunk/python-jsonrpc
the site has been down for a while. Is there a alternative?
Thanks
http://forum.bitcoin.org/index.php?topic=29028
step 15.
svn checkout http://svn.json-rpc.org/trunk/python-jsonrpc
the site has been down for a while. Is there a alternative?
Thanks
svn checkout http://svn.json-rpc.org/trunk/python-jsonrpc
the site has been down for a while. Is there a alternative?
Thanks
Sustained 90C operation will probably lead to premature death, however it doesn't sound like you've had the card for long enough to cause a problem like that. It sounds like a faulty card and should be RMA'd. The card has thermal protection built in, so you can't really overheat it to death unless it's a slow cooking death like 90C over time.
Video board HIS-6990 lasted only 3 days of mining...
Friends,
I got almost 2 Bitcoins mining with my brand new HD6990 and on the third day, GUP1 stopped... When loading Xorg with ATI drivers, the computer freezes... I changed my motherboard/CPU/RAM and nothing, hangs too...
The miner at GPU0 still works, but GPU1 gives the mere 0.1MHash and freezes the machine in seconds... I can only activate the environment using the VESA/Generic driver of Xorg... If I try to load the ATI drivers, it freezes immediatly.
The power source is ideal, 750W... Had not done overclocking, just a test to see if the commands worked, cooler at 100% all the time ... The temperature was at peaks of 92 degrees during the day and 88.00 º C at night... So I lowered the clock to less than 880 during the day time... Incidentally, the machine was installed in a small data center of a company, with air conditioning and everything else...
Abx!
Thiago
Friends,
I got almost 2 Bitcoins mining with my brand new HD6990 and on the third day, GUP1 stopped... When loading Xorg with ATI drivers, the computer freezes... I changed my motherboard/CPU/RAM and nothing, hangs too...
The miner at GPU0 still works, but GPU1 gives the mere 0.1MHash and freezes the machine in seconds... I can only activate the environment using the VESA/Generic driver of Xorg... If I try to load the ATI drivers, it freezes immediatly.
The power source is ideal, 750W... Had not done overclocking, just a test to see if the commands worked, cooler at 100% all the time ... The temperature was at peaks of 92 degrees during the day and 88.00 º C at night... So I lowered the clock to less than 880 during the day time... Incidentally, the machine was installed in a small data center of a company, with air conditioning and everything else...
Abx!
Thiago
In the linked method, what is really interesting to me is:
I've never seen the dir /dev/dri on any of my ubuntu or debian systems: do you have it?Quote
Code:
xhost +
chmod uog+rw /dev/dri/card*
chmod uog+rw /dev/dri/card*
I didn't really plunged onto it.
I only know that this recipe allowed me to open an xterm from text terminal and ./poclbm.py reported correctly the GPU in the same text terminal.
So, I must further investigate...
In the linked method, what is really interesting to me is:
I've never seen the dir /dev/dri on any of my ubuntu or debian systems: do you have it? Quote
Code:
xhost +
chmod uog+rw /dev/dri/card*
chmod uog+rw /dev/dri/card*
Really? Not in this thread? It's been discussed in several places in this thread and the guide even uses screen to accomplish the task of doing multiple things in the same terminal window. Using screen via SSH is the answer to the question asked.
The method used in that linked guide is like using a hammer to drive in a screw. It will probably work but it's not the best way to go about things.
The method used in that linked guide is like using a hammer to drive in a screw. It will probably work but it's not the best way to go about things.
It was a problem of permissions with X server. It seems, that Ubuntu default policy is opener than Debian's. I was not possible for me to stablish a connection to X server out of the main screen.
In the linked method, what is really interesting to me is:
Quote
Next edit /etc/gdm/Init/Default and add the following code just before the exit 0.
Code:
Code:
Code:
xhost +
chmod uog+rw /dev/dri/card*
chmod uog+rw /dev/dri/card*
Really? Not in this thread? It's been discussed in several places in this thread and the guide even uses screen to accomplish the task of doing multiple things in the same terminal window. Using screen via SSH is the answer to the question asked.
The method used in that linked guide is like using a hammer to drive in a screw. It will probably work but it's not the best way to go about things.
The method used in that linked guide is like using a hammer to drive in a screw. It will probably work but it's not the best way to go about things.
Read through this thread, all the clues are in here. I mean, the clue(s) are even in the guide itself. Come on, man.
I've finally found a clue, but not in this thread neither in these forums.
Read through this thread, all the clues are in here. I mean, the clue(s) are even in the guide itself. Come on, man.
I've finally found a clue, but not in this thread neither in these forums.
With the last command before reboot, I'm getting:
If I use Ubuntu's Additional Drivers utility, it will see the adapter but the platform needs to be specified and attempting to mine sends it into a frenzy of errors.
Any suggestions?
Code:
user@box:~$ sudo aticonfig --initial -f --adapter=allUnable to open /etc/ati/control, please reinstall the driver.
aticonfig: No supported adapters detected
aticonfig: No supported adapters detected
If I use Ubuntu's Additional Drivers utility, it will see the adapter but the platform needs to be specified and attempting to mine sends it into a frenzy of errors.
Any suggestions?
Instead of sudo apt-get install fglrx
try this:
Quote
cd ~
sudo aptitude install dkms
wget http://www2.ati.com/drivers/linux/ati-driver-installer-11-5-x86.x86_64.run
sudo sh ati-driver-installer-11-5-x86.x86_64.run --buildpkg Ubuntu/natty
sudo dpkg -i *.deb
sudo apt-get -f install
sudo aticonfig -f --initial --adapter=all
sudo reboot
sudo aptitude install dkms
wget http://www2.ati.com/drivers/linux/ati-driver-installer-11-5-x86.x86_64.run
sudo sh ati-driver-installer-11-5-x86.x86_64.run --buildpkg Ubuntu/natty
sudo dpkg -i *.deb
sudo apt-get -f install
sudo aticonfig -f --initial --adapter=all
sudo reboot
Code:
user@box:~$ sudo aticonfig -f --initial --adapter=all
sudo: aticonfig: command not found
user@box:~$ sudo ln -s /usr/lib/fglrx/bin/aticonfig /etc/alternatives/aticonfig
user@box:~$ sudo ln -s /etc/alternatives/aticonfig /usr/bin/aticonfig user@box:~$ sudo aticonfig -f --initial --adapter=allUnable to open /etc/ati/control, please reinstall the driver.
aticonfig: No supported adapters detected
user@box:~$
sudo: aticonfig: command not found
user@box:~$ sudo ln -s /usr/lib/fglrx/bin/aticonfig /etc/alternatives/aticonfig
user@box:~$ sudo ln -s /etc/alternatives/aticonfig /usr/bin/aticonfig user@box:~$ sudo aticonfig -f --initial --adapter=allUnable to open /etc/ati/control, please reinstall the driver.
aticonfig: No supported adapters detected
user@box:~$
With the last command before reboot, I'm getting:
If I use Ubuntu's Additional Drivers utility, it will see the adapter but the platform needs to be specified and attempting to mine sends it into a frenzy of errors.
Any suggestions?
Code:
user@box:~$ sudo aticonfig --initial -f --adapter=allUnable to open /etc/ati/control, please reinstall the driver.
aticonfig: No supported adapters detected
aticonfig: No supported adapters detected
If I use Ubuntu's Additional Drivers utility, it will see the adapter but the platform needs to be specified and attempting to mine sends it into a frenzy of errors.
Any suggestions?
Instead of sudo apt-get install fglrx
try this:
Quote
cd ~
sudo aptitude install dkms
wget http://www2.ati.com/drivers/linux/ati-driver-installer-11-5-x86.x86_64.run
sudo sh ati-driver-installer-11-5-x86.x86_64.run --buildpkg Ubuntu/natty
sudo dpkg -i *.deb
sudo apt-get -f install
sudo aticonfig -f --initial --adapter=all
sudo reboot
sudo aptitude install dkms
wget http://www2.ati.com/drivers/linux/ati-driver-installer-11-5-x86.x86_64.run
sudo sh ati-driver-installer-11-5-x86.x86_64.run --buildpkg Ubuntu/natty
sudo dpkg -i *.deb
sudo apt-get -f install
sudo aticonfig -f --initial --adapter=all
sudo reboot
With the last command before reboot, I'm getting:
If I use Ubuntu's Additional Drivers utility, it will see the adapter but the platform needs to be specified and attempting to mine sends it into a frenzy of errors.
Any suggestions?
Code:
user@box:~$ sudo aticonfig --initial -f --adapter=allUnable to open /etc/ati/control, please reinstall the driver.
aticonfig: No supported adapters detected
aticonfig: No supported adapters detected
If I use Ubuntu's Additional Drivers utility, it will see the adapter but the platform needs to be specified and attempting to mine sends it into a frenzy of errors.
Any suggestions?
Instead of sudo apt-get install fglrx
try this:
Quote
cd ~
sudo aptitude install dkms
wget http://www2.ati.com/drivers/linux/ati-driver-installer-11-5-x86.x86_64.run
sudo sh ati-driver-installer-11-5-x86.x86_64.run --buildpkg Ubuntu/natty
sudo dpkg -i *.deb
sudo apt-get -f install
sudo aticonfig -f --initial --adapter=all
sudo reboot
sudo aptitude install dkms
wget http://www2.ati.com/drivers/linux/ati-driver-installer-11-5-x86.x86_64.run
sudo sh ati-driver-installer-11-5-x86.x86_64.run --buildpkg Ubuntu/natty
sudo dpkg -i *.deb
sudo apt-get -f install
sudo aticonfig -f --initial --adapter=all
sudo reboot
With the last command before reboot, I'm getting:
If I use Ubuntu's Additional Drivers utility, it will see the adapter but the platform needs to be specified and attempting to mine sends it into a frenzy of errors.
Any suggestions?
Code:
user@box:~$ sudo aticonfig --initial -f --adapter=allUnable to open /etc/ati/control, please reinstall the driver.
aticonfig: No supported adapters detected
aticonfig: No supported adapters detected
If I use Ubuntu's Additional Drivers utility, it will see the adapter but the platform needs to be specified and attempting to mine sends it into a frenzy of errors.
Any suggestions?
this will then replace line 15 of guide correct?
thank you very much for your help
Jenette
Command 3 is equal to Line 27 from the guide
Command 4 is equal to Line 28 from the guide
So you do Commands 1 and 2 instead of line 15, then follow the guide to the end.
Jump to: