|
Card Manufacturer: AMD
Card Model Number: HD 5870
Card OEM: ATI
MHash per Second: 458MHS
Core Clock: 1010MHZ
Memory Clock: 294MHZ
Average Operating Temperature: 62C
Ambient Temperature: 22C
Fan Speed: 50%
Host OS: Bamt 0.5
Driver Version: 11.6 and SDK 2.4
Mining Program: Phoenix
Command Line Flags/GUIminer Settings: BFI_INT VECTORS, FASTLOOP=false AGGRESSION=10
Watts Drawn While Mining: Unknown
Other Information: kernel phatk2, core voltage 1.7
Record stable uptime at current settings 8d (and counting).
|
|
|
|
I'd like to report a stability issue in bamt 0.5a:
Using the exact same settings as I did in the latest 0.4 version I cant get the only rig I have tried Bamt 0.5 in to remain stable, as Im writing this im writing the 0.4 Image back to my usb-stick.
The rig contains one 5870, the clocks Im running are core 970, stock voltage, mem clock at 300. Im using phoenix miner, kernel params BFI_INT VECTORS FASTLOOP=false AGGRESSION=8 (8 because im pointing it at P2pool). Every time (twice so far) that I head out to work or to sleep I come back to find the rig has hung up, wont respond to anything or cant get any imange on it's display.
What other relevant information can I post to help identify the issue ?
I really don't know. 0.5 is the same mining software, same overclocking software, same drivers, same SDK.... I have no idea why or how it would behave any differently in 0.5 than it did in 0.4. It is the same software. Also on a sidenote the exactly same rig, with the exact same setup Is providing a slightly higher Mhs (according to GPUmon) in bamt 0.4. Were talking 1% here, 2-5mhs more, GPUmon has always shown slight variance between ticks to me. Currently it's hashing away at 432.25-439.9 Mhs. Edit: It just occured to me that theres one difference in the setup. In 0.4 I use phatk, where as in 0.5 I used the reccomended phatk2. Any toughts on this ? *sigh...* a note to anyone reading this PLEASE do not tell me "the exact same thing that works on X doesn't work on Y" if you aren't doing the exact same thing. I cannot help you without accurate information. Even worse, inaccurate information leads to bad conclusions that can effect the support other people get. So far, the only repeatable and verified "issues" with 0.5 have been: 2 cases of people not realizing that the pound sign is a comment in Linux 2 cases of typos 1 case of unknown reason but that went away after installing fix #1. (and a verified broken fixer, which is indeed a pretty silly bug to have) (PS - This is out of hundreds of downloads) I understand that it is frustrating when things don't work, but I just cannot guess at what you may have changed and not mentioned. Anyway.. more to the point, of course if you change kernels you will very often see a variance in hash rate and very possibly cause instability. Changing kernels can be a drastic move when you are teetering on the edge of crashing your cards anyway. Each kernel will have a different heat to performance to stability ratio. phatk2 is generally accepted as the best kernel to use for most GPUs. However, it may not be the best for every combination of GPU and clock rates. Also, you may have to adjust your clock rates to get the best performance out of a new kernel. You cannot just drop a new kernel in and expect it to have the same characteristics or work very well without tuning your GPUs for it! I understand it's frustrating getting mislead with innaccurate reports and do apologize for mine. I assure you I triple checked the configs in comparison before posting, but sadly it was only while sitting on the toilet that the difference of configurations occured to me. That phatk2 kernerl was the only real incentive I had to swap out from 0.4, guess Im going to stick with it for the time being. Imho you need to understand or appreciate the fact that a fair amount of the ppl using or even considering using Bamt migth be next-to illiterate when it comes to linux, myself for one. Up to until fairly recentley I have found bamt to be slightly easyer to use than P2pool for example ,which I managed to eventually do. For your software to be more-wideley used and your support donations to grow alongside it you propably should make attempts at making setting things up and using it easyer, here are my two bitcents on the issue: -We like dropbox style menus, we like mouse tooltips giving us hints, we'd propably love invalid syntaxes in configs to "magically" turn red and start blinking or something. -We (and you) might benefit from being discouraged on installing new versions among the first users. |
|
|
|
I'd like to report a stability issue in bamt 0.5a:
Using the exact same settings as I did in the latest 0.4 version I cant get the only rig I have tried Bamt 0.5 in to remain stable, as Im writing this im writing the 0.4 Image back to my usb-stick.
The rig contains one 5870, the clocks Im running are core 970, stock voltage, mem clock at 300. Im using phoenix miner, kernel params BFI_INT VECTORS FASTLOOP=false AGGRESSION=8 (8 because im pointing it at P2pool). Every time (twice so far) that I head out to work or to sleep I come back to find the rig has hung up, wont respond to anything or cant get any imange on it's display.
What other relevant information can I post to help identify the issue ?
I really don't know. 0.5 is the same mining software, same overclocking software, same drivers, same SDK.... I have no idea why or how it would behave any differently in 0.5 than it did in 0.4. It is the same software. Also on a sidenote the exactly same rig, with the exact same setup Is providing a slightly higher Mhs (according to GPUmon) in bamt 0.4. Were talking 1% here, 2-5mhs more, GPUmon has always shown slight variance between ticks to me. Currently it's hashing away at 432.25-439.9 Mhs. Edit: It just occured to me that theres one difference in the setup. In 0.4 I use phatk, where as in 0.5 I used the reccomended phatk2. Any toughts on this ? |
|
|
|
|
I'd like to report a stability issue in bamt 0.5a:
Using the exact same settings as I did in the latest 0.4 version I cant get the only rig I have tried Bamt 0.5 in to remain stable, as Im writing this im writing the 0.4 Image back to my usb-stick.
The rig contains one 5870, the clocks Im running are core 970, stock voltage, mem clock at 300. Im using phoenix miner, kernel params BFI_INT VECTORS FASTLOOP=false AGGRESSION=8 (8 because im pointing it at P2pool). Every time (twice so far) that I head out to work or to sleep I come back to find the rig has hung up, wont respond to anything or cant get any imange on it's display.
What other relevant information can I post to help identify the issue ?
|
|
|
|
Frankfurt in Germany is a good and relax place to ship parcels...
Does this mean that you have a way to ship Eu-customers with our customs seeing the package originating from within the Eu ? ...and if not then what do you mean by this ? |
|
|
|
|
I can confirm that the workaround to apply the patch works and that the patch resolves the Oc issue.
|
|
|
|
Just found it myslef, I really dislike the way this forum works  |
|
|
|
Im back to square one: the usb-stick problem is gone.
bamt.conf wont apply overclocking, the values set are known stable clocks for this particular card. The card in question is a 5870, core voltage 1.16 core clock 970.
My workaround to this is to stop mining and run:
atitweak --set-core-voltage=1.16
atitweak --set engine-clock=970
And then restart mining.
Would you mind doing this to confirm bamt is understanding your config: while mining, in a root shell or from ssh, type: pcontrol press d press f press enter you will see a screen like this:  Make sure the O/C info (shaded purple in shot above, but won't be in real life) matches what you set in bamt.conf use up down arrow to check all your GPUs let me know On my test rig I run pcontrol, hit d and then f and it bombs out like this. BAMT miner1Exception in thread Thread-1:
Display GPUs Pools CoTraceback (most recent call last):
File "/usr/lib/python2.6/threading.py", linCurrent Pool: pit.deepbit.net
self.run()
Hash: 305.334 Mh/s Pools File: /etc/bamt/pools File "/opt/bamt/pcontrolADLT.py", liPool Strategy: priority failover
A/R: 98/0 Kernel: phatk2f.scr.addstr(top + x,rt, ("%" + s Rej: 0.00% "s") % " ") Kernel Params: BFI_INT VECTORS FASTLOOP=false AGG..
Stat: got error: addstr() returned ERR
Que: 0/0
Dlay: 164ms miner1
Eff: 33.3% pcontrol is still very alpha, not intended for normal use at all. try making window bigger, sometimes it gets confused. Sorry for the delayed reply, I was at work. When I run /opt/bamt/fixer I get a message "One of the BAMT tools has suffered a fatal error. Not a GLOB reference at /usr/share/perl/5.10/IO/Zlib.pm line 559 |
|
|
|
|
Im back to square one: the usb-stick problem is gone.
bamt.conf wont apply overclocking, the values set are known stable clocks for this particular card. The card in question is a 5870, core voltage 1.16 core clock 970.
My workaround to this is to stop mining and run:
atitweak --set-core-voltage=1.16
atitweak --set engine-clock=970
And then restart mining.
|
|
|
|
And now it would appear that coldreboot killed my usb-stick.
Unplug and re-insert. See if that helps. I have that happen sometimes on a few rigs. Did that using a different usb port, that did not resolve it. |
|
|
|
|
And now it would appear that coldreboot killed my usb-stick.
edit: Rewriting bamt to the stick atm
edit2: manages to boot up, stick is not dead.
|
|
|
|
Trying to set this up on rig#1
Problems so far: I cant get any overclocking in with bamt.conf. I was able to do some overclocking with AMDOverdrive Ctrl, but Im nowhere near what this particular card can do, it wont let me push the core clock past 900Mhz. I have set up all (3) the core_speeds at 970Mhz, tried only setting one dosent seem to make any difference.
Other than that everything looks fine.
I have been having issues too. What does it say on your http://YourMinerIP/ compared to what you set in bamt.conf? On my (3) 5850 GPU test rig that was doing 1120 Mhash/s under 0.4 is doing around 860 Mhash/s on 0.5 no matter what I put in for the 3 core_speed_X or mem_speed_X, it's like stock speeds only. I'm going to try another single 5850 GPU rig now. Have you checked that oc hasn't been disabled by mother? Not running .5 yet but I'd think this would be included https://bitcointalk.org/index.php?topic=28967.msg755770#msg755770Nope the file mother creates is not there. |
|
|
|
|
I found a workaround to the problem, but it's not pretty:
in root terminal: atitweak --set-core-voltage 1,16
(thats the card's stock voltage)
and: atitweak --set-engine-clock=970
Hashing away at normal rate now.
I'd still like to find out why I can only control the fanspeed from bamt.conf
|
|
|
|
|
Trying to set this up on rig#1
Problems so far: I cant get any overclocking in with bamt.conf. I was able to do some overclocking with AMDOverdrive Ctrl, but Im nowhere near what this particular card can do, it wont let me push the core clock past 900Mhz. I have set up all (3) the core_speeds at 970Mhz, tried only setting one dosent seem to make any difference.
Other than that everything looks fine.
|
|
|
|
|
I almost just bought a nice bitcoin T-shirt off this site:
Price of shirt and delivery to my neck of the woods: 16,95$ (ok decent enough)
But when I pay with bitcoins (OFC!) and check the price compared to current mtgox traderate: 30,96$.
Nuff said.
|
|
|
|
I have a problem I assume is caused by the latest update. Is there any way for me to do a rollback or do I need to do a complete "reinstall" ?
..and btw the problem is 70 or so missing mhs on one of my cards, 5870 @ core 1020Mhz, mem 300, and core voltage: 1.17 I used to get a solid 445Mhs out of this, now its pushig our 373Mhs.
To me it would seem like a problem applying the overclock.
My other 5870, that dosent clock asfar isnt showing any Mhs loss.
there is no "roll back". it would help if you were specific about what is meant by the "latest" update.. do you mean #31? no update has changed the over clocking code in some months, so this would be strange. did you verify that the card is getting the correct settings using atitweak? are you sure you didn't break something in the config file? Aye, #31 I cant find atitweak (sorry, im clueless with Linux) .. however I found AMDOverdriveCtrl and it's telling me that Im running a core clock of 850mhz and stock voltage (1.125) Im fairly sure nothing's broken in the config file (triple checking atm) It sounds like BAMT has disabled overclocking on that GPU because it locked up. You need to reduce your overclocking settings. Then, remove the control file that is preventing overclocking. It will be in /live/image/BAMT/CONTROL/ACTIVE ps... to use atitweak just type: atitweak You were correct on BAMT disabling the Oc. I managed to delete the file and the card is running as usual. I did type atitweak, didnt get a response, tried atitweak -help ... turns out -h is better Will adding: "detect_defunct: 0" to the settings part of bamt.conf prevent this from heppening again ? ..also Im fairly sure me messing around on the running rig caused the crash, those clocks on that rig have had a record uptime of 8 days (and even then it was me that chose to reboot it) Also thank you for your help. turning off detect_defunct will prevent BAMT from recovering from a locked up GPU, yes. It won't prevent the GPU from locking up, and without detection and recovery the machine will simply sit there locked up if it happens. Your call. 8-day uptime says to "kill this feature with fire" imo, once again thank you for your time. |
|
|
|
I have a problem I assume is caused by the latest update. Is there any way for me to do a rollback or do I need to do a complete "reinstall" ?
..and btw the problem is 70 or so missing mhs on one of my cards, 5870 @ core 1020Mhz, mem 300, and core voltage: 1.17 I used to get a solid 445Mhs out of this, now its pushig our 373Mhs.
To me it would seem like a problem applying the overclock.
My other 5870, that dosent clock asfar isnt showing any Mhs loss.
there is no "roll back". it would help if you were specific about what is meant by the "latest" update.. do you mean #31? no update has changed the over clocking code in some months, so this would be strange. did you verify that the card is getting the correct settings using atitweak? are you sure you didn't break something in the config file? Aye, #31 I cant find atitweak (sorry, im clueless with Linux) .. however I found AMDOverdriveCtrl and it's telling me that Im running a core clock of 850mhz and stock voltage (1.125) Im fairly sure nothing's broken in the config file (triple checking atm) It sounds like BAMT has disabled overclocking on that GPU because it locked up. You need to reduce your overclocking settings. Then, remove the control file that is preventing overclocking. It will be in /live/image/BAMT/CONTROL/ACTIVE ps... to use atitweak just type: atitweak You were correct on BAMT disabling the Oc. I managed to delete the file and the card is running as usual. I did type atitweak, didnt get a response, tried atitweak -help ... turns out -h is better Will adding: "detect_defunct: 0" to the settings part of bamt.conf prevent this from happening again ? ..also Im fairly sure me messing around on the running rig caused the crash, those clocks on that rig have had a record uptime of 8 days (and even then it was me that chose to reboot it) Also thank you for your help. |
|
|
|
I have a problem I assume is caused by the latest update. Is there any way for me to do a rollback or do I need to do a complete "reinstall" ?
..and btw the problem is 70 or so missing mhs on one of my cards, 5870 @ core 1020Mhz, mem 300, and core voltage: 1.17 I used to get a solid 445Mhs out of this, now its pushig our 373Mhs.
To me it would seem like a problem applying the overclock.
My other 5870, that dosent clock asfar isnt showing any Mhs loss.
there is no "roll back". it would help if you were specific about what is meant by the "latest" update.. do you mean #31? no update has changed the over clocking code in some months, so this would be strange. did you verify that the card is getting the correct settings using atitweak? are you sure you didn't break something in the config file? Aye, #31 I cant find atitweak (sorry, im clueless with Linux) .. however I found AMDOverdriveCtrl and it's telling me that Im running a core clock of 850mhz and stock voltage (1.125) Im fairly sure nothing's broken in the config file (triple checking atm) |
|
|
|
|
I have a problem I assume is caused by the latest update. Is there any way for me to do a rollback or do I need to do a complete "reinstall" ?
..and btw the problem is 70 or so missing mhs on one of my cards, 5870 @ core 1020Mhz, mem 300, and core voltage: 1.17 I used to get a solid 445Mhs out of this, now its pushig our 373Mhs.
To me it would seem like a problem applying the overclock.
My other 5870, that dosent clock asfar isnt showing any Mhs loss.
|
|
|
|
|
Show Posts
