All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Nikolay Martynov <mar.kolya@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Intel G41 doesn't see any screens connected after suspend/resume
Date: Mon, 17 Mar 2014 16:53:13 +0200	[thread overview]
Message-ID: <87zjkozxk6.fsf@intel.com> (raw)
In-Reply-To: <CALGY4fuhS0aO_nC9WP9PxBPZhBe6vxpwmAwgNgp=1EB8byCj0w@mail.gmail.com>

On Mon, 17 Mar 2014, Nikolay Martynov <mar.kolya@gmail.com> wrote:
> Hi.
>
>>>   2) Should I file a bug? If so - where and what additional
>>> information might be useful in that bug.
>>
>> Please do, on DRM/Intel component at [1]. We'll tend to not forget stuff
>> so easy if they're filed as bugs. Please attach dmesg from early boot
>> with drm.debug=0xe module parameter enabled. Please see if running
>> drm-intel-nightly branch of [2] helps.
>
>   Thank you for you reply. I'll post debug output shortly.
>
>   I would really appreciate if you could point me on some sort of
> manual that describes how to properly run [2] on Ubuntu? Should I run
> the whole kernel or just some modules? Is there any way to build only
> requires modules?

The whole kernel. See https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
for a starting point; please use the drm-intel-nightly branch in our
tree instead of Linus' tree.

BR,
Jani.


>   Sorry, my knowledge is somewhat limited in this regards.
>
>   Thanks!
>
>>
>> [1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI
>> [2] http://cgit.freedesktop.org/drm-intel/
>>
>>>
>
>
> -- 
> Martynov Nikolay.
> Email: mar.kolya@gmail.com

-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2014-03-17 14:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-16  4:06 Intel G41 doesn't see any screens connected after suspend/resume Nikolay Martynov
2014-03-17  7:43 ` Jani Nikula
2014-03-17 14:10   ` Nikolay Martynov
2014-03-17 14:53     ` Jani Nikula [this message]
2014-03-18  4:12       ` Nikolay Martynov
2014-03-18  8:29         ` Jani Nikula
2014-03-20  0:15           ` Nikolay Martynov
2014-03-20  7:46             ` Chris Wilson
2014-03-20 13:38               ` Nikolay Martynov
2014-03-20 13:43                 ` Chris Wilson
2014-03-20 23:17                   ` Nikolay Martynov
2014-03-21 12:08                     ` Chris Wilson

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=87zjkozxk6.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=mar.kolya@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.