Mailing List Archive: ivtv: devel

Tuner (type 47) not loading - WinTV PVR350

Index | Next | Previous | View Threaded

eradicator at gentoo

Feb 19, 2005, 7:41 PM

Post #1 of 17 (2907 views)
Permalink

Tuner (type 47) not loading - WinTV PVR350

I just got a new WinTV PVR-350 from NewEgg a few days ago, and I'm
having a bit of trouble getting the tuner to work properly.

I'm using linux-2.6.10 and ivtv-0.2.0-rc3f. 2.6.10 has the following in
drivers/media/video/tuner.c:
{ "LG NTSC (TAPE series)", LGINNOTEK, NTSC,
16*160.00,16*442.00,0x01,0x02,0x04,0x8e,732 },

This is the same as shown in the latest patches from here:
http://205.209.168.201/~ckennedy/ivtv/new_tuners/

Unfortunately, when I 'modprobe ivtv', the tuner does not get setup.
Additionally, the svideo out is green. Does anyone have any
suggestions?

Thanks,
Jeremy

----
lspci -v
<snip>
0000:02:0a.0 Multimedia video controller: Internext Compression Inc
iTVC15 MPEG-2 Encoder (rev 01)
Subsystem: Hauppauge computer works Inc. WinTV PVR-350
Flags: bus master, medium devsel, latency 64, IRQ 12
Memory at e8000000 (32-bit, prefetchable)
Capabilities: [44] Power Management version 2
<snip>

----
dmesg log from 'modprobe ivtv'

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.2.0 (rc3) loading
ivtv: Linux version: 2.6.10-gentoo-r6 preempt PENTIUMIII gcc-3.3
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 350 card
ivtv: Found an iTVC15 based chip
PCI: Found IRQ 12 for device 0000:02:0a.0
ivtv: XXX PCI device: 0x1130 vendor: 0x8086
tveeprom: Hauppauge: model = 48132, rev = K268, serial# = 7775566
<LOOK HERE>
tveeprom: tuner = LG TAPE H001F MK3 (idx = 68, type = 47)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
</LOOK HERE>
tveeprom: audio_processor = MSP3440 (type = 11)
ivtv: i2c attach [client=tveeprom[3],ok]
saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005)
saa7115: detecting saa7115 client on address 0x42
saa7115: writing init values
ivtv: i2c attach [client=saa7115[3],ok]
saa7115: status: (1E) 0x48, (1F) 0xc0
saa7127: Selecting NTSC video Standard
saa7127: Selecting S-Video+Composite
saa7127: Turn WSS off
saa7127: Widescreen Mode 4:3 Full Format
saa7127: Selecting Normal Encoder Input
saa7127: Enable Video Output
ivtv: i2c attach [client=saa7127[3],ok]
msp34xx: ivtv version
msp34xx: init: chip=MSP3448W-A2, has NICAM support, simple (D) mode,
simpler (G) no-thread mode
msp34xx: $Id$ compiled on: Feb 19 2005 12:42:29
ivtv: i2c attach [client=MSP3448W-A2,ok]
<LOOK HERE>
ivtv: Tuner Type 47, Tuner formats 0x00001000, Radio: yes, Model
0x00ad2598, Revision 0x00000001
ivtv: NTSC tuner detected
ivtv: Radio detected
ivtv: Failed to load module tuner
</LOOK HERE>
ivtv: Encoder revision: 0x02040024
ivtv: Encoder Firmware is buggy, use version 0x02040011
ivtv: Decoder revision: 0x02020023
ivtv: Configuring WinTV PVR 350 card with 9 streams
ivtv: Create DMA stream 0 using 256 16384 byte buffers 4194304 kbytes
total
ivtv: Registered v4l2 device, streamtype 0 minor 0
ivtv: Create DMA stream 1 using 8 131072 byte buffers 1048576 kbytes
total
ivtv: Registered v4l2 device, streamtype 1 minor 32
ivtv: Create stream 2 using 40 52224 byte buffers 2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 2 minor 224
ivtv: Create DMA stream 3 using 455 4608 byte buffers 2097152 kbytes
total
ivtv: Registered v4l2 device, streamtype 3 minor 24
ivtv: Create stream 4
ivtv: Registered v4l2 device, streamtype 4 minor 64
ivtv: Create DMA stream 5 using 16 65536 byte buffers 1048576 kbytes
total
ivtv: Registered v4l2 device, streamtype 5 minor 16
ivtv: Create stream 6 using 1024 2048 byte buffers 262144 kbytes total
ivtv: Registered v4l2 device, streamtype 6 minor 228
ivtv: Create stream 7
ivtv: Registered v4l2 device, streamtype 7 minor 232
ivtv: Create DMA stream 8 using 16 65536 byte buffers 1048576 kbytes
total
ivtv: Registered v4l2 device, streamtype 8 minor 48
<LOOK HERE>
ivtv: Setting Tuner 47
ivtv: i2c client addr: 0x61 not found!
ivtv: i2c client addr: 0x61 not found!
ivtv: Setting audio matrix to input 3, output 1
ivtv: Switching standard to NTSC.
ivtv: i2c client addr: 0x61 not found!
</LOOK HERE>
ivtv: ivtv_enc_thread: pid = 25326, itv = 0xe0c7ffc0
ivtv: ivtv_dec_thread: pid = 25327, itv = 0xe0c7ffc0
saa7115: decoder set norm NTSC
saa7115: set audio: 0x01
saa7127: Setting Encoder Video Standard
saa7127: Set NTSC Video Mode
saa7127: Selecting NTSC video Standard
ivtv: Initialized WinTV PVR 350, card #0
ivtv: ==================== END INIT IVTV ===================
saa7115: decoder set size
lirc_dev: IR Remote Control driver registered, at major 61
lirc_i2c: chip found @ 0x18 (Hauppauge IR)
ivtv: i2c attach [client=Hauppauge IR,ok]
lirc_dev: lirc_register_plugin:sample_rate: 10

----
From rom /etc/modules.conf:
alias char-major-81 videodev
alias char-major-81-0 ivtv
alias char-major-61 lirc_i2c
add above ivtv lirc_dev lirc_i2c ivtv-fb

# NTSC
options ivtv ivtv_std=0

post-install ivtv /usr/local/sbin/ivtv_init

----
/usr/local/sbin/ivtv_init:
/usr/bin/ivtvctl -u 0x3000
/usr/bin/ivtvctl -f width=720,height=480
/usr/bin/ivtvctl -p 4

----
lsmod:
Module Size Used by
ivtv 816612 0
msp3400 29112 0
saa7127 13372 0
saa7115 13496 0
tveeprom 12532 0
i2c_algo_bit 10120 1 ivtv
nfs 208164 2
lockd 65512 2 nfs
sunrpc 152260 6 nfs,lockd
ohci_hcd 22344 0
ehci_hcd 31364 0
ohci1394 36196 0
ieee1394 110164 1 ohci1394
nvidia 3469788 0
i2c_i801 8620 0
i2c_core 22928 6
msp3400,saa7127,saa7115,tveeprom,i2c_algo_bit,i2c_i801
usbkbd 7488 0
snd_seq_midi 8992 0
usbhid 32960 0
snd_emu10k1_synth 7872 0
snd_emux_synth 39360 1 snd_emu10k1_synth
snd_seq_virmidi 7904 1 snd_emux_synth
snd_seq_midi_emul 7744 1 snd_emux_synth
uhci_hcd 34096 0
snd_pcm_oss 53856 0
snd_mixer_oss 20224 1 snd_pcm_oss
snd_seq_oss 37248 0
snd_seq_midi_event 7712 3 snd_seq_midi,snd_seq_virmidi,snd_seq_oss
snd_seq 55056 8
snd_seq_midi,snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_oss,snd_seq_midi_event
snd_emu10k1 103012 1 snd_emu10k1_synth
snd_rawmidi 25216 3 snd_seq_midi,snd_seq_virmidi,snd_emu10k1
snd_seq_device 9228 7
snd_seq_midi,snd_emu10k1_synth,snd_emux_synth,snd_seq_oss,snd_seq,snd_emu10k1,snd_rawmidi
snd_ac97_codec 78744 1 snd_emu10k1
snd_pcm 95400 3 snd_pcm_oss,snd_emu10k1,snd_ac97_codec
snd_timer 26212 3 snd_seq,snd_emu10k1,snd_pcm
snd_page_alloc 10084 2 snd_emu10k1,snd_pcm
snd_util_mem 4608 2 snd_emux_synth,snd_emu10k1
snd_hwdep 9888 2 snd_emux_synth,snd_emu10k1
snd 56292 13
snd_emux_synth,snd_seq_virmidi,snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_emu10k1,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm,snd_timer,snd_hwdep
soundcore 10080 1 snd
intel_agp 22652 1
agpgart 34728 1 intel_agp
evdev 9408 0
usbcore 121592 6 ohci_hcd,ehci_hcd,usbkbd,usbhid,uhci_hcd
binfmt_misc 11944 1
sidewinder 13088 0
adi 9664 0
emu10k1_gp 3808 0
gameport 4736 3 sidewinder,adi,emu10k1_gp
ide_cd 42564 0
cdrom 41020 1 ide_cd
floppy 60944 0
isofs 36728 0
udf 88708 0
rtc 12984 0
tulip 51040 0

Attachments:

signature.asc (0.18 KB)

eradicator at gentoo

Feb 20, 2005, 3:37 AM

Post #2 of 17 (2844 views)
Permalink

Re: Tuner (type 47) not loading - WinTV PVR350 [In reply to]

Ok, I solved the tuner problem by using:
I updated to 2.6.11-rc4 + http://dl.bytesex.org/patches/2.6.11-rc4-2/
and
http://dl.bytesex.org/cvs-snapshots/video4linux-20050218-161823.tar.gz

Also to fix the green svideo out, I did:
ivtvctl -j reg=0x6c,val=0xfa -d /dev/video16

--Jeremy

Attachments:

signature.asc (0.18 KB)

stephen at zmemw16

Feb 21, 2005, 2:28 PM

Post #3 of 17 (2822 views)
Permalink

Re: Tuner (type 47) not loading - WinTV PVR350 [In reply to]

Jeremy Huddleston wrote:

>Ok, I solved the tuner problem by using:
>I updated to 2.6.11-rc4 + http://dl.bytesex.org/patches/2.6.11-rc4-2/
>and
>http://dl.bytesex.org/cvs-snapshots/video4linux-20050218-161823.tar.gz
>
>Also to fix the green svideo out, I did:
>ivtvctl -j reg=0x6c,val=0xfa -d /dev/video16
>
>--Jeremy
>
>
>
used this as a basis for a dec-2000t box,

following some instructions about recording to mpeg, choose to use
'BBC ONE'
had to mkdir ./.xine and ./.tzap
fired up xine on the recorded file, it displayed Eastenders and as a
side effect, which apart from leaving speechless

sound on my toshiba satellite, its the one with ATI chipset

so i am now amazingly happy

stephen

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

mtdean at thirdcontact

Feb 25, 2005, 12:19 PM

Post #4 of 17 (2845 views)
Permalink

Re: Tuner (type 47) not loading - WinTV PVR350 [In reply to]

Jeremy Huddleston wrote:

>Ok, I solved the tuner problem by using:
>I updated to 2.6.11-rc4 + http://dl.bytesex.org/patches/2.6.11-rc4-2/
>and
>http://dl.bytesex.org/cvs-snapshots/video4linux-20050218-161823.tar.gz
>
>Also to fix the green svideo out, I did:
>ivtvctl -j reg=0x6c,val=0xfa -d /dev/video16
>
>
Glad you got it fixed. It looks like the update may have fixed it as a
"side-effect." Linux 2.6.10 and above will work without modifications,
but the problem seemed to be that your system could not find/load the
tuner module itself--not a problem with the tuner definition.

It's possible you may have been missing the tuner module (i.e. didn't
select any of the V4L drivers--BTTV, CX88, etc.--so it wasn't compiled)
or may have had a version compiled for a different version of the kernel
that failed to load into the 2.6.10 kernel or may have had a corrupt binary.

Enjoy your tuner.

Mike

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

jzellman at gmail

Feb 25, 2005, 6:43 PM

Post #5 of 17 (2847 views)
Permalink

Re: Tuner (type 47) not loading - WinTV PVR350 [In reply to]

Hi,

So I tried the fix and I updated to 2.6.11-rc4 +
http://dl.bytesex.org/patches/2.6.11-rc4-2/ and
http://dl.bytesex.org/cvs-snapshots/video4linux-20050218-161823.tar.gz

but all my channels are still static.

Im in the US so I am using ntsc hrc here is the output of dmesg |grep ivtv

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.2.0 (rc3g) loading
ivtv: Linux version: 2.6.11-rc4-kraxel2 preempt PENTIUMIII gcc-3.3
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 350 card
ivtv: Found an iTVC15 based chip
ivtv: XXX PCI device: 0x7124 vendor: 0x8086
ivtv: i2c attach [client=tda9887,ok]
ivtv: i2c attach [client=tveeprom,ok]
ivtv: i2c attach [client=(tuner unset),ok]
tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005)
ivtv: i2c attach [client=saa7115[5],ok]
ivtv: i2c attach [client=saa7127[5],ok]
msp34xx: ivtv version
ivtv: i2c attach [client=MSP3448W-A2,ok]
ivtv: Tuner Type 47, Tuner formats 0x00001000, Radio: yes, Model
0x00ad2598, Revision 0xd0ab088c
ivtv: NTSC tuner detected
ivtv: Radio detected
ivtv: Encoder revision: 0x02040011
ivtv: Decoder revision: 0x02020023
ivtv: Configuring WinTV PVR 350 card with 9 streams
ivtv: Create DMA stream 0 using 256 16384 byte buffers 4194304 kbytes total
ivtv: Registered v4l2 device, streamtype 0 minor 0
ivtv: Create DMA stream 1
ivtv: Registered v4l2 device, streamtype 1 minor 32
ivtv: Create stream 2 using 40 52224 byte buffers 2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 2 minor 224
ivtv: Create DMA stream 3 using 455 4608 byte buffers 2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 3 minor 24
ivtv: Create stream 4
ivtv: Registered v4l2 device, streamtype 4 minor 64
ivtv: Create DMA stream 5 using 16 65536 byte buffers 1048576 kbytes total
ivtv: Registered v4l2 device, streamtype 5 minor 16
ivtv: Create stream 6 using 1024 2048 byte buffers 262144 kbytes total
ivtv: Registered v4l2 device, streamtype 6 minor 228
ivtv: Create stream 7
ivtv: Registered v4l2 device, streamtype 7 minor 232
ivtv: Create DMA stream 8
ivtv: Registered v4l2 device, streamtype 8 minor 48
ivtv: Setting Tuner 47
ivtv: Setting audio matrix to input 3, output 1
ivtv: Switching standard to NTSC.
ivtv: ivtv_enc_thread: pid = 7604, itv = 0xd0aa5780
ivtv: ivtv_dec_thread: pid = 7605, itv = 0xd0aa5780
ivtv: Initialized WinTV PVR 350, card #0
ivtv: ==================== END INIT IVTV ====================

im running debian unstable and have the following configured in
/etc/modutils/ivtv

alias char-major-81 videodev
alias char-major-81-0 ivtv

Anyone have any suggestions?

thanks,

Jeff Zellman

On Fri, 25 Feb 2005 14:19:26 -0500, Michael T. Dean
<mtdean [at] thirdcontact> wrote:
> Jeremy Huddleston wrote:
>
> >Ok, I solved the tuner problem by using:
> >I updated to 2.6.11-rc4 + http://dl.bytesex.org/patches/2.6.11-rc4-2/
> >and
> >http://dl.bytesex.org/cvs-snapshots/video4linux-20050218-161823.tar.gz
> >
> >Also to fix the green svideo out, I did:
> >ivtvctl -j reg=0x6c,val=0xfa -d /dev/video16
> >
> >
> Glad you got it fixed. It looks like the update may have fixed it as a
> "side-effect." Linux 2.6.10 and above will work without modifications,
> but the problem seemed to be that your system could not find/load the
> tuner module itself--not a problem with the tuner definition.
>
> It's possible you may have been missing the tuner module (i.e. didn't
> select any of the V4L drivers--BTTV, CX88, etc.--so it wasn't compiled)
> or may have had a version compiled for a different version of the kernel
> that failed to load into the 2.6.10 kernel or may have had a corrupt binary.
>
> Enjoy your tuner.
>
> Mike
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] lists
> https://lists.sourceforge.net/lists/listinfo/ivtv-devel
>

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

mtdean at thirdcontact

Feb 25, 2005, 7:52 PM

Post #6 of 17 (2806 views)
Permalink

Re: Tuner (type 47) not loading - WinTV PVR350 [In reply to]

Jeffrey Zellman wrote:

>Hi,
>
>So I tried the fix and I updated to 2.6.11-rc4 +
>http://dl.bytesex.org/patches/2.6.11-rc4-2/ and
>http://dl.bytesex.org/cvs-snapshots/video4linux-20050218-161823.tar.gz
>
>but all my channels are still static.
>
>Im in the US so I am using ntsc hrc here is the output of dmesg |grep ivtv
>
>
That cuts out a lot of important information (that doesn't include the
word ivtv) from the ivtv init--including nearly all the important
information for determining the cause of tuner problems. Please post
the output of:

tac /var/log/messages |
sed -n '/=\ \ END INIT IVTV\ \ =/,/= START INIT IVTV =/p;
/= START INIT IVTV =/q' |
tac

Assuming your system log is /var/log/messages. You can also use "dmesg
| tac | " for the first line, but depending on how much has happened
since you initialized the card, some information can roll off the top of
the buffer, so I generally recommend using the system log file.

Mike

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

jzellman at gmail

Feb 25, 2005, 8:00 PM

Post #7 of 17 (2846 views)
Permalink

Re: Tuner (type 47) not loading - WinTV PVR350 [In reply to]

ok, when i load the ivtv module and run the tac command, this is the
output to /var/log/messages
Feb 25 20:57:30 localhost kernel: ivtv: ==================== START
INIT IVTV === =================
Feb 25 20:57:30 localhost kernel: ivtv: version 0.2.0 (rc3g) loading
Feb 25 20:57:30 localhost kernel: ivtv: Linux version:
2.6.11-rc4-kraxel2 preemp t PENTIUMIII gcc-3.3
Feb 25 20:57:30 localhost kernel: ivtv: In case of problems please
include the d ebug info
Feb 25 20:57:30 localhost kernel: ivtv: between the START INIT IVTV
and END INIT IVTV lines when
Feb 25 20:57:30 localhost kernel: ivtv: mailing the ivtv-devel mailinglist.
Feb 25 20:57:30 localhost kernel: ivtv: Autodetected WinTV PVR 350 card
Feb 25 20:57:30 localhost kernel: ivtv: Found an iTVC15 based chip
Feb 25 20:57:30 localhost kernel: PCI: Found IRQ 9 for device 0000:01:07.0
Feb 25 20:57:30 localhost kernel: PCI: Sharing IRQ 9 with 0000:00:01.0
Feb 25 20:57:30 localhost kernel: ivtv: XXX PCI device: 0x7124 vendor: 0x8086
Feb 25 20:57:30 localhost kernel: tda9885/6/7: chip found @ 0x86
Feb 25 20:57:30 localhost kernel: ivtv: i2c attach [client=tda9887,ok]
Feb 25 20:57:30 localhost kernel: ivtv: i2c attach [client=tveeprom,ok]
Feb 25 20:57:30 localhost kernel: ivtv: i2c attach [client=(tuner unset),ok]
Feb 25 20:57:30 localhost kernel: tuner 0-0061: chip found @ 0xc2
(ivtv i2c driv er #0)
Feb 25 20:57:30 localhost kernel: saa7115: starting probe for adapter
ivtv i2c d river #0 (0x10005)
Feb 25 20:57:30 localhost kernel: saa7115: detecting saa7115 client on
address 0 x42
Feb 25 20:57:30 localhost kernel: saa7115: writing init values
Feb 25 20:57:30 localhost kernel: ivtv: i2c attach [client=saa7115[6],ok]
Feb 25 20:57:30 localhost kernel: saa7115: status: (1E) 0x48, (1F) 0xc0
Feb 25 20:57:30 localhost kernel: saa7127: Selecting NTSC video Standard
Feb 25 20:57:30 localhost kernel: saa7127: Selecting S-Video+Composite
Feb 25 20:57:30 localhost kernel: saa7127: Turn WSS off
Feb 25 20:57:30 localhost kernel: saa7127: Widescreen Mode 4:3 Full Format
Feb 25 20:57:30 localhost kernel: saa7127: Selecting Normal Encoder Input
Feb 25 20:57:30 localhost kernel: saa7127: Enable Video Output
Feb 25 20:57:30 localhost kernel: ivtv: i2c attach [client=saa7127[6],ok]
Feb 25 20:57:30 localhost kernel: msp34xx: ivtv version
Feb 25 20:57:30 localhost kernel: msp34xx: init: chip=MSP3448W-A2, has
NICAM sup port, simple (D) mode, simpler (G) no-thread mode
Feb 25 20:57:30 localhost kernel: msp34xx: $Id$ compiled on: Feb 23
2005 22:05:0 6
Feb 25 20:57:31 localhost kernel: ivtv: i2c attach [client=MSP3448W-A2,ok]
Feb 25 20:57:31 localhost kernel: tveeprom: Hauppauge: model = 48132,
rev = K268 , serial# = 7683271
Feb 25 20:57:31 localhost kernel: tveeprom: tuner = LG TAPE H001F MK3
(idx = 68, type = 47)
Feb 25 20:57:31 localhost kernel: tveeprom: tuner fmt = NTSC(M)
(eeprom = 0x08, v4l2 = 0x00001000)
Feb 25 20:57:31 localhost kernel: tveeprom: audio_processor = MSP3440
(type = 11 )
Feb 25 20:57:31 localhost kernel: ivtv: Tuner Type 47, Tuner formats
0x00001000, Radio: yes, Model 0x00ad2598, Revision 0xd0ab088c
Feb 25 20:57:31 localhost kernel: ivtv: NTSC tuner detected
Feb 25 20:57:31 localhost kernel: ivtv: Radio detected
Feb 25 20:57:32 localhost kernel: ivtv: Encoder revision: 0x02040011
Feb 25 20:57:32 localhost kernel: ivtv: Decoder revision: 0x02020023
Feb 25 20:57:32 localhost kernel: ivtv: Configuring WinTV PVR 350 card
with 9 st reams
Feb 25 20:57:32 localhost kernel: ivtv: Create DMA stream 0 using 256
16384 byte buffers 4194304 kbytes total
Feb 25 20:57:32 localhost kernel: ivtv: Registered v4l2 device,
streamtype 0 min or 0
Feb 25 20:57:32 localhost kernel: ivtv: Create DMA stream 1
Feb 25 20:57:32 localhost kernel: ivtv: Registered v4l2 device,
streamtype 1 min or 32
Feb 25 20:57:32 localhost kernel: ivtv: Create stream 2 using 40 52224
byte buff ers 2097152 kbytes total
Feb 25 20:57:32 localhost kernel: ivtv: Registered v4l2 device,
streamtype 2 min or 224
Feb 25 20:57:32 localhost kernel: ivtv: Create DMA stream 3 using 455
4608 byte buffers 2097152 kbytes total
Feb 25 20:57:32 localhost kernel: ivtv: Registered v4l2 device,
streamtype 3 min or 24
Feb 25 20:57:32 localhost kernel: ivtv: Create stream 4
Feb 25 20:57:32 localhost kernel: ivtv: Registered v4l2 device,
streamtype 4 min or 64
Feb 25 20:57:32 localhost kernel: ivtv: Create DMA stream 5 using 16
65536 byte buffers 1048576 kbytes total
Feb 25 20:57:32 localhost kernel: ivtv: Registered v4l2 device,
streamtype 5 min or 16
Feb 25 20:57:32 localhost kernel: ivtv: Create stream 6 using 1024
2048 byte buf fers 262144 kbytes total
Feb 25 20:57:32 localhost kernel: ivtv: Registered v4l2 device,
streamtype 6 min or 228
Feb 25 20:57:32 localhost kernel: ivtv: Create stream 7
Feb 25 20:57:32 localhost kernel: ivtv: Registered v4l2 device,
streamtype 7 min or 232
Feb 25 20:57:32 localhost kernel: ivtv: Create DMA stream 8
Feb 25 20:57:32 localhost kernel: ivtv: Registered v4l2 device,
streamtype 8 min or 48
Feb 25 20:57:32 localhost kernel: ivtv: Setting Tuner 47
Feb 25 20:57:32 localhost kernel: tuner 0-0061: type set to 47 (LG
NTSC (TAPE se ries))
Feb 25 20:57:32 localhost kernel: ivtv: Setting audio matrix to input
3, output 1
Feb 25 20:57:32 localhost kernel: ivtv: Switching standard to NTSC.
Feb 25 20:57:32 localhost kernel: ivtv: ivtv_enc_thread: pid = 8442,
itv = 0xd0a a5780
Feb 25 20:57:32 localhost kernel: ivtv: ivtv_dec_thread: pid = 8443,
itv = 0xd0a a5780
Feb 25 20:57:32 localhost kernel: saa7115: decoder set norm NTSC
Feb 25 20:57:32 localhost kernel: saa7115: set audio: 0x01
Feb 25 20:57:32 localhost kernel: saa7127: Setting Encoder Video Standard
Feb 25 20:57:32 localhost kernel: saa7127: Set NTSC Video Mode
Feb 25 20:57:32 localhost kernel: saa7127: Selecting NTSC video Standard
Feb 25 20:57:32 localhost kernel: ivtv: Initialized WinTV PVR 350, card #0
Feb 25 20:57:32 localhost kernel: ivtv: ==================== END INIT
IVTV === =================

thanks,

Jeff

On Fri, 25 Feb 2005 21:52:26 -0500, Michael T. Dean
<mtdean [at] thirdcontact> wrote:
> Jeffrey Zellman wrote:
>
> >Hi,
> >
> >So I tried the fix and I updated to 2.6.11-rc4 +
> >http://dl.bytesex.org/patches/2.6.11-rc4-2/ and
> >http://dl.bytesex.org/cvs-snapshots/video4linux-20050218-161823.tar.gz
> >
> >but all my channels are still static.
> >
> >Im in the US so I am using ntsc hrc here is the output of dmesg |grep ivtv
> >
> >
> That cuts out a lot of important information (that doesn't include the
> word ivtv) from the ivtv init--including nearly all the important
> information for determining the cause of tuner problems. Please post
> the output of:
>
> tac /var/log/messages |
> sed -n '/=\ \ END INIT IVTV\ \ =/,/= START INIT IVTV =/p;
> /= START INIT IVTV =/q' |
> tac
>
> Assuming your system log is /var/log/messages. You can also use "dmesg
> | tac | " for the first line, but depending on how much has happened
> since you initialized the card, some information can roll off the top of
> the buffer, so I generally recommend using the system log file.
>
> Mike
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] lists
> https://lists.sourceforge.net/lists/listinfo/ivtv-devel
>

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

mavantix at gmail

Feb 25, 2005, 8:20 PM

Post #8 of 17 (2819 views)
Permalink

Re: Tuner (type 47) not loading - WinTV PVR350 [In reply to]

Only way I could get my tuner type 47 to tune channels is to force it
to type 44 in mod*.conf. I still haven't resolved the dma lockup
problem when you ff/rew alot.

-Kenneth

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

jzellman at gmail

Feb 25, 2005, 10:48 PM

Post #9 of 17 (2845 views)
Permalink

Re: Tuner (type 47) not loading - WinTV PVR350 [In reply to]

ive tried 44, 45,46, 47 none seem to work. has anyone found a
solution to this yet?

-Jeff

On Fri, 25 Feb 2005 22:20:57 -0500, Maverick <mavantix [at] gmail> wrote:
> Only way I could get my tuner type 47 to tune channels is to force it
> to type 44 in mod*.conf. I still haven't resolved the dma lockup
> problem when you ff/rew alot.
>
> -Kenneth
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] lists
> https://lists.sourceforge.net/lists/listinfo/ivtv-devel
>

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

mavantix at gmail

Feb 25, 2005, 10:58 PM

Post #10 of 17 (2861 views)
Permalink

Re: Tuner (type 47) not loading - WinTV PVR350 [In reply to]

I had static on my type 47 until I forced the tuner type to 44, I may
have also upgraded to the 0.3.x version of ivtv at the same time. Have
you tried that?

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

mtdean at thirdcontact

Feb 27, 2005, 6:26 AM

Post #11 of 17 (2843 views)
Permalink

Re: Tuner (type 47) not loading - WinTV PVR350 [In reply to]

Maverick wrote:

>Only way I could get my tuner type 47 to tune channels is to force it
>to type 44 in mod*.conf. I still haven't resolved the dma lockup
>problem when you ff/rew alot.
>
>
That's because your kernel doesn't have support for type 47. If you
upgrade to 2.6.10 or patch your kernel as described at
http://ivtv.no-ip.info/new_tuners, type 47 will work as autodetected.

Mike

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

mtdean at thirdcontact

Feb 27, 2005, 6:28 AM

Post #12 of 17 (2839 views)
Permalink

Re: Tuner (type 47) not loading - WinTV PVR350 [In reply to]

Maverick wrote:

>I had static on my type 47 until I forced the tuner type to 44,
>
That's because your kernel doesn't have support for type 47. If you
upgrade to 2.6.10 or patch your kernel as described at
http://ivtv.no-ip.info/new_tuners, type 47 will work as autodetected.

> I may
>have also upgraded to the 0.3.x version of ivtv at the same time. Have
>you tried that?
>
>
I recommend staying away from 0.3.x unless you have a PVR-150 or
PVR-500. The tuner module that ships with 0.3.x is missing many tuner
definitions--including that for tuner 47 (LG TAPE NTSC) and tuner 50
(TCL 2002N NTSC). If using Axel Thimm's RPM's, though, the "hacked up"
tuner is installed as tuner-ivtv and won't interfere.

Mike

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

mtdean at thirdcontact

Feb 27, 2005, 6:34 AM

Post #13 of 17 (2848 views)
Permalink

Re: Tuner (type 47) not loading - WinTV PVR350 [In reply to]

Jeffrey Zellman wrote:

>ok, when i load the ivtv module and run the tac command, this is the
>output to /var/log/messages
>...
>Feb 25 20:57:30 localhost kernel: tuner 0-0061: chip found @ 0xc2
>(ivtv i2c driv er #0)
>
>
good

>...
>Feb 25 20:57:30 localhost kernel: saa7127: Selecting NTSC video Standard
>
>
Good.

>...
>Feb 25 20:57:31 localhost kernel: tveeprom: Hauppauge: model = 48132,
>rev = K268 , serial# = 7683271
>Feb 25 20:57:31 localhost kernel: tveeprom: tuner = LG TAPE H001F MK3
>(idx = 68, type = 47)
>Feb 25 20:57:31 localhost kernel: tveeprom: tuner fmt = NTSC(M)
>(eeprom = 0x08, v4l2 = 0x00001000)
>Feb 25 20:57:31 localhost kernel: tveeprom: audio_processor = MSP3440
>(type = 11 )
>Feb 25 20:57:31 localhost kernel: ivtv: Tuner Type 47, Tuner formats
>0x00001000, Radio: yes, Model 0x00ad2598, Revision 0xd0ab088c
>Feb 25 20:57:31 localhost kernel: ivtv: NTSC tuner detected
>
>
perfect

>...
>Feb 25 20:57:32 localhost kernel: ivtv: Setting Tuner 47
>Feb 25 20:57:32 localhost kernel: tuner 0-0061: type set to 47 (LG
>NTSC (TAPE se ries))
>
>
Everything worked correctly. Therefore, the tuner type is not the
problem. Instead, you may be using the wrong frequency list (i.e.
us-cable instead of us-cable-hrc), the wrong tuner input (you probably
want "-p 4" (tuner 0), or something I'm not yet considering.

At this point, continue debugging the configuration, but look elsewhere
for the problem--not at the tuner.

HTH.

Mike

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

mavantix at gmail

Feb 27, 2005, 10:42 AM

Post #14 of 17 (2823 views)
Permalink

Re: Tuner (type 47) not loading - WinTV PVR350 [In reply to]

> >I had static on my type 47 until I forced the tuner type to 44,
> >
> That's because your kernel doesn't have support for type 47. If you
> upgrade to 2.6.10 or patch your kernel as described at
> http://ivtv.no-ip.info/new_tuners, type 47 will work as autodetected.

I am on kernel 2.6.10, I had to force type 44 to get away from the
static on all channels. If it autodetects it, it's all static, all the
time.

-Kenneth

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

jarod at wilsonet

Feb 27, 2005, 12:31 PM

Post #15 of 17 (2844 views)
Permalink

Re: Tuner (type 47) not loading - WinTV PVR350 [In reply to]

On Sunday 27 February 2005 05:28, Michael T. Dean wrote:
> Maverick wrote:
> >I had static on my type 47 until I forced the tuner type to 44,
>
> That's because your kernel doesn't have support for type 47. If you
> upgrade to 2.6.10 or patch your kernel as described at
> http://ivtv.no-ip.info/new_tuners, type 47 will work as autodetected.
>
> > I may
> >have also upgraded to the 0.3.x version of ivtv at the same time. Have
> >you tried that?
>
> I recommend staying away from 0.3.x unless you have a PVR-150 or
> PVR-500. The tuner module that ships with 0.3.x is missing many tuner
> definitions--including that for tuner 47 (LG TAPE NTSC) and tuner 50
> (TCL 2002N NTSC).

I patched support for 47 back into the 0.3.x tuner module along with support
for the tuner on my PVR-500, so both my PVR-150MCE and 500MCE work with the
0.3.2e+megapatch+500tveeprom patches recently posted to the list. The stuff
for the 500 has been submitted upstream, will hopefully land as tuner type
57...

--
Jarod Wilson
jarod [at] wilsonet

mtdean at thirdcontact

Feb 27, 2005, 5:54 PM

Post #16 of 17 (2825 views)
Permalink

Re: Tuner (type 47) not loading - WinTV PVR350 [In reply to]

Jarod Wilson wrote:

>I patched support for 47 back into the 0.3.x tuner module along with support
>for the tuner on my PVR-500, so both my PVR-150MCE and 500MCE work with the
>0.3.2e+megapatch+500tveeprom patches recently posted to the list. The stuff
>for the 500 has been submitted upstream, will hopefully land as tuner type
>57...
>
Good to hear. I just saw your post on the V4L list. Will keep this in
mind.

Mike

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

mavantix at gmail

Feb 27, 2005, 6:11 PM

Post #17 of 17 (2839 views)
Permalink

Re: Tuner (type 47) not loading - WinTV PVR350 [In reply to]

Cool. I'd love to think all the latest patches (removal of osd vsync
irq stuff) help out the IRQ lockup's I'm having. I'm totally convinced
the problem is because the onboard VGA and the PVR-350 are sharing the
same IRQ in my box. Unfortunately, the BIOS won't let me change them
independently. I moved my 350 and HD to a different box, where things
weren't sharing, and no lockups. Hehe.

On another note, just ordered a Silverstone LC11, Chaintech 7NIF2,
Athlon XP 2700+, 512mb... so it better work correctly with the new
hardware! Of course if the tvout doesn't work, I'll have the onboard
nVidia... :)

-Kenneth

On Sun, 27 Feb 2005 11:31:06 -0800, Jarod Wilson <jarod [at] wilsonet> wrote:
> On Sunday 27 February 2005 05:28, Michael T. Dean wrote:
> > Maverick wrote:
> > >I had static on my type 47 until I forced the tuner type to 44,
> >
> > That's because your kernel doesn't have support for type 47. If you
> > upgrade to 2.6.10 or patch your kernel as described at
> > http://ivtv.no-ip.info/new_tuners, type 47 will work as autodetected.
> >
> > > I may
> > >have also upgraded to the 0.3.x version of ivtv at the same time. Have
> > >you tried that?
> >
> > I recommend staying away from 0.3.x unless you have a PVR-150 or
> > PVR-500. The tuner module that ships with 0.3.x is missing many tuner
> > definitions--including that for tuner 47 (LG TAPE NTSC) and tuner 50
> > (TCL 2002N NTSC).
>
> I patched support for 47 back into the 0.3.x tuner module along with support
> for the tuner on my PVR-500, so both my PVR-150MCE and 500MCE work with the
> 0.3.2e+megapatch+500tveeprom patches recently posted to the list. The stuff
> for the 500 has been submitted upstream, will hopefully land as tuner type
> 57...
>
> --
> Jarod Wilson
> jarod [at] wilsonet
>
>
>

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads