On Sat, 2010-01-02 at 10:15 +0200, Timo Aaltonen wrote: > On Fri, 1 Jan 2010, Geir Ove Myhr wrote: > > > On Fri, Jan 1, 2010 at 7:37 AM, Timo Aaltonen wrote: > >> going to 7.7 makes sense > >> blocker: libdrm needs to be updated to 2.4.17 (or newer) for new > >> intel/ati/nouveau/mesa. There are some known regressions though, and those > >> are being worked on.
Could you link me to the bugs / issues which have regressed (any specific for intel?) https://bugs.edge.launchpad.net/ubuntu/+source/libdrm/+bugs Just shows one open bug. I'm chasing an intermittent crash on mode-probe on Intel (with xorg-edgers), and I think that is somewhere in the libdrm / kernel side DRM code for the DRM_IOCTL_MODE_GETCONNECTOR IOCTL. Sometimes I'm getting a NULL mode_ptr after the second call to this IOCTL, in spite there being a positive mode count. I "suspect", that there is a possibility that the mode list changes between the first time libdrm calls the IOCTL (to get the counts), and the second - where it fills in the data. If an extra mode has appeared between the two calls, there is a size comparison which will fail, and the mode list won't get populated. This is rather tricky to debug though, as the problem is rather intermittent. I'm half expecting it ends up being due to some other intermittent mode detection code. About once in a thousand times, my X server comes up in a low-res mode, as if it were cloning a TV-out mode, with no TV attached.. (most linux intel drivers I can remember have done this on this laptop). Fun fun. Best regards, Peter Clifton -- Ubuntu-x mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-x
