Bug 810198
| Summary: | Black screen on boot on HP Folio 13 laptop | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alexander Lindqvist <alexander> | ||||||||
| Component: | xorg-x11-drv-intel | Assignee: | Adam Jackson <ajax> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 17 | CC: | ajax, gansalmon, garvisdol, itamar, jfeeney, jim, jonathan, jyundt, kernel-maint, madhu.chinakonda, xgl-maint | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | first=3.3 modeset | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-07-31 17:42:41 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Alexander Lindqvist
2012-04-05 10:20:38 UTC
modeset is enabled by default, so the i915.modeset=1 shouldn't be needed. If you only specify acpi_backlight=vendor, does it work? Can you provide the output of acpidump from this machine? Created attachment 575495 [details]
ACPI Dump
ACPI dump from HP Folio 13 laptop
(In reply to comment #1) > modeset is enabled by default, so the i915.modeset=1 shouldn't be needed. If > you only specify acpi_backlight=vendor, does it work? > > Can you provide the output of acpidump from this machine? You were right. acpi_backlight=vendor is enough. Can you boot the machine with 'drm.debug=4' on the kernel command line, and ssh in and attach dmesg from that? Created attachment 585741 [details]
dmesg with drm.debug=4 enabled
This is the HP Folio 13 (model: 2000) booting the EL6.2 kernel with kernel option drm.debug=4 as it is now installed on this laptop and experiencing the exact same problem.
I could probably boot the Fedora live cd and get this info from there if you need it.
Please do, as the code is very different. Created attachment 594952 [details]
dmesg from Fedora17live with drm.debug=4 enabled
Are you still having issue with this on 3.8.2 in updates-testing? This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |