Blue Dude
January 26th, 2012, 04:46 AM
I have a somewhat unorthodox display setup. I re-purposed an older computer running Ubuntu 10.04 LTS to act as a file server, but since I don't have a spare monitor, and usually don't need one, I have the display output piped through a DVI-to-HDMI connection to an A/V receiver, and then out to my TV. I usually don't have a keyboard or mouse connected to it, though I can if needed. Works great, and in the event I need to do anything with the OS, I just use TightVNC to "remote desktop" to the Gnome desktop. All is well, except...
If I reboot the system remotely, with the A/V receiver turned off (i.e. no EDID info, so apparently no display device connected), the graphical desktop does not start. The file server does start, and so does the SSH server, so I can command line into the system, but VNC being dependent on Gnome does not.
I think this is a recent problem, and I have changed very little except install the latest image and Kino. I don't recall having to turn on the receiver first before booting, but I don't try to reboot very often either.
My question is this: How do I force the system to start up a Gnome session, perhaps with an assumed display device and resolution, without the display device being turned on first?
If I reboot the system remotely, with the A/V receiver turned off (i.e. no EDID info, so apparently no display device connected), the graphical desktop does not start. The file server does start, and so does the SSH server, so I can command line into the system, but VNC being dependent on Gnome does not.
I think this is a recent problem, and I have changed very little except install the latest image and Kino. I don't recall having to turn on the receiver first before booting, but I don't try to reboot very often either.
My question is this: How do I force the system to start up a Gnome session, perhaps with an assumed display device and resolution, without the display device being turned on first?