[lug] Problems with X 4.0.3

D. Stimits stimits at idcomm.com
Thu Apr 5 11:21:20 MDT 2001


I'm going give some comments intermixed in there, but it isn't a final
answer; about all I can do is give you clues on how to search. It might
be useful to see the output of "lspci -v" and "cat /proc/pci".

Dhruva Reddy wrote:
> 
> I just bought a Hercules Prophet II MX AGP video card,
> and am trying to get it to work on Debian box.
> 
> According to the documentation for the GeForce2 MB
> chipset, a 4.0 X server is required.  Since Debian has
> not yet packaged the 4.0 SVGA X server, I downloaded
> the source and built it.  It seemed to build and
> install OK, but it does not seem to run.  I get an
> error "could not open default font 'fixed'".  Could
> this have to do with xfs?  Or is it that I don't have
> the font installed correctly?
> 
> I have included the log file, as well as my XF86Config
> file.
> 
> Any help would be greatly appreciated!
> 
> Thanks,
> Dhruva
> 
> LOG FILE:
> 
> XFree86 Version 4.0.3 / X Window System
> (protocol Version 11, revision 0, vendor release 6400)
> Release Date: 16 March 2001
...


> (II) LoadModule: "glx"
> (II) Loading
> /usr/X11R6/lib/modules/extensions/libglx.so
> (II) Module glx: vendor="NVIDIA Corporation"
>         compiled for 4.0.2, module version = 1.0.769
>         Module class: XFree86 Server Extension
>         ABI class: XFree86 Server Extension, version 0.1

According to this, you are using the 4.0.2 module, but your server is
4.0.3. I don't know if this will be the cause of any problems or not
(unlikely the font problem, but it may produce other problems when fonts
are working).

> (II) Loading extension GLX
....
> (II) LoadModule: "type1"
> (II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a
> (II) Module type1: vendor="The XFree86 Project"
>         compiled for 4.0.3, module version = 1.0.0
>         Module class: XFree86 Font Renderer
>         ABI class: XFree86 Font Renderer, version 0.2
> (II) Loading font Type1
> (II) Loading font CID
> (II) LoadModule: "freetype"
> (II) Loading
> /usr/X11R6/lib/modules/fonts/libfreetype.a
> (II) Module freetype: vendor="The XFree86 Project"
>         compiled for 4.0.3, module version = 1.1.9
>         Module class: XFree86 Font Renderer
>         ABI class: XFree86 Font Renderer, version 0.2
> (II) Loading font FreeType
> (II) LoadModule: "nvidia"

The hardware accel version of the nvidia module loaded without error.

> (II) Loading
> /usr/X11R6/lib/modules/drivers/nvidia_drv.o
> (II) Module nvidia: vendor="NVIDIA Corporation"
>         compiled for 4.0.2, module version = 1.0.769
>         Module class: XFree86 Video Driver
>         ABI class: XFree86 Video Driver, version 0.3
....
> (II) NVIDIA(0): Processing requested modes for monitor
> 0
> (II) NVIDIA(0): MyMonitor: Using hsync range of
> 31.00-82.00 kHz
> (II) NVIDIA(0): MyMonitor: Using vrefresh range of
> 55.00-120.00 Hz
> (II) NVIDIA(0): Clock range:  12.00 to 300.00 MHz

Next you'll see many of your monitor modelines are rejected (they exceed
card or monitor specs):

> (WW) NVIDIA(0): Default mode "1280x960" deleted (hsync
> out of range)
> (WW) NVIDIA(0): Default mode "1280x1024" deleted
> (hsync out of range)
> (WW) NVIDIA(0): Default mode "1600x1200" deleted
> (hsync out of range)
> (WW) NVIDIA(0): Default mode "1600x1200" deleted
> (hsync out of range)
> (WW) NVIDIA(0): Default mode "1600x1200" deleted
> (hsync out of range)
> (WW) NVIDIA(0): Default mode "1792x1344" deleted
> (hsync out of range)
> (WW) NVIDIA(0): Default mode "1792x1344" deleted
> (hsync out of range)
> (WW) NVIDIA(0): Default mode "1856x1392" deleted
> (hsync out of range)
> (WW) NVIDIA(0): Default mode "1856x1392" deleted
> (hsync out of range)
> (WW) NVIDIA(0): Default mode "1920x1440" deleted
> (hsync out of range)
> (WW) NVIDIA(0): Default mode "1920x1440" deleted
> (hsync out of range)

Next you'll see several modes are accepted, so you do have ranges that
work:

> (--) NVIDIA(0): Virtual size is 1280x1024 (pitch 1280)
> (**) NVIDIA(0): Default mode "1280x1024": 135.0 MHz,
> 80.0 kHz, 75.0 Hz
> (**) NVIDIA(0): Default mode "1024x768": 94.5 MHz,
> 68.7 kHz, 85.0 Hz
> (**) NVIDIA(0): Default mode "800x600": 56.3 MHz, 53.7
> kHz, 85.1 Hz
> (**) NVIDIA(0): Default mode "640x480": 36.0 MHz, 43.3
> kHz, 85.0 Hz
> (II) NVIDIA(0): Applying EDID constraints on remaining
> valid modes.
> (II) NVIDIA(0): Virtual Screen size determined to be
> 1024 x 768
...

> Could not init font path element unix/:-1, removing
> from list!
> 
> Fatal server error:
> could not open default font 'fixed'

As you mentioned, it is failure of the default font that is causing
shutdown...

....
> CONFIG FILE:
> 
> ##########################################################################
> # Sample XF86Config file for NVIDIA XFree86 drivers.
> #
> # Refer to the XF86Config(4/5) man page for details
> about the format of
> # this file.
> #
> # Be sure to replace the monitor values with correct
> values for your
> # monitor!
> ##########################################################################
> 
> Section "Files"
> 
>     RgbPath     "/usr/X11R6/lib/X11/rgb"

"unix/:-1" means you are using the font server instead of explicit font
paths. The font server is a network protocol, so if networking is
refused by security setup, or otherwise misconfigured (e.g., it uses a
host name instead of dotted-decimal format and host name lookup fails),
the font server will fail.

Also, the font server has become more integrated in 4.x than 3.x; this
means your /etc/rc.d/init.d/xfs script just might be using the wrong xfs
or arguments. Be certain that you are using the xfs that comes with
4.0.3 and not 3.x. On my RH 7.1 beta machine, running 4.0.2, I get this
from "ps aux | grep xfs":
..........xfs -drppriv -da

Does your xfs have arguments "-drppriv -da"? If not, it might be using
the wrong script to start.

>     FontPath   "unix/:-1"
> 
> EndSection
....
> ##########################################################################
> # Graphics device section(s)
> ##########################################################################
> 
> Section "Device"
>     Identifier  "NV AGP"
>     VendorName  "nvidia"
>     Driver   "nvidia"
>     # update this with the PCI id of your card.
> Consult the output
>     # of the 'lspci' command.
>     BusID       "PCI:1:0:0"

Here BusID lists PCI bus one, device 0, function 0, as containing a
video card. A bit of explanation is in order here on this naming. AGP
slots are actually higher performance dedicated PCI slots, so /proc/pci
contents and "lspci -v" will list AGP cards (this is also why AGP will
function without AGP support...it is still ordinary PCI till AGP
features are enabled). There are several PCI busses within any modern
motherboard, usually one bus will connect to several PCI cards or
devices, sharing the bus (many of those devices are not add-on cards,
but integrated parts of the motherboard, e.g., integrated ethernet
cards, PCI bridges, so on). Those busses are numbered starting at 0.
Each PCI add-on card will have at least one function, but can have more.
A sample of multifunction cards would be a sound cards that also have a
game port and midi port; the sound hardware will be the first function
(function 0) of the device, and then there will be functions 1 and 2 of
the same device for game port and midi ports (each function is an
independent piece of hardware in a single PCI add-on card).

So for this example: "PCI:0:1:2"...

...it names electrical bus 0, device 1 on that bus (probably a
particular slot of the add-on card plugged into the motherboard), and it
is function 2 on the card (the 3rd independent piece of hardware on that
card, since it starts numbering at 0, perhaps a game port on a sound
card).

Your AGP card has twinview, so it complicates things. Ordinary video
cards without special addons (e.g., only one video connector, no other
connectors, and no internal frills like television or radio tuners)
would have only one BusID to worry about; on the AGP bus would be *only*
device 0 and function 0. Could you post a copy of /proc/pci, as well as
the output of "lspci -v"? It's really hard to say whether your "Device"
sections are pointed at the right hardware without it (it might be
difficult anyway).

D. Stimits, stimits at idcomm.com



More information about the LUG mailing list