Hi Mike, I have the same problem here with a HVR-1900. The firmware dvb-fe-tda10048-1.0.fw is needed and after loading a firmware with this name i get the same tunig problems as aljaz.
The analog part of the card works perfectly, analog tuner and video input, but the DVB part has no function so far. I have also looked for the lirc driver, but none were loaded.... So if anyone has an idea.... An other light "problem" is that I use the card also for capture from NTSC video cameras. But as the card is a PAL card, I have to add NTSC mode manually via the sys interface. Is it possible to add a NTSC mode to the list of video norms, even if the card is a PAL card? Thank in advance Steffje On Wednesday 01 April 2009, Mike Isely wrote: > On Mon, 30 Mar 2009, Aljaž Prusnik wrote: > > On ned, 2009-03-22 at 16:46 -0500, Mike Isely wrote: > > > Make sure the lirc driver does not get loaded in the kernel. Even if > > > you're not "using" lirc, the mere existence of the driver could be > > > enough to cause trouble. And once it's gone, power cycle the HVR-1900 > > > so that any screwed up state is cleared out. Power cycling will also > > > cause the pvrusb2 driver to forget everything it previously knew about > > > the device and to reinitialize. > > > If lirc is truly out of the picture here, then I currently do not have > > > any idea why you're getting I2C I/O errors. > > > > Hi! > > > > I tried it once more and had a more profound look at the log. It seems > > that the DVB-T tuner device is different to that in the 1950 model > > because I had to find one more firmware it was requesting: > > > > DVB: registering adapter 0 frontend 0 (NXP TDA10048HN DVB-T)... > > tda829x 2-0042: type set to tda8295 > > tda18271 2-0060: attaching existing instance > > tda10048_firmware_upload: waiting for firmware upload > > (dvb-fe-tda10048-1.0.fw)... > > i2c-adapter i2c-2: firmware: requesting dvb-fe-tda10048-1.0.fw > > > > It's not on your list of firmware files and I had hard time finding it > > (seems to be identified as Technotrend 3650 CI for some reason). So my > > suspicion for the error on the bus is that I'm not using the right > > firmware for this. > > Unfortunately I don't have an HVR-1900 here to test, but even if I did I > doubt I could exercise it properly here since my only available video > sources are NTSC and ATSC. > > It is certainly possible that a particular tuner might need extra > firmware, though I hadn't really thought about that before and until > seeing this post such a situation (that I know of) has not been > encountered. > > If the tuner sub-device is in fact asking for that firmware, then it is > definitely needed. This action is actually outside the control of > the pvrusb2 driver. Sorry about not being aware of this. I will have > to find out what this is and add it to the documentation (and > fwextract.pl, if only for completeness). I doubt unfortunately that it > will be possible to document a "manual extraction" procedure to pick off > that firmware. However there may be another means. I need to do some > digging. > > Hauppauge has had a history of changing tuner types without also > changing the device's model number. If that happens with the HVR-1900 > as well then it's going to create a documentation issue. Up to this > point it has been possible to document the exact firmware types needed > based on the product's model number... > > -Mike _______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
