Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kext is not working properly on macOS 14.4+ #12

Open
fivossak opened this issue Mar 31, 2024 · 6 comments
Open

Kext is not working properly on macOS 14.4+ #12

fivossak opened this issue Mar 31, 2024 · 6 comments

Comments

@fivossak
Copy link

With macOS 14.0-14.3.1, we could use the -rtsfbeta boot argument to force the kext to load on an unknown OS version and that did the trick. Starting with macOS 14.4, the kext no longer works as intended. If you go to System Report -> Card Reader, it will display "There was an error loading card reader information" or something along these lines. My device is an RTS522A if that matters.

@5T33Z0
Copy link

5T33Z0 commented May 25, 2024

In macOS 14.5, it's partially workig. With the boot-arg -rtsfbeta the kext will load and infos about the reader are shown in System Profiles:

Bildschirmfoto 2024-05-25 um 06 38 56

But no properties about the inserted SD card are displayed.

@fivossak
Copy link
Author

fivossak commented Jun 2, 2024

In macOS 14.5, it's partially workig. With the boot-arg -rtsfbeta the kext will load and infos about the reader are shown in System Profiles:

Bildschirmfoto 2024-05-25 um 06 38 56

But no properties about the inserted SD card are displayed.

I just tested it on 14.5. With no card inserted, reader info is displayed correctly, but once a card is inserted, I get "There was an error while scanning for Apple Internal Memory Card Readers."

@benjenq
Copy link

benjenq commented Aug 5, 2024

Is there any plan to support macOS 15? I tested with -rtsfbeta on macOS 15 beta but it did not work anymore. It shown volume name but not mounted.

@marciasl
Copy link

Same issue here, from macOS Sonoma 14.4+, there is this issue

@P1nkz
Copy link

P1nkz commented Feb 7, 2025

+1, same problem.

@5T33Z0
Copy link

5T33Z0 commented Feb 7, 2025

Well, the last update was almost 2,5 years ago. I guess somebody has to fork the repo and fix the kext.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants