[SOLVED] Trouble with ONDD


#1

I have installed the ORx package on Arch. Everything seems to be working, the Adapter is up and signal is good, however ONDD is having a problem finding /dev/dvb/adapter0/frontend0 although it exists…

[[email protected] ~]# ls /dev/dvb/adapter0/
demux0  dvr0  frontend0  net0
[[email protected] ~]#

Log:

Sep 15 19:23:54 alarmpi systemd[1]: Starting Outernet Data Delivery agent service...
Sep 15 19:23:54 alarmpi systemd[1]: Started Outernet Data Delivery agent service.
Sep 15 19:23:54 alarmpi ondd[326]: /usr/sbin/ondd: /usr/lib/libcrypto.so.1.0.0: no version information available (required by /usr/sbin/ondd)
Sep 15 19:23:54 alarmpi ipd[326]: [main] v1.0.1
Sep 15 19:23:54 alarmpi ipd[326]: [main] thread exception: open( /dev/dvb/adapter0/frontend0 ) failed: (2) No such file or directory
Sep 15 19:23:54 alarmpi ondd[326]: 19:23:54.844 [main] v1.0.1
Sep 15 19:23:54 alarmpi ondd[326]: 19:23:54.874 [main] thread exception: open( /dev/dvb/adapter0/frontend0 ) failed: (2) No such file or directory
Sep 15 19:23:54 alarmpi systemd[1]: ondd.service: main process exited, code=exited, status=255/n/a

The device is a DM04_LME2510C_DVB-S RS2000
The driver is working and I have a good signal in tvheadend

Can’t upload screenshot because I’m a “new user”…


#2

Here’s a more comprehensive listing of the device path:

[[email protected] ~]# ls /dev/dvb/adapter0/ -l
total 0
crw-rw---- 1 root video 212, 0 Dec 31  1969 demux0
crw-rw---- 1 root video 212, 1 Dec 31  1969 dvr0
crw-rw---- 1 root video 212, 3 Dec 31  1969 frontend0
crw-rw---- 1 root video 212, 2 Dec 31  1969 net0
[[email protected] ~]#

#3

Hi, do you mind submitting a bug report here:

If you don’t have a GitHub account, let me know, and I will submit the bug report for you. However, I think it’s better if you can keep track of your own tickets.

Also, please include information about what Raspberry Pi model you are using.


#4

Done and thanks.

Issue moved here: https://github.com/Outernet-Project/orx-install/issues/34


#5

Thanks for reporting this!


#6

Looks like it was only a stale log entry.