Thanks Chris, that gives me some sense of optimism. Still I'm running Arch Linux, all up to date - and still facing the issue. Since you mentioned modesettigs I assume that this was a kernel related bug (I am not really into the topic, correct me if I'm all wrong). What release shipped the fix? Would you mind providing a reference to a related bug report or issue? I skimmed the release notes of 4.2.6 and 4.2.7 (Arch has 4.2.5) and could not find a hint on a fix related to KMS.
(Chris, sorry for the resend, I used the wrong sender addess and therefore the mailing list rejected my last answer) - Daniel On Mon, Dec 14, 2015 at 12:23 PM Chris Wilson <ch...@chris-wilson.co.uk> wrote: > On Mon, Dec 14, 2015 at 10:02:41AM +0000, Daniel Menet wrote: > > New to the list, please bear with me and give me hints if I violate > any > > rules. > > Its been a while now since I started facing an issue: xrandr only > lists > > mode after a while of waiting. I assume this happend after a upgrade > of > > some packages without an immediate reboot an occurred first after the > > reboot. I accepted the situation for a while due to the lack of time. > More > > details are given at > > [1] > http://unix.stackexchange.com/questions/240949/xrandr-only-lists-mode-after-a-while-of-waiting > > Should be resolved by now. It was just bug that mistakenly marked the first > current-only probe as valid on the initial modesetting. > -Chris > > -- > Chris Wilson, Intel Open Source Technology Centre >
_______________________________________________ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s