Go Back   DisplayLink Forum > DisplayLink Graphics Technology > Mac Software

Reply
 
Thread Tools Search this Thread Display Modes
Old 06-09-2017, 04:11 PM   #41
silence
Junior Member
 
Join Date: Jun 2017
Posts: 1
Default

Quote:
Originally Posted by Carlo View Post
Can you please copy and paste the log message? It may be a new one.

Kind regards,
Carlo
Can confirm this is an issue on Sierra 12.12.5. My log looks exactly like dude123's, and the existing fix no longer works.
silence is offline   Reply With Quote
Old 06-12-2017, 12:29 AM   #42
steve_s
Junior Member
 
Join Date: Jun 2017
Posts: 1
Default

Quote:
Originally Posted by dude123 View Post
Yes sure!

Code:
 No matching context for device (0x7fe957c26f90) - disabling OpenGL
Sender:
/System/Library/PrivateFrameworks/SkyLight.framework/Resources/WindowServer
(/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight)

Subsystem:
com.apple.SkyLight
I am getting the same behavior, running Sierra, with a different 0x... number:

Code:
No matching context for device (0x7ff8ca335340) - disabling OpenGL
steve_s is offline   Reply With Quote
Old 06-13-2017, 12:28 PM   #43
wa2flq
Junior Member
 
Join Date: Jun 2017
Posts: 2
Unhappy Can not reproduce the "ignore" fix.

Quote:
Originally Posted by mcousins View Post
I seem to have stopped the log spam by adding this to my asl.conf in /etc at the top of the file

? [= Sender WindowServer] ignore

And then performing the sudo kill -HUP [PID of process]
I've tired this asl.conf. I can't seem to make it work in Sierra.
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?
wa2flq is offline   Reply With Quote
Old 06-22-2017, 01:16 PM   #44
duncanm
Junior Member
 
Join Date: Jun 2017
Posts: 1
Default 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"
where [PID] is the ID of the process you see in the console.

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
duncanm is offline   Reply With Quote
Old 06-23-2017, 02:49 AM   #45
wa2flq
Junior Member
 
Join Date: Jun 2017
Posts: 2
Default

That works, thanks.
wa2flq is offline   Reply With Quote
Old 07-27-2017, 08:52 PM   #46
dude123
Junior Member
 
Join Date: May 2017
Posts: 3
Default

Quote:
Originally Posted by duncanm View Post
As a temporary fix you can enter the following in your terminal:

Code:
sudo log config --process=[PID] --mode "level:off"
where [PID] is the ID of the process you see in the console.

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
Yes, can confirm, this is the first "solution" that works on Sierra.
MacOS 10.12.6 - DisplayLink 3.1
dude123 is offline   Reply With Quote
Old 09-07-2017, 05:43 AM   #47
benwen
Junior Member
 
Join Date: Dec 2014
Location: San Francisco
Posts: 1
Default

Quote:
Originally Posted by duncanm View Post
As a temporary fix you can enter the following in your terminal:

Code:
sudo log config --process=[PID] --mode "level:off"
where [PID] is the ID of the process you see in the console.

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
Thank you duncamn!

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"
Put that in a file 'quite-dlink' in your $PATH, chmod 0755 it and execute it in Terminal at startup.
benwen is offline   Reply With Quote
Old 09-11-2017, 12:47 PM   #48
paultzirides
Member
 
Join Date: Jun 2013
Posts: 33
Default 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?
paultzirides is offline   Reply With Quote
Reply

Tags
windowserver

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 09:16 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2017, vBulletin Solutions, Inc.