Surak, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/
I have the same problem on a Clevo W230ST based machine running Saucy
13 10. Exactly the same symtoms and print out of ls /sys/class/backlight
both using 3.11 and a 3.8 kernel on a LiveUSB. The keys will reduce the
backlight but not increase leaving one completely in the dark. I am
running
I updated to Saucy Salamander 13.10 and the problem persists even with
kernel 3.11.0-13-generic #20-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux.
Not using Xorg-Edgers PPA, anymore, since I notice nVidia-319 is
available, but still using Bumblebee.
--
You received this bug notification because you
Hello, Richard Hull, thanks for the info. As in comment #27, at least in
my laptop, all I needed to do is to add the acpi_backlight=vendor to
make Fn brightness keys work, but that made VGA connection and auto
screen switch stop working and I use that a lot. BTW, you can probably
keep your
Without adding acpi_backlight=vendor in the boot parameters:
ls /sys/class/backlight
acpi_video0 intel_backlight
Adding acpi_backlight=vendor in the boot parameters:
ls /sys/class/backlight/
intel_backlight
So Fn keys start working with acpi_backlight=vendor boot parameter
because the keys
/bin/echo 0 /sys/class/backlight/intel_backlight/brightness
made the screen completely dark, but the Fn keys did not work. I needed
to type a
echo 4000 /sys/class/backlight/intel_backlight/brightness
to be able to see the screen again.
--
You received this bug notification because you are a
I have a Clevo W350ST with Ubuntu Saucy, had installed the Bumblebee PPA
and experienced the same problem with the brightness keys not working.
However, by removing the bumblebee PPA, purging bumblebee, re-installing
it from the Saucy repos, and then adding kernel boot parameters
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=63201
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1218547
Title:
Thanks for testing those. Since using what was basically the latest
upstream kernel didn't help, it sounds like this is something that needs
to be addressed upstream. That doesn't mean that we'll stop trying to
find a temp solution, just that a fix may originate quicker from
upstream. If you
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1218547
Title:
Clevo W350ST brightness keys don't work on Kubuntu
The easiest way to file this in the kernel bug tracker is to click the
Also effects project button and choose The linux kernel bug filing
form. You will need a account, but that is simple enough to set up.
--
You received this bug notification because you are a member of Kernel
Packages, which
I was unable to test 3.8.13.11-raring because it won't boot with my
LUKS-Crypt Volume, because it does not ask for my passphrase, but tested
with 3.8.13.10-raring and the problem happens with it.
I also tested with 3.11.5-saucy and the problem persists, so I updated
the tags as oriented.
** Tags
** Tags added: needs-testing-upstream
** Tags removed: needs-testing-upstream
** Tags added: needs-upstream-testing
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1218547
Title:
Clevo
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Test the 3.9rc8
kernel, not one in the daily directory. Once you have done this, remove
the tag needs-upstream-testing. If this issue exists in the mainline
kernel add the tag
Ack, actually test using the 3.12rc5 kernel. Didn't notice that you had
already tested 3.11.
Sorry.
Quinn Balazs
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: linux (Ubuntu)
Ack, in actuality you will want to test the latest 3.9 kernel version,
not 3.9rc8.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1218547
Title:
Clevo W350ST brightness keys don't work
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1218547
Title:
Clevo W350ST brightness keys don't work on Kubuntu
Status
I accessed
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D
ordered by date and the most recent raring version is
v3.8.13.10-raring/ 25-Sep-2013 18:57
the most recent saucy version is
v3.11.5-saucy/ 14-Oct-2013 02:52
the most recent 3.9 version is
v3.9.11-saucy/ 21-Jul-2013
For our purposes, the rc builds should be ignored. Let's test this with
v3.8.13.11-raring and v3.11.5-saucy. This should give us a pretty good
picture of where (if anywhere) this issue exists upstream.
v3.8.13.11-raring is from today, and v3.11.5-saucy is from yesterday.
Sorry about the
Looking back at your last comment, this sounds like the core of the
issue is that there are two interfaces present that are trying to
control brightness. Could you try booting with the kernel boot parameter
of acpi_backlight=vendor which should disable acpi_video0 leaving
intel_backlight. Does
apport information
** Tags added: apport-collected raring
** Description changed:
The Fn+F8 and Fn+F9 keys are not working on my Clevo W350ST with Kubuntu
Raring to change screen brightness of the internal laptop screen. I
installed linux-headers-3.11.0-4, linux-headers-3.11.0-4-generic,
I booted with acpi_backlight=vendor and the Fn+F8 and Fn+F9 keys worked
as expected to control the internal laptop screen brightness. But there
was a side effect: now, plugin the external VGA does not change to
external screen automatically anymore. And after manually changing to
the external VGA
22 matches
Mail list logo
