https://bugzilla.kernel.org/show_bug.cgi?id=60710 --- Comment #5 from Alex Deucher <alexdeucher@xxxxxxxxx> --- (In reply to Chris Rankin from comment #4) > (In reply to Alex Deucher from comment #3) > > The hw i2c engine somehow got into a bad state. > > Not only that, but GNOME3 put the HW I2C engine back into that same "bad > state" when I rebooted and logged back in. (The DVI-0 monitor was switched > to a non-native 1680x1050 mode during the whole reboot process, but was then > shut down and disconnected when GNOME3 was unable to reconfigure it for its > native 1920x1200 mode). Well a warm reboot may not have fuly reset the hardware; the bad state may have persisted. > > > hw i2c is diabled by default for a reason. > > Yes, presumably because it has bugs like this in ;-). But surely that > doesn't mean you're not interested in people reporting those bugs when they > find them? Sure, I just wouldn't hold out much hope for a fix :) r5xx hardware is pretty old. -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
