After Installing the Red Hat Linux Advanced Server, I am unable to start using the STARTX for using graphics version to start my system. I have installed GNOME as boot loader. How can I slove this?

goto /etc/inittab and change the line id:3:initdefaul to id:5:initdefaul if it doesn't help, you may have a wrong config for video card settings.

i mean "id:3initdefault:" to "id:5:initdefault:"

Hi, I do have the settings in /etc/inittab as id:5:initdefault. Can you let me know how can I modify the video card settings?

can you tell me what error you are getting? are you getting anything like "screens not found" or "display device not found" or "spawnning too fast... waiting for 5 min" etc? also, pl. post your /etc/X11/XF86Config file and your video configuration. also, please scroll down the main forum page to find couple of discussions on Nvidia card installation.

I've similar problem. My server is IBM Netfinity 5500, the video card is "S3 Incorporated. 86C775/86C785". I tried to install Redhat Linux 8.0 on it. Linux probed the card as "S3 Trio 64V2". However, startx can't be run. Do you have any advise? Thank you! /etc/X11/XF86Config is like this: # File generated by anaconda. Section "ServerLayout" Identifier "Anaconda Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Mouse1" "SendCoreEvents" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" # 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. RgbPath "/usr/X11R6/lib/X11/rgb" # 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. FontPath "unix/:7100" EndSection Section "Module" Load "dbe" Load "extmod" Load "fbdevhw" Load "dri" Load "glx" Load "record" Load "freetype" Load "type1" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" # Option "AutoRepeat" "500 5" # when using XQUEUE, comment out the above line, and uncomment the # following line # Option "Protocol" "Xqueue" # 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" Option "XkbRules" "xfree86" Option "XkbModel" "pc105" Option "XkbLayout" "us" #Option "XkbVariant" "" #Option "XkbOptions" "" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "PS/2" Option "Device" "/dev/psaux" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "yes" EndSection Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Device" "/dev/input/mice" Option "Protocol" "IMPS/2" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor Model" HorizSync 30-54 VertRefresh 50-120 Option "dpms" EndSection Section "Device" # no known options Identifier "S3 86C775 (Trio64V2/DX)" Driver "s3" VendorName "S3 86C775 (Trio64V2/DX)" BoardName "S3 86C775 (Trio64V2/DX)" #BusID EndSection Section "Screen" Identifier "Screen0" Device "S3 86C775 (Trio64V2/DX)" Monitor "Monitor0" DefaultDepth 8 Subsection "Display" Depth 8 Modes "800x600" "640x480" EndSubsection EndSection Section "DRI" Mode 0666 EndSection

lets do the following: first check if the driver module is loaded: dmesg | grep S3 if it is loaded, you should see, S3: loading S3 86C775 (Trio64V2/DX) Kernel Module $(Date 0f loading) if you see this, your module is loaded; but something is stopping it from proper functioning.. change your driver to generic "vesa" driver (first take a backup of your XF86config, then replace S3 with vesa) and do a startx and see if it is working. if you don't see this dmesg response, your module is not loaded into the kernel. findout if the module is existing by rpm -q S3 or modprobe -l | grep S3 if it is not found, you have to download driver for your video card and install it. if you find it here, but not in dmesg | grep S3, you got the module but is not loaded. you have to use modprobe -a S3 to load all related modules.