Please do not send private support request, [email protected] is made for that purpose.
The plan was to update nvidia-kmod in F-10 along with nvidia-newest-kmod from F-9. F-9 will have 180.60 in stable and 185.18.14 in testing for nvidia-newest to match the related cuda toolkit that nvidia support. But indeed, I could have made only 185.18.14 in F-10 for nvidia, I just plan to move them all along to stable (on next kernel update), that will bump the version from 180.51 to 185.18.14. (so akmod-nvidia-180.60 and etc can be provided in the rpmfusion-nonfree-updates-stable, mostly for archiving purpose). Now are you really sure that the problem will be solved by a version bump ? That would deserve a bug report to track what have been done. and what was the behaviour with a cleaner xorg.conf which let autodetection works. Nicolas (kwizart) ---------- Forwarded message ---------- From: Jack Howarth <[email protected]> Date: 2009/7/15 Subject: why no 185.18.14 for fc10? To: [email protected], [email protected] Is there a reason that the nvidia drivers for fc10 are still stuck at the 180.51 release? Today I installed a EVGA GeForce 9600GT which seems unable to process the EDID information under Fedora 10's nvidia drivers. The display is restricted to 640x480 unless I resort to... Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" ModulePath "/usr/lib64/xorg/modules/extensions/nvidia" ModulePath "/usr/lib64/xorg/modules" EndSection Section "ServerFlags" Option "AIGLX" "on" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # keyboard added by rhpxl Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105+inet" Option "XkbLayout" "us" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" HorizSync 28.0 - 81.1 VertRefresh 43.0 - 76.0 Option "DPMS" # 1600x1200 @ 60.00 Hz (GTF) hsync: 74.52 kHz; pclk: 160.96 MHz # Modeline "1600x1200_60.00" 160.96 1600 1704 1880 2160 1200 1201 1204 1242 -HSync +Vsync ModeLine "1680x1050" 119.0 1680 1728 1760 1840 1050 1053 1059 1080 EndSection Section "Device" Identifier "Videocard0" Driver "nvidia" Option "UseEDIDFreqs" "FALSE" Option "UseEDIDDpi" "FALSE" Option "DPI" "100 x 100" Option "ModeValidation" "NoEdidModes" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 24 Option "AddARGBGLXVisuals" "True" Option "ExactModeTimingsDVI" "TRUE" SubSection "Display" Viewport 0 0 Depth 24 Modes "1680x1050" EndSubSection EndSection Section "Extensions" Option "Composite" "Enable" EndSection Unfortunately, I have been unable to find a 1600x1200 modeline which doesn't cause an out of range error on my Viewsonic VP2030b. I am hoping that the newer nvidia drivers might have this resolved (since it isn't an issue on another x86_64 Fedora 10 box with an EVGA GeForce 8600 GT card which doesn't require the above hack). Thanks in advance for any information as it has been a real struggle to get the GeForce 9600 GT to display above 640x480. Jack
