DevHeads.net

Difficul;ties with trying to install and use tv adaptor

Hello.

I have purchased and tried to install, a tv adaptor;
AVerMedia A867R AVerTV Volar HD Nano USB TV Tuner
for PAL digital television in Austyralia, on UbuntuMATE 16.04.x

I have tried to do it on two separate computers.

I tried to inslall MythTV, which would not install from the Ubuntu
Software Centre, because it wants to get rid of MySQL, also tried to
install MeTV and TVTime.

Amongst other problems, apparently, the tv device is not detected.

Ins earching to find whether Linux drivers are available for the
device (the advertisements showed that it should work with Linux, and,
the shop salesperson told me that it should work with MythTV running
on Linux), I found, from
<a href="https://www.mail-archive.com/search?q=a867r&amp;l=linux-media%40vger.kernel.org" title="https://www.mail-archive.com/search?q=a867r&amp;l=linux-media%40vger.kernel.org">https://www.mail-archive.com/search?q=a867r&amp;l=linux-media%40vger.kernel.org</a>
that, as of 2012, Linux apparently incororayed a driver for the device.

But, the device is apparently not detected, and IO can not use it.

On the MythTV list, apparently, a process exists for installing (the
latest version of) MythTV, on Ubuntu, but, the Ubuntu version of
MythTV, apparently requires the elimination of MySQL.

I am wondering whether a simple method exists, of getting this device
working on UbuntuMATE Linux 16.04, without having to eliminate MySQL.

Thank you in anticipation.

Comments

Re: Difficul;ties with trying to install and use tv adaptor

By Oliver Grawert at 05/13/2018 - 05:00

Am Sonntag, den 13.05.2018, 05:25 +0800 schrieb Bret Busby:
the chipset seems to be an Afatech AF9035

<a href="https://www.linuxtv.org/wiki/index.php/Afatech_AF9035" title="https://www.linuxtv.org/wiki/index.php/Afatech_AF9035">https://www.linuxtv.org/wiki/index.php/Afatech_AF9035</a>

what happens if you manually "modprobe dvb-usb-af9035", do you see it
get detected in dmesg ?

it seems to have in fact been first added in linux 3.7-rc1 in 2012:

<a href="https://github.com/torvalds/linux/commit/5da2aecb46597c2b4a3dee2eb78863" title="https://github.com/torvalds/linux/commit/5da2aecb46597c2b4a3dee2eb78863">https://github.com/torvalds/linux/commit/5da2aecb46597c2b4a3dee2eb78863</a>
fee0c8354e

so it should theoretically work ... 

ciao
oli

Re: Difficul;ties with trying to install and use tv adaptor

By Bret Busby at 05/13/2018 - 05:12

On 13/05/2018, Oliver Grawert < ... at ubuntu dot com> wrote:
"
~$ modprobe dvb-usb-af9035
modprobe dvb-usb-af9035: command not found
bret@bret-Inspiron-580-UbuntuMATE:~$ sudo modprobe dvb-usb-af9035
[sudo] password for bret:
sudo: modprobe dvb-usb-af9035: command not found
"

Re: Difficul;ties with trying to install and use tv adaptor

By Oliver Grawert at 05/13/2018 - 08:13

hi,
Am Sonntag, den 13.05.2018, 17:12 +0800 schrieb Bret Busby:
modprobe missing on your system sounds like an actually more serious
problem ... 

what does "which modprobe" return (should be /sbin/modprobe)
...

this is what you *should* see:

ogra@acheron:~$ sudo modprobe dvb-usb-af9035
[sudo] Passwort für ogra: 
ogra@acheron:~$ lsmod |grep af9035
dvb_usb_af9035         40960  0
dvb_usb_v2             40960  1 dvb_usb_af9035
rc_core                36864  2 dvb_usb_af9035,dvb_usb_v2

(and if the device is correctly initialized you should see proper
entries for this at the end of the "dmesg" output)

ciao
oli

Re: Difficul;ties with trying to install and use tv adaptor

By Bret Busby at 05/13/2018 - 09:34

On 13/05/2018, Oliver Grawert < ... at ubuntu dot com> wrote:
Hello.

"
bret@bret-Inspiron-580-UbuntuMATE:~$ which modprobe
/sbin/modprobe
bret@bret-Inspiron-580-UbuntuMATE:~$ sudo modprobe dvb-usb-af9035
[sudo] password for bret:
bret@bret-Inspiron-580-UbuntuMATE:~$ lsmod |grep af9035
dvb_usb_af9035 36864 0
dvb_usb_v2 36864 1 dvb_usb_af9035
rc_core 28672 3 dvb_usb_v2,dvb_usb_af9035
"

at end of dmesg output;

"
[2069430.144425] sd 3:0:0:0: [sdb] tag#0 FAILED Result:
hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[2069430.144436] sd 3:0:0:0: [sdb] tag#0 Sense Key : Hardware Error
[current] [descriptor]
[2069430.144442] sd 3:0:0:0: [sdb] tag#0 Add. Sense: No additional
sense information
[2069430.144449] sd 3:0:0:0: [sdb] tag#0 CDB: ATA command pass
through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
[2069430.269609] sd 3:0:0:0: [sdb] tag#0 FAILED Result:
hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[2069430.269621] sd 3:0:0:0: [sdb] tag#0 Sense Key : Hardware Error
[current] [descriptor]
[2069430.269627] sd 3:0:0:0: [sdb] tag#0 Add. Sense: No additional
sense information
[2069430.269634] sd 3:0:0:0: [sdb] tag#0 CDB: ATA command pass
through(12)/Blank a1 06 20 da 00 00 4f c2 00 b0 00 00
[2069443.259199] [UFW BLOCK] IN=enp3s0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[2069568.250698] [UFW BLOCK] IN=enp3s0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[2069693.242087] [UFW BLOCK] IN=enp3s0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2

"

I am hoping that that is meaningful to you - to me, it looks like
something is wrong, but I can not interpret the output beyond that.

Re: Difficul;ties with trying to install and use tv adaptor

By Oliver Grawert at 05/13/2018 - 09:56

hi,
Am Sonntag, den 13.05.2018, 21:34 +0800 schrieb Bret Busby:

well, it shows an issue with an "sdb" disk device ... not sure this is
even remotely related to your dvb tuner ...

ciao
oli

Re: Difficul;ties with trying to install and use tv adaptor

By Bret Busby at 05/13/2018 - 10:27

On 13/05/2018, Oliver Grawert < ... at ubuntu dot com> wrote:
From df -h the only sdb device connected to the system, is a 500MB
external HP HDD, and, in the file manager, I seem to be able to access
that okay, so I do not know what the problem would be.

Re: Difficul;ties with trying to install and use tv adaptor

By Nils Kassube at 05/13/2018 - 01:14

Bret Busby wrote:
What is the output of the command

ls /dev/dvb

in a terminal when the device is connected? If there is no directory at
that location, what is the output of

lsusb

where it should have an entry for the device with the device name or at
least an entry for Avermedia.

And maybe there is only a missing firmware. You may need the package
linux-firmware-nonfree.

I would suggest to use kaffeine instead of MythTV - there is no conflict
with mysql and it is the best application for DVB reception IMHO.

Nils

Re: Difficul;ties with trying to install and use tv adaptor

By Bret Busby at 05/13/2018 - 03:02

On 13/05/2018, Nils Kassube < ... at gmx dot net> wrote:
"
bret@bret-Inspiron-580-UbuntuMATE:~$ s /dev/dvb
s: command not found
bret@bret-Inspiron-580-UbuntuMATE:~$ ls /dev/dvb
ls: cannot access '/dev/dvb': No such file or directory
bret@bret-Inspiron-580-UbuntuMATE:~$ lsusb
Bus 002 Device 004: ID 03f0:4507 Hewlett-Packard External HDD
Bus 002 Device 019: ID 07ca:1867 AVerMedia Technologies, Inc.
Bus 002 Device 003: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
Bus 001 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial
Bus 001 Device 003: ID 04d9:1503 Holtek Semiconductor, Inc. Keyboard
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
"

Re: Difficul;ties with trying to install and use tv adaptor

By Nils Kassube at 05/13/2018 - 05:38

Bret Busby wrote:
OK, searching for "07ca:1867" reveals
<https://www.linuxtv.org/wiki/index.php/Afatech_AF9035>. The entry for
your device says that it is supported with an unstable driver from
Avermedia, which doesn't look too good. But searching further I also
found this description which looks quite promising:
<https://www.onetransistor.eu/2016/10/sky-digital-key-avermedia-a867-pc.html>.

And sorry about the package name linux-firmware-nonfree. This package
seems to be no longer available for 16.04 (I had only checked it on my
14.04 machine).

Nils

Re: Difficul;ties with trying to install and use tv adaptor

By Bret Busby at 05/13/2018 - 05:59

On 13/05/2018, Nils Kassube < ... at gmx dot net> wrote:
Hello.

Thank you for that.

As you said, it sounds quite promising.

However, having followed the instructions, ...

dmesg shows

"
[2056626.587341] usb 2-1.3: new high-speed USB device number 21 using ehci-pci
[2056626.685318] usb 2-1.3: New USB device found, idVendor=07ca, idProduct=1867
[2056626.685325] usb 2-1.3: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[2056626.685330] usb 2-1.3: Product: A867
[2056626.685334] usb 2-1.3: Manufacturer: AVerMedia TECHNOLOGIES, Inc
[2056626.685338] usb 2-1.3: SerialNumber: 0500093000090
[2056626.688059] usb 2-1.3: dvb_usb_af9035: prechip_version=00
chip_version=03 chip_type=3802
[2056626.688431] usb 2-1.3: dvb_usb_v2: found a 'AVerMedia HD Volar
(A867)' in cold state
[2056626.688495] usb 2-1.3: dvb_usb_v2: downloading firmware from file
'dvb-usb-af9035-02.fw'
[2056626.991868] usb 2-1.3: dvb_usb_af9035: firmware version=12.13.15.0
[2056626.991887] usb 2-1.3: dvb_usb_v2: found a 'AVerMedia HD Volar
(A867)' in warm state
[2056626.994098] usb 2-1.3: dvb_usb_v2: will pass the complete MPEG2
transport stream to the software demuxer
[2056626.994126] DVB: registering new adapter (AVerMedia HD Volar (A867))
[2056627.016782] af9033 12-0038: firmware version: LINK 12.13.15.0 -
OFDM 6.20.15.0
[2056627.020850] af9033 12-0038: Afatech AF9033 successfully attached
[2056627.020871] usb 2-1.3: DVB: registering adapter 0 frontend 0
(Afatech AF9033 (DVB-T))...
[2056627.420831] mxl5007t 12-0060: creating new instance
[2056627.421547] mxl5007t_get_chip_id: unknown rev (3f)
[2056627.421551] mxl5007t_get_chip_id: MxL5007T detected @ 12-0060
[2056627.435915] Registered IR keymap rc-empty
[2056627.436042] input: AVerMedia HD Volar (A867) as
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/rc/rc0/input26
[2056627.436285] rc0: AVerMedia HD Volar (A867) as
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/rc/rc0
[2056627.436291] usb 2-1.3: dvb_usb_v2: schedule remote query interval
to 500 msecs
[2056627.436295] usb 2-1.3: dvb_usb_v2: 'AVerMedia HD Volar (A867)'
successfully initialized and connected
[2056630.435532] usb 2-1.3: dvb_usb_v2: 2nd usb_bulk_msg() failed=-110
[2056630.435542] usb 2-1.3: dvb_usb_v2: rc.query() failed=-110
[2056659.469102] nouveau 0000:01:00.0: Direct firmware load for
nouveau/nva8_fuc084 failed with error -2
[2056659.469116] nouveau 0000:01:00.0: Direct firmware load for
nouveau/nva8_fuc084d failed with error -2
[2056659.469120] nouveau 0000:01:00.0: msvld: unable to load firmware data
[2056659.469124] nouveau 0000:01:00.0: msvld: init failed, -19
[2056694.243576] [UFW BLOCK] IN=enp3s0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
"

Now, dmesg stuff is beyond my limited knowledge, but, I am wondering
whetehr an incompatibility between the driver and nouveau, exists?

Re: Difficul;ties with trying to install and use tv adaptor

By Bret Busby at 05/13/2018 - 06:37

On 13/05/2018, Bret Busby <bret. ... at gmail dot com> wrote:

I do not know whether it is an incompatibility with nouveau, or
something else, but, I decided to try running Kaffeine, and, to see
what happened, and, it kind of partially worked, but I could ne access
the television broadcasts..

Kaffeine detected the device, and, after messing around with some
aerial connections, and, configuration settings, I goy it to scan,
and, it found two of the five (?) available free to air networks, and,
found most of the channels for them, but, in having added the scan
results to the box on the left side, and, selecting one of the
channels, I do not know how to view what is being broadcast on the
television channel.

Re: Difficul;ties with trying to install and use tv adaptor

By oxy via ubuntu-users at 05/13/2018 - 07:42

13 May 2018 at 18:37, Bret Busby wrote:
Re: Difficul;ties with trying to in (at least in part)

IIRC you need to add some extra codacs, but it does (or did here) throw a
dialogue telling you which and may even atempt to download for you (it's been a
while)

Re: Difficul;ties with trying to install and use tv adaptor

By Nils Kassube at 05/13/2018 - 07:05

Bret Busby wrote:
To view TV you should close the window where you scanned for the
channels. Then at the kaffeine start screen select the digital TV button
and it should display the first channel.

If that works, you can try to scan again with the antenna at a different
location (I suppose you use the small whip antenna which probably came
with the device). If you are not really close to the transmitter, the
antenna location may be critical.

Nils

Re: Difficul;ties with trying to install and use tv adaptor

By Bret Busby at 05/13/2018 - 04:00

On 13/05/2018, Bret Busby <bret. ... at gmail dot com> wrote:
Searchimng in synaptic, ddi not find the package linux-firmware-nonfree
but, in searching on the term firmware, I found, and, installed, using apt-get,
firmware-tools firmware-addon-dell firmware-extract

"
$ sudo apt-get install linux-firmware-nonfree
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-firmware-nonfree

"

Re: Difficul;ties with trying to install and use tv adaptor

By oxy via ubuntu-users at 05/13/2018 - 03:37

13 May 2018 at 7:14, Nils Kassube wrote:
Re: Difficul;ties with trying to in (at least in part)

I would give Kaffiene a try, it worked a treat on my old DBV-TV addaptor

Re: Difficul;ties with trying to install and use tv adaptor

By Bret Busby at 05/13/2018 - 03:46

<snip>

Yes, I have tried Kaffeine, but I think that the system needs a driver
for the device.

Re: Difficul;ties with trying to install and use tv adaptor

By oxy via ubuntu-users at 05/13/2018 - 07:42

13 May 2018 at 15:46, Bret Busby wrote:
Re: Difficul;ties with trying to in (at least in part)

I'm not familia with your adaptor, and if (or not) Ubuntu supports it
out-of-the-box, I did find a driver for it here

<a href="https://www.avermedia.com/tv_more/download/avertv_volar_hd_nano" title="https://www.avermedia.com/tv_more/download/avertv_volar_hd_nano">https://www.avermedia.com/tv_more/download/avertv_volar_hd_nano</a>

<a href="http://storage.avermedia.com/web_release_www/A867R/A867R_drv_v1.0.29_20160707.ta" title="http://storage.avermedia.com/web_release_www/A867R/A867R_drv_v1.0.29_20160707.ta">http://storage.avermedia.com/web_release_www/A867R/A867R_drv_v1.0.29_201...</a>
r.bz2

I do note that all the info I can find dates back 6 to 8 years

Re: Difficul;ties with trying to install and use tv adaptor

By Bret Busby at 05/15/2018 - 08:31

On 13/05/2018, Grizzly via ubuntu-users <ubuntu- ... at lists dot ubuntu.com> wrote:
Having, on another system, run the commands as published on the web
page of the second link above, and, having downloaded the driver, I
get the following; the first part is the tail end of the dmesg output,
the second part is where the driver got downloaded.

Why is it not found?

"
[5024767.393352] usb 3-6.3: new high-speed USB device number 18 using xhci_hcd
[5024767.487069] usb 3-6.3: New USB device found, idVendor=07ca, idProduct=1867
[5024767.487083] usb 3-6.3: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[5024767.487085] usb 3-6.3: Product: A867
[5024767.487086] usb 3-6.3: Manufacturer: AVerMedia TECHNOLOGIES, Inc
[5024767.487088] usb 3-6.3: SerialNumber: 0500093000090
[5024767.489915] usb 3-6.3: dvb_usb_af9035: prechip_version=00
chip_version=03 chip_type=3802
[5024767.490306] usb 3-6.3: dvb_usb_v2: found a 'AVerMedia HD Volar
(A867)' in cold state
[5024767.534535] usb 3-6.3: Direct firmware load for
dvb-usb-af9035-02.fw failed with error -2
[5024767.534540] usb 3-6.3: dvb_usb_v2: Did not find the firmware file
'dvb-usb-af9035-02.fw'. Please see linux/Documentation/dvb/ for more
details on firmware-problems. Status -2
[5024767.534549] dvb_usb_af9035: probe of 3-6.3:1.0 failed with error -2
[5024768.167213] [UFW BLOCK] IN=eth0 OUT= MAC=
SRC=fe80:0000:0000:0000:5759:b093:254d:dbca
DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1
FLOWLBL=293196 PROTO=UDP SPT=8612 DPT=8612 LEN=24
[5024768.167226] [UFW BLOCK] IN=eth0 OUT= MAC=
SRC=fe80:0000:0000:0000:5759:b093:254d:dbca
DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1
FLOWLBL=581787 PROTO=UDP SPT=8612 DPT=8610 LEN=24
[5024768.177412] [UFW BLOCK] IN=eth0 OUT= MAC=
SRC=fe80:0000:0000:0000:5759:b093:254d:dbca
DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1
FLOWLBL=293196 PROTO=UDP SPT=8612 DPT=8612 LEN=24
[5024864.300839] [UFW BLOCK] IN=eth0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[5024989.298216] [UFW BLOCK] IN=eth0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[5025114.296602] [UFW BLOCK] IN=eth0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[5025239.293681] [UFW BLOCK] IN=eth0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[5025364.291544] [UFW BLOCK] IN=eth0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[5025489.290511] [UFW BLOCK] IN=eth0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[5025614.289294] [UFW BLOCK] IN=eth0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[5025739.287975] [UFW BLOCK] IN=eth0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[5025864.287176] [UFW BLOCK] IN=eth0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
bret@bret-Aspire-V3-772-UbuntuMATE:~$ ls /lib/firmware
3.19.0-31-generic ct2fw-3.2.3.0.bin
ipw2100-1.3-i.fw iwlwifi-7260-9.ucode mrvl
r128 tigon
3com ct2fw-3.2.5.1.bin
ipw2100-1.3-p.fw iwlwifi-7265-10.ucode
mt7601u.bin r8a779x_usb3_v1.dlmem
ti-keystone
4.4.0-112-generic ctefx.bin ipw2200-bss.fw
iwlwifi-7265-12.ucode mt7650.bin
r8a779x_usb3_v2.dlmem tlg2300_firmware.bin
4.4.0-116-generic ctfw-3.2.1.1.bin ipw2200-ibss.fw
iwlwifi-7265-13.ucode mts_cdma.fw
r8a779x_usb3_v3.dlmem ttusb-budget
4.4.0-59-generic ctfw-3.2.3.0.bin
ipw2200-sniffer.fw iwlwifi-7265-16.ucode
mts_edge.fw radeon
ueagle-atm
a300_pfp.fw ctfw-3.2.5.1.bin isci
iwlwifi-7265-17.ucode mts_gsm.fw
README usbdux
a300_pm4.fw ctspeq.bin
iwlwifi-1000-5.ucode iwlwifi-7265-8.ucode
mts_mt9234mu.fw rp2.fw
usbduxfast_firmware.bin
acenic cxgb3
iwlwifi-100-5.ucode iwlwifi-7265-9.ucode
mts_mt9234zba.fw RS9113_AP_BT_DUAL_MODE.rps
usbdux_firmware.bin
adaptec cxgb4
iwlwifi-105-6.ucode iwlwifi-7265D-10.ucode mwl8k
RS9113_WLAN_BT_DUAL_MODE.rps
usbduxsigma_firmware.bin
advansys dsp56k
iwlwifi-135-6.ucode iwlwifi-7265D-12.ucode mwlwifi
RS9113_WLAN_QSPI.rps
v4l-cx231xx-avcore-01.fw
agere_ap_fw.bin dvb-fe-xc4000-1.4.1.fw
iwlwifi-2000-6.ucode iwlwifi-7265D-13.ucode
myri10ge_eth_big_z8e.dat rsi_91x.fw
v4l-cx23418-apu.fw
agere_sta_fw.bin dvb-fe-xc5000-1.6.114.fw
iwlwifi-2030-6.ucode iwlwifi-7265D-16.ucode
myri10ge_ethp_big_z8e.dat rt2561.bin
v4l-cx23418-cpu.fw
amdgpu dvb-fe-xc5000c-4.1.30.7.fw
iwlwifi-3160-10.ucode iwlwifi-7265D-17.ucode
myri10ge_ethp_z8e.dat rt2561s.bin
v4l-cx23418-dig.fw
ar3k dvb-usb-af9035-02.fw
iwlwifi-3160-12.ucode iwlwifi-7265D-21.ucode
myri10ge_eth_z8e.dat rt2661.bin
v4l-cx2341x-dec.fw
ar5523.bin dvb-usb-dib0700-1.20.fw
iwlwifi-3160-13.ucode iwlwifi-7265D-22.ucode
myri10ge_rss_eth_big_z8e.dat rt2860.bin
v4l-cx2341x-enc.fw
as102_data1_st.hex dvb-usb-it9135-01.fw
iwlwifi-3160-16.ucode iwlwifi-7265D-27.ucode
myri10ge_rss_ethp_big_z8e.dat rt2870.bin
v4l-cx2341x-init.mpg
as102_data2_st.hex dvb-usb-it9135-02.fw.bak
iwlwifi-3160-17.ucode iwlwifi-7265D-29.ucode
myri10ge_rss_ethp_z8e.dat rt3070.bin
v4l-cx23885-avcore-01.fw
asihpi dvb-usb-terratec-h5-drxk.fw
iwlwifi-3160-7.ucode iwlwifi-8000C-13.ucode
myri10ge_rss_eth_z8e.dat rt3090.bin
v4l-cx25840.fw
ath10k ea
iwlwifi-3160-8.ucode iwlwifi-8000C-16.ucode netronome
rt3290.bin
v4l-pvrusb2-24xxx-01.fw
ath3k-1.fw edgeport
iwlwifi-3160-9.ucode iwlwifi-8000C-21.ucode NPE-B
rt73.bin
v4l-pvrusb2-29xxx-01.fw
ath6k emi26
iwlwifi-3168-21.ucode iwlwifi-8000C-27.ucode NPE-C
RTL8192E vicam
ath9k_htc emi62
iwlwifi-3168-22.ucode iwlwifi-8000C-31.ucode nvidia
rtl_bt vntwusb.fw
atmel ene-ub6250
iwlwifi-3168-27.ucode iwlwifi-8265-21.ucode ositech
rtl_nic vpu_d.bin
atmel_at76c504_2958.bin ess
iwlwifi-3168-29.ucode iwlwifi-8265-22.ucode phanfw.bin
rtlwifi vpu_p.bin
atmel_at76c504a_2958.bin f2255usb.bin
iwlwifi-3945-2.ucode iwlwifi-8265-27.ucode
qat_895xcc.bin s2250.fw vxge
atmsar11.fw go7007
iwlwifi-4965-2.ucode iwlwifi-8265-31.ucode
qat_895xcc_mmp.bin s2250_loader.fw
WHENCE.ubuntu
atusb GPL-3
iwlwifi-5000-5.ucode iwlwifi-9000-pu-b0-jf-b0-33.ucode
qat_c3xxx.bin s5p-mfc.fw
whiteheat.fw
av7110 hfi1_dc8051.fw
iwlwifi-5150-2.ucode iwlwifi-9260-th-b0-jf-b0-33.ucode
qat_c3xxx_mmp.bin s5p-mfc-v6.fw
whiteheat_loader.fw
bnx2x hfi1_fabric.fw
iwlwifi-6000-4.ucode kaweth
qat_c62x.bin s5p-mfc-v6-v2.fw
wil6210.brd
brcm hfi1_pcie.fw
iwlwifi-6000g2a-5.ucode keyspan
qat_c62x_mmp.bin s5p-mfc-v7.fw
wil6210.fw
carl9170-1.fw hfi1_sbus.fw
iwlwifi-6000g2a-6.ucode keyspan_pda
qat_mmp.bin s5p-mfc-v8.fw
wsm_22.bin
carl9170fw hp
iwlwifi-6000g2b-6.ucode korg qca
sb16 yam
cavium htc_7010.fw
iwlwifi-6050-5.ucode lbtf_usb.bin qcom
scripts yamaha
cbfw-3.2.1.1.bin htc_9271.fw
iwlwifi-7260-10.ucode lgs8g75.fw qed
sdd_sagrad_1091_1098.bin zd1201-ap.fw
cbfw-3.2.3.0.bin i2400m-fw-usb-1.4.sbcf
iwlwifi-7260-12.ucode libertas
ql2100_fw.bin slicoss zd1201.fw
cbfw-3.2.5.1.bin i2400m-fw-usb-1.5.sbcf
iwlwifi-7260-13.ucode liquidio
ql2200_fw.bin sun zd1211
cis i6050-fw-usb-1.5.sbcf
iwlwifi-7260-16.ucode Makefile
ql2300_fw.bin tehuti
configure i915
iwlwifi-7260-17.ucode matrox
ql2322_fw.bin ti_3410.fw
cpia2 intel
iwlwifi-7260-7.ucode mellanox
ql2400_fw.bin ti_5052.fw
ct2fw-3.2.1.1.bin ipw2100-1.3.fw
iwlwifi-7260-8.ucode moxa
ql2500_fw.bin ti-connectivity
bret@bret-Aspire-V3-772-UbuntuMATE:~$
"

Re: Difficul;ties with trying to install and use tv adaptor

By Bret Busby at 05/15/2018 - 09:58

On 15/05/2018, Bret Busby <bret. ... at gmail dot com> wrote:

It seems strange to me, but, after half an hour or so, the firmware
seems to take effect, and, away it goes.

The only thing is that, on this computer, the sound is all weird. The
voices, in the programmes, are too quite to be heard, but, the
incidental music comes through okay.

Re: Difficul;ties with trying to install and use tv adaptor

By Bret Busby at 05/15/2018 - 13:23

On 15/05/2018, Bret Busby <bret. ... at gmail dot com> wrote:
So, I shuitdown the tv application, and unplug the TV tuner device,
and plug it back into the computer in which I had it previousl;y
working (to an extent).

"There are no DVB devices available".

So, in running dmesg, at the end, I get

"
[2245750.577766] usb 2-1.3: new high-speed USB device number 23 using ehci-pci
[2245750.675826] usb 2-1.3: New USB device found, idVendor=07ca, idProduct=1867
[2245750.675834] usb 2-1.3: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[2245750.675839] usb 2-1.3: Product: A867
[2245750.675844] usb 2-1.3: Manufacturer: AVerMedia TECHNOLOGIES, Inc
[2245750.675848] usb 2-1.3: SerialNumber: 0500093000090
[2245752.681913] usb 2-1.3: dvb_usb_v2: 2nd usb_bulk_msg() failed=-110
[2245752.681936] dvb_usb_af9035: probe of 2-1.3:1.0 failed with error -110
[2245753.521409] [UFW BLOCK] IN=enp3s0 OUT= MAC=
SRC=fe80:0000:0000:0000:be0a:f0db:0a41:0e2c
DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1
FLOWLBL=867240 PROTO=UDP SPT=8612 DPT=8612 LEN=24
[2245753.521432] [UFW BLOCK] IN=enp3s0 OUT= MAC=
SRC=fe80:0000:0000:0000:be0a:f0db:0a41:0e2c
DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1
FLOWLBL=359688 PROTO=UDP SPT=8612 DPT=8610 LEN=24
[2245753.531667] [UFW BLOCK] IN=enp3s0 OUT= MAC=
SRC=fe80:0000:0000:0000:be0a:f0db:0a41:0e2c
DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1
FLOWLBL=867240 PROTO=UDP SPT=8612 DPT=8612 LEN=24
[2245753.531705] [UFW BLOCK] IN=enp3s0 OUT= MAC=
SRC=fe80:0000:0000:0000:be0a:f0db:0a41:0e2c
DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1
FLOWLBL=359688 PROTO=UDP SPT=8612 DPT=8610 LEN=24
[2245805.122250] [UFW BLOCK] IN=enp3s0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[2245824.457593] sd 3:0:0:0: [sdb] tag#0 FAILED Result:
hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[2245824.457599] sd 3:0:0:0: [sdb] tag#0 Sense Key : Hardware Error
[current] [descriptor]
[2245824.457601] sd 3:0:0:0: [sdb] tag#0 Add. Sense: No additional
sense information
[2245824.457605] sd 3:0:0:0: [sdb] tag#0 CDB: ATA command pass
through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
[2245824.586246] sd 3:0:0:0: [sdb] tag#0 FAILED Result:
hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[2245824.586254] sd 3:0:0:0: [sdb] tag#0 Sense Key : Hardware Error
[current] [descriptor]
[2245824.586257] sd 3:0:0:0: [sdb] tag#0 Add. Sense: No additional
sense information
[2245824.586262] sd 3:0:0:0: [sdb] tag#0 CDB: ATA command pass
through(12)/Blank a1 06 20 da 00 00 4f c2 00 b0 00 00
[2245930.114501] [UFW BLOCK] IN=enp3s0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
"

So, I figure that I will leave it for at least half an hour, and, try again...

So, after a while, the end of dmesg becomes

"
[2247024.423591] sd 3:0:0:0: [sdb] tag#0 FAILED Result:
hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[2247024.423602] sd 3:0:0:0: [sdb] tag#0 Sense Key : Hardware Error
[current] [descriptor]
[2247024.423607] sd 3:0:0:0: [sdb] tag#0 Add. Sense: No additional
sense information
[2247024.423613] sd 3:0:0:0: [sdb] tag#0 CDB: ATA command pass
through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
[2247024.544447] sd 3:0:0:0: [sdb] tag#0 FAILED Result:
hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[2247024.544459] sd 3:0:0:0: [sdb] tag#0 Sense Key : Hardware Error
[current] [descriptor]
[2247024.544465] sd 3:0:0:0: [sdb] tag#0 Add. Sense: No additional
sense information
[2247024.544474] sd 3:0:0:0: [sdb] tag#0 CDB: ATA command pass
through(12)/Blank a1 06 20 da 00 00 4f c2 00 b0 00 00
[2247055.037532] [UFW BLOCK] IN=enp3s0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[2247180.028130] [UFW BLOCK] IN=enp3s0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[2247305.020301] [UFW BLOCK] IN=enp3s0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[2247430.011472] [UFW BLOCK] IN=enp3s0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[2247555.001687] [UFW BLOCK] IN=enp3s0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
[2247628.286986] sd 3:0:0:0: [sdb] tag#0 FAILED Result:
hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[2247628.286997] sd 3:0:0:0: [sdb] tag#0 Sense Key : Hardware Error
[current] [descriptor]
[2247628.287003] sd 3:0:0:0: [sdb] tag#0 Add. Sense: No additional
sense information
[2247628.287011] sd 3:0:0:0: [sdb] tag#0 CDB: ATA command pass
through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
[2247628.414366] sd 3:0:0:0: [sdb] tag#0 FAILED Result:
hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[2247628.414377] sd 3:0:0:0: [sdb] tag#0 Sense Key : Hardware Error
[current] [descriptor]
[2247628.414383] sd 3:0:0:0: [sdb] tag#0 Add. Sense: No additional
sense information
[2247628.414390] sd 3:0:0:0: [sdb] tag#0 CDB: ATA command pass
through(12)/Blank a1 06 20 da 00 00 4f c2 00 b0 00 00
[2247679.993142] [UFW BLOCK] IN=enp3s0 OUT=
MAC=01:00:5e:00:00:01:f8:ab:05:8e:34:fa:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
"

MeTV still returns
"There are no DVB devices available".

and Kaffeine shows

"Device not connected"

......

So, a couple of hours later, it started working again.

It appears to take a couple of hours, for the software to detect the
device and the signals.

Re: Difficul;ties with trying to install and use tv adaptor

By Nils Kassube at 05/15/2018 - 16:10

Bret Busby wrote:
Obviously the kernel doesn't find the firmware 'dvb-usb-af9035-02.fw'.
That's quite strange because of this:

So the file is in /lib/firmware but it isn't found?!??

Did you replug the device before it worked?

Unfortunately there is no reason mentioned why the probe failed.

It would be nice if you would remove all the tons of UFW messages and
also the sdb errors. Both have nothing to do with your DVB device and it
would make the dmseg output readable.

When you "try again", you replug the device?

Well there was nothing about the DVB device ... maybe you shouldn't send
the end of the dmesg output but rather what seems to be relevant for the
DVB device. I would suggest the command

dmesg | grep -i -A3 dvb

Of course that is expected if the dvb_usb_af9035 probe failed.

But did you replug the device before it started to work?

Which is quite unlikely IMHO. It only takes a few seconds for a DVB
device to be available for the applications. I'd rather suppose a
problem with the USB connection. As there seems to be a problem with two
different machines, I would expect the problem to be at the device or
the USB cable and not the computer.

Another reason for problems would be a USB hub if you use one. All the
TV devices I had so far wanted to use the maximum available current from
the USB port and there would be nothing left for a USB hub. So if you
use a USB hub, try to connect the device directly to the computer.

Nils

Re: Difficul;ties with trying to install and use tv adaptor

By Bret Busby at 05/15/2018 - 17:37

On 16/05/2018, Nils Kassube < ... at gmx dot net> wrote:

<snip>

Yes, I had done that, a number of times, on each computer.

With both computers; one having an i7CPU and 32GB of RAM, and, the
other having an i3CPU and 16GB of RAM, whilst it may appear to be
neither credible nor rational, it does take about two hours, for the
software to detect the device, and, to detect the television signals.

That much, I have managed to figure out - by waiting a couple of
hours, it works (inasmuch as it does work).

Both computers have the USB port used for the device, next to a USB
port that is used for an external HDD.

The i7 system needed for me to use a hub for the TV tuner device, as
the molding around the metallic part of the USB plug on it, is too
wide to fit into the USB socket when the adjacent USB socket is used.
However, on that computer, I was able to kind of use Kaffeine (it did
display the video from the television channels, and, it did detect two
of the television networks, whereas, on the i3 system, it did not do
either), but, as mentioned previously, the sound was weird, as
previously described. That weirdness of the sound, applied to both
Kaffeine and MeTV, on that computer.

As mentioned above. The i3 computer does not involve a hub, in the
connection of the TV tuner device to the computer. Only MeTV works
with the TV tuner device on that computer, and, it detects only one
network of the five networks and a standalone (community) television
channel.

Re: Difficul;ties with trying to install and use tv adaptor

By Nils Kassube at 05/16/2018 - 09:17

Bret Busby wrote:
OK, then maybe the firmware load works only sometimes, which is of
course strange.

As it takes so long to find the device on both machines, I would suppose
that the device is faulty. Kaffeine or MeTV should detect it within a
few seconds after it is inserted. Receiving a TV signal is another
story, but at least the device should be found.

It would be better to use a USB extension cable instead of a hub.

Is the sound OK if you play a DVD of if you watch a youtube video on
that machine? I think it is unlikely that the sound is only weird with
the TV device because sound and video are mixed in the DVB stream.

The inferior reception quality may be caused by the antenna location. If
you move the antenna something like 20 cm it could make a big
difference.

Nils

Re: Difficul;ties with trying to install and use tv adaptor

By Bret Busby at 05/16/2018 - 11:28

On 16/05/2018, Nils Kassube < ... at gmx dot net> wrote:
No - the firmware does work - it is just that the next sentence
applies, each time that the USB device is connected.

I note that that applies to the plugging in of the USB devicve, and,
not to the loaading of the television viewer (eg, MeTV, the only
television viewer application that I have found to consistently work
on both computers, on UbuntuMATE 16.04 .

When I close the application, and, later reload it, it takes a minute
or two, for the video from the television broadcast, to be displayed,
rather than the about two hours, if I have unplugged the USB device.

I have been using the USB port solely as an extension, in this case -
nothing else was plugged into any of its other sockets. The USB
extension cables that I have found for sale, are plug to plug,
requiring a socket to socket adaptor to join to another USB plug

I have just checked by viewing a bit of a stored movie, using
Kaffeine, on the i7 computer (the only one that would display video
from the device, in Kaffeine), and the sound was good and as expected.

I had thought that, after initially trying the supplied interior (to
the building) aerial, I would try it with connection to the main
household aerial, using a standard 75 ohm coaxial cable, which I have
been using for both computers. The two computers, with apparently
identical software, have different results of what they can receive
through the TV tuner device and the same aerial connection - this one
can receive pnly one network, the othe computer - the i7 computer, can
receive two networks, and, various other channels, which I assume to
be radio channels, and, if this device is not connectedinto the
particular line for the aerial, the rtelevision that would be
connected to it, can receive three of the networks, and, the
standalone (community) channel. One of the other networks (the
national (government) broadcaster network), we can only receive on one
or two days in each year, and, another television network, can be
reecived on only one received in the building - only one television.