Go Back   DisplayLink Forum > DisplayLink Graphics Technology > Mac Software

Reply
 
Thread Tools Search this Thread Display Modes
Old 10-20-2014, 02:12 PM   #21
BMT
Junior Member
 
Join Date: Oct 2013
Posts: 18
Default

Quote:
Originally Posted by Carlo View Post
In 2.2 we started using a new API for an important part of the driver. The previous API has been deprecated and its reliability was rapidly decaying with every new OS version.
The new API has benefits but has some issues as well, one of which is the log spamming in some situations. We have raised all issues with Apple.

I cannot share any more information on this I'm sorry

Cheers
Carlo
I see, that makes sense - thanks for the explanation.
BMT is offline   Reply With Quote
Old 10-23-2014, 07:20 PM   #22
tmendo
Junior Member
 
Join Date: Oct 2014
Posts: 1
Default

Have should I write in the report for Apple? I want to file a bug report also but not sure what I should write to make it more accurate and less prone to be rejected.
tmendo is offline   Reply With Quote
Old 11-08-2014, 09:04 PM   #23
jb8748
Junior Member
 
Join Date: Nov 2014
Posts: 4
Default

I've made a configuration file for ASL to claim all these messages and then ignore them. Seems to be a reasonable solution until such time as a bug fix is available.

http://blog.jamesball.co.uk/2014/11/...nk-driver.html
jb8748 is offline   Reply With Quote
Old 11-10-2014, 10:24 AM   #24
Seemone
Junior Member
 
Join Date: Nov 2014
Posts: 1
Default

A finer workaround would be to add

? [= Sender WindowServer] ignore

in the first line of asl.conf (in the etc directory) and then restart syslog by issuing

kill -hup <PID>

where PID is the syslog process pid

This will filter out only WindowServer messages instead of cutting all the syslog output
Seemone is offline   Reply With Quote
Old 11-12-2014, 01:48 PM   #25
BMT
Junior Member
 
Join Date: Oct 2013
Posts: 18
Default

Disregard.

Last edited by BMT; 11-27-2014 at 10:11 PM. Reason: Problem fixed.
BMT is offline   Reply With Quote
Old 11-12-2014, 06:36 PM   #26
mcousins
Junior Member
 
Join Date: Nov 2014
Posts: 1
Default

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]

Not sure if that's OK, I tried the other way of creating a file under the asl folder and that did nothing for me.

Hope this helps, even if its just towards finding a better answer!
mcousins is offline   Reply With Quote
Old 11-13-2014, 05:18 PM   #27
ehendrix
Member
 
Join Date: Aug 2011
Posts: 39
Default

I changed it a little bit to:

# WindowServer messages about display context (caused by DisplayLink driver)
? [= Sender WindowServer] [= Level Warning] [A= Message _CGXGLDisplayContextForDisplayDevice] claim only

Seems to be working and ensures that any other messages from WindowServer are still going in.
ehendrix is offline   Reply With Quote
Old 11-20-2014, 09:42 PM   #28
ehendrix
Member
 
Join Date: Aug 2011
Posts: 39
Default

No more messages since I've put this in. Interesting that with all the complaining about this within the forums that DisplayLink was never able to provide this as a solution.
Is it perfect? No.
Is it something Apple should fix? yes
Does the work-around work? Heck yes.
Could DisplayLink provide the work-around? Don't see why not.
ehendrix is offline   Reply With Quote
Old 11-21-2014, 08:12 AM   #29
Carlo
Mac Team
 
Carlo's Avatar
 
Join Date: Feb 2009
Posts: 606
Default

Hi ehendrix,

Sorry for going quiet on this one. Yes we think this is a good workaround, we could apply it at install time.

We'd use
? [= Sender WindowServer] [=S Message_CGXGLDisplayContextForDisplayDevice] ignore

Unless anyone can spot any issue with the approach?

Cheers,
Carlo
Carlo is offline   Reply With Quote
Old 11-26-2014, 03:43 PM   #30
jb8748
Junior Member
 
Join Date: Nov 2014
Posts: 4
Default

Quote:
Originally Posted by ehendrix View Post
I changed it a little bit to:

# WindowServer messages about display context (caused by DisplayLink driver)
? [= Sender WindowServer] [= Level Warning] [A= Message _CGXGLDisplayContextForDisplayDevice] claim only

Seems to be working and ensures that any other messages from WindowServer are still going in.
Thank you ehendrix. That does look like a better command - I'm no expert on the logging so I was finding things that worked. I've updated my blog post.

James
jb8748 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 06:29 PM.


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