Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 731. (Read 5805728 times)

Looks like everyone is overseeing this:
OpenGL renderer string: NVIDIA GeForce GT 330M OpenGL Engine

Proofer, is that the card you want to mine on? Its not like aticonfig will help with that card. You will need the nvidia restricted drivers for a start.

If thats the IGP and you also have AMD gpu's in the that machine, then you may have a problem. Ive not gotten a mix of nv and amd cards to work on ubuntu yet with restricted drivers. See if you can disable the nvidia igp in the bios, then try reinstalling the amd drivers.

If you don't log in, the X server is owned by root.

@Proofer: You can try "DISPLAY=:0 sudo xhost +", but don't be surprised if the behaviour goes right back to whatever it is when you log in graphically.

When I log into headless Ubuntu rigs from my Mac, I need to run the following to get cgminer to work:

I don't know why, I just know it works.  Something about access control???

The aticonfig -f --initial ... was done.

When logged in at the Ubuntu machine and using its monitor/keyboard, fglrxinfo lists six cards, aticonfig will show me the six 5970 cores' temperatures, cgminer -n will report 6; and clinfo will report on six GPUs and a CPU; for none do I need DISPLAY=:0 (it's already 0).

When logged in at the Ubunto machine and logged in via ssh from my Mac, all the preceding work OK if I prefix the commands with DISPLAY=:0.

When NOT logged in at the Ubunto machine and logged in via ssh from my Mac:

BTW I usually don't login thru graphical mode either. I find it does affect how the system behaves and my intention was always to use ssh to come in "the backdoor" from my notebook and do admin work. But when using ssh you have to be more fussy about DISPLAY=0: to make sure commands work. Best to add to .bashrc so it gets added to environment. Also, I have found the atitweak tool (discussed in another thread here) behaves better from ssh but is rarely needed when using cgminer since better control is available on screen now.

The Ubuntu 11.10 (Gnome?) login screen with a bar across the top containing the system name, the time, a short control ("gear") menu; a form for entering password, places to click for Other or Guest, and an Ubuntu 11.10 "logo" at the bottom left.  In other words, the first screen after boot that takes user interaction.

~$ cgminer -n
[2011-12-20 15:56:35] Error: Getting Device IDs (num)
[2011-12-20 15:56:35] clDevicesNum returned error, none usable
0 GPU devices detected

See also my next post.

Make sure you don't skip these commands any time you change GPU slots/combinations:

sudo aticonfig -f --initial --adapter=all
sudo reboot

Make sure cards are recognized correctly and listed with,

DISPLAY=:0 sudo fglrxinfo

Also see what you get listed from the SDK utility "clinfo". It should list any cards and CPU. If not then some initialization hasn't occurred.

Wait what?  What login screen?

Also just curious what happens if you try "cgminer -n"?

WOOHOO!  cgminer is running!  The solution?  Don't log in on the miner -- leave it at the login screen.  For now, for me, this is a head-scratcher rather than a forehead-slapper.

However, not out of the woods completely:

[2011-12-20 15:09:22] ADL Initialisation Error!
[2011-12-20 15:09:22] 0 gpu miner threads started
[2011-12-20 15:09:22] 1 cpu miner threads started, using SHA256 'sse2_64' algorithm.

Edit:  Maybe it's running only because it couldn't access the GPUs 

I'm running Ubuntu 11.04 (32 bit) Desktop with ADK 2.4 and drivers 11.6 and cgminer. No problems at all. I'd suggest starting from fresh and following closely the Ubuntu headless tutorial here,

https://bitcointalksearch.org/topic/ubuntu-1104-natty-64bit-headless-bitcoin-mining-with-ati-115-binary-driver-9239

(in my case I used 32 bit versions where suitable, and I ran Phoenix for a while before trying and prefering cgminer) This combo works great for me and I wouldn't suggest bothering with newer driver versions as there are generally cpu problems and no advantages afaik.

According to the pool server, my last activity was 15,328 days ago, i.e., at the beginning of time (in the Unix universe).  Cgminer reported getting some work from it, but that might not count as "activity."

I fell back to fglrx 8.881, the version w/o post-release update, that 11.10 installs from its repositories.  The only difference is that now running cgminer locks up the system so tight that I can't get in via ssh; with the Catalyst 11.12 driver, I was getting in via ssh.

Very weird behavior, indeed.  Two other anomalies that seem unrelated but which I'll mention in case any bells ring:  with fglrx installed, (1) Gnome Classic comes up with only the desktop, no top panel and hence no way to do anything with the GUI; (2) there's no way (that I've found) to dismiss the screen blanker in Unity other than Ctrl-Alt-F2 to get a shell login prompt followed by Ctrl-Alt-F7 to return to the GUI.  Without fglrx, these two anomalies are not present.  But without fglrx, cgminer exits immediately  

Other than the cgminer problem and those two 11.10 anomalies the system seems normal to me, although I'm a newbie w/r Linux.  For completeness, I mention that this is a homebrew system which first had power applied about a week ago.

I'll bet that if a solution is found, it's going to be of the forehead-slapping, "you did [or didn't do] WHAT!?" variety.

Anyone tried this?


The direct source of the patch, in English:
http://www.mindwerks.net/2011/04/ubuntu-11-04-natty-with-fglrx-and-2-6-39/

I mean check for shares on pool server.  I was wondering if it was just some display glitch but if you are getting system lock outside of cgminer it is far beyond that.  I have never have cgminer lockup a linux system like that.  Very weird behavior. 

(Emphasis added)

What Con Kolivas patches?

Is 11.6 compatible with Linux kernel 3 (Ubuntu 11.10)?  I thought I'd seen somewhere that it's not.


Don't! Using gdb to debug cgminer while it's executing OpenCL code on the card connected to your display *will* lead to a complete X server freeze. (If you're still using VNC to access an X server not using the fglrx driver, you might be fine.)