Topic: BAMT version 0.5 - Easy USB based mining Linux with farm wide management tools - page 64. (Read 324176 times)
March 11, 2012, 03:46:09 AM
lodcrappo, can you answer my question?
March 11, 2012, 03:30:59 AM
i really don't know.
cgminer has been nothing but a pain in my ass since I added it to bamt. it's behavior is just flaky in many situations. while phoenix and phoenix2 both are rock solid and never have these types of bizarre problems, unexplained problems seem to be par for the course with cgminer. they often disappear with a new cgminer version, only to be replaced by new insanity.
maybe its something bamt does, but I can't tell what it is. all we are doing is forking with the very command you find works from the shell. nothing complicated. works fine with phoenix and phoenix2.
Cool no problem. As always, thx for you help. I tried phx2, but it has the 100% cpu bug (which is fixed in cgminer by exporting a variable), only started the first gpu, and bamt didnt read Mh/s from it... maybe something with my 7970's being new? I'll stick to cgminer for now since it starts all my cards and mess around with it later on.
The first 10 BTC I made are headed your way... thanks for everything!
Hopefully others make some donations as well! i did 1 BTC per card, but even 1 BTC per rig will help lodcrappo out so please donate!
OK, sorry but the 7xxx series really just are not supported at this time, that is probably the biggest source of things going poorly.
Maybe someday.
And many thanks for the kind contribution
March 11, 2012, 03:26:26 AM
It's possible to set gpu, mem clocks/voltage with it? CGMiner is not an option, because don't support 6 series radeons mem downclocking and undervolting.
March 10, 2012, 11:18:06 PM
i really don't know.
cgminer has been nothing but a pain in my ass since I added it to bamt. it's behavior is just flaky in many situations. while phoenix and phoenix2 both are rock solid and never have these types of bizarre problems, unexplained problems seem to be par for the course with cgminer. they often disappear with a new cgminer version, only to be replaced by new insanity.
maybe its something bamt does, but I can't tell what it is. all we are doing is forking with the very command you find works from the shell. nothing complicated. works fine with phoenix and phoenix2.
Cool no problem. As always, thx for you help. I tried phx2, but it has the 100% cpu bug (which is fixed in cgminer by exporting a variable), only started the first gpu, and bamt didnt read Mh/s from it... maybe something with my 7970's being new? I'll stick to cgminer for now since it starts all my cards and mess around with it later on.
The first 10 BTC I made are headed your way... thanks for everything!
Hopefully others make some donations as well! i did 1 BTC per card, but even 1 BTC per rig will help lodcrappo out so please donate!
March 10, 2012, 03:50:09 PM
something is seriously wrong with your image or your usb key.
suggest to download again.
suggest to download again.
I think my keys are fine, tried 3, of two different brands, and tried burning the img several times. Also, the was no problem with 0.4.
I'll download again from a different source and report once I try.
there is no difference in boot between "0.4" and "0.5". There is very little difference in anything between the last 0.4 fix and the first 0.5 image.
the numbering sequence change was simply an arbitrary decision designed to try and make a clean start with documentation and other administrative things.
from a code perspective, "version 0.4" and "version 0.5" means basically nothing, I just decided instead of doing fix #37 for "0.4" we would call it 0.5 fix 1.
March 10, 2012, 03:43:30 PM
something is seriously wrong with your image or your usb key.
suggest to download again.
suggest to download again.
I think my keys are fine, tried 3, of two different brands, and tried burning the img several times. Also, the was no problem with 0.4.
I'll download again from a different source and report once I try.
March 10, 2012, 03:40:13 PM
I can't boot bamt 0.5 
Bamt 0.4 works fine on two sticks, with bamt 0.5 I get this:
Googled a bit but none of the solutions worked for me (placing syslinux files somewhere else, burning the image onto the usb stick again and again, trying another usb stick, etc.)
I used Win32 Disk Imager, same one I used with bamt 0.4.
Maybe I'm doing something wrong?
Bamt 0.4 works fine on two sticks, with bamt 0.5 I get this:
Code:
SYSLINUX 4.02 debia-20101014CHS Copyright (C) 1994-2010 H. Peter Anvin et al
ERROR: No configuration file found
No DEFAULT or UI configuration directive found!
boot:
Googled a bit but none of the solutions worked for me (placing syslinux files somewhere else, burning the image onto the usb stick again and again, trying another usb stick, etc.)
I used Win32 Disk Imager, same one I used with bamt 0.4.
Maybe I'm doing something wrong?
something is seriously wrong with your image or your usb key.
suggest to download again.
March 10, 2012, 03:30:08 PM
I can't boot bamt 0.5
Bamt 0.4 works fine on two sticks, with bamt 0.5 I get this:
Googled a bit but none of the solutions worked for me (placing syslinux files somewhere else, burning the image onto the usb stick again and again, trying another usb stick, etc.)
I used Win32 Disk Imager, same one I used with bamt 0.4.
Maybe I'm doing something wrong?
Bamt 0.4 works fine on two sticks, with bamt 0.5 I get this:
Code:
SYSLINUX 4.02 debia-20101014CHS Copyright (C) 1994-2010 H. Peter Anvin et al
ERROR: No configuration file found
No DEFAULT or UI configuration directive found!
boot:
Googled a bit but none of the solutions worked for me (placing syslinux files somewhere else, burning the image onto the usb stick again and again, trying another usb stick, etc.)
I used Win32 Disk Imager, same one I used with bamt 0.4.
Maybe I'm doing something wrong?
March 10, 2012, 01:44:01 PM
perfect sense. however, when i cat the bamt.log and check the command it runs, it is:
cd /opt/miners/cgminer;/usr/bin/screen -d -m -S cgminer /opt/miners/cgminer/cgminer --config /etc/bamt/cgminer.conf
I can run this command from CLI and it works fine (except BAMT does not see MH/s, but sees everything else).
However, if I run it from gpumon, nothing ever starts.
By the way, I'm having great luck with the 7970's on standard BAMT. All I had to do install the drivers from here (and use cgminer):
http://www2.ati.com/drivers/hotfix/radeon_7900_series/amd-driver-installer-8.921-x86.x86_64.run
cd /opt/miners/cgminer;/usr/bin/screen -d -m -S cgminer /opt/miners/cgminer/cgminer --config /etc/bamt/cgminer.conf
I can run this command from CLI and it works fine (except BAMT does not see MH/s, but sees everything else).
However, if I run it from gpumon, nothing ever starts.
Quote
---
settings:
miner_id: bamt-miner
miner_loc: unspecified location
do_monitor: 0
cgminer: 1
cgminer_opts: --config /etc/bamt/cgminer.conf
gpu0:
disabled: 0
cgminer: 1
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_fan_lo: 2000
monitor_reject_hi: 2
gpu1:
disabled: 0
cgminer: 1
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_fan_lo: 2000
monitor_reject_hi: 1
gpu2:
disabled: 0
cgminer: 1
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_fan_lo: 2000
monitor_reject_hi: 1
settings:
miner_id: bamt-miner
miner_loc: unspecified location
do_monitor: 0
cgminer: 1
cgminer_opts: --config /etc/bamt/cgminer.conf
gpu0:
disabled: 0
cgminer: 1
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_fan_lo: 2000
monitor_reject_hi: 2
gpu1:
disabled: 0
cgminer: 1
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_fan_lo: 2000
monitor_reject_hi: 1
gpu2:
disabled: 0
cgminer: 1
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_fan_lo: 2000
monitor_reject_hi: 1
By the way, I'm having great luck with the 7970's on standard BAMT. All I had to do install the drivers from here (and use cgminer):
http://www2.ati.com/drivers/hotfix/radeon_7900_series/amd-driver-installer-8.921-x86.x86_64.run
i really don't know.
cgminer has been nothing but a pain in my ass since I added it to bamt. it's behavior is just flaky in many situations. while phoenix and phoenix2 both are rock solid and never have these types of bizarre problems, unexplained problems seem to be par for the course with cgminer. they often disappear with a new cgminer version, only to be replaced by new insanity.
maybe its something bamt does, but I can't tell what it is. all we are doing is forking with the very command you find works from the shell. nothing complicated. works fine with phoenix and phoenix2.
March 10, 2012, 01:38:56 PM
perfect sense. however, when i cat the bamt.log and check the command it runs, it is:
cd /opt/miners/cgminer;/usr/bin/screen -d -m -S cgminer /opt/miners/cgminer/cgminer --config /etc/bamt/cgminer.conf
I can run this command from CLI and it works fine (except BAMT does not see MH/s, but sees everything else).
However, if I run it from gpumon, nothing ever starts.
By the way, I'm having great luck with the 7970's on standard BAMT. All I had to do install the drivers from here (and use cgminer):
http://www2.ati.com/drivers/hotfix/radeon_7900_series/amd-driver-installer-8.921-x86.x86_64.run
cd /opt/miners/cgminer;/usr/bin/screen -d -m -S cgminer /opt/miners/cgminer/cgminer --config /etc/bamt/cgminer.conf
I can run this command from CLI and it works fine (except BAMT does not see MH/s, but sees everything else).
However, if I run it from gpumon, nothing ever starts.
Quote
---
settings:
miner_id: bamt-miner
miner_loc: unspecified location
do_monitor: 0
cgminer: 1
cgminer_opts: --config /etc/bamt/cgminer.conf
gpu0:
disabled: 0
cgminer: 1
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_fan_lo: 2000
monitor_reject_hi: 2
gpu1:
disabled: 0
cgminer: 1
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_fan_lo: 2000
monitor_reject_hi: 1
gpu2:
disabled: 0
cgminer: 1
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_fan_lo: 2000
monitor_reject_hi: 1
settings:
miner_id: bamt-miner
miner_loc: unspecified location
do_monitor: 0
cgminer: 1
cgminer_opts: --config /etc/bamt/cgminer.conf
gpu0:
disabled: 0
cgminer: 1
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_fan_lo: 2000
monitor_reject_hi: 2
gpu1:
disabled: 0
cgminer: 1
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_fan_lo: 2000
monitor_reject_hi: 1
gpu2:
disabled: 0
cgminer: 1
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_fan_lo: 2000
monitor_reject_hi: 1
By the way, I'm having great luck with the 7970's on standard BAMT. All I had to do install the drivers from here (and use cgminer):
http://www2.ati.com/drivers/hotfix/radeon_7900_series/amd-driver-installer-8.921-x86.x86_64.run
March 10, 2012, 01:07:58 PM
Hopefully an easy question... When i start cgminer from gpumon, it only starts the first gpu, even though I have "cgminer: 1" on gpu's 1 and 2 (and gpu's 1 and 2 enabled).
When I take the cgminer_opts string, and start cgminer directly with the same string in the bamt.conf, all GPU's start mining fine. Am I missing something?
When I take the cgminer_opts string, and start cgminer directly with the same string in the bamt.conf, all GPU's start mining fine. Am I missing something?
All the cgminer:1 setting per gpu does is tell BAMT how to pull statistics for that GPU.
It doesn't have anything to do with whether cgminer actually uses it, that is determined entirely by your cgminer configuration.
your cgminer config comes from the cgminer_opts, which may or may not in turn point to a file containing more cgminer configuration. none of it comes from anywhere else in bamt whatsoever. the settings in each GPU section do not effect cgminer's operation in any way at all, only how/whether BAMT talks to cgminer. hope that makes sense.
March 10, 2012, 12:54:18 PM
Hopefully an easy question... When i start cgminer from gpumon, it only starts the first gpu, even though I have "cgminer: 1" on gpu's 1 and 2 (and gpu's 1 and 2 enabled).
When I take the cgminer_opts string, and start cgminer directly with the same string in the bamt.conf, all GPU's start mining fine. Am I missing something?
When I take the cgminer_opts string, and start cgminer directly with the same string in the bamt.conf, all GPU's start mining fine. Am I missing something?
March 10, 2012, 12:39:53 PM
It is likely that you are on the very edge of stability
Earlier this rig worked with large clock permanently without problem.So shall see...
Please don't make assumptions like this. Just because something worked before on something else, doesn't mean it'll work now with something completely different.
March 10, 2012, 11:22:22 AM
It is likely that you are on the very edge of stability
Earlier this rig worked with large clock permanently without problem.So shall see...
Back off your overclock about 10MHz for cgminer, it tends to push the GPUs harder than the other miners do.
This. You likely will find you get the same MH/s and at lower wattage. If it is stable at old clock - 10 Mhz you can try -5 Mhz.
March 10, 2012, 03:40:41 AM
BAMT Pro (fix19)? interesting... more info?
today I moved all my rigs on BAMT .5
lodcrappo greats work!!! catch my litle donations
today I moved all my rigs on BAMT .5
lodcrappo greats work!!! catch my litle donations
March 10, 2012, 02:56:14 AM
It is likely that you are on the very edge of stability
Earlier this rig worked with large clock permanently without problem.So shall see...
Back off your overclock about 10MHz for cgminer, it tends to push the GPUs harder than the other miners do.
March 09, 2012, 05:34:37 PM
It is likely that you are on the very edge of stability
Earlier this rig worked with large clock permanently without problem.So shall see...
March 09, 2012, 05:10:02 PM
Try setting your clocks to stock as a test.
ooo... with stock clock cgminer start (why??? on phoenix it start with OC clock!!!). BIG thx.
BUT!!! after i set previos OC clock and cgminer start too! mystic
It is likely that you are on the very edge of stability. When GPU is overclock too much, strange behavior will result before you go all the way to locking up.
Usually, a GPU running at this type of overclocking will also lock up "for no reason" every few days, or weeks.
March 09, 2012, 05:07:45 PM
Try setting your clocks to stock as a test.
ooo... with stock clock cgminer start (why??? on phoenix it start with OC clock!!!). BIG thx.
BUT!!! after i set previos OC clock and cgminer start too! mystic
March 09, 2012, 02:07:32 PM
if it is going zombie then likely a GPU is hanging with load. Try setting your clocks to stock as a test.
Jump to: