Return to BSD News archive
Xref: sserve comp.windows.x.i386unix:15607 comp.os.386bsd.misc:5529
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!news.hawaii.edu!ames!olivea!rahul.net!a2i!news.clark.net!news.sprintlink.net!howland.reston.ans.net!nctuccca.edu.tw!news.cc.nctu.edu.tw!news!gate!lim
From: lim@gate.sinica.edu.tw (Carmay Lim)
Newsgroups: comp.windows.x.i386unix,comp.os.386bsd.misc
Subject: XF86 3.1.1, ET4000 server hangs on restart
Date: 17 Feb 1995 19:29:23 GMT
Organization: Computing Center, Academia Sinica
Lines: 38
Message-ID: <3i2tej$3v6@gate.sinica.edu.tw>
NNTP-Posting-Host: lim%@gate.sinica.edu.tw
X-Newsreader: TIN [version 1.2 PL2]
I was having a bit of trouble with my S3 864 card under XFree86
3.1.1 (FreeBSD 950210 snapshot) so I swapped it for a Tseng ET4000/W32p
VLB card with 1 meg. I switched the X server over to the XF86_W32 one,
created an appropriate /etc/XF86Config file and rebooted.
My /etc/ttys file starts up "xdm -nodaemon" on /dev/ttyv7 to give
me the xlogin window on startup. Everything comes up fine, I can login
and do stuff, and then logout. At this point, the X server should be
restarted. In my case, with the ET4000, the display stays blank and
the root weave never re-appears. According to the monitor's LED display,
it is in standard 80x25 VGA text mode. Hitting Alt-[Ctrl]-Fkey to
switch consoles just causes a beep. I can login from another terminal
and see that both xdm (two copies) and X are running. Restarting either
doesn't solve the problem. Ctrl-Alt-Backspace doesn't do anything.
Secondly, If I manually run "xdm" as root (e.g., in daemon mode), I
can logout of an X session and the server will be restarted (root weave
comes up, xlogin comes up). There is another minor problem, though.
After the screen clears (from logging out) and before the root weave
reappears, there are about 100 rows of garbage pixels on the screen
(1024x768) which consequently disappear. Could this be some sort of
video buffer memory trashing because the ET4000 only makes 1023K
available instead of the full 1024K? 1K difference shouldn't cause
that many dirty pixels though. Anyone else have this problem?
Lastly, I cannot seem to get xterm or any other X application to
recognize modifier+click events in their windows. For example, xterm's
Control+click menus don't work... it just beeps at me now. My window
manager (ctwm 3.3) has Alt-F1 through Alt-F4 bound to the virtual
desktops. These hotkeys don't work if keyboard focus is in an xterm.
It *does* work if I move the mouse onto the desktop. Switching window
managers doesn't help. In fact, it probably doesn't have anything to
do with the window manager: the problem remains even if I just run X
and then pop up a naked xterm. If I plug the S3 card back in, switch
XF86Config files and X server, the modifier+clicks work again. I don't
see anything different between the two XF86Configs that could be
causing this type of behaviour. Is this a bug in the ET4000 server,
somehow?