Jump to content

Lenovo ThinkPad L450 - from unable to boot OC to an (almost) perfect Sequoia Hackintosh


81 posts in this topic

Recommended Posts

5 hours ago, LockDown said:

You must not have AppleIntelitlwm or itlwm installed.

Im not at home atm. Il get back to you asap.

 

Can you try removing the /(pci(0x0,0x0) 

 

You mean AirportItlwm? Is so, I tried that, and without it, i get the wifi icon with the exclamation mark and I can't switch it on or off anymore.

 

Also it doesn't make a difference to the device properties injection.

However, what did make a difference (unfortunately still hasn't let me apply the patch) was removing the /(pci(0x0,0x0) part. With that removed, device properties seem to get injected properly in IOreg. Still...OCLP doesn't want to recognize that and allow me to patch.

6 hours ago, LockDown said:

for a start:

 

Screenshot 2025-07-10 at 8.20.34 AM.png

Screenshot 2025-07-10 at 8.21.37 AM.png

Screenshot 2025-07-10 at 8.22.59 AM.png

 

Screenshot 2025-07-10 at 8.31.22 AM.png

 

It couldn't be clearer. And I thank you very much for your time and effort in trying to help. :) 

 

However...(believe me, I didn't want to be a "however" anywhere in this message :)) :

  • I can only inject the IOName if the PCI path is without /Pci(0x0,0x0). If I use the full path, as mentioned in Hackintool, only the model (such as "BCM4360 Wireless Network Adapter") gets injected. The most important ones (and especially the IOName), do not. 
    Ok, no problem, we use the "short path".
  • With the "short path", the device properties get injected and show up properly (as far as I can tell) ONLY in IOreg. They do not show up like in your screenshot, in Hackintool.
    So, in IOreg, I have IOName: pci14e4,43a0, in Hackintool, I have: pci8086,95b.
  • With the kexts in the order you mentioned above, I get the exclamation mark on the WiFi icon and can't switch it on or off. But, at this point, I think that's not really important.
  • As a result of the above, OCLP still doesn't detect, nor propose any kind of wireless patching.

I think there might be something else going on here, but I just can't put my finger on it.

 

Update: the problem seems to be the PCI path. I don't know what exactly yet, but I'll look into it.

Update2: yeah, the PCI path is the one with 0x0 at the end. But the problem is, aside from Model, nothing gets injected there. Something probably rewrites it.

Edited by arsradu
  • Like 1

Hi

is your usb mapped properly?

 

IIRC, all you need is just the IONAME & AMFIPass for starter. Install the rest of the kexts once OCLP has been applied. At least thats what i did.

Edited by LockDown
  • Like 1
4 hours ago, LockDown said:

Hi

is your usb mapped properly?

 

IIRC, all you need is just the IONAME & AMFIPass for starter. Install the rest of the kexts once OCLP has been applied. At least thats what i did.

Well...I don't know about USB...I didn't notice any issues with that, so I haven't checked, but why would that affect WiFi?

Also, I did try to remove pretty much everything except for PS2Controller kext, Lilu, VirtualSMC, WEG, and AMFIPass. The issue is still the same. Can't seem to be able to inject those values.

Can you please, tell me which kexts you're using? And also which SMBIOS, just in case that makes any difference? I tried MacBookPro15,1 or something like that, since MacBookPro12,1 was not supported by Sequoia.

Anyway, this is really weird. But since it works in your case...I'm hoping maybe there is a way to get mine to work, as well.

The pic iv shown you was from my Desktop1 which is iMac20,1

I have a laptop that also has AC7265 and used to be MacBooKPro15,1 until Tahoe came and is now MacBookPro16,2

 

Dektop1 is running Clover while Laptop is now in OC ( i have yet to update my sig).

But regardless of bootloader & smbios, both works with AC7265

 

For the USB mapping, macOS didnt recognize the card until i mapped it. Could it be because of being a combo 🤔

Edited by LockDown
  • Like 1
59 minutes ago, LockDown said:

The pic iv shown you was from my Desktop1 which is iMac20,1

I have a laptop that also has AC7265 and used to be MacBooKPro15,1 until Tahoe came and is now MacBookPro16,2

 

Dektop1 is running Clover while Laptop is now in OC ( i have yet to update my sig).

But regardless of bootloader & smbios, both works with AC7265

 

For the USB mapping, macOS didnt recognize the card until i mapped it. Could it be because of being a combo 🤔

Ok...but in my case it does recognize it in Hackintool... It recognizes it too well. :)) If anything, I'm trying to make it not recognize it, so I can convince OCLP to patch it. :))

 

Anyway, I'll check out USB mapping as well, just in case. :)

12 hours ago, LockDown said:

For the USB mapping, macOS didnt recognize the card until i mapped it. Could it be because of being a combo 🤔

@arsradu

I mean, Hackintool or gfxutil shows its Device Path. lspci can see it, but nothing in Hackintool > System >Peripherals

Edited by LockDown
  • Like 1

Well, look who decided to show up? :D 

image.png.5fc5681da6fa42732f879030a390f9eb.png

Looks like I wasn't doing anything wrong. I was just not doing everything I should do in order to get that device recognized. But yeah, I'm typing this from this laptop, with AirportItlwm (I've also tested Itlwm + Heliport and those work perfectly fine as well, but the challenge was to make AirportItlwm work).

Now, BT seems to pose some difficulties as well. But...all in good time. :) 

 

For anyone wondering, I had to use SSDTTime to add the device path and create an SSDT-Bridge.aml to inject through OC. Apparently OC can patch a device if it's already defined, but it won't add it if it's not already present. OC Docs have been proven to be really useful on this journey. :) 

 

So..another milestone completed successfully. :) 

  • Like 2

By the way, guys. I read somewhere that with AirportItlwm you can't use iMessage anymore. I'm happy to tell you I have no such issue and if there is indeed an issue like this, it might not be related to AirportItlwm. :) Could be SMBIOS, could be config, could be something else, but it worked fine for me.

7 hours ago, arsradu said:

 I read somewhere that with AirportItlwm you can't use iMessage anymore. I'm happy to tell you I have no such issue and if there is indeed an issue like this

well done!

others were having issues with it. Have you tried sending message?

Edited by LockDown

Another day, another challenge, another milestone completed.

BlueTooth and (surprisingly) Camera are now working, as well, after mapping my USB ports. Yep, USB ports are related to both BlueTooth and Camera functionality. So I used corpnewt's USBMap script to map my USB ports, create a USBMap.kext file and use it to enable my ports, and with them, BT and Camera. :D 

 

List of things "not working" is getting smaller and smaller every day. And that's awesome! First laptop to hackintosh, and I wish it was just another walk in the park. But nope, laptops are hard. Or at least harder than Desktops to hackintosh. But when you do manage to make them work, they also bring a bigger smile on your face. :D 

Edited by arsradu

And now, card reader works as well with the help of a small efi driver from OcBinary repo. This device is using id 10ec,5227 and someone was kind enough to provide a driver for it. :)

Edited by arsradu
  • Like 1
7 hours ago, LockDown said:

Link please?

 

Update; got it! Thanks

Yesterday I wanted to post a link and for some reason the forum didn't post my message. Then I posted from my phone, but forgot to add the link. :))

 

Anyway, even though you found it, here's the link for reference.

Anyway, I'm planning to either open a new topic or edit this one to include everything that works/doesn't work/hasn't been tested, and also add references to the files I used. So yeah, they will be all in one place.

Because, while this has been a fun and challenging project, looks like it's going to its end, and I'm not sure I will continue to use this particular laptop on MacOS. I already have a lot of Macs and Hacks around. This one I bought for Windows, but I thought: oh, what the hack, let's see if we can make this run MacOS, as well. The answer is: yes, yes you can. :)) At this point, pretty much everything works, and things that don't yet, are really not really important and also, I'm not sure they can be fixed...but yeah, we'll see, so I just need to maybe clean up some things, optimize some things, and we can wrap it up. :) 

 

Edit: before that, I need to see if there's a better trackpad driver or something. Scrolling is kinda weird with this one. But as I said, these are smaller things to fix. 

 

Edit2: forgot to mention, for the SD Card Reader you'll also need this kext. I think the efi is mainly if you want to boot OC from an sd card.

 

Edited by arsradu

Hey guys!

 

So...BT is fixed, Camera is working... However, I seem to have gotten a new issue, and from what I could read online, it might be derived from the USB patching I've done. And I'm not sure exactly what could be the issue, since the patching seems ok...or at least I think so...

 

So, the issue is that the laptop won't go into sleep anymore, and if I close the lid, when trying to wake it up, it stays in a black screen, and the only way to get it back is to force reboot it.

 

I've tested to see if the issue is the USBMap kext and looks like it is... Meaning, with it disabled, the issue does not occur. But of course, that also means no BT and no Camera. :))

 

Have you guys encountered this issue before? Any idea how to fix it...?

 

I have to admit this whole USB patching is really new to me, but I've tried both Corpnewt's USBMap and Hackintool, to fix this issue.

So...I think...the patching was done correctly, especially since the USB ports are working fine after patching, it's just this weird and kind of annoying issue of the laptop not going into sleep anymore, and when trying to open the lid and wake up the screen, the screen stays black. 

 

I also tried USBTookBox on Windows, but...although the process seemed easier, the actual kexts don't seem to have the desired result... Meaning it doesn't work, and also, seems to cause some weird slowdowns upon boot.

 

Occasionally I've also encountered freezes. Like randomly. When trying to click or something, it would just freeze. Might be the same issue, but we won't know until I fix it.

Edited by arsradu

Thank you Anto! But...isn't that for newer CPUs/iGPUs? Like Skylake and above? This one is using a Broadwell CPU.

 

Anyway, I'll give it a try, just in case. :) 

 

By the way, this also occurs with the USBDummy.kext itself. Which makes me think it's not my patching that's wrong, it's probably something else...

 

Update: that (force-online=01000000) unfortunately didn't help. As far as I can tell by the red light on the lid of this laptop (nice addition, I'll be honest), the laptop does try to go to sleep, but it wakes up and stays up immediately after. If I were to open the lid in the first probably 30 seconds or so before it goes to sleep, I think it would work. But if I do it after it goes to sleep, when I try to open the lid, I get a black screen and I have to force reboot.

 

Anyway, thank you very much for your feedback! I'll try to look around for some potential solutions to this (weird) issue. :)) 

Edited by arsradu

Hey guys,

 

Have any of you seen this thing in your attempt to "discover" all USB ports and create a USBMap kext?

What the *#@#!(# is that?!

Should I ignore it, should I disable? This USB thing is super confusing to me right now.

image.png.96ccd47edbfa93b42af7e2e20ef4f502.png

3 hours ago, arsradu said:

Hey guys,

 

Have any of you seen this thing in your attempt to "discover" all USB ports and create a USBMap kext?

What the *#@#!(# is that?!

Should I ignore it, should I disable? This USB thing is super confusing to me right now.

 

Hubs are not controllers, so why does it care?

 

Can you figure out what that hub is connected to?

 

7 hours ago, joevt said:

 

Hubs are not controllers, so why does it care?

 

Can you figure out what that hub is connected to?

 

 

Well, this one is marked as an Hub-1d100000 Controller. Whatever that means. Is it a controller linked to another controller? Controller-ception?

This is what USBMap script has to say about it.

image.png.52ea2a6bf5bdb471ec2f8b18741bc31c.png

This is what the IOreg has to say about it.

image.thumb.png.73a92c087538f326bc0cc73a17e3e4a2.png

Mind you this is after port limit reduction and all that, so it's with USBMap.kext already in place. But it's the same with USBDummy. Just... more ports.

 

By the way, if you want to read something super cool, super informative (sadly not so much for me, since it seems to be targetted more towards Desktops, but still, the same knowledge applies to Laptops, as well), and it's also super light and funny to read, I wholeheartedly recommend taking a read at this: https://usb-map.gitbook.io/project/terms-of-endearment

Edited by arsradu

@arsradu , I can't really help with port mapping. Last time I did it was 8 years ago.


EHCI is USB 2.0. USB 2.0 controllers usually don't have 17 ports. What's going on there? You need some kind of port limit for that controller as well? Usually port limit is only for XHCI chipset controllers. Has anyone done port limits for multiple controllers in the same hackintosh? You need to map port 17 of this controller to a different port number.

 

When searching in IORegistryExplorer.app, it helps to delete the search text after you select the item you were searching for, so you can see more devices related to the selected device.

 

PR17 and PRT1 both have location 1d1 because 17 mod 16 = 1 (macOS allows port numbers between 1 and 15). When USB mapping is correct, you will not have devices with duplicate location hex strings.

 

The two left most digits of the location string represents the host controller location (XHCI is at 0x14 and EH01 is at 0x1D where 0x14 and 0x1D are PCIe device numbers? The rest of the digits in the location hex string are port numbers (if they are between 1 and 15) or 0 which ends the location string.

 

Edited by joevt
  • Like 1
×
×
  • Create New...