|
|
Thread Tools | Search this Thread | Display Modes |
06-09-2017, 04:11 PM | #41 |
Junior Member
Join Date: Jun 2017
Posts: 2
|
|
06-12-2017, 12:29 AM | #42 | |
Junior Member
Join Date: Jun 2017
Posts: 1
|
Quote:
Code:
No matching context for device (0x7ff8ca335340) - disabling OpenGL |
|
06-13-2017, 12:28 PM | #43 | |
Junior Member
Join Date: Jun 2017
Posts: 6
|
Can not reproduce the "ignore" fix.
Quote:
I have SIP (temporarily) turned off. Also tried this in /etc/asl/com.apple.windowserver and com.displaylink.windowserver. I can see that aslmanager is restarting after the HUP to syslog. I still see tons of messages in the Console. Any thoughts as to what I am doing wrong? |
|
06-22-2017, 01:16 PM | #44 |
Junior Member
Join Date: Jun 2017
Posts: 1
|
Stopping log spam in sierra
As a temporary fix you can enter the following in your terminal:
Code:
sudo log config --process=[PID] --mode "level:off" You have to re-do it every time you re-start your mac which is a pain, but at least it saves all those writes to your disk |
06-23-2017, 02:49 AM | #45 |
Junior Member
Join Date: Jun 2017
Posts: 6
|
That works, thanks.
|
07-27-2017, 08:52 PM | #46 | |
Junior Member
Join Date: May 2017
Posts: 4
|
Quote:
MacOS 10.12.6 - DisplayLink 3.1 |
|
09-07-2017, 05:43 AM | #47 | |
Junior Member
Join Date: Dec 2014
Location: San Francisco
Posts: 1
|
Quote:
Here's a quick and dirty shell script to automate the finding of the PID Code:
#!/bin/sh pid=`ps -ax | awk '/SkyLight.framework/ && !/awk/ {print $1}'` echo "Skylight.framework with OpenGL logorrhea PID found. Suppressing log for PID $pid" sudo log config --process=$pid --mode "level:off" |
|
09-11-2017, 12:47 PM | #48 |
Member
Join Date: Jun 2013
Posts: 50
|
Still necessary?
After installing the 4.0 beta, I'm no longer noticing any log spam. I ran the terminal command anyway, but observed no change in the amount or type of logs being generated by the system. Is anyone else seeing the same?
|
09-30-2017, 02:33 AM | #49 |
Junior Member
Join Date: May 2017
Posts: 4
|
Problem solved!!!
Update to 4.0 didn't make it better on macOS 10.12 - BUT after the system update to 10.13 combined with 4.0 - now finally the log spam is solved and on top of that also the hardware support for video etc is very much improved. Well done!! Thank you a lot DisplayLink-Team!!!! |
10-24-2017, 05:43 PM | #50 |
Junior Member
Join Date: Apr 2015
Posts: 2
|
My new MacBook Pro running 10.12.6 and with DisplayLink 4.0.0 is filling up my Console with this error message.
I see where 10.13 might fix it but that is not an option on this work computer. Any suggestions on how to get this to stop? |
Tags |
windowserver |
|
|