Re: Bug#711305: Loading i915 with modeset=1 disables display
On Mon, 15 Jul 2013, Julien Cristau wrote: On Mon, Jul 15, 2013 at 07:37:47 +0100, Robert de Bath wrote: On Sun, 9 Jun 2013, Julien Cristau wrote: If i915 doesn't give you a working display that's a kernel bug. Thanks, I'll add my voice to the multitude over there. Is it an X bug that X doesn't work with the driver if that option is set ? Is it a kernel bug ? Neither. OTOH, I think this should belong to at least one of them as it's a valid configuration option for the end user. They can reasonably choose to not have a graphic display unless they start X. In that way I think it's Both. X has a bug in that it can't configure the driver properly. The kernel is bugged in that it can't remove the driver and restore the display back to what it should be without a reboot. But I suppose both projects will look on this as some sort of reasonable limitation and so WONTFIX. Anyway, thankyou for your time. -- Rob. (Robert de Bath robert$ @ debath.co.uk) http://www.debath.co.uk/ -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.DEB.2.00.1307161929301.21887@mayday
Re: Bug#711305: Loading i915 with modeset=1 disables display
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 signature.asc Description: Digital signature
Bug#711305: Loading i915 with modeset=1 disables display
Package: xserver-xorg-video-intel Version: 2:2.13.0-7 This is an interaction of several different packages. Firstly, as you know the X video driver needs the i915 module to be loaded to work correctly; furthermore it requires the module to attempt to set the video mode during initilisation. Without this X doesn't load the video driver. With it the driver get loaded and works correctly. But, the kernel driver is buggy, if loaded with modeset=1 it will corrupt the display controller blanking the display. Unfortunatly, udev loads all drivers it can during the boot and uses the configuration set for modprobe. Luckily, someone seems to have though of this. When udev loads modules it supplies the --use-blacklist option, whereas X calls modprobe without the --use-blacklist option. So please set the contents of the file /etc/modprobe.d/i915-kms.conf to this: ! blacklist i915 options i915 modeset=1 ! This means it isn't loaded during boot and is loaded correctly when X starts. It also means that xinit true loads the video driver correctly and fixes the screen mode after booting vga=0x305 ... bit of an overkill but never mind that :-) It seems I also need it on one machine for the radeon driver; this being so I would suggest it's a good idea for all drivers using kms and requiring the kernel to do a modeset. -- Rob. (Robert de Bath robert$ @ debath.co.uk) http://www.debath.co.uk/ -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.DEB.2.00.1306060856340.21887@mayday
