Posts by michaelv

Attached are screenshots of the "TV adapter" tree, ATSC Network, and Muxes.

I have installed LE on an AMD A10-5500 system with a Hauppauge WinTV 2255. Installed the TVHeadEnd server/back-end and configured via http. The LG frontend is listed in the device list, configured a Network (ATSC-T Network), and use the preconfigured MUXes for the Seattle area (confirmed the freqs were correct). There are no channels or services found and the status is failed.

dmesg (http://ix.io/1lmw) shows that the driver is loaded along with the proper version of FW. It appears to start with no error.

[ 19.350505] saa7164[0]: Hauppauge eeprom: model=151061
[ 19.429554] si2157 12-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
[ 19.430177] dvbdev: DVB: registering new adapter (saa7164)
[ 19.430181] saa7164 0000:02:00.0: DVB: registering adapter 0 frontend -1 (LG Electronics LGDT3306A VSB/QAM Frontend)...
[ 19.469669] si2157 13-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
[ 19.470927] dvbdev: DVB: registering new adapter (saa7164)
[ 19.470934] saa7164 0000:02:00.0: DVB: registering adapter 1 frontend -1 (LG Electronics LGDT3306A VSB/QAM Frontend)...
[ 19.508440] saa7164[0]: registered device video0 [mpeg]
[ 19.741914] saa7164[0]: registered device video1 [mpeg]
[ 19.954119] saa7164[0]: registered device vbi0 [vbi]
[ 19.954267] saa7164[0]: registered device vbi1 [vbi]
[ 19.350505] saa7164[0]: Hauppauge eeprom: model=151061
[ 19.429554] si2157 12-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
[ 19.430177] dvbdev: DVB: registering new adapter (saa7164)
[ 19.430181] saa7164 0000:02:00.0: DVB: registering adapter 0 frontend -1 (LG Electronics LGDT3306A VSB/QAM Frontend)...
[ 19.469669] si2157 13-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
[ 19.470927] dvbdev: DVB: registering new adapter (saa7164)
[ 19.470934] saa7164 0000:02:00.0: DVB: registering adapter 1 frontend -1 (LG Electronics LGDT3306A VSB/QAM Frontend)...
[ 19.508440] saa7164[0]: registered device video0 [mpeg]
[ 19.741914] saa7164[0]: registered device video1 [mpeg]
[ 19.954119] saa7164[0]: registered device vbi0 [vbi]
[ 19.954267] saa7164[0]: registered device vbi1 [vbi]

Here's the Kodi log (http://ix.io/1lms), Not that familiar with it, but there's no smoking gun that I see.

I also tried w_scan using the -a option to point to the device directly when auto detect didn't work.

VanceMC:/dev/dvb/adapter0 # w_scan -a /dev/dvb/adapter0/frontend0 0 -fa -A2 -c US -X
w_scan -a /dev/dvb/adapter0/frontend0 0 -fa -A2 -c US -X
w_scan version 20170107 (compiled for DVB API 5.10)
using settings for UNITED STATES
ATSC
QAM US/CA
scan type TERRCABLE_ATSC, channellist 2
output format czap/tzap/szap/xine
WARNING: could not guess your codepage. Falling back to 'UTF-8'
output charset 'UTF-8', use -C <charset> to override
-_-_-_-_ Getting frontend capabilities-_-_-_-_
main:4019: FATAL: FE_GET_INFO failed: 19 No such device

I need some help determining why this isn't working.

Thanks.