On Sunday 14 October 2007 22:26:41 Ma Begaj wrote:
> Hi,
>
> I am using a few days old ivtv cvs. I have 1x pvr150 and 1x pvr500.
>
> I receive sometimes after reboot an error that tuner type for pvr150
> is not detected and the ivtv sets 0 and uses NTSC-M by default. but I
> need PAL-B. consequence: I have no picture on pvr150.
>
> [EMAIL PROTECTED]:/tmp# dmesg |grep ivtv0
> ivtv0: Initializing card #0
> ivtv0: Autodetected Hauppauge card (cx23416 based)
> ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> ivtv0: Autodetected Hauppauge WinTV PVR-150
> ivtv0: No tuner detected, default to NTSC-M
> ivtv0: Registered device video0 for encoder MPG (4096 kB)
> ivtv0: Registered device video32 for encoder YUV (2048 kB)
> ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
> ivtv0: Registered device video24 for encoder PCM (320 kB)
> ivtv0: Initialized card #0: Hauppauge WinTV PVR-150
> ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> ivtv0: Encoder revision: 0x02060039
>
>
> as you see, it says:
> ivtv0: No tuner detected, default to NTSC-M
>
> I usually just modprobe ivtv and it loads the rest. I thought about
> using "tuner=xxxx" for modprobe, but I was not sure about this,
> because I have two different cards.
>
> I also see this in dmesg, when tuner type si not recognized:
> [EMAIL PROTECTED]:~# dmesg | grep tveeprom | grep bad
> tveeprom 2-0050: Encountered bad packet header [ff]. Corrupt or not a
> Hauppauge eeprom.
>
>
> When I rmmod ivtv and all depending modules, it is usually ok and
> syslog show this:
> ---------------------------------------------------------------------
>--------------- Oct 14 21:54:21 mythbox kernel: ivtv: Start
> initialization, version 1.1.0 Oct 14 21:54:21 mythbox kernel: ivtv0:
> Initializing card #0
> Oct 14 21:54:21 mythbox kernel: ivtv0: Autodetected Hauppauge card
> (cx23416 based)
> Oct 14 21:54:21 mythbox kernel: ACPI: PCI Interrupt 0000:01:09.0[A]
> -> Link [APC2] -> GSI 17 (level, low) -> IRQ 21
> Oct 14 21:54:22 mythbox kernel: tveeprom 2-0050: Hauppauge model
> 26134, rev F1B3, serial# 10233063
> Oct 14 21:54:22 mythbox kernel: tveeprom 2-0050: tuner model is TCL
> M2523_3DB_E (idx 113, type 55)
> Oct 14 21:54:22 mythbox kernel: tveeprom 2-0050: TV standards
> PAL(B/G) PAL(D/D1/K) (eeprom 0x44)
> Oct 14 21:54:22 mythbox kernel: tveeprom 2-0050: audio processor is
> CX25842 (idx 36)
> Oct 14 21:54:22 mythbox kernel: tveeprom 2-0050: decoder processor is
> CX25842 (idx 29)
> Oct 14 21:54:22 mythbox kernel: tveeprom 2-0050: has no radio, has IR
> receiver, has IR transmitter
> Oct 14 21:54:22 mythbox kernel: ivtv0: Autodetected Hauppauge WinTV
> PVR-150 Oct 14 21:54:22 mythbox kernel: ivtv0: Reopen i2c bus for
> IR-blaster support Oct 14 21:54:22 mythbox kernel: tuner 2-0061: chip
> found @ 0xc2 (ivtv i2c driver #0)
> Oct 14 21:54:22 mythbox kernel: cx25840 2-0044: cx25842-24 found @
> 0x88 (ivtv i2c driver #0)
> Oct 14 21:54:22 mythbox kernel: wm8775 2-001b: chip found @ 0x36
> (ivtv i2c driver #0)
> Oct 14 21:54:22 mythbox kernel: tuner-simple 2-0061: type set to 55
> (TCL 2002MB) Oct 14 21:54:22 mythbox kernel: tuner 2-0061: type set
> to TCL 2002MB Oct 14 21:54:22 mythbox kernel: ivtv0: Registered
> device video0 for encoder MPG (4096 kB)
> Oct 14 21:54:22 mythbox kernel: ivtv0: Registered device video32 for
> encoder YUV (2048 kB)
> Oct 14 21:54:22 mythbox kernel: ivtv0: Registered device vbi0 for
> encoder VBI (1024 kB)
> Oct 14 21:54:22 mythbox kernel: ivtv0: Registered device video24 for
> encoder PCM (320 kB)
> Oct 14 21:54:22 mythbox kernel: ivtv0: Initialized card #0: Hauppauge
> WinTV PVR-150
>
>
> but when it goes bad, syslog shows me this:
> ---------------------------------------------------------------------
>--------------- Oct 14 21:35:39 mythbox kernel: ivtv: Start
> initialization, version 1.1.0 Oct 14 21:35:39 mythbox kernel: ivtv0:
> Initializing card #0
> Oct 14 21:35:39 mythbox kernel: ivtv0: Autodetected Hauppauge card
> (cx23416 based)
> Oct 14 21:35:39 mythbox kernel: ACPI: PCI Interrupt 0000:01:09.0[A]
> -> Link [APC2] -> GSI 17 (level, low) -> IRQ 21
> Oct 14 21:35:39 mythbox kernel: ivtv0: Unreasonably low latency
> timer, setting to 64 (was 32)
> Oct 14 21:35:39 mythbox kernel: ivtv0: Autodetected Hauppauge WinTV
> PVR-150 Oct 14 21:35:39 mythbox kernel: ivtv0: No tuner detected,
> default to NTSC-M Oct 14 21:35:39 mythbox kernel: ACPI: PCI Interrupt
> 0000:00:05.0[A] -> Link [APC7] -> GSI 16 (level, low) -> IRQ 22
> Oct 14 21:35:39 mythbox kernel: tuner 2-0061: chip found @ 0xc2 (ivtv
> i2c driver #0)
> Oct 14 21:35:39 mythbox kernel: cx25840 2-0044: cx25842-24 found @
> 0x88 (ivtv i2c driver #0)
> Oct 14 21:35:39 mythbox kernel: wm8775 2-001b: chip found @ 0x36
> (ivtv i2c driver #0)
> Oct 14 21:35:39 mythbox kernel: tuner-simple 2-0061: type set to 0
> (Temic PAL (4002 FH5))
> Oct 14 21:35:39 mythbox kernel: tuner 2-0061: type set to Temic PAL
> (4002 FH5) Oct 14 21:35:39 mythbox kernel: ivtv0: Registered device
> video0 for encoder MPG (4096 kB)
> Oct 14 21:35:39 mythbox kernel: ivtv0: Registered device video32 for
> encoder YUV (2048 kB)
> Oct 14 21:35:39 mythbox kernel: ivtv0: Registered device vbi0 for
> encoder VBI (1024 kB)
> Oct 14 21:35:39 mythbox kernel: ivtv0: Registered device video24 for
> encoder PCM (320 kB)
> Oct 14 21:35:39 mythbox kernel: ivtv0: Initialized card #0: Hauppauge
> WinTV PVR-150
>
>
> difference is that tuner is not detected and tuner type is set to 0
> ... it is 55 when it works.
>
>
> can I somehow force tuner type for the first card to 55? It works
> when I use "modprobe ivtv tuner=55", but I have no idea does this
> somehow affects pvr500.
No, this is fine. It changes only the tuner for the PVR150 in your
setup.
Is this problem something that you always got, or is it only recently?
It looks like you are using the version from the v4l-dvb repository and
I made a change there some time ago that might cause this problem. Look
in the file ivtv-i2c.c and search for 'udelay'. You find the following
line:
.udelay = 5,
Change the 5 to 10 and see if the problem has gone.
Regards,
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
