philstopford

Thanks. I now have a new revision of the bootpack here that also seems to greatly reduce the time to display for the filevault 2 screen. Brightness keys aren't working, but the volume keys are functional (with the on-screen display). That has me rather confused. No joy with HDMI - machine locks up, also get a boot error screen if HDMI plugged in then CLOVER_working6.zip

To be honest, I'm not exactly sure. It is somewhat of a combination of your bootpack and the archive from here : https://osxlatitude.com/forums/topic/11155-latitude-7480-install-mojave/ Some of the efi and kext packages were updated as well, to match current releases.

So I ended up with the attached which gets me booting with FileVault 2 on my 7600U based E7480, but HDMI causes an instant lock-up and the display isn't responding to the special function keys (changing brightness, etc.). I was originally using Jake Lo's bootpack, but there I couldn't get the FileVault 2 login window to come up. I wondered if anything obvious stood out. clover_7480_fv2_r1.zip

OK. This seems to work. I took Jake Lo's original bootpack and rolled in elements from https://osxlatitude.com/forums/topic/11155-latitude-7480-install-mojave/ clover_7480_fv2_r1.zip

Not sure whether the attached might be useful. Still no joy in getting FileVault2 bootable. efi.zip

I couldn't figure out where to post this, so hopefully this is close to the correct place. Looking at the installed Clover version (4910), the efi drivers have -64 behind them. I was wondering whether the drivers from (https://github.com/acidanthera/AppleSupportPkg/releases) might help with the FileVault LoginWindow being missing, but those lack the -64 in the name and make me uncertain about whether this is the right thing to do.

Rough estimate from Philippe would be minimum of two months and ~1600 USD as a contract job to bring the driver up to par.

I am waiting to hear back from Philippe to see what it might cost/take to get the driver updated. I'll use your troubles as an excuse to follow up with him. I should note that 'worked' turns out to be a little optimistic in my case. It recognizes inserted media, but doesn't really want to do much with it (e.g. formatting an SD card results in an obscure error message).

It seems to be loaded : 141 0 0xffffff7f81198000 0x9000 0x9000 org.tw.CodecCommander (2.7.1) 114866EA-9E10-3A75-8084-CEEE9D344D9F <96 13 12 5 3 1>

I have a working Mojave 10.14.4 install on a Dell Latitude e7480, having followed the guide here (https://osxlatitude.com/forums/topic/8506-dell-latitude-inspiron-precision-vostro-xps-clover-guide/?do=findComment&comment=87342) and using the bootpack from here (https://osxlatitude.com/forums/topic/11315-dell-lattitude-7480-mojave-install-need-help/?tab=comments#comment-88501)

phil_sinetek_rtsx.zip

I originally thought this was working well and got a surprise today when I put my headphones in and was subjected to a loud high pitch squeal/whine. Poking around a bit, it looks like this happens after the 3rd or so wake from sleep. This is with the bootpack from https://osxlatitude.com/forums/topic/11315-dell-lattitude-7480-mojave-install-need-help/?tab=comments#comment-88501 and the rtsx kext I've been looking at for the SD card reader. I just wondered if others had experience this. I did notice the 7440 thread that talks about 'static', but am not certain if this is a similar issue.

Depends on what it would cost. I'm waiting to see how practical this might be.

I'm in touch with Philippe. He has suggested that he would be willing to do some contract work on it. I'm trying to find out what that would involve. Just as information.

So it suddenly started working today. I built the module from the github source and installed it under both CLOVER/kexts/10.14 and also under /L/E Not sure if both locations were needed. In case it's useful, I could attach the kext here, but I'm not sure if that's against the rules. It's simple enough to pull the github repository and build in Xcode, though.

Just to report back. I tried the pre-built kexts and then built the extension from source. The info plist shows the model reported in my machine, but the SD card is not detected, although the extension is loaded in the kernel. That matches some other feedback in the forum and elsewhere, so I guess I'm at an end for now on this part of things.

Hmm. Reports look a little mixed there. Presumably worth a try - thanks.

I haven't been able to figure this out yet. I'm out of ideas at this point. Has anyone had success with FileVault 2 on this machine?

This seems to be a RealTek device, showing under RP01@1C/IOPP/PXSX@0 01:00.0 (null) [ff00]: RealTek Semiconductor Co. Ltd, (null) [10ec:525a] (rev 01) (subsys 1028:07a0) I hunted around and wasn't available to discover an option to enable this, so thought I'd ask just in case.

Ahah. I was coming here to post the same basic solution having spent some time mucking around - it does seem to be down to the rather small EFI partition from Windows. My approach used gparted to make the changes. In case useful: In Windows, resize the Windows volume to make space for both the macOS partition and the EFI expansion. Download tuxboot and gparted. Use tuxboot to make a bootable USB drive with the gparted software installed (see https://sourceforge.net/projects/gparted/ and the instructions at https://gparted.org/liveusb.php). Boot off the USB stick. Move the Windows partition rightwards by the few-hundred MB required to expand the EFI partition. Move the System Reserved partition rightwards as far as the tool will allow you. Now expand the EFI partition. Finally, create a new HFS+ partition in the free space after the Windows partition. Hit 'Apply' to make all these changes. You might get an error reported by gparted, but in my case this was simply that it couldn't expand the EFI partition to the full extent, leaving a few MB unused. In my case, I booted once into Windows, to ensure nothing was broken. Then I went ahead with the macOS install, using the HFS+ partition as the install target. I did have to also go into the Latitude e7480 BIOS to set an EFI entry pointing at Clover; during the install, the system would generally keep booting into Windows. So, much the same, but I had been unclear whether the free MiniTool Partition Wizard would allow the changes needed from within the running Windows environment. Thanks!

Hopefully this isn't a problem to ask in this thread (as it seems related) Is there a viable way to set-up dual boot when the SSD has an existing Windows 10 install on it? I've tried a few experiments (ahead of messing with my existing OS drive), where I shrink the Windows drive down. Then I create a simple volume (exFAT) in the space that is created. I then try to install macOS (mojave), but Disk Utility keeps declaring that MediaKit thinks there is insufficient space to format it / use it. Deleting the exFAT volume in Disk Utility seems not to help at all, and also the action of trying to format the partition makes the Windows 10 installation unbootable.

Hello, I have a working Mojave 10.14.4 install on a Dell Latitude e7480, having followed the guide here (https://osxlatitude.com/forums/topic/8506-dell-latitude-inspiron-precision-vostro-xps-clover-guide/?do=findComment&amp;comment=87342) and using the bootpack from here (https://osxlatitude.com/forums/topic/11315-dell-lattitude-7480-mojave-install-need-help/?tab=comments#comment-88501 The remaining issue I'm running into is the FileVault2 encryption. I've installed the FileVault2 drivers in the Clover installer and made the preboot volume visible per (https://davejansen.com/turning-on-filevault-on-your-hackintosh/), but the system seems to hang trying to create the LoginWindow when booting from the FileVault2 preboot volume. Disk encryption was complete prior to the reboot. I have been searching for a while and didn't find a solution for this, so thought I'd ask.