On Friday 29 September 2006 22:27, you wrote: > Mark wrote: > > Incidentally, I checked the inf file from the windows driver that came on > > the CD - it definatly has the USB id in it for the card. Is there any way > > I can extract the firmware? Maybe they've updated it for this particular > > card. > > Nope -- the firmware is the same, I checked. No worries. I was mainly interested because there was a file called bluebird2.sys - thought it might have been a new thing. > > Scan seems to be working properly (except for the lockup) ... Can you > try to get a video stream using your favorite tool? ie: tzap + mplayer, > mplayer alone, kaffeine, xine, whatever? I can't find a way to generate a channels.conf, which is what I seem to need to use those tools; i'll ask one of my workmates for his in the morning, then i'll give it a shot. > > --- > > Try unloading the dvb-usb-cxusb and dvb-usb modules, then turn on debug > in the dvb-usb module... (see modinfo dvb-usb -- the debug settings are > or-able) and load up the dvb -usb-cxusb module again... Try to reproduce > the lockup above -- we should see better info in dmesg this time. > I loaded dvb-usb with debug=93 and dvb-usb-cxusb with debug=1 and got the following from scan: root@kulfi:/usr/share/doc/dvb-utils/examples/scan/dvb-t# scan ./au-canberra scanning ./au-canberra using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 205625000 1 3 3 3 1 1 0 initial transponder 177500000 1 2 0 3 1 2 0 initial transponder 191625000 1 3 0 3 1 1 0 initial transponder 219500000 1 3 1 3 1 1 0 initial transponder 543500000 1 2 0 3 1 2 0 >>> tune to: 205625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE and this in dmesg: [ 389.531961] check for warm 1660 932 [ 389.532024] something went very wrong, device was not found in current device list - let's see what comes next. [ 389.532096] check for cold fe9 d500 [ 389.532155] check for warm fe9 d501 [ 389.532209] something went very wrong, device was not found in current device list - let's see what comes next. [ 389.532278] check for cold fe9 db50 [ 389.532327] check for warm fe9 db51 [ 389.532381] check for cold fe9 db54 [ 389.532432] check for warm fe9 db55 [ 389.532487] check for cold fe9 db58 [ 389.532535] check for warm fe9 db59 [ 389.532582] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 2' in warm state. [ 389.532642] power control: 1 [ 389.533151] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 389.533438] DVB: registering new adapter (DViCO FusionHDTV DVB-T Dual Digital 2). [ 391.533598] dvb-usb: recv bulk message failed: -110 [ 391.534592] DVB: registering frontend 0 (Zarlink ZL10353 DVB-T)... [ 391.535907] input: IR-receiver inside an USB DVB receiver as /class/input/input9 [ 391.536102] dvb-usb: schedule remote query interval to 150 msecs. [ 391.536161] power control: 0 [ 391.536215] dvb-usb: DViCO FusionHDTV DVB-T Dual Digital 2 successfully initialized and connected. [ 391.536282] check for warm 1660 932 [ 391.536336] something went very wrong, device was not found in current device list - let's see what comes next. [ 391.536392] check for cold fe9 d500 [ 391.536440] check for warm fe9 d501 [ 391.536490] something went very wrong, device was not found in current device list - let's see what comes next. [ 391.536550] check for cold fe9 db50 [ 391.536598] check for warm fe9 db51 [ 391.536646] check for cold fe9 db54 [ 391.536695] check for warm fe9 db55 [ 391.536743] check for cold fe9 db58 [ 391.536790] check for warm fe9 db59 [ 391.536839] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 2' in warm state. [ 391.536898] power control: 1 [ 391.537380] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 391.537625] DVB: registering new adapter (DViCO FusionHDTV DVB-T Dual Digital 2). [ 391.541351] DVB: registering frontend 1 (Zarlink ZL10353 DVB-T)... [ 391.551605] input: IR-receiver inside an USB DVB receiver as /class/input/input10 [ 391.551738] dvb-usb: schedule remote query interval to 150 msecs. [ 391.551787] power control: 0 [ 391.551867] dvb-usb: DViCO FusionHDTV DVB-T Dual Digital 2 successfully initialized and connected. [ 391.551937] usbcore: registered new driver dvb_usb_cxusb [ 552.643852] power control: 1 [ 552.669544] pll addr: 61, freq: 205625000 f89e74a0 [ 552.669678] pll-buf: 61 5 aa b4 2 (and then the lockup occured) I tried it again a bit later and saw this from scan: mark@kulfi:~$ scan /usr/share/doc/dvb-utils/examples/scan/dvb-t/au-canberra scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/au-canberra using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 205625000 1 3 3 3 1 1 0 initial transponder 177500000 1 2 0 3 1 2 0 initial transponder 191625000 1 3 0 3 1 1 0 initial transponder 219500000 1 3 1 3 1 1 0 initial transponder 543500000 1 2 0 3 1 2 0 >>> tune to: 205625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE WARNING: >>> tuning failed!!! >>> tune to: 205625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE (tuning failed) WARNING: >>> tuning failed!!! >>> tune to: 177500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 0x0807 0x0807: pmt_pid 0x0160 Southern Cross Television -- SC10 Canberra (running) 0x0807 0x0827: pmt_pid 0x06ae Southern Cross Television -- SC10 HD (running) and messages quite similar to the previous to the last time in dmesg, except that I also saw messages like: submitting all URBs submitting URB no. 0 submitting URB no. 1 submitting URB no. 2 submitting URB no. 3 submitting URB no. 4 controlling pid parser start feeding start pid: 0x0011, feedtype: 1 setting pid (no): 17 0011 at index 1 'on' start pid: 0x0010, feedtype: 1 setting pid (no): 16 0011 at index 1 'on' start pid: 0x0160, feedtype: 1 setting pid (no): 352 0011 at index 1 'on' start pid: 0x06ae, feedtype: 1 setting pid (no): 1710 0011 at index 1 'on' stop pid: 0x0000, feedtype: 1 setting pid (no): 0 0011 at index 1 'off' stop pid: 0x06ae, feedtype: 1 setting pid (no): 1710 0011 at index 1 'off' stop pid: 0x0160, feedtype: 1 setting pid (no): 352 0011 at index 1 'off' stop pid: 0x0011, feedtype: 1 setting pid (no): 17 0011 at index 1 'off' (had to tap those in by hand due to the lockup but the numbers are all correct. may have missed a few as well but those are from the last second before the machine locked up.) > Next time it locks up..... does yanking out the usb plug unlock it? > (Expect an oops if you yank it while it's in use) > Might be a bit tricky. The card is actually a PCI card with a pci->usb bridge and two usb tuners on it, all surface mounted. > --- > > I think this locking up problem is not directly related to the new > hardware or driver -- DViCO says it is exactly identical to the hardware > used in the prior version. > > Thanks for testing, hopefully we can solve your lockup problem as well. > Thank you for your time and patience! > Cheers, > > Mike Mark _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
