Hi Jonas, Thanks for the response, actually ofonod was crashed during systemd service, here is the log:
-- Logs begin at Fri 2019-05-03 01:00:52 UTC, end at Fri 2019-05-03 01:03:01 UTC. -- May 03 01:01:01 imx6ullevk systemd[1]: Starting Telephony service... May 03 01:01:01 imx6ullevk ofonod[217]: oFono version 1.24 May 03 01:01:02 imx6ullevk systemd[1]: Started Telephony service. May 03 01:01:05 imx6ullevk ofonod[217]: Aborting (signal 11) [/usr/sbin/ofonod] May 03 01:01:05 imx6ullevk systemd[1]: ofono.service: Main process exited, code=exited, status=1/FAILURE May 03 01:01:05 imx6ullevk systemd[1]: ofono.service: Failed with result 'exit-code'. But I have no trouble to start the ofonod manually. Thank you. - jupiter On 5/3/19, Jonas Bonn <[email protected]> wrote: > > > On 02/05/2019 17:03, JH wrote: >> Hi, >> >> The official ofono recipe ofono.inc defines SYSTEMD_SERVICE_${PN} = >> "ofono.service", but the ofonod is not started by system service >> automatically, I have to start the ofonod manually, what could be the >> issue? > > This question should be directed to the OpenEmbedded mailing list as it > has nothing to do with ofono, per se. > > That said: > i) it works for me on all recent versions of OE > ii) including some relevant logging (journalctl, etc.) is generally > helpful in debugging these matters; both the log of the ofono service, > in case it fails to start due to crashes, and the log from systemd > itself, in case systemd is deciding not to start the service for some > reason. > > /Jonas > >> >> Thank you. >> >> Kind regards, >> >> - jupiter >> _______________________________________________ >> ofono mailing list >> [email protected] >> https://lists.ofono.org/mailman/listinfo/ofono >> > _______________________________________________ ofono mailing list [email protected] https://lists.ofono.org/mailman/listinfo/ofono
