Bug 186093
Summary: | Display toggle (Fn F5) not noticed on Acer Aspire 3002LCi, making it impossible to use an external monitor. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Suzanne Hillman <shillman> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | k.georgiou, pfrields, wtogami |
Target Milestone: | --- | Keywords: | Desktop |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-05-05 13:02:30 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 183415 |
Description
Suzanne Hillman
2006-03-21 16:30:28 UTC
I don't think I've encountered a laptop where the Fn keys generate a keycode yet. It's typically magic BIOS SMI stuff. There is an ACPI fix that *might* have something to do with it in the latest kernel on my people page. Give it a try? fn keys: Ah, ok. I was wondering if it was something talking more directly to the hardware, but could never quite tell. Would that fix also solve other Fn keys stuff on other laptops? (also, checking if it helps things; will comment either way) I note that that kernel _did_ fix the problem with being unable to switch between the displays. Thank you! I am reluctant to close when it's not a released kernel, though. Ok, sorta fixed it. It was working, but now I can't get it out of going to both screens mode. I could switch between them until it got to both screen mode... what actually happens when you hit those keys is out of the kernels hands. As I mentioned, it's magic BIOS stuff. The kernel is blissfully unaware that anything even happened when we take an SMI trap. Ok with closing this now that there's an errata kernel with that fix ? Closing since an errata kernel with the fix has been released. |