polyzargone

What about adding this patch in Kernel and Kext Patches ? Name : AppleUSBXHCIPCI Find : 83BD74FF FFFF10 Replace : 83BD74FF FFFF1F Comment : 10.12 change 15 port limit to 20

As you can see in the screenshot, it's the NVIDIA model . Intel's X3100 is unsupported on Sierra so I hope you get the right model if you plan to install it. Also, make sure the CPU is Penryn otherwise you'll be stuck at El Capitan 10.11. Mine is a T9300 for instance.

Yes, it works fine.

Maybe this one ? VoodooTSCSync.kext I'm surprised you need this though. Usually, this kext is used on AMD Systems. Never heard it was on Dell Dxxx !

Cool ! Actually, this is the same exact CLOVER_Sierra.zip than the one I posted in post #74 .

Post #9 updated with working Clover .

Well it looks like the problem is with your hard disk to me… disk2s2 I/O error Will work with Enoch, won't work with Clover . As I already said here, Clover won't boot at all with a MacBookPro5,1 profile on Sierra. I suspect it reads some files that Enoch doesn't and unless these files are modified, Clover won't boot Sierra. Fusion17au at InsanelyMac may have a solution though. I didn't tried myself but it may works :

Or this new one : CLOVER_Sierra_v2.zip

Strange… OK, let's try something : Re-install Clover on the USB pen and replace these 2 folders by the ones from CLOVER_Sierra.zip : • ACPI/patched • Kexts/Other Ad of course, config.plist. I'm not sure the CLOVERX64.efi is really up to date and maybe it's an old version that doesn't work anymore. If I'm correct, there were changes in Sierra DB2/3 that made Clover unable to load and inject kexts.

No, you shouldn't and it (should) be OK as it. From the screenshot you posted, my read is that you have a problem with the infamous "still waiting for root device" error. Usually, this happens when something's wrong with USB. So if you didn't changed anything in the CLOVER_Sierra.zip, I think it's because you're using the wrong port. I'm pretty sure that during the install process, the only one that works is the upper right-hand side. Have you tried it ?

@Tuurbo : Did you modified the config.plist in any way to suit your needs ? Especially the SMBios ?

Last time I had to "cook" it was in december. So far, so good. But again, it's not a permanent fix so I've got my fingers crossed Bon appétit !

USE AT YOUR OWN RISK ! I have the same issue on mine. One solution is to bake the mobo. It's not a permanent fix but it has been working pretty good for me so far. First, make sure you disassembly entirely the D830. Here's a good video : Don't forget any part including CPU, RAM additional cards, plastic caches etc. and clean the graphics chip too ! Then put the mobo into your Owen for about 5/7 min at 200° Celsius maximum (do the conversion if needed). Good luck !

Yes it should if you only use Enoch . If you use Clover, you can't go back to MBP5,1 SMBios once Sierra is installed because it will use the boot.efi (contrary to Enoch) and say : "This version of Mac OS X is not supported" (see this post at InsanelyMac). I guess the limitation is hard-coded right in the boot.efi file so unless we find a way to patch it "on the fly", the only solution is to use a MBP7,1 SMbios or fake the board-id of the MBP5,1. So I wanted to avoid confusion with one Extra_Sierra.zip using MBP5,1 and another Clover_Sierra.zip using MBP7,1. Also, I wanted to simplify installation since using the later doesn't require the user to do anything particular. Finally, I also made a new USB_Injector.kext that works with MBP7,1. Note that it's easy to make one that works with both SMBioses but again, I wanted to make it simple.

Hello guys ! Post #9 Updated for macOS 10.12 Sierra support on eligible D830 models (see [uPDATE 3]) ! Enjoy !

OK. I agree VoodooPS2Trackpad.kext may be redundant though I haven't any issue using it so far (TBH, I hardly use the trackpad). VoodooBattery.kext works fine for me but if APCIBatteryManager.kext solves your issue that's what's counts. But I'm not sure using another config.plist is the right thing to do since it contains DSDT patches that are mandatory to make the USB_Injector works correctly. And you have to make sure that SMBios model is MacBookPro5,1 and nothing else. Also, with the help of other members, I found out that unchecking all Clover fixes solves some of the sleep issues like non-working closing LID. As a side note, there's a small error in the DSDT from original bootpack for D830 that needs to be fixed cause it may cause a black screen. And last but not least, remember that you have to set hibernate mode to 0 : sudo pmset -a hibernatemode 0 @Hervé The error in the DSDT is still present in both Clover and Chameleon 10.10 bootpacks .

Did you tried the complete set of files for Clover available here ? The only thing you'll have to edit is the model name in the provided DSDT which is really easy to do : "model", Buffer (0x17) { "NVIDIA Quadro NVS 135M" } You just have to change it to : "model", Buffer (0x17) { "NVIDIA Quadro NVS 140M" }

Seems like you have an old version of Chameleon somewhere on your drive. If you're still using partition scheme, you can try to erase the whole EFI partition (after backing up its content i.e. existing EFI folder) then reinstall Clover on it. To do so, just open a terminal and type : diskutil list then sudo newfs_msdos -v EFI -F 32 /dev/rdiskXsY Where X and Y are the numbers of your EFI partition. You may also have to try different options in the Clover installer :

Hmm… You mean you downloaded my Clover folder and replaced it with yours ?!? Nonsense ! Anyway… As stated, I just removed all fixes in ACPI Old way/New way. Nothing else. What version of Clover are you using ? You may have to move/copy all kexts from EFI/CLOVER/kexts/10.11 to EFI/CLOVER/kexts/Other. I know some versions of Clover fails to load kexts when placed in EFI/CLOVER/kexts/10.11 . All works fine here with Clover r3330. Anyway, I just uploaded a new Clover.zip with a copy of all kexts in EFI/CLOVER/kexts/Other so you can give a try. And BTW, you can still reset removed fixes in Clover's boot menu > DSDT fix mask.

Fixed ! Remove all fixes in ACPI Old way/new way and Lid close/sleep will work again and fn+esc as well. I didn't tried the ctrl/power button shortcut (is this the correct one ?) as my pwb key is a bit capricious so let me know if it work too . #9 has been edited with new Clover.zip. PS : Special thanks to Bronxteck for putting me on the path !

Yes. I don't know why .

Kernels are now available for El Capitan ! All works with latest version 10.11.2 (15C50). They're not completely perfect but they work great ! Look here. BTW, AMD kernel for Yosemite 10.10.5 (14F1021 at least - not tried with latest 14F1509) also works great .

I noticed that too. Sorry, I don't know how to fix it. It maybe Clover related… or not .

Well, actually restoring orginal DSDT from Bootpack was a mistake. First, this DSDT contains errors with Nvidia injection. It has this : "device_type", Buffer (0x0D) { "NVDA,GeForce" }, "model", Buffer (0x18) { "NVIDIA GeForce 8400M GS" } Where there should be this : "device_type", Buffer (0x0C) { "NVDA,Parent" }, "model", Buffer (0x17) { "NVIDIA Quadro NVS 135M" } Using NVDA,GeForce instead of NVDA,Parent cause black screen issues. Note that 135M can be replaced by 140M, but Quadro NVS is the standard Nvidia graphics model used in D830 Series, not the NVIDIA GeForce 8400M GS. Second, NOT renaming USBx to EHCx works fine but that's not what OS X expect. Not a big deal in Yosemite or previous OS X version since the system doesn't really care but a major issue in El Capitan because it waits for EHCx names so we can't use USBx anymore. But renaming USBx to EHCx is still not enough. If we leave EHCx as it in the DSDT, El Capitan will use this information to map USB ports number according to the SMBios he founds in AppleUSBEHCIPCI.kext inside IOUSBHostFamily.kext. And ports mapping for the MacBookPro5,1 lacks a lot of ports for a D830 Latitude. So we need to bypass the AppleUSBEHCIPCI.kext to inject our own ports mapping. That's the purpose of both renaming EHCx to EH0x and USB_Injector.kext. • The first prevents EHCx to be used by AppleUSBEHCIPCI.kext. • The later is configured to match any occurrences of EH0x in the DSDT (manually or "on the fly patched") to prevail over AppleUSBEHCIPCI.kext. That way, we can inject precisely the number and addresses of each USB port according to the DSDT, not what OS X expects to find in Apple's stock kexts. The reason why you "think" your USB ports are working well is a mystery to me. Using the untouched DSDT (USBx names) with no Clover's DSDT patch for renaming resulted in non-working USB ports at all. I've just tried to see if latest OS X versions changed something on that matter. Well obviously they don't. Perhaps you're only using keyboard and trackpad when using your D830 but I will be very surprised that connecting any USB device in one of the 3 ports of your Latitude actually works. Maybe the one on the back will but I'm pretty sure the two right-sided won't. Even if they do, you may have surprises when connecting some devices like Hard Drives, iPhone, USB sticks, etc. But again, If I do the way you do, none of the USB ports works. And of course USB_Injector.kext does nothing . You should really test all of your USB ports with various devices… I strongly advice you use the new DSDT posted in CLOVER.zip in post #9 which is corrected regarding NVDA,GeForce issue and is now clean on the WIFI side. I completely removed my own patch so you shouldn't have the issue your accurately reported . It's not the original one from EDP/Bootpack but you can see now there's a good reason why . [EDIT] Wait, maybe I read too fast. You meant that you didn't renamed UHCx but still you edited EHC1/EHC2 to EH01/EH02 ? If so, forget what I wrote. Renaming USBx to UHCx is not important. Only EHCx have to be renamed to match what USB_Injector.kext expects so I'm not surprised anymore you have no problem with your ports !

You are correct ! I made edits in the original DSDT from Bootback to match my WIFI hardware. Funny thing is that it's totally useless for me since my Atheros AR928X is natively supported . I've restored the original one in a new set of files in post #9 so everyone can use it. Thanks for reporting this mistake !