MP 1,1-5,1 Innie: A fix for PCI drives seen as external

[GSXB]

So I followed all steps and after reboot no dice. I’m getting ready to throw in the towel!

Try this for the last command
sudo kextcache -system-prelinked-kernel

 

[cdf]

So I followed all steps and after reboot no dice. I’m getting ready to throw in the towel!

There is a lot of troubleshooting information in this thread. A good place to start is #155.

 

[srecoatings]

So I don’t know what happened? I did have to reformat my NVME drive to APFS for Adobe CC! After I restored install, I tried steps on #9 and it worked 1st time! Thank you @cdf & @GSXB!

 

[GSXB]

I’ve installed Catalina DP 10 with dosdude patcher and no patches lilu,innie and appleALC all working. I have HDMI sound and an internal pci M.2 👍

 

[Adam Chuan]

It is well known that macOS sees PCI drives in a cMP as external. In the past, there have been several attempts to fix this annoyance, typically through codeless kexts and driver patches. However, these approaches are far from perfect.

Codeless kexts affect the properties of all (even non-PCI) drives. We therefore have to settle for calling all drives SATA or PCI. Patches can be dangerous, especially if applied to critical kexts. After system updates, these modifications can prevent the system from booting. There are also bootloader approaches, but these are better suited for hacks and not real Macs.

The problem is not just cosmetic. Improperly identified drives can cause issues for Boot Camp Assistant and the macOS installer.

I am currently working on an actual kext that addresses the problem. The kext simply changes the pertinent properties of PCI drives so that they can be seen as internal. So far, the approach works nicely with the 256 GB Apple SSUBX and the 240 GB Kingston HyperX Predator, the drives which I possess. This is how the drives now appear, for example, under Storage in About this Mac:

View attachment 780549

If there is interest in the community for the kext, I will make it available. However, to support other drives, particularly NVMe ones, I would need the names of PCI drives reported in System Information:

View attachment 780555

And, of course, some brave testers. Let me know if you're interested!

Current device list: Innie should now work with any SATA (AHCI) or NVMe drive.

Please refer to Post #9 for the kext and installation instructions.

Does it can work in MacOS 10.14.6?
And the NVMe SSD can be full speed or not?
Because the PCI Express will be internal in MacOS?

 

[GSXB]

Does it can work in MacOS 10.14.6?
And the NVMe SSD can be full speed or not?
Because the PCI Express will be internal in MacOS?

Yes it works in macOS 10.14.6
Just follow post 9 and run this command as well
sudo nvram boot-args="$(nvram boot-args | sed $'s/boot-args//;s/\t//g') -lilubeta -inniebeta"
It’s cosmetic, and it will run at the correct speed

 

[Adam Chuan]

[QUOTE =“ Gboyartis，帖子：27751968，成員：1191246”]
當它寫到4時，它說innie複製到了插件...而我不知道哪個innie是.....我
[/引用]

Yes it works in macOS 10.14.6
Just follow post 9 and run this command as well
sudo nvram boot-args="$(nvram boot-args | sed $'s/boot-args//;s/\t//g') -lilubeta -inniebeta"
It’s cosmetic, and it will run at the correct speed

Thanks for your reply.
Dose the cosmetic can write in after post 9 cosmetic?

Yes it works in macOS 10.14.6
Just follow post 9 and run this command as well
sudo nvram boot-args="$(nvram boot-args | sed $'s/boot-args//;s/\t//g') -lilubeta -inniebeta"
It’s cosmetic, and it will run at the correct speed

Thanks for your reply.
Can I write all cosmetic together or not ?

 

[cdf]

Does it can work in MacOS 10.14.6?
And the NVMe SSD can be full speed or not?
Because the PCI Express will be internal in MacOS?

Yes it works in macOS 10.14.6
Just follow post 9 and run this command as well
sudo nvram boot-args="$(nvram boot-args | sed $'s/boot-args//;s/\t//g') -lilubeta -inniebeta"
It’s cosmetic, and it will run at the correct speed

As a clarification: The beta command is only needed for macOS 10.15. For 10.14.6, the steps in post #9 should be enough. Also, Innie is actually more than cosmetic; there are some useful consequences of making startup disks internal. For a recent example, see post #256. Disk speed, however, should not be affected. It should be the same as it was before Innie.

 

[GSXB]

Installing macOS Catalina DP11 as I type. I will report later on lilu and innie.
UPDATE: lilu, innie and appleALC installed and working I have Correctly identified pci m.2 and HDMI sound👍

 

[scopemonkey]

Once the kext installed, SIP can indeed be re-enabled.

A quick question: I have Lilu with Innie installed on my cMP 4.1 flashed to 5.1. I followed the instructions in post #9 and all worked well. However whenever SIP is turned back on, Lilu and Innie get disabled. The only way I can get them to stay loaded is to disable SIP. Is there a work around for this, or do we actually need to leave SIP disabled?

 

[alphascorp]

Hi everybody,
Lilu 1.3.8 with Innie 1.0.9 (built-in) works fine in Catalina 10.15 (19A583), my 2 NVMe SSD are seen as internal disks.

 

[GSXB]

A quick question: I have Lilu with Innie installed on my cMP 4.1 flashed to 5.1. I followed the instructions in post #9 and all worked well. However whenever SIP is turned back on, Lilu and Innie get disabled. The only way I can get them to stay loaded is to disable SIP. Is there a work around for this, or do we actually need to leave SIP disabled?

Boot into recovery open terminal and run these commands
csrutil enable --without kext
csrutil enable --without fs
this will partially enable SIP and leave lilu and innie alone

 

[pascalsrumours]

I have a Samsung SSD 970 EVO Plus 500GB, is that covered?

 

[cdf]

I have a Samsung SSD 970 EVO Plus 500GB, is that covered?

Yes, Innie should work with any PCI drive.

 

[alphascorp]

I have a Samsung SSD 970 EVO Plus 500GB, is that covered?

Hi @pascalsrumours,

I have the same SSD model as you and I use Lilu 1.3.8 with Innie 1.0.9 that work fine on Mojave since 10.14 until the last supplemental update 10.14.6 (18G103).

That work fine too with Catalina 10.15 but you need to use a code line in Terminal after SIP disabled. For this code see @cdf's message #202 and mine #212, #225, #226

 

[pascalsrumours]

thanks @cdf @alphascorp ! is there a single page as a guide as alot going on everywhere couldnt see instructions..

 

[crjackson2134]

thanks @cdf @alphascorp ! is there a single page as a guide as alot going on everywhere couldnt see instructions..

You are obviously not reading the posts he pointed out. I don’t even need or use this but it’s very plainly shown. Please read those posts, it doesn’t need to be a spoon fed thing.

 

[alphascorp]

@pascalsrumours
If this is the detail of the manipulation you are looking for please read @cdf's message #9 on the first page of this post.

 

[pascalsrumours]

@pascalsrumours
If this is the detail of the manipulation you are looking for please read @cdf's message #9 on the first page of this post.

That was it. Thank you. @alphascorp

 

[SamPotts]

Has anyone tried this on a 2013/6,1 with the AngelShark Carrier Board? It'd be great if the two extra drives were internal so I could use them for Bootcamp.

 

[mani girafe]

Hello, I see my disk externally, does the procedure ( post #9) also work under HIGH SIERRA? thank you for your answer

 

[cdf]

Hello, I see my disk externally, does the procedure ( post #9) also work under HIGH SIERRA? thank you for your answer

Yes.

 

[mani girafe]

Yes.

Merci beaucoup

 

[GSXB]

Installed Catalina with the supplemental update reapplied the terminal commands and all working

 

[mani girafe]

yes it's good for me

intel SSD DC S3500 Series 1.6TB
+ SEDNA Pci Express PCIe