arsradu

@Baio77 Any idea what's going on with the Realtek SD Card Reader kext? panic(cpu 2 caller 0xffffff801d380f9d): Wake transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: science.firewolf.rtsx. Thread 0x3c19. Does it work properly on your hack? What am I missing here? It looks like I'm not the only one with this issue though. And seems to be occurring only with somewhat newer OSes. So, while the driver works...and so far seems to be the only one that actually works, this issue makes me disable the kext for the time being. Cause it crashes in the middle of doing something. Probably only after sleep (since this points to a wake issue) Any idea what could cause this or how to fix it? By the way, the Fn keys issue still occurs. And I can't figure out what causes it. What I noticed is that, after opening the laptop, the Fn key LED indicator blinks once, and that's it. And none of the Fn keys work anymore after that. Update: sp yeah, this seems to only occur after waking from sleep. All good for 3 minutes. After 3 minutes, which seems to be the timeout above, computer restarts, or shuts down completely.

Hey guys, Is there a way to check if you have any conflicts in your ACPI patches? Or maybe something missing there? How would you go about debugging this?

Yeah, that's what I was about to post. Looks like what I want to achieve can't be achieved with only ACPI patches. So yes, ThinkpadAssistant brings back the rest of the functionality. Thank you! Edit: alright. So all the customisations work properly, with ThinkPad Assistant. Everything that's supposed to work, works. Which is great. However, the very first thing that made me open this thread...which is its functionality after waking from sleep, still doesn't. I'm sure there's something that's supposed to do this check, and it fails, but I don't know what am I doing wrong.

Thank you, Herve! Yeah, for some weird reason, the RealtekCardReader kext doesn't show good results in my tests. And apparently I'm not the only one. Searching for a solution, I found more people having the same problem. :)) Which didn't help at all, but at least I know I'm not the only one. Apparently the issue started with Sonoma (maybe Ventura as well...?). So yeah, unfortunately until someone updates/fixes that kexts, that's not gonna be an option for me. Weird thing Sinetek's rtsx kext doesn't work anymore... That was weird. It used to work. Now it just doesn't recognize the card, doesn't pop-up on the Desktop... Weird. As for the FN Keys, I already got volume working, screen brightness adjustments (no backlit keyboard on this one unfortunately, so nothing to fix there) and App Switcher on F11. I was curious if there's a way to map the microphone mute key to its original functionality and of course, maybe fix the sleep issues as well. Anyway, I'm guessing your FN keys don't stop working after sleep, right? Could be something specific to ThinkPads or Lenovo hacks in general. I saw some people having the same issue, unfortunately no clear solution. That's why I was thinking maybe, since this is a hackintosh forum dedicated to laptops (yes, mostly Dells, but I saw a bunch of Lenovos as well), maybe someone found a fix for it. You know what? I'm gonna browse a little bit, maybe someone, with a similar Lenovo already found and fixed the issue. Just not present anymore on the forum. Once again, thank you Herve!

Yeah, the "Friend" kext, as far as I know, is only to make it show up in System Report > Card Reader. Which now it does (if it's placed before the regular one). But I'm having the exact same crash with or without it. So, pretty sure that's not why it crashes. What kind of device properties do you inject for your RTS525A? Are they only cosmetic? If there anything I can apply/adapt to mine? The fact that it shows "unassigned class" in Hackintool (by the way, is it the same for yours?) kinda bothers me. But not because I'd care so much about the estetic part of it, but just in case it might have something to do with the crash I'm experiencing when using this kext. It doesn't happen only during sleep, it also happens during normal use. So this is probably not sleep related (unlike the other issues I've mentioned above). As for the FN keys, have you tried mapping yours or just didn't bother with that? I tried to set up the ACPIDebug thing....but I'm probably doing it wrong or something, cause it doesn't show anything in Console log, and I've read somewhere that from 10.12 (if I remember correctly) you can't use this method anymore. So...I don't know what else can I use. As far as I can tell, the keyboard is sending ACPI code, not PS2 scan code. But...I couldn't figure what should I set so that it does what I want. And also, more importantly, how to have it functional after sleep! I'm pretty sure there's a patch or something. But this is all very new to me. I've spent the last few days learning about ACPI, DSDT, SSDT, patching one or the other (which is definitely NOT for the faint of heart). Still...I can't figure out how (or IF) this can be done at all. I've seen some patches, and even some of my experiments seem to have worked (for example F11 does call for App Switcher, which makes me think it should be possible to also call for some of the other ones), but I can't figure out which codes to use for those. Anyway, thank you so much for your feedback so far.

So far so good! Thank you! I'll use it for a while, and see if it still crashes or something. The actual SD Card functionality seems to be working well so far. I used the RealtekCardReader + its Friend. My card reader is an RTS5227 and seems to be supported, so I didn't get the Generic one, since I don't think that applies in this case, right? I could be wrong. As I said, this is my first laptop hack, and it's proven to be a real challenge from the beginning. :)) Only thing (and I'm only mentioning this since I know this is its purpose), the card reader is still not recognised in System Profiler (says card reader not present or something). I should also mention that Hackintool itself doesn't quite properly recognise this either(unassigned class). So that might have something to do with it. Anyway, I think these are cosmetic issues. I'm most interested in the kext not crashing my system every once in a while. :)) And....so far so good. Thank you! Update: sadly, that didn't work. It still crashes. Update 2: looks like the Friend kext needs to be placed before the other kext, in order for the device to be recognised in System Report. Update 3: now the system doesn't wake from sleep anymore (wake to black screen). After a while, system reboots. Seems to be the same cause. When it comes to laptop hacks, looks like everything is trying to break sleep...or something. Anything. :))

Hey Herve! Indeed. Sorry about that. Typing this late at night was apparently not the best idea. :)) I might actually add an installation guide for this model, since it doesn't seem to be present so far on the forum, once I manage to fix everything. So far, there are a couple of things I'm not quite happy about. The FN keys issue is one of them. But also, I've got a weird issue with the SD card reader. Initially I tried Realtek Card Reader kext, but that was creating some weird sudden reboots and KPs. Could be because the driver hasn't been updated in a while, and I'm using it on Sequoia. Could be something else. I don't know. So I switched to Sinetek's driver, but that doesn't seem to work at all...anymore, for some reason. So...just a cuple of things to iron out. Good thing is that most important things do work: so, graphics acceleration, WiFi and Ethernet work, built-in audio, BT, Airdrop, Continuity features, basic sleep/wake and (I think) hibernation, as well. So most of the things already work fine. I've got some weird issues with trackpad scrolling, but not sure there's anything that can be done here. And the issues above. Anyway. For the FN keys thing, there are third party options, such as Karabiner-Elements. And that works properly before and after sleep. Also, you can add shortcuts from System Settings as well... But I wanted to do something built-in...if possible, but that proves to be challenging.

Hey guys, So, this is my first time hackintoshing a laptop, and...needless to say, it wasn't easy. Now, I'm almost done with it, most of the things work (more or less) and I'm struggling to understand how to map all my function keys to something as close as possible to the actual marking on the keys, but from MacOS. And...I've got some success... Like F1-F3 work fine for Mute and Volume keys. F5-F6 work for Brightness (which is what most people want), and F11 works for App Switcher (Expose). So, the idea would be to have the Mic on/off switch on F4, Multi Display switch for example (on F7), WiFi on/off switch (on F8), System Settings (on F9), Spotlight (on F10) and Launchpad (F12) However, none of these work anymore after waking from sleep. And it seems to be a pretty common issue. Not sure if it's a common issue on all laptops trying to map their FN keys, or specific to ThinkPads. Anyway, if you guys have any feedback here, I'd really appreciate it. Thank you so much!

Sorry, Hervé. Didn't even realise I was using quote. Ok, will try to pay more attention to that. Thanks for pointing it out and editing to remove those quotes. @theawesomerb, in my experience, no, it's not. I mean, usually, at least for desktops, there are very few changes to make to the config (if any), from one version of MacOS to the other. And from Mojave to Catalina for example I don't think I had to change anything in the config. So no, it's not really common, at least on desktops. Could be be pretty common for laptops though.

:)) Told you it's probably easier this way. Well, at least in my opinion, it is. Stuck at that point, usually (at least in my experience) signifies an issue with FakeSMC/VirtualSMC. For as far as I can see, you chose to use VirtualSMC.kext. No problem with that (unless for some reason your laptop prefers FakeSMC.kext instead), but I think, for this case, you might also need the VirtualSMC.efi drier in drivers/UEFI. Seems to be missing in your case. Now, of course, I could be wrong and this might be an entirely different issue. Just sharing my own experience in case it helps.

Did you try gibMacOS? It has versions for both Windows and Mac. You just need the Windows version, of course. For editing the config.plist, you can use ProperTree. If you don't want to use gibMac to add Clover to the USB drive, you can use cvad's BDU instead. So, you can use gibMacOS to make the installer and BDU to add the bootloader. ProperTree if you need to edit the config.plist. Unfortunately I don't have much experience with laptops. And I don't have a Dell Latitude 3350. But the process should be pretty much the same. At least to get you booting. For Wifi, BT, trackpad, brightness control and other wonders, you might need extra kexts or SSDTs. But the idea is to get you booting first. To me, it's still easier to do it from MacOS itself (even if it's virtualised) than Windows. But that's probably just me. So, to make the USB drive, you don't actually need the latest and greatest MacOS. So...you can try to download an already made vmdk with let's say Sierra or something (again, it doesn't need to be the latest version). You can try this one just as an example. If that doesn't work, you can try to google virtual disk image macos. One of them should work. After that, you have a lot of options for creating and managing the USB installer. You can either download the installer App directly from the App Store, or use dosdude1's Catalina Patcher (you don't actually need the "patcher" part of it, just to download you the installer). After that you can use the Terminal to format the USB drive and put the installer onto it using Apple's own createinstallmedia method. I mean, the possibilities are endless. And for the Clover part of the USB drive, since you're on MacOS environment, you can use Clover Configurator to both download Clover and manage the config.plist file So, as you wish. You've got a lot of options.

For what i know, it's downloading the original image from Apple. So that's good. And it should also offer the possibility to add Clover or OC to it. Give it try.

If you're doing this from Windows (which I assume you do), but also if you have another MacOS installation or VM, you can use this little tool to download and create a bootable drive for MacOS. Just make sure you get the one marked as "full install". Also, if you have Clover on a USB drive and you can boot with it, you can also check its version by pressing A when reaching the GUI, to access the About menu.

I'm sure you did, and I have a guess as to where you might have seen them. Having all the kexts in EFI/Clover/kexts/Other is easier to manage, and you can keep the system intact. Also, if I'm not mistaken, during the update, you rely entirely on the EFI partition. So...if you don't have your mandatory kexts there, you can't boot. Easy as that. Update: I don't know, man. I never had any issues having all the kexts in Clover/kexts/Other. Also, because of that, I have no such errors when I try to rebuild caches. And I don't wanna keep VirtualSMC/FakeSMC in EFI and everything else in other places. It's just not organised this way. And I tend to forget which kexts I have where. So I just have them all in one place. Easier this way.

Yes, my recommendation would be to always keep your kexts in Clover/kexts/Other, not L/E or S/L/E, unless there's really no other way around it (usually, there is). The errors are normal when you put your kexts in L/E or S/L/E. However, that doesn't look like an update issue. Is this from the installer log or something? The errors you get are from the commands above.

I don't know how moving kexts from Clover/kexts/10.15 into Clover/kexts/Other (not all in /kexts) would cause that error...but ok. :)) Anyway, I've never seen that disk issue in my entire life. It doesn't recognise any drives. Not just NVME. There's no EFI partition, nothing. Can you post a screen of your Disk Utility window? I'm guessing you're trying to boot off of the USB now?

Could you post the output of diskutil list here? You still haven't renamed your drivers (for example NvmExpressDxe-64.efi to NvmExtressDxe.efi), and you still have kexts in both 10.15 and Other. Also, can you boot without those patched SSDTs? Cause what I would do is first remove them all, see if I can boot, then only add the ones I absolutely know I need.

Yeah, so, if I'm not mistaken, Clover will first look into your specific folders. For example, if you're using Catalina, it will look under 10.15. The problem is, all your important kexts are in Other. Now, the point of the multiple folders for each version is to allow you to separate your kexts for different versions of MacOS. But if you don't need different kexts for different versions, there's no point to keep them separated. That's why, when you use the same kexts for all versions, you put them in the Other folder (and remove them from the dedicated folder). Also, if I'm not mistaken (I honestly don't know if this is accurate, so apologies if it isn't), if you use the custom folders (in this case 10.15) the Other folder (which you actually want in this case) will be ignored. So that's why I said either one or the other, not both. Cause I'm not sure if Clover will actually get to the Other folder if you already have kexts in 10.15. Or anyway, I think one of them will not be used. Again, I could be wrong. As for NVMe, as much as I would love to help you, I can't, cause I don't have an NVMe drive... I'm sorry. The only thing I was suggesting is maybe...if you don't need both (which it could happen for some kexts) to maybe try only one or the other, in case they create conflicts.

@komand Any reason why you have kexts in both /10.15 and /Other folders? Why not have them all in the same place (in /Other)? Or remove the ones from 10.15 if you already have them in /Other. Having them in both places is not a good idea. It's either one or the other. Not both. Also, are all those SSDTs in ACPI/patched really patched? You have a TON of them. I doubt you actually need all of them. Also, you should only have AML versions of those. Not sure if DSLs actually affect it in any way...but..you don't need those. :)) The files are decompiled anyway when you open them in MaciASL. So no need to keep both AML and DSL. Also, you're using a driver (NvmExpressDxe) and a kext (NVMeFix) for NVME... I don't have an NVMe drive, but...is that intended? I'm just wondering whether or not it creates conflicts. Also, doesn't Catalina come with built-in support for NVME? Or is it just for specific models? I thought I read something about this somewhere else. But it was probably only for some specific models. Anyway, if it doesn't show your NVMe drive in Disk Utility, that's probably a driver issue. So first the drive should be visible there, then we can worry about formatting it as APFS/HFS+. Try without the driver in drivers/UEFI, ooor without the "Nvmefix" in /kexts. See if maybe they're conflicting with each other. And see if using any of them actually makes that drive show up in Disk Utility. Also, not sure which Clover that is, but you don't need the "-64" suffix for your drivers anymore. Since Clover only comes in 64-bit by default. Actually, I would rename all of them just to be sure.

Forget about the laptop, have you seen the view? How can I get a house in the trees? I'd love that! I love nature. Anyway, yeah, congrats on the build. Looking good!

Good question. The point of the empty folders is to allow you to separate your kexts for each version of MacOS, in case you need different kexts for different versions. If you use the same ones, obviously there's no need for those and you can put all your kexts in the /Other folder. As for the other question, that's why it would have been a lot easier to just compare your config to the one that Jake linked on the previous page. For as far as I can tell, it's the same laptop model. So...chances are it might work without any modifications. Same for ACPI files. The kext miight need a bit of dusting off. :)) But...again, I think it would still be easier than trying to fiddle around with that menu. I took some time to update the EFI folder from the archive on the thread Jake suggested before. You should now have updated Clover, kexts, drivers. Config and patched SSDT and DSDT have been kept the same. See if you can boot with this one. Also, the config doesn't change as much as you might think between versions. So it's not like you need a separate config for each version. And yes, that menu is just for testing different stuff. The changes won't be saved. EFI.zip

Hey! I don't have that laptop. Just an idea. Have you tried using Lilu + WEG + correct ig-platform-id instead? Here's the list of all available ig-platform-ids. Try to use some of the default ones. Make a separate config for testing only Mojave, and select it from Clover GUI (I think it's under Options). This way you can always boot back to El Cap. If you need to replace/update kexts, my recommendation would be to work on a USB drive, where you can test whatever you need, instead of your main partition. Also, you might want to uncheck Inject Intel in Clover config and do your configuration from Devices -> Properties. Here all you need is to add your iGPU device address (usually PciRoot(0x0)/Pci(0x2,0x0) ) on the left, and on the right, "AAPL,ig-platform-id" as the key, and the value need to be in reversed bytes depending on your actual framebuffer. Type DATA. For example, for HD4000, you could try one of these: 0x01660003 (default), 0x01660009, 0x01660004. And the way you add them in config is, for example for 0x01660003 -> 03006601 (no "0x"). Read from right to left, in pairs of two. As I said, I don't have that laptop, aaand I know it's usually not an easy task to get a laptop to run macos, buuut...I think it might be doable. Especially if you already have a working system. All you have to do is get your graphics fixed. So if you have old kexts like IntelGraphicsFixup or whatever the name was, you might wanna remove that and use Lilu + Whatevergreen instead. Make sure they're also updated. You can use Clover Configurator for that. Wish you good luck!

All empty folders except /Other is intended. You can even remove those folders if you want. But...you don't see a need for kexts? :)) Unfortunately, you will need a couple of those if you want to boot. The log mentions something about unsupported CPU. So I'm guessing, some of the things in config, or maybe one of the kexts, could help with that. If you want, you can remove information from smbios and upload your EFI to take a closer look. There's not much you can do from that menu.

Actually, I've read the same thing on other forums. So...you might not be the only one with this issue. Weird... Maybe broken package? Idk... I used every beta since 10.15.4 to 10.15.5 final and no issues updating. So it could be that the 10.15.5 update introduced something new, and only creates issues when upgrading from 10.15.4 (probably older, too)...? No idea. Anyway, glad you managed to get it installed. Using the full installer was indeed the right call. Enjoy!

@spidey123 It has. Patching the original AppleHDA kext is a pretty bad way to get sound working. :)) But it is/was commonly used on other forums for a while. So, I get where you're coming from. But also, as you noticed, you don't need that anymore. With this method (Lilu + AppleALC + layout-id), AppleHDA stays the same and the updates don't break sound anymore. Enjoy!