asked on

Redhat 9.0 X86Config not working with Samsung 192N LCD

I recently upgraded my monitor from an IBM 19" CRT to a Samsung 192N LCD. When I booted up my Linux machine (IBM 8315) the machine went through the start up process fine until it tried to start the graphics process. At that point the machine shows a "Video Mode Not Supported" image on the screen and the machine hangs at that point. The driver is an I810 and the video card is a I845. I tried to start with a clean install, and had to go into Linux-textmode because the Linux-graphics mode would give the not supported message as well. At the completion of the install, the Xconfigurator seems to identify the monitor at that point , but at boot up it states it is having problems and the not supported message appears again. I have been trying to figure this out for a couple weeks now and have not had any success.

I do use a Belkin KVM switch to share this monitor across a couple Windows machines, and they have no issues with the monitor.

jlevie

What I'd try at this point is to bring the system up to date w/respect to the RH 9 errata (as in running up2date). Included in the errata is a updated version of X which might help with this problem. I'd also try running redhat-config-xfree86 and select one of the Generic Monitor types rather than the "correct" one for the monitor. You might also try some of the Generic Laptop types.

sr5v6

ASKER

When I run the redhat-config-xfree86 I get the "Video mode not supported" and have to reboot. I have dropped into an init level 3 to stop the X-windows from starting for the same reason, once I get that message I am unable to break out unless I power the machine down.

jlevie

Have you brought the system up2date yet?

What you might rry is to connect an ordinary monitor, run redhat-config-xfree86 and select a fairly safe mode from the generics, say 1024x768, and then re-connect the LCD.

Gns

Could you quote the relevant Monitor section from the /etc/X11/XF86Config file here? Sounds to me like you get some wrong refreshrates.

-- Glenn

Gns

You should verify that they are 30-81 Horizontal and 56-85 vertical ... According to the product manual:-)

-- Glenn

sr5v6

ASKER

I have copied the entire XF86Config file into the entry.
========================================

# XFree86 4 configuration created by pyxf86config

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" "PS/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 "DDCPROBED"
      DisplaySize 380      310
      HorizSync 30.0 - 81.0
      VertRefresh 56.0 - 85.0
      Option        "dpms"
EndSection

Section "Device"
      Identifier "Videocard0"
      Driver "i810"
      VendorName "Videocard vendor"
      BoardName "Intel 845"
EndSection

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

Section "DRI"
      Group 0
      Mode 0666
EndSection

ASKER CERTIFIED SOLUTION

jlevie

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Gns

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

sr5v6

ASKER

Folks, thank very much for your help. I took Glenn's suggestion and tried that first and when I started X I received an error stating modes unknown. I commented out the items and went with JLevie's recomendation alone and I when I started X again I got a X item in the middle of the screen and then the screen went black, but it was progress. So I then went back to Glenn's suggestion and took off the "@xx" parameters and started X and it came up fine !!!!

So without the two ideas, I would not of tried the various combinations, thus an award of split points. Thanks so much for your help, this has been a problem plagueing me for two weeks and countless hours of me looking high and low for a solution.

Gns

The point of the @Hz is to make them different from the "autoprobed names"... Should've worked, but you could perhaps have used something else... "my1280x1024" ...:-).

Glad that it works though.

-- Glenn