Bug 236195 - vga= values result in black screen
vga= values result in black screen
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel (Show other bugs)
5.0
All Linux
medium Severity low
: ---
: ---
Assigned To: Don Zickus
Martin Jenner
:
: 216528 234448 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-12 09:48 EDT by Jim Perrin
Modified: 2012-11-08 10:07 EST (History)
11 users (show)

See Also:
Fixed In Version: RHBA-2007-0959
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-11-07 14:46:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Jim Perrin 2007-04-12 09:48:16 EDT
Description of problem:
vga= values which worked with rhel4 no longer work with rhel5

Version-Release number of selected component (if applicable):
2.6.18-x

How reproducible:
always

Steps to Reproduce:
1. append vga=0x31A (or other fb values for decent console resolution)
2. reboot
3. removing rhgb and quiet does not help
  
Actual results:
black screen

Expected results:
better console resolution than 80x25. for example 1024x768. 

Additional info:
Comment 1 Fabian Arrotin 2007-04-18 15:02:57 EDT
Is it possible to have vesafb support back in the kernel ? 
Really annoying to have a 17inch flat screen in a computer room than can only
handle 80x25 when you need to fix something at the console ...
Comment 2 Jim Perrin 2007-04-20 10:21:57 EDT
Seems that vesa support is no longer built into the kernel for some reason. See
below:

[root@gordnbdotllc006 boot]# grep -i vesa config-2.6.18-8.1.1.el5
# CONFIG_FB_VESA is not set

Hopefully someone at rh can shed some light on why this was removed. I consider
it to be highly useful. 
Comment 3 Peter Martuccelli 2007-04-20 13:06:18 EDT
Don will look into setting CONFIG_FB_VESA support on in RHEL 5.1.
Comment 4 RHEL Product and Program Management 2007-04-20 13:44:52 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.
Comment 5 Jim Perrin 2007-04-21 10:58:51 EDT
Thanks for the follow-up on this bug. Is this something that would be considered
for fastrack inclusion, if a rebuild for something else is required later on, or
will this strictly a 5.1 thing?
Comment 6 Peter Martuccelli 2007-04-26 12:10:26 EDT
*** Bug 216528 has been marked as a duplicate of this bug. ***
Comment 8 Gilboa Davara 2007-05-05 09:40:24 EDT
Yet another vote for CONFIG_VESA.

Never the less, if VESA is disabled, why doesn't the kernel just ignore the
vga=xxx command instead of displaying garbled image?

Either way (pending fix), I'd suggest you add a note about it in the release
notes/known issues.

- Gilboa
Comment 9 Don Zickus 2007-05-09 14:25:44 EDT
committed in 2.6.18-18.el5
Comment 10 Jim Perrin 2007-05-09 14:39:10 EDT
Is this available for testing anywhere? 
Comment 11 Don Zickus 2007-05-09 15:31:29 EDT
yes, people.redhat.com/dzickus/el5/18.el5
Comment 12 Patrick C. F. Ernzer 2007-05-13 18:59:13 EDT
*** Bug 234448 has been marked as a duplicate of this bug. ***
Comment 13 Ian Laurie 2007-05-13 20:32:03 EDT
VESA framebuffer support in kernel-2.6.18-18.el5.i686.rpm is working well for me
so far.
Comment 14 Jim Perrin 2007-05-14 20:27:36 EDT
Seems to be working just fine here as well. 
Comment 16 Ian Laurie 2007-05-18 23:03:03 EDT
Don, I notice your have posted a later kernel, kernel-2.6.18-19.el5, and it also
has VESA support, does this later one fix some of the current errata issues
described in Security Advisory RHSA-2007:0347-2 ?  I am currently still running
2.6.18-18.
Comment 17 Don Zickus 2007-05-29 10:43:26 EDT
I am not sure. You will need to know what bugzilla number the advisory is
refering to and then you can check the kernel changelog to see if -19.el5 has
the appropriate fix.

Or a faster way is to see if the bugzilla number is in a MODIFIED state.  If so
then I should have a comment embeded stating which build that patch went into.

Comment 21 errata-xmlrpc 2007-11-07 14:46:37 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2007-0959.html

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