No adapter found / fsmonitor problem on vitual machine?

Hi everybody and a happy new year first!!!

I wanted to move my tvheadend installation to a virtual machine. I do have the problem here that tvheadend does not list any adapters. The adapters are, however, there and are working as shown by mumudvb:

hts@tvheadend:~$ ls -l /dev/dvb
total 0
drwxrwxrwx 2 root root 100 Jan  1 21:06 adapter0

hts@tvheadend:~$ ls -l /dev/dvb/adapter0/
total 0
crwxrwxrwx 1 root root 212, 1 Jan  1 21:06 demux0
crwxrwxrwx 1 root root 212, 2 Jan  1 21:06 dvr0
crwxrwxrwx 1 root root 212, 0 Jan  1 21:06 frontend0

hts@tvheadend:~$ /opt/bin/mediaclient --readsignal=0 -d /dev/dvb/adapter0/frontend0
== reading digital TV signal ==
SIGNAL: [.............................    ] ( 87%)  BER:      0 CNR: 35.00 FREQ: 506000000  Hz LOCKED: YES SYM: 6900000 MOD: QAM256
SIGNAL: [................................ ] ( 97%)  BER:      0 CNR: 35.00 FREQ: 506000000  Hz LOCKED: YES SYM: 6900000 MOD: QAM256
SIGNAL: [................................ ] ( 97%)  BER:      9 CNR: 34.70 FREQ: 506000000  Hz LOCKED: YES SYM: 6900000 MOD: QAM256
SIGNAL: [................................ ] ( 97%)  BER:      9 CNR: 34.70 FREQ: 506000000  Hz LOCKED: YES SYM: 6900000 MOD: QAM256
SIGNAL: [................................ ] ( 97%)  BER:      9 CNR: 34.70 FREQ: 506000000  Hz LOCKED: YES SYM: 6900000 MOD: QAM256
SIGNAL: [................................ ] ( 97%)  BER:      8 CNR: 35.20 FREQ: 506000000  Hz LOCKED: YES SYM: 6900000 MOD: QAM256
SIGNAL: [................................ ] ( 97%)  BER:      8 CNR: 35.00 FREQ: 506000000  Hz LOCKED: YES SYM: 6900000 MOD: QAM256

hts@tvheadend:~$ mumudvb -d -c mumu-orf1.conf 
MuMuDVB Version 1.7.1
 --- Build information ---
Built with CAM support.
Built without transcoding support.
Built with ATSC support.
Built with ATSC long channel names support.
Built with support for DVB API Version 5.
---------
Originally based on dvbstream 0.6 by (C) Dave Chapman 2001-2004
Released under the GPL.
Latest version available from http://mumudvb.braice.net/
Project from the cr@ns (http://www.crans.org)
by Brice DUBOST ([email protected])

Info:  Tune:  You will use DVB API version 5 for tuning your card.
WARN:  Unicast :  You have enabled the support for HTTP Unicast. This feature is quite youg, please report any bug/comment
Info:  Main:  Full autoconfiguration, we activate SAP announces. if you want to deactivate them see the README.
Info:  Main:  Full autoconfiguration, we activate PAT rewritting. if you want to deactivate it see the README.
Info:  Main:  Full autoconfiguration, we activate SDT rewritting. if you want to deactivate it see the README.
Info:  Main:  Full autoconfiguration, we activate sorting of the EIT PID. if you want to deactivate it see the README.
Info:  Main:  ========== End of configuration, MuMuDVB version 1.7.1 is starting ==========
Info:  Autoconf:  The autoconfiguration auto update is enabled. If you want to disable it put "autoconf_pid_update=0" in your config file.
WARN:  Logs:  saving_filename /var/run/mumudvb/mumudvb_generated_conf_card0_tuner0: Permission denied
WARN:  Main:  Can't create /var/run/mumudvb/channels_streamed_adapter0_tuner0: Permission denied
WARN:  Main:  Can't create /var/run/mumudvb/channels_unstreamed_adapter0_tuner0: Permission denied
Info:  Main:  Streaming. Freq 506000000
Info:  Tune:  Using DVB card "Sundtek DVB-C (III)" tuner 0
Info:  Tune:  tuning DVB-C to 506000000 Hz, srate=6900000
Info:  Tune:  Tuning With DVB-API version 5. delivery system : 1
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:       FE_HAS_CARRIER : found a DVB signal
Info:  Tune:       FE_HAS_VITERBI : FEC is stable
Info:  Tune:       FE_HAS_SYNC : found sync bytes
Info:  Tune:       FE_HAS_LOCK : everything's working... 
Info:  Tune:  Event:  Frequency: 506000000
Info:  Tune:          SymbolRate: 6900000
Info:  Tune:          FEC_inner:  9
Info:  Tune:  Bit error rate: 3
Info:  Tune:  Signal strength: 64124
Info:  Tune:  SNR: 64124
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:       FE_HAS_CARRIER : found a DVB signal
Info:  Tune:       FE_HAS_VITERBI : FEC is stable
Info:  Tune:       FE_HAS_SYNC : found sync bytes
Info:  Tune:       FE_HAS_LOCK : everything's working... 
Info:  Main:  Card 0, tuner 0 tuned
Info:  Unicast:  We open the Master http socket for address 0.0.0.0:4242
Info:  Autoconf:  Autoconfiguration Start
Info:  Autoconf:  Autoconfiguration done
Info:  Autoconf:  Diffusion 4 channels
Info:  Autoconf:  Channel number :   0, name : "ORF eins HD"  service id 9036 
Info:  Autoconf:      Multicast4 ip : 239.100.0.0:1234
Info:  Autoconf:      Unicast : Channel accessible via the master connection, 0.0.0.0:4242
Info:  Autoconf:  Channel number :   1, name : "ORF 2 HD"  service id 9037 
Info:  Autoconf:      Multicast4 ip : 239.100.0.1:1234
Info:  Autoconf:      Unicast : Channel accessible via the master connection, 0.0.0.0:4242
Info:  Autoconf:  Channel number :   2, name : "BR Süd HD"  service id 9044 
Info:  Autoconf:      Multicast4 ip : 239.100.0.2:1234
Info:  Autoconf:      Unicast : Channel accessible via the master connection, 0.0.0.0:4242
Info:  Autoconf:  Channel number :   3, name : "SWR BW HD"  service id 9045 
Info:  Autoconf:      Multicast4 ip : 239.100.0.3:1234
Info:  Autoconf:      Unicast : Channel accessible via the master connection, 0.0.0.0:4242

So, only tvheadend does not see the adapters. I am wondering if that has anything to do with fsmonitor?

2016-01-02 09:34:20.313 [  DEBUG] fsmonitor: watch /dev
2016-01-02 09:34:20.313 [  DEBUG] fsmonitor: watch /dev/dvb

Any idea, why tvheadend does not see any adapters, and maybe, how I can debug that?

Thanks

Michael

Replies (6)

RE: No adapter found / fsmonitor problem on vitual machine? - Added by Mark Clarkstone almost 9 years ago

try running tvheadend manually so you get debug output.

sudo -u hts /usr/bin/tvheadend -c /home/hts/.hts/tvheadend

It should output something like

2016-01-02 10:12:21.523 [  ERROR] linuxdvb: unable to open /dev/dvb/adapter0/frontend0

if it can't use the adapters.

RE: No adapter found / fsmonitor problem on vitual machine? - Added by Michael B. almost 9 years ago

hts@tvheadend:~$ tvheadend
2016-01-02 11:26:08.755 [   INFO] main: Log started
2016-01-02 11:26:08.811 [   INFO] config: loaded
2016-01-02 11:26:08.909 [   INFO] scanfile: DVB-T - loaded 44 regions with 1104 networks
2016-01-02 11:26:08.909 [   INFO] scanfile: DVB-S - loaded 1 regions with 92 networks
2016-01-02 11:26:08.909 [   INFO] scanfile: DVB-C - loaded 17 regions with 53 networks
2016-01-02 11:26:08.909 [   INFO] scanfile: ATSC - loaded 2 regions with 14 networks
2016-01-02 11:26:11.359 [   INFO] dvr: Creating new configuration ''
2016-01-02 11:26:11.360 [   INFO] epggrab: module eit created
2016-01-02 11:26:11.360 [   INFO] epggrab: module uk_freesat created
2016-01-02 11:26:11.360 [   INFO] epggrab: module uk_freeview created
2016-01-02 11:26:11.360 [   INFO] epggrab: module viasat_baltic created
2016-01-02 11:26:11.363 [   INFO] epggrab: module opentv-ausat created
2016-01-02 11:26:11.363 [   INFO] epggrab: module opentv-skynz created
2016-01-02 11:26:11.363 [   INFO] epggrab: module opentv-skyit created
2016-01-02 11:26:11.363 [   INFO] epggrab: module opentv-skyuk created
2016-01-02 11:26:11.364 [   INFO] epggrab: module pyepg created
2016-01-02 11:26:11.364 [   INFO] epggrab: module xmltv created
2016-01-02 11:26:11.365 [   INFO] spawn: Executing "/usr/bin/tv_find_grabbers" 
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_es_laguiatv created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_it created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_eu_epgdata created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_combiner created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_se_tvzon created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_is created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_na_dd created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_se_swedb created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_za created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_fi created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_na_dtv created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_in created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_il created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_ar created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_dk_dr created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_fr created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_eu_egon created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_ch_search created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_uk_rt created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_fr_kazer created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_pt_meo created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_hr created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_uk_bleb created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_huro created
2016-01-02 11:26:12.640 [   INFO] epggrab: module /usr/bin/tv_grab_no_gfeed created
2016-01-02 11:26:12.648 [   INFO] epgdb: loaded v2
2016-01-02 11:26:12.648 [   INFO] epgdb:   config     1
2016-01-02 11:26:12.648 [   INFO] epgdb:   channels   0
2016-01-02 11:26:12.648 [   INFO] epgdb:   brands     0
2016-01-02 11:26:12.648 [   INFO] epgdb:   seasons    0
2016-01-02 11:26:12.648 [   INFO] epgdb:   episodes   0
2016-01-02 11:26:12.648 [   INFO] epgdb:   broadcasts 0
2016-01-02 11:26:12.649 [ NOTICE] START: HTS Tvheadend version 4.0.8 started, running as PID:4253 UID:105 GID:112, CWD:/home/hts CNF:/home/hts/.hts/tvheadend

It just showns nothing. Neither an error message nor an open adapter message. It does not even seem to see the adapter.

RE: No adapter found / fsmonitor problem on vitual machine? - Added by Mark Clarkstone almost 9 years ago

Make sure nothing else is using the adapters and try again.

RE: No adapter found / fsmonitor problem on vitual machine? - Added by Michael B. almost 9 years ago

hts@tvheadend:~$ /opt/bin/mediaclient --lc                                         
**** List of Media Clients ****
/dev/dvb/adapter0/frontend0:
  No client connected
/dev/dvb/adapter0/dvr0:
  No client connected
/dev/dvb/adapter0/demux0:
  No client connected
/dev/mediainput0:
  No client connected

Nothing using the adapter.

I am even able to start first tvheadend and then (with tvheadend running) also mumudvb, and mumudvb gets access to the adapter.

Very strange. I did not have that in my last installation (on a real machine). Not sure if that is coincidence or an effect of the virtual machine, that tvh is not finding the adapter.

Any idea? (Thanks for your help, btw.)

RE: No adapter found / fsmonitor problem on vitual machine? - Added by Mark Clarkstone almost 9 years ago

Hmm, very strange. I'm not sure what is going on here. You may want to contact Markus from Sundtek.

RE: No adapter found / fsmonitor problem on vitual machine? - Added by Michael B. almost 9 years ago

I don't think it is something Sundtek specific. First, it worked on the real machine. Second, the sundtek drivers do see and work with the adapter (also on the VM). And last, mumudvb also works with the adapter. So, it probably is something specific on how tvheadend detects the adapters.

But thanks anyway. Maybe Markus can chime in and has some additional ideas.

Best regards

Michael

(1-6/6)

Project

General

Profile

Tvheadend