Topic: BAMT version 0.5 - Easy USB based mining Linux with farm wide management tools - page 20. (Read 324185 times)

underclocking/undervolting will cause instability issues just as much as overclocking.  screwing with your GPU == potential instability.

Given the frequent and varied nature of the problems my rigs have been having, I'd be happy to accept 'overclocking' as the issue, but I sure hope it's not that, because for the vast majority of the time I have been UNDERclocking and UNDERvolting my cards. At one point I even had them running 600 engine, 200 memory, and full 1.05V, and they still kept screwing up. And GPU temps have generally been kept below 75C, only occasionally creeped to 82.

Now I'm running them at 800/300/1.05, and they're not locking up any *more* than they were on much lower speeds. It's incredibly frustrating.

However, I shall trying reflashing the USB stick (which is also something I've done two or three times for each rig already!). It's actually just one rig that's being a pain the last few days so maybe that'll do it, the other two seem to be behaving better.

My latest problem with BAMT - a rig doesn't mine, I can't putty in, and when I bring up a local terminal and try atitweak -s, it tells me about an 'invalid MIT-MAGIC-COOKIE'.

Having waded through pages of forum posts, a temporary fix seems to be to delete ~user/.Xauthority and ~root/.Xauthority and then reboot. But I have to keep going in manually to do this, and it only works til the next hangup maybe half a day later.

Could somebody check my understanding of this? I *think* that it basically only happens when I have to power off the system at the switch... then the problem appears when I boot it up again. But it doesn't ALWAYS seem to happen. And it doesn't happen if the system was mining successfully and I power it down the way it should be done, with a shutdown or coldreboot command.

I read the following from lodcrappo responding to another guy whose problem also seemed to lie with Xauthority somehow:


Okay I think I understand all that. And I suppose what might be happening is that 'step 7 happens before step 5'. BUT, a quick perusal of the start_mining script suggests that this *cannot* happen, as mine_start won't run 'xauth +' until it sees the X server is running.

Also, why the difference in behaviour between the two different ways of rebooting?

Basically how I do stop this shit happening all the time? Or at least shove some extra perl in to detect it and do something clever?

Okay, I responded to your post, but my response was not directed at you personally.  I apologize if you took it as such.

I am not a "Linux smug", I do not like the command line interface, I do like GUIs.

I accuse people of being lazy not because they don't know linux, but because they don't spend 30 seconds to do this...

http://lmgtfy.com/?q=linux+install+amd+app+sdk

...before coming on the forums to ask the same question that has been asked, an answered, at least 20 times before.

There is no issue between Con and I.  This change has nothing to do with the "miner killing super bug incident" and was planned far prior to that.

You've done nothing to piss me off.  I've always found you reasonable and have great respect for your work.

Because you were responding to me.
Listen, is the second time you called people lazy in this thread because of their lacking Linux skills. You act like a Linux smug looking down at Windows people.

Some people know Linux, some know Windows, 'deal with it'.

Soooooo.... Obviously, if you have already done it, months ago at that, you are not one of the people who are to lazy to do it.
Soooooo.... Obviously that statement doesn't apply to you.
Soooooo.... Obviously I didn't call you lazy.

Soooooo.... Why did you post again?

BTW, nice selective quotes.
So obviously I was showing an easy way to swap out BFG for CG if needed in the first statement, and the second statement is totally unrelated.

What makes you think that I am lazy and not able to do updates in Linux? I have already my BAMT running 7970 cards with newer cgminer since months ago thank you very much, I even shared it here.
Who are you to call me lazy?

cgminer does support BFL, Icarus, CM1 (ztex is in there and an older MMQ also)
In fact the optimisations in BFL and Icarus to make them perform best were done by Con and I ... that other miner gets less with BFL on any pool that doesn't accept stales (most pools)
and the code to work properly with CM1 (Icarus timing and options) was all by me ... and then copied unchanged into that other thing
... anyway.

You should put both cgminer and bfgminer in there so bfgminer is only used in cases where fpga mining is needed, i'd rather not use bfgminer if I had the choice for the simple fact that the person who created it is a total ass and is trying to add 1 part to someone else's car and call it his own.

Thanks for the clarification lodcrappo! I look forward to downloading the 5xxx version of BAMT 0.6 when it becomes available.

I'd planned to hold off donating until these rigs had started turning a profit... unfortunately that's unlikely to ever happen now, more of a loss-minimising thing going on until those damn ASICs start flooding the network. So have 3 BTC, courtesy of 1Fhowu3xdhe8w6CaozK81TwUpyVe2Swnov.

You probably didn't do anything, it's just Luke is a better bullshit artist than you Con.   

Doesn't matter though, the two of you (Con, Lod) make the two best pieces of software out there, period.  Everyone in the community is best served if you two play nice, not bitch at each other.

BOTH pieces of software have bugs, and always will.  Deal with it.  Unfortunately, right now, the bugs in certain cases merge together and cause a miner killing super bug.  Deal with it.  It's not either of your fault, it wasn't intentional, it just happened.  Deal with it.

Now, you two kiss and make up and get back to cranking out your respective pieces of software that you kill your self working on, for no pay, and no "Thank You"s from the asshats who use it which can't even be bother to read the ReadMe before coming onto the forum and saying your software is broken.

And balance was restored to the universe....

I can't recall what I did to piss you off, but enjoy your relationship.

I'm not removing support for cgminer, I'm just not taking responsibility for providing a working version anymore.  You'll always be able to use cgminer with bamt (unless they change so much that the existing code doesn't work anymore).

Compile your preferred version of CGminer, swap it into BFGminers location, rename CG to BFG, live like a king...


Oh, and send lodcrappo some BTC for making this work for all you people to lazy to learn enough about Linux to do simple updates.   

The two great features I was waiting for! 

This is not silliness, this is PR.


Sounds great, seems you got it all covered  

...maybe with the exception of choosing BFGminer...meh... but hey, it's your baby.