Re: FC4 screen resolution problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2005-10-12 at 10:25 -0500, Jonathan Berry wrote:
> On 10/12/05, Jean François Ortolo <ortolojf@xxxxxxx> wrote:
> [snip]
> > Section "Device"
> >         Identifier  "Videocard0"
> >         Driver      "vesa"
> >         VendorName  "ASUS"
> >         BoardName   "GeForce 6200 TurboCache(TM)"
> >         videoram    0
> > EndSection
> 
> I doubt you will get very high screen resolution with the vesa driver.
>  I highly suggest that you install the nvidia driver and use it.  To
> do that, install the driver as root, then change the "vesa" above to
> "nvidia" and start X.  By the way, are you running 32-bit FC4 or
> 64-bit?  I also highly suggest 64-bit since you have an Athlon64 in
> which case you will need to get the x86_64 nvidia driver.  I don't
> know if the "nv" driver works with the newer cards, but you could also
> try that one if you do not want to install the nvidia binary driver.
> 
> > Section "Screen"
> >         Identifier "Screen0"
> >         Device     "Videocard0"
> >         Monitor    "Monitor0"
> >         DefaultDepth     24
> >         SubSection "Display"
> >                 Viewport   0 0
> >                 Depth     16
> >                 Modes    "800x600" "640x480"
> >         EndSubSection
> >         SubSection "Display"
> >                 Viewport   0 0
> >                 Depth     24
> >                 Modes    "800x600" "640x480"
> >         EndSubSection
> > EndSection
> 
> You will need to add in the modes you want to use too, as has been stated.
> 
> [snip]
> >
> >   Jean Francois Ortolo
> 
> Jonathan
> 

Thank you very much Sir

  I have been trying only 1024x768 and 800x600, I doubt the vesa driver
doesn't support 1024x768.

  I already tried the nVidia IA32 driver, for I presume I have 32-bits
FC4, it was the only one available on ftp.free.fr , if I'm not wrong, at
the time I downloaded it.

  With the IA32 nVidia driver, I have get exactly the same problem as
now, before uninstalling it to return to the vesa driver.

  I send the xorg.conf content according to the problem:

-------------------------------------------------------------

# Xorg configuration created by system-config-display

Section "ServerLayout"
	Identifier     "single head configuration"
	Screen      0  "Screen0" 0 0
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"

# RgbPath is the location of the RGB database.  Note, this is the name
of the 
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
	RgbPath      "/usr/X11R6/lib/X11/rgb"
	FontPath     "unix/:7100"
EndSection

Section "Module"
	Load  "dbe"
	Load  "extmod"
	Load  "fbdevhw"
	Load  "glx"
	Load  "record"
	Load  "freetype"
	Load  "type1"
	Load  "dri"
EndSection

Section "InputDevice"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#	Option	"Xleds"		"1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
#	Option	"XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#	Option	"XkbModel"	"pc102"
# If you have a US Microsoft Natural keyboard, you can use:
#	Option	"XkbModel"	"microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#	Option	"XkbLayout"	"de"
# or:
#	Option	"XkbLayout"	"de"
#	Option	"XkbVariant"	"nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#	Option	"XkbOptions"	"ctrl:swapcaps"
# Or if you just want both to be control, use:
#	Option	"XkbOptions"	"ctrl:nocaps"
#
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "fr"
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "IMPS/2"
	Option	    "Device" "/dev/input/mice"
	Option	    "ZAxisMapping" "4 5"
	Option	    "Emulate3Buttons" "yes"
EndSection

Section "Monitor"
	Identifier   "Monitor0"
	VendorName   "LG"
	ModelName    "Flatron L1730S"
	HorizSync    30.0 - 83.0
	VertRefresh  56.0 - 75.0
	Option	    "dpms"
EndSection

Section "Device"
	Identifier  "Videocard0"
	Driver      "vesa"
	VendorName  "ASUS"
	BoardName   "GeForce 6200 TurboCache(TM)"
	videoram    0
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Videocard0"
	Monitor    "Monitor0"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     16
		Modes    "1024x768" "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes    "1024x768" "800x600" "640x480"
	EndSubSection
EndSection

Section "DRI"
	Group        0
	Mode         0666
EndSection

------------------------------------------------

  Theoretically, there shouldn't be any error in this file, no ?

  The problem occurs only when I startx as normal user, when I startx as
root all goes fine.

  Thank you very much for your help.

  Best regards.

  Jean Francois Ortolo




[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux