Bug 216528 - vesa framebuffer (vga=0x317) parameter blanks display
vesa framebuffer (vga=0x317) parameter blanks display
Status: CLOSED DUPLICATE of bug 236195
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Don Zickus
Brian Brock
Depends On:
Blocks: 228988 227613
  Show dependency treegraph
Reported: 2006-11-20 17:51 EST by Erik Bussink
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-04-26 12:09:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Erik Bussink 2006-11-20 17:51:42 EST
Description of problem:

If the vga=0x317 kernel boot parameter is present, there is no text display.
The screen stays blank, while the system starts up in the background. 

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

This is the sample section taken from my grub.conf that shows the vga=0x317

title Red Hat Enterprise Linux Client (2.6.18-1.2747.el5)
        root (hd0,1)
        kernel /vmlinuz-2.6.18-1.2747.el5 ro root=LABEL=/ rhgb quiet vga=0x317
        initrd /initrd-2.6.18-1.2747.el5.img

How reproducible:

If the vga=0x317 boot parameter is present, no graphical display. If it's
removed, the boot process is visible at normal text resolution.

Steps to Reproduce:
1. add vga=03x17 to kernel parameters.
2. reboot
3. Connect to system with SSH and edit grub.conf to remove kernel parameter.
Actual results:

Blanks text display

Expected results:

The utilisation of the vga= goes on kernel line and controls the resolution and
colour depth of framebuffer, which should load 128x48 (or 1024x768 pixel)
resolution instead of the default 80x24.

vesafb codes

    | 640x480  800x600  1024x768 1280x1024
256 |  0x301    0x303    0x305    0x307   
32k |  0x310    0x313    0x316    0x319   
64k |  0x311    0x314    0x317    0x31A   
16M |  0x312    0x315    0x318    0x31B

Additional info:

Comment 4 RHEL Product and Program Management 2007-04-25 19:05:51 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
Comment 5 Peter Martuccelli 2007-04-26 12:09:17 EDT

*** This bug has been marked as a duplicate of 236195 ***

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