dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: post@hiereth.de
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Graphic card that needs boot parameter
Date: Tue, 19 May 2020 11:55:10 +0300	[thread overview]
Message-ID: <20200519085510.GU6112@intel.com> (raw)
In-Reply-To: <20200519052256.2E9C7636EA@berlin.abc-admin.de>

On Tue, May 19, 2020 at 07:22:56AM +0200, post@hiereth.de wrote:
> Hello,
> 
> in
> https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html
> You ask
> to inform about hardware that requires the setting
> i915.invert-brightness=1.
> 
> I needed this for an quite old notebook with the following
> specifications
> 
>   lspci -s 00:02 -nn
>   00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile
>   915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03)
>   00:02.1 Display controller [0380]: Intel Corporation Mobile
> 915GM/GMS/910GML
>   Express Graphics Controller [8086:2792] (rev 03)
> 
> Feel free to request additional information if need. Thanks for your
> work on the linux
> kernel and the respective documentation

Please file a new bug at
https://gitlab.freedesktop.org/drm/intel/issues/new

boot with drm.debug=0xe and attach the resulting dmesg to the bug.

Also include the ouput of these
lspci -vs 0:02.0
lspci -nvs 0:02.0

And I'd like to see a dump of the vbios. Can be done like so:
 echo 1 > /sys/devices/pci0000\:00/0000\:00\:02.0/rom 
 cat /sys/devices/pci0000\:00/0000\:00\:02.0/rom > vbios.dump
Pls attach that to the bug as well.

-- 
Ville Syrjälä
Intel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2020-05-19  8:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19  5:22 Graphic card that needs boot parameter post
2020-05-19  8:55 ` Ville Syrjälä [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=20200519085510.GU6112@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=post@hiereth.de \
    /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