Subject: Re: NetBSD/vax 2.0 X woes
To: None <port-vax@NetBSD.org>
From: Blaz Antonic <blaz.antonic@siol.net>
List: port-vax
Date: 02/09/2005 10:11:59
Hello,

A follow-up on my X problems with NetBSD/vax 2.0: i finally got around
to shuffling the hardware around a bit so my Vaxstation ended up with
both HDs i bought recently. The old one contained functional 1.6(.1)
setup that worked just fine with xdm so i copied configuration files
over (entire /usr/X11R6/lib/X11/xdm directory). Voila, at least i got
xdm login from Vax now. Based on differences [actually the lack thereof]
between xdm-config and Xaccess files in both setups my conclusion is
that significantly changed Xresources is probably the culprit.

Anyway, now that i got past this problem i figured i can finally get a
window manager running. Twm works ... to an extent. 

http://tinypic.com/view.html?pic=1oqdtt

This is xterm started via twm menu and xboard started from said xterm,
after 1 minute or so of waiting - plenty of time to come up with
something but nothing did. Ditto for xbomb (window comes up with few
idgets but they are all blank). Xclock -digital shows blank rectangle
while analog clock works. Icewm still dosn't seem to work (it changes
mouse cursor and background and nothing ever shows up, no menu, no
taskbar, no nothing).

Just to make sure my X server wasn't the culprit i startex xdm on a
Linux box (with fvwm) and started xboard there:

http://tinypic.com/view.html?pic=1oqdxj

Worked like a charm. Methinks there is something messed up really bad
with one of the X libraries that come bundled with the (2.0) system.
Since nobody else is complaining i can only conclude that this is a
Vax-specific issue. The odd messages about incompatible protocols i
mentioned in my last e-mail still show up occassionally in xdm-errors
log file but i can't see any pattern.

I tried different X server settings (auto/8/16/24 bit color depth,
auto/LSB/MSD picture byte order, etc.) but to no avail, results are the
same (or worse, in case of 16 bit color depth nothing works, not even
xdm). It's as if one of the X libraries that most apps depend upon for
rendering was seriously fscked up in transition from 1.6.x to 2.0. Any
suggestions ?

Blaz Antonic
-- 
Hi! I'm a signature virus!
Copy me into your signature to help me spread!