On 27/02/2006, at 1:04 AM, Hans Verkuil wrote:
>> From what I can gather your PVR150 is misdetected as a PVR250. The
>> full
> kernel log should be available in /var/log/messages, so it would help
> me a lot if you can check there for the tveeprom messages
Mar 6 04:03:25 tv syslog-ng[6539]: syslog-ng version 1.6.9 starting
Mar 6 04:03:25 tv syslog-ng[6539]: Changing permissions on special
file /dev/tty12
Mar 6 04:03:25 tv t=(tuner unset), addr=61]
Mar 6 04:03:25 tv tveeprom 1-0050: Hauppauge model 48014, rev F408,
serial# 5194951
Mar 6 04:03:25 tv tveeprom 1-0050: tuner model is Philips FI1216 MK2
(idx 8, type 5)
Mar 6 04:03:25 tv tveeprom 1-0050: TV standards PAL(B/G) (eeprom 0x04)
Mar 6 04:03:25 tv tveeprom 1-0050: audio processor is MSP3415 (idx 6)
Mar 6 04:03:25 tv tveeprom 1-0050: has radio
Mar 6 04:03:25 tv saa7115 1-0021: saa7115 found @ 0x42 (ivtv i2c
driver #1)
Mar 6 04:03:25 tv ivtv1: i2c attach to card #1 ok [client=saa7115,
addr=21]
Mar 6 04:03:25 tv msp3400 1-0040: chip=MSP3415D-B3 +nicam +simple
mode=simple
Mar 6 04:03:25 tv msp3400 1-0040: msp3410 daemon started
Mar 6 04:03:25 tv ivtv1: i2c attach to card #1 ok [client=MSP3415D-
B3, addr=40]
Mar 6 04:03:25 tv ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144
bytes)
Mar 6 04:03:25 tv ivtv1: loaded v4l-cx2341x-dec.fw firmware (262144
bytes)
Mar 6 04:03:25 tv ivtv1: Encoder revision: 0x02050032
Mar 6 04:03:25 tv ivtv1: Decoder revision: 0x02020023
Mar 6 04:03:25 tv ivtv1: Allocate DMA encoder MPEG stream: 128 x
32768 buffers (4096KB total)
Mar 6 04:03:25 tv ivtv1: Allocate DMA encoder YUV stream: 161 x
12960 buffers (2048KB total)
Mar 6 04:03:25 tv ivtv1: Allocate DMA encoder VBI stream: 80 x 26208
buffers (2048KB total)
Mar 6 04:03:25 tv ivtv1: Allocate DMA encoder PCM audio stream: 455
x 4608 buffers (2048KB total)
Mar 6 04:03:25 tv ivtv1: Create encoder radio stream
Mar 6 04:03:25 tv tuner 1-0061: type set to 5 (Philips PAL_BG
(FI1216 and compatibles))
Mar 6 04:03:25 tv msp3400 1-0040: I/O error #1 (read 0x10/0x200)
Mar 6 04:03:25 tv msp3400 1-0040: I/O error #2 (read 0x10/0x200)
Mar 6 04:03:25 tv msp3400 1-0040: I/O error #3 (read 0x10/0x200)
Mar 6 04:03:25 tv msp3400 1-0040: giving up, resetting chip. Sound
will go off, sorry folks :-|
> I'd also like to know what ivtv thinks you have. For that, run
> ivtv-detect.
# ivtv-detect
driver: ivtv-0.4.2 (tagged release)
card: WinTV PVR 150, bus info 0000:00:09.0, ivtv card #0
hardware: cx25840 tda9887 wm8775 tveeprom
/dev/v4l/video0: MPG encoding (links: /dev/video, /dev/video0)
/dev/v4l/vbi0: VBI encoding (links: /dev/vbi, /dev/vbi0)
/dev/v4l/video24: PCM encoding (links: /dev/video24)
/dev/v4l/video32: YUV encoding (links: /dev/video32)
driver: ivtv-0.4.2 (tagged release)
card: WinTV PVR 250, bus info 0000:00:0b.0, ivtv card #1
hardware: saa7115 msp34xx tveeprom
/dev/v4l/video1: MPG encoding (links: /dev/video1)
/dev/v4l/radio1: Radio (links: /dev/radio1)
/dev/v4l/vbi1: VBI encoding (links: /dev/vbi1)
/dev/v4l/video25: PCM encoding (links: /dev/video25)
/dev/v4l/video33: YUV encoding (links: /dev/video33)
> The probable cause of all the confusion is that the driver relies
> on the
> PCI IDs of the card to detect what type it is. It turns out that that
> is not very reliable and that instead the tveeprom info should be
> used.
> The problem is that I don't fully know which models map to which card
> type, so misdetections can happen.
>
> However, I first need the info mentioned above before I can say if
> it is
> really a misdetection problem.
>
> You can also as a quick band-aid use the cardtype module option of
> ivtv.
> In your case that should probably be cardtype=1,3 or cardtype=3,1
> depending on whether the PVR250 or the PVR150 is detected first.
I didn't try this last thing yet because it appears (to my uninformed
eye) that the card is being detected appropriately.
Do you believe this is the case?
Ari Maniatis
-------------------------->
ish
http://www.ish.com.au
Level 1, 30 Wilson Street Newtown 2042 Australia
phone +61 2 9550 5001 fax +61 2 9550 4001
PGP fingerprint 08 57 20 4B 80 69 59 E2 A9 BF 2D 48 C2 20 0C C8
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
