Further to below I had been thinking that after a scan sometimes my system would crash but it seems the usb devices became disabled and therefore i could not use the mouse or keyboard. When I do the test remotely I can do further tests, I had not previously noted the correlation of this behaviour. After a reboot it is the first scan that causes disabling of the hub, EMI issue which I don't get on Ubuntu 16.04. Using either adapter0 or 1 creates this error. Closing the terminal and doing a new scan on either adapter successfully completes without any further errors. On Sat, 14 Aug 2021 at 11:10, Andrew Goff <goffa72@xxxxxxxxx> wrote: > > Hi Sean, > > I'll have a go at using bisection. > > Attached is the output of dmesg, when I started a scan of adapter1 the > following occurred - > > usb usb1-port1: disabled by hub (EMI?), re-enabling... > > and when I closed the terminal window the USB ports re-enabled. > > > > On Fri, 13 Aug 2021 at 18:54, Sean Young <sean@xxxxxxxx> wrote: > > > > Hi Andrew, > > > > On Fri, Aug 13, 2021 at 10:21:04AM +1000, Andrew Goff wrote: > > > Hi, I hope this is the right place for posting this. > > > > > > I have the above TV tuner / capture device which has been working well > > > in Ubuntu 16.04. I've decided to update the OS to Ubuntu 20.04 with a > > > fresh install on a different disk and haven't been able to get this > > > device working. > > > > > > Ubuntu 21.04, 18.04 have also been tested with the same results. On a > > > fresh install of 16.04 this device works well. > > > > > > It seems something has changed between 16.04 (kernel 4.15.0-142) and > > > 18.04 (kernel 5.4.0-42). > > > > > > In /etc/modprobe.d/dvb.conf > > > # Sony Play TV > > > options dvb-usb-dib0700 adapter_nr=5,6 force_lna_activation=1 > > > > > > This has been tested with different variations of the above without success. > > > > > > When using w_scan with a file manager open I've noticed if scanning > > > adapter6 I could see the folder named adapter5 disappear. I then > > > opened up the adapter6 folder and two of the four files had > > > disappeared. When the scan finished the files/folder reappeared, > > > however the device then became unusable. > > > > > > 'modinfo dvb_usb_dib0700 | grep depends' yields the following > > > > > > For Ubuntu 18.04 > > > depends: > > > dib7000m,dib9000,dibx000_common,dvb-usb,dib0090,dib0070,dib3000mc,rc-core > > > > > > For Ubuntu 16.04 > > > depends: dib7000m,dvb-usb,dib0090,dib0070,dib3000mc,rc-core > > > > > > So something has changed in the driver? > > > > > > Please let me know if any further information is required to help fix this. > > > > This does sound like a regression, but we'll have to figure out what > > caused this. First of all, is there any output in dmesg when the device > > does not work? > > > > Secondly, the best way to track this down is using bisection. Is this > > something you could do? This would be enormously helpful. > > > > https://www.kernel.org/doc/html/latest/admin-guide/bug-bisect.html > > > > Thanks, > > > > Sean
