On 7/25/22 3:27 PM, Nick Holland wrote:
Somewhere between 7.1 release and -current, X quit working
on this machine. It is a really lousy machine, wireless
doesn't work, slow, etc., and it cost $80 new (and is
currently $60), so "What do you expect?" is a valid response.
But in case someone cares...
On 7.1, X "just worked". By May 12's snapshot, X had quit
working (that's when I bought it, I went "back" to 7.1-rel
to test it).
...
Sigh. collect info, leave out most basic part: what I mean
by "X quit working"...
When running "startx", it blanks the screen, nothing more is
seen on the screen. CTRL-ALT-F1, CTRL-ALT-F5, CTRL-ALT-Backspace
all have no effect. Capslock key still results in change of
the capslock light. If I ssh into the box, I can still look
around, but a "reboot" results in a hung system, requiring a
hard power down. top shows X is running, but attempting to
kill it results in a hung box (caps lock quits responding, too).
Same things happen with xenodm.
Trying to isolate the task that causes the lockup, I was
able to shutdown xenodm without problem, but the hang happened
when I did a kill of this task:
evolveiii# ps -ax |grep X
17869 ?? Zp 0:00.00 (Xorg)
88658 ?? I 0:02.10 /usr/X11R6/bin/X :0 vt05 -auth
/etc/X11/xenodm/authdir/authfiles/A:0-PkNh6u (Xorg)
21819 p0 R+/3 0:00.00 grep X
evolveiii# kill 88658
evolveiii# ps -ax |grep X
17869 ?? Zp 0:00.00 (Xorg)
88658 ?? S 0:02.10 /usr/X11R6/bin/X :0 vt05 -auth
/etc/X11/xenodm/authdir/authfiles/A:0-PkNh6u (Xorg)
65248 p0 R+/2 0:00.00 grep X
evolveiii# kill -9 88658
[hang]
Nick.
