Thanks, I already had tried to load it manually (you didn't think I was rebooting every time did you?) using the same syntax I mentioned that I put in the modules file from my first post. This of course did not work because I had the worng syntax, well not wrong, I just did not have the second tuner number listed (only used tuner=50 not tuner=-1,50).
After you gave me the correct syntax I tried it yesterday afternoon both manually and at boot and it did not work at boot time but it did work manually. I tracked it down to what I beleive is a bug in the init scripts my distro has provided (they have a pseudo non standard init scheme using the standard SysV scheme with a set of custom init scripts for the hardware). I fixed my problem by writing my own init script (put in init.d and linked in the various run levels) that manually loads it with the proper tuner options on the command line. This works fine for me and I have submitted the "bug" to the distro maintainer. Thanks again for the assistance. Andre -------------- Original message ---------------------- From: Hans Verkuil <[EMAIL PROTECTED]> > > > On Saturday 09 September 2006 13:07, [EMAIL PROTECTED] wrote: > > Hans, > > Thanks, I do not know if I am making progress or not but the card > > still does not work. I get the same block in dmesg as before. > > There is something weird with your ivtv options. Try loading it > manually: > > rmmod ivtv (to remove any old ivtv driver) > modprobe ivtv tuner=-1,50 > > See if that helps. > > > > > Scanning for channels does nothing now (before it at least found the > > channels). I have seen on the net that this particular card uses a > > different tuner than #50 (43 I think) so I will try later with some > > other values. > > No, it's tuner 50. Not 43 (that's an NTSC tuner). > > Hans > > > > > If there is any other information you could use from ivtvctl please > > let me know. > > > > Andre > > > > > > > > -------------- Original message ---------------------- > > From: Hans Verkuil <[EMAIL PROTECTED]> > > > > > On Saturday 09 September 2006 02:59, [EMAIL PROTECTED] wrote: > > > > Hans, > > > > I guess my real question is this: > > > > If you have more than one pvr 150 that have different tuners what > > > > is the proper way to configure the second to use a different > > > > tuner than the first (maybe an MCE and a non MCE)? > > > > > > tuner=-1,50 > > > > > > where -1 = autodetect. So the first card is set to autodetect, the > > > second is forced to tuner 50. > > > > > > Hans > > > > > > > Let us assume for the sake of argument there is no autodetect at > > > > all. > > > > > > > > There should be a way to do this but I have not been able to find > > > > any documentation on the ivtvdriver website, in any of the > > > > mailing lists, or any other place on the web. > > > > > > > > Thanks for the suggestion, please see comments below: > > > > > > > > -------------- Original message ---------------------- > > > > From: Hans Verkuil <[EMAIL PROTECTED]> > > > > > > > > > Selec > > > > > > > > > > On Friday 08 September 2006 20:52, [EMAIL PROTECTED] > wrote: > > > > > > I have recently installed a second pvr-150 in my myth system > > > > > > and the second tuner will NOT autodetect. I am running Debian > > > > > > Sarge 2.6.17 kernel with ivtv 0.7.0. I have upgraded and > > > > > > recompiled everything including the firmware per your > > > > > > website. In addition to not autodetecting it will not let me > > > > > > set the tuner via an options clause in the modprobe, > > > > > > providing the option in the ivtv file in modprobe.d, or the > > > > > > two distro specific config files. > > > > > > > > > > > > The second tuner only gives me a black screen with colored > > > > > > diagnal streaks. It appears to change channels properly and > > > > > > the audio comes out as white noise/static. > > > > > > > > > > > > Placing a line in modules: > > > > > > ivtv tuner=50 > > > > > > or > > > > > > ivtv options tuner=50 > > > > > > > > > > That should be: > > > > > > > > > > options ivtv tuner=50 > > > > > > > > > > This tuner is autodetected in the upcoming 2.6.18 kernel. > > > > > > > > > > Hans > > > > > > > > adding the above line to the modules file (not to be confused > > > > with the /etc/modprobe.d/ivtv file) did nothing. I expected it to > > > > throw errors on boot as there actually is no module named > > > > "options" but it did not. It did not load the ivtv driver however > > > > until the hotplug stuff ran. > > > > > > > > I have tried your syntax you suggested above in > > > > > > the /etc/modprobe.d/ivtv file as stated below in my original post > > > and > > > > > > it did not work (see below): > > > > > > only resulted in the driver not finding the firmware file to > > > > > > load at runtime so nothing works. > > > > > > > > > > > > > > > > > > Here is my dmesg output: > > > > > > ivtv: ==================== START INIT IVTV > > > > > > ==================== ivtv: version 0.7.0 (tagged release) > > > > > > loading > > > > > > ivtv: Linux version: 2.6.17-chw-8 SMP preempt mod_unload 586 > > > > > > gcc-3.4 ivtv: In case of problems please include the debug > > > > > > info between ivtv: the START INIT IVTV and END INIT IVTV > > > > > > lines, along with ivtv: any module options, when mailing the > > > > > > ivtv-users mailinglist. ivtv0: Autodetected Hauppauge WinTV > > > > > > PVR-150 card (cx23416 based) ACPI: PCI Interrupt > > > > > > 0000:00:0a.0[A] -> GSI 18 (level, low) -> IRQ 22 tuner > > > > > > 0-0061: chip found @ 0xc2 (ivtv i2c driver #0) > > > > > > cx25840 0-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0) > > > > > > cx25840 0-0044: loaded v4l-cx25840.fw firmware (16382 bytes) > > > > > > wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0) > > > > > > tveeprom 0-0050: Hauppauge model 26052, rev C599, serial# > > > > > > 8805504 tveeprom 0-0050: tuner model is TCL 2002N 5H (idx 99, > > > > > > type 50) tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08) > > > > > > tveeprom 0-0050: audio processor is CX25843 (idx 37) > > > > > > tveeprom 0-0050: decoder processor is CX25843 (idx 30) > > > > > > tveeprom 0-0050: has no radio, has IR remote > > > > > > eth0: no IPv6 routers present > > > > > > eth1: no IPv6 routers present > > > > > > ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) > > > > > > ivtv0: Encoder revision: 0x02050032 > > > > > > ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers > > > > > > (4096KB total) ivtv0: Allocate DMA encoder YUV stream: 194 x > > > > > > 10800 buffers (2048KB total) ivtv0: Allocate DMA encoder VBI > > > > > > stream: 120 x 17472 buffers (2048KB total) ivtv0: Allocate > > > > > > DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB > > > > > > total) tuner 0-0061: type set to 50 (TCL 2002N) > > > > > > ivtv0: Initialized Hauppauge WinTV PVR-150, card #0 > > > > > > ivtv: ====================== NEXT CARD > > > > > > ====================== ivtv1: Autodetected Hauppauge WinTV > > > > > > PVR-150 card (cx23416 based) ACPI: PCI Interrupt > > > > > > 0000:00:0c.0[A] -> GSI 16 (level, low) -> IRQ 17 tuner > > > > > > 1-0061: chip found @ 0xc2 (ivtv i2c driver #1) cx25840 > > > > > > 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #1) cx25840 > > > > > > 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes) wm8775 > > > > > > 1-001b: chip found @ 0x36 (ivtv i2c driver #1) tveeprom > > > > > > 1-0050: Hauppauge model 26132, rev F0B2, serial# 9399761 > > > > > > tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type > > > > > > 4) tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08) > > > > > > tveeprom 1-0050: audio processor is CX25841 (idx 35) > > > > > > tveeprom 1-0050: decoder processor is CX25841 (idx 28) > > > > > > tveeprom 1-0050: has no radio, has IR remote > > > > > > ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) > > > > > > ivtv1: Encoder revision: 0x02050032 > > > > > > ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 buffers > > > > > > (4096KB total) ivtv1: Allocate DMA encoder YUV stream: 194 x > > > > > > 10800 buffers (2048KB total) ivtv1: Allocate DMA encoder VBI > > > > > > stream: 120 x 17472 buffers (2048KB total) ivtv1: Allocate > > > > > > DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB > > > > > > total) tuner 1-0061: tuner type not set tuner 1-0061: tuner > > > > > > type not set ivtv1: Initialized Hauppauge WinTV PVR-150, card > > > > > > #1 > > > > > > ivtv: ==================== END INIT IVTV > > > > > > ==================== > > > > > > > > > > > > > > > > > > Oddly enough this output was generated with the following > > > > > > /etc/modprobe.d/ivtv file in place > > > > > > alias char-major-81 videodev > > > > > > alias char-major-81-0 ivtv > > > > > > alias char-major-81-1 ivtv > > > > > > options ivtv tuner=50 > > > > > > > > Above is the /etc/modprobe.d/ivtv file which has the correct > > > > syntax in it as per your recommendation above. > > > > > > > > > > This is per your website at > > > > > > http://www.ivtvdriver.org/index.php/Howto#Module_options > > > > > > > > > > > > I have also tried it without the alias lines. > > > > > > > > > > > > I have tried the following tuner numbers with no success (per > > > > > > many different websites): > > > > > > 0,4,39,43,47,49,50 > > > > > > > > > > > > I have also tried renaming the above file to > > > > > > /etc/modprobe.d/ivtv1 to designate the second tuner and have > > > > > > tried with all the different combinations of tuner numbers. > > > > > > > > > > > > Unfortunately I could find no clear documentation on your > > > > > > site as to the structure of the config file for multiple > > > > > > tuners. > > > > > > > > > > > > I then upgraded my knoppmyth distro to R5D1 which was > > > > > > released a couple weeks ago. With this distro there are two > > > > > > other possible configuration files. One is the > > > > > > /etc/mythtv/modules/ivtv1 (for the second tuner) to which I > > > > > > added the same options line as the /etc/modprobe.d/ivtv file > > > > > > (supposed to be the same syntax). Then there is the > > > > > > /etc/sysconfig/ivtv/cfg-1 (again the 1 for the second card) > > > > > > and uncommented out the ivtv_tuner line. Again I tried with > > > > > > all the different tuner numbers. > > > > > > > > > > > > I also made sure all these files contained the same values at > > > > > > all times. Of course trying for each of the above listed > > > > > > tuner values. > > > > > > > > > > > > I also have made sure I have not used Mythtv to test the > > > > > > tuner. I have used the command line tools as per your > > > > > > troubleshooting guide. All with the same results. > > > > > > > > > > > > I have checked for IRQ conflicts and there are none. I have > > > > > > even tried putting the cards in different pci slots but every > > > > > > time I get the same result. > > > > > > > > > > > > I have seen on the list that the tuner type of 4 with an idx > > > > > > of 112 have been successfully configured and are in use I do > > > > > > not understand why my system refuses to recognize the second > > > > > > tuner automatically. I also do not understand why it refuses > > > > > > to be force configured as many on the list have had to do. > > > > > > > > > > > > My first tuner card is unaffected by the upgrade and I can > > > > > > still watch/record/etc. with the single tuner. > > > > > > > > > > > > Andre > > > > > > > > > > > > _______________________________________________ > > > > > > ivtv-users mailing list > > > > > > [email protected] > > > > > > http://ivtvdriver.org/mailman/listinfo/ivtv-users > > > > > > > > > > _______________________________________________ > > > > > ivtv-users mailing list > > > > > [email protected] > > > > > http://ivtvdriver.org/mailman/listinfo/ivtv-users > > > > > > > > _______________________________________________ > > > > ivtv-users mailing list > > > > [email protected] > > > > http://ivtvdriver.org/mailman/listinfo/ivtv-users > > > > > > _______________________________________________ > > > ivtv-users mailing list > > > [email protected] > > > http://ivtvdriver.org/mailman/listinfo/ivtv-users > > > > _______________________________________________ > > ivtv-users mailing list > > [email protected] > > http://ivtvdriver.org/mailman/listinfo/ivtv-users > > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
