lol I am not a Window operating system fan. running 64 bit generic
I moved the command to the very end of autostart.sh and it seems to be working now
lol I am not a Window operating system fan. running 64 bit generic
I moved the command to the very end of autostart.sh and it seems to be working now
I mean what the problem with autostart.sh?RC6 is still enabled in kernel as module. As before. But maybe with linux version bump something has been changed.
And btw: on which image is that? Which system? I asked around and Ultra2 with Generic image uses an RC6 remote and still working fine.
I'm not sure, when I run the echo command above from command prompt the rc-6 protocol is enabled. When I do it inside the autostart.sh it doesn't get enabled.
this can be determined by running ip-keytable at the prompt. BTW there are about 5-6 protocols supported but only lirc is enable in the .004 version.
And as to the windows comment above ... go wash your mouth out with soap for using foul language!
And the problem is what exactly? Be sure to have UNIX formated file autostart.sh if editing on windows.
The problem is why do I have to run that command to get rc-6 enabled in lirc when it worked fine 2 alphas ago.
I have a setup where I use ir blasting with my librelec. I have autostart setup to disable and then reenable lirc using my setup. In the last 2 versions my remotes stopped working all together.
I noticed that when runnning ir-keytables that the rc-6 protocol is not enabled.
I was able to get it working by ssh into the machine and typing
echo "rc-6" > /sys/class/rc/rc0/protocols
I tried adding this to autostart.sh to no avail.
Any help appreciated.
I am hoping to start work on a kodi video intercom plugin using webrtc native api later in the summer and need UVC drivers for webcam support.