Best advice IMO: When you get it working, stop fuxing with it.
I believe this is rule #2 of BAMT
Topic: BAMT version 0.5 - Easy USB based mining Linux with farm wide management tools - page 60. (Read 324169 times)
March 19, 2012, 10:23:39 AM
I believe this is rule #2 of BAMT
March 19, 2012, 07:53:47 AM
how do i get this page, the top left image http://i.imgur.com/VoEQF.jpg to show if i am at work? i use windows.
An easy way, if your router/firewall supports it, is to port forward in on a non-standard port for example port 10001 forwarding to port 80 of the rig. Then just hit you home IP on that port. http://homeip:10001
Eagerly awaiting BAMT Pro though.
March 19, 2012, 07:10:44 AM
Same way you make any web page on any private network available to the public internet.
Another option is to subscribe to BAMT Pro.
Another option is to subscribe to BAMT Pro.
Is BAMT Pro now available? Where do I sign up?
March 19, 2012, 06:06:29 AM
how do i get this page, the top left image http://i.imgur.com/VoEQF.jpg to show if i am at work? i use windows.
Same way you make any web page on any private network available to the public internet.
Another option is to subscribe to BAMT Pro.
March 19, 2012, 02:06:51 AM
how do i get this page, the top left image http://i.imgur.com/VoEQF.jpg to show if i am at work? i use windows.
vpn into your home pc.
March 19, 2012, 01:59:16 AM
how do i get this page, the top left image http://i.imgur.com/VoEQF.jpg to show if i am at work? i use windows.
March 18, 2012, 06:49:39 PM
Thanks for this, I was looking for a good alternative to linuxcoin since it hasn't been maintained. I have a problem with overclocking, however.
If I use the bamt config file to overclock, the system locks up and I have to force it to shut down, then boot up bamt on a computer without ati cards to fix the config file. However, if I use ati config to overclock the cards manually, everything works fine.
At the moment I have 2 5770 cards. When overclocking worked, I used these commands:
when I used the bamt config file and it locked up, I used these settings:
I don't remember exactly what all the parameters are called but you get the point.
What is the difference between how aticonfig sets up overclocking and how bamt sets up overclocking to cause this problem?
If I use the bamt config file to overclock, the system locks up and I have to force it to shut down, then boot up bamt on a computer without ati cards to fix the config file. However, if I use ati config to overclock the cards manually, everything works fine.
At the moment I have 2 5770 cards. When overclocking worked, I used these commands:
Quote
aticonfig --od-enable
aticonfig --odsc=960,1200 --adapter=all
aticonfig --odsc=960,1200 --adapter=all
when I used the bamt config file and it locked up, I used these settings:
Quote
card_0:
...
core_0:960
core_1:960
core_2:960
mem_0:1200
mem_1:1200
mem_2:1200
...
card_1:
...
core_0:960
core_1:960
core_2:960
mem_0:1200
mem_1:1200
mem_2:1200
...
...
core_0:960
core_1:960
core_2:960
mem_0:1200
mem_1:1200
mem_2:1200
...
card_1:
...
core_0:960
core_1:960
core_2:960
mem_0:1200
mem_1:1200
mem_2:1200
...
I don't remember exactly what all the parameters are called but you get the point.
What is the difference between how aticonfig sets up overclocking and how bamt sets up overclocking to cause this problem?
Why are you changing profiles 0 and 1??
Please review overclocking basics and how the profiles work in ATI cards.
aticonfig changes clocks only in profile 2 by default. so should you.
March 18, 2012, 05:22:09 PM
Thanks for this, I was looking for a good alternative to linuxcoin since it hasn't been maintained. I have a problem with overclocking, however.
If I use the bamt config file to overclock, the system locks up and I have to force it to shut down, then boot up bamt on a computer without ati cards to fix the config file. However, if I use ati config to overclock the cards manually, everything works fine.
At the moment I have 2 5770 cards. When overclocking worked, I used these commands:
when I used the bamt config file and it locked up, I used these settings:
I don't remember exactly what all the parameters are called but you get the point.
What is the difference between how aticonfig sets up overclocking and how bamt sets up overclocking to cause this problem?
If I use the bamt config file to overclock, the system locks up and I have to force it to shut down, then boot up bamt on a computer without ati cards to fix the config file. However, if I use ati config to overclock the cards manually, everything works fine.
At the moment I have 2 5770 cards. When overclocking worked, I used these commands:
Quote
aticonfig --od-enable
aticonfig --odsc=960,1200 --adapter=all
aticonfig --odsc=960,1200 --adapter=all
when I used the bamt config file and it locked up, I used these settings:
Quote
card_0:
...
core_0:960
core_1:960
core_2:960
mem_0:1200
mem_1:1200
mem_2:1200
...
card_1:
...
core_0:960
core_1:960
core_2:960
mem_0:1200
mem_1:1200
mem_2:1200
...
...
core_0:960
core_1:960
core_2:960
mem_0:1200
mem_1:1200
mem_2:1200
...
card_1:
...
core_0:960
core_1:960
core_2:960
mem_0:1200
mem_1:1200
mem_2:1200
...
I don't remember exactly what all the parameters are called but you get the point.
What is the difference between how aticonfig sets up overclocking and how bamt sets up overclocking to cause this problem?
March 17, 2012, 08:35:53 PM
first time I've ever heard of monitor on/off effecting hash rate. try swapping GPUs around so a different one is gpu 0, maybe will go away.
Just had time to check bamt with fat16, boots and works flawlessly now, will toss you a coin first thing in the morning
EDIT: Tossed.
March 17, 2012, 04:44:07 PM
I had a monitor hooked up to a rig for some time because I was testing lowest energy consuming BIOS settings (no way to do that remotely I think at least not cheaply). Did get any problems after turning it off but I did once I unplugged it (bamt crashed, but it was more driver-related as far as I remember), I remember another user here having the same problem but the solution is to unplug the monitor after saving the BIOS settings (before booting bamt).
But this is really not much of a problem
Once you have everything set up, boot the rig without the monitor and see throught web gpumon or ssh if everything's correct. It happens for you with all gpus, regardless of the slot used?
No, just Gpu0. Im going to try Lordcrappos advice once Im done swapping out the stock cooling on the next gpu im plugging in as it's a lowly 5770 and I figure having the lowest hashing card as gpu0 makes sense... guess that'll be tuesday because of snail-mail latency
March 17, 2012, 04:34:27 PM
I had a monitor hooked up to a rig for some time because I was testing lowest energy consuming BIOS settings (no way to do that remotely I think at least not cheaply). Didn't get any problems after turning it off but I did once I unplugged it (bamt crashed, but it was more driver-related as far as I remember), I remember another user here having the same problem but the solution is to unplug the monitor after saving the BIOS settings (before booting bamt).
But this is really not much of a problem
Once you have everything set up, boot the rig without the monitor and see throught web gpumon or ssh if everything's correct. It happens for you with all gpus, regardless of the slot used?
March 17, 2012, 04:25:22 PM
This is propably more of a feature than a bug/problem, but im clueless as to where to start looking for a solution so here goes:
(In before rtfm and read the thread, done multiple times)
Im running a rig with 3 gpu's in it and to the gpu0 (5830) there is a monitor attached. Whenever I turn the monitor off my hashrate drops about 100Mhs. the motherboard is Asus P5Q-E, bamt is in it's most recent version (up to date 5h ago atleast). Any other info I should supply ?
And I do know I shouldnt even have a monitor attached to the rig, but as it is very much a work in progress I find it easyer this way.
I am unsure what happens when the monitor powers itself doen after X minutes, am currently waiting for this to happen.
Any and all hints would greatly be appreciated.
(In before rtfm and read the thread, done multiple times)
Im running a rig with 3 gpu's in it and to the gpu0 (5830) there is a monitor attached. Whenever I turn the monitor off my hashrate drops about 100Mhs. the motherboard is Asus P5Q-E, bamt is in it's most recent version (up to date 5h ago atleast). Any other info I should supply ?
And I do know I shouldnt even have a monitor attached to the rig, but as it is very much a work in progress I find it easyer this way.
I am unsure what happens when the monitor powers itself doen after X minutes, am currently waiting for this to happen.
Any and all hints would greatly be appreciated.
first time I've ever heard of monitor on/off effecting hash rate. try swapping GPUs around so a different one is gpu 0, maybe will go away.
March 17, 2012, 04:21:19 PM
This is propably more of a feature than a bug/problem, but im clueless as to where to start looking for a solution so here goes:
(In before rtfm and read the thread, done multiple times)
Im running a rig with 3 gpu's in it and to the gpu0 (5830) there is a monitor attached. Whenever I turn the monitor off my hashrate drops about 100Mhs. the motherboard is Asus P5Q-E, bamt is in it's most recent version (up to date 5h ago atleast). Any other info I should supply ?
And I do know I shouldnt even have a monitor attached to the rig, but as it is very much a work in progress I find it easyer this way.
I am unsure what happens when the monitor powers itself doen after X minutes, am currently waiting for this to happen.
Any and all hints would greatly be appreciated.
(In before rtfm and read the thread, done multiple times)
Im running a rig with 3 gpu's in it and to the gpu0 (5830) there is a monitor attached. Whenever I turn the monitor off my hashrate drops about 100Mhs. the motherboard is Asus P5Q-E, bamt is in it's most recent version (up to date 5h ago atleast). Any other info I should supply ?
And I do know I shouldnt even have a monitor attached to the rig, but as it is very much a work in progress I find it easyer this way.
I am unsure what happens when the monitor powers itself doen after X minutes, am currently waiting for this to happen.
Any and all hints would greatly be appreciated.
March 17, 2012, 02:23:34 PM
My rig was crashing when I changed some fan speeds. I put them back and it started working again just fine. So weird.
Best advice IMO: When you get it working, stop fuxing with it.
Best advice IMO: When you get it working, stop fuxing with it.
March 17, 2012, 01:41:14 PM
Does any one knows where is the mgpumon.css file?
I can't find it.
I want to try something
I can't find it.
I want to try something
March 17, 2012, 12:40:18 AM
.....
seems like everything that comes up in bamt lately never gets explained
Lol, sometimes it just goes that way...
March 17, 2012, 12:24:44 AM
Trying to research this.. I'm not finding many references or examples of leaving off the screen number (using only :display instead of the full specifier :display.screen) or reasons for doing this. What made you think it should be done, and is there an explanation of why you would export only the partial setting? Mostly I am worried that this may cause problems with other cgminer versions or driver versions or whatever it is that wants the strange setting in the first place. Any pointer to how you came up with this is appreciated. If I can be sure it's not going to be more trouble, I'll just change the script in a fix/next image.
Its in the cgminer readme...
Quote
On Linux you virtually always need to export your display settings before
starting to get all the cards recognised and/or temperature+clocking working:
export DISPLAY=:0
starting to get all the cards recognised and/or temperature+clocking working:
export DISPLAY=:0
I didnt dig into your scripts to find out why it wasnt working on my 7970's, but I did create my own script to export that display variable to get it working on bamt for myself.
Ok, if cgminer docs call for it then good enough for me. I will update the script to give cgminer :0. Still don't see why cgminer needs a strange display export, been using X for years and always used :display.screen not just :display, not to mention all the other tools (atitweak, phoenix, etc) use the :0.0 form, and I don't see why this is only effecting 7970 people if cgminer docs call for it on all versions, but I'm not much of an X person so maybe its normal or has a sensible explanation.
seems like everything that comes up in bamt lately never gets explained
March 16, 2012, 11:38:53 PM
Trying to research this.. I'm not finding many references or examples of leaving off the screen number (using only :display instead of the full specifier :display.screen) or reasons for doing this. What made you think it should be done, and is there an explanation of why you would export only the partial setting? Mostly I am worried that this may cause problems with other cgminer versions or driver versions or whatever it is that wants the strange setting in the first place. Any pointer to how you came up with this is appreciated. If I can be sure it's not going to be more trouble, I'll just change the script in a fix/next image.
Its in the cgminer readme...
Quote
On Linux you virtually always need to export your display settings before
starting to get all the cards recognised and/or temperature+clocking working:
export DISPLAY=:0
starting to get all the cards recognised and/or temperature+clocking working:
export DISPLAY=:0
I didnt dig into your scripts to find out why it wasnt working on my 7970's, but I did create my own script to export that display variable to get it working on bamt for myself.
March 16, 2012, 09:29:18 PM
I wish I could help. I only have 7970s or I would try to troubleshoot it for you. With 7970s I have to upgrade the drivers and I think that's probably what's causing the issue. Have you tried using the AMD Catalyst™ 12.2 Proprietary Linux x86 Display Driver -> http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx?type=2.4.1&product=2.4.1.3.42&lang=English.
Trying to research this.. I'm not finding many references or examples of leaving off the screen number (using only :display instead of the full specifier :display.screen) or reasons for doing this. What made you think it should be done, and is there an explanation of why you would export only the partial setting? Mostly I am worried that this may cause problems with other cgminer versions or driver versions or whatever it is that wants the strange setting in the first place. Any pointer to how you came up with this is appreciated. If I can be sure it's not going to be more trouble, I'll just change the script in a fix/next image.
As for 12.2, I haven't tried it (and don't have enough variations of hardware here to make good judgment anyway). As of 12.1, it was often said that any driver past 11.6 caused significant slow downs in mining performance, so we have stuck with 11.6 so far. Same with SDK 2.4, although there are are a couple cards that get better performance with 2.6, most have worse, so we stuck with 2.4. Like I said, I can't judge this myself so rely on whats said here on the forums and from people running large farms for feedback and advice on what versions to use in the stock image.
March 16, 2012, 07:49:41 PM
think I read somewhere about installing opencl after the 12.2 driver causes problems. I messed with it yesterday and I don't recall seeing the option to uncheck the APP SDK that normally is present
Jump to: