Bug 85469

Summary: Brightness too high on internal AMD/ATI graphics device, but fine with external AMD/ATI graphics card
Product: DRI Reporter: Paul Menzel <paulepanter>
Component: DRM/RadeonAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium CC: paulepanter
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
output of `radeonreg regs dce4` built from radeontool-1.6.3-10-g6b5e7c6
none
Linux kernel 3.16.5 messages with `drm.debug=0x06`
none
Video BIOS from firmware P1.80 none

Description Paul Menzel 2014-10-26 09:23:40 UTC
Created attachment 108433 [details]
output of `radeonreg regs dce4` built from radeontool-1.6.3-10-g6b5e7c6

As reported on the list dri-devel [1], the brightness of the internal graphics card is too high on the ASRock E350M1 [2].

Please find the output of `radeonreg regs dce4` attached and I’ll attach the Linux kernel 3.16.5 messages and the Video BIOS too.


[1] Brightness too high on internal AMD/ATI graphics device, but fine with external AMD/ATI graphics card
    http://lists.freedesktop.org/archives/dri-devel/2014-July/thread.html#63006
[2] http://www.asrock.com/mb/amd/e350m1/
Comment 1 Paul Menzel 2014-10-26 09:36:45 UTC
Created attachment 108435 [details]
Linux kernel 3.16.5 messages with `drm.debug=0x06`

Captured with `journalctl --dmesg -a > /tmp/20141026--asrock-e350m1--vendor-firmware-p180--Linux-kernel-3.16.5-messages.txt`.
Comment 2 Paul Menzel 2014-10-26 09:38:10 UTC
Created attachment 108438 [details]
Video BIOS from firmware P1.80
Comment 3 Martin Peres 2019-11-19 08:58:01 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/550.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.