On Tuesday 20 June 2006 18:32, Peter Smith wrote: > I have just taken delivery of a new Hauppauge WinTV-Nova-T-USB2 > understanding that this was fully supported by linux. > > I have downloaded the firmware file dvb-usb-nova-t-usb2-01.fw and it is > found on plugging in the card. However no frontend device is created > > Output from message file: > > Jun 20 18:14:39 pingu kernel: usb 1-10: new high speed USB device using > ehci_hcd and address 16 > Jun 20 18:14:41 pingu kernel: usb 1-10: new high speed USB device using > ehci_hcd and address 17 > Jun 20 18:14:41 pingu kernel: usb 1-10: new device found, idVendor=2040, > idProduct=9300 > Jun 20 18:14:41 pingu kernel: usb 1-10: new device strings: Mfr=1, > Product=2, SerialNumber=3 > Jun 20 18:14:41 pingu kernel: usb 1-10: Product: SOHO-FX2 > Jun 20 18:14:41 pingu kernel: usb 1-10: Manufacturer: Hauppau?? > Jun 20 18:14:41 pingu kernel: usb 1-10: SerialNumber: 9301-00-F00843DB > Jun 20 18:14:41 pingu kernel: usb 1-10: configuration #1 chosen from 1 > choice > Jun 20 18:14:41 pingu kernel: dvb-usb: found a 'Hauppauge WinTV-NOVA-T > usb2' in cold state, will try to load a firmware > Jun 20 18:14:41 pingu kernel: dvb-usb: downloading firmware from file > 'dvb-usb-nova-t-usb2-01.fw' Peter, I get something similar when starting up from 'cold'. I then unplug the usb connector from the Hauppage box and reconnect after a few seconds, and consequently get a syslog that looks like this: Jun 20 00:58:52 house kernel: usb 2-1: new high speed USB device using ehci_hcd and address 8 Jun 20 00:58:52 house kernel: usb 2-1: configuration #1 chosen from 1 choice Jun 20 00:58:53 house kernel: dvb-usb: found a 'Hauppauge WinTV-NOVA-T usb2' in cold state, will try to load a firmware Jun 20 00:58:53 house kernel: dvb-usb: downloading firmware from file 'dvb-usb-nova-t-usb2-01.fw' Jun 20 00:58:53 house /etc/hotplug.d/firmware/50-firmware.hotplug[15830]: cat: write error: No such device Jun 20 00:58:53 house /etc/hotplug.d/firmware/50-firmware.hotplug[15830]: /etc/hotplug.d/firmware/50-firmware.hotplug: line 40: /sys//class/firmware/2-1/loading: No such file or directory Jun 20 00:58:53 house kernel: usbcore: registered new driver dvb_usb_nova_t_usb2 Jun 20 00:58:53 house kernel: usb 2-1: USB disconnect, address 8 Jun 20 00:58:53 house kernel: dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. Jun 20 00:58:55 house kernel: usb 2-1: new high speed USB device using ehci_hcd and address 9 Jun 20 00:58:55 house kernel: usb 2-1: configuration #1 chosen from 1 choice Jun 20 00:58:55 house kernel: dvb-usb: found a 'Hauppauge WinTV-NOVA-T usb2' in warm state. Jun 20 00:58:55 house kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Jun 20 00:58:55 house kernel: DVB: registering new adapter (Hauppauge WinTV-NOVA-T usb2). Jun 20 00:58:55 house kernel: dvb-usb: MAC address: 00:0d:fe:07:4a:ab Jun 20 00:58:55 house kernel: dib3000: Found a DiBcom 3000P. Jun 20 00:58:55 house kernel: DVB: registering frontend 0 (DiBcom 3000P/M-C DVB-T)... Jun 20 00:58:55 house kernel: input: IR-receiver inside an USB DVB receiver as /class/input/input3 Jun 20 00:58:55 house kernel: dvb-usb: schedule remote query interval to 100 msecs. Jun 20 00:58:55 house kernel: dvb-usb: Hauppauge WinTV-NOVA-T usb2 successfully initialized and connected. Although it reported not finding the firmware, this was not the problem. As the device comes back 'warm', it would appear that downloading the firmware does actually happen, but that the hotplug process stops at that point??? I'm no expert on this, but you may find that a quick disconnect gets you working. (My details: SuSE 9.3 on Athlon 64/PCIe but with 2.6.16.18 kernel and Mercurial drivers downloaded 5 Jun 06) John _______________________________________________ linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
