Date: Sun, 14 Jul 2024 13:00:18 -0600 From: Warner Losh <imp@bsdimp.com> To: Dmitry Salychev <dsl@freebsd.org> Cc: =?UTF-8?B?R29yYW4gTWVracSH?= <meka@tilda.center>, freebsd-current@freebsd.org Subject: Re: Keyboard on laptop typing problem Message-ID: <CANCZdfr7FpnU0Y2YwEqPvghF1SXYKvAKoWF2b92GT%2BpKQeptfw@mail.gmail.com> In-Reply-To: <86cyngcdsr.fsf@peasant.bootbsd.com> References: <0f378de3-7a20-4284-8cca-6c9ed2d0c55d@tilda.center> <d1a1dd45dd304cdad98191b8abde2ae3@bsdforge.com> <8878ea2e-f91e-4cfd-8ddd-cc1d070eea32@tilda.center> <86cyngcdsr.fsf@peasant.bootbsd.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] M*ay*be try https://reviews.freebsd.org/D45554 and see if that works? Warner On Sun, Jul 14, 2024 at 7:18 AM Dmitry Salychev <dsl@freebsd.org> wrote: > > Goran Mekić <meka@tilda.center> writes: > > > On 7/13/24 18:18, Chris wrote: > >> On 2024-07-13 15:23, Goran Mekić wrote: > >>> Hello, > >>> > >>> I have a laptop with a weird behaving keyboard. Under Linux > >>> everything is fine, > >>> but under FreeBSD it is out of sync. On single key stroke of letter > >>> 'c' (just for > >>> example) terminal first doesn't do anything for about a second, > >>> then it prints > >>> multiple letters 'c' in a row. Is there any way to debug this > >>> behavior and why > >>> it's happening? Any chance there's a known workaround? I don't know > >>> what other > >>> info would be useable, so if you can tell me what other than > >>> usbconfig and pciconf > >>> to look at, I'll be glad to. > >> It would be very helpful to know what hardware you're using. It's > >> otherwise very > >> difficult to answer this sort of question. > > > > You can see that yesterday was the hottest day in my city ever. First, > > I didn't manage to ask what I wanted: what info should I send, second > > I sent the reply only to one person :facepalm: > > > > Anyway, I think the most condensed way to show the hardware is > > https://bsd-hardware.info/?probe=3400ac8782 > > > > Regards, > > meka > > IRQ override [1] which breaks active low IRQs on AMD Ryzen 6000+ systems > might be the reason of your troubles. I don't know the exact place in > the FreeBSD src/ to check whether the same override is implemented or > not, but you'd try to patch ACPI tables yourself [2] till it is fixed. > > Regards, > Dmitry > > [1] > > https://lore.kernel.org/all/CAJZ5v0isLQVX3EqsokFthY5ka=V4Vse9T52s3EGSv41FKM1iGw@mail.gmail.com/ > [2] > https://www.reddit.com/r/linuxhardware/comments/vdc6tz/comment/ijjjwah/ > > -- > https://wiki.freebsd.org/DmitrySalychev > > [-- Attachment #2 --] <div dir="ltr"><div dir="ltr">M<b>ay</b>be try <a href="https://reviews.freebsd.org/D45554">https://reviews.freebsd.org/D45554</a>; and see if that works?</div><div dir="ltr"><br></div><div>Warner<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jul 14, 2024 at 7:18 AM Dmitry Salychev <<a href="mailto:dsl@freebsd.org">dsl@freebsd.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br> Goran Mekić <meka@tilda.center> writes:<br> <br> > On 7/13/24 18:18, Chris wrote:<br> >> On 2024-07-13 15:23, Goran Mekić wrote:<br> >>> Hello,<br> >>><br> >>> I have a laptop with a weird behaving keyboard. Under Linux<br> >>> everything is fine,<br> >>> but under FreeBSD it is out of sync. On single key stroke of letter<br> >>> 'c' (just for<br> >>> example) terminal first doesn't do anything for about a second,<br> >>> then it prints<br> >>> multiple letters 'c' in a row. Is there any way to debug this<br> >>> behavior and why<br> >>> it's happening? Any chance there's a known workaround? I don't know<br> >>> what other<br> >>> info would be useable, so if you can tell me what other than<br> >>> usbconfig and pciconf<br> >>> to look at, I'll be glad to.<br> >> It would be very helpful to know what hardware you're using. It's<br> >> otherwise very<br> >> difficult to answer this sort of question.<br> ><br> > You can see that yesterday was the hottest day in my city ever. First,<br> > I didn't manage to ask what I wanted: what info should I send, second<br> > I sent the reply only to one person :facepalm:<br> ><br> > Anyway, I think the most condensed way to show the hardware is<br> > <a href="https://bsd-hardware.info/?probe=3400ac8782" rel="noreferrer" target="_blank">https://bsd-hardware.info/?probe=3400ac8782</a><br>; ><br> > Regards,<br> > meka<br> <br> IRQ override [1] which breaks active low IRQs on AMD Ryzen 6000+ systems<br> might be the reason of your troubles. I don't know the exact place in<br> the FreeBSD src/ to check whether the same override is implemented or<br> not, but you'd try to patch ACPI tables yourself [2] till it is fixed.<br> <br> Regards,<br> Dmitry<br> <br> [1]<br> <a href="https://lore.kernel.org/all/CAJZ5v0isLQVX3EqsokFthY5ka=V4Vse9T52s3EGSv41FKM1iGw@mail.gmail.com/" rel="noreferrer" target="_blank">https://lore.kernel.org/all/CAJZ5v0isLQVX3EqsokFthY5ka=V4Vse9T52s3EGSv41FKM1iGw@mail.gmail.com/</a><br>; [2] <a href="https://www.reddit.com/r/linuxhardware/comments/vdc6tz/comment/ijjjwah/" rel="noreferrer" target="_blank">https://www.reddit.com/r/linuxhardware/comments/vdc6tz/comment/ijjjwah/</a><br>; <br> -- <br> <a href="https://wiki.freebsd.org/DmitrySalychev" rel="noreferrer" target="_blank">https://wiki.freebsd.org/DmitrySalychev</a><br>; <br> </blockquote></div></div>help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfr7FpnU0Y2YwEqPvghF1SXYKvAKoWF2b92GT%2BpKQeptfw>