Mageia forum

Has anyone had any experience with Mageia and support of a USB ATSC turner. LIke:

http://hauppauge.com/site/products/data_hvr955q.html

Kaffeiene is supposed to work with these.

Thanks

Sorry Wilcal - you know what it's like; you hang on to things for years then decide to throw them out (or recycle) and a week or two later "I could have used that now!" Looked everywhere for the WinTV tuner - nowhere. But am virtually certain that it worked with kaffeine. Unfortunately cannot even check what the exact hardware was but it was used only for dvb-t channels from a coax cable.

Is kaffeine not even seeing your tuner?

Looking at /lib/firmware here:

Code: Select all

$ ls *dvb*
dvb-demod-si2168-02.fw      dvb-tuner-si2158-a20-01.fw
dvb-demod-si2168-a20-01.fw  dvb-usb-dib0700-1.20.fw
dvb-demod-si2168-a30-01.fw  dvb-usb-it9135-01.fw
dvb-demod-si2168-b40-01.fw  dvb-usb-it9135-02.fw
dvb-fe-xc4000-1.4.1.fw      dvb-usb-terratec-h5-drxk.fw
dvb-fe-xc5000-1.6.114.fw    sms1xxx-hcw-55xxx-dvbt-02.fw
dvb-fe-xc5000c-4.1.30.7.fw  sms1xxx-nova-a-dvbt-01.fw
dvb_nova_12mhz_b0.inp       sms1xxx-nova-b-dvbt-01.fw
dvb_nova_12mhz.inp          sms1xxx-stellar-dvbt-01.fw


dib0700 was detected by kaffeine at the channel tuning stage when the WinTV card was plugged in. I think most of these should be registered with the em28xx driver. It keeps a table of the supported devices, and way back, doktor5000 showed me a way to examine that but I cannot put my hand on the notes just now. What I am saying is if you have some clue as to the specific hardware component you could see if it matched any of the firmware and then find out if em28xx knows about it. When a device is recognized the firmware is loaded and leaves a trail in the journal I think. Try journalctl and grep on something like dvb.

It could be dmesg though.

Thanks tarazed. Len and I are presently working a bug:

https://bugs.mageia.org/show_bug.cgi?id=21762

which involves Kaffeines ability to use an ATSC USB tuner and Len is using an older device also ( PCTV Systems nanoStick T2 290e ). Aside from pushing this bug on I'd like to leave some notes in this bug referring to which devices like this work on Mageia M5/M6. It appears that the Hauppauge devices have become a default standard. I may have to purchase one of these devices to get this done unless someone has some experience with it or something else.

And the other thing you could look at is the loaded modules:

Code: Select all

$ sudo lsmod | grep em28xx
em28xx_rc              20480  0
rc_core                28672  3 rc_pinnacle_pctv_hd,em28xx_rc
em28xx_dvb             32768  0
dvb_core              122880  2 cxd2820r,em28xx_dvb
em28xx                 90112  2 em28xx_rc,em28xx_dvb
tveeprom               24576  1 em28xx
v4l2_common            16384  1 em28xx
videodev              167936  2 v4l2_common,em28xx
media                  40960  2 videodev,em28xx
usbcore               245760  10 usbhid,usb_storage,ehci_hcd,xhci_pci,em28xx,em28xx_dvb,btusb,uas,xhci_hcd,ehci_pci


tarazed wrote:dib0700 was detected by kaffeine at the channel tuning stage when the WinTV card was plugged in. I think most of these should be registered with the em28xx driver. It keeps a table of the supported devices, and way back, doktor5000 showed me a way to examine that but I cannot put my hand on the notes just now. What I am saying is if you have some clue as to the specific hardware component you could see if it matched any of the firmware and then find out if em28xx knows about it. When a device is recognized the firmware is loaded and leaves a trail in the journal I think. Try journalctl and grep on something like dvb.

Well, at the very least you should provide the vendor and product IDs, either via lspci -vnnk or via lspcidrake -v as the product name itself is not really relevant. E.g. for some wireless devices there are 3 or 4 different revisions, some even using totally different chipsets from different OEM vendors.

Then the other thing is to look what happens after you plugin your device. Try as root with

Code: Select all

journalctl -af

then wait a few seconds and plug your device.

Apart from that I don't get quite the point of the OP. Are you only asking if DVB adapters are working in general for other people or do you want to get your device to work?

No, this is not about any of my hardware. I do have a working tuner already and was trying to provide some support for wilcal because he was having a bit of difficulty with the kaffeine update. You provided a lot of help for me when I was trying to get the "successor" to my tuner to work - same product name but entirely different hardware internally (three chipsets in fact), for which I located the firmware files. You posted a method of interrogating the em28xx driver to see what hardware it actually supports and as far as I remember the three boards were not mentioned. I just cannot remember what it was you told me. That was long ago and I raised a bug with all the relevant information in it and asked if the the em28xx driver could be updated to reference the specific components. Not been done yet.

What I have been trying to suggest to wilcal is that he follow a similar path, find out what electronics his device contains, and see if there is any attempt to load firmware with similar or corresponding names, using journalctl, as you suggested. The point of the lsmod output was to demonstrate that when a device is supported various modules are present, some of which look DVB-tuner-related. There are two in that list which are specific to my working tuner.

The general problem for devices which do not work out of the box can be resolved into three parts as I see it:
1) Identify the chipsets
2) Look for firmware to support those chipsets
3) determine if em28xx knows about the chipsets and the relevant firmware (presumably stored internally as a lookup table or something similar).