Hervé

Guys, whilst your requests are indeed legitimate, the messages are clear and require no further requests. Please PM Dinesh directly as we don't wish to see this topic turn into public bashing which would result in messages deletion + thread closure. We don't have the source code at OSXL and I'm not seeing any developper here in these last requests.

In your case, I suspect the wrong label was erroneously fitted on the card or it was actually changed from the 08PKF4's to 0VW3T3's. Why? Well, because: this would be the very 1st 0VW3T3 model I see with subsystem id 1028:0023 (I now possess 3 x 0VW3T3 cards with id 1028:0021, like the others I've dealt with for other forum members) the MAC address of the card's label (clearly C8FFxxxxxxxx) does not match the real MAC address shown in macOS (3052xxxxxxxx) you experience the reported behaviour/problems of the 08PKF4 model Depite the label fitted to the card, I'm pretty confident you do not have the 0VW3T3 model. Sorry. If you can, demand a refund/return to the buyer you got it from on the basis that it does not meet the advertised specs.

Dr Hurt is the author of the kext, not Bronxteck !

Fan noise/permanent spinning is not specific to OS X/macOS. It's the same with other operating systems such as Windows and I believe it results from recent BIOS updates.

Make sure you run with the correct MaciASL version Make sure MaciASL is properly setup https://bitbucket.org/RehabMan/os-x-maciasl-patchmatic/downloads/ Once you run with the correct version and the right settings, you'll find that the DSDT table you uploaded on post #1 only contains 1 error (that you'll easily fix) and nothing else. This being said, what's the reason why you would want to patch the E6430 raw DSDT from scratch and not use the pre-patched E6430 DSDT that JakeLo gave you?

Look under the various I2C devices...

Please refer to post #1.

Not much to tune. Try this config. You may want to replace your USB injector kext by Rehabman's USBInjectall kext. config.plist.zip

Try and re-compile the kext directly under Mojave and for Mojave as target. Contact the kext's author Use an external USB mouse

No, no, no; look this up in IORegistryExplorer.

It seems you opted for a RC version as opposed to the final version. But maybe the kext no longer gets the TouchPad properly recognized under Mojave. I'd need to check on my E6230. Edit: confirmed! TouchPad fully recognized by the TrackPad PrefPane under HiSierra, not under Mojave 10.14.5. I'm pretty sure it was under initial version of Mojave so it must have stopped somewhere between 10.14.1 and 10.14.5...

Clearly, the mouse PrefPane is not going to be of any help for your TouchPad. The kexts I refered you to normally enables the TrackPad PrefPane, provided it's been installed properly. You may have done somethign wrong in that respect.

Erm... you did open the TrackPad PrefPane and enable "Tap to Click", right? Because that's not enabled by default ...

So it's the port replicator E-Port K07A001 (USB2.0 ports) or E-Port II K07A002 (USB3.0 ports), check the product label underneath. Anyway, with those docks, VGA output is a matter for graphics framebuffer/drivers only. There's nothing you can do about it since VGA has no official support on platforms starting at Ivy Bridge. There's no patch you could apply unlike DVI/DP/HDMI. In all likelyhood, for dual display with a VGA screen, you'd need a DVI-to-VGA adapter + DP or DP-to-VGA adapter + DVI.

If you have a V3 to V5 TouchPad, clearly go for the latest R6 (compiled by Bronxteck) available on p1. V7 and V8 TouchPads are not properly supported.

VGA is not supported under macOS, so it's highly unlikely you can get it to work as an individual display. It will either work OOB or not at all but there's nothing you can do to make it work if it does not do so properly. I don't know which Dock model you're referring to but it may well be that, like the Type-C current models, VGA only works as a clone to DP/DVI/HDMI in multiple screen arrangement. https://osxlatitude.com/forums/topic/11410-dell-latitude-7490-with-i7-8650u-intel-uhd-620-and-1920x1080-lcd-mojave/?do=findComment&comment=90288

They're in the Clover pack available in my 7490 guide. What are the PCI ids of the TouchPad/TrackPoint models fitted to your 7480? On the 7490: TouchPad = 1028:081c (Dell-renamed Alps) TrackPoint = 044e:1212 (Alps)

I'm pretty sure @philstopford means the actual TrackPad/TouchPad device. Unless I'm mistaken, the 7480 uses a similar Alps I2C device as the 7490 and, indeed, it occasionally fails to respond to finger. Rebooting (once or multiple times) will eventually bring it back to life. This issue is undoubtedly due to those I2C drivers we use; they're not 100% kosher yet, it's work in progress. On the 7490, the device is fully functionnal as a Mac TrackPad/TouchPad and shows as such in the PrefPane. It can just be a little awkward to use. I see no reason why it would be different on the 7480, they're basically the same laptops apart from CPU generation.

So, no-one using this High Sierra/Mojave guide?

It's been mentioned in various places on the forum and I should probably write an FAQ thread on the topic. /S/L/E is the location for Apple's own (i.e. vanilla) kexts. Ideally, this should be left untouched by Hackintoshers unless for very specific and rare reasons (eg: patched AppleHDA). /L/E is the location for 3rd party/add-on kexts. This is where all kexts we use for our Hackintoshes should go. Kexts placed in either of these folders will be cached and this aims at accelerating boot time. Cached kexts are subject to signature and be set to the correct permissions. Cached kexts will be listed/registered in SysProfiler/SysInfo->Software->Extensions. Caching kexts is the recommended manner to use add-on kexts. Clover's E/C/k/O and E/C/k/10.xx are the locations for kexts that Clover injects at boot time: E/C/k/O is used to inject kexts regardless of the OS X/macOS version. E/C/k/10.xx are used to inject kexts for the given OS X/macOS version and therefore allow different kexts to be injected for different versions. Injected kexts are not cached and will not be listed/registered in SysProfiler/SysInfo->Software->Extensions. Injecting kexts results in a slower boot time than with cached kexts (though many would arguably say it's hardly noticeable). Kexts injection operates according to Clover settings on the matter: If kext injection is set to Yes, kexts placed in E/C/K/O (or E/C/k/10.xx) will be injected. If kext injection is set to No, no injection takes place obviously... If kext injection is set to Detect, kext injection operates according to the presence of FakeSMC in the cache (from /L/E or /S/L/E). If present, no injection takes place, if absent, kext injection is performed. Kext injection is very useful for recovery purposes (like booting without cache which ignores /L/E) or when testing kexts for instance; if a newly injected kexts causes issues (like a KP), it's very easy to remove/bypass it. On the other hand, kext injection is known to occasionally cause problem because it's not the natural way in which kexts should be loaded. Kext injection is basically a form of forced loading and, sometimes (though rare these days), it does not work. My own recommendation is to experiment with kexts through injection and, once kexts are validated, to cache them from /L/E. You can Google for this kext injection matter or consult the Clover wiki/InsanelyMac forum. It's all quite widely documented.

https://osxlatitude.com/forums/forum/104-wireless-and-bluetooth/

DW1397 card is not compatible with High Sierra. Disable it in BIOS or physically remove it in case it causes an issue (though it should not). You also need to use a SMBIOS compatible withy High Sierra. MacBookPro7,1 will do perfectly. Can you post a zipped copy of your Clover EFI folder or link to the folder you used (assuming you've not modified it in any way)? Please note that you cannot install High Sierra with Enoch; you need Clover for that. As such, my D630 Sierra guide is not appropriate for High Sierra (I really need to update that guide...). Once HiSie is installed, you can use Enoch to boot it but you'll then need to call on your Clover-based USB installed to complete any subsequent update (like the Security ones). So opt directly for Clover.

Moved from Guides section to Support! Please ensure you use the correct section for all future posting. K3100M is Kepler and is therefore expected to work OOB. K2200M is Maxwell and requires the nVidia Web Driver. It's therefore only supported up to High Sierra. You also have to take the potential issue of Optimus into account (unsupported on Hackintoshes).

It'll be the same EFI folder as for Sierra or High Sierra. You can derive it from the initial Chameleon/Enoch bootpacks available here. Due to unsupported C2D CPU + nVidia GPU, the D630 (like the D830) requires the well-known tricks for Mojave: replacement of telemetry plugin by that of High Sierra 10.13.6 to avoid non-SSE4.2 C2D-related KP (extract it from 10.13.6 combo update available off Apple's web site) installation of Tesla kexts from High Sierra 10.13.6 (they do not exist in Mojave due to lack of compatibility with Metal). I recommend you install those in /L/E patched PlatformSupport.plist or, ideally, change of SMBIOS to a Mojave-compatible model like, say MBP9,x (this is required for Mojave updates) And, since Mojave 10.14.4, you also need: replacement of GPUSupport + OpenGL frameworks by those from Mojave 10.14.3 (extract them from 10.14.3 combo update) You can refer to these threads/guides: https://osxlatitude.com/forums/topic/10726-macos-1014-mojave-betas-releases/?do=findComment&comment=83099 https://osxlatitude.com/forums/topic/11148-dell-vostro-200-st-with-c2d-e8600-geforce-gt730-gt1030-high-sierra-mojave/?do=findComment&comment=87085

Yes.