[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#711305: marked as done (Loading i915 with modeset=1 disables display)

Your message dated Sun, 9 Jun 2013 16:35:39 +0200
with message-id <20130609143538.GG19497@radis.cristau.org>
and subject line Re: Bug#711305: Loading i915 with modeset=1 disables display
has caused the Debian Bug report #711305,
regarding Loading i915 with modeset=1 disables display
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
711305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711305
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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/>

--- End Message ---
--- Begin Message --- 
On Thu, Jun  6, 2013 at 09:19:59 +0100, Robert de Bath wrote:

> 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
> >>!
> 
Not going to happen.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: