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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu kernels
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu kernels
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu
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
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,
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 Ubuntu
Bugs, which is
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 Ubuntu
Bugs, which is subscribed
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:
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
I've emailed the person that commited them. With luck.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
To manage
I have no idea how to do that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
To manage notifications about this bug go
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
To
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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.
--
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901089
Title:
Ubuntu kernels 5.4.0-51 and 5.4.0-52 break
memtest86+ freezes on my am4 ryzen 3 2200G and 3200G systems. Runs fine
on all my older systems. And Theirs nothing wrong with the memory on the
amd system. Multiple passes with another tester.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Same here. Reported to
https://bugzilla.kernel.org/show_bug.cgi?id=204325
Covers all 5.2.x kernels up to 5.2.5. No video, no KB response. But system
runs. Can ssh into it. Runs fine on kernels up to 5.1.21.
Ryzen 3 2200G using internal video.
** Bug watch added: Linux Kernel Bug Tracker #204325
** Summary changed:
- vlc liblirc-client0 depends breaks kernel lirc
+ ir-keytable -c -w /etc/rc_keymaps/file
** Description changed:
- Subject pretty much says it all. Installing vlc also installs liblirc-
- client0. This hoses up kernel lirc by not allowing some key codes to be
- passed to
Has to be the right shift key on my 18.04lts system, but I've always
just used tapping the Esc key immediately after post until the grub menu
comes up. I explained earlier how to remove the .24 kernel. But don't
try to remove the one you are running at the time. Not sure what would
happen then.
Easiest thing to do is just delete the .24 kernel. During boot, start
tapping the esc key repeatedly. You should get the grub menu. Select the
advanced option, and then load the last good kernel, which should be the
.23 one if you've kept the system up to date. Once it boots and
everything is
I only had the slow boot problem on 2 out of 3 systems with the .24
kernel. Both systems that had problems had single ssd drives in them.
One was an ECS GF8200A mb and the other was a jetway GF8200 based mb.
The system that didn't have a problem was also an ECS GF8200A mb, but
does not have a ssd
I had already installed everything from the proposed mirror using
software updater, but it didn't install the new .26 kernel on the 2
affected machines. So I installed the image, headers, module-extra
packages using apt-get install /bioic-proposed. that
worked and everything worked fine afterwards
Don't know why the new kernel didn't install from the software updater,
but after manually installing it, it works fine. Now to do the same on
other machine. Funny it all installed fine with the software updater on
my main machine.
--
You received this bug notification because you are a member
After turning on developer options for pre-release upgrades and
installing a lot of stuff, I still have the same problem with the slow
boot on the 2 machines I updated. uname-a shows same as before.Is that
normal? I turned off developer stuff afterwards. Since 4.15.0-23 works
fine, should I just
Public bug reported:
Last software update with kernel 4.15.0.24.26 causes systems with sata ssd
drives to take 5-10 minutes to init. All previous kernels booted quick. Going
back to 4.15.0.23.25 works fine. Didn't see any different Failed commands in
kern.log Don't know if this will help as i
OK, I changed one key code and then issued this command;
root@mythfe0:/home/wes# ir-keytable -c -w /etc/rc_keymaps/myremotes
Then tested that it worked like this]
root@mythfe0:/home/wes# ir-keytable -t
Testing events. Please, press CTRL-C to abort.
555.460958: event type EV_MSC(0x04): scancode =
having got ir-keytable the way I want it and all key codes working with
vlc and liblic-client0 removed, I then reinstalled vlc and all the key
codes still worked, even after a reboot. So now I'm guessing that
liblirc-client0 prevents proper setup of the key codes if it is
installed, but after it's
** Description changed:
- Subject pretty says it all. Installing vlc also installs liblirc-
+ Subject pretty much says it all. Installing vlc also installs liblirc-
client0. This hoses up kernel lirc by not allowing some key codes to be
- passed to apps. ir-table -t shows it is working fine.
Public bug reported:
Subject pretty says it all. Installing vlc also installs liblirc-
client0. This hoses up kernel lirc by not allowing some key codes to be
passed to apps. ir-table -t shows it is working fine. Removing liblirc-
client0 fixes the problem but also removes vlc.
** Affects: vlc
42 matches
Mail list logo
