Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues

[Mark Edwards]

On Tuesday, February 11, 2003, at 12:37 PM, Joe Marcus Clarke wrote:

Well, I updated to 2.2 today, and while I was still in the gnome
desktop, it seemed to fix the anti-aliasing issues I was having.
However, I restarted, and now I get this:

Feb 11 00:51:32 lilbuddy gdm[24662]: gdm_slave_xioerror_handler: Fatal
X error - Restarting :0
Feb 11 00:51:34 lilbuddy gdm[24666]: gdm_slave_xioerror_handler: Fatal
X error - Restarting :0
Feb 11 00:51:39 lilbuddy gdm[24670]: gdm_slave_xioerror_handler: Fatal
X error - Restarting :0
Feb 11 00:51:44 lilbuddy gdm[24674]: gdm_slave_xioerror_handler: Fatal
X error - Restarting :0
Feb 11 00:51:44 lilbuddy gdm[24661]: Failed to start X server several
times in a short time period; disabling display :0

I've seen this before, of course.  gdm is starting from
/usr/X11R6/etc/rc.d/gdm.sh, so that's not it.

I removed the font-related alterations I made recently, that's not it.

How do I figure out what's causing gdm to hang?

Not sure.  What's in your /var/log/XFree86.0.log?

Joe

I think I'm onto it. I don't have a /var/log/XFree86.0.log, but I do have a /var/log/:0.log (where'd that name come from?), and it says:

XFree86 Version 3.3.6 / X Window System
(protocol Version 11, revision 0, vendor release 6300)
Release Date: xx November 2000
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: FreeBSD 4.5-PRERELEASE i386 [ELF]
Configured drivers:
Mach64: accelerated server for ATI Mach64 graphics adaptors (Patchlevel 1)
Using syscons driver with X support (version 2.0)
(using VT number 9)

XF86Config: /etc/XF86Config
(**) stands for supplied, (--) stands for probed/default values
(--) no ModulePath specified using default: /usr/X11R6/lib/modules
freetype: Unknown error loading module
type1: Unknown error loading module
(**) XKB: rules: "xfree86"
(**) XKB: model: "pc101"
(**) XKB: layout: "us"
(**) Mouse: type: SysMouse, device: /dev/mouse, resolution: 100
(**) Mouse: buttons: 3, 3 button emulation (timeout: 50ms)
(**) Mach64: Graphics device ID: "Primary Card"
(**) Mach64: Monitor ID: "Primary Monitor"
Warning: 'fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts/local".
Entry deleted from font path.
(Run 'mkfontdir' on "/usr/X11R6/lib/X11/fonts/local").
(**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc:unscaled,/usr/X11R6/lib/X11/fonts/75dpi:unscaled,
/usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1,/usr/
X11R6/lib/X11/fonts/Speedo,/usr/X11R6/lib/X11/fonts/misc,/usr/X11R6/lib/X11/
fonts/75dpi,/usr/X11R6/lib/X11/fonts/100dpi,/usr/X11R6/lib/X11/fonts/webfonts/
"
(--) Mach64: PCI: Mach64 CT rev 9, Aperture @ 0xfe000000, Block I/O @ 0xfc00
(--) Mach64: Card type: PCI
(--) Mach64: Memory type: DRAM (1)
(--) Mach64: Clock type: Internal
(--) Mach64: Maximum allowed dot-clock: 80.000 MHz
(**) Mach64: Mode "800x600": mode clock = 60.750
(--) Mach64: Virtual resolution: 800x600
(--) Mach64: Video RAM: 2048k
(--) Mach64: Using hardware cursor
(--) Mach64: Using 16 MB aperture @ 0xfe000000
(--) Mach64: Ramdac is Internal
(--) Mach64: Ramdac speed: 80 MHz
(**) Mach64: Color weight: 565
(--) Mach64: Pixmap cache: 0 256x256 slots, 0 128x128 slots, 0 64x64 slots
(--) Mach64: Font cache: 0 fonts
failed to set default font path '/usr/X11R6/lib/X11/fonts/misc:unscaled,/usr/X11R6/lib/X11/fonts/75dpi:unscaled,
/usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1,/usr/
X11R6/lib/X11/fonts/Speedo,/usr/X11R6/lib/X11/fonts/misc,/usr/X11R6/lib/X11/
fonts/75dpi,/usr/X11R6/lib/X11/fonts/100dpi,/usr/X11R6/lib/X11/fonts/webfonts/
'
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

Now, I'd say the error is clear. Do I just need to run mkfontdir on my font directories? Odd that I need to do that, since this was a working installation before the 2.2 update.

Other questions -- why does the log report XFree86 Version 3.3.6 on FreeBSD 4.5 PRERELEASE? As far as I can tell I'm running XFree86 4.2.1, and I'm definitely running FreeBSD 4.7p4. That's scary. Maybe I need to completely reinstall and reconfigure XFree86? Is that as simple as removing the XFree86-libraries-4.2.1_6 package and reinstalling it? Do I just need to go to /stand/sysinstall and re-configure XFree86?

Very odd.

--
Mark Edwards
Engineer
Mr. Toad's
San Francisco, CA


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message