Jump to content
tonyx86

Mojave on Dell Latitude E6410

40 posts in this topic

Recommended Posts

Advertisement

sorry to double post,  but I also wanted to ask if you were able to get speedstepping going on Nvidia 3100m?  I can’t help but wonder if there is a relation between sleep and GPU power management and it would be good to rule that out

Share this post


Link to post
Share on other sites
Posted (edited)
On 6/17/2019 at 3:44 PM, Dr. Monkey said:

Do you know how I would check what the permissible values to SLPE would be?

I don't know.  I'd try searching for it.  I don't even know the units of time (e.g. clocks, milliseconds, ...).

 

On 6/17/2019 at 3:59 PM, Dr. Monkey said:

sorry to double post,  but I also wanted to ask if you were able to get speedstepping going on Nvidia 3100m?  I can’t help but wonder if there is a relation between sleep and GPU power management and it would be good to rule that out

From a previous post in this thread:   My method of injecting the device-id for Nvidia gets AGPM loaded, but it's probably not the correct solution.  I re-read duduclx original El Capitan thread and some work on this.  See here for this analysis.  I haven't tried any of it yet.

Edited by tonyx86

Share this post


Link to post
Share on other sites
Posted (edited)
On 6/17/2019 at 3:59 PM, Dr. Monkey said:

sorry to double post,  but I also wanted to ask if you were able to get speedstepping going on Nvidia 3100m?  I can’t help but wonder if there is a relation between sleep and GPU power management and it would be good to rule that out

@Dr. Monkey- I just reread the thread that I linked above.  I haven't made this a priority yet and would love to know what you find.

Edited by tonyx86

Share this post


Link to post
Share on other sites

so I’ve been through the AGPM guide a few times,  and AGPM loads for me.  However I still only show a frequency of 400 MHz with the extremely infrequent dip to 250MHz,  and I am unable to see anything in the system.log

Share this post


Link to post
Share on other sites
Posted (edited)
On 6/17/2019 at 9:30 PM, Dr. Monkey said:

so I’ve been through the AGPM guide a few times,  and AGPM loads for me.  However I still only show a frequency of 400 MHz with the extremely infrequent dip to 250MHz,  and I am unable to see anything in the system.log

 

You made more progress than I did.  I just tried the suggestion (if I read it correctly).  I created a new entry for Device 10de,0a6c under MacBookPro 6,2 in AppleGraphicsPowerManagement.kext/Contents/info.plist and I set control-id to 18 (I also tried control-ids 16 and 17).  I don't see GPU Core/Memory clock changing at all - stuck on 405MHz.  What was your method for getting the frequency to make the "extreme infrequent dip to 250MHz?"

 

Note that I confirmed that AGPM loaded with the control-id I specified in info.plist for each of the cases control-id = 16, 17 and 18.  HWMonitor doesn't show any GPU Core/Mem clock changes.  

 

Could it be that HWMonitor isn't showing the GPU state changes?

Edited by tonyx86

Share this post


Link to post
Share on other sites
Posted (edited)
On 6/17/2019 at 8:19 PM, tonyx86 said:

@Dr. Monkey- I just reread the thread that I linked above.  The methodology looks very promising and should be applicable to the E6410.  I haven't made this a priority yet and would love to know what you find.

@Dr. Monkey I found one of your original discussions here.  I can see that you've looked at the AGPM throttling issue much more than I have, so I'll defer to you on this. After a bit of reading, I am using the FakeSMC.kext method to inject AGPM properties for the 10de,0a6c.  If you have anything you'd like me to try, let me know.  If you can post your DSDT.aml, config.plist and kexts for comparison, that would be very helpful.  Thanks!  

Edited by tonyx86

Share this post


Link to post
Share on other sites
Posted (edited)

EDIT: IOHWControl does not load properly under AGPM.  There's something "wrong" with my _DSM for discrete graphics (AGP.GFX0._DSM) in my DSDT.  If I enable "Inject NVidia" in CLOVER config plist, IOHWControl loads immediately.  Still testing this and have not updated the files attached to Post #1.

 

IOHWControl should load under AGPM as shown in the attached HighSierraAGPM.png.

HighSierraAGPM.png

MojaveAGPM.png

Edited by tonyx86

Share this post


Link to post
Share on other sites
Posted (edited)

EDIT:  Deleting this post.  IOHWControl is not loaded because there's something wrong with the discrete graphics _DSM in my DSDT.  Currently testing a modified DSDT combined with enabling "Inject NVidia" in CLOVER config.plist and have not posted revised configuration files yet.

Edited by tonyx86

Share this post


Link to post
Share on other sites

I found a bug in the E6410 DSDT for BIOS A17.  In Method (GNOT), the expression 

 

    If (LOr (LGreater (OSYS, 0x07D0), LLess (OSYS, 0x07D6)))

 

always evaluates to TRUE regardless of the value of OSYS (so the first branch ( Notify (\_SB.PCI0, Arg1) ) is always executed.  I suspect that LOr should be LAnd so that the expression reads

 

    If (LAnd (LGreater (OSYS, 0x07D0), LLess (OSYS, 0x07D6)))

 

which executes the first branch ( Notify (\_SB.PCI0, Arg1) ) if the Operating System is a Windows 2001 variant and the second branch ( Notify (\_SB.PCI0.VID, Arg1) ) for any other operating system.

 

While this bug may have no affect on MacOS (especially since the patched Method (HPET) has no dependency on OSYS), the real problem with this bug is that it's obvious, should never have made it through Dell QA and should not be in BIOS version A17.  This same bug appears in the BIOS for other Latitude models.

Edited by tonyx86

Share this post


Link to post
Share on other sites

@MadHatter806  - I'd like to try UEFI booting my E6410.  I've tried creating a UEFI-bootable USB drive with CLOVER, but my E6410 doesn't appear to recognize the USB as bootable.  Do you have any advice for creating a UEFI-bootable device for the E6410?  Here's what I tried:

  • Format USB (GUID partition map)
  • Install CLOVER on USB in ESP (UEFI boot)
  • Configure E6410 BIOS for UEFI boot (Change mode from Legacy to UEFI, don't configure a boot file)
  • Attempt to boot from USB (F12 -> Boot Menu -> UEFI USB)

My E6410 doesn't boot from the USB.  Instead, it shows a strange boot screen.  

 

Any advice for getting the E6410 to UEFI boot would be appreciated.  Thanks!

Share this post


Link to post
Share on other sites

It appears that I incorrectly applied the patch that duduclx referred to as "Intel GMA Ready," because in my DSDT, the patch contents are in Device (IGPU) instead of in Method (_DSM) within Device (IGPU).  MaciASL didn't complain about this and it doesn't appear to have had any affect.  I made this correction to my DSDT but haven't updated the files in Post #1.

Edited by tonyx86

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   1 member

  • Similar Content

    • By Jessi-mj
      No success so far.
       
      There is no way I can get Mojave (or High Sierra) to install on this rig.
       
      I'd be really grateful for any help.
       
      My config is 
      Asus Maximus XI Hero (no WiFi); 
      I9-9900k; 
      Sapphire triX Radeon R9 290; 
      Corsair Pro RGB 2x16GB CMW32GX4M2C3200C16
       
      I am using my R9 290 I had at home because I don't need powerful graphics really.
       
      So what I've done
      1) Created USB installation drive using [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] -  UEFi option
       
      2) Bios settings
      - Updated BIOS to lastest version
       
      - Load Optimised defaults
       
      - applied the following
      VT-d, disabled
      CFG-Lock, disabled
      Secure Boot Mode, disablef
      OS Type set to Other OS
      XHCI Handoff Enabled
      AI Overclocked set to XMP 3200
      Extreme twerking enabled
      Graphics Primary display set to PCIe
      Legacy USB support enabled
      Power on by PCI disabled
      Fast boot disabled
      Boot logo display disabled
      Boot option 1 set to UEFI usb installer
      Saved and rebooted.
       
      I either get no screen response (stuck in qcode 99 on MB) or stuck on PCI configuration begins.
       
      So what am I doing wrong?
       
      Five hours of trial and error and I gave up on installing from USB.
       
      I am now  installing Mojave from my MacBook Pro to SSD and will use [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] before moving the drive over to my PC
       
      The settings I am going to use in [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url]
       
      Quick Start > UEFI Boot Mode
      Drivers > Audio > AppleALC
      Drivers > Misc > FakeSMC Plugins
      Drivers > Misc > FakeSMC HWMonitor Application
      Drivers > Misc > Core Graphics Fixup AKA WhateverGreen
      Drivers > Network > Intel > IntelMausiEthernet (I used the latest version)
      Drivers > USB > Remove XHCI USB Port Limit <--- Adds PMHeart’s patch to remove XHCI USB Port Limit
      Drivers > USB > USBInjectAll
      Bootloaders -> Clover v2.4k r4xxx UEFI
      Customize -> System Definitions > iMac > iMac18,3
       
      If you have any suggestions please help.
       
      Perhaps someone can share their EFI folder for a similar rig?
       
    • By Kielligzind
      Hello, i am trying to boot the installer of MacOS Mojave 10.14.5 on my HP Z220 CMT Workstation, but it gets stuck at this error. i attached pictures of this error and i posted my EFI folder. 
      i hope someone can help me. Thanks in advance.
       
      https://drive.google.com/file/d/1qH_ok-jzIwiLXd5LEEvVloRFZDgPAY2d/view?usp=sharing
       

    • By crazybirdy
      Patched OSInstaller.framework to allow macOS 10.14 installation on MBR HFS+ partition.
       
      To use those patched files you must follow HowTo to create an USB installer. You can't just run the app downloaded from Mac App Store.
      The patch is made base on 落下爱@pcbeta 10.10.x MBR patch method, and more patch for 10.14 HFS Firmware check by crazybirdy.
       
      What is this patched OSInstaller doing?
      1. Patch the MBR check, allow macOS 10.14 installation on MBR partition.
      2. Patch the Firmware check, bypass the error of "An error occurred while verifying firmware".
      3. Patch to stop auto-convert to APFS , "ConvertToAPFS=false" is no longer worked with 10.14.
      4. This patched MBR OSInstaller will never convert to APFS, and will always install as HFS+ partition.
      5. This patched MBR OSInstaller method works with both MBR HFS+ and GPT HFS+ partition (GPT+recovery).
      No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch.
       
      What's the difference between createinstallmedia method, MBR-Manual-Method, and MBR-Automatic-Method?
      As the following....
      1. createinstallmedia method,
          needs stage 1, stage 2 installation process, which is worked with GUID partition only, always convert to APFS format.
      2. MBR-Manual-Method (same as 10.12),
          install via stage 2 manually, which is worked with both MBR and GUID, HFS+ and APFS, will never convert the partition format.
          We can manually format as MBR or GPT, HFS+ or APFS on installation screen like as 10.12.
          We can manually select MBR HFS+ partition to install 10.13 and 10.14 on installation screen now.
          Needn't to update the MBR-Manual-Method files, it will still work on 10.13, and 10.14 future versions, I think so.
          It can be installed as Fresh installation on formated blank partition only, but can't be installed as update from previous version.
      3. MBR-Automatic-Method (new for 10.13+),
          install via stage 2 automatically, which is worked with both MBR and GUID, HFS+ and APFS, will never convert the partition format.
          It can be installed as Fresh installation on formated blank partition, and can be installed as update from previous version.

      How to make 10.14 installer for MBR (MBR-Manual-Method)?
      Just use EasyMBR-InstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.12.
      Read HowTo Q/A Q5. How to patch to work with CPU SSE4.1 only for Mojave?
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.14.x combo-update to MBR and GPT with installScript directly?
       
      How to make 10.14 installer for MBR (MBR-Automatic-Method)?
      Just use 14MBRinstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.13.
      Read HowTo Q/A Q5. How to patch to work with CPU SSE4.1 only for Mojave?
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.14.x combo-update to MBR and GPT with installScript directly?
       
      And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist.
       


       
      Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      A6. Some people download installer app from App Store, and get only 18 MB size, not the complete installer app (5.68 GB). You should boot to 10.12, or 10.13 to download it again from App Store, or use script Q6-DownloadFullApp/installScript_1014fullapp to download the full installer app via swscan.apple.com.
       

       
    • By fusion71au
      Patch Catalina or Mojave macOS Installer App for Unsupported Machines
       
      Often for economic reasons, Apple prevents the Installer.app for its latest macOS from installing on older machines perfectly capable of running it eg macOS 10.14 Mojave on Unsupported Macs Thread.
       

       
      In Mojave 10.14, @ASentientBot posted a method to patch the distribution file in OSInstall.mpkg to enable the Mojave installer to install on unsupported machines (with or without graphics card metal support). 
       
      In Catalina 10.15beta, the above method no longer works since Apple is checking OSInstall.mpkg for its file signature and the mandatory requirement in Catalina to install to 2 separate apfs volumes necessitates using the original Catalina macOS Base System Installer.  Fortunately, it is still possible to substitute High Sierra’s Apple Signed OSInstall.mpkg inside the Catalina or Mojave InstallESD.dmg by making it R/W.
       
      The procedure below will allow Macs or Hacks able to install High Sierra to also install Catalina or Mojave (eg SMBIOS MacPro5,1, iMac11,3, MacBook Pro7,1 which have been unsupported in macOS 10.14.x and 10.15beta) -credit to @ASentientBot's post.
       
      Prerequisites
      1. Mac or Hack capable of and running High Sierra 10.13.x
      2. An original, untouched copy of OSInstall.mpkg from High Serra InstallESD.dmg - attached OSInstall_10.13.6.mpkg.zip save to your ~/Downloads folder
      3. macOS Installer App eg for Catalina beta or Mojave downloaded to /Applications
      4. Add NVRAM boot arg (or Clover config.plist boot arg on a hack) -no_compat_check to enable system to boot to final completed Mojave or Catalina install.
       
      Procedure
      1. Open Terminal and type the following
       
      open /Applications/Install*/Contents/SharedSupport/InstallESD.dmg (assuming the Catalina or Mojave Installer App is in /Applications)  
      2. Open Disk Utility, click File|New Image|Image from ‘InstallESD”
      3. Save as read/write image, no encryption in /Applications
      4. Unmount InstallESD in DU by clicking the "eject" icon next to it
       
       
      5. Open the R/W InstallSD.dmg in /Applications and replace Catalina’s/Mojave's OSInstall.mpkg with High Sierra’s version by typing in terminal
       
      open /Applications/InstallESD.dmg cp ~/Downloads/OSInstall_10.13.6.mpkg /Volumes/InstallESD/Packages/OSInstall.mpkg  
      6. Unmount InstallESD in DU by clicking the "eject" icon next to it
      7. Replace original Catalina/Mojave InstallESD.dmg with our patched one, making a backup of the original.  In terminal, type
       
      sudo mv /Applications/Install*/Contents/SharedSupport/InstallESD.dmg /Applications/InstallESD_orig.dmg sudo mv /Applications/InstallESD.dmg /Applications/Install*/Contents/SharedSupport/  
      8.  Test the newly patched installer!…

    • By Coddyx
      Hi,
       
      I followed the AMD OSX Vanilla Guide and managed to successfully build my first hackingtosh.
      Everything works great EXCEPT for my MSI - Radeon RX 580 8 GB GAMING X.
      I ran some benchmarks (and tried World of Warcraft) and I am getting ~50% of the performance I am usually getting in Windows 10.
      Unigine Heaven reports ~950 vs 1750 in Windows and World of Warcraft runs @ 30 fps lowest settings vs 60 fps ultra settings in Windows.
       
      Here are the kexts I am using:
      AppleALC Lilu NullCPUPowerManagement RealtekRTL811 VirtualSMC WhateverGreen  
      I should mention that this is an AMD hackingtosh running on Ryzen 5 1600 3.2 GHz 6-Core Processor.
       
      I read and I completely understand that I should not expect 100% performance. But I believe a 50% drop is out of the ordinary.
       
      If anyone has ideas on what I could try to up the performance it would be greatly appreciated.
       
      Thank you!
       
       
×