Red Hat Bugzilla – Bug 26892
Wrong video mode on reboot with Rage Mobility
Last modified: 2007-04-18 12:31:23 EDT
During a GUI installation (NFS-Full, FTP-Full, HTTP-Laptop), I chose
1024x768x16 for my display settings. Upon reboot, the system was set to
This problem doesn't exhibit itself after a TUI installation. Also, during
"test settings" the correct resolution is diplayed.
TUI: FTP-Full, HTTP-Laptop
Also, I tried this with qa0207-qa209.
This defect is considered MUST-FIX for Florence Release-Candidate #1
Is the XF86Config file right and the resolution just comes up wrong, or is the
Brent, here's what I've found:
Even though I picked everything correctly during the install, a post install
check of XF86Config shows:
"800x600", "Generic Monitor". (I was wrong about 640x480, just looked like it.
When I manually change it to "1024x768", "Generic Laptop Display 1024x768", it
works like a champ.
so user error - picked wrong LCD screen setting.
Re-opening, per Matt's recommendation.
Still not working. In my above comment, when I say "manually change", I mean
"running Xconfigurator" from the shell as root.
Tried inserting "linux vga-787" at bootup. Didn't have any effect.
Interestingly, this does not happen in TUI mode. Also, testing X at 1024x768
results in a correct file written to /tmp/XF86Config.test during the install.
After package installation, however, the wrong settings are written to the
/mnt/sysimage/etc/X11/XF86Config-4 file. This doesn't make much sense.
I presume the mobility is on a notebook with built-in LCD. What is the model of
notebook? Can you give any more information, e.g. ddcprobe output, or the
original XF86Config-4 file that's written to the disk?
I have access to several notebooks with mobility chipsets, but I do not believe
I have seen the bebaviour where you select 1024x768, but "800x600" is actually
set in the XF86Config-4 file...
I've seen it happen on a Compaq Presario 1700T and Aaron's is a Dell Latitude
CPx. Both have the ATI Rage Mobility with 8MB of vram.
This problem is due to a bug in iw/xconfig.py. I have a fix for it, but I'm
waiting for permission to check it into CVS.
The update has now been committed to cvs. Brock, this is a large change to the
code, so if you have time to double check me here, it would be appreciated.
I'll be testing this today as well. The change affects the x configuration
screen in general, not just the Rage Mobility. It just so happens that this
video card exposed a bug in xconfig.py that had been there for a while.