On Tuesday 23 February 2016 09:17:34 Thierry de Coulon wrote: > On Tuesday 23 February 2016 09.27:39 Gene Heskett wrote: > > In the event that it works for HD with winderz but not linux, the > > list to ask next would be the v4l list on vger.kernel.org (I think, > > I've not been on it in a couple years) Some pretty sharp digital > > video folks hang out there. You'll need to show them the lspci or > > lsusb/lshw output so they can properly ID the chipset in the stick. > > > > Cheers, Gene Heskett > > I can confirm that it works with Windows (same stick, on the same > machine). There seem to be two problems: > > a) Can Kaffeine display HD TV? If not there's not much to do short of > looking for another program. kaffeine can display HD TV, but I've had to move some firmware around so it could be found and uploaded to my card, and I can report that tv test utilities that are supplied by the pcHDTV-3000 card (that I have) vendor, now display all the local channels signal strengths with dtvscan, and that dtvsnr now reports sensible values on the active channels, and likewise dtvsignal shows sensible signal strengths on the locally active channels. HOWEVER, kaffeine is not finding what dtvscan discovers, IMNSHO because it scans about 20x faster than the card can achieve lock on a new frequency, ignoring the 1.5 to 2 or even 5 seconds allowed for lock time in one of its setup menu's. kaffeine's scanner claims it has scanned half a gigahertz and found nothing in something under a minute. dtvscan takes around 3, maybe 4 minutes, starting at channel 2, to find and report good signals on north american atsc channels 5, 10, 12, and 33. > b) How can I create a new program list, as w_scan crashes (so badly > that it locks the machine competely). You may have something missplaced, before I could make the cards software/firmware load, I had to cp the contents of /usr/lib/hotplug/firmware/* to /lib/firmware. It seems todays systems have moved the default location for this stuff, which for my card, was set 9 years ago, in 2007. Along that same train of thought, perhaps something kaffeine needs has been moved. Its all stable here, no crashes while exploring the dvb menu's, but it doesn't work either. I see it has the ability to manually add a channel but haven't tried that, I should have at least one eye open, which this time of the night locally, isn't always the state. Theoretically, I should be able to use the data that dtvsignal reports to compose a manually added entry. These utilities I mention are of course specific to this card, hopefully you have similar utilities available for your card or dongle? So you may want to take a look at your dmesg output for messages similar to this: [56092.124304] or51132: Waiting for firmware upload(dvb-fe-or51132-vsb.fw)... [56092.124323] cx88-mpeg driver manager 0000:01:08.2: firmware: failed to load dvb-fe-or51132-vsb.fw (-2) [56092.124327] cx88-mpeg driver manager 0000:01:08.2: Direct firmware load failed with error -2 [56092.124329] cx88-mpeg driver manager 0000:01:08.2: Falling back to user helper Which should look more like this, card diffs notwithstanding: [56620.469051] or51132: Waiting for firmware upload(dvb-fe-or51132-vsb.fw)... [56620.469454] cx88-mpeg driver manager 0000:01:08.2: firmware: direct-loading firmware dvb-fe-or51132-vsb.fw [56623.063706] or51132: Version: 10001134-19430000 (113-4-194-3) [56623.064325] or51132: Firmware upload complete. And, noting the cx88 above, an "lsmod | grep cx88" returns quite a lengthy list of suspects: gene@coyote:/usr/src/dvb-atsc-tools-1.0.8$ lsmod |grep cx88 cx88_dvb 30487 0 cx88_vp3054_i2c 12564 1 cx88_dvb videobuf_dvb 12762 1 cx88_dvb dvb_core 101854 3 cx88_dvb,videobuf_dvb,or51132 cx8800 35230 0 cx8802 17368 1 cx88_dvb cx88xx 80293 3 cx88_dvb,cx8800,cx8802 btcx_risc 12555 3 cx8800,cx8802,cx88xx tveeprom 20593 1 cx88xx videobuf_dma_sg 17248 4 cx88_dvb,cx8800,cx8802,cx88xx videobuf_core 21831 5 videobuf_dma_sg,videobuf_dvb,cx8800,cx8802,cx88xx rc_core 22405 13 ir_sharp_decoder,lirc_dev,ir_lirc_codec,rc_hauppauge,ir_rc5_decoder,ir_nec_decoder,ir_sony_decoder,cx88xx,ir_mce_kbd_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_sanyo_decoder v4l2_common 12995 3 tuner,cx8800,cx88xx videodev 130540 4 tuner,cx8800,cx88xx,v4l2_common i2c_algo_bit 12751 3 cx88_vp3054_i2c,cx88xx,nouveau 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 I would assume that for whatever chipset is in your device, you would be getting a similar output as above, chipset diffs notwithsranding. Maybe there is a clue here for you. For me, its plain that kaffeine itself isn't functional as currently configured on my machine, using the TDE version of 8.8. > I'll take a look at the v4l list. thanks. > > Regards, > Thierry Cheers Thierry, 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>