From owner-freebsd-questions@freebsd.org Wed Feb 3 22:39:39 2021 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A18E352EB33 for ; Wed, 3 Feb 2021 22:39:39 +0000 (UTC) (envelope-from lumiwa@dismail.de) Received: from mx1.dismail.de (mx1.dismail.de [78.46.223.134]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mx1.dismail.de", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DWGp21Jj1z3w2B for ; Wed, 3 Feb 2021 22:39:37 +0000 (UTC) (envelope-from lumiwa@dismail.de) Received: from mx1.dismail.de (localhost [127.0.0.1]) by mx1.dismail.de (OpenSMTPD) with ESMTP id 1294d720; Wed, 3 Feb 2021 23:39:35 +0100 (CET) Received: from smtp1.dismail.de ( [10.240.26.11]) by mx1.dismail.de (OpenSMTPD) with ESMTP id 1896b535; Wed, 3 Feb 2021 23:39:34 +0100 (CET) Received: from smtp1.dismail.de (localhost [127.0.0.1]) by smtp1.dismail.de (OpenSMTPD) with ESMTP id 3ae45701; Wed, 3 Feb 2021 23:39:34 +0100 (CET) Received: by dismail.de (OpenSMTPD) with ESMTPSA id ec2513b4 (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Wed, 3 Feb 2021 23:39:33 +0100 (CET) Date: Wed, 3 Feb 2021 17:39:30 -0500 From: LuMiWa To: Polytropon 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> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; amd64-portbld-freebsd12.2) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4DWGp21Jj1z3w2B X-Spamd-Bar: ------ X-Spamd-Result: default: False [-6.70 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[dismail.de:s=20190914]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:78.46.223.134]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; DWL_DNSWL_MED(-2.00)[dismail.de:dkim]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[78.46.223.134:from]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[dismail.de,reject]; DKIM_TRACE(0.00)[dismail.de:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:24940, ipnet:78.46.0.0/15, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; MAILMAN_DEST(0.00)[freebsd-questions] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Feb 2021 22:39:39 -0000 On Wed, 3 Feb 2021 00:21:53 +0100 Polytropon wrote: > On Tue, 2 Feb 2021 18:11:48 -0500, LuMiWa wrote: > > On Tue, 2 Feb 2021 23:21:48 +0100 > > Polytropon 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