@tom-horsley
It's alright. Glad to see I'm not the only one with this "wonky" state.
Hard term to search on. I just retested on:
```
Linux 5.8.0-55-generic #62~20.04.1-Ubuntu SMP Wed Jun 2 08:55:04 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
```
... this morning and it still repeats.
Please make
Looks like the bug I just added at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932360 is a
duplicate of this which I didn't find in any searches before I added it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Haven't fully tracked this issue in all kernels updated via apt but:
Kernel 5.4.0-51
Kernel 5.4.0-52
Kernel 5.4.0-65
Kernel 5.8.0-44
Kernel 5.8.0-49
Kernel 5.8.0-53
... all still have this issue.
At Kernel 5.8.0-49 IR went wonky with repeating key button presses for
quite some time although it
Kernel 5.4.0-71 has finally fixed the problem. Having just installed it,
I have not run extensive test on it, but it appears to be stable.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Still screwed up after reinstall. At this point I'd just recommend
installing the 5.11.3 kernel from the ppa and be done with it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1901089
While 5.10.0-1017 did fix the ir-keytable problem it introduced other
problems which I couldn't live with. After deleting my 5.11.3 kernel I
have since reinstalled it and am running it.Maybe I'll try to reinstall
the 5.10.0-1017 kernel later and see if I just got a bad install.
--
You received
I'm happy to report that the following dist kernel has fixed the problem.
wes@mythfe0:~$ uname -a
Linux mythfe0 5.10.0-1017-oem #18-Ubuntu SMP Fri Mar 5 18:33:48 UTC 2021 x86_64
x86_64 x86_64 GNU/Linux
It's in the repos.
And it also supports my nvme drive status which was why I was running later
Well, I run newer kernels from the ppa as my main kernel. Currently
running 5.11.3, so it's not a problem for me. As long as whomever does
the distribution kernels keep using old base kernels, the problem will
never be fixed. If you want to run a distribution kernel, then you
should go back to
I appreciate that you keep trying to verify that the fix is in place. I
guess I'll continue to use the workaround until I see that you have
confirmed the fix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Kernel 5.4.0-67 is still broken.
Can anyone explain this to me.
A patch that fixed it was done in Dec. 2020. And it was implemented in ppa
kernels compiled after 01/28/2021.
So why is it that this has not made it into any of the distribution kernels
yet. Kernels 5.10 has shown up in the repos,
last kernel upgrade to 5.4.0-66 is still broken.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Patch was added into kernel builds on 01-31-21. Working later kernels.
Linux mythfe0 5.10.13-051013-generic #202102032337 SMP Thu Feb 4 00:17:21 UTC
2021 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
After a system upgrade last night, the patched version 5.4.0-59 that
works was replaced by an older version of 5.4.0-59 dated Dec 10. So
anyone that installed the patched version will likely find their remote
not working again if they do a system upgrade.
--
You received this bug notification
I've submitted a PR
https://lore.kernel.org/linux-media/20210102101209.ga32...@gofer.mess.org/T/#t
This has to be merged by Mauro (linux-media). Then Linus has to merge it.
Finally, it needs to be merged into the stable tree. So it may be some time.
--
You received this bug notification
Just curious how long that takes. 5.10.3 was just released today and
doesn't look like it made it into it going by the changes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Thank you @wesnewell and @kaihengfeng for testing this!
Now that we know the patch works, I'll send the patch upstream and it'll
be included in the stable kernels as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Yes! That fixed it for me. Glad someone here could compile it. I was lost.
What happens now to all the other kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Test kernel with the patch:
https://people.canonical.com/~khfeng/lp1901089/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu kernels 5.4.0-51 and 5.4.0-52 break
After enabling sources and reverting to ubuntu kernel 5.4.0-58 installed
first part. Will continue tomorrow or later tonight.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Well, that didn't work.
wes@mythfe0:~$ sudo apt-get build-dep linux linux-image-$(uname -r)
[sudo] password for wes:
Reading package lists... Done
E: You must put some 'deb-src' URIs in your sources.list
wes@mythfe0:~$ uname -r
5.10.2-051002-generic
wes@mythfe0:~$
Last time I compiled a kernel
Thanks for that.
It seems very possible that this issue is solved by this patch:
https://patchwork.linuxtv.org/project/linux-
media/patch/20201221091929.26504-1-s...@mess.org/
Would you be able to test this patch please? There are instructions for
compiling the kernel here.
As you can see there's no reference to ir-keytable running in that
kernel. Ran the same on good kernel 5.8.7 and here's a snippet from the
output of it.
Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3:
/usr/lib/udev/rules.d/60-ir-keytable.rules:5 RUN '/usr/bin/ir-keytable -a
/etc/rc_maps.cfg
here goes.
root@mythfe0:/home/wes# journalctl -u systemd-udevd.service -f
-- Logs begin at Thu 2020-09-24 22:03:46 CDT. --
Dec 21 06:58:08 mythfe0 systemd-udevd[1702]: value '[dmi/id]sys_vendor' is 'To
Be Filled By O.E.M.'
Dec 21 06:58:08 mythfe0 systemd-udevd[1702]: 1-8: Device (SEQNUM=4105,
Thanks for that. It looks like on 5.8.8 it has not loaded the rc keymap
at all. It looks like a default mce keymap with the default rc-6
protocol enabled.
So for some reason /etc/rc_map.cfg did not get processed at all. That's
super odd. Let's try and see what udevd does when you plug in the
Oops. here's the other.
** Attachment added: "config-5.8.7-050807-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+attachment/5445251/+files/config-5.8.7-050807-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is
Ccofigs for both kernels attached.
** Attachment added: "config-5.8.8-050808-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+attachment/5445250/+files/config-5.8.8-050808-generic
--
You received this bug notification because you are a member of Kernel
Packages, which
This is with kernel 5.8.8 which doesn't work.
Found /sys/class/rc/rc0/ with:
Name: Media Center Ed. eHome Infrared Remote Transceiver (0471:0815)
Driver: mceusb
Default keymap: rc-rc6-mce
Input device: /dev/input/event7
LIRC device: /dev/lirc0
This is with working kernel 5.8.7.
root@mythfe0:/home/wes# ir-keytable
Found /sys/class/rc/rc3/ with:
Name: Media Center Ed. eHome Infrared Remote Transceiver (0471:0815)
Driver: mceusb
Default keymap: rc-rc6-mce
Input device: /dev/input/event19
LIRC device:
Actually you said "on newer systems it does not enable the nec
protocol". That is odd.
what is the output of ir-keytable on newer (broken) systems?
also what is the kernel config on broken systems (not sure how to see that on
ubuntu)
--
You received this bug notification because you are a
Thank you for that.
With evtest I mean the evtest tool from the evtest package:
https://packages.ubuntu.com/focal/evtest
when you run ir-keytable there is an line which says "Input device:
/dev/input/event..". Use that as an argument to evtest:
evtest /dev/input/event19
There will be some
On 12/19/20 5:09 PM, Sean Young wrote:
> Hello, the author of those commits here. It's not clear to me how those
> commits broke things. Either something else changed, or there is
> something subtle going on.
>
> The following bits of information would be very useful.
>
> 1. Is the issue
Hello, the author of those commits here. It's not clear to me how those
commits broke things. Either something else changed, or there is
something subtle going on.
The following bits of information would be very useful.
1. Is the issue intermittent or consistent, i.e. does booting with a new
I've emailed the person that commited them. With luck.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
I have no idea how to do that.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
Status in linux package in
Thanks. That boils down to two commits:
9af0c46a761293ef04c57f001cc2641d4ec1add3 media: rc: uevent sysfs file races
with rc_unregister_device()
bff924ee40ae3857e7373536fdda203378795e3c media: rc: do not access device via
sysfs after rc_unregister_device()
Can you please try which one breaks it?
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable
5.8.7-050807-generic #202009051031 SMP Sat Sep 5 10:34:16 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux WORKS.
kernel 5.8.8 does not.
Looks like any kernel built after Sep 5 2020 will be bad.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Last ubuntu kernel that worked was 5.4.0-48. First that doesn't is 5.4.0-51.
And there isn't a 5.4.0 dir list here.
https://kernel.ubuntu.com/~kernel-ppa/mainline/
It works in some later kernels from mainline but quit working sometime after
5.4.53, and doesn't work in 5.9 or 5.10.
--
You
First, find the last -rc kernel works and the first -rc kernel doesn’t
work from http://kernel.ubuntu.com/~kernel-ppa/mainline/
Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the
Well, that means upstream kernel is also affected. Please do a kernel
bisection.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu kernels 5.4.0-51 and 5.4.0-52 break
AFAICT, it affects all later kernels starting after 5.4.0-48 somewhere.
that includes 5.9 and 5.10 which i just installed a couple of days ago.
If you think it would help I can reboot to whichever kernel you want and
post dmesg output.Wondering if this should be posted as a kernel bug
too.
--
Please boot under kernels with the issue, and attach dmesg here?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Interesting, but doesn't seem to be a proper fix. Been running ir-
keytable for years and was never able to use ir-krytable -t as a regular
user. had to redo keymap file going from xubuntu 18.04lts to 20.04lts.
Having to load after boot is not a viable option as this is a frontend
my wife uses
Workaround that seems to work:
Running ir-keytable -t as my user gave "permission denied" on
/dev/input/event16 and /dev/lirc0. After adding my user to the "input"
and "video" groups that own those devices, the remote works correctly.
However, I also have to manually load the custom keymap
Just upgraded to -58 kernel and it broke my remote too. Going back to
-42 kernel fixed it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu kernels 5.4.0-51 and
45 matches
Mail list logo
