[BAMT] GPU Disappears???

[ilaurens]

Hi,

I am currently using BAMT 1.2. I have a problem with my 2x r9 card. The problem is when I start the miner, it'll work for a few mins ~ when the temperature is on a good number 85 oC something like that. The second card disappears. Also I have noticed that GPUMON and via webinterface both of them often disappears then reappears after refreshing.

Can someone give me pointers or did anyone of you have the same problem?


http://puu.sh/5LzTS.png


Thanks ~

[ilaurens]

I noticed it will still mine in the backgrounds with both speeds. However 0 will show only and 1 will disappear. I want to be sure regarding temps. I do not know how it'll acts to I can't trust it unfortunately.

[mousebat]

This happens with me - I've got MSI R9 290's and running litecoin bamt 1.2.

It's almost as if occasionally the api get's blocked or something. Either one or both of the cards disappears from gpumon and the web gui

Very strange - wish I knew how to fix it

[phy6]

This happens with me - I've got MSI R9 290's and running litecoin bamt 1.2.

It's almost as if occasionally the api get's blocked or something. Either one or both of the cards disappears from gpumon and the web gui

Very strange - wish I knew how to fix it

It's happening to me to, with BAMT 1.2/NotSMOS.  I'm using two Gigabyte R9 290's.

Sometimes the web interface will drop to 0 and show neither card, and sometimes the browser will just refresh to programming jibberish with the error:
"Can't use an undefined value as a Hash" and then it complains about not being able to write to a death log file because of file permissions.  ANd 10 seconds later it will autorefresh and show one or both cards running.

LXTerminal is also flakey for me, usually it's the second card (GPU 1) whose entire column disappears, and then when it does reappear it's full of hash rates, like it was being recorded the entire time.

[zeddy]

After a lot of digging, I've found what I think is a bug in BAMTs monitoring perl script.

I noticed the clock speed on my R9 290 fluctuates (DISPLAY=:0.0 /usr/local/bin/atitweak -s), and sometimes outputs a decimal MHz value.

Theres a regex inside /opt/bamt/common.pl (search for "monster"), that tries to match the clock speed as an integer value. When its not an integer value, the regular expression fails and the function returns no GPU's.

An easy fix is to replace the (\d+) section with (.)

[figjam]

After a lot of digging, I've found what I think is a bug in BAMTs monitoring perl script.

I noticed the clock speed on my R9 290 fluctuates (DISPLAY=:0.0 /usr/local/bin/atitweak -s), and sometimes outputs a decimal MHz value.

Theres a regex inside /opt/bamt/common.pl (search for "monster"), that tries to match the clock speed as an integer value. When its not an integer value, the regular expression fails and the function returns no GPU's.

An easy fix is to replace the (\d+) section with (.)

zeddy is right that this is the cause of the problem, but that regex modification didn't work for me.  What you can do is go to that area by searching for monster, then find the capture group (\d+) after engine\sclock\s.  Change it from (\d+) to (\d+\.*\d+) .  This will match properly for both digits and digits with a decimal.

After this change, you shouldn't see GPUs disappearing from the BAMT web interface any longer.  Hope this helps someone.

[infinitybo]

@Ilaurens Not necessarily the same probleme however you should use the "mining" section.

[Fiftyways]

Hi,

I had the same issue with my second R9 290x GPU. Both were actually mining (as reported by the hash rate measured by the pool where I subscribed), but the second board was not monitored by gpumon.
 
The change from (\d+) to (\d+\.*\d+) worked perfectly fine for my rig.

Thanks to all contributors, very skilled guys !