Topic: Ubuntu Natty Narwhal 11.04 Mining Guide / HOWTO - page 22. (Read 281450 times)

does the stream sdk 2.1 support 6950 card?

Yeah this guide isn't intended for the Live versions of Ubuntu, only for dedicated installs.  Some people have apparently gotten it working, but it's just such a hassle and hard drives are dirt cheap and you are somewhat limited with a live install...

I plan on figuring out how to do this from a USB stick, after that I will probably look into adjusting for a Live install, but both come after I finish my current project which will hopefully be announced RSN.

Hi sorry TStarter. never got back to you. My working comp just frozed up bad again today. And I've been discussing the idea to a potential investor although this might head no where. I'm intending to expand to a small farm. Thus I'll need to script all these and learn as fast as I can how to remotely administer them. I'll try your guide again with a fresh install of Ubuntu.

After reading the whole thread again so I don't waste your time on any issues that's already been answered. I realize there is a fundamental difference as I'm running on LiveCD. However, I was able to get the miners to start in one of my installation though, so I'm sure it works too (w/ persistence), like I mention. I'll run the installation through with a fresh installation of LiveCD w/ persistence and let you know.

On step 11, there's a vestigial [/color] tag:
you may wish to fix.

thanks for this ! it worked for me using the info in this topic

Not in step 22. You really should start using the search/replace function when you're fixing these kind of mistakes.

You have to login to your router and forward port 22 to the internal ip address of your mining box.  It's not hard but it's not really something that's easy to explain since every router is different.

Hmm I'll be glad to but I'm busy right now and can't attend to this yet. And what is (to the box port 22) forward what to where?

Well, you set it up as optional step one in this guide.  However, if you're behind a firewall, you'd have to forward the port on your router to the box (port 22) and give me the ip address and the login/password information.

Err.. so what do you observe? Is it by any chance, the redish background displays for a short while, and then just a dark screen? If that happens, try hitting escape before the boot to bring up the grub menu, choose low graphics option and see if you can boot that way.

Actually. I might but what's SSH and how do I set it up hmm?

Does someone with a "broken" 32 bit system want to give me SSH access and let me look at what's going on specifically?

Is what I did. I realized somehow I downloaded the x64 instead. And then I was trying to get the x86 installed. However, I looked around /opt/ati-stream-sdkv2.1-lnx64/ and realized there is an x86 folder too hmm...?

By the way. after I got everything right then reboot, Ubuntu died. Doesn't boot properly anymore. So I'll say it doesn't work? I don't know.

Can anyone help me with this?


I did all the steps but i still get this error.

Yeah, if onboard graphics is nvidia don't do it .... mostly it is for system stability if you are Ocling the mining GPUs a lot ... you can lose many MHash when system freezing all the time.

Makes sense, thanks. Weighing whether I want to expend the effort (and accept the risk) just to pick up a few MHash/sec.

Schizo-

That message:

is telling you the compiler can't find the openCL header file "cl.h". That can be either because it's not there, or it's looking in the wrong place. To verify it's actually there, look at the files in:
/opt/ati-stream-sdk-v2.1-lnx32/include/CL/
(assuming you running 32-bit). You should see a file "cl.h" in that directory.

It should have been put there when you did:
which is "unzipping" the contents of the tgz file and dumping them in /opt.

The other possibility is that this step was missed or messed up:
which is what tells pyopencl where to look for the header. You can re-run that step, but it will tell you that you have already configured, and if you want to re-configure, to delete a certain file. I forget what it's called. Just delete it, and re-run the configure step.

If this is a dedicated mining rig, here's a tip: if you do have integrated mobo  AMD graphics, you can use that to drive the monitor (assuming you aren't in headless mode) i.e. make the integrated graphics the default adapter for xorg and then the GPU's will work better for dedicated mining ... the GPU that would have been attached to the monitor screen would have been getting fairly frequent xorg calls and interruptions.

I can verify the instructions work for 2.4/69xx cards too. I have a 6850 and a 6970 that are running phoenix now on 64-bit Ubuntu. I just needed to substitute 2.4 APP SDK here:

http://developer.amd.com/sdks/AMDAPPSDK/downloads/Pages/default.aspx#one

for the 2.1 Stream SDK that's in the instructions. And use the icd-registration.tgz that comes with it instead of the one in the instructions. Of course that ripples through to the /opt paths so that they are /opt/AMD-APP-SDK-v2.4-lnx?? instead of /opt/ATI-STREAM-SDK-v2.1-lnx??.

I had a few quirks, like the wget failed for me; stopped downloading before it had the whole file (stopped after only a few KB, instead of all 70-some MB) so I just downloaded from the APP SDK page in firefox and copied it.

One minor thing: When it says:


I think it means

Which works for me.

And in case other newbies are setting up machines: I had a trouble getting Ubuntu installed. Installer would fail. I finally stumbled on disabling the integrated video on the motherboard, and putting in one of the ATI cards. Then it installed, but graphics were hosed on booting to where you couldn't log in. So hitting escape before boot brings up the grub menu where you can select a low-graphics boot. Then once logged in, I saw the package for proprietary ATI drivers on the software manager. Installed those and then it was fine, and I proceeded as described above.

Been almost a decade since I used a bash shell in linux, but it's coming back.

I think it works now but boot fail after reboot -.- this might have nothing to do with this. I'm reinstalling a fresh

Anyway, how do I run it as a script? Like save as what file and how do I run it? just double click? hmm..?