[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#702188: marked as done (src:linux: [3.6 -> 3.7 regression] : Brightness control became ineffective)

Your message dated Sat, 16 Oct 2021 01:54:13 -0700 (PDT)
with message-id <616a9335.1c69fb81.530e4.3264@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #702188,
regarding src:linux: [3.6 -> 3.7 regression] : Brightness control became ineffective
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
702188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702188
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:linux
Version: 3.8-1~experimental.1
Severity: important

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

In kernel prior to 3.7 I used to control the brightness through
gnome-control-center (or writing a value in /sys/class/acpi_video0), but since
3.7 this is broken (ditto for the brightness function keys which are supported
since this version), unless I boot with the '!Windows 2012' kernel
parameter. I guess commit a57f7f9175b8 is the culprit, however I didn't
try to boot with it reverted yet.

Apart booting with the above kernel parameter, I guess it would be
possible to blacklist the "video" module in order to make the backlight
control fallback to intel_backlight.

Anyway, I don't know if this issue is exclusively the kernel fault or if
the firmware is at fault too. Also I didn't check if there was a
possibility to add a quirk for this system to avoid it to boot with
the Windows 2012 _OSI deleted.

Thanks and have a nice day,
Vincent

- -- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlEzka0ACgkQbO4uEp7kOBM8bACg1LF9IWl6t5hbsiHnp1bWCZn7
xr0An3uDV5RJtBP+2/gjHqM58UBfMOYe
=eAH1
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: