Ok, folks, I'm tearing out my (almost already gone) hair here on this one.
Yesterday, I asked if anyone knew why NFS installs for 6.1 worked last week,
but are broken now. Didn't get an answer, but the problem seems to be that
on some of the cards, it can't load the proper driver (it's mis-detecting
them, but doing it automatically :( On others, well, they're old cards, and
I have at least two bum cards (I've now tried an even dozen, of many
different makes).
My new problem is more insidious, but probably better solvable, though I
haven't a clue where to start other than to stair at some directories.
Yesterday, a coworker logged into our 6.1 upgraded machine for the first
time since the upgrade... and had a devil of a time. I had xdm running in
the background, with Gnome being the main window manager. He finally got
logged in, and everything was >SLOW< from the console... I mean glacial,
even though remote terminals on the machine were normal. Well, we rebooted
it to see if perhaps something strange existed... no problem for me,
everything was back to normal, but it still acted funky for him. Last
night, at about 4 (when it was running daily cron jobs) the machine sent out
an error message saying that the following:
-----------------------------------------------------------------------
Subject: Cron <root@Linus> run-parts /etc/cron.daily
X-Cron-Env: <SHELL=/bin/bash>
X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <MAILTO=root>
X-Cron-Env: <HOME=/>
X-Cron-Env: <LOGNAME=root>
mkdir: cannot make directory `/tmp/whatis766': No space left on device
chmod: /tmp/whatis766: No such file or directory
-----------------------------------------------------------------------
It then promptly rebooted itself (I've never seen that before, and it's not
one of my cron jobs....) When it came back up, I had 49% use on the drive
/tmp is on.
Today, we were ordered to move some machines, so now it's on MY desk.... but
we had to shutdown again. This time, I can't get startx to bring up
X-Windows (and of course, xdm, gdm, and kdm are all right out). I'm getting
the following error (I've snipped most of the earlier non-error messages),
which means it's obviously a font problem:
----------------------------------------------------------------------------
--
(--) S3: Using 16 planes of 960x255 at (0,769) aligned 8 as font cache
_FontTransSocketUNIXConnect: Can't connect: errno = 111
failed to set default font path 'unix/:-1'
Fatal server error:
could not open default font 'fixed'
When reporting a problem related to a swerver crash, please send
the full server output, not just the last messages
X connection to :0.0 broken (explicit kill or server shutdown).
wew >
----------------------------------------------------------------------------
----
Looking through the various font folders under /usr/X11R6/lib/X11/fonts, I
have to admit, I don't see a font named 'fixed'.... but a 5.2 verion on a
different machine ALSO doesn't show a font named 'fixed' and it works fine.
Help!!!!!
TIA
Bill Ward
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
