By default the dvbsnoop uses the adapter0, frontend0, demux0 etc.
You can change to different demux or frontend using the following:
dvbsnoop -s pidscan -demux /dev/dvb/adapter0/demuxX -frontend /dev/dvb/adapter0/frontendY
I am testing on OS mega and have no issues with dvbsnoop and pidscan!
root@osmega:~# dvbsnoop -s pidscan -demux /dev/dvb/adapter0/demux0 -frontend /dev/dvb/adapter0/frontend2
dvbsnoop V1.4.53 -- https://github.com/persianpros/dvbsnoop
---------------------------------------------------------
Transponder PID-Scan...
---------------------------------------------------------
PID found: 0 (0x0000) [SECTION: Program Association Table (PAT)]
PID found: 1 (0x0001) [SECTION: Conditional Access Table (CAT)]
PID found: 16 (0x0010) [SECTION: Network Information Table (NIT) - actual network]
PID found: 17 (0x0011) [SECTION: Service Description Table (SDT) - actual transport stream]
PID found: 18 (0x0012) [SECTION: Event Information Table (EIT) - actual transport stream, schedule]
PID found: 20 (0x0014) [SECTION: Time Date Table (TDT)]
....
If pidscan is not working and correct demuxer is selected, then something is really wrong with drivers!
So tune to a channel (a single channel), don't make recordings or using IPTV etc at the same time, then use pidscan (the demux0 should be in use).
Edited by athoik, 24 May 2017 - 16:12.
Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916