Re: Problems getting X to run properly on 9.0/amd64

[Michael Siegel <msi%malbolge.net@localhost>]

Am 15.07.20 um 12:33 schrieb nia:
> On Mon, Jul 13, 2020 at 03:09:31AM +0200, Michael Siegel wrote:
>> Hello,
>>
>> I'm trying to use X on my laptop, running NetBSD 9.0/amd64, but it's
>> not really working, meaning:
>>
>>   * The X server will start, but needs nearly 1 minute to finish
>>     starting up and giving me a graphical environment.
> 
> Could be waiting to unlock files, startx is iffy about that.
> What happens when you press ctrl+c?

I'm seeing some errors about files being locked, occasionally, but I
haven't been able to reproduce and record them.

Pressing Ctrl+C doesn't do anything, as far as I can see. The keyboard
is unresponsive as soon as I run `startx'. I can sometimes use the
cursor keys to navigate Openbox' root menu, though, after I have brought
it up with a mouse click. That will only work for a very limited period
of time, however.

>>   * When the X environment is up, I'm unable to use the computer's
>>     touchpad. A USB mouse will work to bring up my window manager's
>>     menu, though. (I'm using Openbox.)
> 
> There is a bug causing mouse lockups with Synaptics devices, it's fixed
> in 9_STABLE and will be in 9.1. You should try a 9_STABLE kernel.
> 
> dmesg would confirm it's a Synaptics device, the driver is called pms(4)

I have now set up my system to track 9.0_STABLE using `sysupgrade'. But
so far, this hasn't changed anything concerning X.

Running `dmesg | grep pms' revealed the following:

  [     1.017302] pms0 at pckbc1 (aux slot)
  [     1.017302] pms0: autoconfiguration error: unsupported Elantech
  version 2.4 (2 0 4)
  [     1.017302] wsmouse0 at pms0 mux 0

> It looks like there are existing problem reports for
> "pckbport: command timeout", some containing information
> about workarounds.

Okay, I'll have a look.


--Michael