Looking in /sys/module/dvb_usb_dib0700/parameters/force_lna_activation it says 0! Despite there being a 'options dvb....' line in my modules.conf. I've tried serveral things but still can't get it to say 1! So in the end I just rmmod the dvb_usb_dib0700 module then did a modprobe on it with force_lna on the command line and that worked. I need to go back and check why its not picking up the modules.conf on boot. I then tried with the as-supplied SandyHeath transmitter file and that failed as it had done before. I then used the list which you supplied - and some of them worked! I can now watch a few channels of TV! I'll experiment later with altering the SPURCHECK & recompiling. And invest in a amp! Thanks very much for your help, Matt Graham Tavener writes: > Matt, > I found the reason why the force_lna_activation is not being applied. > Firstly I was still using 2.6.19.1 when I thought I was on 2.6.20-rc5 (doh), > a quick change to grub sorted that, but my signals were also very low and > the modprobe.conf made no difference as the module is not dynamically loaded > and is not shown when you do a lsmod. Apparently when the support is built > into the kernel and it no longer loads a module the setting is not applied > using modprobe.conf and you should pass the parameters to the kernel at > bootup. > So in my case I had to edit /boot/grub/menu.lst and add add > dvb_usb_dib0700.force_lna_activation=1 > to the options so it then became > kernel /boot/vmlinuz-2.6.20-rc5 ro root=LABEL=/ rhgb > dvb_usb_dib0700.force_lna_activation=1 > Checking the signal level in mythtv it has jumped up and the file > /sys/module/dvb_usb_dib0700/parameters/force_lna_activation now contains 1 > rather than 0 > Also handy to know that if there is a file under one of the modules it > implies the parameter can be set. > In my case I now have a better signal, but it refuses to lock using > 2.6.20-rc5 > > It might be related to the errors in /var/log/messages > > DVB: registering frontend 1 (DiBcom 3000MC/P)... > DVB: unable to find symbol mt2060_attach() > dvb-usb: Hauppauge Nova-T-500 Dual DVB-T successfully initialized > and connected > > I made another change to 2.6.19.1 which may have helped. I edited > /usr/src/linux-2.6.19.1/drivers/media/dvb/frontend/mt2060_priv.h and enabled > MT2060_SPURCHECK before compiling the kernel. It has been reported that > this *can* help some people with poor reception, but has not been proven. > > I'm going back to 2.6.19.1 as it tuned in ok, but suffered the occasional > lockup. > > Graham > > ----- Original Message ----- > From: <matt.nottingham@xxxxxxxxx> > To: "Graham Tavener" <graham.tavener@xxxxxxx> > Cc: <matt.nottingham@xxxxxxxxx>; <linux-dvb@xxxxxxxxxxx> > Sent: Sunday, January 28, 2007 9:45 PM > Subject: Re: Problem getting channel list with nova-t-500 > > > > > > Graham, > > > > I think I have! As I mentioned originally, I do have a line like this > > in my modules.conf, but there is nothing mentioned about this flag > > being set in dmesg on boot up. > > > > Thanks, > > > > Matt > > > > Graham Tavener writes: > > > Matt, have you enabled the amplifier? > > > Add the following line to the end of /etc/modprobe.conf > > > > > > options dvb-usb-dib0700 force_lna_activation=1 > > > > > > It forces the Low Noise Amplifier on and this made the difference > > > between > > > <40% to 70% signal for me. > > > > > > I'm using Fedora Core 6 2.6.20-rc5 on a AM2 dual core 3800 and it has > > > been > > > pretty reliable, but I've had a couple of complete hangs which seem to > > > be > > > dvb driver related. > > > > > > Graham > > > > > > ----- Original Message ----- > > > From: <matt.nottingham@xxxxxxxxx> > > > To: <linux-dvb@xxxxxxxxxxx> > > > Sent: Sunday, January 28, 2007 6:10 PM > > > Subject: Problem getting channel list with nova-t-500 > > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > I have a Debian (unstable) AMD64 (with 4gig RAM) and a nova-t-500 > > > > card. I'm currently running linux 2.6.20-rc6. If I try 'scan' I get > > > > the following: > > > > > > > > # scan -vvv > > > > /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-SandyHeath > > > > scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-SandyHeath > > > > using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' > > > > initial transponder 641833334 0 2 9 3 0 0 0 > > > > >>> tune to: > > > > 641833334:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE > > > > >>> tuning status == 0x1a > > > > WARNING: filter timeout pid 0x0011 > > > > WARNING: filter timeout pid 0x0000 > > > > WARNING: filter timeout pid 0x0010 > > > > dumping lists (0 services) > > > > Done. > > > > > > > > If I use kaffeine (using Sandyheath as the default location) I see: > > > > > > > > Using DVB device 0:0 "DiBcom 3000MC/P" > > > > tuning DVB-T to 641833000 Hz > > > > inv:2 bw:0 fecH:2 fecL:9 mod:3 tm:0 gi:0 hier:0 > > > > . LOCKED. > > > > Transponders: 1/1 > > > > > > > > Invalid section length or timeout: pid=17 > > > > > > > > > > > > Invalid section length or timeout: pid=0 > > > > > > > > Frontend closed > > > > > > > > So it certainly seems to find the signal (as it locks) but then gets a > > > > bit grumpy! > > > > > > > > I've tried 2.6.19.2, setting mem=3G (having 4gig of ram has upset > > > > certain cards (ethernet, USB,....) in the past), using the latest > > > > drivers from the SCM system, having > > > > 'options dvb-usb-dib0700 force_lna_activation=1' > > > > in my /etc/modules.conf - but all give the above results. > > > > > > > > I don't have a TV with me nor do I have MS-Windows to try the card out > > > > there - so is it just a signal (ie. lack there-of!) problem? Hopefully > > > > next weekend I'll have my USRP (http://gnuradio.org/trac/wiki) with me > > > > and be able to see what strength signals I do have. > > > > > > > > Any thoughts or hints or suggestions would be welcome! > > > > > > > > Thanks > > > > > > > > Matt Nottingham > > > > > > > > Just for completeness, if I do 'dmesg | grep -i dvb' I get: > > > > > > > > > > > > dvb_usb_dib0700 2-1:1.0: usb_probe_interface > > > > dvb_usb_dib0700 2-1:1.0: usb_probe_interface - got id > > > > dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will > > > > try > > > > to load a firmware > > > > dvb-usb: downloading firmware from file 'dvb-usb-dib0700-01.fw' > > > > dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. > > > > **WARNING** I2C adapter driver [Hauppauge Nova-T 500 Dual DVB-T] > > > > forgot to > > > > specify physical device; fix it! > > > > dvb-usb: will pass the complete MPEG2 transport stream to the software > > > > demuxer. > > > > DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T). > > > > DVB: registering frontend 0 (DiBcom 3000MC/P)... > > > > dvb-usb: will pass the complete MPEG2 transport stream to the software > > > > demuxer. > > > > DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T). > > > > DVB: registering frontend 1 (DiBcom 3000MC/P)... > > > > dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and > > > > connected. > > > > usbcore: registered new interface driver dvb_usb_dib0700 > > > > > > > > _______________________________________________ > > > > linux-dvb mailing list > > > > linux-dvb@xxxxxxxxxxx > > > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > > > > > > > > > > -------------------------------------------------------------------------------- > > > I am using the free version of SPAMfighter for private users. > > > It has removed 142 spam emails to date. > > > Paying users do not have this message in their emails. > > > Try SPAMfighter for free now! > > > > > > > > > > -------------------------------------------------------------------------------- > I am using the free version of SPAMfighter for private users. > It has removed 142 spam emails to date. > Paying users do not have this message in their emails. > Try SPAMfighter for free now! > > _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
