-
Posts
10027 -
Joined
-
Last visited
-
Days Won
561
Content Type
Profiles
Articles, News and Tips
Forums
Everything posted by Hervé
-
There are existing threads on keyboard remapping. https://osxlatitude.com/index.php?/forum/102-keyboard-trackpadtouchpad/
-
Forget about 802.11ac cards under SL or Lion; OS X only supports this from ML 10.8.4, or 10.8.5 i.e. unreachable territories for the D630 GMA X3100. In addition, please note that the D630 only takes full-size mini-PCIe cards so you would need to add an adapter plate if you want to install a half-size wireless card. I would advise you to consider a full-size 802.11n Broadcom and/or Atheros card that'll work OOB. I can recommend Atheros AR5B91 (2.4GHz) or AR5BXB92 (2.4+5GHz). On the Broadcom side, you have the DW1505.
-
You're getting compilation error for the _OFF and _ON methods you've added because they're not declared in the DSDT but in one of the SSDTs. As such, you must declare these functions as External functions at the very top of your DSDT; you'll see similar code lines for other functions. Just copy/paste existing external declarations and adjust to _OFF/_ON functions. Should be something like: External (_SB.PCI0.PEG0.VID._OFF, MethodObj) External (_SB.PCI0.PEG0.VID._ON, MethodObj) You'll find guidance and samples on this matter here.
-
I would modify 2 things in your Clover config.plist: in Graphics tab, I'd select option "inject nVidia" in SMBIOS tab, I'd opt for iMac16,1 (Broadwell) rather than MacPro6,1 (IvyBridge) If you can, try and press F4 at Clover main menu to extract your raw BIOS tables and get them saved to CLOVER/ACPI/origin folder of EFI partition. You can then post us a zip archive of your DSDT and SSDTs.
-
Many Dell workstations are configured with a PCI root set to 4. With default PCI root set at 0, bootloaders often can't initialise graphics cards properly until the value of 4 is specified.
-
Recompile the table and save the .aml file to ACPI/patched folder of your EFI folder. Patched AppleHDA must be placed in /S/L/E where it replaces the vanilla kext. Permissions must be repaired and cache rebuilt thereafter. The kext will not load from anywhere else.
-
There should not be much really. Look for builds of similar specs or post a zipped copy of the EFI folder of your EFI partition and we'll have a look.
-
You'll probably have to make up your own boot pack. All you need to begin with is the FakeSMC kext (it's mandatory). Thereafter, you look for drivers that handle your hardware elements (LAN, audio, wireless, etc.). You're also going to have to configure Clover according to your system. Your Workstation is based on a Broadwell platform.
-
I don't believe BCM5722D LAN kext applies to the E Series... Kexts placed in the EFI/CLOVER folder are injected at startup. Once you're happy you've got the right kexts, move them to /L/E from where they can be cached, which improves startup time.
-
[SOLVED] Run macOS Sierra from an external hard drive, possible?
Hervé replied to spidey123's topic in The Archive
Your DSDT patch is fine as it is; nothing to change. Do the rest. -
[SOLVED] Run macOS Sierra from an external hard drive, possible?
Hervé replied to spidey123's topic in The Archive
Identify SD card reader in IOReg through IOregistryExplorer app (or any equivalent). Patch the DSDT device under which the SD card reader registers Remove all instances of VoodooSDHC kext (in SLE and/or LE and/or EFI/CLOVER/kexts folder of EFI partition) Rebuild cache from Terminal using: touch -f /S*/L*/E* touch -f /L*/E* sudo kextcache -Boot -U / If you get an error 77, repeat the commands. -
You can create a Sierra USB installer using the usual manual process (same as for Yosemite or El Capitan), then install the bootloader (Clover or Enoch) and the required bootpack. You can reuse your existing Yosemite pack (I understand you currently run that). For an Enoch based installation with BIOS in legacy mode, you can follow a similar process as described here, excluding the computer's specific pack of course. I would recommend you create a separate partition and retain Yosemite for the time being.
-
[SOLVED] Run macOS Sierra from an external hard drive, possible?
Hervé replied to spidey123's topic in The Archive
Spidey123, the patch certainly looks good now so, if your SD card reader is indeed under Device (RP06), you should have a fully functional reader. If not, do as Jake suggests right above. -
[SOLVED] Run macOS Sierra from an external hard drive, possible?
Hervé replied to spidey123's topic in The Archive
Upload it here. I trust you did not just copy/paste Jake's patch into your DSDT. It's meant to be saved into a text file then loaded as a patch to apply. -
Please try and do your homework...
-
I cannot speak for Clover, but nVidia GeForce GT610 certainly is support OOB under Chameleon/Enoch with simple boot option GraphicsEnabler=Yes. Maybe you can post a zipped copy of your EFI folder for us to check things out. NB: GT610 is unsupported under Sierra for the moment.
-
[SOLVED] Run macOS Sierra from an external hard drive, possible?
Hervé replied to spidey123's topic in The Archive
Maybe you patched your DSDT incorrectly. If done correctly, the patch is 100% successful on the E6x20 and E6x30 series. You most also remove the VoodooSDHC kext and rebuild your cache afterwards. NB: the DSDT patch does not change the PCI ids at all; it merely injects compatibility with Apple's default SD card reader. That's all. -
[SOLVED] Run macOS Sierra from an external hard drive, possible?
Hervé replied to spidey123's topic in The Archive
If required, download Ukulele app and extract the Logitech keyboard Mappings. they go to /Library/Keyboard Layouts. You may also check the ISO settings of the Keyboard driver as detailed here. -
[SOLVED] Run macOS Sierra from an external hard drive, possible?
Hervé replied to spidey123's topic in The Archive
~ is for home directory, i.e. /Users/. If in doubt, open up Terminal, then type: cd / -> to go to HDD root pwd -> to check current directory then type: cd ~ pwd -
Re: USB ports, grab the USB injector off my D630n ElCapitan 10.11 pack. Make sure to: modify the DSDT and rename USB2.0 controller devices from EHCx to EH0x use MacBookPro5,1 SMBIOS
- 1 reply
-
- d630
- quadro nos 135m
-
(and 5 more)
Tagged with:
-
Webcam 1bcf:2b93 = Sunplus Innovation Technology model. Should be a UVC USB-internal accessory. Sunplus webcams usually work OOB but if this one does not, then expect it to be unsupported. The finger scanner will not be supported.
-
A few things to note about /L/E: the folder can be considered for 3rd party extensions the folder is untouched at updates (except kexts that Apple place there themselves) the folder is totally bypassed when booting without cache Regarding TrackPad, you can use the script posted by Dr Hurt here once you've installed the PrefPane and configured it to your liking.
-
As I said above, /E/E/kexts/Other or /E/E/kexts/Other/LE is an invalid folder for kexts. Nothing will load from there. Please pay attention... You can inject kexts: from /E/E of OS X partition with Enoch from /EFI/CLOVER/kexts/Other or /EFI/CLOVER/kexts/10.xx of EFI partition with Clover Note that if/when you update, your /L/E folder will remain untouched; only /S/L/E will be modified; Hence the usefulness of Clover on-the-fly patches. With Enoch, you have to manually (re)patch vanilla kexts of /S/L/E folder. It may not have occurred to you that the LE folder placed in the EFI folder of Jake's pack is to indicate that kexts placed there are to go to /L/E of the OS X installation partition. Sorry if you missed that subtlety... Same principle in the presence of an SLE folder.
-
Right click->Get info gives you the version of a kext. Placing the IDT kext in /E/E/kexts/other/LE is not going to work, it's not a folder used by anything, you got that part wrong. You can place it in EFI/CLOVER/kexts/Other or EFI/CLOVER/kexts/10.xx of your EFI partition or, better, place it in /L/E, repair permissions and rebuild cache. You must also repair permissions and rebuild cache for patched AppleHDA in /S/L/E. Kexts placed in Clover EFI partition folder are injected at boot time, whereas kexts placed in /L/E are cached, which is better and faster at startup. I'd avoid Kext Helper or Kext Wizard if I were you; this kind of tools does not report on kextcache rebuilding errors. You'd be better advised to follow the manual way described a million times here: 1) copy the kext(s) to the targeted folder(s) 2) Repair permissions and rebuild cache with the following Terminal commands: sudo chmod -Rf 755 /S*/L*/E* sudo chown -Rf 0:0 /S*/L*/E* sudo chmod -Rf 755 /L*/E* sudo chown -Rf 0:0 /L*/E* sudo touch -f /S*/L*/E* sudo touch -f /L*/E* sudo kextcache -Boot -U / If you obtain an error 77, repeat the touch + kextcache commands.