-
Posts
10027 -
Joined
-
Last visited
-
Days Won
561
Content Type
Profiles
Articles, News and Tips
Forums
Everything posted by Hervé
-
attachements need to be zipped.
-
Last update: 20 July 2017 For those who need an extracted copy of Sierra kernels to build their manual Chameleon/Enoch-based USB installers, here are copies of the various kernels that have come out so far. I also include copies of the patched AppleIntelCPUPowerManagement kexts that are necessary on SandyBridge/IvyBridge CPUs. Patches courtesy of Pimentel and his tools as published at IM. Vanilla kernels for Core2Duo/Core2Quad, Arrandale and Sandy/Ivy Bridge CPUs: Vanilla_kernel_10.12.zip (Darwin 16.0.0) Vanilla_kernel_10.12.1.zip (Darwin 16.1.0) Vanilla_kernel_10.12.2.zip (Darwin 16.3.0) Vanilla_kernel_10.12.3.zip (Darwin 16.4.0) Vanilla_kernel_10.12.4.zip (Darwin 16.5.0) Vanilla_kernel_10.12.5.zip (Darwin 16.6.0) Vanilla_kernel_10.12.6.zip (Darwin 16.7.0) Patched kernels for Haswell, Broadwell, Skylake CPUs: N/A (Clover and Enoch can patch the vanilla kernel on the fly) Patched AppleIntelCPUPowerManagement kexts for Sandy/Ivy Bridge CPUs: Patched_AICPUPM_10.12.zip Patched_AICPUPM_10.12.1.zip Patched_AICPUPM_10.12.2.zip Patched_AICPUPM_10.12.3.zip Patched_AICPUPM_10.12.4.zip Patched_AICPUPM_10.12.5.zip Patched_AICPUPM_10.12.6.zip NB: kernels go to /System/Library/Kernels as kernel; patched AICPUPM kext goes to /System/Library/Extensions
- 1 reply
-
- 13
-
-
-
Moving from Chameleon/Mavericks to Clover/Sierra on Dell XPS 210
Hervé replied to sbhachu's topic in The Archive
Erm, for the kernel, do not use El Capitan's, obviously! Use Sierra's. Arf, never posted them... Bear with me... -
VoodooSDHC is known to cause Wake issues. I know of no fix unfortunately. That's why we've been lucky the DSDT patch to inject compatibility with Apple's device works on the Latitude Series. Good luck with your future experimentations.
-
The IOReg shows various devices under PCIE@1E: * ethernet@0 -> Broadcom LAN card * CRD0@1 -> Ricoh Co Ltd R5C832 IEEE 1394 Controller (1180,832) * FRWR@1,4 -> Ricoh Co Ltd xD-Picture Card Controller (1180,852) so DSDT _DSM method seems inappropriate to me then 3 x Ricoh devices: * 1180,822@1,1 -> Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter * 1180,843@1,2 -> Ricoh Co Ltd R5C843 MMC Host Controller * 1180,592@1,3 -> Ricoh Co Ltd R5C592 Memory stick Bus Host Adapter In the DSDT, only CRD0, FRWR and CRD1 are defined. You do not necessarily need to inject anything for those missing devices in the DSDT. The LAN card is the vey proof of it; you just need the correct driver. Use DPCIManager->PCI List tab to identify which kext is used for each device. You may have to add the other device 843 + 592 to the kext too. Experiment... I take it you initially worked according to this, right? This being said, you could also give a try to a DSDT Patch that injects a device for the card reader and declares it compatible with Apple's default SD card reader. This would be placed alongside the existing devices under PCIE and would look like this: Device (SDXC) { Name (_ADR, 0x00010001) Method (_INI, 0, NotSerialized) { SMI (0x95, 0x04) // or SMI (0x9D, 0x04) } Name (_S1D, Zero) Name (_S3D, 0x03) Method (_DSM, 4, NotSerialized) { Store (Package () { "device_type", Buffer () { "Media controller" }, "AAPL,slot-name", Buffer (0x09) { "Built-in" }, "model", Buffer () { "Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter" }, "compatible", Buffer () { "pci14e4,16bc" }, }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } No guarantees of course, these are just pointers/ideas for experimentation... I've got one question though: is the DSDT you posted of Inspiron1720 origin or does it come from another computer like the D630 (because it really looks like it does!)? I would not mind the raw table...
-
Your SSD is partitioned MBR so you will need to apply the MBR patch in order to be able to install OS X on that disk. Yes, you can normally install OS X and Windows on the same disk in a dual-boot arrangement. Clover will support this. Have a look at Jake's guide for the installation process and necessary files. No need to re-invent the wheel. Note that it's the same process between El Capitan and Sierra.
-
It's the exact same model as fitted to the good old D430: D430_ML:~ admin$ lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03) 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) 00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 01) 00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 1 [8086:27d0] (rev 01) 00:1c.1 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 2 [8086:27d2] (rev 01) 00:1c.2 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 3 [8086:27d4] (rev 01) 00:1d.0 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 [8086:27c8] (rev 01) 00:1d.1 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 [8086:27c9] (rev 01) 00:1d.2 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 [8086:27ca] (rev 01) 00:1d.3 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 [8086:27cb] (rev 01) 00:1d.7 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller [8086:27cc] (rev 01) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev e1) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge [8086:27b9] (rev 01) 00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 01) 00:1f.3 SMBus [0c05]: Intel Corporation N10/ICH 7 Family SMBus Controller [8086:27da] (rev 01) 02:01.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev b4) 02:01.1 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C552 IEEE 1394 Controller [1180:0552] (rev 09) 02:01.2 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 18) 09:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express [14e4:1600] (rev 02) 0c:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11a/b/g [14e4:4312] (rev 01) D430_ML:~ admin$ From memory, we could get it detected through VoodooSDHC kext but could not get it to work properly because the device apparently shares an IRQ with the Ethernet. I cannot say whether it would be the same on the 1720 of same generation but an older VoodooSDHC kext may work provided it can load under Sierra. Griftopia, try this fat binary kext: VoodooSDHC.kext.zip
-
Moving from Chameleon/Mavericks to Clover/Sierra on Dell XPS 210
Hervé replied to sbhachu's topic in The Archive
Alternatively, you can simply switch to latest Enoch bootloader and retain all your existing Chameleon setup. The differences will be: the new kernel.plist in /Extra (with specific new kernel parameters) the need to copy (not move) kexts to /Library/Extensions to load/cache them (kext from /E/E will only be injected if new boot option KernelBooter_kexts=Yes is used. Useful as a backup when you want to boot without cache which ignores /L/E...) ideally remove defacto-obsolete myHack.kext in /S/L/E You can check my D630/E6220/E6230 guides for El Capitan to that effect (Sierra uses exact same process). -
Just a little update after all this time: the patch still runs in El Capitan and Sierra. NB: Rather than patch CellPhoneHelper directly or use a patched copy of the kext, the patch can also be added as an entry to FakeSMC Info.plist and Bob's your uncle! No need to patch the kext any more, except if the kext Info.plist file gets syntax changed throughout OS X versions of course...
-
Don't confuse the HDD partition scheme (the type of partitioning) and the partition formatting (NTFS, OS X Journaled, etc.). OS X default partitioning scheme is GUID whereas, with Windows, it used to be MBR. MBR is not natively supported by OS X, hence my asking. If you can boot your OS X USB installer, the Disk Utility will show you the current scheme.
-
A few questions: 1) what is the SSD current partition scheme? 2) are you using Clover or Enoch bootloader? 3) what BIOS mode do you currently run (legacy or UEFI)?
-
Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter https://pci-ids.ucw.cz/read/PC/1180/0822 May work with VoodooSDHC kext but it'll need patching with PCI ids.
-
I run Sierra on all my Hacks, yes. I used the TrackPad pref pane of 10.11.6 and the binary exec from Dr Hurt to retain the settings.
-
Try and replace your BatteryManager kext by Rehabman's latest version 1.7x.x
-
Forget about SSDT tables. I've just checked your initial set of 1720 files again and the devices EHC1/EHC2 are defined in your DSDT. I don't know how you could have walked past them. You should know what to do now...
-
You can extract your raw BIOS tables from Windows using tools such as AIDA64. If you're using Clover, press F4 at main menu and the extracted files will go the the Clover EFI/Clover/ACPI folder.
-
If you'll only have OS X on the HDD, partition it GUID.
-
I think you're mistaken. Chameleon systematically loads by default any DSDT file called "DSDT.aml" found in /Extra folder. There is no need to reference it in the boot plist. How did you setup your HDD in terms of partition scheme and formatting? Should be respectively GUID (not MBR) and OS X Extended (journaled).
-
On occasions, USB ports are defined in a SSDT table. If you've already extracted them all, check them out. Otherwise, extract all your SSDT raw tables from BIOS.
-
This is strange because I understood the E6440 and E7440 have the exact same TouchPad. Try and remove your patched PrefPane to see if it makes any difference.
-
Guys, you can safely use this revised PS2 Controller kext (Release 4) recently re-written by Dr Hurt. I recommend you move all your add-on kexts to /L/E then repair permissions and rebuild your cache rather than inject them through Clover EFI partition. It's quicker in terms of startup.
-
Use Dr Hurt's latest (Release 4, posted yesterday). Should work perfectly on your E7440. It certainly does on my E6440.
-
With Chameleon, you need to manually install the Haswell-patched kernel in /S/L/K. Copies of each kernel are available here. If you switch to Enoch, you'll be able to keep the vanilla kernel as long as you set KernelPm parameter to Yes in the kernel.plist file.
-
No it does not make a difference, it's perfectly Ok to do such a swap. You just need to use the HiRes DSDT, that's all.
-
I don't know why you kept using KextWizard or whatever tool when all you had to do was copy/paste the kext to SLE or LE then repair whichever folder's permissions and rebuild the cache.