[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Difficul;ties with trying to install and use tv adaptor

Bret Busby wrote:
> On 15/05/2018, Bret Busby <bret.busby at gmail.com> wrote:
> > On 15/05/2018, Bret Busby <bret.busby at gmail.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.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 at 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.