Public bug reported:
I was testing Fedora 19 when I realized my brightness controls did not
work predictably. If I hit brightness down, it did nothing. If I hit
brightness up, my brightness went to about 1% and stayed there
indefinitely. Thinking this was similar to what I had to do in Ubuntu
GNOME 13.04 (add the Windows 2012 Grub parameter), I did so, and it
fixed it. On Fedora 19, it did not fix it.
So why might you be asking am I talking about Fedora in an Ubuntu bug
report?
I just fired up Ubuntu GNOME 13.10 and tried the same thing, and it acts
100% identical.
jason@JS-E430:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.9.0-7-generic
root=UUID=984ddcf5-7b38-410b-9398-6edb27732c20 ro quiet splash
"acpi_osi=!Windows\x202012"
Now I'm wondering if this is a kernel issue. Both distros are on 3.9.X.
The only work around I have now is to add the brightness extension for
Gnome and use that to control my brightness.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.9.0-7-generic 3.9.0-7.15 [modified:
boot/vmlinuz-3.9.0-7-generic]
ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
Uname: Linux 3.9.0-7-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.10.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: jason 1683 F.... pulseaudio
Date: Wed Jun 26 22:39:40 2013
HibernationDevice: RESUME=UUID=504647a2-9377-4a75-9669-218848b4ee6b
InstallationDate: Installed on 2013-06-26 (0 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64
(20130625)
MachineType: LENOVO 3254CTO
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-7-generic
root=UUID=984ddcf5-7b38-410b-9398-6edb27732c20 ro quiet splash
"acpi_osi=!Windows\x202012"
RelatedPackageVersions:
linux-restricted-modules-3.9.0-7-generic N/A
linux-backports-modules-3.9.0-7-generic N/A
linux-firmware 1.109
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/27/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: H0ET91WW (2.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 3254CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrH0ET91WW(2.51):bd02/27/2013:svnLENOVO:pn3254CTO:pvrThinkPadEdgeE430:rvnLENOVO:rn3254CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3254CTO
dmi.product.version: ThinkPad Edge E430
dmi.sys.vendor: LENOVO
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195083
Title:
Windows 2012 Grub parameter passes as Windowsx202012
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1195083/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
