The online community for MiSTer FPGA enthusiasts
https://misterfpga.org/
I never had a Bluetooth device synced on my MiSTer before.iso70x wrote: ↑Tue Aug 24, 2021 3:20 pm I've had this happen occasionally, and found that pairing the device while no other bluetooth pads/keyboards are connected has worked. This does require you have an IO board with the 3 buttons though.
Try switching off *all* bluetooth devices that are connected to the MiSTer, then do the following:
1. Hold down the OSD button on the MiSTer until the bluetooth pairing dialog appears (takes a few seconds)
2. Stick the device you wish to pair into 'pairing mode'
3. Wait and see whether it picks it up.
I've found that if I have a PS DS3 actively connected to my MiSTer via bluetooth, then there are a few devices that fail to pair. As soon as I switch the DS3 off and follow the above sequence, I can pair the device ok. After that, I can have them both connected fine. Seems there might be a conflict with some device combinations and the bluetooth pairing feature.
I don't use the update script on my MiSTer, mainly because I don't want every single core of everything, only the ones I want. Can I manually edit a file or something?FoxbatStargazer wrote: ↑Thu Aug 26, 2021 1:24 am A big update to bluetooth drivers and pairing just went through. Use update script and then be sure to use the built-in dialog (hold OSD button or F11 while the OSD is open), not the bluetooth_pair script you may have in the scripts folder, and give it a try.
Combining two Switch joy-cons into a single Pro controller works really well now!
Just running the update.sh script updates this.FoxbatStargazer wrote: ↑Thu Aug 26, 2021 6:15 am You need to update "main/linux" but I have no idea how to do that, been relying on update_all script myself.
Is that the one: https://raw.githubusercontent.com/MiSTe ... /update.shaberu wrote: ↑Thu Aug 26, 2021 2:55 pmJust running the update.sh script updates this.FoxbatStargazer wrote: ↑Thu Aug 26, 2021 6:15 am You need to update "main/linux" but I have no idea how to do that, been relying on update_all script myself.
Also I usually tell people to not use update_all to update the linux since continued writes after the linux image writes without a reboot can corrupt the linux image. If the linux image is updated, the update.sh script updates linux fully right at the end and reboots immediately after. This is critical. I have helped about a person or two a week with manually downloading the linux files and overwriting them because they got corrupted, and most of the time they used the update_all script. Not saying it's a bad script, just something for users to be aware of.
yes. That script downloads the newest version of the other one in that repo, mister_updater.sh, and executes it (among other things). That way you always get the newest script.the_importer wrote: ↑Thu Aug 26, 2021 8:00 pm Is that the one: https://raw.githubusercontent.com/MiSTe ... /update.sh
Yes you can do it this way.the_importer wrote: ↑Thu Aug 26, 2021 6:05 am I don't use the update script on my MiSTer, mainly because I don't want every single core of everything, only the ones I want. Can I manually edit a file or something?
aberu wrote: ↑Thu Aug 26, 2021 10:33 pmyes. That script downloads the newest version of the other one in that repo, mister_updater.sh, and executes it (among other things). That way you always get the newest script.the_importer wrote: ↑Thu Aug 26, 2021 8:00 pm Is that the one: https://raw.githubusercontent.com/MiSTe ... /update.sh
Yes you can do it this way.the_importer wrote: ↑Thu Aug 26, 2021 6:05 am I don't use the update script on my MiSTer, mainly because I don't want every single core of everything, only the ones I want. Can I manually edit a file or something?
https://github.com/MiSTer-devel/Updater ... for-mister
The readme includes instructions on how to create an update.ini in the same folder to customize what you do and don't want.
Good to know. Is this reported on the update_all github? (Did not see anything obvious enough to my brain on the issues page.)aberu wrote: ↑Thu Aug 26, 2021 2:55 pm Also I usually tell people to not use update_all to update the linux since continued writes after the linux image writes without a reboot can corrupt the linux image. If the linux image is updated, the update.sh script updates linux fully right at the end and reboots immediately after. This is critical. I have helped about a person or two a week with manually downloading the linux files and overwriting them because they got corrupted, and most of the time they used the update_all script. Not saying it's a bad script, just something for users to be aware of.
Here is what Locutus73 told me (he maintains the mister update script). This is edited to just show our back and forth.ash2fpga wrote: ↑Fri Aug 27, 2021 7:08 pmGood to know. Is this reported on the update_all github? (Did not see anything obvious enough to my brain on the issues page.)aberu wrote: ↑Thu Aug 26, 2021 2:55 pm Also I usually tell people to not use update_all to update the linux since continued writes after the linux image writes without a reboot can corrupt the linux image. If the linux image is updated, the update.sh script updates linux fully right at the end and reboots immediately after. This is critical. I have helped about a person or two a week with manually downloading the linux files and overwriting them because they got corrupted, and most of the time they used the update_all script. Not saying it's a bad script, just something for users to be aware of.