07-25-2011 05:30 AM
as I didn't find a matching thread I have to describe my problem in a new one. However, if the issue is already covered in another thread, I'd be pleased if you could just paste the link to the thread.
I'm using a W500 with an advanced minidock.
Usually I use the notebokk with closed lid in the docking station with a HP LCD connected.
When I undocked the notebook and opened the lid afterwards the display switched to the notebook display.
For a few days now the problem is that the display turns black after I open the lid. If you are fast enough you can see the picture on the notebook display shortly after opening it, but then it turns black.
Even FN + F7 doesn't switch it on again. Also FN + F7, "Arrow down", "Return" (to choose a profile blindely in the PD) doesn't work.
If I put the notebook back again into the docking station the display recovers again.
If I open the display before undocking the notebook. The display doesn't turn off.
I tried updateing the presentation director, using different profiles for docked and undocked. Nothing helped.
I have a "docked" profile which is set to "use after docking the notebook". This step works. So if I use another profile and dock the notebook it switches to the designated profile.
When I undock the notebook (with open lid) there's no switching to another profile.
The docked profile is set as "clone displays". As I don't have a wide screen lcd yet, there are black sidebars on the notebook display when docked with open lid.
After undocking the screen on the notebook expands to a matching resolution for the widescreen of the notebook, althoug it's the same pd profile.
Does anybody have an idea how to get back to the behavior that the screen doesn't turn black after opening the lid after undocking the notebook?
Right now I set the FN + F7 beaviour to switch between external and internal screen, so I'm able to get a picture if I forget to open the lid before undocking.
Of course, this works fine and it's only one shortcut, but it would be good to have the old behavior back.
Solved! Go to Solution.
07-31-2011 09:39 PM