Red Hat Bugzilla – Bug 105938
Graphical Installer Glitch on Dell Inspiron 7500
Last modified: 2007-11-30 17:10:31 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Description of problem:
The graphical installer doesn't come up correctly with either severn beta. The
xserver starts but only about 1/4 of an inch of video is displayed on the left
hand side of the screen. The laptop in question has a 1400x1050 display and a
ATI Rage Mobility graphics card. After doing a text install, the generated
default X config works fine.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot a severn install disc
2. Proceed with the graphical install
Actual Results: Only the left most 1/4 inch of video is displayed, and it looks
Expected Results: The normal graphical redhat install is displayed.
If you start with 'resolution=1400x1050' does it come up in the graphical
What happened to my previous updates? I already answered these questions. I'll
re-upload them when I'm not traveling. Basically, at 1400x1050, the screen just
came up grey.
I was referring to the install boot time option like:
which makes the graphical installer try to use 1400x1050 instead of 800x600.
OK, here are the comments from my previous entries that were lost:
------- Additional Comments From firstname.lastname@example.org 2003-10-01 06:38 -------It looks
like the X server only starts once. The console says Probing mouse, Attempting
to start xserver, waiting for X server, 1 2 3 4 5 xserver started successfully.
It doesn't look like it tries twice.
When supplying the resolution=1400x1050 on the command line, when X comes up it
just shows a blank grey screen.
Back to today, October 15th:
I just tried it last night with test3 and the same problems occur. I saw a post
that about nofb so I tried it and everything worked fine that way. So "linux
nofb" makes the graphical installer work fine with test3 anaconda.
Okay, that's going to have to be the workaround, then. Basically, it's a video
BIOS bug in that it can't handle running the native X resolution after going
into the vga16fb mode.