| Summary: | Intel - display brightness control not working with i915.fastboot=1 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Arthur Borsboom <arthurborsboom> | ||||||||||
| Component: | DRM/Intel | Assignee: | Maarten Lankhorst <bugs> | ||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||
| Severity: | major | ||||||||||||
| Priority: | low | CC: | bugs, intel-gfx-bugs | ||||||||||
| Version: | XOrg git | ||||||||||||
| Hardware: | Other | ||||||||||||
| OS: | All | ||||||||||||
| See Also: | https://bugs.freedesktop.org/show_bug.cgi?id=104838 | ||||||||||||
| Whiteboard: | ReadyForDev | ||||||||||||
| i915 platform: | HSW | i915 features: | display/backlight | ||||||||||
| Attachments: |
|
||||||||||||
Created attachment 135605 [details] [review] Call intel_opregion_notify_encoder Just a hunch, does this work? Hi Maarten, I am an application developer and not an OS/driver developer, so I cannot judge the hunch by looking at your patch. However, I can test, but I do need some instructions/guidance. :) For example, against which (git) source do I have to apply your patch? After that, give me some time to get the hang of the kernel compilation and patching process. How do you suggest I apply your patch? You can build drm-tip by cloning git://anongit.freedesktop.org/drm-tip To build you can use the patches from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/HEADER.html After applying the patches you can also apply the patch I linked in this bug, and then build the kernel like you would for any other debian/ubuntu package. If that doesn't work I can make some own packages, but that will take a while to upload. Hi Maarten, I have cloned drm-tip, applied your patch, compiled and installed this kernel 4.15.0-rc1 to my daily system. If I boot this kernel without the fastboot kernel option, the brightness keys still work. If I add 'i915.fastboot=1', then the brightness keys do not work as before anymore. I also noticed that when using the fastboot method, the brightness of the screen is at maximum. Can you get a boot log with drm.debug=0x1f with the patched kernel? Created attachment 135832 [details]
boot log with drm.debug
Requested boot log.
Booted with the patched kernel including the fastboot and the drm debug setting. Around 16 seconds the system has been booted. Around 20 seconds I have pressed 4 or 5 times to decrease the backlight until the screen turned black. After that I have pressed 1 time to increase the backlist, which turned it on to maximum brightness again. See attachment. Same here on same laptop with 4.15.5 kernel. It works after resume from suspend to ram. First of all. Sorry about spam. This is mass update for our bugs. Sorry if you feel this annoying but with this trying to understand if bug still valid or not. If bug investigation still in progress, please ignore this and I apologize! If you think this is not anymore valid, please comment to the bug that can be closed. If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug. Reporter, do you still have the issue? Please try to reproduce the issue using drm-tip (https://cgit.freedesktop.org/drm-tip) and kernel parameters drm.debug=0x1e log_buf_len=4M, and if the problem persists attach the full dmesg from boot. Created attachment 141507 [details]
dmesg with fastboot and drm debugging enabled
I have just tested the issue on the stable kernel on my laptop, since I do not have the knowledge yet to use 'drm-tip'. The issue seems to remain with kernel 4.18.5 with a small difference that the screen does not turn black anymore, after pressing the Fn-Brightness down key many times. I have added the dmesg output with DRM debugging enabled. Is this sufficient information or is more needed? If the drm-tip usage is a necessity, please provide detailed step-by-step instructions how to do that. > The issue seems to remain with kernel 4.18.5 with a small difference that
> the screen does not turn black anymore, after pressing the Fn-Brightness
> down key many times.
>
Does it mean, pressing reduce brightness button multiple times doesn't go black (which is the original problem) but stays full brightness.
Now the issue is that you are not able to reduce the brightness. Correct me, if I am wrong.
The original problem is not the fact that the screen goes completely black. The original problem is that the brightness cannot be changed, except after pressing the Fn-Brightness-down for 10 or 20 times and then the screen turns black. I will summarize the differences by the behavior below. ----------------------------------------------------------- Fastboot disabled (default) / everything works as expected ----------------------------------------------------------- Brightness keys function as expected. Brightness up + down keys change the intensity of the backlight with certain steps. Pressing the down button many times, will lower the backlight and finally turns of the screen and results in a black screen. ------------------------------------------------------------- Fastboot enabled with kernel 4.13.11 - 4.15.5 (original problem) ------------------------------------------------------------- Pressing the brightness keys does not change the intensity of the backlight. Pressing the brightness down key many times, results in a black screen. ------------------------------------------------------------- Fastboot enabled with kernel 4.18.5 - 4.15.5 ------------------------------------------------------------- Pressing the brightness keys does not change the intensity of the backlight. Pressing the brightness down key many times, does not result in a black screen anymore. I am not sure if that is good or bad, but something did change in comparison to previous kernels. In other words, with fastboot enabled, I cannot change the brightness of the screen anymore with the brightness keys, as was the case without fastboot enabled. Does this help sufficiently to understand the issue? Pretty sure this has been debugged in bug 108225. Resolving dupe. If the steps in that bug don't lead to similar results, please reopen. *** This bug has been marked as a duplicate of bug 108225 *** Closed as duplicate. |
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.
Created attachment 135522 [details] dmesg when booted with the fastboot flag Hardware: Asus N751JK laptop, i7-4710HQ OS: Arch Linux Kernel: 4.13.11 Kernel module: i915 While reading through a news article on Phoronix.com, I decided to test an upcoming kernel/driver feature: Intel display 'fastboot'. This can be activated by the kernel option i915.fastboot=1 This indeed speeds up the boot process and reduces the flickering, but with a side effect. Normally I use the Fn-buttons to change the brightness of the (laptop) screen. This works fine without the fastboot kernel parameter. This does not work anymore with the kernel parameter. It seems to be stuck at maximum brightness. When I press the reduce brightness button multiple times, the screen turns black. When I press then only 1 time the increase brightness button, the screen is back on at maximum brightness. dmesg when booted with the fastboot parameter is attached. Is this misconfiguration, a bug or something else? Do I need to provide more information and if so what? Best regards, Arthur Borsboom.