OS X 10.8.2 update - all working ok so far

[creamhackered]

Hi guys,

Just thought I'd let ya know that all is working well for me, I am using display rotation too.

[Stephen]

I wanted to sound in as well, it appears that 10.8.2 have fixed some of the issues. LaunchPad, which I rarely use at work still causes the the CPU to spike and my MacBookPro to lock up.

Password on the screen saver works, jumpy youtube videos are fixed.

[chandler767]

So all the issues with the 1.8 driver are fixed in 10.8.2? Downloading now to confirm.

Edit: Didn't fix the driver issues. ):

[undo]

Confirmed, works with 10.8.2

apply the update, restart
uninstall driver, restart
reinstall driver, restart

voila :)

[unusedusername]

Edit: Didn't fix the driver issues. ):

Yes. I followed the uninstall driver, update OS, reinstall driver path and I still have the same issues.

I have 2 USB connected monitors both are Dell 1907FP connected via DVI to 2 different BVU195 adapters which are plugged directly into the USB ports on the side of the Mac. Machine is a early 2011 17" Macbook pro. Monitors are not rotated and are all in one horizontal line.

(laptop's internal screen)(USB monitor)(Video card external monitor)(USB monitor)

Strange text blurring happens on both of the USB monitors and also the GUI buttons for some apps are not drawn in the same location as where you click to activate them (Firefox).

This is exactly the same issue I had before this update.

Any news on a fix?

[VA2SS]

Seems to work for me too so far !!!

1- Uninstall 1.7 driver
2- Install OS X 10.8 over 10.7
3- Upgrade to OS X 10.8.2
4- Install 1.8 driver

No login behavior anymore
No corrupted applications
Only background did not saved properly.... but it is not a big deal !!

Thanks to .......... A P P L E :p

[rod242]

Unfortunately I don't think installing OSX 10.8.2 reliably fixes the problem.

After installing 10.8.2 and uninstalling/reinstalling the DisplayLink (1.8) driver, all of the symptoms from before are still present ... and in fact are present immediately.

On OSX 10.8.1 I could install the driver, usually work for most of the day, then have problems and uninstall/re-install the driver. Now its stuffed as soon as I install the driver :-(

I really wish DisplayLink would make a comment on what is happening.... the silence is deafening.

[cmwade77]

I just posted on the other thread about Mountain Lion problems that I may have found a work around, but I won't be able to fully test it until tomorrow at work. The work around is not ideal, but if it works, I will post it.

[Stephen]

After a few days, I am beginning to have issues again under OS 10.8.2, so I am not certain what is going on.

[shoffman]

uninstalled 1.8 (weeks ago now:mad:)
upgraded to 10.8.2 --> rebooted
installed 1.8 --> rebooted

Immediately got the "hidden" username/password box, logged in anyway and used hot corners to activate screensaver and apps started crashing just as before... For me, 10.8.2 didn't fix anything.

*sigh* I guess I'll stare at my blank 24" monitor a while longer...

[VA2SS]

Seems to work for me too so far !!!

1- Uninstall 1.7 driver
2- Install OS X 10.8 over 10.7
3- Upgrade to OS X 10.8.2
4- Install 1.8 driver

No login behavior anymore
No corrupted applications
Only background did not saved properly.... but it is not a big deal !!

Thanks to .......... A P P L E :p

Still working for me since september 20th. Crossing my finger :D

Installation steps are crucial.

[mcfrantzen]

I have a MacBook Pro (mid-2012) running 10.8.2. Installed the 1.8 driver and found that many programs would not run, flash games did not run, advertisement on various news websites would not load, Safari downloads button would not show the downloads (had to search for the 1.8 driver manually in the downloads folder). A simple uninstall recovered my machine, but cannot use USB graphics card. Whats wrong? :confused:

[Dracnath]

It seems ages since we've had word from anyone on these issues. Does anyone know of an open source Mac driver? Maybe we need to start work on one! We should be able to use the Linux one as a starting point.

[stevedave]

It seems ages since we've had word from anyone on these issues. Does anyone know of an open source Mac driver? Maybe we need to start work on one! We should be able to use the Linux one as a starting point.

I know its been awhile since we've heard anything from DL. I suggest we all take pictures of the issues we're having them. Then tag DL's facebook page with the issues.

They aren't answering so perhaps we take this to a more public forum.

[Wim]

Hi All

It's good that it looks like Apple have addressed some of the issues we have been working on. A summary of our plans for releasing a new driver are summarised here:

http://displaylink.org/forum/showthread.php?t=2007

Wim

[andynormancx]

It's good that it looks like Apple have addressed some of the issues we have been working on. A summary of our plans for releasing a new driver are summarised here:

Your plans to fix the problem involve us all not using the products we bought for yet another 3 months, at least.

It really seems like there is little urgency from DL to get this problem fixed. Unless you are just waiting on Apple to fix something, why exactly is there a three month delay between now and when you think the problem will be fixed ?

Is there still development effort involved in fixing the problem or is the three months some sort of extended QA period ?

As a software developer myself I don't understand how you can be sure that you already know how to fix the problem AND you know it is going to take AT LEAST 3 months to fix.

[Wim]

We are working on a Mac 2.0 software release which uses our latest core code and to write a new interface to the Mac Operating system. This involves writing new Mac virtual graphics drivers, device detection, USB video driver, audio driver and Ethernet driver. And making sure that our latest video encoder works efficiently on a Mac. That's quite a lot of work.

Once we have the new architecture, the core code gives us much more flexibility to workaround bugs found in the Apple OSX, if Apple does not address them.

With V1.8 release and older, it is getting harder to try and address a problem without breaking something else in the code. This is why V1.8 is on "life support" and you're not seeing a lot of updates.

We're trying to address the most critical bugs to make sure you can still use USB 2.0 devices. But rather than sinking more of the engineering team's time into this code stream, we want to get v2.0 out as soon as possible, as it will give the best long term solution.

Wim

[cmwade77]

We are working on a Mac 2.0 software release which uses our latest core code and to write a new interface to the Mac Operating system. This involves writing new Mac virtual graphics drivers, device detection, USB video driver, audio driver and Ethernet driver. And making sure that our latest video encoder works efficiently on a Mac. That's quite a lot of work.

Once we have the new architecture, the core code gives us much more flexibility to workaround bugs found in the Apple OSX, if Apple does not address them.

With V1.8 release and older, it is getting harder to try and address a problem without breaking something else in the code. This is why V1.8 is on "life support" and you're not seeing a lot of updates.

We're trying to address the most critical bugs to make sure you can still use USB 2.0 devices. But rather than sinking more of the engineering team's time into this code stream, we want to get v2.0 out as soon as possible, as it will give the best long term solution.

Wim
Sounds like all work needs to stop on 2.0 until you can get 1.8.1 out, get it out the door, get everyone back up and running, then resume work on 2.0, leaving one or 2 people to work on problems in 1.8.1 for a week or two and the completely ignore it, focusing solely on 2.0.

[andynormancx]

That's great, I guess. But in the meantime I and many others are sat staring at useless blank screens for another 3 months or more.

If it really is going to be another 3+ months I'll have to go and find another solution, I can't work without my second external monitor for much longer. It won't unfortunately be a DL based product of course :(

It isn't as if we are talking about a discontinued product here, the non functioning adapter I own is still on sale to unsuspecting customers who are going to get a shock when it doesn't work with the latest version of OSX. I note that the driver download page makes no mention of the Mountain Lion problems.

[GodwinC]

I think the key is if using Displaylink.. don't ever let the machine goes to screen saver / power save..

[andynormancx]

I think the key is if using Displaylink.. don't ever let the machine goes to screen saver / power save..

When my DisplayLink driver is causing problems there is no screen saver or power save involved. It can sometimes be in its broken state immediately after booting for the first time after installing it.

[GodwinC]

In that case, make sure DMProxy is loading correctly when you plug it in.. it should say something like, I also find some microUSB cables are junk:


2012-10-04 10:06:20.214 AM WindowServer[80]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'.
2012-10-04 10:06:20.270 AM WindowServer[80]: Display 0x04273740: MappedDisplay Unit 0; ColorProfile { 2, "iMac"}; TransferTable (256, 3)
2012-10-04 10:06:20.271 AM WindowServer[80]: Display 0x2b34488d: MappedDisplay Unit 1; ColorProfile { 3, "DELL U2212HM"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.272 AM WindowServer[80]: Display 0x04273740: MappedDisplay Unit 0; ColorProfile { 2, "iMac"}; TransferTable (256, 3)
2012-10-04 10:06:20.272 AM WindowServer[80]: Display 0x2b38400f: MappedDisplay Unit 3; ColorProfile { 4, "DELL 2005FPW"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.273 AM WindowServer[80]: Display 0x2b34488d: MappedDisplay Unit 1; ColorProfile { 3, "DELL U2212HM"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.274 AM WindowServer[80]: Display 0x2b38400f: MappedDisplay Unit 3; ColorProfile { 4, "DELL 2005FPW"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.275 AM WindowServer[80]: Display 0x04273740: MappedDisplay Unit 0; ColorProfile { 2, "iMac"}; TransferTable (256, 3)
2012-10-04 10:06:20.276 AM WindowServer[80]: Display 0x2b34488d: MappedDisplay Unit 1; ColorProfile { 3, "DELL U2212HM"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.276 AM WindowServer[80]: Display 0x2b38400f: MappedDisplay Unit 3; ColorProfile { 4, "DELL 2005FPW"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.334 AM WindowServer[80]: Display 0x04273740: MappedDisplay Unit 0; ColorProfile { 2, "iMac"}; TransferTable (256, 3)
2012-10-04 10:06:20.334 AM WindowServer[80]: Display 0x04273740: MappedDisplay Unit 0; ColorProfile { 2, "iMac"}; TransferTable (256, 3)
2012-10-04 10:06:20.335 AM WindowServer[80]: Display 0x04273740: MappedDisplay Unit 0; ColorProfile { 2, "iMac"}; TransferTable (256, 3)
2012-10-04 10:06:20.335 AM WindowServer[80]: Display 0x2b34488d: MappedDisplay Unit 1; ColorProfile { 3, "DELL U2212HM"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.336 AM WindowServer[80]: Display 0x2b34488d: MappedDisplay Unit 1; ColorProfile { 3, "DELL U2212HM"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.336 AM WindowServer[80]: Display 0x2b34488d: MappedDisplay Unit 1; ColorProfile { 3, "DELL U2212HM"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.337 AM WindowServer[80]: Display 0x2b38400f: MappedDisplay Unit 3; ColorProfile { 4, "DELL 2005FPW"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.337 AM WindowServer[80]: Display 0x2b38400f: MappedDisplay Unit 3; ColorProfile { 4, "DELL 2005FPW"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.338 AM WindowServer[80]: Display 0x2b38400f: MappedDisplay Unit 3; ColorProfile { 4, "DELL 2005FPW"}; TransferFormula (1.000000, 1.000000, 1.000000)


When my DisplayLink driver is causing problems there is no screen saver or power save involved. It can sometimes be in its broken state immediately after booting for the first time after installing it.

[cmwade77]

I think the key is if using Displaylink.. don't ever let the machine goes to screen saver / power save..

Mine had gone to power save just fine all the time using the work around I posted earlier, but did not always work on boot, which is why we have gone over to the J5 Create devices with Mountain Lion systems for now, we have two other systems that we want to upgrade, but are trying to wait for the DisplayLink drivers.

3 Months will not work for our time frame that we want to upgrade within, ideally we would like to have this done by the end of next week, which means we need time to test the drivers on one system today or Monday, at the latest.