> Hi Hans,
>
> I will try the 'bleeding edge' driver tomorrow and let you know the
> results.
>
> I posted the dmesg initially, but save you some research :) Below is the
> output on the new Alix 1C board;
I saw that one, but I need the *full* dmesg output, not just the ivtv part.
Regards,
Hans
>
>
> ivtv: Start initialization, version 1.0.0
> ivtv0: Initializing card #0
> ivtv0: Autodetected Hauppauge card (cx23416 based)
> ACPI: PCI Interrupt Link [LNKC] BIOS reported IRQ 0, using IRQ 10
> ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
> ACPI: PCI Interrupt 0000:00:0c.0[A] -> Link [LNKC] -> GSI 10 (level, low)
> -> IRQ 10
> ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> ivtv0: Encoder revision: 0x02060039
> tveeprom 0-0050: Hauppauge model 26559, rev F189, serial# 9929952
> tveeprom 0-0050: tuner model is TCL MFPE05 2 (idx 89, type 38)
> tveeprom 0-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L')
> PAL(D/D1/K)(eeprom 0x74)
> tveeprom 0-0050: audio processor is CX25843 (idx 37)
> tveeprom 0-0050: decoder processor is CX25843 (idx 30)
> tveeprom 0-0050: has radio, has no IR receiver, has no IR transmitter
> ivtv0: Autodetected Hauppauge WinTV PVR-150
> cx25840 0-0044: cx25843-24 found @ 0x88 (ivtv i2c driver #0)
> cx25840 0-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> ivtv0: i2c hardware 0x00000020 (wm8775) not found for command 0x4008646d
> ivtv0: Registered device video0 for encoder MPEG (4 MB)
> ivtv0: Registered device video32 for encoder YUV (2 MB)
> ivtv0: Registered device vbi0 for encoder VBI (1 MB)
> ivtv0: Registered device video24 for encoder PCM audio (1 MB)
> ivtv0: Registered device radio0 for encoder radio
> ivtv0: Initialized card #0: Hauppauge WinTV PVR-150
> ivtv: End initialization
>
> Below the part I miss on the Alix 1C but see on another pc;
>
> tuner 0-0043: chip found @ 0x86 (ivtv i2c driver #0)
> tda9887 0-0043: tda988[5/6/7] found @ 0x43 (tuner)
> tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> tuner 0-0061: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3))
>
> Hope this helps...
>
> Kind regards,
> Jan
>
> Hans Verkuil wrote:
>> On Monday 10 March 2008 12:12:09 Jan Tiri wrote:
>>
>>> Hans Verkuil wrote:
>>>
>>>> On Tuesday 26 February 2008 20:41:47 Jan Tiri wrote:
>>>>
>>>>> Hi Hans,
>>>>>
>>>>> Good point. Actually, because I have a 3,5" hanging on the Alix
>>>>> 1C, I hooked it on an ATX powersupply of 300W. I can imagine that
>>>>> the board is limiting the current and therefore does not comply
>>>>> completely with the PCI standards? But I still wonder why it works
>>>>> on the Alix 1C of my friend.
>>>>>
>>>> Does your card work fine in another PC? Just to verify it isn't
>>>> broken (the other possibility, of course).
>>>>
>>> Yes, I transferred the card to another pc to be able to record some
>>> programs, but it's just a temporary workaround. The working PVR150 on
>>> another Alix 1C was a misunderstanding, my friend reports the same
>>> issue, on debian. I saw a mail passing by concerning I2C conflicts
>>> with other chips... is that a possibility that my tuner is not
>>> detected and if so, how can I detect that and fix it?
>>>
>>
>> Using either a 2.6.25-rcX kernel or a kernel >= 2.6.22 together with the
>> bleeding-edge driver
>> (http://www.ivtvdriver.org/index.php/Download#Bleeding_Edge_driver)
>> will fix any i2c conflicts.
>>
>> It's not easy to detect i2c conflicts: I can tell whether that happens
>> if you would mail me your full dmesg output. But if there are no other
>> PCI cards besides the PVR150, then i2c conflicts are very unlikely.
>> However, if you also have a DVB card installed next to the PVR150, then
>> conflicts are definitely a possibility.
>>
>> Regards,
>>
>> Hans
>>
>>
>>>>> Is there an alternative for a PVR150 in USB format (= with mpeg2
>>>>> encoder/decoder and preferably ivtv support)? Or perhaps other
>>>>> ideas?
>>>>>
>>>> The PVR150 is of course just encoding, not decoding (only the
>>>> PVR-350 can do that). But the WinTV PVR USB2 is a USB-based encoder
>>>> using exactly the same encoder chip, although you need to use the
>>>> pvrusb2 driver for that one.
>>>>
>>> Ok, thanks.
>>>
>>> Kind regards,
>>> Jan
>>>
>>>
>>>> Regards,
>>>>
>>>> Hans
>>>>
>>>>
>>>>> Kind regards,
>>>>> Jan
>>>>>
>>>>> Hans Verkuil wrote:
>>>>>
>>>>>> On Tuesday 26 February 2008 20:01:56 Jan Tiri wrote:
>>>>>>
>>>>>>> Friendly reminder...
>>>>>>>
>>>>>>> I have no idea what to do next, except for downgrading the
>>>>>>> kernel and installing the ivtv package manually. I know the card
>>>>>>> is working fine in another pc, so I really wonder what is
>>>>>>> causing it to no detect certain modules.
>>>>>>>
>>>>>> A known reason for this behavior might be a powersupply that is
>>>>>> not powerful enough. i2c chips that cannot be detected is a
>>>>>> typical symptom of this. Since this a miniITX board I would not
>>>>>> be surprised if this is in fact the cause. These PVR boards need
>>>>>> more power than most.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Hans
>>>>>>
>>>>> _______________________________________________
>>>>> 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
