dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Lu <aaron.lu@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
	der-b <der-b@der-b.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: I915 did not work whit modset=1
Date: Wed, 08 Jan 2014 20:47:34 +0800	[thread overview]
Message-ID: <52CD48E6.3080408@intel.com> (raw)
In-Reply-To: <8738kydemf.fsf@intel.com>

On 01/08/2014 05:09 PM, Jani Nikula wrote:
> On Mon, 30 Dec 2013, Jani Nikula <jani.nikula@linux.intel.com> wrote:
>> On Mon, 23 Dec 2013, der-b <der-b@der-b.com> wrote:
>>> Hello,
>>>
>>> i got a new Notebook with an Intel Core i7-3689Y whit a Intel HD 
>>> Graphics 4000. I got a blank screen while booting but I could use ssh. 
>>> This happened each time, when I enabled CONFIG_I915_KMS in the kernel 
>>> config (modeset=1). Setting the option "invert_brightness=1" solved the 
>>> problem.
>>
>> Hi Bernd -
>>
>> The i915.invert_brightness parameter has only ever been needed on some
>> gen4 Acer laptops; I suspect this is something else.
>>
>> Please drop that parameter, and try one of the v3.13-rc kernels or
>> video.use_bios_initial_backlight=0 module parameter.
> 
> For completeness, the reporter replied privately that
> video.use_bios_initial_backlight=0 works.

Is it possible for the reporter to test a v3.13-rc kernel? That param is
removed in v3.13 after I did some clean up so it would be great to know
if v3.13 kernel still works for him.

Thanks,
Aaron

> 
> Jani.
> 
> 
>>
>> If those don't help, please file a bug on Product=DRI,
>> Component=DRM/Intel as instructed in [1].
>>
>> BR,
>> Jani.
>>
>>
>> [1] https://01.org/linuxgraphics/documentation/how-report-bugs
>>
>>>
>>> I attached the "lspci -s 00:002 -nn -v" output.
>>> I use the gentoo kernel 3.10.17.
>>>
>>> I hope this helps you a little bit.
>>>
>>> Kind regards,
>>>
>>> Bernd Lehmann
>>>
>>>
>>> 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
>>> processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA 
>>> controller])
>>>      Subsystem: Lenovo Device [17aa:3977]
>>>      Flags: bus master, fast devsel, latency 0, IRQ 42
>>>      Memory at e0000000 (64-bit, non-prefetchable) [size=4M]
>>>      Memory at d0000000 (64-bit, prefetchable) [size=256M]
>>>      I/O ports at 2000 [size=64]
>>>      Expansion ROM at <unassigned> [disabled]
>>>      Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
>>>      Capabilities: [d0] Power Management version 2
>>>      Capabilities: [a4] PCI Advanced Features
>>>      Kernel driver in use: i915
>>>      Kernel modules: i915
>>>
>>> _______________________________________________
>>> dri-devel mailing list
>>> dri-devel@lists.freedesktop.org
>>> http://lists.freedesktop.org/mailman/listinfo/dri-devel
>>
>> -- 
>> Jani Nikula, Intel Open Source Technology Center
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/dri-devel
> 

      reply	other threads:[~2014-01-08 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23 17:31 I915 did not work whit modset=1 der-b
2013-12-30 12:14 ` Jani Nikula
2014-01-08  9:09   ` Jani Nikula
2014-01-08 12:47     ` Aaron Lu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52CD48E6.3080408@intel.com \
    --to=aaron.lu@intel.com \
    --cc=der-b@der-b.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox