KMS:RV635:Radeon 3650HD graphics driver broken on a laptop when connected to a docking station and external display

[Pasi Kärkkäinen]

On Thu, Jun 03, 2010 at 11:00:44AM -0400, Alex Deucher wrote:
> >> >>
> >> >
> >> > I just tried with Ubuntu 10.04 (kernel 2.6.32) and it fails in a similar way than F13 (kernel 2.6.33) does.
> >> >
> >> > To summarize:
> >> >        - Booting the laptop in the dock, both the internal laptop display and the external DVI display connected,
> >> >          shows the beginning of the boot process on the internal display and then both displays go blank.
> >> >
> >> >        - Booting the laptop in the dock, internal display in use and the external display powered *off*,
> >> >          shows the kernel boot process on the internal display but when GDM should show up the internal display goes blank.
> >> >          Nothing on the external display either (if I power it on).
> >> >
> >> >        - Booting the laptop without the dock (and without the external display) works OK, I can see kernel boot process and GDM/X just OK.
> >> >
> >> >        - Booting the laptop without the dock, and attaching it to the dock after X is running allows me to use (=enable) the external display once.
> >> >          But Gnome Monitor application shows the external display twice (as two devices)..
> >> >
> >>
> >> Does it work if you boot with the laptop in the dock and then after it
> >> boots attach the external monitor and enable it?  Do things work any
> >> better if you use xrandr rather than the gnome displays tool?
> >>
> >
> > I just shutdown the laptop, connected it to the dock,
> > disconnected the DVI cable from the dock, and then powered on the laptop.
> > Now the boot process was OK using the laptop internal display.. gdm and X
> > showed up on the internal display OK.
> >
> > When I was in X I connected the DVI cable to the dock, and went to gnome
> > Monitors application. Same thing - the external display is shown as
> > two separate devices. Although they don't work - no matter which one
> > of the external displays I choose I don't get picture on the external DVI display.
> >
> > I also tried with xrandr:
> >
> > $ xrandr
> > Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192
> > VGA-0 disconnected (normal left inverted right x axis y axis)
> > LVDS connected 1680x1050+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
> >   1680x1050      60.0*+
> >   1400x1050      60.0     60.0
> >   1280x1024      59.9     60.0
> >   1440x900       59.9
> >   1280x960       60.0     59.9
> >   1280x854       59.9
> >   1280x800       59.8
> >   1280x720       59.9
> >   1152x768       59.8
> >   1024x768       60.0     59.9
> >   800x600        60.3     59.9     56.2
> >   848x480        59.7
> >   720x480        59.7
> >   640x480        59.9     59.4
> > DVI-0 connected (normal left inverted right x axis y axis)
> >   1920x1080      59.9 +
> >   1600x1200      60.0
> >   1680x1050      60.0
> >   1280x1024      60.0
> >   1440x900       59.9
> >   1280x960       60.0
> >   1280x800       59.8
> >   1024x768       60.0
> >   800x600        60.3     56.2
> >   640x480        60.0
> > HDMI-0 connected (normal left inverted right x axis y axis)
> >   1920x1080      59.9 +
> >   1600x1200      60.0
> >   1680x1050      60.0
> >   1280x1024      60.0
> >   1440x900       59.9
> >   1280x960       60.0
> >   1280x800       59.8
> >   1024x768       60.0
> >   800x600        60.3     56.2
> >   640x480        60.0
> >
> > $ xrandr --output DVI-0 --right-of LVDS
> >
> > Didn't make a difference.. no picture on the external DVI display.
> >
> > I wonder if that HDMI-0 is the key to the problem.. I don't have anything connected
> > to the HDMI connector on the laptop. There's no HDMI connector on the dock, it's only in the laptop.
> 
> Indeed that is the problem.  On your system the HDMI and DVI ports
> share the same encoder and DDC line so they will both come up as
> connected since the line is shared.  The driver used to check the edid
> when the lines where shared and select HDMI or DVI based on the EDID,
> but perhaps that got broken at some point.
> 

Makes sense. Does some kernel option/parameter affect that? 

-- Pasi