Log In
Home
Topic RSS
3:33 pm
Ken
January 21, 2018
Offline
I installed this great Nintendo image and using a Pi 3 Model B, and happened to notice the CPU temp really climb quickly where it was showing the thermometer on screen while in emulationstation. It appears to drop while in a game or emulator. I suspect it has to do with the audio and video goin on in the theme.
The case I'm using is a basic one without a fan for silent operation. Even with the top cover removed, it still overheats.
Has anyone else experienced this issue, or have any recommendations on how to address it?
4:03 am
Arcade Punk
February 9, 2018
Offline I have MadLittlePixels 128 attract mode on mine.. I used it a bit and when i was trying some N64 stuff it locked up.. the heatsink was so hot i couldnt hold my finger on it.. I am brand new to this (Pi) so no idea on heat and such.. but unless i have a bad PI mine seemed to lock up on N64 games.. I have a fan on the way. But i too am concerned. I got mine in a kit from Amazon with everything (case, board, PSU cord)Â so not sure if i need to replace or?
2:06 pm
April 14, 2017
Offline i assume you are both overclocked or running over clocked images and possibly unaware the image is doing so?
that could be the biggest factor in your overheating aside from any cases you are using not allowing the heat to dissipate adequately.
the PI3b i have in my cab has no heat sinks, no case just velcro'd underneath the control panel to hold it in place and ive not experienced any of these issues even on the few n64 games that "play"
try backing the clocking speed down until you see an acceptable operating temp, or set back to factory clocking to help you alleviate the issues, or you could always "invest" in cooling
2:11 pm
Ken
January 21, 2018
Offline AS it turns out, this NES image has a bluetooth.sh script being invoked that appears to be continually searching for controllers. Running 'top' confirmed there was a bsh process consuming considerable CPU. I tracked down the offending script from the process ID and looking at the /proc/$PID$/cmdline file and located the offending script. Disabled the script, and everything is great now.
6:18 am
Ken
March 2, 2018
Offline Thanks for the heads up! Can you provide a little more info? Where is the script located, and what exactly did you do to disable it? Thanks for the help.
5:37 am
Ken
March 2, 2018
Offline I was able to resolve this via the Front End. I went to Config -> Bluetooth -> Configure bluetooth connect mode. Then I changed it to the boot option (Connect to devices once at boot). I no longer see the script in the 'top' output. Thanks again for finding this one.
1 Guest(s)
