configuring Xfree86?

bigpoppapumpg

Member
Oct 8, 2003
46
0
0
as the root user, when you shell configure xfree86 on freebsd with xf86config, after I'm done I save the config file to the default location. then when I try to start it with startx, it gives me this message. Am i saving the config file to the wrong location? I'm running this in microsoft virtualpc 2004, where it says video cards are not recognized as native devices... so i'm not sure if that is the source of my problem or not.



Build Operating System: FreeBSD 5.2 i386 [ELF]
Build Date: 07 December 2003
Before reporting problems, check http://www.XFree86.Org/
to make sure that you have the latest version.
Module Loader present
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: Wed Feb 4 12:13:42 2004
(==) Using config file: "/root/XF86Config"
(EE) No devices detected.

Fatal server error:
no screens found

When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file "/var/log/XFree86.0.log".
Please report problems to xfree86@xfree86.org.

X connection to :0.0 broken (explicit kill or server shutdown).
xauth: creating new authority file /root/.Xauthority
xauth: (argv):1: bad display name ":0" in "remove" command
xauth: (argv):1: bad display name ":0" in "remove" command
 

n0cmonkey

Elite Member
Jun 10, 2001
42,936
1
0
The config you are using is in /root/XF86Config. It should probably be in /etc/X11, but as long as it is using the correct one that isn't a problem. I'd look into the "no screens found" error.
 

Crusty

Lifer
Sep 30, 2001
12,684
2
81
Open your config file and paste it here, along with relevant system info.
 

Barnaby W. Füi

Elite Member
Aug 14, 2001
12,343
0
0
"no screens found" is a generic error. Look in /var/log/XFree86.0.log for the real error(s).

edit: dear god, don't use xf86config. Try xf86cfg, then tweak the config it gives you to taste.
 

bigpoppapumpg

Member
Oct 8, 2003
46
0
0
Ok I think I know the problem. There seems to be 2 methods to configure X. the commands are as follows as the root user: sysinstall--->Config--->XFree86-->xf86cfg(fully graphical) or xf86config(shell-script based)

I used both methods just to see where it was saving the new config file.

With the xf86cfg method, here is where it stores the updated config file:

XF86Config write configuration: /usr/X11R6/lib/X11/XF86Config XKB Write configuration: /usr/X11R6/lib/X11/X0-config.keyboard

With the xf86config method:

write: /etc/X11/XF86Config

[in both configuration methods I choose modest resolutions, 16 bit color, driver 'nv', and in the fully graphical tool I chose my geforce 4 ti4200 from a drop down list, in the shell config tool I choose 'GeForce' chipset]


NOW after I configured Xfree86 and KDE, this is the error message I get when I use 'startx', notice the line that says which config file X is attempting to use. It's the root config file, not the one I've been updating in the configuration routine. So all I have to do is figure out how to make X look at the correct config file right?

Build Operating System: FreeBSD 5.2 i386 [ELF]
Build Date: 07 December 2003
Before reporting problems, check http://www.XFree86.Org/
to make sure that you have the latest version.
Module Loader present
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: Thu Feb 5 16:09:21 2004
(==) Using config file: "/root/XF86Config"
(EE) No devices detected.

Fatal server error:
no screens found

When reporting a problem related to a server crash, please send
the full server output, not juÐÑ the last messages.
This can be found in the log fÒÓe "/var/log/XFree86.0.log".
Please report problems to xfree86@xfree86.org.

X connection to :0.0 broken (explicit kill or server shutdown).
xauth: creating new authority file /root/.Xauthority
xauth: (argv):1: bad display name ":0" in "remove" command
xauth: (argv):1: bad display name ":0" in "remove" command


----------------------------------------------------------------------
I also tried copying the XF86Config I create from /usr/X11R6/lib/X11/ to the /root. However when I 'startx', it still seems to be using the generic template file, not the properly configured file. This is the contents of /usr/X11R6/lib/X11/ directory, would any of them tell me what's going wrong? They seem to be very long files, so im not sure I could copy and paste them.:


# ls
Cards XF86Setup fonts rstart xkb
Options XKeysymDB fs twm xman.help
XErrorDB Xcms.txt icons x11perfcomp xserver
XF86Config app-defaults lbxproxy xanim xsm
XF86Config.98 config locale xdm
XF86Config.eg doc proxymngr xedit
 

bigpoppapumpg

Member
Oct 8, 2003
46
0
0
Originally posted by: n0cmonkey
Try putting a config in /etc/X11



I did, using the xf86config method it writes to this location:

/etc/X11/XF86Config


I'm running freebsd in windows virtual environment with M$ virtual pc 2004. the documentation for that says it doesn't recognize agp video cards as native devices, whatever that means. I noticed on my Suse 9.0 Live eval bootable cd, the device manager sees the video card as a generic S3 chipset. I actually have a Geforce 4 installed. Perhaps when I configure XFree86 by specifying Nvidia geforce 4 graphic card, I should instead choose S3?
 

bigpoppapumpg

Member
Oct 8, 2003
46
0
0
Lol this is how I got it to work.


# /usr/X11R6/bin/xf86config
- run the X configuration utility

it wrote the new config file using an S3 video adapter to this location: /etc/X11/XF86Config


Then I copied that config file to /root and startx worked. It started right into KDE which I had previously set as the default. I think it was me choosing S3 instead of nvidia Geforce4 that made it work. I will mess around with it to make sure its working ok, but looks like it was the virtual environment that messed things up.