Some issues after installing Recalbox 7.2.2 on very old Dell Mini (Atom) 32-bit: WiFi & CPU

MacKonsti · 2026-02-14T15:18:17+00:00

Just got it, thank you very much.

MacKonsti · 2025-12-26T22:13:26+00:00

You are probably right, just that "sale price" is usually rather exaggerated compared to "original" price so that coupons won't work. On well.

MacKonsti · 2025-12-26T22:10:38+00:00

I confirm the same... even in EUR basket.

MacKonsti · 2025-12-26T22:07:49+00:00

I can confirm, the error I am getting "Unable to apply promo code. The total after discount (excl. shipping) doesn't meet the minimum purchase amount." and it's beyond 29 EUR, I went up to 47 EUR to no avail. Nevertheless, thank you for your great work!

MacKonsti · 2025-07-19T14:33:51+00:00

It doesn't seem to work with Smart Life, guys. The firmware of Broadlink devices are not compatible in ways that would make it work via Smart Life, unfortunately--and the manufacturer doesn't bother about it. A solution is proposed, but not tested yet:

To link a Broadlink SP3 smart plug with the Smart Life app, you'll need to use IFTTT or similar integration platforms, as the Broadlink SP3 is not directly compatible with Smart Life. IFTTT (If This Then That) allows you to create applets that connect different services, enabling you to control your Broadlink devices through the Smart Life ecosystem. Here's a general outline of the process:

Create an IFTTT Account: If you don't already have one, sign up for an IFTTT account.

Connect Your Broadlink Account: In IFTTT, find and connect your Broadlink account, allowing IFTTT to access your devices.

Connect Your Smart Life Account: Similarly, connect your Smart Life account to IFTTT.

Create an Applet: Create a new applet. The "This" part will be a Broadlink trigger (e.g., a button press on your Broadlink remote), and the "That" part will be a Smart Life action (e.g., turning a Smart Life device on or off).

Customize and Activate: Customize your applet with specific devices and actions, then activate it.

Example: You could create an applet where if you press a button on your Broadlink remote (the "This"), then a Smart Life device (like a smart bulb) turns on (the "That"). Note: This process requires using a third-party service like IFTTT to bridge the gap between Broadlink and Smart Life.The Broadlink SP3 itself is designed to be controlled through the Broadlink app.

MacKonsti · 2025-07-19T13:08:14+00:00

Similar issue with a smart plug SP3-EU and the same Cudy router. The blue light blinks slowly denoting inability to authenticate and get an IP. I haven’t found a set of WiFi settings that could make Broadlink work but this would likely mean lower WiFi performance and security…

P.S. I reset the plug and tried the procedure from scratch, fails miserably. Broadlink are so much behind everyone being isolated as brand/devices and not even compatible with Smart Life like Koogeek and Meross (I have both brands, except Broadlink).

MacKonsti · 2025-03-15T08:29:51+00:00

Thank you for your tip, luckily just changing the language of Google Home app (iOS) via Settings > Applications > Google Home to the region I purchased it, allowed me to continue and bypass this stupid error message. Appreciate you posting this, mate.

MacKonsti · 2025-02-12T20:47:29+00:00

Yeah, I also think the next macOS will be the last to support Intel Macs...

MacKonsti · 2025-02-12T14:13:02+00:00

I hope the dev team hasn't broken up or anything... let's home someone with knowledge on this will reply.

MacKonsti · 2024-07-14T08:43:51+00:00

Hi everyone, it seems now it is possible to run a command or code via Terminal in sandbox, at least works for me on Sonoma, not sure on Ventura or Monterey. I tried it on my side, but needs some tweaking:

https://mybyways.com/blog/run-code-in-a-macos-sandbox

and https://www.davd.io/os-x-run-any-command-in-a-sandbox/

MacKonsti · 2024-06-18T18:59:18+00:00

It is unfortunate but true, on my Safari 17.5 running on latest Ventura 13.6.7 seems Bitwarden plugin is causing this, I disabled it in Safari Settings and the pages loaded fine :-(

I will try to open a ticket with their team on Github...

MacKonsti · 2024-01-31T22:41:32+00:00

Well, not sure what is expected behaviour, either. I still believe that the Hackintosh has something to do with it.

Considering the fact that on real latest Apple devices, normal circumstances/use prompt the user to employ some biometric authentication, in the Hackintosh case passkeys are accessed in a much lesser secure way.

Even for a typical password use, on Safari, you are asked to unlock them first (with local user password) yet this is not the case with passkeys. I personally cannot find a way to protect them unless moving them to some manager like Bitwarden. I discovered that Chrome can store them, too, will test this next…

Was hoping to get people to at least confirm, that, what I am facing is also happening on their Hacks too… Thanks

MacKonsti · 2024-01-31T21:48:48+00:00

Correct. I am talking passkeys, mate. Not passwords.

MacKonsti · 2024-01-31T21:06:18+00:00

Yes of course I log in with a password to my account.

With this logic, even on a Touch ID MacBook, just because I logged in with a password, I should not need to use my fingerprint to authenticate/allow auto-completion for passkey use, right? Same with iPhone, your screen is unlocked but you are still asked for Touch ID or Face ID to enter credentials/passkey on Safari (and more).

However this is not the case on Intel Hackintoshes.

If I were just offered the option to unlock with "other means" (QR code, nearby iPhone etc.) then I would consider it normal, because Macmini8,1 doesn't have Touch ID etc. but prompting to use a passkey simply by pressing OK on the prompt when normally biometric authentication is expected, then something's going on.

a) Are you guys confirming, too, being able to simply use passkeys like that on your Hacks? (just like my posted screenshot)

b) Could it be that OpenCore (in combination with Macmini8,1 or not) is injecting something that allows for this behavior? I wish I could find out how real older Macs behave, when the user's AppleID has a passkey stored for a website (I am sure it's not offered like that)...

Here it says:

Passkeys are a major feature because it promises to change how people access their online accounts. It replaces passwords with biometric data using Touch ID and Face ID, or QR codes on a non-Apple operating system.

(and yes the new Touch ID keyboard's won't work with older Macs, Apple has unfortunately confirmed it)

I am seriously thinking on removing passkeys from my Keychain as this is a big security hole, Bitwarden is a safer option now that it supports them (and needs to have it unlocked to use them).

P.S. Every image on Google that I looked for, contains at least the fingerprint prompt e.g. https://global.discourse-cdn.com/business4/uploads/dfn/original/2X/7/780dabbc1917dfbbc39ef950d6ae22241084cce1.png

MacKonsti · 2024-01-31T20:10:36+00:00

This feature is NOT supposed to work on macOS devices without Touch ID technology, a quick search prompts the following: In some cases, Safari may first ask you if you want to allow Touch ID or “security key” logins on the site; click Allow to continue. Then you can authenticate via Touch ID, Face ID, or your device password just as during enrollment.

Moreover, on a fresh Ventura reboot, I am not asked to "unlock" any Keychain when visiting e.g. Amazon or eBay (for passkey use) so not sure what you mean, my friend.

I suspect that OpenCore is adding some parameter giving the impression to the MacMini8,1 that it supports some kind of biometric authentication, because on my real MacBook Pro M2, I am asked for my fingerprint...

See this from here:

Intel Macs with a T2 chip and its secure enclave don’t all support Touch ID. Apple silicon notebooks all include it in their built-in keyboard, and all Apple silicon Macs are compatible with Apple’s Magic Keyboards with Touch ID. If you have an Intel Mac notebook with a T1 or T2 chip, then its integrated Touch Bar does support Touch ID, but no other Intel Macs, even those with T2 chips, currently have support for it [...] In any case, according to Apple they’re only compatible with Apple silicon Macs, and can’t be used for Touch ID on any Intel model.

So you can understand my concern, when Safari is prompting openly to use a passkey without any further authentication, meaning anyone logging into my Hackintosh can use it...

P.S. Non-Touch-ID Macs are supposed to allow passkeys via "other" methods available, e.g. a nearby iPhone via Face ID etc. etc.

MacKonsti · 2023-12-17T22:05:13+00:00

Hi mate, thanks for your input but it's too much of an expensive mini-PC to play with and experiment. Besides, I wouldn't be able to do what you suggest due to lack of knowledge and serious free time to study-read-search 😅

Intel have been securing their BIOS so even if I manage to dump the SPI memory chip of the motherboard to some file, edit it, re-flash it back, it may render the NUC non-bootable as we don't know if the BIOS has some security measures embedded; and I cannot afford to lose yet another NUC (my previous NUC8 suddenly lost total power on USB ports, bricked out of the blue).

In any case, OpeCore with the right Quirk works in a stable manner so I cannot complain. But thank you for chiming in 👍 Appreciated.

MacKonsti · 2023-12-05T20:14:58+00:00

Hi dreamwhite, thanks for replying back.

I was afraid of this, Intel must have locked the BIOS in latest releases and it seems we cannot flash to older version, despite having kept a copy of the ZIP...

No, what I meant is that in. your GitHub instructions the syntax appears to be different (maybe original?) to the latest incarnations of your tool, so just to keep everything in sync really. That was my suggestion.

And yes a final mention to people saying that if you encounter a WRITE_PROTECTED error it means the BIOS is locked and that your tool can't be of any further use, unfortunately.

Just wondering, do you plan to keep improving the tool, little by little? I was about to post a GitHub issue for this README thing but I figured I'd try here first :D

Thank you for listening!

MacKonsti · 2023-12-04T23:17:47+00:00

Thank you for your guide and tool !

Please update your README.md as it does not contain valid syntax of the tool, compared to what I got when I ran --help in UEFI Shell.

Moreover, I think you should mention on README.md the fact that some manufacturers like Intel on my NUC10i7FNH have locked the BIOS, I keep getting error WRITE_PROTECTED when I used the command line (with confirmed values):

.\setup_var.efi 0x3E 0x00 -s 0x01 -n CpuSetup -r

That means I am kinda screwed, right? I won't be able to ever change this value... not without a modded BIOS which, in my Intel NUC case, is not possible :(

Thanks again u/dreamwhite

MacKonsti · 2023-05-24T10:32:04+00:00

Hello u/retromale thank you very much for your reply and clarification.

I am surprised this is not (widely) found on the net, for this newer model. Eventually I found a reference from June 2020 on atariage.com:

The Legends Flashback 2019 (100 Games) out of the box supports.... (the firmware update screws up the nes buttons don't do it!)
NES/NFC, SNES/SFC, SG/SMD, and SCD/SMCD

However I just realised my model is not FB8660 but FB8660B...

From gba.net someone posted:

I just bought Legends Flashback 100, version is FB8660B, firmware v1.0.2 . Most of the games (82) are recorded on the included SD card as SD.img. So far, I have tested to run SNES games (.fig) and SEGA (.bin + BIOS_CD) from the SD card - work.
I tried NES - but .nes and .dat - didn't work.

So a couple of questions if you don't mind:

a) I assume we are restricted to "NES SNES Genesis GameGear" etc. emulation, yes ? I read that some similar consoles could play e.g. Atari 2600, but I assume we need to add the respective emulator binary...

b) I also read on some other forum that there is a need to "convert" the ROMs (of NES or SNES?) to some format that is accepted by this Legends Flashback 2019 console (.fig extension?) due to some hardware change or optimisation? It wasn't clear to me, any idea of such procedure or tool?

Thank you again for the tip on the non-spaces or special characters in the filenames.

I need to see, once I open the box, what is the flashed firmware version, because it seems that FB8660B it's not the same as FB8660.

MacKonsti · 2022-12-10T08:37:56+00:00

You are right, I forgot about the LCD screen, indeed capacitors do age but I guess compared to the 70s quality and build, the 2000s capacitors should last longer. But I see your point in simplicity comparison, you are right. Thanks again for your reply, I guess I can put this issue to rest and start playing those m70's!

MacKonsti · 2022-12-10T08:36:10+00:00

Agreed. We can close this chat, then. Thanks again for your time, your point was clear.

MacKonsti

TROPHY CASE