entered the pastebin as a link
my original Xbox DVD dongle stopped working after the latest update. after running:
cat /sys/kernel/debug/usb/devices i see the following for the adapter:
T: Bus=01 Lev=02 Prnt=02 Port=04 Cnt=02 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=045e ProdID=0284 Rev= 0.0a
C:* #Ifs= 2 Cfg#= 1 Atr=00 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=58(unk. ) Sub=42 Prot=00 Driver=(none)
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=16ms
I:* If#= 1 Alt= 0 #EPs= 0 Cls=59(unk. ) Sub=00 Prot=00 Driver=(none)
looks like the driver (im assuming xpad) is not working. any ideas?
The module should be lirc_xbox (IIRC); not xpad. What’s lsmod show?
I have the same issue with the same response from cat /sys/kernel/debug/usb/devices
lsmod does not appear to show lirc_xbox (does show xpad):
Module Size Used by
cmac 16384 1
bnep 20480 2
hci_uart 20480 1
bluetooth 409600 23 hci_uart,bnep
ecdh_generic 36864 1 bluetooth
8021q 32768 0
garp 20480 1 8021q
stp 16384 1 garp
llc 16384 2 garp,stp
iptable_nat 16384 0
nf_conntrack_ipv4 16384 1
nf_defrag_ipv4 16384 1 nf_conntrack_ipv4
nf_nat_ipv4 16384 1 iptable_nat
nf_nat 32768 1 nf_nat_ipv4
nf_conntrack 139264 3 nf_conntrack_ipv4,nf_nat_ipv4,nf_nat
iptable_mangle 16384 0
iptable_filter 16384 0
brcmfmac 262144 0
brcmutil 16384 1 brcmfmac
cfg80211 626688 1 brcmfmac
rfkill 28672 5 bluetooth,cfg80211
xpad 28672 0
ff_memless 16384 1 xpad
snd_bcm2835 32768 0
snd_pcm 114688 1 snd_bcm2835
snd_timer 36864 1 snd_pcm
snd 86016 3 snd_timer,snd_bcm2835,snd_pcm
bcm2835_thermal 16384 0
bcm2835_gpiomem 16384 0
uio_pdrv_genirq 16384 0
fixed 16384 0
uio 20480 1 uio_pdrv_genirq
ip_tables 24576 3 iptable_mangle,iptable_filter,iptable_nat
x_tables 36864 3 iptable_mangle,ip_tables,iptable_filter
ipv6 475136 44
I also tried this with results shown (again this has been functional for years before last night’s update):
osmc@OSMC-RPi3:~$ sudo systemctl stop lircd_helper@lirc0
osmc@OSMC-RPi3:~$ mode2 -d /dev/lirc0
mode2: could not get file information for /dev/lirc0
mode2: default_init(): No such file or directory
osmc@OSMC-RPi3:~$ sudo systemctl start lircd_helper@lirc0
Job for lircd_helper@lirc0.service failed because the control process exited with error code.
See “systemctl status lircd_helper@lirc0.service” and “journalctl -xe” for details.
osmc@OSMC-RPi3:~$ systemctl status lircd_helper@lirc0.service
- lircd_helper@lirc0.service - lircd remote support
Loaded: loaded (/lib/systemd/system/lircd_helper@.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2018-11-03 16:03:11 ADT; 3min 36s ago
Process: 1255 ExecStart=/bin/sh -c /var/run/lirc/lircd-lirc0.sh (code=exited, status=127)
Nov 03 16:03:11 OSMC-RPi3 systemd[1]: Starting lircd remote support…
Nov 03 16:03:11 OSMC-RPi3 sh[1255]: /bin/sh: 1: /var/run/lirc/lircd-lirc0.sh: not found
Nov 03 16:03:11 OSMC-RPi3 systemd[1]: lircd_helper@lirc0.service: Control process exited, code=exited status=
Nov 03 16:03:11 OSMC-RPi3 systemd[1]: Failed to start lircd remote support.
Nov 03 16:03:11 OSMC-RPi3 systemd[1]: lircd_helper@lirc0.service: Unit entered failed state.
Nov 03 16:03:11 OSMC-RPi3 systemd[1]: lircd_helper@lirc0.service: Failed with result ‘exit-code’.
osmc@OSMC-RPi3:~$ journalctl -xe
– Defined-By: systemd
– Support: Debian -- User Support
– Unit lircd_helper@lirc0.service has failed.
– The result is failed.
Nov 03 16:00:32 OSMC-RPi3 systemd[1]: lircd_helper@lirc0.service: Unit entered failed state.
Nov 03 16:00:32 OSMC-RPi3 systemd[1]: lircd_helper@lirc0.service: Failed with result ‘exit-code’.
Nov 03 16:00:32 OSMC-RPi3 sudo[1200]: pam_unix(sudo:session): session closed for user root
Nov 03 16:00:37 OSMC-RPi3 ntpd[615]: 206.108.0.131 local addr 192.168.25.93 →
Nov 03 16:02:22 OSMC-RPi3 systemd[1]: Starting Cleanup of Temporary Directories…
– Subject: Unit systemd-tmpfiles-clean.service has begun start-up
– Defined-By: systemd
– Support: Debian -- User Support
– Unit systemd-tmpfiles-clean.service has begun starting up.
Nov 03 16:02:22 OSMC-RPi3 systemd[1]: Started Cleanup of Temporary Directories.
– Subject: Unit systemd-tmpfiles-clean.service has finished start-up
– Defined-By: systemd
– Support: Debian -- User Support
– Unit systemd-tmpfiles-clean.service has finished starting up.
– The start-up result is done.
Nov 03 16:02:56 OSMC-RPi3 sudo[1244]: osmc : TTY=pts/0 ; PWD=/home/osmc ; USER=root ; COMMAND=/bin/system
Nov 03 16:02:56 OSMC-RPi3 sudo[1244]: pam_unix(sudo:session): session opened for user root by osmc(uid=0)
Nov 03 16:02:56 OSMC-RPi3 sudo[1244]: pam_unix(sudo:session): session closed for user root
Nov 03 16:03:11 OSMC-RPi3 sudo[1252]: osmc : TTY=pts/0 ; PWD=/home/osmc ; USER=root ; COMMAND=/bin/system
Nov 03 16:03:11 OSMC-RPi3 sudo[1252]: pam_unix(sudo:session): session opened for user root by osmc(uid=0)
Nov 03 16:03:11 OSMC-RPi3 systemd[1]: Starting lircd remote support…
– Subject: Unit lircd_helper@lirc0.service has begun start-up
– Defined-By: systemd
– Support: Debian -- User Support
– Unit lircd_helper@lirc0.service has begun starting up.
Nov 03 16:03:11 OSMC-RPi3 sh[1255]: /bin/sh: 1: /var/run/lirc/lircd-lirc0.sh: not found
Nov 03 16:03:11 OSMC-RPi3 systemd[1]: lircd_helper@lirc0.service: Control process exited, code=exited status=
Nov 03 16:03:11 OSMC-RPi3 systemd[1]: Failed to start lircd remote support.
– Subject: Unit lircd_helper@lirc0.service has failed
– Defined-By: systemd
– Support: Debian -- User Support
– Unit lircd_helper@lirc0.service has failed.
– The result is failed.
Nov 03 16:03:11 OSMC-RPi3 systemd[1]: lircd_helper@lirc0.service: Unit entered failed state.
I suspect there have been some changes with LIRC (will investigate). This is why we want to stay on 4.14 for a while.
Sam
Remote issues should be fixed.
I’d appreciate it if you could test this and provide feedback before we potentially release this as an update to other users. To test this update:
- Login via the command line
- Edit the file
/etc/apt/sources.list - Add the following line:
deb http://apt.osmc.tv stretch-devel main - Run the following commands to update:
sudo apt-get update && sudo apt-get dist-upgrade && reboot - Your system should have have received the update.
Please see if the issue is resolved.
I also recommend you edit /etc/apt/sources.list again and remove the line that you added after updating. This will return you to the normal update channel.
Working for me also
Thanks for confirming. We’ll roll this out to all users shortly.
Just to confirm this also worked for me, On a Pi 1,& 3 many thanks
1 Like
Works like a charm on my pi3! Thanks alot!!