-
Posts
14365 -
Joined
-
Last visited
-
Days Won
868
Content Type
Profiles
Articles, News and Tips
Forums
Everything posted by Jake Lo
-
The screenshots only provide the CPU info and not much more. What I'm looking for is: CPU: you already provided Touchpad: Synaptics, Elantech, Alps, I2C..etc Audio: CodecID..ie ALCxxx HDMI port? DP port? USB-C port? Those are the basics. Better that you post the export of dxdiag from Windows. Also you can't use a Config from an old Clover with the new Clover, way too many changes due to new Clover integrating OpenCore drivers for Big Sur. I don't have any experience with the new Clover, I have since moved to OpenCore. I'll help you with OpenCore setup going forward after I have all those info requested.
-
@Next One Thanks for the update. The is exactly what I have on my Precision 5510 / 7510 as well. However I have different values than yours Method (BRT6, 2, NotSerialized) { If (_OSI ("Darwin")) { If (LEqual (Arg0, One)) { Notify (\_SB.PCI0.LPCB.PS2K, 0x0406) } If (And (Arg0, 0x02)) { Notify (\_SB.PCI0.LPCB.PS2K, 0x0405) } } Else { BRTX (Arg0, Arg1) } }
-
[solved] Latitude 5400: LCD brightness, DP and HDMI not working
Jake Lo replied to ryuu_nami's topic in The Archive
At this point, I think you might just have to try changing the DVMT pre-alloc to 128MB -
[solved] Latitude 5400: LCD brightness, DP and HDMI not working
Jake Lo replied to ryuu_nami's topic in The Archive
Try this config.4K.zip -
Looks like it's an installer issue. Re download and create the installer
-
@biker972 AMD is still not disabled according to the IOreg file. Is this new or same one attached previously. If it's new then try replacing SSDT with this one SSDT-Disable-DGPU.aml.zip
-
Under display preference, does it even have the brightness slider? If not, then don't expect fn keys will work. Post new IOReg file, Config.plist and ACPI folder
-
[solved] Latitude 5400: LCD brightness, DP and HDMI not working
Jake Lo replied to ryuu_nami's topic in The Archive
try this for ambient light, try adding SSDT-ALS0, you should be able to find on google Don't think it works on Hackbook with what you are asking. config-HDMI-DP.zip -
does Fn+S and Fn+B work?
-
@truceFR Your images are not attaching. Anyway, with your display 1366x768, you should use the Config-LoRes
-
Just run this patch by Rehabman #Maintained by: RehabMan for: Laptop Patches #fix_PARSEOP_ZERO.txt # credit toleda: http://www.tonymacx86.com/dsdt/89727-maciasl-patch-repository-thread.html#post574047 into device label PCI0 code_regex (\s+Zero){2,} removeall_matched; # if you need something more agressive... into_all all code_regex (\s+Zero){2,} removeall_matched; into device label PCI0 code_regex (\s+Zero){2,} removeall_matched;
-
I looked at a bunch of IOReg files for different E5470's and they all look different. Best you do your own USB Remap by using Hackintool. Then post your new IOreg so I could compare. I don't own this system so can't do the mappings for you. Post your current IOReg file, maybe it's similar to the other's I have seen
-
@biker972 In deed it has an AMD graphics card and it's not supported. Add this SSDT to ACPI folder and declare it in the Config file under ACPI/Add This should fix the issues. SSDT-Disable-DGPU.aml.zip
-
@biker972 The behavior you described sounds like system might have a dgpu. Post IOReg file using IORegistryExplorer.app v2.1 to confirm. If you have the Intel wifi and use the Config-IntelWifi.plist, the Intel kext(Airportitlwm.kext) is already included hence your wifi is working.
-
@biker972 Are you using Fn+F11 and Fn+F12, assuming those are the Fn keys. If you have the Fn locked, then it's just F11 and F12. Does Fn+B /Fn+S work? What do you mean when you turn off / on the screen? You mean external monitor? I assume you're using the Intel Wifi...it's still on Beta so you can't expect too much there. Swap out with a compatible device like DW1830 / DW1560 /DW1820A You can dual boot, but you'll need to select Windows Manager from the Bios F12. Add OpenCore to BIOS boot option and select the priority of which you want to boot as the default. Boot time can be shorten by removing the verbose mode. Also with the Intel kext, I noticed it does increase boot time, but less than a min is really good.
-
[solved] Latitude 5400: LCD brightness, DP and HDMI not working
Jake Lo replied to ryuu_nami's topic in The Archive
What patches are applied in the DSDT in your ACPI folder? So brightness setting is not working at all? Please post IOReg file -
@truceFR Give this a try. Files are defaulted for the following configuration BIOS A24 i5-3340M 1600x900 If your display resolution is lower, then use Config-LoRes and rename it as Config I also include DSDT-A23 for BIOS version A23, you'll just need to rename it in the Config file If you have different CPU other than the ones I included, i5-3340M and i5-3320M, then you could use SSDTPrGen.sh to generate your own Place it in ACPI, rename it to whatever you like ...maybe SSDT-PM.aml? But make sure to rename it in the Config file as mine is defaulted to i5-3340M.aml Upgrade your BIOS to A24 or A23 to use my files otherwise you probably get the same automatic sleep right after boot. I see you have A20, I could probably patch that for you, but I'll need the vanilla DSDT exported from your system. Good luck E6430_A24_OC_0.6.8.zip
-
Latitude 7480: no USB ports after Big Sur update to 11.3
Jake Lo replied to kenux's topic in The Archive
@kenux See here from Dortania regarding xhciportlimit. You should have use Hackintool to generate USBPorts.kext prior to the upgrade. It's been warned for ages that USBInjectall or xhciportlimit patches are temporary fixes. Now you see why. -
Yes, the bootpack should work without any modification.
-
it'll only work if the device = IGPU According to your DSDT, your device = VID so you'll need to add a patch to rename that to IGPU and change the device in the ssdt to IGPU as well. Normally Whatevergreen will automatically rename GFX0 to IGPU, so the ssdt will just have device = GFX0 but not for you system.