Hi, Emmanuel Emmanuel Quémener schrieb: > Hartmut Hackmann a écrit : > >> Hi, Emmanuel >> >> Emmanuel Quémener schrieb: >> >>> Hartmut Hackmann a écrit : >>> >>> >>>> Hi, Emmanuel >>>> >>>> Emmanuel Quémener schrieb: >>>> >>>> >>>>> Emmanuel Quémener a écrit : >>>>> >>>>> >>>>> >>>>>> Hartmut Hackmann a écrit : >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> I noticed 2 things: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> tuner 2-004b: AGC2 gain is: 10 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> This means maximum gain. With active LNA, i would expect lower >>>>>>> values... >>>>>>> second: The reason for the tumbling channel decoder might be a >>>>>>> not closed AGC loop. >>>>>>> But if DVB-T works after analog was on once with tuner_config 3, >>>>>>> this leads me to this: >>>>>>> Analog - digital mode switch might be GPIO22 like it is with some >>>>>>> ADS / Lifeview cards. Did you ever try card=87? >>>>>>> But this would cause trouble with the LNA since in the Philips >>>>>>> solutions, GPIO22 always is involved. >>>>>>> Are you sure the board has a LNA? In the philips designs, it sits >>>>>>> under the tuner shield and looks like a SMD voltage regulator. >>>>>>> If there is a LNA, the board seems to have a mode switch we haven't >>>>>>> seen yet. Except - did you try to invert tda1004x GPIO1, so >>>>>>> .gpio_config = TDA10046_GP00_I, >>>>>>> instead >>>>>>> .gpio_config = TDA10046_GP01_I, >>>>>>> >>>>>>> Maybe this helps >>>>>>> Hartmut >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> I will do it this evening. >>>>>> >>>>>> So, if I sum up, there are 2 tests to perform : >>>>>> - #1 : try to change board from 109 to 87 : in this case, must I get an >>>>>> clean archive or do I keep some changes to tuner_config reference ? >>>>>> - #2 : try to change GPIO config reference : in this case, same as >>>>>> before : clean archive or modified one on tuner_config reference ? >>>>>> >>>>>> Bye >>>>>> >>>>>> EQ >>>>>> >>>>>> Is it necessary to keep tuner_config=3 to definitions or must I get a >>>>>> not modified archive to try to change my board from 109 to 87 and change >>>>>> only GPIO config >>>>>> >>>>>> >>>>>> >>>>> Sorry, but I didn't take the time in the past 2 weeks to experiment the >>>>> tests you'd like. >>>>> >>>>> I try on last sunday to compile a new kernel (the last one : 2.6.20) >>>>> with a blank repository on v4l-dvb archive and make the changes on it : >>>>> it sucks !!! >>>>> >>>>> - the new kernel 2.6.20 does not recognized my board >>>>> - when I try to compile new repository and install the modules, the >>>>> saa7134 module doesn't want to load >>>>> - when I search in files saa7134-dvb.c and saa-7134-cards.c the >>>>> references to tuner_config, It was impossible to find them >>>>> >>>>> So, my questions : >>>>> - how is it possible for me to compile last kernel 2.6.20 with third >>>>> party v4l-dvb archives ? >>>>> - when can I get this 2.6.20 working archives ? >>>>> - what modifications can I perform to test and make working my board >>>>> (1043:4871 reference)... >>>>> >>>>> >>>>> >>>> Please use my personal repository for the tests. It is at: >>>> http://linuxtv.org/hg/~hhackmann/v4l-dvb >>>> It does compile on kernel 2.6.20, i have it running here. >>>> Just to be sure: >>>> - if you compiled for another kernel before, you need to >>>> delete the file v4l/.version >>>> - don't try to merge the files into the kernel, compile them separately >>>> with make, make install (for the install, you need to be root >>>> - never mix modules with older versions. >>>> - afik, you need to enable the v4l and dvb stuff in the kernel tree. >>>> >>>> Looks like you missed a mail from me, i will just paste it here: >>>> >>>> I had a look at the eeprom dump again: The card should be a copy of the Tiger-S >>>> reference design without radio. So please try this: >>>> Get a copy of my personal repository, compile and install. Then do: >>>> modprobe saa7134 card=109 secam=l >>>> modprobe saa7134-alsa >>>> modprobe saa7134-dvb >>>> This should do it as long as there are not tricks with the windows driver. >>>> >>>> You sould no longer need to load the saa7134-alsa and saa7134-dvb modules >>>> manually. >>>> >>>> Good luck >>>> Hartmut >>>> >>>> >>>> _______________________________________________ >>>> linux-dvb mailing list >>>> linux-dvb@xxxxxxxxxxx >>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >>>> >>>> >>>> >>> I've just compiled the modules on a fresh 2.6.20.1 kernel and the output >>> is badly following : >>> >>> saa7134: disagrees about version of symbol videobuf_streamoff >>> saa7134: Unknown symbol videobuf_streamoff >>> saa7134: disagrees about version of symbol videobuf_poll_stream >>> saa7134: Unknown symbol videobuf_poll_stream >>> saa7134: disagrees about version of symbol videobuf_read_stop >>> saa7134: Unknown symbol videobuf_read_stop >>> saa7134: disagrees about version of symbol videobuf_dma_free >>> saa7134: Unknown symbol videobuf_dma_free >>> saa7134: disagrees about version of symbol videobuf_reqbufs >>> saa7134: Unknown symbol videobuf_reqbufs >>> saa7134: Unknown symbol ir_codes_encore_enltv >>> saa7134: disagrees about version of symbol videobuf_waiton >>> saa7134: Unknown symbol videobuf_waiton >>> saa7134: disagrees about version of symbol videobuf_dqbuf >>> saa7134: Unknown symbol videobuf_dqbuf >>> saa7134: disagrees about version of symbol videobuf_queue_init >>> saa7134: Unknown symbol videobuf_queue_init >>> saa7134: Unknown symbol ir_rc5_timer_keyup >>> saa7134: Unknown symbol ir_codes_asus_pc39 >>> saa7134: Unknown symbol ir_rc5_timer_end >>> saa7134: disagrees about version of symbol videobuf_dma_unmap >>> saa7134: Unknown symbol videobuf_dma_unmap >>> saa7134: disagrees about version of symbol videobuf_read_stream >>> saa7134: Unknown symbol videobuf_read_stream >>> saa7134: disagrees about version of symbol videobuf_querybuf >>> saa7134: Unknown symbol videobuf_querybuf >>> saa7134: disagrees about version of symbol video_unregister_device >>> saa7134: Unknown symbol video_unregister_device >>> saa7134: disagrees about version of symbol videobuf_qbuf >>> saa7134: Unknown symbol videobuf_qbuf >>> saa7134: disagrees about version of symbol video_device_alloc >>> saa7134: Unknown symbol video_device_alloc >>> saa7134: disagrees about version of symbol videobuf_read_one >>> saa7134: Unknown symbol videobuf_read_one >>> saa7134: disagrees about version of symbol video_register_device >>> saa7134: Unknown symbol video_register_device >>> saa7134: disagrees about version of symbol videobuf_iolock >>> saa7134: Unknown symbol videobuf_iolock >>> saa7134: disagrees about version of symbol videobuf_streamon >>> saa7134: Unknown symbol videobuf_streamon >>> saa7134: disagrees about version of symbol video_device_release >>> saa7134: Unknown symbol video_device_release >>> saa7134: disagrees about version of symbol videobuf_mmap_mapper >>> saa7134: Unknown symbol videobuf_mmap_mapper >>> saa7134: disagrees about version of symbol videobuf_mmap_free >>> saa7134: Unknown symbol videobuf_mmap_free >>> >>> I seem not to have a good compiled. Where am I wrong ? >>> >>> >> This occurs when you mix module versions. I guess you forgot to remove >> all video related modules before you tried to load the new ones. >> after you did "make install", you should either do: >> "make rmmod" or reboot the system before you load the new modules. >> >> >> Good luck >> Hartmut >> >> > - I've purged my repository : rm ~/v4l-dvb > - I've downloaded a new one : hg clone > http://linuxtv.org/hg/~hhackmann/v4l-dvb > - I've removed the old modules : cd ~/v4l-dvb ; make rmmod ; make rminstall > - I've compiled and installed the new modules : make -j 2 all ; make install > - I've rebooted : on boot the same wrong messages appears > > When I've tried manually to unload and load the modules with v4l-dvb > tools (make rmmod ; make insmod), the module saa7134 loaded fine (but > with the wrong parameters). > Hmm, can you please check this: After you did "make install" could it be that you have modules twice in your /lib/modules/xxx tree? This would explain the version conflict when the modules get autoloaded. Does depmod give any "strange" message? > When I tried to manually remove the modules (rmmod saa7134_alsa > saa7134_dvb and rmmod saa7134), my kernel crashed (I must boot my > machine with noapic and nolapic options) : impossible for me to save the > crashed messages... > On my system, i can load and unload the modules as i like. But: It is a known issue that streaming must be shut down before you can unload the modules. Could it be that you have some service running in the background and you have the "force module remove" option set in the kernel config? When exactly does it crash, when you remve the modules step by step? > When I remove the following modules tuner compat_ioctl32 videodev > ir_kbd_i2c v4l1_compat v4l2_common video_buf ir_common before installing > saa7134 with options card=109 secam=l, the module loads fine, but I > already got the same problem of instability connection. I correct it as > before with launching on boot time a fake scantv in order to correct > gain on analogic tuner. > > I don't know what I can do to help you debugging the kernel crash on > unload process... > When we start debugging this, you should set the options debug=1 for the modules tuner and tda827x. Then the drivers report what they try to do with the gain. Best regards Hartmut _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
