Pages:
Author

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

sr. member
Activity: 303
Merit: 250
I get 318-319 at 980mhz with phoenix2

how do i run phoenix 2? phoenix2: 1 in bamt.conf then configure phoenix2.conf file and it won't run

i have a doubts with the [cl:0:0] things for each device, should i keep going like [c:0:x] or [c:x:0]?
newbie
Activity: 56
Merit: 0
I feel like an idiot asking here, so if you find this annoying, please disregard my post.

But I've been looking for the command that helps me identify which gpu is which in BAMT Linux. I thought it was -atigpuidentify or something like that. Any helps would be great! Thanks!

aticonfig --list-adapters
That was quick! Thanks! Grin
sr. member
Activity: 303
Merit: 250
I feel like an idiot asking here, so if you find this annoying, please disregard my post.

But I've been looking for the command that helps me identify which gpu is which in BAMT Linux. I thought it was -atigpuidentify or something like that. Any helps would be great! Thanks!

aticonfig --list-adapters
newbie
Activity: 56
Merit: 0
I feel like an idiot asking here, so if you find this annoying, please disregard my post.

But I've been looking for the command that helps me identify which gpu is which in BAMT Linux. I thought it was -atigpuidentify or something like that. Any helps would be great! Thanks!
hero member
Activity: 626
Merit: 500
Mining since May 2011.

start with 880 core, stock volts. only remove the '#' for the core_speed_2 line, that is the profile active when mining

then move up from there to say 950, 980, 1000 my 5830s refuse to clock to 1000

Awesome, thanks!
Got it at 980 right now, seems good so far.
Gonna let it run tonight and see if it's still cool in the morning.
Thanks for the help guys, BAMT rocks!!!

And when you can, remember to donate up at http://bamter.org/ to help keep the project funded.  Cool
full member
Activity: 155
Merit: 100

start with 880 core, stock volts. only remove the '#' for the core_speed_2 line, that is the profile active when mining

then move up from there to say 950, 980, 1000 my 5830s refuse to clock to 1000

Awesome, thanks!
Got it at 980 right now, seems good so far.
Gonna let it run tonight and see if it's still cool in the morning.
Thanks for the help guys, BAMT rocks!!!
sr. member
Activity: 303
Merit: 250
dunno why you cant, but you dont need to get into amd overdrive ctl or ccc or any of that.  

everything you need is right in the bamt.conf file.

edit it properly, restart mining.  that is all.

you should be getting 310 to 320 mhash with 5830.  it sounds like you did not set your overclocking in bamt.conf properly.  please double check it.

I agree. Now that it's hashing, I'm not really concerned with CCC or overdrive.
I didn't set any overclocking, because the guide said to run it at stock first.
What are the suggested (starting) OC settings for an XFX 5830 with reference cooler?
It's currently set at 300/800/980 in the conf file.
How do I know which profile is currently in use?

start with 880 core, stock volts. only remove the '#' for the core_speed_2 line, that is the profile active when mining

then move up from there to say 950, 980, 1000 my 5830s refuse to clock to 1000
hero member
Activity: 616
Merit: 506

After you boot BAMT for the first time and you're at the GUI, does it say anything in the top right of the screen under GPUs Detected: ?

Thanks for the quick reply!
Yeah, it does.
It says:
GPUs Detected:
0 01:00.0 ATI Radeon HD 5800 Series

Hang on...it's doing something now, but I still can't get into CCC or AMD Overdrive Ctrl
It appears to be hasing at around 247Mh/s, which seems awfully low.

dunno why you cant, but you dont need to get into amd overdrive ctl or ccc or any of that.  

everything you need is right in the bamt.conf file.

edit it properly, restart mining.  that is all.

you should be getting 310 to 320 mhash with 5830.  it sounds like you did not set your overclocking in bamt.conf properly.  please double check it.

you have to set core clock to 1000 for a 5830 to have 320MH/s, my 5830s are at 950 core 305MH/s


I get 318-319 at 980mhz with phoenix2
full member
Activity: 155
Merit: 100
dunno why you cant, but you dont need to get into amd overdrive ctl or ccc or any of that. 

everything you need is right in the bamt.conf file.

edit it properly, restart mining.  that is all.

you should be getting 310 to 320 mhash with 5830.  it sounds like you did not set your overclocking in bamt.conf properly.  please double check it.

I agree. Now that it's hashing, I'm not really concerned with CCC or overdrive.
I didn't set any overclocking, because the guide said to run it at stock first.
What are the suggested (starting) OC settings for an XFX 5830 with reference cooler?
It's currently set at 300/800/980 in the conf file.
How do I know which profile is currently in use?
sr. member
Activity: 303
Merit: 250

After you boot BAMT for the first time and you're at the GUI, does it say anything in the top right of the screen under GPUs Detected: ?

Thanks for the quick reply!
Yeah, it does.
It says:
GPUs Detected:
0 01:00.0 ATI Radeon HD 5800 Series

Hang on...it's doing something now, but I still can't get into CCC or AMD Overdrive Ctrl
It appears to be hasing at around 247Mh/s, which seems awfully low.

dunno why you cant, but you dont need to get into amd overdrive ctl or ccc or any of that.  

everything you need is right in the bamt.conf file.

edit it properly, restart mining.  that is all.

you should be getting 310 to 320 mhash with 5830.  it sounds like you did not set your overclocking in bamt.conf properly.  please double check it.

you have to set core clock to 1000 for a 5830 to have 320MH/s, my 5830s are at 950 core 305MH/s
hero member
Activity: 626
Merit: 500
Mining since May 2011.
files, still does not run. I think the only thing that changed was adding in the bamtpro_id: and do_submitter: a week or so ago when I became a BAMT Pro Member. Commenting out those lines does not fix it either.

Puzzled...


you cannot run submitter and mgpumon on the same machine.  they both need to listen for the same traffic.


Thanks, I figured it was going to be something like that. I moved the Pro config over to a different rig, coldreboot'd the rig that was trying to run mgpumon, it now works again.

But... now I'm having issues with the submitter submitting on the rig I moved it over to. (Even coldreboot'd, double checked bamtpro_id, etc.)

So is it ok to run submitter on one rig, mgpumon with cgsnoop on another rig or are their potential conflicts with all this on the same network segment/subnet? Also, are there dangers of running more than one submitter on the same subnet?

It is OK to run as many mgpumon as you like on a network, but you should only run one submitter.
Otherwise you might get strange graphs in Android app.. it would see multiple samples in same time period..  your farm might get twice as fast suddenly Smiley  Not "dangerous" just not right.

only one process can bind to the listening port required to hear network traffic, that is why you cannot run multiple mgpumon on same machine, or mgpumon + submitter on same machine.

remember that IP subnets don't count as separate networks for BAMT status broadcasts.  It is physical networks that you must think about.  There should be one and only one submitter on each physical network. 

If you have disabled status broadcast, submitter will not function normally.  Did you use directed status anywhere?  That would be a problem. 

cgsnoop should be fine, but only if also in broadcast mode.


Yes, I have the do_bcast_status: 1 on all the rigs.
If for some chance I did run a submitter on a rig, removing the line in bamt.conf and restarting mining does not seem to allow me to run mgpumon after. Maybe the submitter is still bound to the port and restarting mining does not release that?

I now only have 1 submitter per physical network.

I did use do_direct_status: (my external ip) from a remote site, port forwarded into my main mgpumon rig so I could have full farm visibility. Is that something I should not do if I have a submitter running on that physical network (separate location) as well?
hero member
Activity: 616
Merit: 506
After you boot BAMT for the first time and you're at the GUI, does it say anything in the top right of the screen under GPUs Detected: ?

Thanks for the quick reply!
Yeah, it does.
It says:
GPUs Detected:
0 01:00.0 ATI Radeon HD 5800 Series

Hang on...it's doing something now, but I still can't get into CCC or AMD Overdrive Ctrl
It appears to be hasing at around 247Mh/s, which seems awfully low.

dunno why you cant, but you dont need to get into amd overdrive ctl or ccc or any of that. 

everything you need is right in the bamt.conf file.

edit it properly, restart mining.  that is all.

you should be getting 310 to 320 mhash with 5830.  it sounds like you did not set your overclocking in bamt.conf properly.  please double check it.
full member
Activity: 155
Merit: 100
After you boot BAMT for the first time and you're at the GUI, does it say anything in the top right of the screen under GPUs Detected: ?

Thanks for the quick reply!
Yeah, it does.
It says:
GPUs Detected:
0 01:00.0 ATI Radeon HD 5800 Series

Hang on...it's doing something now, but I still can't get into CCC or AMD Overdrive Ctrl
It appears to be hasing at around 247Mh/s, which seems awfully low.
sr. member
Activity: 303
Merit: 250
Hi All,
Just started running BAMT for my first additional mining rig.
It will run headless out in my shop, once I get it up and running.
I have BAMT installed and configured, mostly.
The one thing it won't do is actually mine.
If I try to run the catalyst control center, I get an error saying that "No ATI graphics driver is installed..."
What causes this?
I'm running a HD 5830 card.
I've searched a bit, but can't find anything about that error.
It seems like BAMT is supposed to come with the drivers pre-installed?
Please help, I'm a total noob to linux and don't know where to start.

when you look at the desktop screen do you see your vga in the top right corner? if you don't go to root terminal (in the "start menu") type:
Quote
aticonfig --list-adapters
you should see it there, if you do everything is alright just go to bamt config (start menu) edit /etc/bamt/ pools follow the instruction and type your pool, then edit /etc/bamt bamt.conf read the instructions carefully and config your miner and GPUs, then go to bamt control-> restart mining sessions

Done
hero member
Activity: 626
Merit: 500
Mining since May 2011.
Hi All,
Just started running BAMT for my first additional mining rig.
It will run headless out in my shop, once I get it up and running.
I have BAMT installed and configured, mostly.
The one thing it won't do is actually mine.
If I try to run the catalyst control center, I get an error saying that "No ATI graphics driver is installed..."
What causes this?
I'm running a HD 5830 card.
I've searched a bit, but can't find anything about that error.
It seems like BAMT is supposed to come with the drivers pre-installed?
Please help, I'm a total noob to linux and don't know where to start.

After you boot BAMT for the first time and you're at the GUI, does it say anything in the top right of the screen under GPUs Detected: ?
full member
Activity: 155
Merit: 100
Hi All,
Just started running BAMT for my first additional mining rig.
It will run headless out in my shop, once I get it up and running.
I have BAMT installed and configured, mostly.
The one thing it won't do is actually mine.
If I try to run the catalyst control center, I get an error saying that "No ATI graphics driver is installed..."
What causes this?
I'm running a HD 5830 card.
I've searched a bit, but can't find anything about that error.
It seems like BAMT is supposed to come with the drivers pre-installed?
Please help, I'm a total noob to linux and don't know where to start.
hero member
Activity: 616
Merit: 506
Mother went ahead on wrote me a noOCGPU0 file, happened before, will happen again untill my risers get here, the card in question is sitting over a rather hot northbridge of the mobo. Somehow the file came out as a read only, I couldnt delete it. chmod 777 noOCGPU0 did not work, after a reboot the file was deleteable tough, wonder what caused this ?

This happens when the filesystem isn't closed properly (and on really bad crashes like the ones where mother has to reboot the rig, its not uncommon).  On next boot it is mounted read-only. 

Sometimes it fixes itself on the boot after that.  Sometimes you have to stick the key in a Windows machine, "Safely Eject" it, and then it will be fine.

Best solution: quit locking up your rig Smiley

hero member
Activity: 616
Merit: 506
files, still does not run. I think the only thing that changed was adding in the bamtpro_id: and do_submitter: a week or so ago when I became a BAMT Pro Member. Commenting out those lines does not fix it either.

Puzzled...


you cannot run submitter and mgpumon on the same machine.  they both need to listen for the same traffic.


Thanks, I figured it was going to be something like that. I moved the Pro config over to a different rig, coldreboot'd the rig that was trying to run mgpumon, it now works again.

But... now I'm having issues with the submitter submitting on the rig I moved it over to. (Even coldreboot'd, double checked bamtpro_id, etc.)

So is it ok to run submitter on one rig, mgpumon with cgsnoop on another rig or are their potential conflicts with all this on the same network segment/subnet? Also, are there dangers of running more than one submitter on the same subnet?

It is OK to run as many mgpumon as you like on a network, but you should only run one submitter.
Otherwise you might get strange graphs in Android app.. it would see multiple samples in same time period..  your farm might get twice as fast suddenly Smiley  Not "dangerous" just not right.

only one process can bind to the listening port required to hear network traffic, that is why you cannot run multiple mgpumon on same machine, or mgpumon + submitter on same machine.

remember that IP subnets don't count as separate networks for BAMT status broadcasts.  It is physical networks that you must think about.  There should be one and only one submitter on each physical network. 

If you have disabled status broadcast, submitter will not function normally.  Did you use directed status anywhere?  That would be a problem. 

cgsnoop should be fine, but only if also in broadcast mode.

hero member
Activity: 910
Merit: 1000
Items flashing here available at btctrinkets.com
Mother went ahead on wrote me a noOCGPU0 file, happened before, will happen again untill my risers get here, the card in question is sitting over a rather hot northbridge of the mobo. Somehow the file came out as a read only, I couldnt delete it. chmod 777 noOCGPU0 did not work, after a reboot the file was deleteable tough, wonder what caused this ?
hero member
Activity: 626
Merit: 500
Mining since May 2011.
What is the best way to troubleshoot mgpumon not running? It had been running for weeks in a putty console on my win 7 workstation/gaming system, I needed to reboot so I hit q to exit mgpumon, then typed exit to close the session. I rebooting my Win 7 system and when I connected via putty, gpumon works fine, but mgpumon (mgpumon /etc/bamt/mgpumon.conf) just clears the term window and goes back to the prompt. It wigs out the console too, like you can't see what you type anymore. Very strange. I did try restarting that rig, but it still will not run even after power cycle. I went to the console on the rig itself and try to run it from the GUI, but when you try to start it from the menu, it just pops the console window and closes. I tried looking in /var/log/bamt.log but no errors if you tail it and try to launch it from another term window.

Just to rule out a going bad USB stick, I also wrote a fresh image on a new USB stick, copied over my config files, still does not run. I think the only thing that changed was adding in the bamtpro_id: and do_submitter: a week or so ago when I became a BAMT Pro Member. Commenting out those lines does not fix it either.

Puzzled...


you cannot run submitter and mgpumon on the same machine.  they both need to listen for the same traffic.


Thanks, I figured it was going to be something like that. I moved the Pro config over to a different rig, coldreboot'd the rig that was trying to run mgpumon, it now works again.

But... now I'm having issues with the submitter submitting on the rig I moved it over to. (Even coldreboot'd, double checked bamtpro_id, etc.)

So is it ok to run submitter on one rig, mgpumon with cgsnoop on another rig or are their potential conflicts with all this on the same network segment/subnet? Also, are there dangers of running more than one submitter on the same subnet?
Pages:
Jump to: