Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
Not able to start X when booting with nomodeset rdblacklist=nouveau
Version-Release number of selected component (if applicable):
kernel-2.6.32-201.el6.x86_64
xorg-x11-drv-nouveau-0.0.16-13.20110719gitde9d1ba.el6.x86_64
xorg-x11-drv-vesa-2.3.0-2.el6.x86_64
xorg-x11-server-Xorg-1.10.4-3.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Boot up with nomodeset rdblacklist=nouveau
2.
3.
Actual results:
No X start, log attached
Expected results:
X should start using vesa driver.
Additional info:
Possible regression 6.1 worked fine.
01:00.0 VGA compatible controller [0300]: nVidia Corporation GT218 [NVS 3100M] [10de:0a6c] (rev a2)
Hmm, strange. X didn't even try to load vesa from the looks of it. I'm not 100% sure if it's even supposed to if there's and xorg.conf, I think perhaps not.
Does it autoload vesa if you get rid of it?
Also, any particular reason for disabling nouveau, should we have a bug for that too?
Ohh crap I forgot on ol xorg.conf.
So you are right removing xorg.conf will fix this.
So I think NOTABUG, or?
BTW speaking about balcklisting, it acts same in moth cases (blacklist/not blacklist).
Yep, if that fixes it it'd be find to close as NOTABUG.
Yeah, blacklisting isn't necessary with nomodeset. Nouveau will load, but it won't actually touch the device at all.