I guess I spoke too soon on this. I can get video and sound from my PVR150 now, but I can't successfully change channels. Using ptune doesn't do anything at all. Output in the terminal window claims it is changing channels, but nothing is happening. Any ideas?
Ryan On 8/11/05, Ryan <[EMAIL PROTECTED]> wrote: > Interestingly enough, I seemed to have solved my own problem. Stupid > really. I was following Jarod's Guide (thanks a ton Jarod) and was > incorrectly setting the input for the 150 to 4, just like the 250. > Well, it seems that input 4 on the 150 is not Tuner, but instead it is > Composite 2. So, a quick change of the input "/usr/bin/ivtvctl -p 6 > -d /dev/video1" and suddenly, viola, 150 is working. > > As far as the sound goes on the 250, I did a "/sbin/rmmod ivtv" then > "/sbin/modprobe ivtv" and suddenly the sound worked. Can anyone > explain to me why I would have to modproe ivtv, the rmmod it, then > modprobe it again to get the sound on the 250 to work? > > > On 8/11/05, Ryan <[EMAIL PROTECTED]> wrote: > > Ok, I removed the alias lines and tried again. here is what I get in dmesg > > > > ivtv: ==================== START INIT IVTV ==================== > > ivtv: version 0.3.6 (w) loading > > ivtv: Linux version: 2.6.12-1.1390_FC4 686 REGPARM 4KSTACKS gcc-4.0 > > ivtv: In case of problems please include the debug info > > ivtv: between the START INIT IVTV and END INIT IVTV lines when > > ivtv: mailing the ivtv-devel mailinglist. > > ivtv: Autodetected WinTV PVR 250 card > > ivtv: Found an iTVC16 based chip > > ivtv: Unreasonably low latency timer, setting to 64 (was 32) > > ivtv: VIA PCI device: 0x3189 vendor: 0x1106 > > ivtv: i2c attach [client=tveeprom,ok] > > ivtv: Tuner Type 8, Tuner formats 0x00001000, Radio: yes, Model > > 0x00893496, Revision 0xc0384b10 > > ivtv: NTSC tuner detected > > ivtv: Radio detected > > ivtv: i2c attach [client=(tuner unset),ok] > > tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0) > > saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005) > > ivtv: i2c attach [client=saa7115[50],ok] > > ivtv: i2c attach [client=MSP3448W-A2,ok] > > ivtv: Encoder revision: 0x02040024 > > ivtv: Encoder Firmware may be buggy, use version 0x02040011 > > ivtv: Configuring WinTV PVR 250 card with 5 streams > > ivtv: Registered v4l2 device for encoder MPEG minor 0 > > ivtv: Create DMA encoder MPEG stream: 0 x 32768 buffers (0KB total) > > ivtv: Registered v4l2 device for encoder YUV minor 32 > > ivtv: Create DMA encoder YUV stream: 0 x 10800 buffers (0KB total) > > ivtv: Registered v4l2 device for encoder VBI minor 224 > > ivtv: Create DMA encoder VBI stream: 0 x 8736 buffers (0KB total) > > ivtv: Registered v4l2 device for encoder PCM audio minor 24 > > ivtv: Create DMA encoder PCM audio stream: 0 x 4608 buffers (0KB total) > > ivtv: Registered v4l2 device for encoder radio minor 64 > > ivtv: Create encoder radio stream > > ivtv: Setting Tuner 8 > > ivtv: Setting audio matrix to input 3, output 1 > > ivtv: Switching standard to NTSC. > > ivtv: Initialized WinTV PVR 250, card #0 > > ivtv: Autodetected WinTV PVR 150 card > > ivtv: Found an iTVC16 based chip > > ivtv: ivtv_enc_thread: pid = 3105, itv = 0xe24a8320 > > ivtv: ivtv_enc_vbi_thread: pid = 3106, itv = 0xe24a8320 > > ivtv: Unreasonably low latency timer, setting to 64 (was 32) > > ivtv: VIA PCI device: 0x3189 vendor: 0x1106 > > ivtv: i2c attach [client=tveeprom,ok] > > ivtv: i2c attach [client=(tuner unset),ok] > > tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1) > > saa7115: starting probe for adapter ivtv i2c driver #1 (0x10005) > > ivtv: Tuner Type 0, Tuner formats 0x00001000, Radio: yes, Model > > 0x008d1659, Revision 0xc0384b10 > > ivtv: Radio detected > > cx25840: starting probe for adapter ivtv i2c driver #0 (0x10005) > > cx25840: starting probe for adapter ivtv i2c driver #1 (0x10005) > > ivtv: i2c attach [client=cx25840[50],ok] > > ivtv: i2c attach [client=wm8775[50],ok] > > ivtv: Encoder revision: 0x02040024 > > ivtv: Encoder Firmware may be buggy, use version 0x02040011 > > ivtv: Configuring WinTV PVR 150 card with 5 streams > > ivtv: Registered v4l2 device for encoder MPEG minor 1 > > ivtv: Create DMA encoder MPEG stream: 0 x 32768 buffers (0KB total) > > ivtv: Registered v4l2 device for encoder YUV minor 33 > > ivtv: Create DMA encoder YUV stream: 0 x 10800 buffers (0KB total) > > ivtv: Registered v4l2 device for encoder VBI minor 225 > > ivtv: Create DMA encoder VBI stream: 0 x 8736 buffers (0KB total) > > ivtv: Registered v4l2 device for encoder PCM audio minor 25 > > ivtv: Create DMA encoder PCM audio stream: 0 x 4608 buffers (0KB total) > > ivtv: Registered v4l2 device for encoder radio minor 65 > > ivtv: Create encoder radio stream > > ivtv: Setting Tuner 0 > > ivtv: Switching standard to NTSC. > > ivtv: Initialized WinTV PVR 150, card #1 > > ivtv: ==================== END INIT IVTV ==================== > > ivtv: ivtv_enc_thread: pid = 3192, itv = 0xe24cb8cc > > ivtv: ivtv_enc_vbi_thread: pid = 3193, itv = 0xe24cb8cc > > > > Any obvious problems with this?? > > > > Thanks, > > Ryan > > > > On 8/11/05, Adam Forsyth <[EMAIL PROTECTED]> wrote: > > > These lines are only for old versions, not 0.3.x: > > > > > > alias tveeprom tveeprom-ivtv > > > alias tuner tuner-ivtv > > > alias msp3400 msp3400-ivtv > > > > > > Also, you should send your "dmesg | grep ivtv" to the list. > > > > > > On 8/11/05, Ryan <[EMAIL PROTECTED]> wrote: > > > > I've recently added a PVR150 to my current setup, and therefor need to > > > > go to the 0.3.x release of IVTV. Install is on a Fedora Core 4 box > > > > running kernel 2.6.12-1.1390. Both devices get created successfully, > > > > but when I try to capture from both, the 250 gives me video with no > > > > sound, and the 150 just gives me a black screen. Here is what I > > > > currently have in my modprobe.conf. > > > > > > > > alias char-major-81 videodev > > > > alias char-major-81-0 ivtv > > > > alias char-major-81-1 ivtv > > > > alias tveeprom tveeprom-ivtv > > > > alias tuner tuner-ivtv > > > > alias msp3400 msp3400-ivtv > > > > > > > > Does anyone have a 250 and a 150 working, and if so, what does your > > > > modprobe.conf look like? > > > > > > > > I'm fairly new to Linux, so if I need to provide more information, I > > > > can. > > > > > > > > Thanks, > > > > Ryan > > > > > > > > > > > > ------------------------------------------------------- > > > > SF.Net email is Sponsored by the Better Software Conference & EXPO > > > > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > > > > Practices > > > > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & > > > > QA > > > > Security * Process Improvement & Measurement * > > > > http://www.sqe.com/bsce5sf > > > > _______________________________________________ > > > > ivtv-devel mailing list > > > > [email protected] > > > > https://lists.sourceforge.net/lists/listinfo/ivtv-devel > > > > > > > > > > > > > ------------------------------------------------------- > > > SF.Net email is Sponsored by the Better Software Conference & EXPO > > > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > > > Practices > > > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > > > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > > > _______________________________________________ > > > ivtv-devel mailing list > > > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/ivtv-devel > > > > > > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
