Allan Stirling wrote: > Manu Abraham wrote: > >> Allan Stirling wrote: >> >>> Allan Stirling wrote: >>> >>>> >>>> Something is going wrong here. Adding some debugging to the /* >>>> Get PMT PID */ >>>> section gives... >>>> >>>> parse_pat: PAT => Section Length=[41], TS ID=[12270] >>>> program_count: 10 >>>> p_params->service_id: 4703 >>> >> >> This one is from your channels.conf.. It is trying to compare it with >> the service_id in the PAT.. >> >> If this matches, that PMT_PID is used >> >>>> p_pat->p_program_descriptor->program_number: 176 >>>> p_params->service_id: 4703 >>>> p_pat->p_program_descriptor->program_number: 61155 >>>> p_params->service_id: 4703 >>>> p_pat->p_program_descriptor->program_number: 12288 >>>> p_params->service_id: 4703 >>>> p_pat->p_program_descriptor->program_number: 65337 >>>> p_params->service_id: 4703 >>>> p_pat->p_program_descriptor->program_number: 65530 >>>> p_params->service_id: 4703 >>>> p_pat->p_program_descriptor->program_number: 4603 >>>> p_params->service_id: 4703 >>>> p_pat->p_program_descriptor->program_number: 15967 >>>> p_params->service_id: 4703 >>>> p_pat->p_program_descriptor->program_number: 65474 >>>> p_params->service_id: 4703 >>>> p_pat->p_program_descriptor->program_number: 4809 >>>> p_params->service_id: 4703 >>>> p_pat->p_program_descriptor->program_number: 4906 >>>> >> >> From your list, what i can see is, You don't have service_id 4703 in >> the PAT, i believe .. >> >> These 2 has to be the same .. Else no PMT_PID, well that's what's >> happening .. Anyway let's get into the next part to see things are >> okay .. >> >>>> I notice in your channels.conf that some of the values are >>>> duplicated. That's not true on this network :( >>>> >>>> Cheers, >>>> >>>> Allan. >>>> >>> This is what the program_numbers look like from within ca_zap. As you >>> can see, no 4703, which is what is detected by scan. Do you have a >>> command line for dvbsnoop which would give more info? I'll be looking >> >> >> Ok, what you can temporarily do is hard code the PMT_PID for your >> channel into pmt_pid in si.c and try running it .. See whether it >> get's hung still .. This would work only if you have that valid PMT_PID. >> else this would not work .. >> >> Have you got this channels.conf, doing a scan, or is it some stock >> channels.conf .. ? > > This is from a current scan of this single transponder, which is identical. > > using '/dev/dvb/adapter3/frontend0' and '/dev/dvb/adapter3/demux0' > 0x0000 0x05e7: pmt_pid 0x0000 (null) -- (null) (???) > 0x0000 0x1261: pmt_pid 0x0100 BSkyB -- Sky One (running, scrambled) > 0x0000 0x13f0: pmt_pid 0x0102 BSkyB -- Sky Mix (running, scrambled) > 0x0000 0x13f1: pmt_pid 0x010d BSkyB -- 1840 (running, scrambled) > 0x0000 0x13f2: pmt_pid 0x010c BSkyB -- 1837 (running, scrambled) > 0x0000 0x1456: pmt_pid 0x0106 BSkyB -- The Box (running, scrambled) > 0x0000 0x1582: pmt_pid 0x0109 BSkyB -- KISS (running, scrambled) > 0x0000 0x16a9: pmt_pid 0x0000 BSkyB -- 1871 (not running, scrambled) > 0x0000 0x16aa: pmt_pid 0x010a BSkyB -- CommunityChnl (running) > 0x0000 0x16ac: pmt_pid 0x010b BSkyB -- Q (running, scrambled) > Network Name 'ASTRA' > Network Name 'ASTRA' > dumping lists (10 services) > Sky One:11343:v:0:27500:515:643:4705 > Sky Mix:11343:v:0:27500:514:642:5104 > 1840:11343:v:0:27500:514:642:5105 > 1837:11343:v:0:27500:514:642:5106 > The Box:11343:v:0:27500:513:641:5206 > KISS:11343:v:0:27500:519:647:5506 > CommunityChnl:11343:v:0:27500:518:646:5802 > Q:11343:v:0:27500:517:645:5804 > [05e7]:11343:v:0:27500:0:0:1511 > 1871:11343:v:0:27500:0:0:5801 > Done. > Try some of these .. channels .. There is no program_number by 4703 . Try saving this to the channels.conf and use some of them .. Manu
