Bitcoin Forum

AM3
8GB RAM
1200W PSU
5 X 7950's



I have been trying to get BAMT to work.  I can get it to boot into BAMT if I only use one GPU.  But when it boots it has a big red bar at the bottom and it says that "Mining has been disabled because there are noe GPUs."  Or something like that.



I think I need to install the AMD drivers.  I have downloaded the Linux drivers but since BAMT is so bare I cannot figure out how to install them.




Can anyone help me out here?




Thanks

I am assuming you have something like a 7XXX card and thats why BAMT isnt seeing the cards.  Follow these instructions to update CGMiner (if thats what you chose to use in BAMT) and update the AMD drivers.

https://bitcointalk.org/index.php?topic=127622.0

There are guides around here about this.
There is also a modified version of BAMT with drivers already installed for 7xxx cards.

Could you point me to it?  I have read 3 guides and have only saw how to install older drivers.

The drivers installed on that guide should be the only ones you need, it will get BAMT to see them, and any performance increases will come from tweaking, not necessarily because of updated drivers or SDK, but if you want the updated 2.8 SDK then I am sure there is a work around.  Go to that post and ask Mobius.

Older drivers are what you need. New ones suck.
http://www.bitcointrading.com/forum/linux-distros/bamt-version-0-5-easy-usb-based-mining-linux-with-farm-wide-management-tools/#post_phillipsgcnbamt

Also a newer (2.11.4) cgminer for the above BAMT: cgminer.zip (http://www.uploadmb.com/dw.php?id=1366626591)

EDIT: Yeah, unsupported, do it on your own risk and all that jazz.

Im probably wrong but at the top of https://bitcointalk.org/index.php?topic=127622.0 you posted it says Will not work with 7xxx cards.

That is irrelevant to what I said. I didn't posted that link.
What you have there is a tutorial (and a good one) on how to upgrade cgminer on an official BAMT.
(The one that doesn't work with 7xxx cards)

I have pointed you to a modified BAMT that works with 7xxx cards and also already gave you a working cgminer for that BAMT.

You have to decide what solution to use:
1 Download a fresh official BAMT and upgrade its drivers/SDK and cgminer using various tutorials or,

2 Download the one with the drivers/SDK already updated and use the also updated cgminer I gave you.

Sorry I dont know where I got that link from.


So BAMT .6 beta is the BAMT that already has the drivers installed?

So if I understand right I could use the .6 beta then just update cgminer?

So sorry for all this and I REALLY appreciate the help.  Sorry for being a newb.



Sorry sorry I see the the link you gave me with the modified BAMT.  Sorry I will post back.

No, not talking about 0.6 beta, I haven't tried that beta version yet (shame on me though).
We waited for a long time for a final release of BAMT 0.6  but sadly it never materialized (past that beta stage).

I am talking about the same old 0.5 BAMT but with AMD drivers updated.
Read again the exact post I linked before (BAMT 0.6 is metioned in a post below).

There are two links there, one direct and one using bitorrent.

EDIT: Oh, OK :)

Ok so I have downloaded your BAMT with the drivers already installed.


When I boot into it I get a red screen that says "A fault has been detected on GPU 0".


I only have 1 GPU hooked up right now.



I am going to update CGMiner too but was wondering what this fault is about first.



Thanks again.

Ran the fixer and then hit restart mining and it is gone now.



So I am going to update the cgminer now.

Spoke too soon.



About 2 mins later the red screen came back with the same message.

For updating cgminer go to /opt/miners where you gonna find a folder named cgminer. Delete that folder and replace it with the new cgminer folder (from the downloaded zip).

Dont forget to apply all the fixes (including fix 21) and of course edit bamt conf with your settings.
For all the rest consult the BAMT main thread.

I have ran BAMT update and applied about 5 updates.

It now says BAMT is up to date.


But my screen is still red and says a fault has been detected on GPU 0.




Sorry to keep bugging you.

I REALLY REALLY appreciate the help.

There are 21 fixes to apply.

Have you configured bamt.conf with your settings for cgminer, pools etc? (you need to use cgminer for this version)
Everything that applies for the official BAMT applies also here.

With the exception of new drivers is the same BAMT and most likely whatever question you have they are already answered in the BAMT thread.

Ok I will jump over to that thread.


When I was doing the fixes I did I just ran the fixer and then hit f to check for updates then F to apply the updates.

Then it says BAMT is up to date.


I will check the other thread.


Thanks

I plugged another GPU in and it says both have a fault.

I guess I did install 21 updates.


If I go to /opt/bamt/fix.history it has a list like this.


bamt5_fix_3.tar,1330825106,install


And it goes from 0 to 21 minus #20.  I have read about #20 being messed up so I guess thats why it is not included.



So I guess my problem is not the updates? 

The fixes are fine then.
Have you configured BAMT to use cgminer in bamt.conf with all the necessary settings as described in BAMT thread?

The BAMT thread you are talking about is https://bitcointalk.org/index.php?topic=65915.0 (https://bitcointalk.org/index.php?topic=65915.0)?

For some reason the GPU fault and red screen were gone when I rebooted.  Everything looked normal but it was not mining.  Then after a few mins it goes back to the red GPU fault screen.  And when I reboot it it says no GPUs are configured.


I set my pool in the pool config.


I have 2 GPUs in right now.  I set the BAMT config the way it should be pretty sure.

When I click restart mining sessions it says.

cgminer api failed



So All I had to do was copy the cgminer folder over and delete the older one to update cgminer?  I dont have to do anything else?


I have not found a guide here to setting the config files.  But they are pretty self explanatory when you read the directions in the configs.


I must be doing something wrong.


Besides setting the config files is there anything else I have to do?


Thanks

I ran cgminer just like I would from the command line in Windows and it works.  It will mine BTC and LTC.  Only getting 300-350 KH/s but I havent messed with tuning it yet.


I still have the red background saying the GPU has a fault.

Yes, that is the thread.

Set the pool in the cgminer line, not in the pool config.

Yes, all you need to do is copy the new cgminer folder in the same place where the old one was.
At the first run make sure you give cgminer plenty of time to compile its kernel for your cards. It may take a while.

Do you have the red screen when mining LTC, or BTC?
While the red screen is on open a terminal and enter the command:
Is cgminer working?


If, as you say, cgminer is working from the command line but not when managed by BAMT then something is not configured right in your bamt.conf.

When I run that screen -r cgminer it says "There is no screen to be resumed matching cgminer."

I ran it from root terminal while at root@bamt-miner:/home/user#


Thanks for the help.  I will def throw you some LTC for all the help.

Then my guess is that something is not configured right in bamt.conf.
Probably BAMT tries to start cgminer and something in config prevents it...missing pools?

No need to send anything to me, if you want to donate, donate to loddcrapo (BAMT creator).

Here is my bamt.config file



# Big A Miner Thing configuration

# full example of options available in /etc/bamt/bamt.conf



---

settings:

 
 
# miner info used in alerts, etc

 

# id is used to set hostname and identify this rig in farm wide displays
  miner_id: bamt-miner
 
# loc is any addition string you wish to use to identify this rig (location?)
 
miner_loc: unspecified location

 

# sending status to mgpumon..

 

# send directly to IP address (only needed if mgpumon is on different network)
 
# do_direct_status: 192.168.1.1

 

# and/or broadcast on local IP network  1 = yes, 0 = no
 
# recommend to leave enabled, harmless and very handy
 
do_bcast_status: 1

 

# central config managment? 1 = yes, 0 = no  (sensing a pattern here?)
 
do_manage_config: 0

 

# command to run for config updates, this is just one example..
 
# note this is old school, pre autoconf but still a fine way to do things if you prefer it
 
# config_update_cmd: /usr/bin/rsync -aL rsync://192.168.1.1:873/config/miner1/* /etc/bamt/


 


# how long to wait for X to start (seconds) - increase if mining fails to start at boot
 
# slower machines or booting from slow USB key may need as long as 60 seconds here
 
start_mining_init_delay: 20

 

# delay in between starting individual GPUs (seconds) - increase if gpus lock during mining init
 
start_mining_miner_delay: 3

 

# api keys for gpumon, all optional

 

# apikey_btcguild:
 
# apikey_deepbit:
 
# apikey_bitclockers:
 
# apikey_slush:
 
# apikey_bithasher:
 
# apikey_mtred:
 
# apikey_ozcoin:
 
# apikey_nofee:
 
# apikey_rfc:
 
# apikey_polmine:
 
# apikey_btcpool:
 
# apikey_triple:
 
# apikey_abc:


 

# monitoring config..
 
# should we monitor the cards? (send email alerts, etc)  1 = yes, 0 = no
 
do_monitor: 0

 

# smtp settings for sending alerts
 
 

# required..
 
# smtp_host: 127.0.0.1
 
# smtp_to: you@youremail.com
 
 

# optional..
 
# smtp_port: 587
 
# smtp_from: miner@mydomain.com
 
 

# set these to 1 to enable
 
# smtp_tls: 1
 
# smtp_ssl: 1
 
 

# authentication for sasl or tls
 
# smtp_auth_user: youruser
 
# smtp_auth_pass: yourpass
 
 

# don't send emails more often than smtp_min_wait seconds, default 300
 
# smtp_min_wait: 300
 
# include current system status details in alerts? (defaults on, disable for smaller emails)
 
# smtp_include_details: 1
 
# if you don't like the automatic subjects..
 
# smtp_subject: I wanted a custom subject in my alerts...
 
 
 


# start autoconf client - no harm in running client even if not using autoconf server on network
 
do_autoconf_client: 1
 
 

# start mgpumon in background using /etc/bamt/mgpumon.conf?
 
do_mgpumon: 0

 
 


# detect hung GPUs and auto reboot (phoenix only)
 
detect_defunct: 1


 


# use cgsnoop?
 
do_cgsnoop: 0

 
 
 

# cgminer options
 
 

# start cgminer?  set this to 1, and also set cgminer: 1 on each GPU you will manage with cgminer
 
cgminer: 1
 
 

# options to cgminer (must have at least --api-listen for any bamt tools to work)
 
# see cgminer documentation for options.  you may want to put cgminer config in
 
# another file and simply put --config /that/file here.
 
cgminer_opts: -o http://mine.pool-x.eu:8080 -u Helper556.1 -p x --intensity 16 --api-listen --gpu-powertune 5 --gpu-engine 1150 --gpu-

memclock 1000 --auto-fan --temp-target 70
 
 

# tcp port for cgminer.. defaults to 4028
 
# cgminer_port: 4028
   
 
 
 
 



# GPU Configuration

# You'll need one gpuX: section per GPU installed.  Not sure what's installed,

# or the order?  Open a root shell and type:  aticonfig --list-adapters

#

# You can delete gpu sections if you don't have that many cards..







gpu0:
 
# remove this or set to 0 to actually use this card..
 

 


# set to 1 if cgminer will manage this gpu.
 
cgminer: 1
 
 

# overclocking.. all optional 

 

# enable to debug overclocking.. provides info on screen during mine start/restart
 
# debug_oc: 1
 
 
 
# optional command to execute prior to overclocking
 
# pre_oc_cmd:

 

# val_x = the value to set for this profile (0-2)
 
# Profile 2 is used while mining, but setting values
 
# in profile 2 that are lower than the values in the other
 
# profiles is not allowed on some GPUs, so you have to adjust
 
# the other profiles as well.

 
 
# core_speed_0: 1000
 
# core_speed_1: 1050
 
# core_speed_2: 1100
 
# mem_speed_0: 1470
 
# mem_speed_1: 1544
 
# mem_speed_2: 1617
 
# core_voltage_0: 1.125
 
# core_voltage_1: 1.125
 
# core_voltage_2: 1.250

 

# fan_speed: 70

 

# optional command to execute after overclocking
 
# post_oc_cmd:

 

# mining setup

 

# kernel to use.. currently one of:  phatk phatk2 phatk-bamt04 phatk-svn phatk-1.50 poclbm
 
# kernel: phatk2

 

# phoenix style kernel params.  do not include DEVICE=x
 
# kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=9

 

# optional phoenix queuesize parameter: how many work units to keep queued at all times
 
# queue_size: 2

 

# optional phoenix avgsamples parameter: how many samples to use for hashrate average
 
# avg_samples: 10

 

# IMPORTANT: pool_file must contain a list of pool URLs.. one at least, more if
 
# you like.  You can share the same file for all GPUs, or have one for each.
 
# Miner will start with first URL in file, however if no shares are accepted
 
# for any reason in (pool_timeout) seconds, the miner will move to next URL
 
# in the file.  Wraps around to first URL when last one fails.
 
# You can also set pool specific values, see the docs.

 

pool_file: /etc/bamt/pools

 

# default time to allow phoenix to run without finding a share..
 
# exceed this and we move to next pool in poolfile
 
pool_timeout: 180

 

# monitoring values, used by email alerts and gpumon
 
monitor_temp_lo: 45
 
monitor_temp_hi: 80
 
monitor_load_lo: 80
 
monitor_hash_lo: 125
 
monitor_fan_lo: 1000
 
monitor_reject_hi: 3





gpu1:
 
disabled: 0
 
cgminer: 1
 
# core_speed_0: 1000
 
# core_speed_1: 1050
 
# core_speed_2: 1100
 
# mem_speed_0: 1470
 
# mem_speed_1: 1544
 
# mem_speed_2: 1617
 
# core_voltage_0: 1.125
 
# core_voltage_1: 1.125
 
# core_voltage_2: 1.250

 

fan_speed: 100

 

kernel: phatk2
 
kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11

 

pool_file: /etc/bamt/pools
 
pool_timeout: 180

 

monitor_temp_lo: 45
 
monitor_temp_hi: 80
 
monitor_load_lo: 80
 
monitor_hash_lo: 125
 
monitor_fan_lo: 1000
 
monitor_reject_hi: 3

Then in my pool config file I just have 1 pool line where at the bottom it says:


#At the very least, change the next line to a valid worker url:
http://XXXXXXX:XXXX@mine.pool-x.eu:8080


But you say not to use this?



So how am I supposed to use BAMT?  If everything were working correctly am I just supposed to start cgminer from a terminal?


Or am I supposed to use the "Start mining sessions"?

Before anything else you forgot to add the --scrypt option in cgminer config.
That is a pool for mining LTC.

You mean I add --scrypt in the bamt.config file I just posted?


So it would go here?

cgminer_opts: -o http://mine.pool-x.eu:8080 -u Helper556.1 -p x --intensity 16 --api-listen --gpu-powertune 5 --gpu-engine 1150 --gpu-

memclock 1000 --auto-fan --temp-target 70



So like this?


cgminer_opts: -o http://mine.pool-x.eu:8080 -u Helper556.1 -p x --intensity 16 --scrypt --api-listen --gpu-powertune 5 --gpu-engine 1150 --gpu-

memclock 1000 --auto-fan --temp-target 70

Yes.

OK so I ran

export DISPLAY=:0
export GPU_USE_SYNC_OBJECTS=1
export GPU_MAX_ALLOC_PERCENT=100


Then I manually started cgminer using just --scrypt argument.  Then when cgminer started I manually put the URL and U:P in and now it is mining and accepting shares.

YAY!


But the KH/s is still low.


345 KH/s on I 20

Then (for now) use the same arguments in bamt.conf and Restart mining session.
Stop the manually started cgminer first.

Sorry for all the newb stuff.


But do you mean put these in the conf?

export DISPLAY=:0
export GPU_USE_SYNC_OBJECTS=1
export GPU_MAX_ALLOC_PERCENT=100

And ifso where would I put them?

No need. These are automatically executed by BAMT before running cgminer.

The line should look something like this:

OK so I had BAMT running all night.


It runs good but low KH/s.  Like between 350-400.



This is with me just starting it and then increasing the intensity.


If I try to start it and specify the thread concurrency it always gives me this message and wont start.

Loaded config file from xxx/xxx/xxx/.cgminer
Probing for alive pool
Maximum buffer memory device 0 supports says 805306368
Your scrypt settings come to 1245184000
Error -61: clCreateBuffer (padbuffer8), decrease TC or increase LG


I tried doing it by starting cgminer with the --thread concurrency xxxxx -I 20.
And I tried putting the settings in the cgminer config file and then just starting cgminer.

It always gives me the same message.




Just for the info I have tried -I 16-20 and --thread concurrency -18000-21712.
Always same message.


So today I tried -I 20 and --thread concurrency 9000 and it is working and they start running aT 600-620 KH/s but the steadily and slowly go down down down to the 400ish range.



And idea on this?


Much thanks for all the help.

Cant say much or anything about LTC mining, I'm mining only BTC or similar.
As long as I can still mine BTC with GPUs I'm not gonna kill my cards even for that extra profit.

Finding the right settings for LTC is a kind of a black art. All I can do is:

1 Point you to this thread with lots of good info: https://bitcointalk.org/index.php?topic=117221.0

2 Provide you with latest cgminer (3.0.0) that contains scrypt (LTC) improvements.

3 Advise you to not ever ever mine LTC with more than 3 cards without using powered risers.

Also, don't forget to read the READMEs included in cgminer´s folder.
Most of the time the answers are there, but no one gives a crap about the Readme, go figure.

As soon as I compile the cgminer (maybe tomorrow) I will notify you here.

Cool.


Yea I have the opposite problem.

I read so many readme's, threads, and other info that I get information overload and forget stuff or just can't put it together.


I kind of understand why mining LTC would be more stressful on a GPU but not fully.


As long as I am using powered risers and keep the temps below 80 C I should be ok?

I dunno if it's real or not but on my Windows 8 rig I have 2 cards running right now (7950's) using GUIMiner Scrypt and it says they are getting 810 and 860 KH/s.  Wierd, same settings.   Probably fake or something.

Stick with what is written in cgminer´s readme and that guide I linked.

Basically LTC mining brings higher consumption and temperatures.
Cant really say what temperature is safe. I keep my cards around 60, at 80 I would shut them down immediately.
OTOH I remember one guy around here bragging about keeping his cards at 90 for months.

About hashrates, you better compare speeds as they are reported by the pool.
I remember guiminer constantly blowing up the speeds. And if you are using Reaper as miner, that one is even a bigger liar.

OK.


I had BAMT running cgminer mining LTC at 600-650 KH/s for a few hours.  Of course I turned it off so I could move it to another room.



So now when I turn it back on and run cgminer it connects and stuff but all my shares are going to HW.  Barely any are getting accepted.




So I thought that running

export DISPLAY=:0
export GPU_USE_SYNC_OBJECTS=1
export GPU_MAX_ALLOC_PRECENT=100

fixes all of that.  but I ran those and it did not.  Been running just a couple mins and I got HW: 64 and A:4.



What is all this about now?


Im really close to having this all figured out.  I was perfectly happy when it was running 600-650 KH/s.  now I just gotta figure this out.

As i said before, no need to run those commands. They are executed automatically by BAMT.

You only need to run them if you start cgminer manually.



Try to remember what you did different.

Yea I do start cgminer manually.


I am still thinking but I dont think I did anything different.


I removed my cgminer config file and started it with just my pool info and it does the same thing.



Im going to mess with it and see what I can figure out.

I didnt see anywhere in your bamt.conf file where you specified using a cgminer.conf file. Are you actually using one?  I have always found that its easier, and you get better results if you use a cgminer.conf file, rather than making all your arguments in one line.

Yes when I start cgminer it says loaded config file and I can see that when I change a setting like the intensity it iwll start with that intensity.



I really dont get it.  I had it running awesome at over 600 for a few hours.  I turn it off then back on and now it wont work.  All I get is tons of HW errors.


If I reduce the intensity it will stop giving me HW and accept shares but it is SLOW.  I tried to slowly increase the intensity and I can get it to 12 and any higher just give HW.  At -I 12 I only get about 200 KH/s.



I have went over everything ten times.  I dont get it.  Everything is the same.

The config I posted on page 2 is the BAMT config.


I am not using BAMT miner I am manually starting cgminer.


This is the cgminer config I am using.  Its the same as the one I was using when all was good and I was getting over 600 KH/s.  The only difference is the intensity was at 20.


{
"pools" : [
   {
      "url" : "http://mine.pool-x.eu:8080",
      "user" : "XXXXXXXXXX.XXXXXX",
      "pass" : "XXXXXXX"
   }
]
,
"intensity" : "14",
"vectors" : "0",
"worksize" : "256",
"kernel" : "scrypt",
"lookup-gap" : "0",
"thread-concurrency" : "9000",
"api-port" : "4028",
"expiry" : "120",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"gpu-threads" : "1",
"gpu-engine" : "1100",
"gpu-memclock" : "1375",
"gpu-powertune" : "20",
"log" : "5",
"no-pool-disable" : true,
"queue" : "1",
"scan-time" : "60",
"scrypt" : true,
"shares" : "0",
"kernel-path" : "/usr/local/bin"

Other than that what could have changed?


I am using AMD overdrive to OC the cards.

I have the same settings in cgminer that I do on overdrive.

I got BAMT mining (not manually cgminer) and it will run at good speed but it barely generates any shares.  I imagine this is because they are all HW but the GPUMON doesnt have a spot to view HW.

Sorry to keep posting without a response.


I made another bamt on another flash drive and I changed my settings.  Now bamt actually mines correctly!  It gets about 600 KH/s per card and it accepts shares correctly.  And not with me manually starting cgminer like before but with the built in bamt.


Problem is that after a few mins.  And I mean just a few like 2 it just goes poof and dies.


One thing I was thinking is that does bamt have an auto shutoff for the GPU temp getting too high?  I ask this because since bamt starts mining as soon as it boots up It doesnt give me much time to turn the fan all the way up.  so it may have gotten up to like 85 or something before it died.


I have restarted it and this time I hurried and stopped mining as soon as it booted.  Then I turned the fan to 100% and restarted mining.


It is working as of right now.  If it stays this way I may just have a party!  Knowing my luck somebody would end up spilling a beer on my rig and I would have to start over.  hahaha


But as long as it doesnt die again I got it working perfect.  Will update.


If you have any other reasons why it would just turn off like that please let me know.  I know it is not automatically set to go to sleep or something because I was using the rig when it died.  And I do not have any riser cables hooked up right now.  Just 2 GPUs straight into the mobo.

You are mixing the hell out of things.

Do not use AMD overdrive at the same time with cgminer.
Do not use a gazillion of cgminer configs, that separated cgminer config is a mess. No wonder BAMT craps out, it is confused by all those contradictory settings.

Burn a fresh BAMT again, apply all the fixes and enter all (ALL) the necessary settings (pools, clocks, fan speeds etc) in that cgminer line and no place else.
(yes, this is one method, the other one is to use a separated config, but do not use both, for the sake of simplicity stick with the above since it is already there)
Don't copy/paste random settings you found all over the forum, stick with cgminer´s README & that guide I linked before.
Don't use two instances of cgminer at the same time, one started by BAMT and one by you.
You can monitor what cgminer is doing by enter in terminal: screen -r cgminer while cgminer is running (if started by BAMT).


All you need to do is enter the right settings in the bamt config (that cgminer_opts line) and BAMT will work.

Yes, this is what I was getting at, it appears he is trying to declare things in both the CGMiner line in the BAMT config, as well as the CGMiner config file itself.  Its simple really, use the config file, and just tell BAMT to go look there.  So, this is what you should do.

1) Clean in stall BAMT (including changing your root password, and getting root acess)
2) Run fixer and get all updates
3) Update CGMiner and AMD SDK using the instructions here https://bitcointalk.org/index.php?topic=127622.0
4) In the BAMT config file, make these declarations.
     -Just below where it has the SMTP settings put these setting:
          -cgminer: 1
          -cgminer_opts: --config /etc/bamt/cgminer.conf
     -Go down to GPU0, delete the disable: 1 line, and replace it with cgminer: 1
     -Save your file
5) Create the cgminer.conf by typing: nano /etc/bamt/cgminer.conf
6) Copy and paste the config file you posted earlier for it in here, including all of the pool data, then save.
7) Coldreboot

That should be all you need for BAMT to start, start CGMiner automatically, connect, and use the settings you have told it to.

The BAMT he is using has the best combination of SDK and AMD drivers for 7XXX cards already installed.
I also gave him one of the latest cgminer (the same version I use now).
This was the point of my intervention here, a ready to use BAMT for 7xxx cards.

What method to use for cgminer arguments is a matter of choice, there isn't a good one and a bad one.
This BAMT is already configured for entering all the arguments in the cgminer_opts line.
He can always choose the other method instead, but better not mix them.

I understood there were two ways to do it.  By using a cgminer config with me manually starting cgminer and then by using BAMT.  I think some of my problem was that I kept forgetting that BAMT was gonna automatically start mining.  So some of the times I was starting cgminer manually BAMT was already mining.

I just thought that the BAMT way wasn't working because I was trying to mine LTC.


So I was bouncing back and forth trying to figure it out.



So last night I got it running by just changing the cgminer opts line.  Right now I got it running using the cgminer conf and the ops line.  all I have on the ops line is, --scrypt, apil-listen, and gpu fan 100.



When I first got to the rig this morning it was like stuck.  It still said it was mining and it wasnt froze as I could open stuff.  But the shares werent going up.

I tried to hit restart mining and then I tried stop mining and then start mining.  And nothing happened.  The GPOUmon never showed that mining had stopped.


I ended up having to close the GPUmon window and reopen it.

Im gonna see if it does it again.  It is running fine right now.  I think maybe GPUmon froze and it really was mining.  Because when I hit stop mining it popped up the window where it stops mining but GPUmon didn't show any change.  Then when I closed and reopened GPUmon it showed that mining was stopped.  (I had stopped it).


And again Im sorry for bugging you guys by being all over the place.  I REALLY appreciate your help.  Especially you Phillips.  I would be nowhere without your help.  I have donated to lordcrappo as you suggested.

I set it to run again and all was running right.


Then I left for a couple hours and when I got back it was froze again.  This time I couldnt even move the mouse.


Going to go over everything again and see if it does it again.  If it does I am going to start over with a fresh BAMT install.

And how do I get the IP address of my BAMT rig?  Right now the only address I can get is the local one 192.168.x.xxx.  This is not the correct address to use right?  Because I will only be able to loginto it if I were connected to my home network?


I have SSH client on my iphone and it would be great to be able to restart the miners if they crash.

Start reading from here: https://bitcointalk.org/index.php?topic=28967.msg758975#msg758975

As I have been told you: consult the BAMT main thread, tons and tons of answers already there.

As promised, latest cgminer (3.1.1) compiled on this version of BAMT: cgminer.zip (http://www.uploadmb.com/dw.php?id=1368368772)

So do the same thing as with the other cgminer?  Just copy the folder over?


Much thanks