• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

RH9 X setup issue

slag

Lifer
originally posted over in tech support, it makes better sense to be here.

installed redhat 9 on my box awhile ago and today i wanted to swap out the s3 pci card for an agp geforce 2 card.

I looked at redhat.com and they said to just do the swap and then run xf86config.

Well, that doesnt work.

What do I need to do --is there some sort of re-setup utility i can run?

How do i get my desktop back.

Thanks


 
xf86config, unless RH9 swapped it for something else, is a pretty ancient tool that's missing lots of data. Log in as root, type redhat-config- and hit Tab - that will show you all the RH config tools. You want the -xfree86 or -display tool - I don't remember the exact name. That should do a better job than xf86config. If that doesn't work, post the error that you get from X along with the contents of your /etc/X11/XF86Config file.
 
To be more specific:
Type redhat-config- (Those are dashes if it's unclear)
Do not press enter
Hit the Tab key
You will see a list of command completions
Complete the command appropriately
 
redhat-config-kickstart redhat-config-packages
redhat-config-network redhat-config-printer
redhat-config-network-cmd redhat-config-printer-gui
redhat-config-network-druid redhat-config-printer-tui
redhat-config-network-gui redhat-config-proc
redhat-config-network-tui redhat-config-services


there are no display configs
 
This is interesting.. last sunday someone i know had a similar problem w/ RH 9.0. Except that I havent used RH since ver. 6.2 🙂 (in other words, I havent used it for a really long time..)
I think the RH installation cd has a redhat-config for xfree. I cannot really tell you the exact name of the package but you should try in CD1
 
Looked it up - should be redhat-config-xfree86. Don't know why it's not there, but whatever... Post your XF86Config file and we'll sort it out.
 
Section "Device"
Identifier "Videocard0"
Driver "s3"
VendorName "Videocard vendor"
BoardName "S3 Trio64 (generic)"
VideoRam 4096
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 16
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection
 
when it fails to work when you type "startx", what is exactly the error it gives you?

All X stuff is logged, so if you go into the /var/log directory there will probably be a XF86config.log of some sort. You can see the errors there if that's easier for you.

 
XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2)
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.20-3bigmem i686 [ELF]
Build Date: 27 February 2003
Build Host: porky.devel.redhat.com

Before reporting problems, check http://www.XFree86.Org/
to make sure that you have the latest version.
Module Loader present
OS Kernel: Linux version 2.4.20-20.9 (bhcompile@porky.devel.redhat.com) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Mon Aug 18 11:27:43 EDT 2003
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Fri Oct 3 08:22:40 2003
(==) Using config file: "/etc/X11/XF86Config"


(EE) No devices detected.

Fatal server error:
no screens found
 
Replace this:

Section "Device"
Identifier "Videocard0"
Driver "s3"
VendorName "Videocard vendor"
BoardName "S3 Trio64 (generic)"
VideoRam 4096
EndSection

With:

Section "Device"
Identifier "Videocard0"
Driver "nv"
VendorName "NVidia"
BoardName "Geforce 2"
EndSection
 
actually, with the help of some guys at work, we got it figured out.

There was a connector package that my machine did not have for some reason.. we scp'd it across my ssh tunnel and rpm'd it. Then things started working ok.

Thanks all!!

 
Back
Top