Hi,
I have a Macbook Pro that I very regularly hook up to my 32" LCD. It's running Leopard with all the latest updates. I've had this setup for a few months and pretty much I just plug the cable in and everything works perfectly, until recently that is... Nowadays it just stops sending output to the LCD sometimes. The display prefs will show 2 displays hooked up but normally the resolution on the LCD is 1360 * 768, yet in these instances it will show as 1440 * 900, like the internal display. "Detect displays" does nothing. So if I reboot the system with the cable plugged in it doesn't change anything. If I unplug it, then reboot, then plug it back in, it works fine, until the next time it stops working that is.
I thought this may be a hardware issue but I've pretty much ruled that out. I have Windows on Bootcamp and I've done some considerable testing over there and it works perfectly every time, so I can only conclude that something's gone wrong with Leopard. I think this only started happening after a recent update...
Thanks for any help on this.
I have a Macbook Pro that I very regularly hook up to my 32" LCD. It's running Leopard with all the latest updates. I've had this setup for a few months and pretty much I just plug the cable in and everything works perfectly, until recently that is... Nowadays it just stops sending output to the LCD sometimes. The display prefs will show 2 displays hooked up but normally the resolution on the LCD is 1360 * 768, yet in these instances it will show as 1440 * 900, like the internal display. "Detect displays" does nothing. So if I reboot the system with the cable plugged in it doesn't change anything. If I unplug it, then reboot, then plug it back in, it works fine, until the next time it stops working that is.
I thought this may be a hardware issue but I've pretty much ruled that out. I have Windows on Bootcamp and I've done some considerable testing over there and it works perfectly every time, so I can only conclude that something's gone wrong with Leopard. I think this only started happening after a recent update...
Thanks for any help on this.