From: Sean Young <sean@mess.org>
To: Ralf Schmidt <rds2@gmx.de>
Cc: linux-media@vger.kernel.org
Subject: Re: Missing Protocols ir-keytable Ubuntu 20.04
Date: Fri, 8 May 2020 10:03:19 +0100 [thread overview]
Message-ID: <20200508090319.GA32337@gofer.mess.org> (raw)
In-Reply-To: <6446b77c-e6de-9d0a-2ed3-691481917b80@gmx.de>
Hi Ralf,
On Wed, May 06, 2020 at 02:35:32PM +0200, Ralf Schmidt wrote:
> Only working Receiver: all RF X10 Wireless Receiver
> All Outputs with just upgraded 5.4.0-29-generic Kernel (Ubuntu 20.04LTS)
> and newly installed ir-keytable
>
> ralf@nexus:~$ ir-keytable --version
> IR keytable control version 1.18.0
>
> ralf@nexus:~$ sudo ir-keytable -p all
> [sudo] Passwort für ralf:
> Die Protokolle für das Gerät können nicht geändert werden
> Protokolle geändert in other
Well those messages can't both be true.
> /dev/lirc0: kein Empfangsgerät für unverarbeitetes Infrarot
> BPF-Protokoll rc-mm konnte weder in /etc/rc_keymaps/protocols noch in
> /lib/udev/rc_keymaps/protocols gefunden werden
> BPF-Protokoll imon konnte weder in /etc/rc_keymaps/protocols noch in
> /lib/udev/rc_keymaps/protocols gefunden werden
> BPF-Protokoll cec konnte weder in /etc/rc_keymaps/protocols noch in
> /lib/udev/rc_keymaps/protocols gefunden werden
> BPF-Protokoll xmp konnte weder in /etc/rc_keymaps/protocols noch in
> /lib/udev/rc_keymaps/protocols gefunden werden
> BPF-Protokoll sharp konnte weder in /etc/rc_keymaps/protocols noch in
> /lib/udev/rc_keymaps/protocols gefunden werden
> BPF-Protokoll rc-6 konnte weder in /etc/rc_keymaps/protocols noch in
> /lib/udev/rc_keymaps/protocols gefunden werden
> BPF-Protokoll mce_kbd konnte weder in /etc/rc_keymaps/protocols noch in
> /lib/udev/rc_keymaps/protocols gefunden werden
> BPF-Protokoll sanyo konnte weder in /etc/rc_keymaps/protocols noch in
> /lib/udev/rc_keymaps/protocols gefunden werden
> BPF-Protokoll nec konnte weder in /etc/rc_keymaps/protocols noch in
> /lib/udev/rc_keymaps/protocols gefunden werden
> BPF-Protokoll sony konnte weder in /etc/rc_keymaps/protocols noch in
> /lib/udev/rc_keymaps/protocols gefunden werden
> BPF-Protokoll jvc konnte weder in /etc/rc_keymaps/protocols noch in
> /lib/udev/rc_keymaps/protocols gefunden werden
> BPF-Protokoll rc-5-sz konnte weder in /etc/rc_keymaps/protocols noch in
> /lib/udev/rc_keymaps/protocols gefunden werden
> BPF-Protokoll rc-5 konnte weder in /etc/rc_keymaps/protocols noch in
> /lib/udev/rc_keymaps/protocols gefunden werden
> BPF-Protokoll lirc konnte weder in /etc/rc_keymaps/protocols noch in
> /lib/udev/rc_keymaps/protocols gefunden werden
> BPF-Protokoll unknown konnte weder in /etc/rc_keymaps/protocols noch in
> /lib/udev/rc_keymaps/protocols gefunden werden
Oops. Yes, I broke this. ir-keytable should not be doing this. I'll fix
this; in the mean time those messages can be ignored.
-snip-
> But all the protocols are available
Yes, you are right.
> On more thing: because off the removed -d parameter, Remotes like the
> Technisat TTS35AI are no longer supported, such Type of Remotes are not
> recognized in /sys/class/rc/.
Hmm it would be good to know more about this. What device is this exactly?
It would be good to have lsusb output.
> Sorry for my bad English
You are very clear and thank you for your bug report.
Thanks,
Sean
next prev parent reply other threads:[~2020-05-08 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 12:35 Missing Protocols ir-keytable Ubuntu 20.04 Ralf Schmidt
2020-05-08 9:03 ` Sean Young [this message]
2020-06-02 16:08 ` Sean Young
2020-06-09 6:10 ` Peter Hutterer
2020-06-10 12:43 ` Sean Young
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200508090319.GA32337@gofer.mess.org \
--to=sean@mess.org \
--cc=linux-media@vger.kernel.org \
--cc=rds2@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).