On Mon, Aug 2, 2010 at 2:07 AM, Yann Dirson <ydir...@free.fr> wrote: > On Sun, Aug 01, 2010 at 10:12:27PM -0400, Alex Deucher wrote: >> On Mon, Jul 26, 2010 at 3:21 PM, Yann Dirson <ydir...@free.fr> wrote: >> > Package: xserver-xorg-video-radeon >> > Version: 1:6.13.1-2 >> > Severity: normal >> > >> > Turning on my box, I see the monitor claiming no video output. >> > Checking video cable, I see it was not fully plugged and fixed that, >> > but got no change. Logging remotely I see (log below) that the server >> > indeed failed to start because of this. Restarting gdm fixed the >> > problem. >> > >> > It is a very unfriendly behaviour indeed. Google shows people with >> > other video chips got a similar issue, so indeed the problem may not >> > be specific to the radeon driver, please reassign as see fit. >> > >> >> Unfortunately, if there is no monitor plugged in, the driver has no >> way of know what's connected, so it has no idea what connectors to >> light up. That said, in xserver 1.9, the xserver will start with a >> default 1024x768 framebuffer and no connected outputs, and if you are >> using kms and a hotplug enabled driver, you will get an event when a >> monitor finally gets plugged in. > > That's more like what I'd have expected. Can be considered fixed-upstream ? >
I suppose so, although only kms drivers will work properly in that scenario. Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
