@Qiset I didn't like the way that model information was presented to me so I did some checking.
Your first assessment is correct, I think. The model B is not a model 2 even though it has a rev 2 listed. Time to do a head slap.

Thanks guys - I managed to create another SD card image and used an SD reader to access the faulty one so at least I've rescued all my content!

@curplunk said in Issues with fresh install:

If I restart with both joy sticks plugged in it boots to a setting screen and not one, I can configure the 2nd stick. Thoughts?

Assuming the joysticks are identical (same model), configuring the 1st would automatically configure the 2nd one - the configuration is associated with the joystick name, so they would share the same configuration. Did you properly exit EmulationStation after configuring the 1st joystick ?

Also, what key do I set for coins/adding more lives?

That's bound to the Select button.

@mitu yeah i saw that on the raspberry pi fourms. I set it to that already, and nothing happened.

@thesterninator a usb flash drive should not cause power issues. And seriously start fresh. It will teach you how the whole RetroPie system works.

@quicksilver hdmi_enable_4kp60=1 works fine :)

pi@retropie:~ $ ./checkPi.sh OVERCLOCK: core: frequency(1)=549993152 v3d: frequency(46)=750001472 arm: frequency(48)=2100515584 FIRMWARE VERSION Feb 4 2020 12:06:47 Copyright (c) 2012 Broadcom version 53597a93bd1906c9358277b08bff097299216004 (clean) (release) (start) OS VERSION Linux retropie 4.19.93-v7l+ #1290 SMP Fri Jan 10 16:45:11 GMT 2020 armv7l GNU/Linux

l8r I'll check some performence ...btw if ur having a good cooling system force your games to run at governer mode.

quoted by buzz
"If you want to set the performance governor when running games, that is already supported
https://github.com/RetroPie/RetroPie-setup/wiki/runcommand
(It sets it on game start, and restores previous setting on game exit)"

@john need more information

Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

@goferffxi said in "_M_construct null not valid" upon bootup, started after a year of no issues.:

@mitu said in "_M_construct null not valid" upon bootup, started after a year of no issues.:

@WhackAMole said in "_M_construct null not valid" upon bootup, started after a year of no issues.:

Any chance someone could translate this fix in to layman's for a newbie?

The only applicable advice in the above topic is

uninstall es dev, reinstall regular binary

Try re-installing your EmulationStation package, either from binary or from source.

So,, I tried the advice here from both Binary and source. I even removed all exp packages just to ensure it wasn't anything in there. The error still appears and now i've decided to attempt a complete rebuild from Raspbian up. I am also increasing SD capacity from 16gb to 32 GB to ensure space isn't an issue.
So, I did a basic install and then removed all main packages then proceeded to reinstall the main packages from source. See what happens there

@Clyde said in External Boot in my image:

@MPlay Thank you for sharing your solution.

you are welcome, my next step is set retropie to stream my game play (if possible in net play mode) in my youtube channel.

thank you and other friends for support.

Tnx @mitu .
I cheched that link but my issues seems to link to remove slice system-ifup.slice problem.
(no timer appears and Pi 3 shutdown immediately)

Reporting Progress Update...
Got the hard drive working and the skin changes in place. My buttons don't work yet, but the LED does. I just need to get the button scripts installed (POWER and RESET). I will say this.. I think I know what caused the corruption. The PiStation build I'm doing has a microSD card ribbon cable, to make access the the SD card external. When I screwed the top down on my case, I crushed one of the wires in the ribbon between the screws. During all of my re-building today, I kept it simple without using that cable. Everything now works right. I tried hooking up the cable again, and sure enough, I get filesystem read/write errors on my screen. So I've ordered a replacement. Cheap enough, but coming from Taiwan so it might take a couple weeks. The other thing I noticed... since the POWER and RESET buttons aren't working yet, I've had the power going straight into the Pi. I've had ZERO undervoltage warnings flash up on my screen. BUT, once I put the Mausberry circuit into the mix, all of a sudden those lightning bolts started showing up. So I don't know if I have a faulty circuit, of it maybe the circuit isn't capable of supporting the volts/amps. I need to try and get in touch with them and see if they can recommend a solution.

As an aside, but related question.. Does the "Powerblock" people use work in a similar fashion? Detecting a button push then sending a signal to the Pi to shut down, then cutting out the power? If so, maybe it can handle the power?

@shizmartelpi Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first (as agreed when registering).

Pi Model or other hardware: 3
Power Supply used: CanaKit 2.5A Micro USB Power Supply with Noise Filter
RetroPie Version Used 4.2
Built From: Flashed retropie to work through Jessie, made a disc image copy to place onto new (not working) micro sd
USB Devices connected: keyboard, ps3 controller (via bluetooth)
Controller used: ps3
Error messages received: none - system stops during boot
Log found in /dev/shm/runcommand.log (if relevant):
Guide used: youtube install instructions
File:
Emulator:
Attachment of config files:
How to replicate the problem: plug in retropie to turn it on. system stops during boot process.

@isrnick said in Emulationstation crashes after RetroPie boots up - Permission denied:

@mitu But the keyboard is disabled when it crashes, so you can't type the commands to even open raspi-config to be able to enable SSH.

Sometimes, I can free the keyboard by pressing Alt+PrtScr/SysRq+R simultaneously. It's a Linux Magic SysRq key combination that switches the keyboard from raw mode, which graphical programs tend to use, to XLATE mode. May be worth a try.

Note that on some keyboards, Laptops etc. the key combination is slightly different. See the link above for the variations.