On 09-12-2011 18:04, Eddi De Pieri wrote:
Hi,
v2: Use mfe_shared
on hvr930c this patch solve the commutation issue of frontend.
Ok, good. One issue solved.
still persist same issue like Fredrik on w_scan. scan still works perfectly...
root@depieri1lnx:~# w_scan -f t -c IT
w_scan version 20110616 (compiled for DVB API 5.3)
using settings for ITALY
DVB aerial
DVB-T Europe
frontend_type DVB-T, channellist 4
output format vdr-1.6
output charset 'UTF-8', use -C<charset> to override
Info: using DVB adapter auto detection.
/dev/dvb/adapter0/frontend0 -> DVB-C "DRXK DVB-C": specified was
DVB-T -> SEARCH NEXT ONE.
/dev/dvb/adapter0/frontend1 -> DVB-T "DRXK DVB-T": good :-)
Using DVB-T frontend (adapter /dev/dvb/adapter0/frontend1)
-_-_-_-_ Getting frontend capabilities-_-_-_-_
Using DVB API 5.4
frontend 'DRXK DVB-T' supports
INVERSION_AUTO
QAM_AUTO
TRANSMISSION_MODE_AUTO
GUARD_INTERVAL_AUTO
HIERARCHY_AUTO
FEC_AUTO
FREQ (47.12MHz ... 865.00MHz)
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
Scanning 7MHz frequencies...
[...]
858000: (time: 03:10) (time: 03:13)
ERROR: Sorry - i couldn't get any working frequency/transponder
Nothing to scan!!
this verbose mode seems interesting but I don't figure out why i get timeout.
177500: (time: 00:04) set_frontend: using DVB API 5.4
(time: 00:06) set_frontend: using DVB API 5.4
signal ok:
QAM_AUTO f = 177500 kHz I999B7C999D999T999G999Y999
NIT (actual TS)
new transponder:
(QAM_64 f = 1600000 kHz I999B8C34D0T8G16Y0)
Info: NIT(other) filter timeout
Try to use w_scan with "-F" parameter, to increase the timeout. Maybe this
issue is due to a smaller timeout on w_scan, when compared with scan.
If this doesn't help, then you'll need to figure out what w_scan is doing
different than scan.
Regards,
Mauro.
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
