Dialog pops up indicating switching to low resolution mode when no monitor is connected
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| xserver-xorg-video-intel (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: xserver-
This is the situation:
I have two PCs, both running Ubuntu, but only one set of monitor, keyboard and mouse. My idea was to set up Ubuntu on the new PC, leave it connected to the network, and VNC into the new machine from the old one.
Ubuntu is set up properly on the new machine with the monitor connected - the monitor is displayed correctly, the driver is loaded properly, resolution set properly. However, when I remove the monitor, re-boot the box, and try to VNC into it from the old machine, VNC fails to connect.
When I connect back the monitor, I notice that there is dialog popped up asking for user input - to confirm that the display will be switched into low resolution mode and if it is ok. Once I dismiss the dialog, the system boots into 640 x 480 and then I can vnc in.
When I reboot the machine again without the monitor connected, the same dialog pops and hence VNC from old machine fails to connect.
However, these are the questions I have.
1. I understand that since no monitor is connected, the driver tries to set 640 x 480. However, why should a dialog be popped up? There is no monitor connected, which I guess can be detected, and in this case, isn't it odd to expect the user to provide an input??
2. Is there a way to set the resolution that the system would boot into when there is no display connected??
My graphics component is Intel GMA 3100, the driver loaded is intel, monitor being used is a Dell 15" with a max resolution of 1024 x 768 @ 85 Hz.
Do let me know if you need any other information.
Regards
Radha.
| Bryce Harrington (bryce) wrote | #1 |
| Changed in xserver-xorg-video-intel: | |
| status: | New → Invalid |
Youve' got sort of a non-standard config, but I think you can make it work. Shut off gdm on the remote machine (System > Admin > Services), and if you want X running on it, modify your boot scripts to launch X via startx.
You may also want to check into XvMC.
Since this is a pretty non-standard config, this is being closed as not a bug, however please feel free to file a blueprint with a proposal for an alternative way way of handling this kind of a setup.