Brightness hotkeys have no effect on Clevo laptop

[YannUbuntu]

******** the bug is fixed with kernel 3.7.0.

On Ubuntu 11.10, and 12.04, and even on 12.04 with mainline kernel 3.4, and 3.6 , the brightness hotkeys (decrease=Fn+F8 , and increase=Fn+F9) have no effect on my Clevo laptop.

- however, brightness control via "System Settings" -> "Brightness and lock" menu (in 12.04) work out-of-the-box.
- when adding the "acpi_osi=" option, hotkeys work , but the "Brightness and lock" menu has no effect any more.
- more information on http://ubuntuforums.org/showthread.php?t=2046843

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-26-generic 3.2.0-26.41
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: yyy 1571 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xf7e00000 irq 43'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0269,15584140,00100100 HDA:80862805,15584140,00100000'
   Controls : 27
   Simple ctrls : 13
Date: Fri Aug 24 11:15:07 2012
HibernationDevice: RESUME=UUID=56eb9210-7151-425c-93dd-b92af2e792ba
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
MachineType: CLEVO CO. W240HU/W250HUQ
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-26-generic root=UUID=789016b1-f3f0-4b76-be92-afa2dbb36c5e ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-26-generic N/A
 linux-backports-modules-3.2.0-26-generic N/A
 linux-firmware 1.79
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/09/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: Tag 12345
dmi.board.name: W240HU/W250HUQ
dmi.board.vendor: CLEVO CO.
dmi.board.version: D02A
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnCLEVOCO.:pnW240HU/W250HUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240HU/W250HUQ:rvrD02A:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: W240HU/W250HUQ
dmi.product.version: Not Applicable
dmi.sys.vendor: CLEVO CO.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.6 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc3-quantal/

[YannUbuntu (yannubuntu)]

Same result with 3.6 kernel in Precise (tested with and without linux-image-extra).
Mainline kernel does not fix this bug

[Helder (heldrida)]

I've got the exact same issue, trough system settings I can increase or decrease brightness but not by using FN + F8 or F9.

My computer is Clevo W370ET with nvidia gtx 660m

Thanks for looking!

[Helder (heldrida)]

This worked for me:
http://ubuntuforums.org/showthread.php?t=2046843&page=3

[YannUbuntu (yannubuntu)]

@Helder: please could you tell exactly what worked and how?
(there are several combinations on the page you linked)

[penalvch (penalvch)]

YannUbuntu, thank you for reporting this and helping make Ubuntu better. Could you please provide the information following https://wiki.ubuntu.com/Hotkeys/Troubleshooting ?

As well, could you please test the latest upstream kernel available (v3.6.2-quantal) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Please let us know your results. Thank you for your understanding.

[YannUbuntu (yannubuntu)]

Following https://wiki.ubuntu.com/Hotkeys/Troubleshooting :

Fn+F8 and Fn+F9 don't have any effect in xev
Fn+F8 and Fn+F9 don't have any effect in acpi_listen

Following /usr/share/doc/udev/README.keymap.txt :
/lib/udev/findkeyboards outputs input/event4
Running sudo /lib/udev/keymap -i input/event4 , then pressing Fn+F8 or Fn+F9 does not show any key name. (but other keys work, eg Fn+F5 gives the sound keyname)

[YannUbuntu (yannubuntu)]

$ sudo lsinput > lsinput.log
sudo: lsinput: command not found

Which package should i install ?

[YannUbuntu (yannubuntu)]

lshal -m does not show anything.

Switching to a virtual terminal and back (e.g. ctrl+alt+F1 ; ctrl+alt+f7) does not change anything.

[YannUbuntu (yannubuntu)]

(all results from post#9 were carried out in my 12.04.1 installed session)

Same problem in a 12.04.1 Guest Account.

Same problem in a Quantal-daily (kernel 3.5.0.17.19) live-session (liveUSB).

I will now test the latest upstream kernel.

[YannUbuntu (yannubuntu)]

Bug still exists with v3.6.2-quantal

[penalvch (penalvch)]

YannUbuntu, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1041116/comments/11 :
>"$ sudo lsinput > lsinput.log
sudo: lsinput: command not found
Which package should i install ?"

input-utils

[YannUbuntu (yannubuntu)]

Thanks Christopher.

Attached the lsinput.log from a v3.6.2-quantal session, after cold boot.

The previous logs were taken from my Ubuntu12.04.1 session (3.2.0.32).

Do you want the logs from a v3.6.2-quantal session? after suspend+resume?

[penalvch (penalvch)]

YannUbuntu, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1041116/comments/18 :
>"Attached the lsinput.log from a v3.6.2-quantal session, after cold boot.
The previous logs were taken from my Ubuntu12.04.1 session (3.2.0.32).
Do you want the logs from a v3.6.2-quantal session?"

If the output of lsinput is different in Ubuntu12.04.1 session (3.2.0.32), then please attach it. If not, please do not.

>"...after suspend+resume?"

We would not want to introduce suspend issues into this report, as suspend is treated as a separate bug report. If you are having a problem with this, please file a new report by executing the following via a terminal:
ubuntu-bug linux

As well, did this problem not occur in a release prior to Oneiric?

[YannUbuntu (yannubuntu)]

Here is the lsinput in Ubuntu12.04.1 session (3.2.0.32).
It is different.

[YannUbuntu (yannubuntu)]

Brightness hotkeys have no effect also on 10.04.3 liveCD and 11.04 liveCD.

[penalvch (penalvch)]

Marking Triaged as kernel-bug-exists-upstream-v3.6.2-quantal, regression tested back to Lucid, and requested information from https://wiki.ubuntu.com/Hotkeys/Troubleshooting provided.

[YannUbuntu (yannubuntu)]

in 10.04.3 too, the "acpi_osi=" option makes the brightness hotkeys work.

What does the acpi_osi= option do?
is there a way to enable it without its drawback (it disables the "Brightness and lock" feature in 12.04) ?

[penalvch (penalvch)]

YannUbuntu, regarding your comments :
>"in 10.04.3 too, the "acpi_osi=" option makes the brightness hotkeys work."

Thank you for testing Lucid. As a follow up, if you did not use the acpi_osi= kernel parameter in Lucid, the brightness hotkeys would not work?

>"What does the acpi_osi= option do?"

Please see http://www.kernel.org/doc/Documentation/kernel-parameters.txt .

>"is there a way to enable it without its drawback (it disables the "Brightness and lock" feature in 12.04) ?"

Unfortunately, I do not have any further information on this.

Despite this, the next step would be to add information desired by kernel.org triagers and developers to your upstream bug. Could you please do this following https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Overview_on_Reporting_Bugs_Upstream ?

[YannUbuntu (yannubuntu)]

Thanks Christopher

If I don't use the acpi_osi= kernel parameter in Lucid, the brightness hotkeys do not work. (see comment #21)
Remark: all my comments and attached files until comment #21 are without acpi_osi= (except the "when adding the acpi_osi= [snip] any more." sentence in the bug description)

According to http://www.kernel.org/doc/Documentation/kernel-parameters.txt says acpi_osi= disables all strings in the "list of supported OS interface strings". Would it help if i indicate the content of this list? (if yes, where can i find this list?)

I'll try to follow https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Overview_on_Reporting_Bugs_Upstream .

[YannUbuntu (yannubuntu)]

According to https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Reporting_non-USB_Bugs_Upstream , i should send an email to a Maintainer list, but i can't find any maintainer for brightness hotkeys in http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=MAINTAINERS . Any clue?

As i already filled a bug in the Kernel Bug Tracker ( https://bugzilla.kernel.org/show_bug.cgi?id=46401 ), do i really need to send this email?

[penalvch (penalvch)]

YannUbuntu, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1041116/comments/26 :
>"According to https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Reporting_non-USB_Bugs_Upstream , i should send an email to a Maintainer list, but i can't find any maintainer for brightness hotkeys in http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=MAINTAINERS . Any clue?"

the maintainer list you could send it to is <email address hidden> .

>"As i already filled a bug in the Kernel Bug Tracker ( https://bugzilla.kernel.org/show_bug.cgi?id=46401 ), do i really need to send this email?"

If you want to maximize your chances of this being looked at by a kernel.org triager or developer, you would want to both send an appropriately formatted E-Mail as per https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Reporting_non-USB_Bugs_Upstream , and make a comment in your bug kernel.org report containing the formatting noted in https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Reporting_non-USB_Bugs_Upstream .

[YannUbuntu (yannubuntu)]

[1.] One line summary of the problem:
Brightness hotkeys have no effect on Clevo laptop

[2.] Full description of the problem/report:
Brightness hotkeys (decrease=Fn+F8 , and increase=Fn+F9) have no effect on my
Clevo (W240HU/W250HUQ) laptop.
However, brightness control via "System Settings" -> "Brightness and lock"
menu (in Ubuntu 12.04) work out-of-the-box.
When adding the "acpi_osi=" option, hotkeys work , but the "Brightness and
lock" menu has no effect any more.
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1041116 and
https://bugzilla.kernel.org/show_bug.cgi?id=46401 for further information.

[3.] Keywords:
brightness, hotkeys, kernel-bug-exists-upstream-v3.6.2

[4.] Kernel version (from /proc/version):
Linux version 3.6.2-030602-generic (apw@gomeisa) (gcc version 4.6.3
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201210121823 SMP Fri Oct 12 22:24:18 UTC 2012

[5.] Output of Oops.. message (if applicable)
I am not sure if it is applicable or not.

[6.] A small shell script or example program which triggers the problem (if
possible)
Sorry, i don't know what to provide here.

[7.] Environment
Description: Ubuntu 12.04.1 LTS
Release: 12.04

[7.1.] Software (add the output of the ver_linux script here)
Linux yyy-W240HU-W250HUQ 3.6.2-030602-generic #201210121823 SMP Fri Oct 12
22:24:18 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Gnu C 4.6
Gnu make 3.81
binutils 2.22
util-linux 2.20.1
mount support
module-init-tools 3.16
e2fsprogs 1.42
pcmciautils 018
PPP 2.4.5
Linux C Library 2.15
Dynamic linker (ldd) 2.15
Procps 3.2.8
Net-tools 1.60
Kbd 1.15.2
Sh-utils 8.13
wireless-tools 30
Modules Loaded bnep rfcomm parport_pc bluetooth ppdev binfmt_misc
dm_crypt joydev snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel
snd_hda_codec snd_hwdep arc4 snd_pcm rtl8192ce rtl8192c_common rtlwifi
snd_seq_midi snd_rawmidi snd_seq_midi_event mac80211 snd_seq coretemp snd_timer
kvm_intel snd_seq_device kvm psmouse cfg80211 mei snd soundcore snd_page_alloc
lpc_ich jmb38x_ms memstick serio_raw mac_hid lp microcode parport
ghash_clmulni_intel cryptd i915 drm_kms_helper drm i2c_algo_bit jme sdhci_pci
sdhci wmi video

[7.2.] Processor information (from /proc/cpuinfo):
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i3-2350M CPU @ 2.30GHz
stepping : 7
microcode : 0x1b
cpu MHz : 800.000
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm
pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx lahf_lm arat epb
xsaveop...

[YannUbuntu (yannubuntu)]

[1.] One line summary of the problem:
Brightness hotkeys have no effect on Clevo laptop

[2.] Full description of the problem/report:
Brightness hotkeys (decrease=Fn+F8 , and increase=Fn+F9) have no effect on my
Clevo (W240HU/W250HUQ) laptop.
However, brightness control via "System Settings" -> "Brightness and lock"
menu (in Ubuntu 12.04) work out-of-the-box.
When adding the "acpi_osi=" option, hotkeys work , but the "Brightness and
lock" menu has no effect any more.
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1041116 and
https://bugzilla.kernel.org/show_bug.cgi?id=46401 for further information.

[3.] Keywords:
brightness, hotkeys, kernel-bug-exists-upstream-v3.6.2

[4.] Kernel version (from /proc/version):
Linux version 3.6.2-030602-generic (apw@gomeisa) (gcc version 4.6.3
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201210121823 SMP Fri Oct 12 22:24:18 UTC 2012

[5.] Output of Oops.. message (if applicable)
I am not sure if it is applicable or not.

[6.] A small shell script or example program which triggers the problem (if
possible)
Sorry, i don't know what to provide here.

[7.] Environment
Description: Ubuntu 12.04.1 LTS
Release: 12.04

[7.1.] Software (add the output of the ver_linux script here)
Linux yyy-W240HU-W250HUQ 3.6.2-030602-generic #201210121823 SMP Fri Oct 12
22:24:18 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Gnu C 4.6
Gnu make 3.81
binutils 2.22
util-linux 2.20.1
mount support
module-init-tools 3.16
e2fsprogs 1.42
pcmciautils 018
PPP 2.4.5
Linux C Library 2.15
Dynamic linker (ldd) 2.15
Procps 3.2.8
Net-tools 1.60
Kbd 1.15.2
Sh-utils 8.13
wireless-tools 30
Modules Loaded bnep rfcomm parport_pc bluetooth ppdev binfmt_misc
dm_crypt joydev snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel
snd_hda_codec snd_hwdep arc4 snd_pcm rtl8192ce rtl8192c_common rtlwifi
snd_seq_midi snd_rawmidi snd_seq_midi_event mac80211 snd_seq coretemp snd_timer
kvm_intel snd_seq_device kvm psmouse cfg80211 mei snd soundcore snd_page_alloc
lpc_ich jmb38x_ms memstick serio_raw mac_hid lp microcode parport
ghash_clmulni_intel cryptd i915 drm_kms_helper drm i2c_algo_bit jme sdhci_pci
sdhci wmi video

[7.2.] Processor information (from /proc/cpuinfo):
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i3-2350M CPU @ 2.30GHz
stepping : 7
microcode : 0x1b
cpu MHz : 800.000
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm
pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx lahf_lm arat epb
...

[penalvch (penalvch)]

YannUbuntu, just a quick follow up, what is your full laptop model name (ex. Clevo w240HU)?

[YannUbuntu (yannubuntu)]

CLEVO CO. W240HU/W250HUQ (see the bug description)

Full description in French: http://www.ldlc.com/fiche/PB00111856.html

[penalvch (penalvch)]

YannUbuntu, thank you for your comments. Regarding them https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1041116/comments/31 :
>"CLEVO CO. W240HU/W250HUQ (see the bug description)"

I did notice this in the Bug Description. However, I asked about the specific model number that may be on a sticker on the computer itself, not queried and posted into the Bug Description by Launchpad. The reason why is I was unable to find your specific model on Clevo's website http://www.clevo.com.tw/en/products/index.asp . Do you have a sticker on your computer that gives a more accurate model number?

>"Full description in French: http://www.ldlc.com/fiche/PB00111856.html ."

Unfortunately, I do not read French so this would not be as helpful as providing the information above.

Thank you for your understanding.

[YannUbuntu (yannubuntu)]

On the sticker under the laptop, it is written:

NOTEBOOK COMPUTER
MODEL: W253HU
PRODUCT CODE: W253HUQ

I bought it on the LDLC.fr website, where they called it "LDLC Aurore BB1-i3-4-H5", but it is indeed a Clevo hardware.

I bought it in October 2011, so i guess this hardware is not sold any more on the Clevo website.

Detailed specs are at the bottom of this page: http://www.ldlc.com/fiche/PB00111856.html
Most important data are in English:
i3-2350M (Dual-Core 2.3 GHz - Cache 3 Mo - DMI 5 GT/s),
Mobile Intel HM65 Express chipset,
15.6inch Intel HD Graphics
RAM 4Go PC3-10600 - DDR3 1333 MHz

[penalvch (penalvch)]

YannUbuntu, thank you for providing the requested information. Another reason why I wanted to know the specific model is to check into a BIOS upgrade. However, Clevo does not maintain you model number on their website. Doing a cursory investigation, one may be expected to contact the retailer to find out what the newest BIOS version is, and the direct link to it. Could you please do this to find out if you have the newest BIOS version?

Thank you for your understanding.

[YannUbuntu (yannubuntu)]

Christopher,
I contacted the retailer (LDLC). They say that some BIOS update exists for this model, but they give the file only to advanced users when the update fixes a specific problem. They say this hotkeys problem is not due to the BIOS but to missing drivers in Ubuntu.

[Daniel Ricao Canelhas (daniel-canelhas)]

Having the same issue on a Clevo P150EM notebook with a fresh install of
Ubuntu 12.04.1 x86_64

The following terminal command works:

echo X | sudo tee /sys/class/backlight/acpi_video0/brightness

where X is an integer between 0 and 7.

[Daniel Ricao Canelhas (daniel-canelhas)]

Testing the troubleshooting guide at https://wiki.ubuntu.com/Hotkeys/Troubleshooting i note that xev does not record a keypress for the hotkeys <Fn+F8> <Fn+F9>.

No xev keypress events are produced for some other keys too (switching off the touchpad, bluetooth, wlan, switching monitors) but their expected functions work nonetheless.

/lib/udev/findkeyboards
returns "AT keyboard: input/event4"

sudo /lib/udev/keymap -i input/event4

causes a continuous stream of <return> to be sent to any selected window. The function keys relative to this bug report produce no output here either. Notably, disabling the wlan at this point (using its function key) causes it to remain disabled in spite of trying to toggle it back on.

[waxline (waxline)]

Having the same issue on a new Clevo W370ET notebook with a fresh install of Ubuntu 12.04 x86_64.

[penalvch (penalvch)]

Daniel Ricao Canelhas / waxline, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[YannUbuntu (yannubuntu)]

Dear all,

the bug is fixed with kernel 3.7.0.

Thanks to everybody who contributed!

[penalvch (penalvch)]

YannUbuntu, could you please test for this in Raring via http://cdimage.ubuntu.com/daily-live/current/ ?

[YannUbuntu (yannubuntu)]

Bug is fixed in Raring.

[penalvch (penalvch)]

YannUbuntu, did you need a backport to a release prior to Raring, or may we mark this Status Invalid?

[YannUbuntu (yannubuntu)]

I personally don't need the backport, and I don't think it is worth it spending time on it because there is a workaround (using the "System Settings" -> "Brightness and lock" menu).
Thanks for proposing anyway.

[penalvch (penalvch)]

YannUbuntu, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1041116/comments/42 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[Dow Hurst (dow-hurst)]

Just updated to Linux x8e 4.4.0-112-generic #135-Ubuntu and the same problem previously described has reappeared. Before the update to this kernel, I was running 4.4.0-109-generic. Since I installed ubuntu 16.04 LTS MATE the F8 and F9 keys adjusted the brightness. Now they do nothing. The laptop is a rebranded Clevo by Eurocom and is an Extreme X8E.

[penalvch (penalvch)]

Dow Hurst, this closed report is not scoped to your problem. Hence, it will help immensely if you use the computer the problem is reproducible with, and provide necessary debugging logs by filing a new report with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.