Still can't get X font server problem resolved.
I am still unable to resolve the problems with getting X to run on my newly installed SuSE 9.0 system. The system is an AMD700MHz on an Asus board with an Nvidia Geoforce 440 MX with 64 MB of video memory. I just noticed that the XFree86.log file shows this: (--) PCI:*(0:12:0) nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] rev 162, Mem @ 0xd9000000/24, 0xdc000000/26, BIOS @ 0x000c0000/17 which seems to indicate an AGP card when actually it is a PCI card. The problem that I am seeing is that when I try to start X, I get the following: Could not init font path element /usr/X11R6/lib/X11/fonts/local, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/kwintv, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID, removing from list! So, I googled and found that this is related to the xfs server not being able to start. When I try to start it manually, I get: xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/100dpi:unscaled (unreadable) xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/japanese:unscaled (unreadable) xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/baekmuk:unscaled (unreadable) xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/CID (unreadable)xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/PEX (unreadable)xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/cyrillic (unreadable) xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/latin2/misc (unreadable) xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/latin2/75dpi (unreadable) xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/latin2/100dpi (unreadable) xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/latin2/Type1 (unreadable) xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/latin7/75dpi (unreadable) xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/kwintv (unreadable) -------------- If I can't resolve this, I will have to switch back to RedHat or maybe to Slackware. I have been trying to solve this problem for a week now. I solved part of it by downloading and installing the new NVidia drivers, but I am left with this path thing. Anybody got a clue about how to solve this? --vicki
<snip>
Could not init font path element /usr/X11R6/lib/X11/fonts/local, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/kwintv, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID, removing from list!
Does the server start? I am a bit confused.
So, I googled and found that this is related to the xfs server not being able to start. When I try to start it manually, I get:
Why? I thought that the X server didn't need this anymore. I may be wrong though.
xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/100dpi:unscaled (unreadable) xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/japanese:unscaled (unreadable) xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/baekmuk:unscaled (unreadable) xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/CID (unreadable)xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/PEX (unreadable)xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/cyrillic (unreadable) xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/latin2/misc (unreadable) xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/latin2/75dpi (unreadable) xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/latin2/100dpi (unreadable) xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/latin2/Type1 (unreadable) xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/latin7/75dpi (unreadable) xfs notice: ignoring font path element /usr/X11R6/lib/X11/fonts/kwintv (unreadable)
Well if the X server starts, then I would not worry about it too much. One possible reason for these error messages is that the X server cannot find the fonts listed in the directories. Whether the permissions are wrong or they are not existant. You can either remove the paths in the XF86Config file or you can install the fonts that are missing amd be sure to run SuSEconfig --module fonts afterwards as root. Yast will do this for you automatically.
If I can't resolve this, I will have to switch back to RedHat or maybe to Slackware. I have been trying to solve this problem for a week now. I solved part of it by downloading and installing the new NVidia drivers, but I am left with this path thing. Anybody got a clue about how to solve this?
Well ther are a few suggestions above. Try them and see if the situation gets any better. Marshall
On Wed, Apr 28, 2004 at 09:18:10PM -0400, Marshall Heartley wrote:
<snip>
Could not init font path element /usr/X11R6/lib/X11/fonts/local, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/kwintv, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID, removing from list!
Does the server start? I am a bit confused. No, X won't start so I am assuming the font server doesn't start. Well if the X server starts, then I would not worry about it too much. One possible reason for these error messages is that the X server cannot find the fonts listed in the directories. I looked and the directories exist and the permissions look right. Anyway it doesn't work for root either. I don't know what files are supposed to be in these directories though. If I knew a font package name, I might be able to (re)install the rpm.
Whether the permissions are wrong or they are not existant. You can either remove the paths in the XF86Config file or you can install the fonts that are missing amd be sure to run SuSEconfig --module fonts afterwards as root. Yast will do this for you automatically. I have run Yast2 several times. Everything looks fine within Yast, but when I leave it and try to start X, it is the same problem.
Thanks for trying though, --vicki
No, X won't start so I am assuming the font server doesn't start.
OK. Is the font errors the only ones that you see? Are there others?
I looked and the directories exist and the permissions look right. Anyway it doesn't work for root either. I don't know what files are supposed to be in these directories though. If I knew a font package name, I might be able to (re)install the rpm.
There are several .rpms that are available. Look around in YaST. I find quite a few of them.
I have run Yast2 several times. Everything looks fine within Yast, but when I leave it and try to start X, it is the same problem.
Make sure that you are in runlevel 3 and execute this command "sax2 -m 0=nvidia" all on one line and without the quotes. This will tell SaX2 to use the nvidia module for that video card. Be sure to test the card configuration by chooding the option in SaX2. I do agree with the other poster that this is weird that your card that is PCI is reporting that it is an AGP card. Did this card work before? Or is this a new setup that you are trying to get running?
Thanks for trying though,
Welcome. Marshall
Hi! I'm new to SuSE (9.0 Pro) and i know this question might've been answered zillions of times though as i'm new to all this SuSE differences (which 'till now i love). My problem is that i want to add some other media sources in this case an FTP mirror to grab the baseic packages. and src.rpm's too. But i tried every whcih way possible but no use. How could i add Eg: ftp.suse.com/pub/suse/i386/9.0 to my "Change Installation Source" Server name: ftp.suse.com Server path: /pub/suse/i386/9.0 i've tried everything. Would anyone give me some help, please?. Thanks a lot gurus. -- Best regards, David mailto:test@tuxcafe.com
On 28/4/2004 22:41, Vicki Stanfield wrote:
I am still unable to resolve the problems with getting X to run on my newly installed SuSE 9.0 system. The system is an AMD700MHz on an Asus board with an Nvidia Geoforce 440 MX with 64 MB of video memory. I just noticed that the XFree86.log file shows this:
(--) PCI:*(0:12:0) nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] rev 162, Mem @ 0xd9000000/24, 0xdc000000/26, BIOS @ 0x000c0000/17
I think the line above is your problem. With a PCI card also, my corresponding line reads (--) PCI:*(0:13:0) nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] rev 21, Mem @ 0xcf000000/24, 0xca000000/25, BIOS @ 0xceff0000/16 No mention of AGP. I presume you configured with sax2? If so, try, as root, configuring with xf86config. Or, run /sbin/lspci and find the location of your card. I get 00:0d.0 VGA compatible controller: nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] (rev 15) Note that initial 00:0d:0. This is in hexadecimal but your XF86Config file needs to be in decimal. So, 00:0d:0 becomes 0:13:0 and the relevant part of my file reads Section "Device" BoardName "RIVA TNT2 Model 64" BusID "0:13:0" Driver "nvidia" Identifier "Device[0]" Screen 0 Option "Rotate" "off" VendorName "NVidia" EndSection See p75 et seq of the Admin Guide for more info.
which seems to indicate an AGP card when actually it is a PCI card. The problem that I am seeing is that when I try to start X, I get the following:
<snip> The font "errors" are unimportant. You can ignore those messages or remove the paths from XF86Config. -- Vic Ayres
On Thu, Apr 29, 2004 at 09:05:08AM +0100, Vic Ayres wrote:
On 28/4/2004 22:41, Vicki Stanfield wrote:
I am still unable to resolve the problems with getting X to run on my newly installed SuSE 9.0 system. The system is an AMD700MHz on an Asus board with an Nvidia Geoforce 440 MX with 64 MB of video memory. I just noticed that the XFree86.log file shows this:
(--) PCI:*(0:12:0) nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] rev 162, Mem @ 0xd9000000/24, 0xdc000000/26, BIOS @ 0x000c0000/17
I think the line above is your problem. With a PCI card also, my corresponding line reads (--) PCI:*(0:13:0) nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] rev 21, Mem @ 0xcf000000/24, 0xca000000/25, BIOS @ 0xceff0000/16 No mention of AGP.
I presume you configured with sax2? If so, try, as root, configuring with xf86config. Yes, I configured with sax2. As soon as I exit it and try to start X with the resulting config file, it won't work. I checked with lspci and saw that mine comes back as the equivalent to 0:12:0 which is what my config file says. For what it is worth, when I switch drives and put back my old RedHat 9.0 install, it works fine. Of course the XF86Config file for that system doesn't include the bus line. I will try to reconfig using xf86config when I get home tonight.
--vicki
On Thu, Apr 29, 2004 at 10:49:08AM -0500, Vicki Stanfield wrote:
On Thu, Apr 29, 2004 at 09:05:08AM +0100, Vic Ayres wrote:
On 28/4/2004 22:41, Vicki Stanfield wrote:
I am still unable to resolve the problems with getting X to run on my newly installed SuSE 9.0 system. The system is an AMD700MHz on an Asus board with an Nvidia Geoforce 440 MX with 64 MB of video memory. I just noticed that the XFree86.log file shows this:
(--) PCI:*(0:12:0) nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] rev 162, Mem @ 0xd9000000/24, 0xdc000000/26, BIOS @ 0x000c0000/17
I think the line above is your problem. With a PCI card also, my corresponding line reads (--) PCI:*(0:13:0) nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] rev 21, Mem @ 0xcf000000/24, 0xca000000/25, BIOS @ 0xceff0000/16 No mention of AGP.
I presume you configured with sax2? If so, try, as root, configuring with xf86config. Well, xf86config made no difference. I am hosed. I get to put my new Linux box together this weekend, and I think I have to go with Slackware. I will, however, pop the SuSE 9.0 harddrive in it and rerun Yast2 to set up X just to see if it works. It will have the same nVidia card and the same monitor, so it might be interesting to see if it works with different motherboard and memory. Just doing it for kicks really.
--vicki
participants (4)
-
David Gonzalez -
Marshall Heartley -
Vic Ayres -
Vicki Stanfield