On Sunday 05 June 2016 03:02:10 Alexandre GRIVEAUX wrote: > Hi, > > Maybe a firmware you need ? > Maybe found inside firmware-linux-nonfree. > That entry seems to be empty.
However, I did find it. 3 files from the tarball from pchdtv.com, were, when it was last built in Feb 2005, that are supposed to be put in /lib/hotplug/firmware, are now, like all their ilk, in /lib/firmware as -rw-r--r-- 1 root root 12772 Feb 25 22:46 dvb-fe-or51132-qam.fw -rw-r--r-- 1 root root 17532 Feb 25 22:47 dvb-fe-or51132-vsb.fw I now believe I have all the modules showing in an lsmod: gene@coyote:/lib/firmware$ lsmod |grep tuner - tuner_simple 21273 2 tuner_types 16409 1 tuner_simple tuner 25658 2 v4l2_common 12995 3 tuner,cx8800,cx88xx videodev 130540 4 tuner,cx8800,cx88xx,v4l2_common i2c_core 50108 17 drm,cx88_dvb,tuner,drm_kms_helper,tda8290,tda9887,i2c_algo_bit,cx88_vp3054_i2c,cx8800,cx88xx,v4l2_common,tveeprom,nouveau,tuner_simple,or51132,i2c_nforce2,videodev And I was able to modprobe the or51132.ko from the kernel tree, but that made no difference in the reported error. Which is: Using DVB device 0:0 "Oren OR51132 VSB/QAM Frontend" tuning ATSC to 57028000 inv:2 mod:7 ERROR tuning : Inappropriate ioctl for device Frontend closed dvbsi: Cant tune DVB For each channel in the Atsc us table, in this case shown, channel 2, wash, rinse, repeat for all other channels. This is running a channel scan from kaffeine. The channel scan, if kaffeine was launched from a bash shell, also runs at a higher rate such that even if the command "ioctl" was correct, the error comes back and cancels the 5 second timeout in approximately .75 seconds, no where near enough time for this card to achieve a signal lock and show a picture. I know this worked in the previous ubu 10-04 LTS's version of kaffeine, 8.6 IIRC, and this is 8.7 and doesn't work. pcHDTV's own dtvscan does work, finding all the local on air channels and reporting their signal strength ok. All the rest of the test utils that came on the cd, dtvsnr and dtvsignal also work as expected. But even if I feed kaffeine with the data that should at least tune it, no signal is detected because the console has logged that same error as above, but for channel 5. xawtv's scanner, wscan also failed but for other reasons I don't have in the bash history now, and since it was junk I had it removed. Based on that, I am pointing my finger at the newer kaffeine now. But its been years since I've filed a bug. No clue how to do it on wheezy at what could be considered this late date. Or has someone else done that, and found a fix? [...] Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
