Bug 592155 - vesa driver cannot work with KMS driver loaded
vesa driver cannot work with KMS driver loaded
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-drv-vesa (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Ben Skeggs
Boris Ranto
: Patch, Triaged
: 592177 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2010-05-13 22:00 EDT by Ben Skeggs
Modified: 2010-11-11 11:31 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-11 11:31:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Proposed fix (646 bytes, text/plain)
2010-05-13 22:00 EDT, Ben Skeggs
no flags Details

  None (edit)
Description Ben Skeggs 2010-05-13 22:00:51 EDT
Created attachment 413932 [details]
Proposed fix

Description of problem:

xorg-x11-drv-vesa will cause very bad interactions with KMS drivers, if they're loaded.  Vesa should detect this and refuse to load.
Comment 3 RHEL Product and Program Management 2010-05-13 23:49:51 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
Comment 4 Bill Nottingham 2010-05-14 10:37:30 EDT
*** Bug 592177 has been marked as a duplicate of this bug. ***
Comment 5 Ben Skeggs 2010-05-17 19:23:00 EDT
MODIFIED xorg-x11-drv-vesa-2.2.1-2.el6 is in brew.
Comment 8 releng-rhel@redhat.com 2010-11-11 11:31:05 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.