LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices


Reply
  Search this Thread
Old 05-09-2011, 12:54 AM   #16
John VV
LQ Muse
 
Registered: Aug 2005
Location: A2 area Mi.
Posts: 17,624

Rep: Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651

removing then installing ( and reinstalling ) somethings might help ? unknown if it will
BUT a lot of times this will "fix" a system - things can get messed up .


you might try this

you will need to make a few lists and see what IS installed
most you can just use a pen and paper to take notes


1) remove all and any nvidia
for a list of what is installed
Code:
su -
rpm -qa | grep nvidia
then for any copy/paste the name into yum
Code:
su -
yum remove ??????
-- NOTE : DO NOT , DO NOT use the "y" option in yum
then remove any copy’s of "xorg.conf"
and remove ANY hidden nvidia file from your HOME folder ( .nvidia-settings-rc )

then reinstall "nouveau" ( Plymouth graphical boot dose need it )
i am thinking that maybe yum removed other things when you uninstalled this ? maybe?
Code:
yum search nouveau

-- then copy/paste it's name from the list 
yum install ???????
doing a reinstall of xorg might help
same as above search then use "reinstall"
something like this
Code:
su -
yum reinstall xorg
this might bring a bunch of things so it might take a bit of time.

remove ANY blacklist that you put in menu.lis ( grub.conf)!!!!!!!

reboot

then see if the "nouveau" ( default) driver will let you change the screen resolution
 
Old 05-09-2011, 03:37 PM   #17
ingesis
LQ Newbie
 
Registered: May 2011
Posts: 15

Original Poster
Rep: Reputation: 0
I've followed all the instructions to uninstall any Nvidia driver and reinstall of noveau; and just get the same, after various restarts and trying to configure my monitor resolution with System -> Preferences -> Monitor, I get an Unknown model with 3 options 1024x768, 800x600 and 640x480.

So, in order to not get a headache with that refresh rate (60 Hz) I decided to reinstall the Nvidia driver from the guide with the akmod version. After this just got the same that yesterday, a lot of resolution options but not the ones I want.

My new xorg.conf file has this:

Code:
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 260.19.29  (mockbuild@hephaestus.wilsonet.com)  Thu Dec 16 04:43:59 EST 2010

# RPM Fusion - nvidia-xorg.conf
# 

Section "ServerLayout"
    Identifier     "Default Layout"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "InputDevice"
    # generated from data in "/etc/sysconfig/keyboard"
    Identifier     "Keyboard0"
    Driver         "kbd"
    Option         "XkbLayout" "la"
    Option         "XkbModel" "pc105"
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 "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Samsung SyncMaster"
    HorizSync       30.0 - 71.0
    VertRefresh     50.0 - 160.0
EndSection

Section "Device"
    Identifier     "Videocard0"
    Driver         "nvidia"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce 8600 GTS"
EndSection

Section "Screen"
    Identifier     "Default Screen"
    Device         "Videocard0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "1152x864_75 +0+0; 1024x768 +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection
So, it was a success the uninstall and reinstall of Nvidia driver but, is there any thing more to do? A fresh reinstall of Fedora could help?
 
Old 05-09-2011, 03:50 PM   #18
John VV
LQ Muse
 
Registered: Aug 2005
Location: A2 area Mi.
Posts: 17,624

Rep: Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651
I am at a loss on this

you should be able to change the screen resolution
 
Old 05-09-2011, 07:36 PM   #19
ingesis
LQ Newbie
 
Registered: May 2011
Posts: 15

Original Poster
Rep: Reputation: 0
Me again. I've made a fresh new installation of all my Fedora system and the first thing to config was my NVidia driver. It worked fine and just got the same resolutions previously described... although, I've noticed something, it seems that the plymouth app doesn't work at my HW since it starts in text mode and reading about this app in wikipedia I've noticed that it needs kernel-based mode-setting (KMS) to work. May be this KMS function should be configured previously in my system in order to have all the potencial of my Nvidia card.

What do you think?

I've been thinking about to put a new post in the forum especifically to my new problem, because the one that describes this thread doesn't have to be with Monitor resolution config.
 
Old 05-09-2011, 07:55 PM   #20
John VV
LQ Muse
 
Registered: Aug 2005
Location: A2 area Mi.
Posts: 17,624

Rep: Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651
plymouth uses the "nouveau" driver and is not compatible with nvidia.
 
Old 05-09-2011, 08:05 PM   #21
cascade9
Senior Member
 
Registered: Mar 2011
Location: Brisneyland
Distribution: Debian, aptosid
Posts: 3,753

Rep: Reputation: 935Reputation: 935Reputation: 935Reputation: 935Reputation: 935Reputation: 935Reputation: 935Reputation: 935
I'd guess that for whatever reason, EDID isnt working with your monitor. Adding the required resolutions in xorg.conf should give you the modes you are after.

I'd copy over my xorg.conf file, but I'm testing nouveau (and its still yuck) so I dont have one.

Quote:
Originally Posted by ingesis View Post
Me again. I've made a fresh new installation of all my Fedora system and the first thing to config was my NVidia driver. It worked fine and just got the same resolutions previously described... although, I've noticed something, it seems that the plymouth app doesn't work at my HW since it starts in text mode and reading about this app in wikipedia I've noticed that it needs kernel-based mode-setting (KMS) to work. May be this KMS function should be configured previously in my system in order to have all the potencial of my Nvidia card.
Unless nVidia has changed direction, KMS will not work with the closed drivers. Well, it might be hackable somehow, but (AFAIK) offically the nVidia closed drivers dont support KMS, so trying to get KMS with the closed drivers could (would?) be asking for more headaches.

Interesting that fedora actually kicks you back to text mode, ubuntu with plymouth doesnt do that, it just looks UGLY.

*edit- that 'ugly with the closed drivers' problem is fixable with some hacking, but I dont like plymouth and I dont use it, so I've never tried myself.

Quote:
Originally Posted by ingesis View Post
So, in order to not get a headache with that refresh rate (60 Hz) I decided to reinstall the Nvidia driver from the guide with the akmod version. After this just got the same that yesterday, a lot of resolution options but not the ones I want.
Just FYI, the 60Hz = headache' problem is something you only get with CRTs. It shouldnt happen with LCDs, LED LCDs, etc..

Last edited by cascade9; 05-10-2011 at 05:58 PM.
 
Old 05-09-2011, 10:10 PM   #22
ingesis
LQ Newbie
 
Registered: May 2011
Posts: 15

Original Poster
Rep: Reputation: 0
Well, thanks for the comments... and I begin to think it would be better to get another monitor, this time an LCD, of course; it's just that I thought it would be a good idea to use my HW with a Linux distro since they have the fame to deal great with legacy stuff.

It would be possible that with another distro, maybe debian or ubuntu, this situation could be solved? Although I doub it since Fedora is very popular and for the know-how of Red Hat in the business.
 
Old 05-10-2011, 06:01 PM   #23
cascade9
Senior Member
 
Registered: Mar 2011
Location: Brisneyland
Distribution: Debian, aptosid
Posts: 3,753

Rep: Reputation: 935Reputation: 935Reputation: 935Reputation: 935Reputation: 935Reputation: 935Reputation: 935Reputation: 935
If your thinking of getting an LCD, I'd get a LED LCD.The lower power consumption from LED LCDs is nice.

Its possible that changing distro will help. I cant be sure, its been a long time since I've had EDID problem, and when I get get the isue it was with other peoples hardware.

Last edited by cascade9; 05-10-2011 at 06:11 PM.
 
Old 05-14-2011, 11:27 AM   #24
ingesis
LQ Newbie
 
Registered: May 2011
Posts: 15

Original Poster
Rep: Reputation: 0
I have a few doubts about this issue.

What would be the reason that the same HW, with the correct set of drivers, works better in Windows XP than in Fedora even when the linux distro is much more recent that the windows OS? It's possible that windows has a "feature" to make this happen?

The resolution in which a monitor works it's defined by the monitor specs or by the video card? I mean, if I want to get a new monitor should I consider to get a new video card to get the resolutions I wish?
 
Old 05-15-2011, 03:23 AM   #25
cascade9
Senior Member
 
Registered: Mar 2011
Location: Brisneyland
Distribution: Debian, aptosid
Posts: 3,753

Rep: Reputation: 935Reputation: 935Reputation: 935Reputation: 935Reputation: 935Reputation: 935Reputation: 935Reputation: 935
I have no idea why EDID sometimes fails, but I doubt it has anything to do with windows. BTW, just to check if it is EDID try running this command-

grep -i edid /var/log/Xorg.0.log

Post the results (I'll bet you get "Unable to read EDID for display device")

The resolution is defined by the monitor, even some of the video cards I have that are _really_ old go to much higher resolutions than are common even now (like a GF4MX will go to 2048x1536). So anything that uses the 270.41.06 dirvers should work fine with the most common resolutions aroud now, 1440x900, 1920x1080, even the rarer but IMO much better 1920x1200.
 
Old 05-16-2011, 12:02 AM   #26
ingesis
LQ Newbie
 
Registered: May 2011
Posts: 15

Original Poster
Rep: Reputation: 0
Thanks for your help cascade9 but I think my problem is even bigger than EDID since it doesn't appear in the /var/log/Xorg.0.log. Right now I'm not in my Fedora machine but luckily I have a version of this file at hand and doing a search for EDID term indicates it doesn't exist any reference.

So, here it is the complete file, I know it's to long but I just don't know which part is important and which not (see attached file).

Is there something else that you can see is erroneous?
Attached Files
File Type: log Xorg.0.log (64.4 KB, 26 views)
 
Old 06-01-2011, 06:46 PM   #27
ingesis
LQ Newbie
 
Registered: May 2011
Posts: 15

Original Poster
Rep: Reputation: 0
Thumbs up

I've kept working on this problem and now I can have the resolutions I've being looking for, although I don't have the refresh rate I need. But I'm very pleasant with the results obtained.

I've been using the cvt comand in this way:
Code:
$ cvt 1280 768 79
# 1280x768 78.89 Hz (CVT) hsync: 63.67 kHz; pclk: 109.00 MHz
Modeline "1280x768_79.00"  109.00  1280 1368 1496 1712  768 771 781 807 -hsync +vsync
$ cvt 1280 800 76
# 1280x800 75.89 Hz (CVT) hsync: 63.67 kHz; pclk: 109.00 MHz
Modeline "1280x800_76.00"  109.00  1280 1368 1496 1712  800 803 809 839 -hsync +vsync
And using that info within the xorg.conf file, I've ended with this:
Code:
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 260.19.29  (mockbuild...)  Thu Dec 16 04:43:59 EST 2010

# RPM Fusion - nvidia-xorg.conf
# 

Section "ServerLayout"
    Identifier     "Default Layout"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "InputDevice"

    # generated from data in "/etc/sysconfig/keyboard"
    Identifier     "Keyboard0"
    Driver         "kbd"
    Option         "XkbLayout" "la"
    Option         "XkbModel" "pc105"
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 "Monitor"
    Identifier     "Monitor0"
    VendorName     "Samsung"
    ModelName      "Samsung SyncMaster"
    HorizSync       30.0 - 70.00
    VertRefresh     50.0 - 160.00
    Option	   "DPMS"
    #Option         "PreferredMode" "1280x768"
    Option	   "1280x768" "1280x800"
    UseModes       "Modes[0]"
EndSection

Section "Modes"
Identifier "Modes[0]"
Modeline "1280x800_76.00"  109.00  1280 1368 1496 1712  800 803 809 839
Modeline "1280x768_79.00"  109.00  1280 1368 1496 1712  768 771 781 807
Modeline "1024x768_75.00"   82.00  1024 1088 1192 1360  768 771 775 805
EndSection

Section "Device"
    Identifier     "Videocard0"
    Driver         "nvidia"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce 8600 GTS"
EndSection

Section "Screen"
    Identifier     "Default Screen"
    Device         "Videocard0"
    Monitor        "Monitor0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth   24 
    Option         "TwinView" "0"
    #Option         "metamodes" "nvidia-auto-select +0+0"
    #Option	   "metamodes" "1280x800_75.00 +0+0"
    Option	   "1280x768_79.00 +0+0" "1280x800_76.00 +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection
and with the nvidia-settings command I'm allowed to change the resolution to 1280x800 or 1280x768 with no problems.

But... I just can not manage it to work with this resolution as default the next time a start up the GUI environment.

In the Xorg.0.log file I get this messages:
Code:
[  3678.678] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  3678.680] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jun  1 18:08:45 2011
[  3678.682] (==) Using config file: "/etc/X11/xorg.conf"
[  3678.682] (==) Using config directory: "/etc/X11/xorg.conf.d"
[  3678.683] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  3678.684] (==) ServerLayout "Default Layout"
[  3678.684] (**) |-->Screen "Screen0" (0)
[  3678.684] (**) |   |-->Monitor "Monitor0"
[  3678.685] (**) |   |-->Device "Device0"
[  3678.685] (**) |-->Input Device "Keyboard0"
[  3678.685] (**) |-->Input Device "Mouse0"
[  3678.685] (**) Option "Xinerama" "0"
and in the middle of the file
Code:
[  3678.709] (II) LoadModule: "nvidia"
[  3678.711] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
[  3678.712] (II) Module nvidia: vendor="NVIDIA Corporation"
[  3678.712] 	compiled for 4.0.2, module version = 1.0.0
[  3678.712] 	Module class: X.Org Video Driver
[  3678.712] (II) NVIDIA dlloader X Driver  260.19.36  Tue Jan 18 16:57:32 PST 2011
[  3678.712] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[  3678.713] (--) using VT number 7
[  3678.725] (II) Loading sub module "fb"
[  3678.725] (II) LoadModule: "fb"
[  3678.726] (II) Loading /usr/lib64/xorg/modules/libfb.so
[  3678.727] (II) Module fb: vendor="X.Org Foundation"
[  3678.727] 	compiled for 1.9.5, module version = 1.0.0
[  3678.727] 	ABI class: X.Org ANSI C Emulation, version 0.4
[  3678.727] (II) Loading sub module "wfb"
[  3678.727] (II) LoadModule: "wfb"
[  3678.728] (II) Loading /usr/lib64/xorg/modules/libwfb.so
[  3678.729] (II) Module wfb: vendor="X.Org Foundation"
[  3678.729] 	compiled for 1.9.5, module version = 1.0.0
[  3678.729] 	ABI class: X.Org ANSI C Emulation, version 0.4
[  3678.729] (II) Loading sub module "ramdac"
[  3678.729] (II) LoadModule: "ramdac"
[  3678.729] (II) Module "ramdac" already built-in
[  3678.729] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[  3678.730] (==) NVIDIA(0): RGB weight 888
[  3678.730] (==) NVIDIA(0): Default visual is TrueColor
[  3678.730] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[  3678.730] (**) NVIDIA(0): Option "TwinView" "0"
[  3678.730] (**) NVIDIA(0): Enabling RENDER acceleration
[  3678.730] (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
[  3678.730] (II) NVIDIA(0):     enabled.
[  3679.324] (II) NVIDIA(0): NVIDIA GPU GeForce 8600 GTS (G84) at PCI:2:0:0 (GPU-0)
[  3679.325] (--) NVIDIA(0): Memory: 262144 kBytes
[  3679.325] (--) NVIDIA(0): VideoBIOS: 60.84.32.00.10
[  3679.325] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[  3679.325] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[  3679.325] (--) NVIDIA(0): Connected display device(s) on GeForce 8600 GTS at PCI:2:0:0
[  3679.325] (--) NVIDIA(0):     Samsung SyncMaster (CRT-1)
[  3679.325] (--) NVIDIA(0): Samsung SyncMaster (CRT-1): 400.0 MHz maximum pixel clock
[  3679.400] (II) NVIDIA(0): Assigned Display Device: CRT-1
[  3679.400] (==) NVIDIA(0): 
[  3679.400] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[  3679.400] (==) NVIDIA(0):     will be used as the requested mode.
[  3679.400] (==) NVIDIA(0): 
[  3679.401] (II) NVIDIA(0): Validated modes:
[  3679.401] (II) NVIDIA(0):     "nvidia-auto-select"
[  3679.401] (II) NVIDIA(0): Virtual screen size determined to be 1024 x 768
[  3679.426] (--) NVIDIA(0): DPI set to (81, 81); computed from "UseEdidDpi" X config
[  3679.426] (--) NVIDIA(0):     option
[  3679.426] (==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
[  3679.426] (--) Depth 24 pixmap format is 32 bpp
[  3679.426] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access.
[  3679.427] (II) NVIDIA(0): Initialized GPU GART.
[  3679.439] (II) NVIDIA(0): Setting mode "nvidia-auto-select"
[  3679.472] (II) Loading extension NV-GLX
[  3679.499] (II) NVIDIA(0): Initialized OpenGL Acceleration
[  3679.522] (==) NVIDIA(0): Disabling shared memory pixmaps
[  3679.522] (II) NVIDIA(0): Initialized X Rendering Acceleration
[  3679.522] (==) NVIDIA(0): Backing store disabled
[  3679.522] (==) NVIDIA(0): Silken mouse enabled
[  3679.524] (**) NVIDIA(0): DPMS enabled
[  3679.524] (II) Loading extension NV-CONTROL
[  3679.524] (II) Loading extension XINERAMA
[  3679.524] (WW) NVIDIA(0): Option "1280x768" is not used
[  3679.524] (WW) NVIDIA(0): Option "1280x768_79.00 +0+0" is not used
[  3679.524] (II) Loading sub module "dri2"
[  3679.524] (II) LoadModule: "dri2"
[  3679.525] (II) Reloading /usr/lib64/xorg/modules/extensions/libdri2.so
[  3679.525] (II) NVIDIA(0): [DRI2] Setup complete
[  3679.525] (==) RandR enabled
where the part I don't like is this
Code:

[  3679.524] (WW) NVIDIA(0): Option "1280x768" is not used
[  3679.524] (WW) NVIDIA(0): Option "1280x768_79.00 +0+0" is not used
Finally, I need Gnome taking the resolution defined as default every time the GUI starts.
Any suggestion?

Last edited by ingesis; 06-02-2011 at 06:31 PM.
 
Old 06-02-2011, 04:14 AM   #28
cascade9
Senior Member
 
Registered: Mar 2011
Location: Brisneyland
Distribution: Debian, aptosid
Posts: 3,753

Rep: Reputation: 935Reputation: 935Reputation: 935Reputation: 935Reputation: 935Reputation: 935Reputation: 935Reputation: 935
Quote:
Originally Posted by ingesis View Post
Thanks for your help cascade9 but I think my problem is even bigger than EDID since it doesn't appear in the /var/log/Xorg.0.log. Right now I'm not in my Fedora machine but luckily I have a version of this file at hand and doing a search for EDID term indicates it doesn't exist any reference.
Sorry, I totally missed this post. :S

That is what happens when you EDID isnt working, it wont appear in /var/log/Xorg.0.log.

Quote:
Originally Posted by ingesis View Post
with the nvidia-settings command I'm allowed to change the resolution to 1280x800 or 1280x768 with no problems.

But... I just can not manage it to work with this resolution as default the next time a start up the GUI environment.
Try lauching nvidia-setings as root. Then change the resolution to 1280x768 (or 1280x800 if you perfer). Then hit the 'Save to X Configuration File" button. That should save your current settings and keep them when you reboot.
 
Old 06-02-2011, 07:34 PM   #29
ingesis
LQ Newbie
 
Registered: May 2011
Posts: 15

Original Poster
Rep: Reputation: 0
Talking

It works!

Thanks for your help cascade9. Following your recommendation I finally managed to get "startx" use the resolution I need, but it was not so easy.

I tested a few other options that didn't work. Then I went with the option of let nvidia-settings do the work and didn't work either. So, I kept moving, copying and renaming the xorg.conf file and in some place I forgot to put a version of xorg.conf, then when I was making another try with the nvidia-settings tool I realized that a fresh new version of xorg.conf file was made and I ended with this one:

Code:
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 260.19.29  (mockbuild@hephaestus.wilsonet.com)  Thu Dec 16 04:43:59 EST 2010

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
    FontPath        "/usr/share/fonts/default/Type1"
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"
    # generated from data in "/etc/sysconfig/keyboard"
    Identifier     "Keyboard0"
    Driver         "keyboard"
    Option         "XkbLayout" "la"
    Option         "XkbModel" "pc105"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Samsung SyncMaster"
    HorizSync       30.0 - 71.0
    VertRefresh     50.0 - 160.0
    ModeLine       "1280x768_79.00" 108.740 1280 1360 1496 1712 768 769 772 804 +hsync +vsync
    ModeLine       "1024x768_85.00" 94.390 1024 1088 1200 1376 768 769 772 807 +hsync +vsync
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce 8600 GTS"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "1280x768_79 +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection
although... I just realized that it erased my 1280x800 @ 79Hz resolution. So it seems I still have one more try to do.

Bottom line: this version of xorg.conf works well!
 
Old 06-02-2011, 08:28 PM   #30
Arcane
Member
 
Registered: May 2006
Location: Latvia, Europe
Distribution: random
Posts: 310

Rep: Reputation: 312Reputation: 312Reputation: 312Reputation: 312
Speaking about this issue it's worth mentioning that Fedora forums has guide about installing nvidia-drivers
http://forums.fedoraforum.org/showthread.php?t=204752
Also if there is need for quick solution Fedora has these user made "mods" which are approved on forums aswell
http://www.dnmouse.org/autoten/
http://easylifeproject.org
Just sharing for people who might need this info.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
fedora 11 starting problem saumyag Fedora 2 04-16-2011 08:43 PM
Problem with starting mysql under fedora gvenugopal140 Linux - Newbie 7 06-15-2010 03:51 AM
Problem with starting mysql under fedora gvenugopal140 Linux - Newbie 1 06-14-2010 06:09 AM
problem starting fedora on laptop pa_ash Linux - Newbie 1 06-28-2004 02:53 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora

All times are GMT -5. The time now is 01:55 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration