Description of problem:
Using a nVidia NV44 [GeForce 6200 TurboCache(TM) rev. a1] on an Intel DP965LT
mainboard (version AAD41694-206) leads to unsupported video modes on an Acer
AL1716 monitor. The issue is reproductible in Fedora Core 6 as well (both
default packets and updated ones, as to 20070122).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install RHEL5 Beta 2 / FC6 on a system having a previously described hardware
2. reboot the system after install either in runlevel 5 or runlevel 3 and
'xinit' or 'startx'.
Actual results: The monitor displays "Invalid input mode".
Expected results: on screen image at the required resolution (1280x1024).
Additional info: Output is OK in RHEL4-ES-U2; installing NVidia-provided drivers
on RHEL5 Beta 2 / FC6 appears to solve the problem. I have also tried to
manually edit /etc/X11/xorg.conf and define the vertical refresh freq. It
appears to work, although the frequencies displayed by the monitor are quite
different than the ones set up in xorg.conf (e.g. 60 Hz vert. / 64 kHz hor.
despite having set Mode "1280x1024@75Hz" in xorg.conf).
Can you attach the X log from the failed startup please?
Created attachment 146506 [details]
X log file when trying to use "nv" driver
I tried again right now to start X using the included nv driver (the system is
using the NVidia provided drivers right now). The reported behaviour statys the
Is this still an issue in F7 + updates?
Reporter, could you please reply to the previous question? If you won't reply in
one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.