Hi! I have a hunch what could be wrong with the missing files at compilation of the driver (I did locate dvb_frontend.h command on a laptop which has current debian testing but a stock kernel and guess what - no file showed up! Made me think I shouldn't compile dvb core stack as a module. A new custom 2.6.30 kernel compilation is in the runnings to check that.) --after compilation: No, it didn't work. The files are still "missing". I cannot figure out how to tell Debian, that the sources are there (I checked multiple times and they're there). Do I have to tell make anything else to find those files?
Apart from that I did play with the HVR-1900 device on a different host hardware. It's a laptop (HP nc4010) with current Debian testing on it. I compiled the latest snapshot of the driver and tried scanning DVB channels with Kaffeine. Guess what - the same I2C error as reported originally: [ 4391.627459] DVB: registering frontend 0 (NXP TDA10048HN DVB-T)... [ 4391.671809] tda829x 1-0042: type set to tda8295 [ 4391.725905] tda18271 1-0060: attaching existing instance Starting Kaffeine: [ 4401.721213] tda10048_firmware_upload: waiting for firmware upload (dvb-fe-tda10048-1.0.fw)... [ 4401.721225] firmware: requesting dvb-fe-tda10048-1.0.fw [ 4401.730573] tda10048_firmware_upload: firmware read 24878 bytes. [ 4401.730581] tda10048_firmware_upload: firmware uploading [ 4404.944819] tda10048_firmware_upload: firmware uploaded Channel scanning - just the first sequence of repeating messages: [ 4415.908670] tda18271_read_regs: ERROR: i2c_transfer returned: -5 [ 4415.908690] tda18271_ir_cal_init: error -5 on line 786 [ 4415.908698] tda18271_init: error -5 on line 810 [ 4415.908704] tda18271_tune: error -5 on line 831 [ 4415.908711] tda18271_set_params: error -5 on line 912 What I don't understand is, how are these two firmwares for the digital tuner connected (why is device registered with tda10048 but channel scanning uses tda18271)? And from the previous mail you said: >> make INSTALL_MOD_DIR=pvrusb2 -C /lib/modules/2.6.29.4-custom/source >> M=/share/dmz/hardware/Hauppauge/pvrusb2-mci-20090509/driver >> CONFIG_VIDEO_PVRUSB2=m CONFIG_VIDEO_PVRUSB2_24XXX=y >> CONFIG_VIDEO_PVRUSB2_SYSFS=y CONFIG_VIDEO_PVRUSB2_DVB=y >> CONFIG_VIDEO_PVRUSB2_DEBUGIFC=y CONFIG_VIDEO_ADV_DEBUG=y modules > >This is not the procedure I documented. See earlier. (However with >that said, what you have above may still work - it's just not what I >do. I tried to set up the snapshot driver build so that it will <always "play well" with the kernel build system so what you're doing >may very well be fine.) I do not understand - what is different in this config? this make line is displayed as soon as I say make within the driver folder. _______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
