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 ?
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.
