TV Tuner (Hauppauge WinTV-NOVA-T USB2) is not being recognised

Bug #1694199 reported by Spud Link
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Tuner works on my laptop (Ubuntu 16.04) but not on my desktop Ubuntu 17.04 (uname -a: Linux machine 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux).
This link (https://linuxtv.org/wiki/index.php/DVB-T_USB_Devices) says:
 the tuner is supported since kernel 2.6.13,
 its Hardware (?) is dib3000mc and
 firmware is dvb-usb-nova-t-usb2-02.fw.
Tuner firmware was copied from laptop to desktop /lib/firmware
     -rw-r--r-- 1 root root 11023 Dec 10 22:39 /lib/firmware/dvb-usb-nova-t-usb2-02.fw
On Desktop (where the problem exists)
lsusb shows Bus 001 Device 004: ID 2040:9300 Hauppauge WinTV NOVA-T USB2 (cold) *
* Tuner shows light out when cold. If I boot into Windows light goes on. When I return to Linux light remains on and lsusb reports warm.
dmesg |grep dvb shows dvb_usb_dibusb_mc_common: Unknown symbol __symbol_get (err 0) ------- Whether tuner warm or cold
This page (https://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-USB2) states the following drivers are required:
 - dib3000-common.ko
 - dib3000mc.ko
 - dvb-usb.ko
 - dvb-usb-dibusb-common.ko
 - dvb-usb-nova-t-usb2.ko
lsmod|grep dvb shows:
 dvb_usb_dibusb_common 16384 0
 dvb_usb 24576 1 dvb_usb_dibusb_common
 dvb_core 126976 1 dvb_usb
 rc_core 28672 1 dvb_usb
lsmod|grep dib shows:
 dvb_usb_dibusb_common 16384 0
 dib3000mc 20480 0
 dibx000_common 16384 1 dib3000mc
 dvb_usb 24576 1 dvb_usb_dibusb_common
"dvb-usb-nova-t-usb2.ko" is located in /lib/modules/4.10.0-21-generic/kernel/drivers/media/usb/dvb-usb/dvb-usb-nova-t-usb2.ko.
However modprobe "dvb-usb-nova-t-usb2.ko" outputs
 "modprobe: FATAL: Module dvb-usb-nova-t-usb2.ko not found in directory /lib/modules/4.10.0-21-generic"
and modprobe "dvb-usb-nova-t-usb2" outputs
 "modprobe: ERROR: could not insert 'dvb_usb_nova_t_usb2': Unknown symbol in module, or unknown parameter (see dmesg)"
dmesg |grep dvb shows
[ 2.481132] dvb_usb_dibusb_mc_common: Unknown symbol __symbol_get (err 0) ------ upon boot
[ 646.407012] dvb_usb_dibusb_mc_common: Unknown symbol __symbol_get (err 0) ------ upon modprobe

With reference to https://wiki.ubuntu.com/Kernel/Firmware, using command "udevadm monitor --property"
there is nothing reported for a "SUB-SYSTEM Firmware" event and driver "dvb-usb-nova-t-usb2" is not mentioned.

The TV tuner is plugged into a USB2 only back plug on Desktop and PC is operating in BIOS (not UEFI) mode.

On my laptop where the card works, dmesg|grep dvb provides
 [ 186.878500] dvb-usb: found a 'Hauppauge WinTV-NOVA-T usb2' in cold state, will try to load a firmware
 [ 186.889946] dvb-usb: downloading firmware from file 'dvb-usb-nova-t-usb2-02.fw'
 [ 186.970174] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
 [ 186.970655] usbcore: registered new interface driver dvb_usb_nova_t_usb2
 [ 188.882272] dvb-usb: found a 'Hauppauge WinTV-NOVA-T usb2' in warm state.
 [ 188.882562] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
 [ 188.887424] dvb-usb: MAC address: XX:XX:XX:XX:XX:XX
 [ 188.947464] dvb-usb: schedule remote query interval to 100 msecs.
 [ 188.947467] dvb-usb: Hauppauge WinTV-NOVA-T usb2 successfully initialized and connected.
Also lsmod reports the presence of dvb-usb-nova-t-usb2

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-21-generic 4.10.0-21.23
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: spudlink 2011 F.... pulseaudio
 /dev/snd/controlC1: spudlink 2011 F.... pulseaudio
 /dev/snd/controlC0: spudlink 2011 F.... pulseaudio
CurrentDesktop: Unity:Unity7
Date: Mon May 29 13:29:17 2017
HibernationDevice: RESUME=UUID=468cfd2f-7272-4c4a-a9ca-a1f0d6a89587
InstallationDate: Installed on 2016-12-12 (167 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
 enp0s31f6 no wireless extensions.

 lo no wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 2040:9300 Hauppauge WinTV NOVA-T USB2 (cold)
 Bus 001 Device 003: ID 046d:08d7 Logitech, Inc. QuickCam Communicate STX
 Bus 001 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic root=UUID=ef5cd7f7-a4a5-47fa-9476-0a28fda40e86 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-21-generic N/A
 linux-backports-modules-4.10.0-21-generic N/A
 linux-firmware 1.164.1
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-04-16 (42 days ago)
dmi.bios.date: 03/14/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F6
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B150M-D3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd03/14/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB150M-D3H-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Spud Link (spudlink) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc3

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Spud Link (spudlink) wrote : Re: [Bug 1694199] Re: TV Tuner (Hauppauge WinTV-NOVA-T USB2) is not being recognised
Download full text (3.7 KiB)

Hi Joe and thanks for your email.

I had not used this TV tuner on my desktop computer with an earlier
version of OS.

I had used the tuner (as stated earlier) on my laptop which used Ubuntu
16.04 and that was successful. So tuner OK.

At this point I am reluctant to venture to use the upstream kernel (my
lack of skills etc).

However what I did do was install Ubuntu 16.04 (linux 4.4.0-78-generic)
as a VM on my desktop. I have included the pertinent "dmesg" output
below. To my way of thinking, processing got beyond the issue I raised
(Unknown symbols) and the TV Tuner was identified. There is another
issue present

"[ 101.325099] dvb-usb: could not restart the USB controller CPU."

but I would be thinking that it is related to the VM setup.
Perhaps,because the host OS is not doing what it should do for the USB
TV Tuner, the guest OS stumbles). Subsequent to testing on VM, I checked
the TV Tuner on the laptop and it is functioning A OK.

Would you consider that this is sufficient to indicate that there was a
kernel bug?

Cheers

Jack

DMESG OUTPUT

usb 1-1: new high-speed USB devic[ 101.325099]e number 2 using ehci-pci
[ 97.883850] usb 1-1: New USB device found, idVendor=2040, idProduct=9300
[ 97.883853] usb 1-1: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[ 99.808439] dvb-usb: found a 'Hauppauge WinTV-NOVA-T usb2' in cold
state, will try to load a firmware
[ 99.867024] dvb-usb: downloading firmware from file
'dvb-usb-nova-t-usb2-02.fw'
[ 101.325099] dvb-usb: could not restart the USB controller CPU.
[ 101.325115] dvb_usb_nova_t_usb2: probe of 1-1:1.0 failed with error -22
[ 101.325472] usbcore: registered new interface driver dvb_usb_nova_t_usb2
[ 101.330946] usb 1-1: USB disconnect, device number 2
[ 111.766837] usb 1-1: new high-speed USB device number 3 using ehci-pci
[ 111.917878] usb 1-1: New USB device found, idVendor=2040, idProduct=9301
[ 111.917888] usb 1-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 111.917894] usb 1-1: Product: SOHO-FX2
[ 111.917898] usb 1-1: Manufacturer: Hauppau⁧攀
[ 111.917902] usb 1-1: SerialNumber: 9301-00-FXXXXXXX
[ 111.922917] dvb-usb: found a 'Hauppauge WinTV-NOVA-T usb2' in warm state.
[ 111.925455] dvb-usb: will pass the complete MPEG2 transport stream to
the software demuxer.
[ 111.929056] DVB: registering new adapter (Hauppauge WinTV-NOVA-T usb2)
[ 111.943336] dvb-usb: MAC address: XX:XX:XX:XX:XX:XX
[ 111.957735] usb 1-1: DVB: registering adapter 0 frontend 0 (DiBcom
3000MC/P)...
[ 112.172674] input: IR-receiver inside an USB DVB receiver as
/devices/pci0000:00/0000:00:0b.0/usb1/1-1/input/input8
[ 112.173027] dvb-usb: schedule remote query interval to 100 msecs.
[ 112.173037] dvb-usb: Hauppauge WinTV-NOVA-T usb2 successfully
initialized and connected.
[ 114.269804] dvb-usb: recv bulk message failed: -110

On 31/05/17 01:11, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test ...

Read more...

Revision history for this message
Spud Link (spudlink) wrote :

Ran using 4.12.0-041200rc4 upstream kernel.

This time the TV USB card was identified. However a 'Call Trace'
appeared in 'dmesg' (attached). I wouldn't know if that is kernel
related, or not, so have not updated any bug status info. Let me know if
you require any further info

On 31/05/17 01:11, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.12 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc3
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.