Bug 843608
| Summary: | lid test should not use HAL | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Hardware Certification Program | Reporter: | Greg Nichols <gnichols> | ||||||
| Component: | Test Suite (tests) | Assignee: | Greg Nichols <gnichols> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 1.6.4 | CC: | czhang, qcai, rlandry | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||||
| Doc Text: |
Feature:
lid test reads data from /proc interface instead of reading HAL info for hardware detection in test planning and execution.
Reason:
HAL is deprecated in RHEL6.
Result (if any):
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-02-01 18:21:00 UTC | Type: | Bug | ||||||
| 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: | 851892 | ||||||||
| Attachments: |
|
||||||||
|
Description
Greg Nichols
2012-07-26 18:30:13 UTC
/proc/acpi/button/lid/*/state appears to be the best source. Also in /proc/bus/input/devices Created attachment 601561 [details]
procDeviceDetector patch for check /proc/bus/input for devices
Created attachment 601562 [details]
lid test patch to use proc
I'm not certain if it's helpful, but it looks like /sys/class/backlight/acpi_video0 could possibly be a way to system side check the backlight status instead or in addition to asking the user? Marking as verified based on comment 12, and team discussion. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0222.html |