Mountain Lion Problems

[chandler767]

Applescript.

set the alert_message to "You may now plug in your DisplayLink device."
display dialog the alert_message buttons {"OK"} default button 1
set the my_choice1 to the button returned of the result
if my_choice1 is "OK" then
end if
on quit
	
	set the alert_message to "Unplug your DisplayLink device now."
	display dialog the alert_message buttons {"OK"} default button 1
	set the my_choice to the button returned of the result
	if my_choice is "OK" then
		tell application "Finder"
			continue quit
		end tell
		
	end if
	continue quit
end quit

[cmwade77]

Ok, so if we as a community can figure this out, shouldn't DsiplayLink be able to get a seamless solution working?

Also, is there a way to disable USB ports during the login process, then renable them automatically? If so, wouldn't this work the same as unplugging and plugging back in the device?

[chandler767]

Originally Posted by cmwade77

Ok, so if we as a community can figure this out, shouldn't DsiplayLink be able to get a seamless solution working?

Also, is there a way to disable USB ports during the login process, then renable them automatically? If so, wouldn't this work the same as unplugging and plugging back in the device?

Unfortunately its not that easy...

[Wim]

Hi All

About a week ago, Apple released v10.8.3 OSX update to developers. The release notes don't mention the login issue being fixed, but we have been testing this and the Login issues seem to have "gone away".

We're wondering if this is just coincidence in our testing, as we know it is timing related, or is it fixed for anyone else on here with access to the 10.8.3 developer release?

Thanks

Wim

[sltyler1]

Originally Posted by Wim

Hi All

About a week ago, Apple released v10.8.3 OSX update to developers. The release notes don't mention the login issue being fixed, but we have been testing this and the Login issues seem to have "gone away".

We're wondering if this is just coincidence in our testing, as we know it is timing related, or is it fixed for anyone else on here with access to the 10.8.3 developer release?

Thanks

Wim

I would, but I don't use the beta's anymore after a huge hiccup from using one of the beta's last year haha. Have you guys looked at chandler767's temporary solution? it's a simple work around and should help your techs if they don't already know the problems or how to find a solution around the current problems.

[briangig]

Ready for this one?

I haven't used my DisplayLink adapter in a few weeks, the drivers have long been uninstalled.

This week I was having some memory problems, related to the 16GB I updated to back in Sept. I finally isolated the bad DIMM, so I am running on one 8GB. I decided to boot into single user mode to double check this one with memtest overnight (this included a fsck of the main HD).

This morning I rebooted, and I have no login screen...I guess the location and login, and my Finder is crashing, just like I had the DL drivers installed. I ran the uninstaller from my Desktop, and it said no drivers found (which was correct).

I rebooted, and the login screen was there that time. I had to leave for work, but I thought this was a very bizarre issue.

TL;DR: I had the no login/Finder crashing problem with NO DisplayLink drivers installed after I ran memtest in single user mode overnight.

[kaci]

Originally Posted by Wim

Hi All

About a week ago, Apple released v10.8.3 OSX update to developers. The release notes don't mention the login issue being fixed, but we have been testing this and the Login issues seem to have "gone away".

We're wondering if this is just coincidence in our testing, as we know it is timing related, or is it fixed for anyone else on here with access to the 10.8.3 developer release?

Thanks

Wim

I am currently running 10.8.3 on my MBPR. I will use my display link driver to test.

[kaci]

Previously I posted that I would test the theory that issues with display link manager were fixed with 10.8.3. I have crash logs every day from 12/7/12- present of display link manager crashing. If it would be helpful I can send a zip of my logs.

[dkn]

It looks like it might be a general problem in Mac OS X 10.8 with third party display drivers.

I tried out AirParrot (external display via AirPlay on Apple TV - it also sets up a display driver) - exactly the same symptoms as described here:
* no login window (managed to log in simply by entering the password blindly)
* some types of output don't show - e.g. iTunes video

This is extremely uncool - devices are only partly functional.

If DisplayLink have a workaround, by all means please publish it.

If the problem can be traced to Apple.. well, blame Apple and demand a fix.

[jpap]

I've installed OS X 10.8.3 (12D38) on a late-2011 13" MBP, with a DL-195 connected to a 24" 90deg rotated DVI HP display.

No random crashes after a full week. The HP display doesn't go live until after login and looks as it should.

After a really bad DisplayLink driver-support issue on 10.7, I waited several months before upgrading to 10.8 and after seeing that 10.8 was "supported" on the driver download page. (Yes, the DL driver was the only thing holding me back!)

I did not have an appreciation of the severity of the issues in KB333 until I had experienced them myself. I would recommend not saying that 10.8 is supported on the Driver Download page until a user can use the driver normally. I don't consider random crashes of Finder and other apps, caused by a OS bug or DL driver issue, as being "supported".

Glad it wasn't your bug in the end, DL, but you still fail on communication. Luckily that's something you can easily fix going forward. ;-)

jpap

Originally Posted by Wim

Hi All

About a week ago, Apple released v10.8.3 OSX update to developers. The release notes don't mention the login issue being fixed, but we have been testing this and the Login issues seem to have "gone away".

We're wondering if this is just coincidence in our testing, as we know it is timing related, or is it fixed for anyone else on here with access to the 10.8.3 developer release?

Thanks

Wim