18.04 LIRCD failure [ BODGED]

Moderators: mdrjr, odroid

18.04 LIRCD failure [ BODGED]

Unread postby richard-g8jvm » Tue Sep 11, 2018 12:31 am

Hi
hitting a few probs with 18.04
its noticeably slower than 16.04
the time it take to ask ffor a password with sudo is long, 5ecs, with 16.04 it was instant]

Lirc installed as per wiki, but it refuses to run, the moduels are loaded for the HK remote, which I use
but
Code: Select all
odroid@odroid:~$ sudo service lircd restart
odroid@odroid:~$ sudo service lircd status
● lircd.service - Flexible IR remote input/output application support
   Loaded: loaded (/lib/systemd/system/lircd.service; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Mon 2018-09-10 15:16:05 UTC; 3s ago
     Docs: man:lircd(8)
           http://lirc.org/html/configure.html
  Process: 1553 ExecStart=/usr/sbin/lircd --nodaemon (code=killed, signal=SEGV)
 Main PID: 1553 (code=killed, signal=SEGV)

Sep 10 15:16:05 odroid systemd[1]: Started Flexible IR remote input/output application support.
Sep 10 15:16:05 odroid lircd[1553]: ciniparser: input line too long in /etc/lirc/lirc_options.conf (37)
Sep 10 15:16:05 odroid lircd-0.10.0[1553]: Info: lircd:  Opening log, level: Info
Sep 10 15:16:05 odroid lircd-0.10.0[1553]: Notice: Version: lircd 0.10.0
Sep 10 15:16:05 odroid lircd-0.10.0[1553]: Notice: System info: Linux odroid 3.16.57-25 #1 SMP PREEMPT Mon Jul 30 19:27:38 -03 2018 aarch64 aarch64 aarch64 GNU/Linux
Sep 10 15:16:05 odroid systemd[1]: lircd.service: Main process exited, code=killed, status=11/SEGV
Sep 10 15:16:05 odroid systemd[1]: lircd.service: Failed with result 'signal'.

I checked line 37 and it the last line,
Code: Select all
release-suffix  = _EVUP



Edited with more info
I ran journalctl and found this :
Code: Select all
Sep 10 15:30:32 odroid sudo[1641]: pam_unix(sudo:session): session closed for user root
Sep 10 15:30:32 odroid lircd-uinput[1647]: ciniparser: input line too long in /etc/lirc/lirc_options.conf (37)
Sep 10 15:30:32 odroid lircd-uinput[1647]: lircd-0.10.0[1647]: Info: lircd-uinput:  Opening log, level: Info
Sep 10 15:30:32 odroid lircd-uinput[1647]: lircd-0.10.0[1647]: Info: Reading data from /var/run/lirc/lircd, writing to /dev/uinput
Sep 10 15:30:32 odroid lircd-uinput[1647]: lircd-0.10.0[1647]: Cannot stat socket path /var/run/lirc/lircd: No such file or directory
Sep 10 15:30:32 odroid lircd-uinput[1647]: lircd-0.10.0[1647]: Error: Cannot setup input file descriptor.
Sep 10 15:30:32 odroid lircd-0.10.0[1647]: Info: lircd-uinput:  Opening log, level: Info
Sep 10 15:30:32 odroid systemd[1]: lircd-uinput.service: Main process exited, code=exited, status=1/FAILURE
Sep 10 15:30:32 odroid lircd-0.10.0[1647]: Info: Reading data from /var/run/lirc/lircd, writing to /dev/uinput
Sep 10 15:30:32 odroid lircd-0.10.0[1647]: Cannot stat socket path /var/run/lirc/lircd: No such file or directory
Sep 10 15:30:32 odroid systemd[1]: lircd-uinput.service: Failed with result 'exit-code'.


Any ideas ??? , what have I missed ?
Last edited by richard-g8jvm on Tue Sep 11, 2018 11:08 pm, edited 1 time in total.
BR
Richard G8JVM
richard-g8jvm
 
Posts: 310
Joined: Sun Jan 18, 2015 1:27 am
Location: Telford UK
languages_spoken: english
ODROIDs: C1+ C2, XU4

Re: 18.04 LIRCD failure

Unread postby mad_ady » Tue Sep 11, 2018 3:11 am

There's a wiki entry for lirc on 18.04 for xu4. There are some changes you need to make to the config files to have it run.

Regarding sudo, it sounds like a name resolving issue. Have you renamed your odroid and did not add [c]127.0.0.1 newname[/] in /etc/hosts?
User avatar
mad_ady
 
Posts: 4707
Joined: Wed Jul 15, 2015 5:00 pm
Location: Bucharest, Romania
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1

Re: 18.04 LIRCD failure

Unread postby richard-g8jvm » Tue Sep 11, 2018 3:20 am

Hiya
no name change, its still odroid.
Are you sure its for a XU4 ? as that doesn't have a IR sensor ???
I'll look anyway.
Thanks
BR
Richard G8JVM
richard-g8jvm
 
Posts: 310
Joined: Sun Jan 18, 2015 1:27 am
Location: Telford UK
languages_spoken: english
ODROIDs: C1+ C2, XU4

Re: 18.04 LIRCD failure

Unread postby mad_ady » Tue Sep 11, 2018 3:28 am

It's somewhere in the add a ir blaster section.
User avatar
mad_ady
 
Posts: 4707
Joined: Wed Jul 15, 2015 5:00 pm
Location: Bucharest, Romania
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1

Re: 18.04 LIRCD failure

Unread postby richard-g8jvm » Tue Sep 11, 2018 4:29 am

OK found that,
Its the same as the section in the C2 wiki, with serial modules loaded as its using GPIO
BR
Richard G8JVM
richard-g8jvm
 
Posts: 310
Joined: Sun Jan 18, 2015 1:27 am
Location: Telford UK
languages_spoken: english
ODROIDs: C1+ C2, XU4

Re: 18.04 LIRCD failure

Unread postby richard-g8jvm » Tue Sep 11, 2018 5:32 am

Ive stopped trying to start LIRCD as a service, as it looks from what i'm finding that systemd has been a bit knobbled, to encourage the use of systemctl

So I've run sudo systemctl enable lircd
and rebooted as I did with getting motion to start, which it did.

and now getting a different status message:-
Code: Select all
odroid@odroid:~$ sudo systemctl status lircd
● lircd.service - Flexible IR remote input/output application support
   Loaded: loaded (/lib/systemd/system/lircd.service; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Sun 2018-01-28 15:58:25 UTC; 7 months 12 days ago
     Docs: man:lircd(8)
           http://lirc.org/html/configure.html
  Process: 769 ExecStart=/usr/sbin/lircd --nodaemon (code=killed, signal=SEGV)
 Main PID: 769 (code=killed, signal=SEGV)

Jan 28 15:58:25 odroid systemd[1]: Started Flexible IR remote input/output application support.
Jan 28 15:58:25 odroid lircd[769]: ciniparser: input line too long in /etc/lirc/lirc_options.conf (37)
Jan 28 15:58:25 odroid lircd-0.10.0[769]: Info: lircd:  Opening log, level: Info
Jan 28 15:58:25 odroid lircd-0.10.0[769]: Notice: Version: lircd 0.10.0
Jan 28 15:58:25 odroid lircd-0.10.0[769]: Notice: System info: Linux odroid 3.16.57-25 #1 SMP PREEMPT Mon Jul 30 19:27:38 -03 2018 aarch64 aarch64 aarch64 GNU/Linux
Jan 28 15:58:25 odroid systemd[1]: lircd.service: Main process exited, code=killed, status=11/SEGV
Jan 28 15:58:25 odroid systemd[1]: lircd.service: Failed with result 'signal'.
Jan 28 15:58:25 odroid systemd[1]: lircd.service: Start request repeated too quickly.
Jan 28 15:58:25 odroid systemd[1]: lircd.service: Failed with result 'signal'.
Jan 28 15:58:25 odroid systemd[1]: Failed to start Flexible IR remote input/output application support.



There is also something very screwy here, the ciniparser line is rejecting a line with a "#" at the start
I put that there to stop the comment !
it should not be reading a line with a hash at the start.
It also looks like the use of "service start"in the wiki may be incorrect.
with this kernel and ubuntu18 using "service start lircd" results in systemd not having permissions or something like that to write to files in /var
BR
Richard G8JVM
richard-g8jvm
 
Posts: 310
Joined: Sun Jan 18, 2015 1:27 am
Location: Telford UK
languages_spoken: english
ODROIDs: C1+ C2, XU4

Re: 18.04 LIRCD failure

Unread postby richard-g8jvm » Tue Sep 11, 2018 8:05 pm

There is something definitly wrong with lirc

Just in case I'd imported a non displayed character , I copied the lirc_options.conf file again from the Wiki, straight copy and paste
re-enabled lircd with systemctl
Ran systemctl start lircd
sytemctl status lircd shows:-
Code: Select all
odroid@odroid:~$ sudo systemctl start lircd
odroid@odroid:~$ sudo systemctl status lircd
● lircd.service - Flexible IR remote input/output application support
   Loaded: loaded (/lib/systemd/system/lircd.service; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Tue 2018-09-11 10:38:07 UTC; 14s ago
     Docs: man:lircd(8)
           http://lirc.org/html/configure.html
  Process: 3858 ExecStart=/usr/sbin/lircd --nodaemon (code=killed, signal=SEGV)
 Main PID: 3858 (code=killed, signal=SEGV)

Sep 11 10:38:07 odroid systemd[1]: Started Flexible IR remote input/output application support.
Sep 11 10:38:07 odroid lircd[3858]: ciniparser: input line too long in /etc/lirc/lirc_options.conf (30)
Sep 11 10:38:07 odroid lircd-0.10.0[3858]: Info: lircd:  Opening log, level: Info
Sep 11 10:38:07 odroid lircd-0.10.0[3858]: Notice: Version: lircd 0.10.0
Sep 11 10:38:07 odroid lircd-0.10.0[3858]: Notice: System info: Linux odroid 3.16.57-25 #1 SMP PREEMPT Mon Jul 30 19:27:38 -03 2018 aarch64 aarch6
Sep 11 10:38:07 odroid systemd[1]: lircd.service: Main process exited, code=killed, status=11/SEGV
Sep 11 10:38:07 odroid systemd[1]: lircd.service: Failed with result 'signal'.


NOTE ciniparser still shows the last line is too long
You can put a hash in front of this line so it should not be read, but it still is !
the new conf file does not have the preamble the distributed file has , hence it lists line 30 and not 37
Considering that up to now the HK remote would function with the supplied image, in other words lirc was configured by default.
Why change this practise, unless its known that LIRC does not work with ubuntu 18.04 arm64 ???
Lirc works well on Ubuntu16.04, but the diectory structure has change on 18.04 , so have the config files.
I'll ask on the lirc list and see if this is known there.
BR
Richard G8JVM
richard-g8jvm
 
Posts: 310
Joined: Sun Jan 18, 2015 1:27 am
Location: Telford UK
languages_spoken: english
ODROIDs: C1+ C2, XU4

Re: 18.04 LIRCD failure

Unread postby richard-g8jvm » Tue Sep 11, 2018 11:07 pm

Hi
This problem is well known about !!!!!!
The version of lirc distributed with ubuntu LTS 18.04 is BROKEN
see https://ubuntuforums.org/showthread.php?t=2396923
Following the link given in the reply to that posting:-
the depositoty to be added to /etc/apt/sources.list is

Code: Select all
deb http://ports.ubuntu.com/ubuntu-ports xenial main universe

loading lirc version 0.9.0 , the config file from the wiki should be that of ubuntu LTS 16.0
rename the original hardware.conf and lircd.conf , and copy the files over from the wiki to /etc/lirc

I started lircd with sudo lircd
running irw I get
Code: Select all
odroid@odroid:~$ irw
000000004db29966 00 KEY_LEFT odroid
000000004db29966 01 KEY_LEFT odroid
000000004db29966 02 KEY_LEFT odroid
000000004db2837c 00 KEY_RIGHT odroid
000000004db2837c 01 KEY_RIGHT odroid
000000004db2738c 00 KEY_ENTER odroid
000000004db2738c 01 KEY_ENTER odroid
000000004db253ac 00 KEY_UP odroid
000000004db253ac 01 KEY_UP odroid
000000004db253ac 02 KEY_UP odroid
000000004db24bb4 00 KEY_DOWN odroid
000000004db24bb4 01 KEY_DOWN odroid
000000004db259a6 00 KEY_BACK odroid
000000004db2a35c 00 KEY_MENU odroid
000000004db2a35c 01 KEY_MENU odroid
000000004db201fe 00 KEY_VOLUMEUP odroid
000000004db201fe 01 KEY_VOLUMEUP odroid
000000004db201fe 02 KEY_VOLUMEUP odroid
000000004db2817e 00 KEY_VOLUMEDOWN odroid
000000004db2817e 01 KEY_VOLUMEDOWN odroid
000000004db2817e 02 KEY_VOLUMEDOWN odroid
000000004db211ee 00 KEY_MUTE odroid
000000004db211ee 01 KEY_MUTE odroid
000000004db241be 00 KEY_HOME odroid
000000004db241be 01 KEY_HOME odroid
000000004db241be 02 KEY_HOME odroid



It appears to auto start on boot up as well :)
and the remote works on kodi.

Just a shame the hardkernel guys couldn't say , "We know lirc 10.0.2 is broken , that s why its not included in the image"
BR
Richard G8JVM
richard-g8jvm
 
Posts: 310
Joined: Sun Jan 18, 2015 1:27 am
Location: Telford UK
languages_spoken: english
ODROIDs: C1+ C2, XU4

Re: 18.04 LIRCD failure [ BODGED]

Unread postby mad_ady » Tue Sep 11, 2018 11:33 pm

Actually lirc comes from cannonical
User avatar
mad_ady
 
Posts: 4707
Joined: Wed Jul 15, 2015 5:00 pm
Location: Bucharest, Romania
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1

Re: 18.04 LIRCD failure [ BODGED]

Unread postby richard-g8jvm » Wed Sep 12, 2018 12:06 am

Hi mad_ady
its still broken and known about, which begs the question about the contents of the wiki.
Its not only me saying is broken,
Considering that a lot of the SBC odroids end up as media centers, kodi etc, where a remote is important, and that Hardkernel make and sell the remotes for this
and the other odroid boards which have IR sensors, it should have been checked, its slipped through the net.
Its probably due to the old kernel versions used and available for arm boards, Lirc 10.0.2 might work with later kernels, 4 and later.
I can safely assume you knew nothing of it, otherwise you would have said straight away, but someone at hardkernel must have known about it.
At least there is a work around that can be used on the C2, probably the others too.
The help you give is appreciated by all -thanks
BR
Richard G8JVM
richard-g8jvm
 
Posts: 310
Joined: Sun Jan 18, 2015 1:27 am
Location: Telford UK
languages_spoken: english
ODROIDs: C1+ C2, XU4

Re: 18.04 LIRCD failure [ BODGED]

Unread postby mad_ady » Wed Sep 12, 2018 12:53 am

Yeah, I'm only using it for an ir blaster, not a receiver, so I can't comment.
User avatar
mad_ady
 
Posts: 4707
Joined: Wed Jul 15, 2015 5:00 pm
Location: Bucharest, Romania
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1

Re: 18.04 LIRCD failure [ BODGED]

Unread postby odroid » Thu Sep 13, 2018 9:36 am

Is there something to be updated in this instruction for Ubuntu 18.04?
https://wiki.odroid.com/odroid-c2/appli ... buntu18.04
User avatar
odroid
Site Admin
 
Posts: 28855
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: 18.04 LIRCD failure [ BODGED]

Unread postby rooted » Thu Sep 13, 2018 2:14 pm

richard-g8jvm wrote:It should have been checked, its slipped through the net.


There is no way to check every subsystem of every os release with their limited resources unfortunately.

I setup lirc without downgrading lircd a month ago. It was broken due to a configuration error on the wiki, I figured out it was simply a path problem and the wiki was updated to reflect this.
User avatar
rooted
 
Posts: 5676
Joined: Fri Dec 19, 2014 9:12 am
Location: Gulf of Mexico, US
languages_spoken: english
ODROIDs: C1, C1+, C2
XU3 Lite, XU4
N1
VU7+
HiFi Shield 2
Smart Power (original)

Re: 18.04 LIRCD failure [ BODGED]

Unread postby richard-g8jvm » Thu Sep 13, 2018 6:13 pm

Hi
since that time there is a new kernel for arm64, and it looks as if the use of "service START|STATUS| etc <service type>"
has been depreciated.
Its forcing the use of "systemctl" to start sevices.
This is applicable to services that used to start with "service start"
The kernels used on odroids are pretty ancient, the computer upstairs runs on 4.17, this laptop uses 4.15
Port naming is still eth0, wlan0 etc, whereas thats has been superceeded by enp9s0 and wlp12s0, examples from my laptop running linux mint which
uses ubuntu 18.04, but with cinnamon as a DM
I do get the impression when I post something the Odroid developers just regard it as "that F'ing idiot posting rubbish again "
I'm very grateful for the help of mad_ady for the help he gives.
It is a fact that when packages are a new version and ported to other architectures and used with old kernels there are likely to be be problems,
and LIRC has been flagged on other distros as having problems with the newest version 10.0.2.

I'll probably get told to leave the list for criticising now
BR
Richard G8JVM
richard-g8jvm
 
Posts: 310
Joined: Sun Jan 18, 2015 1:27 am
Location: Telford UK
languages_spoken: english
ODROIDs: C1+ C2, XU4

Re: 18.04 LIRCD failure [ BODGED]

Unread postby rooted » Fri Sep 14, 2018 12:16 am

I'm not affiliated with Hardkernel, I was just saying when the image was released and no less than 30 days ago lirc was working fine.

So there is really no way they would have known it's now broken without someone like you telling them. This is an Ubuntu issue not Hardkernel, they don't maintain that package.

mad_ady is great, I also do my best to help people when I can. I don't believe any hardkernel developers have said anything negative to you, they are all patient, helpful people.

An updated 4.18 based kernel for the C2 is close to release.

viewtopic.php?t=22717
User avatar
rooted
 
Posts: 5676
Joined: Fri Dec 19, 2014 9:12 am
Location: Gulf of Mexico, US
languages_spoken: english
ODROIDs: C1, C1+, C2
XU3 Lite, XU4
N1
VU7+
HiFi Shield 2
Smart Power (original)

Re: 18.04 LIRCD failure [ BODGED]

Unread postby richard-g8jvm » Fri Sep 14, 2018 1:50 am

Glad to hear a 4.18 kernel is not too far away.
Its not a ubuntu problem, as its several distros that have been effected; the fickle finger of fate points clearly at LIRC
Maybe when kernel 4.18 comes on line LIRC 10.0.2 may work, or more likely 10.0.4 with all the bug fixes will.
BR
Richard G8JVM
richard-g8jvm
 
Posts: 310
Joined: Sun Jan 18, 2015 1:27 am
Location: Telford UK
languages_spoken: english
ODROIDs: C1+ C2, XU4


Return to Ubuntu

Who is online

Users browsing this forum: No registered users and 1 guest