Consulting http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html : 3.11.0-0.2 3.11.0-rc4 3.11.0-0.1 3.11.0-rc3 3.10.0-6.17 3.10.3
Hence, before commit bisecting, one would want to switch to the mainline, and further kernel version bisect. Hence, from your last information provided, we have as per http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D : v3.11-rc3-saucy/ v3.11-rc2-saucy/ v3.11-rc1-saucy/ v3.10.19-saucy/ v3.10.18-saucy/ v3.10.17-saucy/ v3.10.16-saucy/ v3.10.15-saucy/ v3.10.14-saucy/ v3.10.13-saucy/ v3.10.12-saucy/ v3.10.11-saucy/ v3.10.10-saucy/ v3.10.9-saucy/ v3.10.8-saucy/ v3.10.7-saucy/ v3.10.6-saucy/ v3.10.5-saucy/ v3.10.4-saucy/ v3.10.3-saucy/ Hence, is this problem reproducible in v3.10.13-saucy/ ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229591 Title: display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
