RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Screen becomes black after choosing kernel for boot. (grub works)

Version-Release number of selected component (if applicable):
2.6.32-220.7.1

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:
Black screen on boot

Expected results:
should show boot progress

Additional info:

Works with kernel parameters i915.modeset=1 acpi_backlight=vendor
Fedora 17 alpha works out of the box.

Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Created attachment 585742 [details]
dmesg with drm.debug=4 enabled

kernel booted with drm.debug=4

Are you still seeing this in 6.3 (or a 6.4 snapshot)?  The sandybridge drm support has seen significant changes since 6.2.

The HP Folio 13 was replaced with a HP Elitebook (Sandy bridge based on EL6.3) so I can't test this now.

This bug can be closed