Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 3 Feb 2021 17:39:30 -0500
From:      LuMiWa <lumiwa@dismail.de>
To:        Polytropon <freebsd@edvax.de>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: vi editor
Message-ID:  <20210203173930.6bb72e82@dismail.de>
In-Reply-To: <20210203002153.81725c82.freebsd@edvax.de>
References:  <20210202052155.3a6ca086@dismail.de> <20210202232148.995f86c7.freebsd@edvax.de> <20210202181148.2ea69176@dismail.de> <20210203002153.81725c82.freebsd@edvax.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 3 Feb 2021 00:21:53 +0100
Polytropon <freebsd@edvax.de> wrote:

> On Tue, 2 Feb 2021 18:11:48 -0500, LuMiWa wrote:
> > On Tue, 2 Feb 2021 23:21:48 +0100
> > Polytropon <freebsd@edvax.de> wrote:
> >=20
> > > On Tue, 2 Feb 2021 05:21:55 -0500, LuMiWa via freebsd-questions
> > > wrote:
> > > > I do not what happened but yesterday when I start typing it
> > > > doesn't respond on the keyboard immediately. I need to type
> > > > from 5 to 10 times and than start. I never had the same problem
> > > > in 20 years. For user I have ksh93 shell and root sh but on the
> > > > both are the same.
> > >=20
> > > A few questions:
> > >=20
> > > Does this delay affect shell interaction already, or is it present
> > > only in vi?
> > >=20
> > > Does it happen inside an X session (terminal) or at the console?
> > > If inside X, which input method are you using, and how?
> > >=20
> > > Do you use the system locally or via network connection?
> > >=20
> > > Lagging _could_ be a problem of networking (if networking is
> > > involved here). But any program generating system load could
> > > interfere with input processing, so check "top" output for
> > > any suspicious values. Also try "reset" to get rid of any
> > > terminal misconfiguration that might have happened.
> > >=20
> > >=20
> > >=20
> >=20
> > I am sorry hat I didn't sent an email about my mistake or. better
> > the keyboard problem. I had the old Cherry which is connected with
> > adapter to usb port and I had sometimes problem but never with vi.
>=20
> Regarding USB (and especially converters from PS/2 to USB):
>=20
> Sometimes, they are discovered by the kernel _after_ the login
> prompt has been displayed, i. e., after booting completed. No
> idea why, probably a "slow" firmware inside the converter that
> needs some time to load.
>=20
> Sidenote: I am currently using an IBM model M keyboard with
> such an adapter, or to be precise, a chain of adapters (HIL to
> DIN, DIN to PS/2, PS/2 to USB), really _sometimes_ the keyboard
> isn't present yet when the system displays the XDM login screen;
> a few seconds later, it works as expected. And it will continue
> working after I have turned to dust many years in the distant
> future... ;-)
>=20
> So what you've been observing could be fully normal for your
> hardware setting (including the "sometimes" aspect). Also note
> that even though USB is a fundamental part of the kernel, the
> kernel changes, therefore "detection order" might be affected
> after a system (or kernel) upgrade.
>=20
>=20
>=20

Thank you very much. It is time to buy a new Cherry because this one is
very old. I think from my 286 with 2MB RAM and 50 MB Quantum HD :).

--=20
=E2=80=9CWise men speak because they have something to say; fools because t=
hey
have to say something.=E2=80=9D

--Plato



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210203173930.6bb72e82>