I've been appreciating the updates from others waiting for withdrawals in this thread, and I am delighted to finally be able to return the favour  . I received a >3000 EUR SEPA withdrawal today (2013-11-26) which was requested 2013-10-17.

Det var i allfall kjekt å høre at man antageligvis sitter trygt så lenge det er salg til utenlandsk børs det handler om. Men det er jo veldig tullete hvis det sementeres at man skal betale mva. på kjøp, så man får vel bare håpe at de kommer på bedre tanker.

Gevinstbeskatning på 28 % høres jo greit nok ut, men hva betyr det egentlig at man skal betale mva? Dvs., i hvilke situasjoner skal man i såfall betale dette? Når man har gravd frem bitcoins og selger de på f.eks. bitstamp, skal man da betale både 28 % gevinstskatt + 25 % mva?

I've been waiting since 2013-09-18 (so well over 3 weeks) for a < 1000 EUR SEPA withdrawal, so there is at least some trouble there as well.

I don't know of that error. Only thing I can think of is to try and back up your ~/.yacoin/wallet.dat and then delete the entire ~/.yacoin directory, as it seems to be having trouble with one of the files in there.

Something like:
yacoind -gen -genproclimit=-1 -daemon
Where -daemon makes it run as a daemon (duh!). You can then call "yacoind getmininginfo" and so on to check on the status :-)

rUQ52ik4mxhMs3wf36JX5HaZDYjxSRGMKK

Yeah I noticed that as well. Perhaps the two are related.

Hopefully these issues will be fixed in SDK 2.4, which shouldn't be too far out if they keep the same release pace. I know these issues (multi-gpu on linux and high CPU use) have been brought up at the AMD forums, so let's hope they got it fixed and we don't have to wait for SDK 2.5.

Wouldn't you know it, it works fine with SDK 2.1

On OpenSUSE I tried all the SDK's (2.1, 2.2 and 2.3), but that was with catalyst 11.2. On Debian with catalyst 10.9 it works with SDK 2.1.

Still a bit of a pain to have to use an old SKD/driver set (I do some OpenCL developement myself so it matters a bit to me), but at least it's working

It's the same if I mine solo.

Still the same

Man, every time I've tried switching to Linux there's something only Windows does. This time it's just multi-gpu, but that's a deal breaker considering I have two GPUs 

Thanks to everyone for trying to help. If I do figure out what's wrong I'll be sure post an update.

Oh yes, I have dual boot with Windows 7 x64 and Debian Testing x64. And the PSU is definitely beefy enough (1000 W).

Tried it. Moved the old xorg.conf and did aticonfig --initial --adapter=all again and the new file was identical to the old one.

Thanks for trying to help though . Hopefully someone else who has experienced similar problems at some point will see the thread. I find it very odd considering I've had the exact same problem with openSUSE and Debian, but others seem to get multiple GPUs to work with no hassle.

Thanks, using aticonfig --odgc --adapter=all gives me the loads.

I've checked the DISPLAY variable using echo $DISPLAY. I've also tried setting the COMPUTE variable (which is preferred over DISPLAY by the SDK) to :0 but it's still the same.

Basically if I start two instances of poclbm the one I start first (say on the first card) will do about 250000 khash/s and the second one will do 50000 khash/s (it varies but those seem to be roughly the averages). The load using aticonfig reflects this (i.e. one GPU is like 80% and the other jumps around a bit but is much lower). If I then stop the first instance the load shifts to the second GPU, also reflected in aticonfig.

So it seems I am definitely starting the program correctly (i.e. each instance is using it's own GPU), but it's like the work gets serialized somewhere and is limited to the performance of one card.

Is there a way to do that in linux? My searches are coming up empty.

Tried to close all other applications and remove the extra parameters, so I'm running:
But it's still the same. Both cards perform as expected on their own but when run at the same time performance does not exceed that of a single card.

Lower than 120 (i.e. 60 and lower) makes it interfere with stuff, like HD video playback, games (on Windows with -f 120 I can mine even when gaming at about half speed) and more if it's really low. Considering the performance difference is less than 10% I keep -f high to not impact usability.

Hi. I have two HD 5870 cards, and both seem to be set up and working correctly.

I am using poclbm (latest version by doing "git clone git://github.com/m0mchil/poclbm poclbm" today).
I am using Catalyst 10.9 from debian repositories.
I am using SDK 2.2.

I have configured the cards by doing:

And I've added "export DISPLAY=:0" do my .bashrc.

running just ./poclbm lists the devices:

Each devices seems to be working fine. Running poclbm like this:
for both -d 1 and -d 2 gives about 300000 khash/s as expected. However if I start both at the same time I only get a total of about 300000 khash/s. I.e. if one of the cards is doing 250000 khash/s the other one will be doing 50000 khash/s.

I am absolutely sure that I am using a different device. I.e. in one terminal I've entered:

And in the other one:

So both the devices and user names on slush's server are different.

It's working fine on windows using the poclbm GUI, so this does seem to be a Linux configuration problem. Anyone have any ideas on how to fix it?

By the way, I've also tried the same in OpenSUSE with catalyst 11.2 and SDK 2.1, 2.2 and 2.3 with the same result. Presumably there is simply some configuration I've missed.

Watts per hour also does not make sense. As others have noted watts are a measure of energy per time already, so "watts per <insert time unit here>" would be some funky kind of energy acceleration measure that nobody uses .

It really is as simple as:
100 W = 0.1 kW

If we use 0.1 kW for 5 hours we would get:
0.1 kW * 5 h = 0.5 kWh

Don't feel bad though, I've even seen electricians getting confused by this

I had no idea Intel had released (beta) drivers with OpenCL support, and I even try to keep myself informed since I use OpenCL myself. Apparently Intel didn't release said drivers with much fanfare, I can't even find any information about it when searching.

Sorry for the misinformation though. Guess it is possible, but unlikely to be very effective.

No Intel graphics cards to date have supported OpenCL, so I don't think that will be possible.