On Mon, Jul 15, 2013 at 07:37:47 +0100, Robert de Bath wrote: > On Sun, 9 Jun 2013, Julien Cristau wrote: > > >><<! > >> blacklist i915 > >> options i915 modeset=1 > >>>>! > >> > >Not going to happen. > > > > Can't say I'm surprised, especially, as thinking some more on it, X > doesn't have to be installed for the bug to manifest. > > As a, somewhat, interested party, where do you think the bug should reside? > If i915 doesn't give you a working display that's a kernel bug. > Should X really be honouring the blacklist flag, DESPITE, the fact that once > you put X on top of the driver it actually works? Does the modprobe.d file > format need a 'blacklist for all except X'. Especially as it's normal for > the package manager to install ALL the X video drivers. > > What would you do if one of the other utils added "modeset=0" ? (Breaking X) File a serious bug against whichever package does that. > Is it an X bug that X doesn't work with the driver if that option is > set ? Is it a kernel bug ? > Neither. Cheers, Julien
Attachment:
signature.asc
Description: Digital signature