Dear Sirs,
I just finished a long weekend of upgrades on a 2100A. We
upgraded from DU 3.2G up to DU 4.0B including the latest
patch kit.
But somehow, the X server does not want to start on the
graphics console of the 2100 even with the console firmware
set to 'graphics'.
I traced the problem to dtlogin/Xdec. dtlogin is trying
to start '/usr/bin/X11/X :0' but the X server dies on him.
I manually tried to run the X server using the command line
above and got the followings errors:
use: X [:<display>] [option]
-a #
-ac
-audit
...
This seems to indicate the X server does not like the
command line parameters. What's strange is that we did not make
any changes to the X config files and that is the same command
that dtlogin is trying to run.
They only thing I can think of is that we were using a 'console serial'
during the upgrade to capture everything on a PC, and this changed the
behavior of the installupdate? Or a problem with the 'locale' stuff?
I am at a lost (and its getting late 8-) ). If you have any insight
please let me know.
Thanks in advance.
NOTE: If there is anybody doing the same upgrade on a 2100A with
more than 1GB of main memory you will have another problem.
There is a bug in DU 4.0A which causes a panic during the kernel
boot for 2100A's with more than 1GB of main memory. The work around
is to boot vmunix interactive and specify memlimit=1024.
NOTE: Also, stay away from DECnet/OSI if you can. Its always a bitch
to upgrade. 8-)
Finally, I am doing a 3.2G to 4.0B upgrade on a 8400 in a few weeks.
if anybody knows of any gotchas for such a config I would appreciate
hearing about them.
Thanks again!
Yvon Lauriault
National Library of Canada
Received on Mon Mar 02 1998 - 00:17:00 NZDT