PI 3 + PS3 Bluetooth controller freeze fix. UPDATED
-
Ok...not trying to be critical of you but first off....Sudo has to be changed to all lower case
Secondly...I dunno here so maybe someone can help out.... after getting the rpi-update installed and trying the "sudo sed xxxxx" line...mine errors out "sed: -e expression #1, char 10: unknown option to 's"
Just tried the last "sudo update_self....." line and it also errors out something about 'curl - certificates' or something....
-
The curl errors might be related to invalid or old certificates. Try this:
sudo update-ca-certificates --fresh -
I don't know about a controller freezing but if you are having trouble with a "certificates error", check the time on the Pi. If it's not correct you will receive a error.
-
@Rascas It's grabbing stuff right now... THANKS for the clarification!
@glennlake Thanks to you as well...never thought about my date/time being unset. Which brings me to a question. Is there a way to keep the date/time in sync after a shutdown? I have a date/time module but would like to save it for another project....but if I really have to use it....probably have to setup an auto-grab on each boot in a config file if I don't...
-
@jmebd On my Pi3 if connected to the internet via the ethernet jack the time will update automatically. If using the wifi it never seemed to update so I added a line to the /etc/rc.local file. First you need to install "rdate". Go to the command line and type "sudo apt-get install rdate"(without quotes). Then type "sudo nano /etc/rc.local"(again without quotes). This will open the rc.local file so you can edit it. What you want to do is between the "fi" and the "exit 0" you want to enter this line:
sudo rdate -n -4 time-a.nist.gov
Now save this file with the extra line by typing "ctrl x", y, then enter. Now reboot and it should pull the correct time from the goverment time site and keep your pi in sync(if I haven't fat-fingered something).
-
@glennlake Fantastic! Thank you....I'll give that a shot when I get home from work afterwhile. I checked the date/time and it was incorrect so I went ahead and put the date/time module last night but I'd like for it to not be on there. I keep mine plugged in to ethernet just for kodi stuff so this will help greatly!
Thanks everyone for their patience and help. I'm sure LOTS will benefit from just this one thread itself.
p.s. I got my PS3 controller transferred back to onboard bluetooth after the update last night but didn't get a lot of time to play with it but in the 30 minutes I did....worked fine. Anyone else experiences thus far?
-
Trying now.. 30 good minutes without any freeze, that's a record! :) Will let the pi on for a while running a Mame game....
-
After some hours still running fine, and no new problem has appeared. :)
-
pi3, 3.7, updated to kernel 4.4, ps3 wireless
I've been using the shutdown system through the menu to turn off the system. I have to unplug it and can't leave it on for the time being.
I performed the update as per the first post including the certificate command (curl error).
Immediately after this update, when I use the shutdown command and unplug the pi, it won't boot upon re-plugging it in. It either crashes and stays black or I get a bunch of timeout messages on the screen. If I unplug without using the shutdown command it boots up just fine. If I unplug during the crash and re-plug it boots fine.
What log info can I provide to help with this and does this need it's own thread even though I believe it's related to the kernel 4.4 update.
-
After I do the "sudo rpi-update 15ffab5493d74b12194e6bfc5bbb1c0f71140155" and it's doing the update thing, then after a bit, I get several errors, like:
"gzip: stdin not in gzip format"
"tar: Child returned status 1"
"tar: error is not recoverable: exiting now"I'm doing this on my raspberry pi 3, Retropie 3.7.
Any idea how to solve this?
-
@opensourcefan I dont't know, I cannot reproduce it. Check /var/log/syslog.
@thorgim reboot and try again.
-
@Rascas It did the same thing again, but after I did a "sudo rpi-update", then it update the firmware to 4.4.9-v7, and it backup the 4.1.19-v7 with no errors at all. Seems it work better than the other option.
-
@thorgim rpi-update without the hash updates to the latest kernel version available, with the hash updates to the specific commit. Since that specific commit is already verified to work for many people, and later ones not, that was the reason to pick that specific commit.
EDIT: That is no longer needed. Kernel 4.4 is on Raspbian repo now, just update as normal:
sudo apt-get update && sudo apt-get dist-upgrade -
@Rascas Thanks
-
@Rascas Thank you!
-
pi3, 3.7, updated to kernel 4.4, ps3 wireless
I got my pi last month and was running retropie with the old kernel before and got everything running except for the random freezing problem. So I updated the kernel to 4.4 yesterday. Now it seems impossible for me to pair my ps3 wireless with my pi. Maybe I missed some important settings?
That's what I did:
'sudo apt-get install rpi-update'
'sudo rpi-update 15ffab5493d74b12194e6bfc5bbb1c0f71140155'
'sudo update-ca-certificates --fresh'I also tried to use:
'sudo apt-get update && sudo apt-get dist-upgrade'
Still the controller is working with usb, only. Any suggestions what else I could try to get my bluetooth working again? (I'm quite new to all of this so it is hard to tell what's going wrong for me)
-
I think this is a bug with the update itself. It may be killing the Bluetooth. Take a look at this thread https://retropie.org.uk/forum/topic/905/lost-ps3-bluetooth-after-updating-raspbian/9
-
I foresaw there being a BT issue in retropie when I saw the release notes for Raspian on Distrowatch yesterday from Simon Long:
"We've just released a new version of our Raspbian image with some (hopefully) useful features. When the Pi 3 launched back in February, we'd not had time to do much in terms of getting access to the new on-board Bluetooth hardware. There was a working software stack, but the UI was non-existent. I'd hoped to be able to use one of the existing Linux Bluetooth UIs, but on trying them all, none were really what I was looking for in terms of usability and integration with the look and feel of the desktop. I really didn't want to write one from scratch, but that ended up being what I did, which meant a fun few weeks trying to make head or tail of the mysteries of BlueZ and D-Bus. After a few false starts, I finally got something I felt was usable, and so there is now a Bluetooth plugin for the LXPanel taskbar."
So, the new bluetooth module does fix BT in LXDE...but apparently breaks in in Retropie. The short term solution is to downgrade it as stated in the previous post (although I have yet to confirm that...but I see no reason why it would not work) but again it is a short term solution. The solution is not to suppress the update but to fix the compatibility issue in Retropie. Hopefully we'll see a v3.8 with compatibility with the new BT module fixed so that we can enjoy the best of all worlds.
-
After a dist-upgrade, do:
wget http://archive.raspberrypi.org/debian/pool/main/p/pi-bluetooth/pi-bluetooth_0.1.0_armhf.deb
and
sudo dpkg -i pi-bluetooth_0.1.0_armhf.deb
Reboot afterward. If hciconfig give you an output the bluetooth is working again.
This will downgrade the bluetooth module and allow the PS3 controller (and other BT devices) to work again. Best part is now that the kernel has been updated the freezing no longer exists. I have been using the PS3 controller all night without a freeze.
-
what way can I check what version of the bluetooth module is installed from the commandline and also how to check if the bluetooth module is seeing the controller at commandline level?
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.