Attract mode shuts down automaticaly on RPi3

[Roverius]

I run the Attract mode on Raspbeey Pi3 and all works fine (well most of it)

I use the MAME2010 test inveronment to let some roms work.

BUT, when the screensaver is on, then suddenly after a unknown time, the attract mode exits to the prompt in text-mode.
I have to restart "xinint attract" to run the attract mode again.

Is this due to the usage of mame2010 or is it due to Attract Mode?
Or is it a auto-shutdown due to long time inactivity?

[Roverius]

Ok,

I noticed that the screensaver froze and the green led was on fixed.
After a while it went to text-mode (shutted down x-server) and the temp was 57° CPU and 58°GPU

Is that to hot or is that normal?

[Finhead]

I run the Attract mode on Raspbeey Pi3 and all works fine (well most of it)

I use the MAME2010 test inveronment to let some roms work.

BUT, when the screensaver is on, then suddenly after a unknown time, the attract mode exits to the prompt in text-mode.
I have to restart "xinint attract" to run the attract mode again.

Is this due to the usage of mame2010 or is it due to Attract Mode?
Or is it a auto-shutdown due to long time inactivity?

I have had AM installed on my RPi3 for about 2 weeks and it has been on 90% of that time testing, running mame4all and Daphne. I have never had it lock up or shutdown other than when I tried to run a ROM it didn't like.
Mine gets up to 78 deg when running grid screen saver for Daphne so I don't think it's due to heat either.
I would suspect mame2010 or maybe just a corrupt img.

[omegaman]

If you have a thermal problem you should see a yellow square in the top right corner on the pi.

I don't think attract is the problem. But, of course that doesn't explain what happen while in screensaver mode. As you know mame2010 is experimental so there's that.

The pi does have a power save mode, so that might have caused a glitch but who knows. 

Try to disable screen blanking by editing /usr/bin/setterm

Place this line before exit 0
 
 -blank 0 -powerdown off
 

[Roverius]

the same problem happens with emulationstation.
So i think it has nothing to do with attract mode.

I installed a new image and did a manual compile of attract mode instead of the pre-made image.

I also will have a look at the powersave mode.

i keep you updated.

[Roverius]

If you have a thermal problem you should see a yellow square in the top right corner on the pi.

I don't think attract is the problem. But, of course that doesn't explain what happen while in screensaver mode. As you know mame2010 is experimental so there's that.

The pi does have a power save mode, so that might have caused a glitch but who knows. 

Try to disable screen blanking by editing /usr/bin/setterm

Place this line before exit 0
 
 -blank 0 -powerdown off

I made setterm with the option -blank 0 -powerdown 0 -powersave off

i will let it run overnight and see what happens on a new installe retropie with AM compiled
i let it run on emulationstation, because ES did also crash back to prompt.

[Roverius]

Update,

Overnight test was OK.
System did not crash back to prompt.
Test test was running a game in MAME
AM was not setup properly.
I will setup AM with paths and folders etc.. and robospin as the  FrontEnd.

one difference is, the crash happened on Retropie V3.7
Now i test with Retropie v3.6

[fbs777]

Just happened here a few minutes ago. It was in screensaver and then after a few minutes it crashed.
Now is running again in screensaver mode and no problem after more than 30 minutes.
Im using the Floob's v.02 image ( http://forum.attractmode.org/index.php?topic=705.0 ) with the newest robospin layout

The output error:
 

Code: [Select]

AL lib: (EE) ALSAProc: mmap commit error: Broken pipe

[fbs777]

Ok, now i know this is something to do with the rom video file, but i still not sure if its because of the size in MB or the video quality.
 And dont need to wait the screensaver, just crash if you go to the rom in the list and try to see the video to play until the end.

This is an example of video working fine:
size: 2,7MB
video :320 x 240, codec H.264 (High Profile), 30fps, 520 kbps
audio: MPEG-4 AAC, stereo, 48000 Hz, 64 kbps

this is an example of video crashing the AM: (from a megadrive rom, but you can rename it to test http://www.4shared.com/video/i7OS-hKGba/Gunstar_Heroes__Europe_.html )
size: 5,0MB
video :612 x 464, codec H.264 (Baseline Profile), 30fps, 3390 kbps
audio: MPEG-4 AAC, stereo, 44000 Hz, 124 kbps

another one crashing the AM: (from a megadrive rom, but you can rename it to test http://www.4shared.com/video/oixiVb78ba/Thunder_Force_IV__Europe_.html )
size: 11,9MB
video :612 x 464, codec H.264 (Baseline Profile), 30fps, 4832 kbps
audio: MPEG-4 AAC, stereo, 44000 Hz, 125 kbps

Oh, btw, im using the Raspberry Pi 2.

[progets]

fbs777,

I had this issue when I used videos from my HyperSpin build. I resolved this issue by downloading lower resolution videos from emumovies.com (a subscription might be required).

I think the problem has to do with hardware acceleration not being enabled. There have been a bunch of posts of people trying to overcome this by using ffmpeg with hardware acceleration but there seems to be little success due to the changes that happened moving from Wheezy to Jessie and the ffmpeg dependency files.

[Roverius]

After few tests, AM v3.6 AM v3.7 on RPi2 and RPi3, still crash while in screensaver mode.

I changed settings now like:

Keep Aspect Ratio = Yes
Collage = No
Sound = Off

Will see what happens

The Vid files are from Emumovies, but i have a mix from MP4 and FLV files.

[Floob]

Are your vids 240p (SQ) or 480p (HQ) from emumovies?

[omegaman]

Without HWaccel enabled only SQ videos will work. Of note, I'm using SQ 240P snaps from emumovies without issue. I tested screensaver mode without issue as well.

[Omamez]

I have experienced reboot 2 times today while adding roms and snaps etc just random rpi3 cpu temp 104

[Floob]

Thats pretty hot - are you running SQ videos - and are you overclocking?
Maybe try a heatsink.