Fortitude Posted September 1, 2021 Share Posted September 1, 2021 Thanks for adding support for the RTS5260! The driver is not fully working for me yet, but it seems that it’s almost ready. It seems to detect my card reader, but is unable to mount a card in Finder/Disk Utility. On a good note, it looks like your driver knows when a card is connected/disconnected which is a great sign! (please see attached screenshot/boot log with a card inserted) Boot Log for RTS5260.txt Link to comment Share on other sites More sharing options...
Austere.J Posted September 1, 2021 Author Share Posted September 1, 2021 On 8/28/2021 at 5:42 AM, Sherlocks said: report 1. sleep with inserted sdcard 2. wakeup with inserted sdcard, screen is black, i can't see anything. i have to force reboot @Sherlocks This is probably the sign of a kernel panic when your laptop wakes up. On 8/29/2021 at 8:26 AM, whatnameisit said: I'm almost always getting a kernel panic when putting the computer to sleep with the card inserted. @whatnameisit So the kernel panic happened when your laptop went to sleep. On 8/30/2021 at 3:32 AM, gnpaone said: Yeah, you are right, the recent version creates this issue. It's fine with previous builds. I cleared my nvram and tested and it's exactly the same issue as you stated (previously I didn't clear, sorry) @gnpaone I am assuming that you had the same issue when your laptop went to sleep. I didn't observe this kernel panic before, so please try 0.9.7 Nightly Build 1 and see if the issue is resolved. ------------------------------------------------------------------------------------------------------------ On 8/30/2021 at 7:00 AM, SavageAUS said: Any way to get mine working with this kext? @SavageAUS Please follow the instructions, read the FAQs and attach kernel logs as requested. 15 hours ago, Fortitude said: (please see attached screenshot/boot log with a card inserted) @Fortitude Your kernel log is incomplete. See above and attach logs as requested. Link to comment Share on other sites More sharing options...
gnpaone Posted September 2, 2021 Share Posted September 2, 2021 (edited) 13 hours ago, Austere.J said: @gnpaone I am assuming that you had the same issue when your laptop went to sleep. I didn't observe this kernel panic before, so please try 0.9.7 Nightly Build 1 and see if the issue is resolved. I tried the latest nightly build, same issue sir. I still get kernel panic upon wake, mac goes to sleep normally but it cannot wake, I think some process is stopping from waking, this happens only when sdcard is inserted during wake. panic(cpu 0 caller 0xffffff80045c57d6): Kernel trap at 0xffffff800a28c9b4, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0x00000000000000c8, CR3: 0x000000000afed000, CR4: 0x00000000003626e0 RAX: 0x0000000000000000, RBX: 0xffffff93571b7560, RCX: 0xffffff9356815fc8, RDX: 0xffffff800a270510 RSP: 0xffffffa0ab723d00, RBP: 0xffffffa0ab723d20, RSI: 0xffffffa0ab723d58, RDI: 0x0000000000000000 R8: 0x0000000000000000, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0x0000000000000008 R12: 0xffffff93571b7560, R13: 0xffffff800a27bea0, R14: 0x0000000000000000, R15: 0xffffff9356815e80 RFL: 0x0000000000010286, RIP: 0xffffff800a28c9b4, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0x00000000000000c8, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1 Backtrace (CPU 0), Frame : Return Address 0xffffffa0ab723720 : 0xffffff800448e04d mach_kernel : _handle_debugger_trap + 0x3fd 0xffffffa0ab723770 : 0xffffff80045d4e13 mach_kernel : _kdp_i386_trap + 0x143 0xffffffa0ab7237b0 : 0xffffff80045c540a mach_kernel : _kernel_trap + 0x55a 0xffffffa0ab723800 : 0xffffff8004432a2f mach_kernel : _return_from_trap + 0xff 0xffffffa0ab723820 : 0xffffff800448d86d mach_kernel : _DebuggerTrapWithState + 0xad 0xffffffa0ab723940 : 0xffffff800448db63 mach_kernel : _panic_trap_to_debugger + 0x273 0xffffffa0ab7239b0 : 0xffffff8004c9dc0a mach_kernel : _panic + 0x54 0xffffffa0ab723a20 : 0xffffff80045c57d6 mach_kernel : _sync_iss_to_iks + 0x2c6 0xffffffa0ab723ba0 : 0xffffff80045c54bd mach_kernel : _kernel_trap + 0x60d 0xffffffa0ab723bf0 : 0xffffff8004432a2f mach_kernel : _return_from_trap + 0xff 0xffffffa0ab723c10 : 0xffffff800a28c9b4 science.firewolf.rtsx : __ZN14IOSDHostDriver20onSDCardRemovedGatedEPN8IOSDCard10CompletionE + 0x14 0xffffffa0ab723d20 : 0xffffff800a270715 science.firewolf.rtsx : __ZN14IOSDHostDevice20onSDCardRemovedGatedEPN8IOSDCard10CompletionE + 0x65 0xffffffa0ab723d80 : 0xffffff800a2741b3 science.firewolf.rtsx : __ZN27RealtekCardReaderController20onSDCardRemovedGatedEPN8IOSDCard10CompletionE + 0x53 0xffffffa0ab723db0 : 0xffffff800a27bf59 science.firewolf.rtsx : __ZN30RealtekUSBCardReaderController22fetchDeviceStatusGatedEP18IOTimerEventSource + 0xb9 0xffffffa0ab723de0 : 0xffffff8004bf47e5 mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0xa5 0xffffffa0ab723e50 : 0xffffff8004bf46e6 mach_kernel : __ZN18IOTimerEventSource17timeoutAndReleaseEPvS0_ + 0xc6 0xffffffa0ab723e80 : 0xffffff80044d4605 mach_kernel : _thread_call_delayed_timer + 0x4a5 0xffffffa0ab723ef0 : 0xffffff80044d5574 mach_kernel : _thread_call_delayed_timer + 0x1414 0xffffffa0ab723fa0 : 0xffffff800443213e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: science.firewolf.rtsx(0.9.7)[3E3E22A0-A604-3E59-9684-BB6FBC7B7E87]@0xffffff800a252000->0xffffff800a353fff dependency: com.apple.iokit.IOPCIFamily(2.9)[F7AA4BAF-35CF-3784-A50C-5FD9CDCBE488]@0xffffff8006f6c000->0xffffff8006f94fff dependency: com.apple.iokit.IOStorageFamily(2.1)[6CD2A6EC-9FFC-370D-8FEE-C8016E5C6BBA]@0xffffff800706f000->0xffffff8007080fff dependency: com.apple.iokit.IOUSBHostFamily(1.2)[3FDCC3CF-64A8-3794-A52C-5D8DE43A8265]@0xffffff800728a000->0xffffff8007318fff Process name corresponding to current thread: kernel_task Boot args: -wegnoegpu msgbuf=10485760 chunklist-security-epoch=0 -chunklist-no-rev2-dev Mac OS version: 20G95 Kernel version: Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:31 PDT 2021; root:xnu-7195.141.2~5/RELEASE_X86_64 Kernel UUID: FECBF22B-FBBE-36DE-9664-F12A7DD41D3D KernelCache slide: 0x0000000004200000 KernelCache base: 0xffffff8004400000 Kernel slide: 0x0000000004210000 Kernel text base: 0xffffff8004410000 __HIB text base: 0xffffff8004300000 System model name: MacBookPro16,1 System shutdown begun: NO Panic diags file available: YES (0x0) Hibernation exit count: 0 System uptime in nanoseconds: 122626517647 Last Sleep: absolute base_tsc base_nano Uptime : 0x0000001c8d1c2fe9 Sleep : 0x0000001c64e5018a 0x0000000771979b42 0x0000000000000000 Wake : 0x0000001c66f8a130 0x0000000102d04486 0x0000001c6560ce83 rtsx-f4eca02.log.zip Edited September 2, 2021 by gnpaone Link to comment Share on other sites More sharing options...
whatnameisit Posted September 2, 2021 Share Posted September 2, 2021 (edited) 12 hours ago, Austere.J said: On 8/30/2021 at 12:26 AM, whatnameisit said: @whatnameisit So the kernel panic happened when your laptop went to sleep. It's actually on wake. It's my bad I didn't state it correctly. I downloaded the nightly build and it still panics upon wake. panic(cpu 0 caller 0xffffff8019bc57d6): Kernel trap at 0xffffff801db759b4, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0x00000000000000c8, CR3: 0x0000000023c4b000, CR4: 0x00000000000226e0 RAX: 0x0000000000000000, RBX: 0xffffff936e0d52a0, RCX: 0xffffff936dd085e8, RDX: 0xffffff801db59510 RSP: 0xffffffb0adefbd00, RBP: 0xffffffb0adefbd20, RSI: 0xffffffb0adefbd58, RDI: 0x0000000000000000 R8: 0x0000000000000000, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0x0000000000000008 R12: 0xffffff936e0d52a0, R13: 0xffffff801db64ea0, R14: 0x0000000000000000, R15: 0xffffff936dd084a0 RFL: 0x0000000000010286, RIP: 0xffffff801db759b4, CS: 0x0000000000000008, SS: 0x0000000000000000 Fault CR2: 0x00000000000000c8, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1 Backtrace (CPU 0), Frame : Return Address 0xffffffb0adefb720 : 0xffffff8019a8e04d mach_kernel : _handle_debugger_trap + 0x3fd 0xffffffb0adefb770 : 0xffffff8019bd4e13 mach_kernel : _kdp_i386_trap + 0x143 0xffffffb0adefb7b0 : 0xffffff8019bc540a mach_kernel : _kernel_trap + 0x55a 0xffffffb0adefb800 : 0xffffff8019a32a2f mach_kernel : _return_from_trap + 0xff 0xffffffb0adefb820 : 0xffffff8019a8d86d mach_kernel : _DebuggerTrapWithState + 0xad 0xffffffb0adefb940 : 0xffffff8019a8db63 mach_kernel : _panic_trap_to_debugger + 0x273 0xffffffb0adefb9b0 : 0xffffff801a29dc0a mach_kernel : _panic + 0x54 0xffffffb0adefba20 : 0xffffff8019bc57d6 mach_kernel : _sync_iss_to_iks + 0x2c6 0xffffffb0adefbba0 : 0xffffff8019bc54bd mach_kernel : _kernel_trap + 0x60d 0xffffffb0adefbbf0 : 0xffffff8019a32a2f mach_kernel : _return_from_trap + 0xff 0xffffffb0adefbc10 : 0xffffff801db759b4 science.firewolf.rtsx : __ZN14IOSDHostDriver20onSDCardRemovedGatedEPN8IOSDCard10CompletionE + 0x14 0xffffffb0adefbd20 : 0xffffff801db59715 science.firewolf.rtsx : __ZN14IOSDHostDevice20onSDCardRemovedGatedEPN8IOSDCard10CompletionE + 0x65 0xffffffb0adefbd80 : 0xffffff801db5d1b3 science.firewolf.rtsx : __ZN27RealtekCardReaderController20onSDCardRemovedGatedEPN8IOSDCard10CompletionE + 0x53 0xffffffb0adefbdb0 : 0xffffff801db64f59 science.firewolf.rtsx : __ZN30RealtekUSBCardReaderController22fetchDeviceStatusGatedEP18IOTimerEventSource + 0xb9 0xffffffb0adefbde0 : 0xffffff801a1f47e5 mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0xa5 0xffffffb0adefbe50 : 0xffffff801a1f46e6 mach_kernel : __ZN18IOTimerEventSource17timeoutAndReleaseEPvS0_ + 0xc6 0xffffffb0adefbe80 : 0xffffff8019ad4605 mach_kernel : _thread_call_delayed_timer + 0x4a5 0xffffffb0adefbef0 : 0xffffff8019ad5574 mach_kernel : _thread_call_delayed_timer + 0x1414 0xffffffb0adefbfa0 : 0xffffff8019a3213e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: science.firewolf.rtsx(0.9.7)[3E3E22A0-A604-3E59-9684-BB6FBC7B7E87]@0xffffff801db3b000->0xffffff801dc3cfff dependency: com.apple.iokit.IOPCIFamily(2.9)[F7AA4BAF-35CF-3784-A50C-5FD9CDCBE488]@0xffffff801c56c000->0xffffff801c594fff dependency: com.apple.iokit.IOStorageFamily(2.1)[6CD2A6EC-9FFC-370D-8FEE-C8016E5C6BBA]@0xffffff801c66f000->0xffffff801c680fff dependency: com.apple.iokit.IOUSBHostFamily(1.2)[3FDCC3CF-64A8-3794-A52C-5D8DE43A8265]@0xffffff801c88a000->0xffffff801c918fff Process name corresponding to current thread: kernel_task Boot args: radpg=15 msgbuf=10485760 debug=0x100 keepsyms=1 chunklist-security-epoch=0 -chunklist-no-rev2-dev Mac OS version: 20G95 Kernel version: Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:31 PDT 2021; root:xnu-7195.141.2~5/RELEASE_X86_64 Kernel UUID: FECBF22B-FBBE-36DE-9664-F12A7DD41D3D KernelCache slide: 0x0000000019800000 KernelCache base: 0xffffff8019a00000 Kernel slide: 0x0000000019810000 Kernel text base: 0xffffff8019a10000 __HIB text base: 0xffffff8019900000 System model name: MacPro6,1 (Mac-F60DEB81FF30ACF6) System shutdown begun: NO Panic diags file available: YES (0x0) Hibernation exit count: 0 System uptime in nanoseconds: 87609392051 Last Sleep: absolute base_tsc base_nano Uptime : 0x0000001465ed407b Sleep : 0x000000142d83bd2b 0x0000000c21c5113f 0x0000000000000000 Wake : 0x000000142e34d662 0x000000001467b121 0x000000142db61516 Edited September 2, 2021 by whatnameisit test and attach log Link to comment Share on other sites More sharing options...
SavageAUS Posted September 2, 2021 Share Posted September 2, 2021 Any way to get mine working with this kext? I have both kexts RealtekCardReaderFriend.kext & RealtekCardReader.kext I am trying with a Samsung 32 EVO SDHC & a generic SDHC 4Gb on my laptop (specs in sig) on Monterey.So from reading maybe I need to roll back to an earlier kext?Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
Fortitude Posted September 2, 2021 Share Posted September 2, 2021 Oops, sorry… Hopefully this one’s better. Please find below the attached kernel log with a card inserted. rtsx-5260.log Link to comment Share on other sites More sharing options...
mnfesq Posted September 5, 2021 Share Posted September 5, 2021 (edited) Hi. I have the RTL8411B PCI-e card reader and everything looks great in terms of the card reader showing up in IOreg and System Info but I cannot get any flash drives to actually mount. In my log, I saw several references to "Error: Failed to issue the ACMD41." Something is telling me that this is significant. I have attached my log file and hope you have a suggestion. I believe @Allan is having the same problem. Here is what you said in response to his report: Quote Your card did not respond to the CMD8, which means that it is probably a v1.00/v1.01 SD card. (i.e. an old SDSC card.) Your card was then timed out when the host driver issued an ACMD41 to request the card to switch to 1.8V. In this case, I have not implemented any fallback mechanism yet. Mine is a brand new 512 GB SD Card made by Nuilaks. Thanks. RTL8411B rtsx.log P.S. Maybe this will help? https://www.microchip.com/forums/m572718.aspx Edited September 5, 2021 by mnfesq 1 Link to comment Share on other sites More sharing options...
ic005k Posted September 7, 2021 Share Posted September 7, 2021 On 8/28/2021 at 8:42 PM, Sherlocks said: report 1. sleep with inserted sdcard 2. wakeup with inserted sdcard, screen is black, i can't see anything. i have to force reboot 1. sleep without inserted sdcard 2. wakeup without inserted sdcard, screen is back. it's normal. thanks This issue has been solved in the latest version 0.9.7, you can download and try. RealtekCardReader_0.9.7_f4eca02_RELEASE.zip 1 Link to comment Share on other sites More sharing options...
ic005k Posted September 7, 2021 Share Posted September 7, 2021 Very nice! This is definitely another creation in the Hackintosh field, one less gap in the Hackintosh field, thank you very much! 2 Link to comment Share on other sites More sharing options...
gnpaone Posted September 7, 2021 Share Posted September 7, 2021 21 minutes ago, ic005k said: This issue has been solved in the latest version 0.9.7, you can download and try. No, it doesn't work, the issue exists still. I tried debug version of that same kext in last post and as you said to try release version I tried it and same again, no change. Keep the sdcard inserted while waking from sleep and try it, going to sleep is not the issue. Link to comment Share on other sites More sharing options...
ic005k Posted September 7, 2021 Share Posted September 7, 2021 8 minutes ago, gnpaone said: No, it doesn't work, the issue exists still. Here is the file I use, you can try it, good luck. (Previously, there was a black screen and death on my side after waking up) RealtekCardReader.zip Link to comment Share on other sites More sharing options...
gnpaone Posted September 7, 2021 Share Posted September 7, 2021 1 hour ago, ic005k said: Here is the file I use, you can try it, good luck. (Previously, there was a black screen and death on my side after waking up) No, not working, sorry, what card reader you have? Link to comment Share on other sites More sharing options...
ic005k Posted September 7, 2021 Share Posted September 7, 2021 41 minutes ago, gnpaone said: what card reader you have? My machine is DELL 7472, please see the screenshot below for details. Everything works fine now, including the SD card still being loaded automatically after waking up from sleep with the SD card inserted. Link to comment Share on other sites More sharing options...
Sherlocks Posted September 7, 2021 Share Posted September 7, 2021 46 minutes ago, gnpaone said: No, not working, sorry, what card reader you have? also not working too. 1 minute ago, ic005k said: My machine is DELL 7472, please see the screenshot below for details. Everything works fine now, including the SD card still being loaded automatically after waking up from sleep with the SD card inserted. randomly success. almost get blackscreen after wakeup. Link to comment Share on other sites More sharing options...
ic005k Posted September 7, 2021 Share Posted September 7, 2021 The EFI I use is here. https://github.com/ic005k/DELL7472/releases/download/20210907/EFI.zip Link to comment Share on other sites More sharing options...
ic005k Posted September 7, 2021 Share Posted September 7, 2021 5 minutes ago, Sherlocks said: randomly success. almost get blackscreen after wakeup. Maybe need to wait for the author to update this kext again... 2 Link to comment Share on other sites More sharing options...
gnpaone Posted September 7, 2021 Share Posted September 7, 2021 1 hour ago, Sherlocks said: also not working too. After lots of experimenting with the settings, it's still not working. But I found one thing, when waking up it powers on everything like cpu fans ramp up, sdcard reader and usb gets power, the laptop detects the peripherals connected including sdcard, it tries to initialise sdcard, but I think some code is in a infinite loop after initialising/while initialising the card during wake up from sleep, maybe if there is a way to delay that process by milliseconds so that the process starts just after waking up instead of starting the process parallel @Austere.J. After lots of research apple says Failure code:: 0x00000000 0x0000001f occurs only in MacBook Pro 16 inch versions and it occurs due to various peripherals (when plugged in)(in this case it's card reader) not powering up properly in various cases and in response apple has asked users to disable power nap and apple has delayed starting of those kexts by milliseconds during wake to overcome that issue. It's clear from @ic005k EFI config that it is Macbook Pro 15 inch so working fine. One question, Users facing this issue using Macbook 16 inch? On 8/30/2021 at 4:13 PM, gnpaone said: Sleep Wake failure in EFI Failure code:: 0x00000000 0x0000001f Please IGNORE the below stackshot ================================================================ Date/Time: 2021-08-30 16:02:01.336 +0530 OS Version: ??? ??? (Build ???) Architecture: x86_64 Report Version: 32 Data Source: Stackshots Shared Cache: 0C9EB0DE-F5CE-3AFC-8F08-0C6DB1E7FC44 slid base address 0x7fff20061000, slide 0x61000 Event: Sleep Wake Failure Duration: 0.00s Steps: 1 Boot args: -wegnoegpu msgbuf=10485760 chunklist-security-epoch=0 -chunklist-no-rev2-dev Time Awake Since Boot: 21s Process: swd [363] Architecture: x86_64 Footprint: 380 KB Time Since Fork: 0s Num samples: 1 (1) Thread 0x94e 1 sample (1) priority 4 (base 4) <thread QoS background (requested background), thread darwinbg, process darwinbg, IO tier 2> 1 start + 1 (libdyld.dylib + 89917) [0x7fff2038af3d] 1 1 ??? [0x109d20454] 1 1 ??? [0x109d201e8] 1 1 __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 146934) [0x7fff2035cdf6] 1 *1 ??? [0xffffff80002331f6] 1 *1 ??? [0xffffff800094001e] 1 *1 ??? [0xffffff800084a211] 1 *1 ??? [0xffffff800025651f] 1 *1 ??? [0xffffff800028d86d] (running) 1 Binary Images: 0x7fff20339000 - 0x7fff20368fff libsystem_kernel.dylib (7195.141.2) <B51DEA59-1260-35C6-B7B6-AA6D8459ECEC> /usr/lib/system/libsystem_kernel.dylib 0x7fff20375000 - 0x7fff203b0fff libdyld.dylib (852.2) <11007DE4-ABE1-3079-BF1C-4D0EADA884DD> /usr/lib/system/libdyld.dylib 1 hour ago, Sherlocks said: randomly success. almost get blackscreen after wakeup. It's the same black screen I face everytime. 1 Link to comment Share on other sites More sharing options...
Austere.J Posted September 8, 2021 Author Share Posted September 8, 2021 @Sherlocks @gnpaone @whatnameisit Based on your kernel panic reports, I think you guys all have the same issue. In theory, that page fault should never happen. I need more information, so please try this experimental build under the following scenarios. RealtekCardReader_0.9.7_a359519+EXPSL_DEBUG.zip Scenario 1: 1) Boot your computer without the SD card. 2) Put your computer into sleep. 3) Wait for a while, say 5 minutes, and wake up the computer. --> Check: Can you wake up the computer properly? Is there a kernel panic? 4) If not, insert your card and check whether the card is working properly. 5) If everything is working fine, you do not need to dump the kernel log. Scenario 2: 1) Boot your computer without the SD card. 2) When you see the desktop, insert the SD card. Your card should be working properly. 2) Put your computer into sleep with the card inserted. Do not remove the card while the computer is sleeping. 3) Wait for a while, say 5 minutes, and wake up the computer. Do not remove the card after the computer wakes up. --> Check: Can you wake up the computer properly? Is there a kernel panic? 4) If there is no kernel panic, dump the kernel log now. Is your card mounted automatically after the computer wakes up? (Probably not at this moment.) 5) If the card is not mounted, remove the card and insert it back. You should be able to see your card now. If you observe any kernel panics, please reboot your computer and dump the IOReg before and after the card is inserted. -------------------------------------------------------------------------------- @mnfesq @SavageAUS Now it's a known, common issue that cards cannot be initialized with RTL8411B card reader. I will review the controller code when I am available. @Fortitude Yes, this time it's better. Your kernel logs report several errors, but I think the fatal one is that the driver fail to tune your UHS-I card. Please try again with the boot argument `-iosd3v3` to initialize the card at 3.3V. Do you have other cards to test with? I am a little busy recently, so I may not respond timely. 1 1 Link to comment Share on other sites More sharing options...
SavageAUS Posted September 8, 2021 Share Posted September 8, 2021 Yeah I tried the latest Realtek + Friend kexts with no luck. Will wait for you to update for our chips. Appreciate your work. If I can help by providing anything for 8411 let me know. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
Sherlocks Posted September 8, 2021 Share Posted September 8, 2021 2 hours ago, Austere.J said: @Sherlocks @gnpaone @whatnameisit Based on your kernel panic reports, I think you guys all have the same issue. In theory, that page fault should never happen. I need more information, so please try this experimental build under the following scenarios. RealtekCardReader_0.9.7_a359519+EXPSL_DEBUG.zip 220.36 kB · 4 downloads Scenario 1: 1) Boot your computer without the SD card. 2) Put your computer into sleep. 3) Wait for a while, say 5 minutes, and wake up the computer. --> Check: Can you wake up the computer properly? Is there a kernel panic? 4) If not, insert your card and check whether the card is working properly. 5) If everything is working fine, you do not need to dump the kernel log. Scenario 2: 1) Boot your computer without the SD card. 2) When you see the desktop, insert the SD card. Your card should be working properly. 2) Put your computer into sleep with the card inserted. Do not remove the card while the computer is sleeping. 3) Wait for a while, say 5 minutes, and wake up the computer. Do not remove the card after the computer wakes up. --> Check: Can you wake up the computer properly? Is there a kernel panic? 4) If there is no kernel panic, dump the kernel log now. Is your card mounted automatically after the computer wakes up? (Probably not at this moment.) 5) If the card is not mounted, remove the card and insert it back. You should be able to see your card now. If you observe any kernel panics, please reboot your computer and dump the IOReg before and after the card is inserted. -------------------------------------------------------------------------------- @mnfesq @SavageAUS Now it's a known, common issue that cards cannot be initialized with RTL8411B card reader. I will review the controller code when I am available. @Fortitude Yes, this time it's better. Your kernel logs report several errors, but I think the fatal one is that the driver fail to tune your UHS-I card. Please try again with the boot argument `-iosd3v3` to initialize the card at 3.3V. Do you have other cards to test with? I am a little busy recently, so I may not respond timely. thank you i tested attached file. here is process. 1. boot macos without inserted sdcard. 1. rtsx-boot-withoutsdcard.log 2. go sleep without inserted sdcard, then wakeup without inserted sdcard. it's no problem. 2. rtsx-afterwakeup_withoutsdcard.log 3. no reboot and no shutdown. go sleep again with inserted sdcard, then wakeup with inserted sdcard. get normal screen. it is no problem. 3. rtsx_afterwakeupwithsdcard, it works.log 4. go sleep again with inserted sdcard(i didn't touch sdcard after inserted 1 time), then wakeup, i got black screen. i can't get kernel panic log. just black screen thanks in advance. Link to comment Share on other sites More sharing options...
Fortitude Posted September 8, 2021 Share Posted September 8, 2021 Adding `-iosd3v3` seemed to do the trick! My SD is now being mounted. There’s just one problem though… The read/write speeds of my SD card are incredibly slow compared to Windows. I’ve attached another kernel log with an SD card inserted and -iosd3v3` added. rtsx-5260 Slow Read:Write.log Aside from that, the driver seems to be very stable! Thank you so much for taking the time to write this driver! If it helps, the only SD card that I have is this one, but I’m happy to buy any others in the future that you’d recommend for testing: Link to comment Share on other sites More sharing options...
gnpaone Posted September 8, 2021 Share Posted September 8, 2021 (edited) 20 minutes ago, Fortitude said: Adding `-iosd3v3` seemed to do the trick! My SD is now being mounted. There’s just one problem though… The read/write speeds are incredibly slow compared to Windows. @Fortitude Well, the benchmarking method of CrystalDisk is different compared to BlackMagic Disk benchmark, so please try CrystalDisk available for mac AmorphousDiskMark.app.zip Edited September 8, 2021 by gnpaone Link to comment Share on other sites More sharing options...
Fortitude Posted September 8, 2021 Share Posted September 8, 2021 (edited) Here's my results of AmorphousDiskMark when my SD card is inserted into the internal card reader: And here's my results when attaching my SD card to a USB adapter and running the Blackmagic Disk benchmark again: Read/Write speeds are much slower than they should be in the internal card reader. Edited September 8, 2021 by Fortitude Link to comment Share on other sites More sharing options...
gnpaone Posted September 8, 2021 Share Posted September 8, 2021 19 minutes ago, Fortitude said: I attached my SD card to a USB adapter and ran the Blackmagic Disk benchmark again. No not like that, I mean use the app provided by me earlier to test in Mac, just for apples to apples comparison as windows results were posted by you already. I gave the same app. Blackmagic speed test is a bit complicated, for example your first and second pictures show different levels of the test so definitely the speed indication is different for different levels and the test order is not standard. Link to comment Share on other sites More sharing options...
gnpaone Posted September 8, 2021 Share Posted September 8, 2021 (edited) 4 hours ago, Austere.J said: Scenario 1: 1) Boot your computer without the SD card. 2) Put your computer into sleep. 3) Wait for a while, say 5 minutes, and wake up the computer. --> Check: Can you wake up the computer properly? Is there a kernel panic? 4) If not, insert your card and check whether the card is working properly. 5) If everything is working fine, you do not need to dump the kernel log. Scenario 2: 1) Boot your computer without the SD card. 2) When you see the desktop, insert the SD card. Your card should be working properly. 2) Put your computer into sleep with the card inserted. Do not remove the card while the computer is sleeping. 3) Wait for a while, say 5 minutes, and wake up the computer. Do not remove the card after the computer wakes up. --> Check: Can you wake up the computer properly? Is there a kernel panic? 4) If there is no kernel panic, dump the kernel log now. Is your card mounted automatically after the computer wakes up? (Probably not at this moment.) 5) If the card is not mounted, remove the card and insert it back. You should be able to see your card now. If you observe any kernel panics, please reboot your computer and dump the IOReg before and after the card is inserted. @Austere.J I did test the kext provided by you. There are pretty interesting results this time. Scenario 1: Everything went well and Mac behaved normally. Nothing unusual. So here it works fine. Scenario 2: Here's where the twist occurs. I did tests two times (well the reason is only to gather IOReg dumps with and without sdcard inserted during force reboot after kernel panic as you asked in the last). This time the kernel log is very different compared to kernel logs provided by all of us in earlier posts. As commented by @Sherlocks in the last comment (well I am online when he is posting 😉), I got the black screen similar to him (screenshot is uploaded) but not even once it woke from sleep with sdcard inserted (both tests - first is putting my Mac to sleep without shutting down my Mac after Scenario 1 (it's the same case as said by @Sherlocks where he told his Mac woke from sleep with sdcard inserted), second is formally shutting down my Mac after Scenario 1 and following the steps mentioned in Scenario 2). General log (same as before): Sleep Wake failure in EFI Failure code:: 0x00000000 0x0000001f Please IGNORE the below stackshot ================================================================ Date/Time: 2021-09-08 15:56:36.662 +0530 OS Version: ??? ??? (Build ???) Architecture: x86_64 Report Version: 32 Data Source: Stackshots Shared Cache: 0C9EB0DE-F5CE-3AFC-8F08-0C6DB1E7FC44 slid base address 0x7fff20109000, slide 0x109000 Event: Sleep Wake Failure Duration: 0.00s Steps: 1 Boot args: -wegnoegpu msgbuf=10485760 chunklist-security-epoch=0 -chunklist-no-rev2-dev Time Awake Since Boot: 21s Process: swd [367] Architecture: x86_64 Footprint: 400 KB Time Since Fork: 1s Num samples: 1 (1) Thread 0x97b 1 sample (1) priority 4 (base 4) <thread QoS background (requested background), thread darwinbg, process darwinbg, IO tier 2> 1 start + 1 (libdyld.dylib + 89917) [0x7fff20432f3d] 1 1 ??? [0x106499454] 1 1 ??? [0x1064991e8] 1 1 __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 146934) [0x7fff20404df6] 1 *1 ??? [0xffffff80002331f6] 1 *1 ??? [0xffffff800094001e] 1 *1 ??? [0xffffff800084a211] 1 *1 ??? [0xffffff800025651f] 1 *1 ??? [0xffffff800028d86d] (running) 1 Binary Images: 0x7fff203e1000 - 0x7fff20410fff libsystem_kernel.dylib (7195.141.2) <B51DEA59-1260-35C6-B7B6-AA6D8459ECEC> /usr/lib/system/libsystem_kernel.dylib 0x7fff2041d000 - 0x7fff20458fff libdyld.dylib (852.2) <11007DE4-ABE1-3079-BF1C-4D0EADA884DD> /usr/lib/system/libdyld.dylib Model: MacBookPro16,1, BootROM 1554.100.64.0.0, 4 processors, Quad-Core Intel Core i5, 2.4 GHz, 16 GB, SMC Graphics: kHW_IntelUHDGraphics630Item, Intel UHD Graphics 630, spdisplays_builtin Memory Module: BANK 0/ChannelA-DIMM0, 8 GB, DDR4, 2666 MHz, 0000 Memory Module: BANK 2/ChannelB-DIMM0, 8 GB, DDR4, 2666 MHz, SK Hynix AirPort: spairport_wireless_card_type_airport_extreme (0x8086, 0x84), itlwm: 2.0.0 fw: 48.1335886879.0 Bluetooth: Version 8.0.5d7, 3 services, 26 devices, 1 incoming serial ports Network Service: Wi-Fi, AirPort, en1 Serial ATA Device: CT1000MX500SSD1, 1 TB USB Device: USB 3.1 Bus USB Device: Bluetooth HCI USB Device: USB2.0 HD UVC WebCam USB Device: USB2.0-CRW Thunderbolt Bus: Detailed Kernel logs: First test: panic(cpu 4 caller 0xffffff800b47100e): RTSX: Assertion triggered in file /Users/FireWolf/Library/Mobile Documents/com~apple~CloudDocs/Workspace/RealtekCardReader/RealtekCardReader/IOSDHostDevice.cpp at line 123 Backtrace (CPU 4), Frame : Return Address 0xffffffa0ac9bba10 : 0xffffff800568e04d mach_kernel : _handle_debugger_trap + 0x3fd 0xffffffa0ac9bba60 : 0xffffff80057d4e13 mach_kernel : _kdp_i386_trap + 0x143 0xffffffa0ac9bbaa0 : 0xffffff80057c540a mach_kernel : _kernel_trap + 0x55a 0xffffffa0ac9bbaf0 : 0xffffff8005632a2f mach_kernel : _return_from_trap + 0xff 0xffffffa0ac9bbb10 : 0xffffff800568d86d mach_kernel : _DebuggerTrapWithState + 0xad 0xffffffa0ac9bbc30 : 0xffffff800568db63 mach_kernel : _panic_trap_to_debugger + 0x273 0xffffffa0ac9bbca0 : 0xffffff8005e9dc0a mach_kernel : _panic + 0x54 0xffffffa0ac9bbd10 : 0xffffff800b47100e science.firewolf.rtsx : __ZN14IOSDHostDevice20onSDCardRemovedGatedEPN8IOSDCard10CompletionE + 0xae 0xffffffa0ac9bbd80 : 0xffffff800b475033 science.firewolf.rtsx : __ZN27RealtekCardReaderController20onSDCardRemovedGatedEPN8IOSDCard10CompletionE + 0x53 0xffffffa0ac9bbdb0 : 0xffffff800b47d6bd science.firewolf.rtsx : __ZN30RealtekUSBCardReaderController22fetchDeviceStatusGatedEP18IOTimerEventSource + 0xbd 0xffffffa0ac9bbde0 : 0xffffff8005df47e5 mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0xa5 0xffffffa0ac9bbe50 : 0xffffff8005df46e6 mach_kernel : __ZN18IOTimerEventSource17timeoutAndReleaseEPvS0_ + 0xc6 0xffffffa0ac9bbe80 : 0xffffff80056d4605 mach_kernel : _thread_call_delayed_timer + 0x4a5 0xffffffa0ac9bbef0 : 0xffffff80056d5574 mach_kernel : _thread_call_delayed_timer + 0x1414 0xffffffa0ac9bbfa0 : 0xffffff800563213e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: science.firewolf.rtsx(0.9.7)[EF48247F-5F33-3113-8BD3-35CAFB2C6FE3]@0xffffff800b452000->0xffffff800b558fff dependency: com.apple.iokit.IOPCIFamily(2.9)[F7AA4BAF-35CF-3784-A50C-5FD9CDCBE488]@0xffffff800816c000->0xffffff8008194fff dependency: com.apple.iokit.IOStorageFamily(2.1)[6CD2A6EC-9FFC-370D-8FEE-C8016E5C6BBA]@0xffffff800826f000->0xffffff8008280fff dependency: com.apple.iokit.IOUSBHostFamily(1.2)[3FDCC3CF-64A8-3794-A52C-5D8DE43A8265]@0xffffff800848a000->0xffffff8008518fff Process name corresponding to current thread: kernel_task Boot args: -wegnoegpu msgbuf=10485760 chunklist-security-epoch=0 -chunklist-no-rev2-dev Mac OS version: 20G95 Kernel version: Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:31 PDT 2021; root:xnu-7195.141.2~5/RELEASE_X86_64 Kernel UUID: FECBF22B-FBBE-36DE-9664-F12A7DD41D3D KernelCache slide: 0x0000000005400000 KernelCache base: 0xffffff8005600000 Kernel slide: 0x0000000005410000 Kernel text base: 0xffffff8005610000 __HIB text base: 0xffffff8005500000 System model name: MacBookPro16,1 System shutdown begun: NO Panic diags file available: YES (0x0) Hibernation exit count: 0 System uptime in nanoseconds: 137200185708 Last Sleep: absolute base_tsc base_nano Uptime : 0x0000001ff1c4b6fe Sleep : 0x0000001fc97bdd35 0x0000000773a1c748 0x0000000000000000 Wake : 0x0000001fcb90d17c 0x000000010a0bbdc4 0x0000001fc9f87ddd Second Test: panic(cpu 2 caller 0xffffff8006e7100e): RTSX: Assertion triggered in file /Users/FireWolf/Library/Mobile Documents/com~apple~CloudDocs/Workspace/RealtekCardReader/RealtekCardReader/IOSDHostDevice.cpp at line 123 Backtrace (CPU 2), Frame : Return Address 0xffffffb0bc633a10 : 0xffffff800108e04d mach_kernel : _handle_debugger_trap + 0x3fd 0xffffffb0bc633a60 : 0xffffff80011d4e13 mach_kernel : _kdp_i386_trap + 0x143 0xffffffb0bc633aa0 : 0xffffff80011c540a mach_kernel : _kernel_trap + 0x55a 0xffffffb0bc633af0 : 0xffffff8001032a2f mach_kernel : _return_from_trap + 0xff 0xffffffb0bc633b10 : 0xffffff800108d86d mach_kernel : _DebuggerTrapWithState + 0xad 0xffffffb0bc633c30 : 0xffffff800108db63 mach_kernel : _panic_trap_to_debugger + 0x273 0xffffffb0bc633ca0 : 0xffffff800189dc0a mach_kernel : _panic + 0x54 0xffffffb0bc633d10 : 0xffffff8006e7100e science.firewolf.rtsx : __ZN14IOSDHostDevice20onSDCardRemovedGatedEPN8IOSDCard10CompletionE + 0xae 0xffffffb0bc633d80 : 0xffffff8006e75033 science.firewolf.rtsx : __ZN27RealtekCardReaderController20onSDCardRemovedGatedEPN8IOSDCard10CompletionE + 0x53 0xffffffb0bc633db0 : 0xffffff8006e7d6bd science.firewolf.rtsx : __ZN30RealtekUSBCardReaderController22fetchDeviceStatusGatedEP18IOTimerEventSource + 0xbd 0xffffffb0bc633de0 : 0xffffff80017f47e5 mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0xa5 0xffffffb0bc633e50 : 0xffffff80017f46e6 mach_kernel : __ZN18IOTimerEventSource17timeoutAndReleaseEPvS0_ + 0xc6 0xffffffb0bc633e80 : 0xffffff80010d4605 mach_kernel : _thread_call_delayed_timer + 0x4a5 0xffffffb0bc633ef0 : 0xffffff80010d5574 mach_kernel : _thread_call_delayed_timer + 0x1414 0xffffffb0bc633fa0 : 0xffffff800103213e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: science.firewolf.rtsx(0.9.7)[EF48247F-5F33-3113-8BD3-35CAFB2C6FE3]@0xffffff8006e52000->0xffffff8006f58fff dependency: com.apple.iokit.IOPCIFamily(2.9)[F7AA4BAF-35CF-3784-A50C-5FD9CDCBE488]@0xffffff8003b6c000->0xffffff8003b94fff dependency: com.apple.iokit.IOStorageFamily(2.1)[6CD2A6EC-9FFC-370D-8FEE-C8016E5C6BBA]@0xffffff8003c6f000->0xffffff8003c80fff dependency: com.apple.iokit.IOUSBHostFamily(1.2)[3FDCC3CF-64A8-3794-A52C-5D8DE43A8265]@0xffffff8003e8a000->0xffffff8003f18fff Process name corresponding to current thread: kernel_task Boot args: -wegnoegpu msgbuf=10485760 chunklist-security-epoch=0 -chunklist-no-rev2-dev Mac OS version: 20G95 Kernel version: Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:31 PDT 2021; root:xnu-7195.141.2~5/RELEASE_X86_64 Kernel UUID: FECBF22B-FBBE-36DE-9664-F12A7DD41D3D KernelCache slide: 0x0000000000e00000 KernelCache base: 0xffffff8001000000 Kernel slide: 0x0000000000e10000 Kernel text base: 0xffffff8001010000 __HIB text base: 0xffffff8000f00000 System model name: MacBookPro16,1 System shutdown begun: NO Panic diags file available: YES (0x0) Hibernation exit count: 0 System uptime in nanoseconds: 459801982129 Last Sleep: absolute base_tsc base_nano Uptime : 0x0000006b0e557c7a Sleep : 0x0000006ae5f45f96 0x0000000767c2c9ee 0x0000000000000000 Wake : 0x0000006ae80ad7da 0x000000010a043356 0x0000006ae6705ceb It says last sleep: absolute, that means sleep function is executed successfully, so no problem during sleep, problem is during wake. Both detailed reports are different (first line) so I posted it seperately. This time the log says which line in which file created kernel panic, I think this maybe helpful. Note: All the logs and IOReg dump and screen captures are uploaded below. rtsx-a359519.zip Edited September 8, 2021 by gnpaone 1 Link to comment Share on other sites More sharing options...
Recommended Posts