Difficul;ties with trying to install and use tv adaptor

classic Classic list List threaded Threaded
25 messages Options
12
Reply | Threaded
Open this post in threaded view
|

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

Bret Busby-2
On 15/05/2018, Bret Busby <[hidden email]> wrote:

> On 15/05/2018, Bret Busby <[hidden email]> wrote:
>> On 13/05/2018, Grizzly via ubuntu-users <[hidden email]>
>> wrote:
>>> 13 May 2018  at 15:46, Bret Busby wrote:
>>> Re: Difficul;ties with trying to in (at least in part)
>>>
>>>>On 13/05/2018, Grizzly via ubuntu-users <[hidden email]>
>>>> wrote:
>>>>
>>>>
>>>><snip>
>>>>
>>>>>>> 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 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.
>>>>>
>>>>> I would give Kaffiene a try, it worked a treat on my old DBV-TV
>>>>> addaptor
>>>>>
>>>>
>>>>Yes, I have tried Kaffeine, but I think that the system needs a driver
>>>>for the device.
>>>
>>> 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
>>>
>>> https://www.avermedia.com/tv_more/download/avertv_volar_hd_nano
>>>
>>> http://storage.avermedia.com/web_release_www/A867R/A867R_drv_v1.0.29_20160707.ta
>>> r.bz2
>>>
>>> I do note that all the info I can find dates back 6 to 8 years
>>>
>>> --
>>> ubuntu-users mailing list
>>> [hidden email]
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>>>
>>
>> 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:~$
>> "
>>
>>
>> --
>>
>> Bret Busby
>> Armadale
>> West Australia
>>
>> ..............
>>
>> "So once you do know what the question actually is,
>>  you'll know what the answer means."
>> - Deep Thought,
>>  Chapter 28 of Book 1 of
>>  "The Hitchhiker's Guide to the Galaxy:
>>  A Trilogy In Four Parts",
>>  written by Douglas Adams,
>>  published by Pan Books, 1992
>>
>> ....................................................
>>
>
>
> 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.
>
> --
>
> Bret Busby
> Armadale
> West Australia
>
> ..............
>
> "So once you do know what the question actually is,
>  you'll know what the answer means."
> - Deep Thought,
>  Chapter 28 of Book 1 of
>  "The Hitchhiker's Guide to the Galaxy:
>  A Trilogy In Four Parts",
>  written by Douglas Adams,
>  published by Pan Books, 1992
>
> ....................................................
>

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.


--

Bret Busby
Armadale
West Australia

..............

"So once you do know what the question actually is,
 you'll know what the answer means."
- Deep Thought,
 Chapter 28 of Book 1 of
 "The Hitchhiker's Guide to the Galaxy:
 A Trilogy In Four Parts",
 written by Douglas Adams,
 published by Pan Books, 1992

....................................................

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

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

Nils Kassube-2
Bret Busby wrote:
> On 15/05/2018, Bret Busby <[hidden email]> wrote:
> > On 15/05/2018, Bret Busby <[hidden email]> 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.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

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

> >> bret@bret-Aspire-V3-772-UbuntuMATE:~$ ls /lib/firmware
[...]
> >> ar3k                      dvb-usb-af9035-02.fw

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

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

Did you replug the device before it worked?

> 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.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

Unfortunately there is no reason mentioned why the probe failed.

> [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

> [2245824.457593] sd 3:0:0:0: [sdb] tag#0 FAILED Result:
> hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

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.

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

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

> So, after a while, the end of dmesg becomes

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

> MeTV still returns
> "There are no DVB devices available".
>
> and Kaffeine shows
>
> "Device not connected"

Of course that is expected if the dvb_usb_af9035 probe failed.

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

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

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

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


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

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

Bret Busby-2
On 16/05/2018, Nils Kassube <[hidden email]> wrote:
> Bret Busby wrote:

<snip>

>> So, a couple of hours later, it started working again.
>
> But did you replug the device before it started to work?
>

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

>> It appears to take a couple of hours, for the software to detect the
>> device and the signals.
>
> 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.
>

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.

> 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.
>

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.




--

Bret Busby
Armadale
West Australia

..............

"So once you do know what the question actually is,
 you'll know what the answer means."
- Deep Thought,
 Chapter 28 of Book 1 of
 "The Hitchhiker's Guide to the Galaxy:
 A Trilogy In Four Parts",
 written by Douglas Adams,
 published by Pan Books, 1992

....................................................

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

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

Nils Kassube-2
Bret Busby wrote:
> On 16/05/2018, Nils Kassube <[hidden email]> wrote:
> > Bret Busby wrote:
> >> So, a couple of hours later, it started working again.
> >
> > But did you replug the device before it started to work?
>
> Yes, I had done that, a number of times, on each computer.

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

> >> It appears to take a couple of hours, for the software to detect
> >> the
> >> device and the signals.
> >
> > 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.
>
> 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.

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.

> 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.

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

> 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.

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.

> > 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.
> 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.

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


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

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

Bret Busby-2
On 16/05/2018, Nils Kassube <[hidden email]> wrote:

> Bret Busby wrote:
>> On 16/05/2018, Nils Kassube <[hidden email]> wrote:
>> > Bret Busby wrote:
>> >> So, a couple of hours later, it started working again.
>> >
>> > But did you replug the device before it started to work?
>>
>> Yes, I had done that, a number of times, on each computer.
>
> OK, then maybe the firmware load works only sometimes, which is of
> course strange.
>

No - the firmware does work - it is just that the next sentence
applies, each time that the USB device is connected.

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

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.

>> > 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.
>>
>> 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.
>
> 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.
>
>> 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.
>
> It would be better to use a USB extension cable instead of a hub.
>

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

>> 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.
>
> 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.
>

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.

>> > 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.
>> 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.
>
> 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.
>

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.


--
Bret Busby
Armadale
West Australia
..............

"So once you do know what the question actually is,
 you'll know what the answer means."
- Deep Thought,
 Chapter 28 of Book 1 of
 "The Hitchhiker's Guide to the Galaxy:
 A Trilogy In Four Parts",
 written by Douglas Adams,
 published by Pan Books, 1992

....................................................

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
12