LG 38WN95C-W how to get 144Hz on 16" MBP 2016

[joevt]

Tried that as well

MacBookPro-4:~ jpmoran$ sudo nvram boot-args="debug=0x144"
Password:
nvram: Error setting variable - 'boot-args': (iokit/common) not permitted
MacBookPro-4:~ jpmoran$

You need to disable SIP or do the command from recovery.

 

[jpmoran]

Turned off SIP, but cannot get the lspci to run because DirectHW.Kext not loaded

MacBookPro-4:~ jpmoran$ nvram boot-args
boot-args    debug=0x144
MacBookPro-4:~ jpmoran$ ls
Applications        Google Drive        Pictures
Conferencing        IDrive Downloads    Public
Creative Cloud Files    IDrive-Sync        getting-started
DeLorme            Library            mapdrives.bat
Desktop            Local Sites        pcitree
Documents        Movies            pciutils
Downloads        Music            polar
MacBookPro-4:~ jpmoran$ sudo lspci
DirectHW.kext not loaded.
lspci: Cannot find any working access method.
MacBookPro-4:~ jpmoran$ sudo ./pcitree.sh
sudo: ./pcitree.sh: command not found

 

[joevt]

Turned off SIP, but cannot get the lspci to run because DirectHW.Kext not loaded

MacBookPro-4:~ jpmoran$ nvram boot-args
boot-args    debug=0x144
MacBookPro-4:~ jpmoran$ ls
Applications        Google Drive        Pictures
Conferencing        IDrive Downloads    Public
Creative Cloud Files    IDrive-Sync        getting-started
DeLorme            Library            mapdrives.bat
Desktop            Local Sites        pcitree
Documents        Movies            pciutils
Downloads        Music            polar
MacBookPro-4:~ jpmoran$ sudo lspci
DirectHW.kext not loaded.
lspci: Cannot find any working access method.
MacBookPro-4:~ jpmoran$ sudo ./pcitree.sh
sudo: ./pcitree.sh: command not found

You're using Mojave?
Try sudo lspci -A detect

From your home directory, the pcitree.sh script is in the pcitree folder so you would run it like this:
sudo pcitree/pcitree.sh

 

[jpmoran]

Here is a screenshot of my latest terminal result and system overview. I am running OS 10.14.6

MacBookPro-4:~ jpmoran$ sudo pcitree/pcitree.sh
Password:
# Unexpected pattern DirectHW.kext not loaded.
sed: 1: /tmp/pcidevices1.txt: extra characters at the end of D command
#=========================================================================================
MacBookPro-4:~ jpmoran$

 

[joevt]

Here is a screenshot of my latest terminal result and system overview. I am running OS 10.14.6

MacBookPro-4:~ jpmoran$ sudo pcitree/pcitree.sh
Password:
# Unexpected pattern DirectHW.kext not loaded.
sed: 1: /tmp/pcidevices1.txt: extra characters at the end of D command
#=========================================================================================
MacBookPro-4:~ jpmoran$

Show the results of sudo lspci -A detect.

 

[jpmoran]

MacBookPro-4:~ jpmoran$ sudo lspci -A detect
Password:
Trying method darwin......cannot open AppleACPIPlatformExpert (add boot arg debug=0x144 & run as root)...No.
Trying method intel-conf1...DirectHW.kext not loaded.
...no I/O permission...No.
Trying method intel-conf2......no I/O permission...No.
lspci: Cannot find any working access method.
MacBookPro-4:~ jpmoran$

 

[joevt]

MacBookPro-4:~ jpmoran$ sudo lspci -A detect
Password:
Trying method darwin......cannot open AppleACPIPlatformExpert (add boot arg debug=0x144 & run as root)...No.
Trying method intel-conf1...DirectHW.kext not loaded.
...no I/O permission...No.
Trying method intel-conf2......no I/O permission...No.
lspci: Cannot find any working access method.
MacBookPro-4:~ jpmoran$

I don't know what's going on if SIP is disabled and debug=0x144. Are you using OpenCore or Clover or something?

Try one last verify:

csrutil status
nvram boot-args

If SIP is disabled and debug=0x144 then maybe it's time to give-up, since I don't want to get into the stuff needed to install DirectHW.kext....

 

[jpmoran]

Well, it was a great try. I wonder if the reason my system is different is due to system upgrades rather than a native install. I am going to attempt a full wipe of the system and then installing Big Sur over the holidays. I'll post back to this thread if it changes the situation.

MacBookPro-4:~ jpmoran$ csrutil status
System Integrity Protection status: disabled.
MacBookPro-4:~ jpmoran$ nvram boot-args
boot-args    debug=0x144
MacBookPro-4:~ jpmoran$

 

[Acejam2k]

2021 Update

I recently picked up an LG 38WN95C-W to go with my 2019 16" MBP. (Radeon 5500M) After setup, I used the included white USB-C/TB3 cable. The picture appeared a bit grainy at times initially, fonts were pixelated, and I tried messing with all of the monitor settings. It wasn't until a few minutes in that I realized it was running at 3840x1600, but only at 75Hz.

It wasn't until I found this thread that I realized you need to select Show low resolution modes to reveal the hidden Refresh Rate menu. 144 Hertz was available as an option in that menu. Once selected, the monitor finally came to life and things were significantly brighter. It also revealed several disabled settings within the monitor's own configuration menu.

I am now happily running 3840x1600 @ 144 Hz. Note that my laptop is fully closed in clamshell mode, with only this single monitor attached. I believe this part might be the key.

 

[SirThanksalot]

Yes, I can confirm that as well.

Also, if Night Shift is not working for you (and I know the solution sounds crazy, but it works for me):

1. Go into the display's menu and turn on PBP, doesn't matter if anything is connected on a HDMI port
2. The display will switch to 1920x1600
3. Check for the Night Shift option, it should be there now
4. Turn it off and on again (or just on)
5. Switch back to fullscreen (so disable PBP)
6. If it's still on, good. If not
7. Turn on HDR and turn it off again
8. Night Shift should be active now. If not, repeat from step 1 until it's working

This is how I get it to work. This is quite the hassle, but if I do it once and leave the MacBook connected, my scheduled Night Shift works. It's not showing up in the menu, though, so if I want to change it, I'd need go back into PBP.