Description of problem:
vga= values which worked with rhel4 no longer work with rhel5
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. append vga=0x31A (or other fb values for decent console resolution)
3. removing rhgb and quiet does not help
better console resolution than 80x25. for example 1024x768.
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 ...
Seems that vesa support is no longer built into the kernel for some reason. See
[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.
Don will look into setting CONFIG_FB_VESA support on in RHEL 5.1.
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
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?
*** Bug 216528 has been marked as a duplicate of this bug. ***
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
committed in 2.6.18-18.el5
Is this available for testing anywhere?
*** Bug 234448 has been marked as a duplicate of this bug. ***
VESA framebuffer support in kernel-2.6.18-18.el5.i686.rpm is working well for me
Seems to be working just fine here as well.
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
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.
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.