On Mon, 2007-07-30 at 22:55 +0200, Janne Grunau wrote: > You need a cold (powerless) reboot to get the new firmware loaded. > You > don't have to worry about the firmware file. The exact filename is > hardcoded in the source. > You can check if you look in your kernel messages for following line: > dvb-usb: downloading firmware from file 'dvb-usb-dib0700-03-pre1.fw' [ 30.965645] dib0700: loaded with support for 5 different device-types [ 30.965925] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware [ 31.008899] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-03-pre1.fw' [ 31.015377] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 22 [ 31.016189] PCI: Setting latency timer of device 0000:00:1b.0 to 64 [ 31.206081] dib0700: firmware started successfully. [ 31.265279] NET: Registered protocol family 17 [ 31.711176] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. [ 31.711222] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 31.711325] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [ 31.831535] DVB: registering frontend 0 (DiBcom 3000MC/P)... [ 31.854890] MT2060: successfully identified (IF1 = 1220) [ 32.388673] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 32.388853] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [ 32.394293] DVB: registering frontend 1 (DiBcom 3000MC/P)... [ 32.398790] MT2060: successfully identified (IF1 = 1220) [ 32.959607] input: IR-receiver inside an USB DVB receiver as /class/input/input4 [ 32.959633] dvb-usb: schedule remote query interval to 150 msecs. [ 32.959637] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected. [ 32.959657] usbcore: registered new interface driver dvb_usb_dib0700 Yes ! Nico _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
