I finally got my Display res wkng on my HP-800x600 @ 60hz monitor for my JAMD OS (another RH spin off). All 5 linux distros are working on the HP monitor now. I just got a new monitor for Christmas (a Liquidvideo 15" flat tft-lcd, model: A150X1, 1024x768/XGA, 16million colors). When I hooked it up, the mandrake, suse, and debian worked fine. The red hat and jamd did not. I got the RH wkng by editing the XF86Config with a GUI txt editor while it was hooked up to the HP. The hooked it back up to the Liquidvideo and it wkd fine with the new monitor. I tried the same thing with the JAMD, but it didn't work. After editing the XF86Config file, I couldnt get to the display on either monitor. So while it was hooked up to the HP, I ran XFree86 -configure to create a new XF86Config file with i used to replace the old one. Now I can get to the GUI on the HP but still cant get to the GUI on the new monitor, so I tried that command again with the new monitor attached but it didnt wk the second time....does anyone know why and how to get it to work? The message I get now when I type "XFree86 -configure" is:

"Fatal server error:
Server is already active for display 0
IF theis server is no longer running, remove /tmp/.X0-lock and start again.

When reporting a problem related to a server crash, please send
the full server output, not just the last message.
Please report problems to xfree86@xfree86.org"

I once had the exact same problem with the RH on the HP monitor. I was never able to fix it or figure out why that happened the second time I ran that cmd. I was able to get the display wkng by manually editing for the RH, but that is not working for the JAMD.

Can any one help?

-Rob











Terrene Bell

First things first, find the refresh rate for your new monitor. Then delete that file. It shouldnt hurt anything.

Good Luck!!!
Thad Blankenship

Well the message I get is :

"Out of Range
H: +53.7khz
V: +85.0hz

Range
H: 28-65
V: 56-78hz
max 1024x768"


Delete what file?

"First things first, find the refresh rate for your new monitor."

When I boot into JAMD with the new monitor attached I get the following message from the monitor:

"Out of Range
H: +53.7khz
V: +85.0hz

Range
H: 28-65
V: 56-78hz
max 1024x768"


"Then delete that file. It shouldnt hurt anything."

I dont understand? What file? and when I delete it, what then?

-Rob

"Then delete that file. It shouldnt hurt anything."

I guess you meant the:
/tmp/.X0-lock file?

Well I deleted the file (/tmp/.X0-lock file) and nothing happened! After deleting it I rebooted then tried the command "XFree -configure" and got the exact same message as above. Why does that cmd only work once!? ...and whaat should I try next??

I have a question (sorry no answers) to any one who as configured XFree86 to work with the LiquidVideo E17LCD1 XJ17 . I am posting this here because I think from the sounds of it people have had some sucess. What are the monitor settings you are using in XFree?

hsync=31-38

Vrefresh=28-60

display 1024-768 or 800x600@60hz...

cant remember. im not booted into it @ the moment.
I will check tomorrow.

You will likely have to restart you computer after this but here goes as this is what I did to get my LiquidVideo 17" E17LCD1 to work:

If X has started (it will be runing automatically run level 5) then try ALT+CTRL+BKSPC. This may kill you X server unless gdn is running as it is on my machine.

Check at the prompt to ensure it is stoped

To Check

ps aux | grep X

You may see
root 1024 3.9 9.8 26996 12380 ? S< 23:31 0:32 /usr/X11R6/bin/X
root 1256 0.0 0.4 3276 624 pts/0 S 23:45 0:00 grep X

The /usr/X11R6/bin/X line with pid 1024 means it is still running. If you don't see this then you are fine.

Killing /usr/X11R6/bin/X with a command kill 1024 won't do the trick as gdm will restart it.

To kill gdm (if any one has a better idea I would like to here it ) do the following

pstree -p | more

look for a line like the follwoing:

|-gdm-binary(978)---gdm-binary(1023)-+-X(1024)
| `-gnome-session(1033)---ssh-agent(1

See the gdm-binary(1023) ... thats what we are looking for.

kill 1023

or whatever process id is gdm on your system!!!

Now X should be dead. If not ALT+CTRL+F7 and wait a sec then ALT+CTRL+BKSPACE

Now X should be dead

ALT+CTRL+F1 to the terminal

Now your can edit your X86Config file in /etc/X11/X86Config.

Do not edit /etc/XF86Config as the startup scripts copy it from /etc/X11 to /etc to protect the original file.

startx when you want to try it out and ALT+CTRL+BKSPACE when you want to kill X. And retry your hand at a X66Config file.

The problem you are likely having is that X was running while you were editing the files. When you called startx it was complaining about a copy of X running display 0 "Server is already active for display 0"

I had some of the same issues as you. I belive mine centered around the video card memroy and the refresh rates of the monitor. I put a floor and celing on my vert and horiz refreshrates based on the owners manual (last page). Yep there are people who read thoes things.

Below is my XFree86 file for anyone who is interested. It configs a ATI 3D Rage Pro driving a LiquidVideo E17LCD1. It pushes 1280X1024 at 16 million looks great.



# 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.
# 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 "dri"
Load "glx"
Load "record"
Load "freetype"
Load "type1"
EndSection

Section "InputDevice"
# 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 "XkbOptions" ""
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "us" #Option "XkbVariant" ""
EndSection

Section "InputDevice"
# Modified by mouseconfig
Identifier "Mouse0"
Driver "mouse"
Option "Device" "/dev/mouse"
Option "Protocol" "IMPS/2"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
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 31.0 - 80.0
VertRefresh 60.0 - 75.0
Option "dpms"
EndSection

Section "Device"
# no known options
#BusID
Identifier "ATI Mach64"
Driver "ati"
VendorName "ATI Mach64"
BoardName "ATI Mach64"
EndSection

Section "Screen"
Identifier "Screen0"
Device "ATI Mach64"
Monitor "Monitor0"
DefaultDepth 16
SubSection "Display"
Depth 16
Modes "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "DRI"
Mode 0666
EndSection