Re: X problem after update from REX to BO (detailed error messages now)
On Fri, 26 Sep 1997, Lawrence wrote: Thank for your info. and yes the server compiled with a default font paths. By the way, I can still run startx with the following FontPath, and don't know you said your won't work? FontPath tcp/localhost:7100 FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/Type1/ FontPath /usr/X11R6/lib/X11/fonts/Speedo/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/100dpi/ You can use this FontPath. However if xfs is running it will provide all of the fonts to the server so only the tcp/localhost:7100 line is really used. And if xfs is not running, the X server will crash when it tries to contact the nonexistant font server. So, in short: yes you can use it, but this FontPat has no advantage compared to the single line FontPath tcp/localhost:7100 Remco -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
I tried to comment out ALL FontPath and I can't still run startx, though the Font looks bad, xfs not running and the following commands give error. I am using xsvga, does it has a VERY default font! fsinfo -server localhost:7100 fslsfonts -server localhost:7100 Remco Blaakmeer wrote: On Fri, 26 Sep 1997, Lawrence wrote: If I put 'FontPath tcp/localhost:7100' the very first line and follow by others font paths, do you think the X server will try to use the xfs, if fails it uses the others. Hmm, interesting thought. I'll try it. -- wait some time -- No, it doesn't work. With this in XF86Config: FontPath tcp/localhost:7100 FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/Type1/ FontPath /usr/X11R6/lib/X11/fonts/Speedo/ and xfs not running, I get: [all normal messages] (**) FontPath set to tcp/localhost:7100,/usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/75dpi/, /usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/ [more normal messages] _FontTransSocketINETConnect: Can't connect: errno = 111 failed to set default font path 'tcp/localhost:7100,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled, /usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/' Fatal server error: could not open default font 'fixed' So, it turns out your suggestion doesn't work here. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
sorry, my previous post have some typo errors, here is the correct one. I tried to comment out ALL FontPath and I CAN still run startx, though the Font looks bad, xfs not running and the following commands give error. I am using xsvga, does it has a VERY default font! fsinfo -server localhost:7100 fslsfonts -server localhost:7100 Why commenting out all FontPath and I can still run startx? Lawrence -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
On Fri, 26 Sep 1997, Lawrence wrote: sorry, my previous post have some typo errors, here is the correct one. I tried to comment out ALL FontPath and I CAN still run startx, though the Font looks bad, xfs not running and the following commands give error. I am using xsvga, does it has a VERY default font! fsinfo -server localhost:7100 fslsfonts -server localhost:7100 Why commenting out all FontPath and I can still run startx? Because of this (I tried it, too): $ X -probeonly [normal messages] Warning: No FontPath specified, using compiled-in default. Warning: The directory /usr/X11R6/lib/X11/fonts/100dpi/ does not exist. Entry deleted from font path. (--) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/, /usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/ [more normal messages] You see, if you don't say where the fonts are the X server tries to find them itself. Remco -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
Remco Blaakmeer wrote: On Fri, 26 Sep 1997, Lawrence wrote: sorry, my previous post have some typo errors, here is the correct one. I tried to comment out ALL FontPath and I CAN still run startx, though the Font looks bad, xfs not running and the following commands give error. I am using xsvga, does it has a VERY default font! fsinfo -server localhost:7100 fslsfonts -server localhost:7100 Why commenting out all FontPath and I can still run startx? Because of this (I tried it, too): $ X -probeonly [normal messages] Warning: No FontPath specified, using compiled-in default. Warning: The directory /usr/X11R6/lib/X11/fonts/100dpi/ does not exist. Entry deleted from font path. (--) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/, /usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/ [more normal messages] You see, if you don't say where the fonts are the X server tries to find them itself. Thank for your info. and yes the server compiled with a default font paths. By the way, I can still run startx with the following FontPath, and don't know you said your won't work? FontPath tcp/localhost:7100 FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/Type1/ FontPath /usr/X11R6/lib/X11/fonts/Speedo/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/100dpi/ Lawrence -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
According to Steve Hsieh [EMAIL PROTECTED]: I encountered the same problem. Doing a mkfontdir /usr/X11R6/lib/X11/fonts/* seems to fix the problem for Xfree servers; it still doesn't work after that for AcceleratedX though. Thanks a lot for the hint. Unfortunately it doesn't work for me. :-( I still get these error messages: (this time all of them) XFree86 Version 3.3 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: Jun 2 1997 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: Linux 2.0.21 i486 [ELF] Configured drivers: Mach64: accelerated server for ATI Mach64 graphics adaptors (Patchlevel 0) (using VT number 4) XF86Config: /etc/X11/XF86Config (**) stands for supplied, (--) stands for probed/default values (**) XKB: rules: xfree86 (**) XKB: model: pc102 (**) XKB: layout: de (**) XKB: variant: nodeadkeys (**) Mouse: type: MouseMan, device: /dev/mouse, baudrate: 1200 (**) Mach64: Graphics device ID: ATI Graphics Pro Turbo (**) Mach64: Monitor ID: MAG-MX17S (**) FontPath set to tcp/localhost:7100 (--) Mach64: PCI: Mach64 GX rev 3, Aperture @ 0xfa00, Sparse I/O @ 0x02ec (--) Mach64: card type: PCI (--) Mach64: Memory type: 5 (--) Mach64: Clock type: ATI18818-1/ICS2595 (--) Mach64: Maximum allowed dot-clock: 135.000 MHz (**) Mach64: Mode 1152x864: mode clock = 92.000 (**) Mach64: Mode 1024x768: mode clock = 85.000 (**) Mach64: Mode 800x600: mode clock = 50.000 (**) Mach64: Mode 640x480: mode clock = 31.500 (**) Mach64: Mode 1280x1024: mode clock = 80.000 (**) Mach64: Virtual resolution: 1280x1024 (--) Mach64: videoram: 4096k (--) Mach64: Using hardware cursor (--) Mach64: Using 8 MB aperture @ 0xfa00 (--) Mach64: Ramdac is ATI68860 Rev C (**) Mach64: Color weight: 565 (--) Mach64: Pixmap cache: 1 256x256 slots, 2 128x128 slots, 8 64x64 slots (--) Mach64: Font cache: 16 fonts Fatal server error: could not open default font 'fixed' When reporting a problem related to a server crash, please send the full server output, not just the last messages _X11TransSocketUNIXConnect: Can't connect: errno = 111 giving up. xinit: Connection refused (errno 111): unable to connect to X server xinit: No such process (errno 3): Server error. Please, please someone help me. It is so frustrating to work on the text console only. TALIA, Andy. Andy Spiegl, University of Technology, Muenchen, Germany E-Mail: [EMAIL PROTECTED] OR: [EMAIL PROTECTED] URL:http://www.appl-math.tu-muenchen.de/~spiegl PGP fingerprint: B8 48 24 7B DB 96 6F 1C D9 6D 8E 6C DB C2 E7 E9 o _ _ _ - __o __o /\_ _ \\o (_)\__/o (_) --- _`\,__`\,__(_) (_)/_\_| \ _|/' \/ -- (_)/ (_) (_)/ (_) (_)(_) (_)(_)' _\o_ ~~~ Andy Spiegl, University of Technology, Muenchen, Germany E-Mail: [EMAIL PROTECTED] OR: [EMAIL PROTECTED] URL:http://www.appl-math.tu-muenchen.de/~spiegl PGP fingerprint: B8 48 24 7B DB 96 6F 1C D9 6D 8E 6C DB C2 E7 E9 o _ _ _ - __o __o /\_ _ \\o (_)\__/o (_) --- _`\,__`\,__(_) (_)/_\_| \ _|/' \/ -- (_)/ (_) (_)/ (_) (_)(_) (_)(_)' _\o_ ~~~ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
Looks like you're missing the FontPath line(s) in the Files section of /etc/X11/XF86Config. Try man XF86Config. Andy Spiegl wrote: According to Steve Hsieh [EMAIL PROTECTED]: I encountered the same problem. Doing a mkfontdir /usr/X11R6/lib/X11/fonts/* seems to fix the problem for Xfree servers; it still doesn't work after that for AcceleratedX though. Thanks a lot for the hint. Unfortunately it doesn't work for me. :-( I still get these error messages: (this time all of them) XFree86 Version 3.3 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: Jun 2 1997 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: Linux 2.0.21 i486 [ELF] Configured drivers: Mach64: accelerated server for ATI Mach64 graphics adaptors (Patchlevel 0) (using VT number 4) XF86Config: /etc/X11/XF86Config (**) stands for supplied, (--) stands for probed/default values (**) XKB: rules: xfree86 (**) XKB: model: pc102 (**) XKB: layout: de (**) XKB: variant: nodeadkeys (**) Mouse: type: MouseMan, device: /dev/mouse, baudrate: 1200 (**) Mach64: Graphics device ID: ATI Graphics Pro Turbo (**) Mach64: Monitor ID: MAG-MX17S (**) FontPath set to tcp/localhost:7100 (--) Mach64: PCI: Mach64 GX rev 3, Aperture @ 0xfa00, Sparse I/O @ 0x02ec (--) Mach64: card type: PCI (--) Mach64: Memory type: 5 (--) Mach64: Clock type: ATI18818-1/ICS2595 (--) Mach64: Maximum allowed dot-clock: 135.000 MHz (**) Mach64: Mode 1152x864: mode clock = 92.000 (**) Mach64: Mode 1024x768: mode clock = 85.000 (**) Mach64: Mode 800x600: mode clock = 50.000 (**) Mach64: Mode 640x480: mode clock = 31.500 (**) Mach64: Mode 1280x1024: mode clock = 80.000 (**) Mach64: Virtual resolution: 1280x1024 (--) Mach64: videoram: 4096k (--) Mach64: Using hardware cursor (--) Mach64: Using 8 MB aperture @ 0xfa00 (--) Mach64: Ramdac is ATI68860 Rev C (**) Mach64: Color weight: 565 (--) Mach64: Pixmap cache: 1 256x256 slots, 2 128x128 slots, 8 64x64 slots (--) Mach64: Font cache: 16 fonts Fatal server error: could not open default font 'fixed' When reporting a problem related to a server crash, please send the full server output, not just the last messages _X11TransSocketUNIXConnect: Can't connect: errno = 111 giving up. xinit: Connection refused (errno 111): unable to connect to X server xinit: No such process (errno 3): Server error. Please, please someone help me. It is so frustrating to work on the text console only. TALIA, Andy. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
According to Bob Clark [EMAIL PROTECTED]: Looks like you're missing the FontPath line(s) in the Files section of /etc/X11/XF86Config. Try man XF86Config. You are right, I commented out the FontPath lines in XF86Config, but I am running xfs. Shouldn't that provide all the fonts? Thanks, Andy. Andy Spiegl, University of Technology, Muenchen, Germany E-Mail: [EMAIL PROTECTED] OR: [EMAIL PROTECTED] URL:http://www.appl-math.tu-muenchen.de/~spiegl PGP fingerprint: B8 48 24 7B DB 96 6F 1C D9 6D 8E 6C DB C2 E7 E9 o _ _ _ - __o __o /\_ _ \\o (_)\__/o (_) --- _`\,__`\,__(_) (_)/_\_| \ _|/' \/ -- (_)/ (_) (_)/ (_) (_)(_) (_)(_)' _\o_ ~~~ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
On 25 Sep 1997, Andy Spiegl wrote: According to Bob Clark [EMAIL PROTECTED]: Looks like you're missing the FontPath line(s) in the Files section of /etc/X11/XF86Config. Try man XF86Config. You are right, I commented out the FontPath lines in XF86Config, but I am running xfs. Shouldn't that provide all the fonts? You need to tell X to use the xfs server in your FontPath line then. Check the howtos for details. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
On Thu, 25 Sep 1997, Scott Ellis wrote: On 25 Sep 1997, Andy Spiegl wrote: According to Bob Clark [EMAIL PROTECTED]: Looks like you're missing the FontPath line(s) in the Files section of /etc/X11/XF86Config. Try man XF86Config. You are right, I commented out the FontPath lines in XF86Config, but I am running xfs. Shouldn't that provide all the fonts? You need to tell X to use the xfs server in your FontPath line then. Check the howtos for details. I took a look at the output of the X server in an earlier post and it already uses xfs for the fonts. But you have to configure xfs so that it looks in the right place for the fonts. Take a look at the 'catalogue' line in /etc/X11/xfs/config. You have to set this to exactly the set of font dirs that you have. Xfs is very unforgiving if you specify an unexisting or empty directory (dumps core on my computer). I encountered the same problem when I wanted to start using xfs for the fonts and found that I had to remove the '100dpi' directory from the 'catalogue' line. It now works fine for me. Remco -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
You didn't say (and I can't figure out from your error messages) whether or not you are using AcceleratedX. If so, you need to go into all of your font directories and gunzip the fonts, then ncompress them if you have it, then do the mkfontdir step. AcceleratedX can't do gzipped fonts, but it does understand compressed fonts. If this is your problem, I can forward you a message from Xi Graphics support that gives you the step by step details. Kevin On 25 Sep 1997, Andy Spiegl wrote: According to Steve Hsieh [EMAIL PROTECTED]: I encountered the same problem. Doing a mkfontdir /usr/X11R6/lib/X11/fonts/* seems to fix the problem for Xfree servers; it still doesn't work after that for AcceleratedX though. Thanks a lot for the hint. Unfortunately it doesn't work for me. :-( I still get these error messages: (this time all of them) XFree86 Version 3.3 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: Jun 2 1997 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: Linux 2.0.21 i486 [ELF] Configured drivers: Mach64: accelerated server for ATI Mach64 graphics adaptors (Patchlevel 0) (using VT number 4) XF86Config: /etc/X11/XF86Config (**) stands for supplied, (--) stands for probed/default values (**) XKB: rules: xfree86 (**) XKB: model: pc102 (**) XKB: layout: de (**) XKB: variant: nodeadkeys (**) Mouse: type: MouseMan, device: /dev/mouse, baudrate: 1200 (**) Mach64: Graphics device ID: ATI Graphics Pro Turbo (**) Mach64: Monitor ID: MAG-MX17S (**) FontPath set to tcp/localhost:7100 (--) Mach64: PCI: Mach64 GX rev 3, Aperture @ 0xfa00, Sparse I/O @ 0x02ec (--) Mach64: card type: PCI (--) Mach64: Memory type: 5 (--) Mach64: Clock type: ATI18818-1/ICS2595 (--) Mach64: Maximum allowed dot-clock: 135.000 MHz (**) Mach64: Mode 1152x864: mode clock = 92.000 (**) Mach64: Mode 1024x768: mode clock = 85.000 (**) Mach64: Mode 800x600: mode clock = 50.000 (**) Mach64: Mode 640x480: mode clock = 31.500 (**) Mach64: Mode 1280x1024: mode clock = 80.000 (**) Mach64: Virtual resolution: 1280x1024 (--) Mach64: videoram: 4096k (--) Mach64: Using hardware cursor (--) Mach64: Using 8 MB aperture @ 0xfa00 (--) Mach64: Ramdac is ATI68860 Rev C (**) Mach64: Color weight: 565 (--) Mach64: Pixmap cache: 1 256x256 slots, 2 128x128 slots, 8 64x64 slots (--) Mach64: Font cache: 16 fonts Fatal server error: could not open default font 'fixed' When reporting a problem related to a server crash, please send the full server output, not just the last messages _X11TransSocketUNIXConnect: Can't connect: errno = 111 giving up. xinit: Connection refused (errno 111): unable to connect to X server xinit: No such process (errno 3): Server error. Please, please someone help me. It is so frustrating to work on the text console only. TALIA, Andy. Andy Spiegl, University of Technology, Muenchen, Germany E-Mail: [EMAIL PROTECTED] OR: [EMAIL PROTECTED] URL:http://www.appl-math.tu-muenchen.de/~spiegl PGP fingerprint: B8 48 24 7B DB 96 6F 1C D9 6D 8E 6C DB C2 E7 E9 o _ _ _ - __o __o /\_ _ \\o (_)\__/o (_) --- _`\,__`\,__(_) (_)/_\_| \ _|/' \/ -- (_)/ (_) (_)/ (_) (_)(_) (_)(_)' _\o_ ~~~ Andy Spiegl, University of Technology, Muenchen, Germany E-Mail: [EMAIL PROTECTED] OR: [EMAIL PROTECTED] URL:http://www.appl-math.tu-muenchen.de/~spiegl PGP fingerprint: B8 48 24 7B DB 96 6F 1C D9 6D 8E 6C DB C2 E7 E9 o _ _ _ - __o __o /\_ _ \\o (_)\__/o (_) --- _`\,__`\,__(_) (_)/_\_| \ _|/' \/ -- (_)/ (_) (_)/ (_) (_)(_) (_)(_)' _\o_ ~~~ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
I took a look at the output of the X server in an earlier post and it already uses xfs for the fonts. But you have to configure xfs so that it looks in the right place for the fonts. Take a look at the 'catalogue' line in /etc/X11/xfs/config. You have to set this to exactly the set of font dirs that you have. Xfs is very unforgiving if you specify an unexisting or empty directory (dumps core on my computer). I encountered the same problem when I wanted to start using xfs for the fonts and found that I had to remove the '100dpi' directory from the 'catalogue' line. It now works fine for me. What is the xfs for? Why using it? Though I don't this daemon, I have no problem using X11. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
On Thu, 25 Sep 1997, Civ Kevin F. Havener wrote: You didn't say (and I can't figure out from your error messages) whether or not you are using AcceleratedX. If so, you need to go into all of your font directories and gunzip the fonts, then ncompress them if you have it, then do the mkfontdir step. AcceleratedX can't do gzipped fonts, but it does understand compressed fonts. If this is your problem, I can forward you a message from Xi Graphics support that gives you the step by step details. But that doesn't matter if you use xfs for the fonts. Just configure xfs, set the FontPath of the X server to tcp/localhost:7100 and you're all set. Then xfs will handle the fonts (gzipped or not) and the X server uses a standard protocol to ask xfs for them. Remco -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
On Fri, 26 Sep 1997, Lawrence wrote: I took a look at the output of the X server in an earlier post and it already uses xfs for the fonts. But you have to configure xfs so that it looks in the right place for the fonts. Take a look at the 'catalogue' line in /etc/X11/xfs/config. You have to set this to exactly the set of font dirs that you have. Xfs is very unforgiving if you specify an unexisting or empty directory (dumps core on my computer). I encountered the same problem when I wanted to start using xfs for the fonts and found that I had to remove the '100dpi' directory from the 'catalogue' line. It now works fine for me. What is the xfs for? Why using it? Though I don't this daemon, I have no problem using X11. Xfs is the X Font Server. You won't have much problems if you don't use it, but it seems to be better than letting the X server manage the fonts in some cases. For example, you don't have to gunzip all fonts if you are using an X server that doesn't understand gzipped fonts. And of course you can use one font server to serve a whole network of X servers (I have no idea what the performance would be). Remco -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
According to Remco Blaakmeer [EMAIL PROTECTED]: I took a look at the output of the X server in an earlier post and it already uses xfs for the fonts. But you have to configure xfs so that it looks in the right place for the fonts. Take a look at the 'catalogue' line in /etc/X11/xfs/config. You have to set this to exactly the set of font dirs that you have. Xfs is very unforgiving if you specify an unexisting or empty directory (dumps core on my computer). I encountered the same problem when I wanted to start using xfs for the fonts and found that I had to remove the '100dpi' directory from the 'catalogue' line. It now works fine for me. I experienced exactly the same, when I first updated the fonts, but not the Xserver. I had to play around with the Catalogue line until only the valid paths were listed. Then I updated to XFree86 3.3 and could restore the previous Catalogue line. So, I think xfs should be configured fine. Is there any way to make xfs list the fonts it can serve? In order to check the configuration? If that's not it, I am still clueless. Should I - maybe - completely purge X and reinstall it? I'd hate to do it, but if there is no other way... Thanks to all, Andy. Andy Spiegl, University of Technology, Muenchen, Germany E-Mail: [EMAIL PROTECTED] OR: [EMAIL PROTECTED] URL:http://www.appl-math.tu-muenchen.de/~spiegl PGP fingerprint: B8 48 24 7B DB 96 6F 1C D9 6D 8E 6C DB C2 E7 E9 o _ _ _ - __o __o /\_ _ \\o (_)\__/o (_) --- _`\,__`\,__(_) (_)/_\_| \ _|/' \/ -- (_)/ (_) (_)/ (_) (_)(_) (_)(_)' _\o_ ~~~ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
Andy Spiegl wrote: According to Remco Blaakmeer [EMAIL PROTECTED]: I took a look at the output of the X server in an earlier post and it already uses xfs for the fonts. But you have to configure xfs so that it looks in the right place for the fonts. Take a look at the 'catalogue' line in /etc/X11/xfs/config. You have to set this to exactly the set of font dirs that you have. Xfs is very unforgiving if you specify an unexisting or empty directory (dumps core on my computer). I encountered the same problem when I wanted to start using xfs for the fonts and found that I had to remove the '100dpi' directory from the 'catalogue' line. It now works fine for me. I experienced exactly the same, when I first updated the fonts, but not the Xserver. I had to play around with the Catalogue line until only the valid paths were listed. Then I updated to XFree86 3.3 and could restore the previous Catalogue line. So, I think xfs should be configured fine. Is there any way to make xfs list the fonts it can serve? In order to check the configuration? If that's not it, I am still clueless. Should I - maybe - completely purge X and reinstall it? I'd hate to do it, but if there is no other way... maybe, have a script to parse/verify/modify the font paths. Lawrence -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
Xfs is the X Font Server. You won't have much problems if you don't use it, but it seems to be better than letting the X server manage the fonts in some cases. For example, you don't have to gunzip all fonts if you are using an X server that doesn't understand gzipped fonts. And of course you can use one font server to serve a whole network of X servers (I have no idea what the performance would be). do you mean that X11 uses the xfs if the daemon is running, otherwise, it does it by its own? Lawrence -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
On 25 Sep 1997, Andy Spiegl wrote: According to Remco Blaakmeer [EMAIL PROTECTED]: I took a look at the output of the X server in an earlier post and it already uses xfs for the fonts. But you have to configure xfs so that it looks in the right place for the fonts. Take a look at the 'catalogue' line in /etc/X11/xfs/config. You have to set this to exactly the set of font dirs that you have. Xfs is very unforgiving if you specify an unexisting or empty directory (dumps core on my computer). I encountered the same problem when I wanted to start using xfs for the fonts and found that I had to remove the '100dpi' directory from the 'catalogue' line. It now works fine for me. I experienced exactly the same, when I first updated the fonts, but not the Xserver. I had to play around with the Catalogue line until only the valid paths were listed. Then I updated to XFree86 3.3 and could restore the previous Catalogue line. So, I think xfs should be configured fine. Is there any way to make xfs list the fonts it can serve? In order to check the configuration? Look at fsinfo and fslsfonts (and anything else starting with fs). (BTW I /did/ think you were running a different Xserver in my private mail - perhaps something I misread in an earlier post.) -- David Wright, Open University, Earth Science Department, Milton Keynes MK7 6AA U.K. email: [EMAIL PROTECTED] tel: +44 1908 653 739 fax: +44 1908 655 151 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
On 25 Sep 1997, Andy Spiegl wrote: According to Remco Blaakmeer [EMAIL PROTECTED]: I took a look at the output of the X server in an earlier post and it already uses xfs for the fonts. But you have to configure xfs so that it looks in the right place for the fonts. Take a look at the 'catalogue' line in /etc/X11/xfs/config. You have to set this to exactly the set of font dirs that you have. Xfs is very unforgiving if you specify an unexisting or empty directory (dumps core on my computer). I encountered the same problem when I wanted to start using xfs for the fonts and found that I had to remove the '100dpi' directory from the 'catalogue' line. It now works fine for me. I experienced exactly the same, when I first updated the fonts, but not the Xserver. I had to play around with the Catalogue line until only the valid paths were listed. Then I updated to XFree86 3.3 and could restore the previous Catalogue line. So, I think xfs should be configured fine. Is there any way to make xfs list the fonts it can serve? In order to check the configuration? Try: fsinfo -server localhost:7100 fslsfonts -server localhost:7100 If that's not it, I am still clueless. Should I - maybe - completely purge X and reinstall it? I'd hate to do it, but if there is no other way... If xfs is properly configured and running, and if the FontPath in XF86Config is set to tcp/localhost:7100, there should really be no problem. Remco -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
On Fri, 26 Sep 1997, Lawrence wrote: Xfs is the X Font Server. You won't have much problems if you don't use it, but it seems to be better than letting the X server manage the fonts in some cases. For example, you don't have to gunzip all fonts if you are using an X server that doesn't understand gzipped fonts. And of course you can use one font server to serve a whole network of X servers (I have no idea what the performance would be). do you mean that X11 uses the xfs if the daemon is running, otherwise, it does it by its own? No, you will have to tell the X server that it must use the font server. Look in /etc/X11/XF86Config for some lines like: FontPath /usr/X11R6/lib/X11/fonts/75dpi/ Place a '#' in front of all those lines, and add a line: FontPath tcp/localhost:7100 This will cause the X server to try to make the connection with xfs at localhost, port 7100. If xfs is not running, the X server will fail to start because it can't find any fonts. Remco -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
Remco Blaakmeer wrote: No, you will have to tell the X server that it must use the font server. Look in /etc/X11/XF86Config for some lines like: FontPath /usr/X11R6/lib/X11/fonts/75dpi/ Place a '#' in front of all those lines, and add a line: FontPath tcp/localhost:7100 This will cause the X server to try to make the connection with xfs at localhost, port 7100. If xfs is not running, the X server will fail to start because it can't find any fonts. If I put 'FontPath tcp/localhost:7100' the very first line and follow by others font paths, do you think the X server will try to use the xfs, if fails it uses the others. Lawrence -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: X problem after update from REX to BO (detailed error messages now)
On Fri, 26 Sep 1997, Lawrence wrote: If I put 'FontPath tcp/localhost:7100' the very first line and follow by others font paths, do you think the X server will try to use the xfs, if fails it uses the others. Hmm, interesting thought. I'll try it. -- wait some time -- No, it doesn't work. With this in XF86Config: FontPath tcp/localhost:7100 FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/Type1/ FontPath /usr/X11R6/lib/X11/fonts/Speedo/ and xfs not running, I get: [all normal messages] (**) FontPath set to tcp/localhost:7100,/usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/75dpi/, /usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/ [more normal messages] _FontTransSocketINETConnect: Can't connect: errno = 111 failed to set default font path 'tcp/localhost:7100,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled, /usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/' Fatal server error: could not open default font 'fixed' So, it turns out your suggestion doesn't work here. Remco -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
