Bump. Ran into this minor problem as well

Hi, they connect just fine when I turn it off and back on if I need to reboot my pi. I just liked the way they always turned off immediately on a reboot using retorpie 4.3. The little hack for connect on boot would reconnect my controllers every time on a reboot without me having to turn them off and on again. But with 4.4 there is some type of delay sometimes that causes them not turn turn off immediately when I reboot (therefore causing problems with the boot "hack").

I just didn't know if there was some kind of script (if that is the right term) that could help assist with the killing of the bluetooth signal when rebooting under 4.4...?

@KnightZ87

Have a look at this article about hdparm! There are many settings you can tweak!

Tune Your Hard Disk with hdparm:
http://www.linux-magazine.com/Online/Features/Tune-Your-Hard-Disk-with-hdparm

You could also set the sleep/standby timer to a longer time!

Change hard drive's sleep/standby mode timer to reduce power consumption:
https://linuxconfig.org/change-hard-drive-s-sleep-standby-mode-timer-to-reduce-power-consumption

Spin Down and Manage Hard Drive Power on Raspberry Pi
https://www.htpcguides.com/spin-down-and-manage-hard-drive-power-on-raspberry-pi/

@Charlie-Scheib

Is there no way within the drive settings itself to keep it spinning on the RetroPie/Pi settings?

I haven't tested this but this might work!
You'll need to do most of this from the command line (difficulty: medium)

There are a couple hard drive power management programs that can be used on the Raspberry Pi to control how long before the hard drive spins down to save power and the life of the hard drive.

I wonder if the program hdparm will work for you. You could set the 'spindown_time =' to something like an hour (720) or 2 hours (1440). You basically find out how long you want measured in seconds and take that number and divide it by 5. So 2 hours is 7200 seconds (7200sec / 5 = 1440).
https://www.htpcguides.com/spin-down-and-manage-hard-drive-power-on-raspberry-pi/

@mitu @cyperghost

I sent an e-mail to RetroFlag the other day describing the issue and from looking at the photo of the wires I sent, they said the colored wires were in the wrong position. They apologized then gave some directions on how to take the wires out and what the proper color order is.

I tried taking them out of the black plug but it seemed a bit of a hassle. Fortunately a replacement case arrived from Amazon today and the colored wires in the replacement case are in the correct position. I rebuilt my RetroPie and the shutdown and reset worked right away :). Thanks again for the help.

tldr: Original case wires were messed up, replacement worked.

@zuuzuu
Hello guys.
I've encountered the exact same problem with ALL f1 games for ps1. 2001 version is unplayable, and others get stuck in the first screen, right after "ea games challenge everything..." Did you guys manage to fix or at least identify the problem?
I tried also an android emulator and got the exact same result.... That's sad, I have plenty of ps1 games on my raspberry, and they all work great...

@mattrixk lol yeah man I'm having fun with it all, made one theme already but working on anither now just couldn't get rid of that text so I could add my own.

I will have to upload my first theme to share soon.
Thanks again.

Wow, that was fast!

Thank you @mitu

Thanks folks for your great advice and quick response. Making the keyboard change in raspi-config worked like a charm. By the way, I highly recommend this nespicase+ case. Thanks again!!!

@D39 Have fun with RetroPie !

@brunozero I have not noticed any issues with exiting mupen64plus on my pi. Please read and answer the questions so we can help you:

https://retropie.org.uk/forum/topic/3/read-this-first

@mitu

You forgot to ask me an important question, "Is there a copy of that image?"

The answer is yes!!! I am now back in business. This time I will pay close attention to what the heck I am changing. This was a great learning opportunity, however, so thank you very much for your support. =)

I have two cards for the sake of clustering, in case you were wondering.

@webodan

EDIT: OK, so I double-checked the md5s of the bios files that i have downloaded BEFORE and AFTER sending them to the pi (just in case they would get corrupted as they were sent or something) they matched on winmd5 just fine.

lr-pcsx-rearmed can use only scph5501.bin from the list of BIOS files you have, and that file has a wrong MD5 in your screenshot - it's not what's in the docs or what the core expects.

Unfortunately I can't get a copy of the game to test, but can you just get a RetroArch log file and put it on pastebin.com - enable Verbose logging in the Runcommand launch menu, run the game for a while, then upload the /dev/shm/runcommand.log log file to pastebin.com and paste the URL here.

@krullbeast said in can udev read i2c and hardwired GPIO buttons simultaneously?:

do you think it is possible to read the i2c data and also the A and B buttons inside of retroarch?

Not an expert on this, but I think RetroArch doesn't read directly from GPIO (I2C or otherwise), instead it uses an established input driver (udev/sdl/etc.) - https://github.com/libretro/RetroArch/tree/master/input/drivers.

@BobHarris

Ok I'll check it out! I'll install it from PuTTY and see if there's any improvement.

I can always reinstall everything and keep going with a clean installation, that should do it as well.

Thank you for your help!

@willcroft said in Kodi Builds on the Pi:

Again, is there a build that runs on RetroPie?

Yes - the official Kodi package for Raspbian, as explained in the docs.

I was somewhat deceptive in my question gathering as I think this is entirely unrelated to the sixaxishelper, as I haven't actually gotten to use the wii controller until now.

I have tried removing and syncing the devices from bluetooth config menu and also bluetoothctlthey sync just fine.

/proc/bus/input/devices lots of things.
Logitech* AnywhereMX & K350 & K400
Sony Playstation(r)3* Controller & Motion Sensors
Nintendo Wii Remote* Accelerometer & IR & _Remote & Motion Plus (lists 4 inputs)

So my question could have been is the Wii Motion Plus incompatible? I searched the forums but I ignored that they go on and on without answers.
It syncs fine, and the jstest buttons respond, it is some mapping overlay, but also there is this Traceback in joy2key. It is very close to working. But very close could be miles, underground.

I have a hundred tabs open and a link to this was broken, will go here https://github.com/retropie/retropie-setup/wiki/Wiimote-Controller
and hopefully it will work.

@carlosricardocm said in Launching chromium from emulationstation:

I get the following message:
Failed to put Xlib into threaded mode.
Gtk: cannot open display

In order to fix that, you need to follow this tutorial.
In the end, I only had to run the two installs below:

sudo apt-get install xinit sudo apt-get install matchbox-window-manager

I have a script called chromium[dot]sh in RetroPie/roms/chromium which contains the following line inside:
chromium-browser

After installing xinit and matchbox-window-manager, I've modified my Chromium launcher script exactly as instructed in the aforementioned tutorial.

Also I added the following to the file es_sytems.cfg located in /opt/retropie/config/all/emulationstation/es_system
<system> <fullname>Chromium</fullname> <name>chromium</name> <path>~/RetroPie/roms/ chromium</path> <extension>.sh .SH</extension> <command>bash %ROM%</command> <platform>chromium</platform> </system>

In my file, I've got:

<system> <name>chromium</name> <fullname>Chromium Web Browser</fullname> <path>/home/pi/RetroPie/roms/chromium</path> <extension>.sh .SH</extension> <command>startx %ROM% > /dev/null 2>&1</command> <platform>chromium</platform> <theme>chromium</theme> </system>

Note the <command> line: I've entered startxfollowed by the %ROM% parameter (which will get the script name) then an extra > /dev/null 2>&1 (this is to omit the output from the script commands, keeping a clean console).

Update:
Initially I had xinit in the command line to invoke the script from a window manager environment. A couple days after, while managing modules and plugins (throwing apt-gets at random, for no reason whatsoever), I ended up somehow breaking xinit as in it would no longer start the X-Server. So I found a workaround by replacing xinit with startx in the <command> line, and all was good again.