No; without the flags I've never seen anything except the "starting" line except for the time that bitcoind wasn't running on my Mac.


I have libncurses5-dev 5.7+20080803-2ubuntu3 and my configure output looks exactly the same.


Each of six threads was using 16-17%, i.e., about 100% total.

The output is the same without -T.  It's the -D that was producing output.


One core (Sempron 145).  Maybe sometime I'll attempt to unlock the other, but it hasn't seemed important as I wasn't anticipating CPU intensity.


It's been my intention to use a pool; this solo experiment was just for intitial test and familiarization.  I'd be shocked if adding a pool cures what seems to be a problem of the software hanging after a couple of seconds.  But I'll add the pool just to be sure.  And then, if I'm not shocked, I'll start researching the minimum-loss way to upgrade Ubuntu.

This is my first Unix/Linux and the idea of LTS and the implied stability was appealing.

However, you happened to ask during the process of my upgrading from 10.04 to 10.10, on the way to 11.04 and then 11.10.  Or is there a cgminer-related reason to stop at 11.04?

Soooooooooooooooooo Nobody has created a GUI for this amazing miner? Why?

I'm new in town but I've been around software for a while and I have a multi-part guess:

--Con is not a GUI kind of guy and might not be inclined to offer much support to someone who volunteers to write a GUI, or to the finished result.  (N.B. I have no knowledge of Mr. Kolivas beyond what I've read in his READMEs, forum posts, etc.)

--No one thus far has combined the interest, time, and other resources to do it.

--Miners tend to be nerds/techies who don't present a robust demand for a GUI.

No reason to stop at 11.04 - but certainly a reason to start there since all work was done with that, and now with 11.10
I'm pretty sure 11.10 is what ckolivas now uses.
Why not just install 11.04 or 11.10?

To expand on that: if you'd used a .deb to install fglrx, the re-install might have happened automatically.

Anyhow, you might edit the Driver "fglrx" line inetc/X11/xorg.conf to read Driver "vesa" until the upgrade is finished.
You could even try, when you get the messed-up screen, to press ctrl-alt-F2 and log in at the console level to continue the upgrade there.

Well, he mentioned he didn't want to do that to be able to carry over changes in settings...

Yes and no; mostly no, though...
It contains a closed-source binary part and an adapter layer that needs to get compiled at each kernel change. As a result, you need to re-install the driver with each kernel update (partly because for new kernel versions, the old driver is in the wrong path, partly because the kernel ABI changes frequently and it's more or less impossible for ATI to ship the driver for every kernel version in every distro out there).

Have you come across the BinaryDriverHowto ATI page in the wiki? Specifically the part around (https://help.ubuntu.com/community/BinaryDriverHowto/ATI#Manually_installing_Catalyst_11.2):

I haven't used Ubuntu in a few months and thus have no idea whether this still works; at least part of the howto is seriously outdated, but perhaps that part still works. If it does, you may want to use it to build the fglrx debs so you won't have to manually reinstall fglrx all the time. If anything has changed, you may want to research how to build the debs in more recent versions of Ubuntu.

Whoops, I'm stuck.  I got 11.04 up in low-graphics mode and followed the AMD-recommended procedure for uninstalling its driver/utilities.  Then I restarted, and after the Ubunto-logo-with-sequenced-dots-underneath screen I got a terminal-screen that displayed a bunch of messages that are apparently results of various checks, and none seem alarming.  The last one is Checking Battery; tt seemed hung there.  If I hit Ctrl-Alt-F2 I can get a console login, but I don't know what to do after I log in.