Toggle sidebar Toggle sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

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

h9826790 said:
You can boot to recovery partition with just a normal RX580, not need flashed card or original Apple card.

In some case, disconnect all monitor but only leave one attached will help (if screens stay black after boot to recover).
Click to expand...


I have never heard of this, my understanding was that if you have a non-apple flashed GPU, nothing is available until the drivers load, which is right before the login screen - perhaps I'll try it at some point...

Also, Original Apple card can also boot Mojave, and the associated recovery partition. So, you won't lose any ability to do that.
Click to expand...

AFAIK, this is wrong. Mohave requires Metal support, and the original card in this machine (5770) does not have Metal support. I know THIS for a fact as I was unable to run the firmware update that is the first part of the Mojave install because it would fail due to a non-metal supported GPU.

Regardless, its irrelevant to the issue at hand, which is now resolved.
 
djtimyd said:
I have never heard of this, my understanding was that if you have a non-apple flashed GPU, nothing is available until the drivers load, which is right before the login screen - perhaps I'll try it at some point...

AFAIK, this is wrong. Mohave requires Metal support, and the original card in this machine (5770) does not have Metal support. I know THIS for a fact as I was unable to run the firmware update that is the first part of the Mojave install because it would fail due to a non-metal supported GPU.

Regardless, its irrelevant to the issue at hand, which is now resolved.
Click to expand...

Both your undesstanding are not entirely correct.

1) You are right about non flashed card won't display anything until driver is loaded. However, you miss the fact that Recovery Partition has its own GPU driver, therefore, all natively supported non flashed card can work in Recovery Partition. The most common trouble is just some multi screen setup may not work properly in Recovery Partition. As long as only connect one monitor, Recovery Partition should always work. At least, it always work for me (non flashed HD7950, R9 280, R9 380, RX580, Radeon VII).

2) Metal supported GPU is required to install Mojave, not boot Mojave. You can't install Mojave with HD5770, but once you installed in, you can boot Mojave with HD5770 and use it normally.
 
h9826790 said:
you can boot Mojave with HD5770 and use it normally.
Click to expand...
This is valid for cards that have pre-boot configuration support, Mac EFI. A PC non-flashed HD5770 won't show any screen with Mojave. It's the EFI drivers that are used when Mojave don't support a GPU - no EFI, no screen.
 
  • Like
Reactions: h9826790
tsialex said:
This is valid for cards that have pre-boot configuration support, Mac EFI. A PC non-flashed HD5770 won't show any screen with Mojave. It's the EFI drivers that are used when Mojave don't support a GPU - no EFI, no screen.
Click to expand...

Thanks for further polish the answer. It was "his original card (5770)" in my mind when I typing the post.
 
I have the Mac EFI 5770 (the original card that came in my 5,1 cMP) - so, y'all are telling me that all of the other sources on the interwebs are wrong, and that I can just put a natively supported but non-flashed card (like the RX580) in the machine to INSTALL Mojave, but I don't need to keep it in the machine to RUN Mojave? Sorry for my skepticism, but this is the first I've heard of this, and goes against everything that I have read about Mojave absolutely REQUIRING a metal supported GPU (without workarounds and kext and whatnot).

Please, for my education, could you put some links to support this?
 
djtimyd said:
I have the Mac EFI 5770 (the original card that came in my 5,1 cMP) - so, y'all are telling me that all of the other sources on the interwebs are wrong, and that I can just put a natively supported but non-flashed card (like the RX580) in the machine to INSTALL Mojave, but I don't need to keep it in the machine to RUN Mojave? Sorry for my skepticism, but this is the first I've heard of this, and goes against everything that I have read about Mojave absolutely REQUIRING a metal supported GPU (without workarounds and kext and whatnot).

Please, for my education, could you put some links to support this?
Click to expand...
It's the EFI fall back mode, unaccelerated, and at best, you can tolerate it for text edit operations.

Any EFI GPU that is unsupported with Mojave will show a screen and it's very useful for rescue mode/debug operations, but you can't even see a video with an EFI unsupported GPU, no acceleration at all.
 
djtimyd said:
I have the Mac EFI 5770 (the original card that came in my 5,1 cMP) - so, y'all are telling me that all of the other sources on the interwebs are wrong, and that I can just put a natively supported but non-flashed card (like the RX580) in the machine to INSTALL Mojave, but I don't need to keep it in the machine to RUN Mojave? Sorry for my skepticism, but this is the first I've heard of this, and goes against everything that I have read about Mojave absolutely REQUIRING a metal supported GPU (without workarounds and kext and whatnot).

Please, for my education, could you put some links to support this?
Click to expand...

I don't know what's the original wording of "all other sources". I can't tell if they are wrong, or you misinterpret the info.

Since you have the card, you can try it yourself. You will know the answer within 5min. And no need to trust any link, or any other info. Just trust your own test result.

Anyway, there are plenty of related posts on this forum already.
 
interesting discussion, since ElCapitan I had trouble booting into USB-Installer with 2nd NON-Efi-Card
I always had to remove Nvidia non efi cards from MacPro 3,1/ 5,1 until High Sierra even with DOSdude Patcher, sometimes it did not load with 2nd non efi card until High Sierra..from USB installer.
Recovery Partitions Load with 2nd non EFI GPU since Sierra...
 
@cdf I can't get this to work for the life of me... Could you help me troubleshoot please?

Hardware:
-2009 Mac Pro 4,1, flashed to firmware 5,1.
-Adapter is OWC Mercury Accelsior S with a Crucial MX300 750GB SSD in PCIe Slot #4 (the top slot that says "x4 / RAID")
-Running High Sierra 10.13.6.

I have performed the following:

Disable SIP:
1) Reboot in recovery mode (cmd+R)
2) In recovery terminal: csrutil disable
3) In recoverry terminal: reboot
4) Computer reboots, and after login I launch terminal and just do a quick check "csrutil status" shows "disabled"

Lilu and Innie
5) Come to this thread, post #9, go to your github releases and download the following:
6) Lilu-1.4.1-DEBUG.zip
7) Lilu-1.4.1-RELEASE.zip
8) "Show Contents" of Lilu-1.4.1-DEBUG (which becomes "Lilu.kext" after it's DL'd) -- file size is 1.2MB
9) Create folder within Contents titled "Plugins" -- without "" of course, as per your instructions
10) Copy "Lilu-1.4.1-RELEASE" (which becomes "Lilu-1" after it's DL'd) into "Plugins" file within Lilu.kext above
11) Copy Lilu.kext (Lilu-1.4.1-DEBUG) to /Library/Extensions -- then authenticate

Terminal
12) in terminal:
Code: 
sudo chmod -R 755 /Library/Extensions/Lilu.kext
sudo chown -R root:wheel /Library/Extensions/Lilu.kext
sudo touch /Library/Extensions
sudo kextcache -update-volume 

Kext with invalid signatured (-67062) allowed: <yada yada yada>
KernelCache ID: 0B2D2D3 etc.../

sudo reboot

Checking if it worked
13) Computer reboots, I login -- my SSD still shows an external drive icon on desktop for the SSD...
14) in terminal: csrutil status -- still shows "disabled"
15) diskutil list -- still shows SSD as external
15) system report still shows SSD as external


Any idea where I went wrong?
Did I use the wrong Lilu.kext?
Any tips?

I am asking because in this thread there are people posting that this works on PCI SSD's, so this should work on my setup, correct?
 
Looks like you’ve copied Lilu 1.4.1 into itself. You need to copy Innie (1.2.0 (RELEASE).zip at the bottom of post #9) to Lilu>Contents>Plugins

When enabling SIP I use this command
Code: 
csrutil enable --without kext --without fs
 
Last edited:
JedNZ said:
Looks like you’ve copied Lilu 1.4.1 into itself. You need to copy Innie (1.2.0 (RELEASE).zip at the bottom of post #9) to Lilu>Contents>Plugins

When enabling SIP I use this command
Code: 
csrutil enable --without kext --without fs
Click to expand...

I did copy Innie (1.4.1 (RELEASE).zip) from his github to Lilu>Contents>Plugins, then Lilu.kext to /Library Extensions/

I tried this procedure several times, once doing a regular SIP disable, install, then enable, and another time enabling SIP with your your code, but when I entered your code, terminal said it would break eventually and cause my system to become unresponsive. (just an fyi).

Still no luck.
 
Correct me if I’m wrong but Lilu is at 1.4.1, but Innie is still at 1.2.0 Release. I suggest you download Innie 1.2.0 Release from post #9 and download Lilu 1.4.1 Release from here and go through the process again. I too am using an Accelsior S SATA III PCIe card, but with a Samsung 850 EVO, so our systems aren’t too dissimilar.
 
  • Like
Reactions: prefuse07
JedNZ said:
Correct me if I’m wrong but Lilu is at 1.4.1, but Innie is still at 1.2.0 Release. I suggest you download Innie 1.2.0 Release from post #9 and download Lilu 1.4.1 Release from here and go through the process again. I too am using an Accelsior S SATA III PCIe card, but with a Samsung 850 EVO, so our systems aren’t too dissimilar.
Click to expand...

edit: It worked! -- I also used your code when re-enabling SIP, and just fyi, it gives the following:

Code: 
-bas-3.2# csrutil enable --without kext --without fs
csrutil: requesting an unsupported configuration. This is likely to break in the future and leave your machine in an unknown state.
csrutil: requesting an unsupported configuration. This is likely to break in the future and leave your machine in an unknown state.
Successfully enabled System Integrity Protection. Please restart the machine for the changes to take effect.
-bash-3.2#

Thanks again for all your help, @JedNZ , very much appreciated!
 
Last edited:
  • Like
Reactions: cdf and JedNZ
I get that message too, and bravely ignore it. I actually updated to Lilu 1.4.0 a month or more ago and forgot to add Innie and couldn’t work out why my drives were seen as external. I only just fixed it yesterday when I worked out my mistake. I also have WhateverGreen installed for HEVC decoding - haven’t done any so don’t know if that works or not.
 
  • Like
Reactions: prefuse07
First of all: Thank you for the great work!

Unfortunately, no success here 😔

System: MacPro 7,1 @ Catalina 15.2, SIP confirmed disabled
NVMEs: 2 x Evo 970 via 2 x simple PCIe adapters (no PLX)
Lilu / Innie: 1.41 / 1.2.0
Steps: exactly Post #9, triple checked

Status: both Lilu / Innie kexts loaded, unsigned, not notarized

Couple reboots, booted and exited rescue console, not change. Drives stay external.

Any help is greatly appreciated. Thank you!


See ioreg / kextstat dump attached.

PS: Not done yet: NVRAM reset, boot args changed - since I read somewhere it's not necessary anymore on Catalina
 

Attachments

spacerunner said:
First of all: Thank you for the great work!

Unfortunately, no success here 😔

System: MacPro 7,1 @ Catalina 15.2, SIP confirmed disabled
NVMEs: 2 x Evo 970 via 2 x simple PCIe adapters (no PLX)
Lilu / Innie: 1.41 / 1.2.0
Steps: exactly Post #9, triple checked

Status: both Lilu / Innie kexts loaded, unsigned, not notarized

Couple reboots, booted and exited rescue console, not change. Drives stay external.

Any help is greatly appreciated. Thank you!


See ioreg / kextstat dump attached.

PS: Not done yet: NVRAM reset, boot args changed - since I read somewhere it's not necessary anymore on Catalina
Click to expand...
Hi spacerunner, did you enable SIP again at the end of process? I also had same status like you, but after enabling SIP and reboot, drives were internal. Anyway, I have nMP 4.1 > 5.1 with Sonnet Tempo SSD Pro. My drives were loosing write speed rapidly before this Innie magic, and since this fix couple months ago, ssd write speeds are staying at max all the time. Great! Thank you guys, you are the best!
 
  • Like
Reactions: cdf
zigund said:
Hi spacerunner, did you enable SIP again at the end of process? I also had same status like you, but after enabling SIP and reboot, drives were internal.
Click to expand...

The issue is compatibility: spacerunner has a 2019 Mac Pro.
 
  • Like
Reactions: zigund
cdf said:
The kext is called "Innie" and is a Lilu plugin. Lilu is an open-source kext that provides a unified platform to apply various fixes (see https://github.com/acidanthera/Lilu). For the latest version of Innie, I recommend the latest release version of Lilu (see the releases page).

The latest version, 1.2.0, brings support for Catalina. The previous debug version of Innie remains available.

To install Innie, please carry out these steps:

0) Disable SIP. (SIP can be enabled again after.)
1) Download Lilu. The file (unzipped) will be called Lilu.kext.
2) Control-click on Lilu.kext and select Show Package Contents. You will see the folder "Contents." Open it.
3) In Contents, create a new folder called "Plugins" (exactly like this, but without quotation marks, of course). This is where Innie (and any other plugins) will live.
4) Copy Innie into the Plugins folder.
5) Now copy Lilu.kext to /Library/Extensions. You will need to authorize this.
6) Open terminal. Enter the following commands:

Code: 
sudo chmod -R 755 /Library/Extensions/Lilu.kext
sudo chown -R root:wheel /Library/Extensions/Lilu.kext
sudo touch /Library/Extensions
sudo kextcache -update-volume /

Wait for the last command to complete.
7) Reboot.

If all goes well, your drive will now be seen as internal.
Click to expand...


I don't see any file called "innie"

is it the .dsym file?
 
See post #9 at the bottom.
1581037437875.jpeg
 
thank you got it working... last command outputted this error but



Works-Mac-Pro:~ workpro$ sudo kextcache -update-volume /


Warning: /AppleInternal/Library/Extensions: No such file or directory


Kext with invalid signatured (-67062) allowed: <OSKext 0x7fc0cf0a43f0 [0x7fff913d08e0]> { URL = "file:///Library/Extensions/Lilu.kext/Contents/Plugins/Innie.kext/", ID = "com.innieteam.Innie" }


Kext with invalid signatured (-67062) allowed: <OSKext 0x7fc0cf0a49b0 [0x7fff913d08e0]> { URL = "file:///Library/Extensions/Lilu.kext/", ID = "as.vit9696.Lilu" }


kext file:///System/Library/Extensions/PACESupportFamily.kext/Contents/PlugIns/PACESupportSnowLeopard.kext/ is in hash exception list, allowing to load


KernelCache ID: 4*************************


Works-Mac-Pro:~ workpro$


[Restored Feb 7, 2020 at 12:25:33 PM]


Last login: Fri Feb 7 12:25:31 on console


Restored session: Fri Feb 7 12:19:08 EST 2020


Works-Mac-Pro:~ workpro$
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back