 | Junior Member with 14 posts. | | | | About the rosolution???? I have problem with my rosolution.
My computer rosolution is 800x600, but i wan to change it into 1024x768.
I have try the redhat-config-xfree86 command, but it doesn't work.
Acutually, i can get into the display setting after i type redhat-config-xfree86, and i also changed the rosolution from 800*600 to 1024*768. However, the second time i went into the display setting, i found that the rosolution stay the same as 800*600. What's up?
Just now, i also try to edit etc/X11/XF86Config file with vi.
1, I login as root.
2, From that file, it seems that there are only two rovolution availalbe for the
Linux systems, which are 800x600 and 640x480.
3, I insert the 1024x768 rovolution into the file, and save it.
4, After that, i use the redhat-config-xfree86 to set rovolution as 1024x768.
5, Finally, the rovolution always stay as 800x600.
Which means the problem is still here.
Somebody Help. | | Junior Member with 14 posts. | | | | by the way, i am using the redhat9.
here is the XF86Config file's detail,
# XFree86 4 configuration created by redhat-config-xfree86
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "DevInputMice" "AlwaysCore"
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 "keyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/psaux"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection
Section "InputDevice"
# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time.
Identifier "DevInputMice"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "1024x768@75HZ"
HorizSync 31.5 - 37.9
VertRefresh 50.0 - 75.0
Option "dpms"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "nv"
VendorName "Videocard vendor"
BoardName "NVIDIA GeForce 4 MX (generic)"
VideoRam 65536
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "800x600" "640x480"
EndSubSection
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection | | Senior Member with 1,410 posts. | | | | If you haven't already, you should definitely have a look at ftp://download.nvidia.com/XFree86/Li...496/README.txt for some excellent info on configuring the nvidia drivers. If you are not using the latest nvidia drivers, you should download and install them. Regardless, I suspect that your resolution problem is not a driver issue -- but to be sure, you should examine the file /var/log/XFree86.#.log, where # is the number of your display (likely 0 -- that's zero, not the letter 'O'). You may find some clues there, such as 1024x768 not being a supported resolution for your monitor/card, etc.
Hope this helps.
__________________ The slowest component still sits at the keyboard. | | Junior Member with 14 posts. | | | | | | | Junior Member with 14 posts. | | | | By the way, the system cannot find my monitor in the list provided by redhat.
FOR MONITOR:
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "1024x768@75HZ"(I use vi to write this by myself)
HorizSync 31.5 - 37.9
VertRefresh 50.0 - 75.0
Option "dpms"
EndSection
FOR VIDEO CARD
Section "Device"
Identifier "Videocard0"
Driver "nv"
VendorName "Videocard vendor"
BoardName "NVIDIA GeForce 4 MX (generic)"
VideoRam 65536
EndSection
FOR SCREEN:
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "800x600" "640x480"
(I try to write this line like "Modes "1024x768" "800x480" 640x480" , but it doesn't work.
EndSubSection
EndSection | | Senior Member with 1,410 posts. | | | | I suspect your monitor is the problem. You have specified a limited horizontal sync range (which may, in fact, be correct for your monitor, but you should check this -- what brand/model of monitor are you using?). X-windows calculates the available modes from information about the capabilities of your video card/chipset and monitor and removes any modes that are unsupported by the combination of your hardware. You may find messages about the modes removed in /var/log/XFree86.0.log. For example, my log contains messages such as:
(II) S3VIRGE(0): Not using default mode "640x350" (vrefresh out of range)
(II) S3VIRGE(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan)
(II) S3VIRGE(0): Not using default mode "640x400" (vrefresh out of range)
(II) S3VIRGE(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan)
(II) S3VIRGE(0): Not using default mode "720x400" (vrefresh out of range)
(II) S3VIRGE(0): Not using default mode "360x200" (bad mode clock/interlace/doublescan)
(II) S3VIRGE(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
(II) S3VIRGE(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
(II) S3VIRGE(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
etc.
You might have a look at your log and see what you find.
Hope this helps.
__________________ The slowest component still sits at the keyboard. | | Junior Member with 14 posts. | | | | Information from XFree86.0.log list below,
(II) Setting vga for screen 0.
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/X11R6/lib/modules/linux/libint10.a
(II) Module int10: vendor="The XFree86 Project"
compiled for 4.3.0, module version = 1.0.0
ABI class: XFree86 Video Driver, version 0.6
(II) NV(0): Initializing int10
(II) NV(0): Primary V_BIOS segment is: 0xc000
(--) NV(0): Chipset: "GeForce4 MX Integrated GPU"
(**) NV(0): Depth 24, (--) framebuffer bpp 32
(==) NV(0): RGB weight 888
(==) NV(0): Default visual is TrueColor
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/X11R6/lib/modules/libvgahw.a
(II) Module vgahw: vendor="The XFree86 Project"
compiled for 4.3.0, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.6 | | Junior Member with 14 posts. | | | | (II) NV(0): Monitor0: Using hsync range of 31.50-37.90 kHz
(II) NV(0): Monitor0: Using vrefresh range of 50.00-75.00 Hz
(II) NV(0): Clock range: 12.00 to 350.00 MHz
(II) NV(0): Not using default mode "640x350" (vrefresh out of range)
(II) NV(0): Not using default mode "320x175" (vrefresh out of range)
(II) NV(0): Not using default mode "640x400" (vrefresh out of range)
(II) NV(0): Not using default mode "320x200" (vrefresh out of range)
(II) NV(0): Not using default mode "720x400" (vrefresh out of range)
(II) NV(0): Not using default mode "360x200" (vrefresh out of range)
(II) NV(0): Not using default mode "640x480" (hsync out of range)
(II) NV(0): Not using default mode "320x240" (hsync out of range)
(II) NV(0): Not using default mode "800x600" (hsync out of range)
(II) NV(0): Not using default mode "400x300" (hsync out of range)
(II) NV(0): Not using default mode "800x600" (hsync out of range)
(II) NV(0): Not using default mode "400x300" (hsync out of range)
(II) NV(0): Not using default mode "800x600" (hsync out of range)
(II) NV(0): Not using default mode "400x300" (hsync out of range)
(II) NV(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1024x768" (hsync out of range)
(II) NV(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1024x768" (hsync out of range)
(II) NV(0): Not using default mode "512x384" (hsync out of range)
(II) NV(0): Not using default mode "1024x768" (hsync out of range)
(II) NV(0): Not using default mode "512x384" (hsync out of range)
(II) NV(0): Not using default mode "1024x768" (hsync out of range)
(II) NV(0): Not using default mode "512x384" (hsync out of range)
(II) NV(0): Not using default mode "1024x768" (hsync out of range)
(II) NV(0): Not using default mode "512x384" (hsync out of range)
(II) NV(0): Not using default mode "1152x864" (hsync out of range)
(II) NV(0): Not using default mode "576x432" (hsync out of range)
(II) NV(0): Not using default mode "1280x960" (hsync out of range)
(II) NV(0): Not using default mode "640x480" (hsync out of range)
(II) NV(0): Not using default mode "1280x960" (hsync out of range)
(II) NV(0): Not using default mode "640x480" (hsync out of range)
(II) NV(0): Not using default mode "1280x1024" (hsync out of range)
(II) NV(0): Not using default mode "640x512" (hsync out of range)
(II) NV(0): Not using default mode "1280x1024" (hsync out of range)
(II) NV(0): Not using default mode "640x512" (hsync out of range)
(II) NV(0): Not using default mode "1280x1024" (hsync out of range)
(II) NV(0): Not using default mode "640x512" (hsync out of range)
(II) NV(0): Not using default mode "1600x1200" (hsync out of range)
....................................
.................................... | | Junior Member with 14 posts. | | | | .................................
(II) NV(0): Not using default mode "1024x768" (hsync out of range)
(--) NV(0): Virtual size is 800x600 (pitch 800)
(**) NV(0): *Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(II) NV(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync
(**) NV(0): *Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
(II) NV(0): Modeline "640x480" 31.50 640 656 720 840 480 481 484 500 -hsync
-vsync
(**) NV(0): Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
(II) NV(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync
(**) NV(0): Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz
(II) NV(0): Modeline "640x480" 31.50 640 664 704 832 480 489 491 520 -hsync
-vsync
(**) NV(0): Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz
(II) NV(0): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525 -hsync
-vsync
.................................................... | | Junior Member with 14 posts. | | |
16-Dec-2003, 07:57 AM
#10 | After i have those information, what shall i do next?
I am a new. | | Junior Member with 14 posts. | | |
16-Dec-2003, 08:17 AM
#11 | | | | Junior Member with 14 posts. | | |
16-Dec-2003, 08:18 AM
#12 | | | | Junior Member with 14 posts. | | |
16-Dec-2003, 08:19 AM
#13 | more Is there any problems,
Thanks. | | Senior Member with 1,410 posts. | | |
18-Dec-2003, 03:24 AM
#14 | The messages in your log suggest that your monitor cannot support the 1024x768 resolution (due to limited horizontal sync), and this is why X-windows ignores this specification in your XF86Config file. Can you run the monitor in 1024x768 resolution in Windoze or some other O/S? What brand/model of monitor are you using?
Additional info appreciated.
__________________ The slowest component still sits at the keyboard. | | Junior Member with 14 posts. | | |
18-Dec-2003, 09:06 AM
#15 | yes, the monitor can support 1024*768 resoloution in winXP.
My monitor is a LCD, it is small brand product.
It support 1024*768 @75Hz. |  THIS THREAD HAS EXPIRED.
Are you having the same problem?
We have volunteers ready to answer your question, but first you'll have to join for free. Need help getting started? Check out our Welcome Guide.
|
Smart Search
| Find your solution! | |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | | |  WELCOME TO TECH SUPPORT GUY! Are you looking for the solution to your computer problem? Join our site today to ask your question -- for free! Our site is run completely by volunteers who want to help you solve your computer problems. See our Welcome Guide to get started.
| You Are Using: |
Advertisements do not imply our endorsement of that product or service.
All times are GMT -5. The time now is 06:50 AM.
Copyright © 1996 - 2009 TechGuy, Inc. All rights reserved.
Powered by vBulletin, Copyright © 2000 - 2009, Jelsoft Enterprises Ltd. | |
|