Volumio 3 and IR Remote Control Apple A1294

That’s expected, but the remote’s play/pause button is still dedidated to the toggle function and can be used instead of the menu button.

Yes, but I don’t think it has an effect on the pointer control issue.

That’s because the function assigned to KEY_ENTER is “volumio volume toggle”. While “volumio toggle” toggles between play and pause, “volumio volume toggle” toggles between muted and unmuted (for more info on Volumio’s command line client: Command Line Client - Volumio Documentation).

Please post the result of

systemctl status -l lircmd.service

Here it is …
systemctl status -l lircmd.service
● lircmd.service - Convert IR remotes button presses to mouse movements and clicks
Loaded: loaded (/lib/systemd/system/lircmd.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2022-09-19 15:44:22 UTC; 32min ago
Docs: man:lircmd(8)
LIRC - Linux Infrared Remote Control
Main PID: 3065 (lircmd)
Tasks: 1 (limit: 2133)
CGroup: /system.slice/lircmd.service
└─3065 /usr/sbin/lircmd --nodaemon

Sep 19 15:44:22 myvolumio systemd[1]: Started Convert IR remotes button presses to mouse movements and clicks.
Sep 19 15:44:22 myvolumio lircd-0.10.1[3065]: Notice: lircmd: Opening log, level: Notice
Sep 19 15:44:22 myvolumio lircmd[3065]: lircd-0.10.1[3065]: Notice: lircmd: Opening log, level: Notice
volumio@myvolumio:~$

Please post the output of

cat /var/log/Xorg.0.log

cat /var/log/Xorg.0.log

[ 45.368]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[ 45.368] Build Operating System: Linux 5.4.0-109-generic armv8l Raspbian
[ 45.368] Current Operating System: Linux myvolumio 5.10.92-v7+ #1514 SMP Mon Jan 17 17:36:39 GMT 2022 armv7l
[ 45.368] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 splash plymouth.ignore-serial-consoles dwc_otg.fiq_enable=1 dwc_otg.fiq_fsm_enable=1 dwc_otg.fiq_fsm_mask=0xF dwc_otg.nak_holdoff=1 quiet console=ttyS0,115200 console=tty1 imgpart=/dev/mmcblk0p2 imgfile=/volumio_current.sqsh rootwait bootdelay=5 elevator=noop logo.nologo vt.global_cursor_default=0 net.ifnames=0 snd-bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 loglevel=0
[ 45.368] Build Date: 04 August 2022 12:56:42PM
[ 45.368] xorg-server 2:1.20.4-1+rpt4+deb10u5 (Debian -- User Support)
[ 45.368] Current version of pixman: 0.36.0
[ 45.368] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 45.368] Markers: (–) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 45.369] (==) Log file: “/var/log/Xorg.0.log”, Time: Mon Sep 19 15:33:28 2022
[ 45.377] (==) Using config directory: “/etc/X11/xorg.conf.d”
[ 45.377] (==) Using system config directory “/usr/share/X11/xorg.conf.d”
[ 45.383] (==) No Layout section. Using the first Screen section.
[ 45.383] (==) No screen section available. Using defaults.
[ 45.383] (
) |–>Screen “Default Screen Section” (0)
[ 45.383] (**) | |–>Monitor “”
[ 45.390] (==) No monitor specified for screen “Default Screen Section”.
Using a default monitor configuration.
[ 45.390] (==) Automatically adding devices
[ 45.390] (==) Automatically enabling devices
[ 45.390] (==) Automatically adding GPU devices
[ 45.390] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 45.391] (WW) The directory “/usr/share/fonts/X11/cyrillic” does not exist.
[ 45.391] Entry deleted from font path.
[ 45.393] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 45.393] (==) ModulePath set to “/usr/lib/xorg/modules”
[ 45.393] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 45.393] (II) Loader magic: 0x1fdf80
[ 45.393] (II) Module ABI versions:
[ 45.393] X.Org ANSI C Emulation: 0.4
[ 45.393] X.Org Video Driver: 24.0
[ 45.393] X.Org XInput driver : 24.1
[ 45.393] X.Org Server Extension : 10.0
[ 45.396] (–) using VT number 2

[ 45.396] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 45.396] (II) no primary bus or device found
[ 45.396] (II) LoadModule: “glx”
[ 45.399] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 45.486] (II) Module glx: vendor=“X.Org Foundation”
[ 45.486] compiled for 1.20.4, module version = 1.0.0
[ 45.486] ABI class: X.Org Server Extension, version 10.0
[ 45.486] (==) Matched modesetting as autoconfigured driver 0
[ 45.486] (==) Matched fbdev as autoconfigured driver 1
[ 45.486] (==) Assigned the driver to the xf86ConfigLayout
[ 45.486] (II) LoadModule: “modesetting”
[ 45.488] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 45.495] (II) Module modesetting: vendor=“X.Org Foundation”
[ 45.496] compiled for 1.20.4, module version = 1.20.4
[ 45.496] Module class: X.Org Video Driver
[ 45.496] ABI class: X.Org Video Driver, version 24.0
[ 45.496] (II) LoadModule: “fbdev”
[ 45.496] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 45.499] (II) Module fbdev: vendor=“X.Org Foundation”
[ 45.499] compiled for 1.20.3, module version = 0.5.0
[ 45.499] Module class: X.Org Video Driver
[ 45.499] ABI class: X.Org Video Driver, version 24.0
[ 45.499] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 45.499] (II) FBDEV: driver for framebuffer: fbdev
[ 45.515] (WW) Falling back to old probe method for modesetting
[ 45.515] (EE) open /dev/dri/card0: No such file or directory
[ 45.515] (WW) Falling back to old probe method for fbdev
[ 45.515] (II) Loading sub module “fbdevhw”
[ 45.515] (II) LoadModule: “fbdevhw”
[ 45.515] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 45.518] (II) Module fbdevhw: vendor=“X.Org Foundation”
[ 45.518] compiled for 1.20.4, module version = 0.0.2
[ 45.518] ABI class: X.Org Video Driver, version 24.0
[ 45.518] (II) FBDEV(0): using default device
[ 45.519] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 45.519] (II) FBDEV(0): Creating default Display subsection in Screen section
“Default Screen Section” for depth/fbbpp 24/32
[ 45.519] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[ 45.519] (==) FBDEV(0): RGB weight 888
[ 45.519] (==) FBDEV(0): Default visual is TrueColor
[ 45.519] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[ 45.519] (II) FBDEV(0): hardware: BCM2708 FB (video memory: 7011kB)
[ 45.519] (DB) xf86MergeOutputClassOptions unsupported bus type 0
[ 45.519] (II) FBDEV(0): checking modes against framebuffer device…
[ 45.519] (II) FBDEV(0): checking modes against monitor…
[ 45.519] (II) FBDEV(0): Virtual size is 1824x984 (pitch 1824)
[ 45.519] () FBDEV(0): Built-in mode “current”
[ 45.519] (==) FBDEV(0): DPI set to (96, 96)
[ 45.519] (II) Loading sub module “fb”
[ 45.519] (II) LoadModule: “fb”
[ 45.519] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 45.526] (II) Module fb: vendor=“X.Org Foundation”
[ 45.526] compiled for 1.20.4, module version = 1.0.0
[ 45.526] ABI class: X.Org ANSI C Emulation, version 0.4
[ 45.526] (
) FBDEV(0): using shadow framebuffer
[ 45.526] (II) Loading sub module “shadow”
[ 45.526] (II) LoadModule: “shadow”
[ 45.527] (II) Loading /usr/lib/xorg/modules/libshadow.so
[ 45.530] (II) Module shadow: vendor=“X.Org Foundation”
[ 45.530] compiled for 1.20.4, module version = 1.1.0
[ 45.530] ABI class: X.Org ANSI C Emulation, version 0.4
[ 45.530] (II) UnloadModule: “modesetting”
[ 45.530] (II) Unloading modesetting
[ 45.564] (==) FBDEV(0): Backing store enabled
[ 45.569] (==) FBDEV(0): DPMS enabled
[ 45.571] (II) Initializing extension Generic Event Extension
[ 45.572] (II) Initializing extension SHAPE
[ 45.572] (II) Initializing extension MIT-SHM
[ 45.573] (II) Initializing extension XInputExtension
[ 45.578] (II) Initializing extension XTEST
[ 45.579] (II) Initializing extension BIG-REQUESTS
[ 45.580] (II) Initializing extension SYNC
[ 45.581] (II) Initializing extension XKEYBOARD
[ 45.582] (II) Initializing extension XC-MISC
[ 45.583] (II) Initializing extension SECURITY
[ 45.584] (II) Initializing extension XFIXES
[ 45.585] (II) Initializing extension RENDER
[ 45.586] (II) Initializing extension RANDR
[ 45.588] (II) Initializing extension COMPOSITE
[ 45.591] (II) Initializing extension DAMAGE
[ 45.592] (II) Initializing extension MIT-SCREEN-SAVER
[ 45.593] (II) Initializing extension DOUBLE-BUFFER
[ 45.594] (II) Initializing extension RECORD
[ 45.595] (II) Initializing extension DPMS
[ 45.596] (II) Initializing extension Present
[ 45.597] (II) Initializing extension DRI3
[ 45.597] (II) Initializing extension X-Resource
[ 45.598] (II) Initializing extension XVideo
[ 45.599] (II) Initializing extension XVideo-MotionCompensation
[ 45.599] (II) Initializing extension SELinux
[ 45.599] (II) SELinux: Disabled on system
[ 45.599] (II) Initializing extension GLX
[ 45.600] (II) AIGLX: Screen 0 is not DRI2 capable
[ 47.033] (II) IGLX: Loaded and initialized swrast
[ 47.033] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 47.033] (II) Initializing extension XFree86-VidModeExtension
[ 47.034] (II) Initializing extension XFree86-DGA
[ 47.035] (II) Initializing extension XFree86-DRI
[ 47.038] (II) Initializing extension DRI2
[ 47.376] (II) config/udev: Adding input device gpio_ir_recv (/dev/input/event2)
[ 47.377] () gpio_ir_recv: Applying InputClass “libinput keyboard catchall”
[ 47.377] (II) LoadModule: “libinput”
[ 47.377] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[ 47.411] (II) Module libinput: vendor=“X.Org Foundation”
[ 47.411] compiled for 1.20.3, module version = 0.28.2
[ 47.411] Module class: X.Org XInput Driver
[ 47.411] ABI class: X.Org XInput driver, version 24.1
[ 47.411] (II) Using input driver ‘libinput’ for ‘gpio_ir_recv’
[ 47.411] (
) gpio_ir_recv: always reports core events
[ 47.411] () Option “Device” “/dev/input/event2”
[ 47.412] (
) Option “_source” “server/udev”
[ 47.443] (II) event2 - gpio_ir_recv: is tagged by udev as: Keyboard Pointingstick
[ 47.445] (II) event2 - gpio_ir_recv: device is a pointer
[ 47.445] (II) event2 - gpio_ir_recv: device is a keyboard
[ 47.445] (II) event2 - gpio_ir_recv: device removed
[ 47.501] (II) libinput: gpio_ir_recv: needs a virtual subdevice
[ 47.501] () Option “config_info” “udev:/sys/devices/platform/ir-receiver@11/rc/rc0/input14/event2”
[ 47.501] (II) XINPUT: Adding extended input device “gpio_ir_recv” (type: MOUSE, id 6)
[ 47.501] (
) Option “AccelerationScheme” “none”
[ 47.501] () gpio_ir_recv: (accel) selected scheme none/0
[ 47.501] (
) gpio_ir_recv: (accel) acceleration factor: 2.000
[ 47.501] () gpio_ir_recv: (accel) acceleration threshold: 4
[ 47.505] (II) event2 - gpio_ir_recv: is tagged by udev as: Keyboard Pointingstick
[ 47.506] (II) event2 - gpio_ir_recv: device is a pointer
[ 47.506] (II) event2 - gpio_ir_recv: device is a keyboard
[ 47.512] (II) config/udev: Adding input device Logitech K400 Plus (/dev/input/event0)
[ 47.512] (
) Logitech K400 Plus: Applying InputClass “libinput pointer catchall”
[ 47.512] () Logitech K400 Plus: Applying InputClass “libinput keyboard catchall”
[ 47.512] (II) Using input driver ‘libinput’ for ‘Logitech K400 Plus’
[ 47.512] (
) Logitech K400 Plus: always reports core events
[ 47.512] () Option “Device” “/dev/input/event0”
[ 47.512] (
) Option “_source” “server/udev”
[ 47.522] (II) event0 - Logitech K400 Plus: is tagged by udev as: Keyboard Mouse
[ 47.522] (II) event0 - Logitech K400 Plus: device is a pointer
[ 47.522] (II) event0 - Logitech K400 Plus: device is a keyboard
[ 47.524] (II) event0 - Logitech K400 Plus: device removed
[ 47.581] (II) libinput: Logitech K400 Plus: needs a virtual subdevice
[ 47.581] () Option “config_info” “udev:/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.2/0003:046D:C52B.0003/0003:046D:404D.0004/input/input12/event0”
[ 47.581] (II) XINPUT: Adding extended input device “Logitech K400 Plus” (type: MOUSE, id 7)
[ 47.582] (
) Option “AccelerationScheme” “none”
[ 47.582] () Logitech K400 Plus: (accel) selected scheme none/0
[ 47.582] (
) Logitech K400 Plus: (accel) acceleration factor: 2.000
[ 47.582] () Logitech K400 Plus: (accel) acceleration threshold: 4
[ 47.591] (II) event0 - Logitech K400 Plus: is tagged by udev as: Keyboard Mouse
[ 47.591] (II) event0 - Logitech K400 Plus: device is a pointer
[ 47.591] (II) event0 - Logitech K400 Plus: device is a keyboard
[ 47.596] (II) config/udev: Adding input device Logitech K400 Plus (/dev/input/mouse0)
[ 47.597] (II) No input driver specified, ignoring this device.
[ 47.597] (II) This device may have been added with another device file.
[ 47.614] (
) gpio_ir_recv: Applying InputClass “libinput keyboard catchall”
[ 47.614] (II) Using input driver ‘libinput’ for ‘gpio_ir_recv’
[ 47.614] () gpio_ir_recv: always reports core events
[ 47.614] (
) Option “Device” “/dev/input/event2”
[ 47.614] () Option “_source” “_driver/libinput”
[ 47.614] (II) libinput: gpio_ir_recv: is a virtual subdevice
[ 47.614] (
) Option “config_info” “udev:/sys/devices/platform/ir-receiver@11/rc/rc0/input14/event2”
[ 47.614] (II) XINPUT: Adding extended input device “gpio_ir_recv” (type: KEYBOARD, id 8)
[ 47.614] () Option “xkb_model” “pc105”
[ 47.614] (
) Option “xkb_layout” “us”
[ 47.615] () Logitech K400 Plus: Applying InputClass “libinput pointer catchall”
[ 47.615] (
) Logitech K400 Plus: Applying InputClass “libinput keyboard catchall”
[ 47.615] (II) Using input driver ‘libinput’ for ‘Logitech K400 Plus’
[ 47.615] () Logitech K400 Plus: always reports core events
[ 47.615] (
) Option “Device” “/dev/input/event0”
[ 47.615] () Option “_source” “_driver/libinput”
[ 47.615] (II) libinput: Logitech K400 Plus: is a virtual subdevice
[ 47.615] (
) Option “config_info” “udev:/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.2/0003:046D:C52B.0003/0003:046D:404D.0004/input/input12/event0”
[ 47.615] (II) XINPUT: Adding extended input device “Logitech K400 Plus” (type: KEYBOARD, id 9)
[ 47.615] () Option “xkb_model” “pc105”
[ 47.615] (
) Option “xkb_layout” “us”
[ 47.627] (II) config/udev: removing device gpio_ir_recv
[ 47.627] (II) UnloadModule: “libinput”
[ 47.627] (II) config/udev: removing device gpio_ir_recv
[ 47.628] (II) event2 - gpio_ir_recv: device removed
[ 47.690] (II) UnloadModule: “libinput”
[ 47.692] (II) config/udev: Adding input device gpio_ir_recv (/dev/input/event2)
[ 47.692] () gpio_ir_recv: Applying InputClass “libinput keyboard catchall”
[ 47.692] (II) Using input driver ‘libinput’ for ‘gpio_ir_recv’
[ 47.692] (
) gpio_ir_recv: always reports core events
[ 47.692] () Option “Device” “/dev/input/event2”
[ 47.692] (
) Option “_source” “server/udev”
[ 47.696] (II) event2 - gpio_ir_recv: is tagged by udev as: Keyboard Pointingstick
[ 47.697] (II) event2 - gpio_ir_recv: device is a pointer
[ 47.697] (II) event2 - gpio_ir_recv: device is a keyboard
[ 47.698] (II) event2 - gpio_ir_recv: device removed
[ 47.740] (II) libinput: gpio_ir_recv: needs a virtual subdevice
[ 47.740] () Option “config_info” “udev:/sys/devices/platform/ir-receiver@11/rc/rc0/input14/event2”
[ 47.740] (II) XINPUT: Adding extended input device “gpio_ir_recv” (type: MOUSE, id 6)
[ 47.741] (
) Option “AccelerationScheme” “none”
[ 47.741] () gpio_ir_recv: (accel) selected scheme none/0
[ 47.741] (
) gpio_ir_recv: (accel) acceleration factor: 2.000
[ 47.741] () gpio_ir_recv: (accel) acceleration threshold: 4
[ 47.745] (II) event2 - gpio_ir_recv: is tagged by udev as: Keyboard Pointingstick
[ 47.745] (II) event2 - gpio_ir_recv: device is a pointer
[ 47.745] (II) event2 - gpio_ir_recv: device is a keyboard
[ 47.747] (
) gpio_ir_recv: Applying InputClass “libinput keyboard catchall”
[ 47.747] (II) Using input driver ‘libinput’ for ‘gpio_ir_recv’
[ 47.747] () gpio_ir_recv: always reports core events
[ 47.747] (
) Option “Device” “/dev/input/event2”
[ 47.747] () Option “_source” “_driver/libinput”
[ 47.747] (II) libinput: gpio_ir_recv: is a virtual subdevice
[ 47.747] (
) Option “config_info” “udev:/sys/devices/platform/ir-receiver@11/rc/rc0/input14/event2”
[ 47.748] (II) XINPUT: Adding extended input device “gpio_ir_recv” (type: KEYBOARD, id 8)
[ 47.748] () Option “xkb_model” “pc105”
[ 47.748] (
) Option “xkb_layout” “us”
[ 47.748] (WW) Option “xkb_variant” requires a string value
[ 47.748] (WW) Option “xkb_options” requires a string value
[ 700.072] (II) config/udev: Adding input device lircmd (/dev/input/mouse1)
[ 700.072] (II) No input driver specified, ignoring this device.
[ 700.072] (II) This device may have been added with another device file.
[ 700.242] (II) config/udev: Adding input device lircmd (/dev/input/event1)
[ 700.242] () lircmd: Applying InputClass “libinput pointer catchall”
[ 700.242] (II) Using input driver ‘libinput’ for ‘lircmd’
[ 700.242] (
) lircmd: always reports core events
[ 700.242] () Option “Device” “/dev/input/event1”
[ 700.242] (
) Option “_source” “server/udev”
[ 700.245] (II) event1 - lircmd: is tagged by udev as: Mouse
[ 700.245] (II) event1 - lircmd: device is a pointer
[ 700.245] (II) event1 - lircmd: device removed
[ 700.350] () Option “config_info” “udev:/sys/devices/virtual/input/input15/event1”
[ 700.350] (II) XINPUT: Adding extended input device “lircmd” (type: MOUSE, id 10)
[ 700.351] (
) Option “AccelerationScheme” “none”
[ 700.351] () lircmd: (accel) selected scheme none/0
[ 700.351] (
) lircmd: (accel) acceleration factor: 2.000
[ 700.351] (**) lircmd: (accel) acceleration threshold: 4
[ 700.353] (II) event1 - lircmd: is tagged by udev as: Mouse
[ 700.353] (II) event1 - lircmd: device is a pointer
volumio@myvolumio:~$

Thanks, log looks normal.

Please head over to the IR controller plugin’s config page, change the chosen remote control profile to something other and save it. Then select to your A1294 profile again and save it.

I assigned the Yamaha RAV363, clicked save - message “config saved/configuration successfull changed”
After that I assigned back the Apple Remote 1294, clicked save - message “config saved/configuration successfull changed”
Unfortunaltely the same behavior as before

Ok, next thing you could try is executing

systemctl start lircd-uinput.service

On my system I had started this service at first, too. But since pointer control worked after a reboot even without starting this service (again), I think it is not necessary… but we will see. :slight_smile:

What I did:

sudo systemctl start lircd-uinput.service
volumio@myvolumio:~$ exit
logout

reboot

After reboot:
volumio@myvolumio:~$ ps -ef| grep lircd-uinput
volumio 1877 1822 0 16:49 pts/0 00:00:00 grep lircd-uinput

so the service is not running.

Now started the service:
sudo systemctl start lircd-uinput.service
volumio@myvolumio:~$ ps -ef| grep lircd-uinput
root 1916 1 0 16:49 ? 00:00:00 /usr/sbin/lircd-uinput
volumio 1927 1822 0 16:49 pts/0 00:00:00 grep lircd-uinput

Service is running.

Nothing changed

The LIRC documentation states one should put the following section in one’s Xorg.conf file:

Section "InputDevice"
   Identifier  "LIRC-Mouse"
   Driver      "mouse"
   Option      "Protocol" "IntelliMouse"
   Option      "SendCoreEvents"
   Option      "Buttons" "5"
   Option      "ZAxisMapping" "4 5"
EndSection

So I initially created a file named “80-lircpointer.conf” in “/etc/X11/xorg.conf.d” but had the impression that it wasn’t necessary, as the pointer control still worked after renaming it to “80-lircpointer.conf_” and rebooting… But you may also check if adding a file “/etc/X11/xorg.conf.d/80-lircpointer.conf” with the content above helps.

1 Like

What I did:

volumio@myvolumio:~$ cd /etc/X11/xorg.conf.d
volumio@myvolumio:/etc/X11/xorg.conf.d$ ls
95-touch_display-plugin.conf
volumio@myvolumio:/etc/X11/xorg.conf.d$ sudo nano 80-lircpointer.conf
volumio@myvolumio:/etc/X11/xorg.conf.d$ cat 80-lircpointer.conf
Section “InputDevice”
Identifier “LIRC-Mouse”
Driver “mouse”
Option “Protocol” “IntelliMouse”
Option “SendCoreEvents”
Option “Buttons” “5”
Option “ZAxisMapping” “4 5”
EndSection

volumio@myvolumio:/etc/X11/xorg.conf.d$ exit
logout

reboot

Nothing changed.

In which country you are located?

Do have an Apple A1294 as IR remote control on a Raspberry Pi 3 Model B+ for testing available?

No, but I maybe found something interesting: On my system I just ran “systemctl enable lircmd.service” and rebooted. After rebooting initially the pointer control didn’t work until I ran

systemctl restart lircmd.service

This is likely to happen, because the IR controller plugin has not fully started when systemd already starts “lircmd.service”.

So please also try if the restart command helps.

On my system I just ran “systemctl enable lircmd.service” and rebooted. After rebooting initially the pointer control didn’t work

This is the same on my system.
Before rebooting I typed command “systemctl enable lircmd.service” and after the boot the service was not running:
Welcome to Volumio for Raspberry Pi (5.10.92-v7+ armv7l)
volumio@myvolumio:~$ ps -ef|grep lircmd
volumio 1686 1455 0 19:38 pts/0 00:00:00 grep lircmd
volumio@myvolumio:~$

Then I typed your command for restarting the service:
volumio@myvolumio:~$ sudo systemctl restart lircmd.service
volumio@myvolumio:~$ ps -ef|grep lircmd
root 1713 1 0 19:42 ? 00:00:00 /usr/sbin/lircmd --nodaemon
volumio 1722 1455 0 19:42 pts/0 00:00:00 grep lircmd
volumio@myvolumio:~$

Now it runs, but the behavior of the MENU button doesn’t change.
No navigation after pressing MENU

I’m afraid the problem is simply caused by the fact that the key to activate the cursor control does not create an independent second level for the other keys, so that these keys, detached from their “normal” function, can be used to control the cursor.

Simply said: Keys that are already assigned with a function in “lircrc” can no longer be used for cursor control.

You may test this by commenting out the sections for e.g. “KEY_UP” and “KEY_DOWN” in your lircrc:


#begin
#prog = irexec
#button = KEY_UP
#config = /usr/local/bin/volumio volume plus
#end
#begin
#prog = irexec
#button = KEY_DOWN
#config = /usr/local/bin/volumio volume minus
#end

After saving the modified lircrc temporarily activate another profile as described above and then return to the A1294 profile.

Good morning gvolt,
a new day for analyzing :smiley:

What I did regarding your last post:

volumio@myvolumio:/etc/lirc$ cd /etc/lirc
volumio@myvolumio:/etc/lirc$ sudo nano lircrc
volumio@myvolumio:/etc/lirc$ cat lircrc

begin
prog = irexec
button = KEY_PLAY
config = /usr/local/bin/volumio toggle
end
begin
prog = irexec
button = KEY_ENTER
config = /usr/local/bin/volumio volume toggle
end
#begin
#prog = irexec
#button = KEY_UP
#config = /usr/local/bin/volumio volume plus
#end
#begin
#prog = irexec
#button = KEY_DOWN
#config = /usr/local/bin/volumio volume minus
#end
begin
prog = irexec
button = KEY_LEFT
config = /usr/local/bin/volumio previous
end
begin
prog = irexec
button = KEY_RIGHT
config = /usr/local/bin/volumio next
end

volumio@myvolumio:/etc/lirc$ sudo cp lircrc "/data/INTERNAL/ir_controller/configurations/Apple Remote A1294"

Activated another profile, saved and reactivated A1294 profile and saved

Start playing music - Okay
used up/down button - as expected no reaction
pressed MENU button
used up/down button - unfortunately no reaction

reboot

pressed MENU button
used up/down button - unfortunately no reaction

Deactivated also KEY_LEFT and KEY_RIGHT maybe the cursor has to be moved before UP/DOWN

Activated another profile, saved and reactivated my A1294 profile, saved

Unfortunately no navigation after pressing MENU

I’m very short of time ATM, but are you able to copy the whole “lircmd.conf” file from your Pi and upload it here?

I uploaded all files from /etc/lirc because these are the same as in my dir "/data/INTERNAL/ir_controller/configurations/Apple Remote A1294"

lircrc.zip (1.8 KB)

I forgot a file and a directory, which I appended here.
irexec.zip (5.6 KB)

There is a subdir called lircd.conf.d with a file named devinput.lircd.conf
This file contains another HEX code KEY_MENU 139
I changed the Hex for KEY_MENU from 0xC0 to 139 in lircd.conf and copied it to my dir, but no effect.
So I edited it back to 0xC0 .

I have only had a chance to skim the files. They look ok IMHO.

Could you check if the problem persists when you run Volumio with the K400 (and any other) keyboard disconnected?