Hi Edward,
I think you probably have a HVR-1600 with Samsung memory chips. This
hasn't been tested yet, but you definitely need the very latest cx18
driver for that (I've added Samsung timings yesterday).
Whether it will work I do not know, but the easiest way to test it is to
load the driver, try 'cat /dev/video0 >test.mpg' and if it doesn't work
check dmesg. You will probably see some 'Mismatch' messages, meaning
that the memory timings are probably still not right.
Note that this is the cx18 driver, not ivtv. The ivtv driver has nothing
to do with this (except for the fact that much of the cx18 driver code
is a copy of ivtv code).
Regards,
Hans
On Monday 31 December 2007 16:29, Edward Monk wrote:
> Hello Hans,
>
> When I enter the command you mentioned I get a nasty message saying :
> dcerouter_52331:/dev# cat /dev/video0 >test.mpg
> cat: /dev/video0: No such device or address
>
> BTW, This installation is for linuxMCE.
>
>
> I did the dmseg, but I did not see any mention of the ivtv.
>
> [ 32.176000] cx18: Start initialization, version 0.1.0
> [ 32.176000] cx18-0: Initializing card #0
> [ 32.176000] cx18-0: Autodetected Hauppauge card
> [ 32.176000] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKA] ->
> GSI 3 (level, low) -> IRQ 3
> [ 32.176000] cx18-0: Unreasonably low latency timer, setting to 64
> (was 32)
> [ 32.176000] cx18-0: cx23418 revision 01010000 (B)
> [ 32.344000] tveeprom 0-0050: Hauppauge model 74541, rev C5B6,
> serial# 2980264
> [ 32.344000] tveeprom 0-0050: MAC address is 00-0D-FE-2D-79-A8
> [ 32.344000] tveeprom 0-0050: tuner model is Philips FM1236 MK5
> (idx 116, type 43)
> [ 32.344000] tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
> [ 32.344000] tveeprom 0-0050: audio processor is CX23418 (idx 38)
> [ 32.344000] tveeprom 0-0050: decoder processor is CX23418 (idx 31)
> [ 32.344000] tveeprom 0-0050: has radio, has no IR receiver, has no
> IR transmitter
> [ 32.344000] cx18-0: Autodetected Hauppauge HVR-1600
> [ 32.384000] input: PC Speaker as /class/input/input2
> [ 32.420000] parport: PnPBIOS parport detected.
> [ 32.420000] parport0: PC-style at 0x378 (0x778), irq 7, dma 3
> [PCSPP,TRISTATE,COMPAT,ECP,DMA]
> [ 32.452000] input: PS/2 Logitech Mouse as /class/input/input3
> [ 32.540000] bcm43xx driver
> [ 32.820000] tuner' 1-0043: chip found @ 0x86 (cx18 i2c driver
> #0-1) [ 32.820000] tda9887 1-0043: tda988[5/6/7] found
> [ 32.828000] tuner' 1-0061: chip found @ 0xc2 (cx18 i2c driver
> #0-1) [ 32.876000] cs5345 0-004c: chip found @ 0x98 (cx18 i2c
> driver #0-0) [ 32.884000] cx18-0: Disabled encoder IDX device
> [ 32.884000] cx18-0: Registered device video0 for encoder MPEG (2
> MB) [ 32.884000] cx18-0: Registered device video16 for TS (2 MB) [
> 32.884000] cx18-0: Registered device video32 for encoder YUV (2 MB)
> [ 32.884000] cx18-0: Registered device vbi0 for encoder VBI (1 MB)
> [ 32.884000] cx18-0: Registered device video24 for encoder PCM
> audio (1 MB)
> [ 32.884000] cx18-0: Registered device radio0 for encoder radio
> [ 32.884000] tuner-simple 1-0061: type set to 43 (Philips NTSC MK3
> (FM1236MK3 or FM1236/F))
> [ 32.884000] tuner' 1-0043: Tuner frontend module has no way to set
> config [ 32.884000] cx18-0: Initialized card #0: Hauppauge HVR-1600
> [ 32.884000] cx18: End initialization
>
> I do see sveral entries for cx18 with reference to the card (which
> seems encouraging).
>
> Examples:
> cx18: Start initializtaion, version 0.1.0
> cx18-0: Initializing Card #0
> cx18-0: Auto Detected Hauppauge card
>
> Then a couple of lined below that a couple of other cx18 lines
> a lot of tveeprom lines...all look like good messages
> and finally a...
> cx18-0: Autodetected Hauppage HVR-1600 (that looks pretty good too).
>
> later in the listing there is lots of reference to cx18 and the
>
> On Dec 31, 2007 10:03 AM, Hans Verkuil <[EMAIL PROTECTED]> wrote:
> > On Sunday 30 December 2007 21:57, Edward Monk wrote:
> > > Hello,
> > >
> > > I am trying to use the hauppauge 1600 with the information found
> > > on: http://ivtvdriver.org/index.php/Cx18
> > >
> > > with the linuxmce...
> > > I followed the instuctions and it seems to have responed to the
> > > commands, but I have no idea if it worked. I guess I do not know
> > > enough about kubuntu to know if it recognizes the card. anyone
> > > have any suggestions?
> >
> > If you can do 'cat /dev/video0 >test.mpg' and you actually get a
> > file that's not just 0 bytes, then it's working fine.
> >
> > mplayer test.mpg can be used to play the file (without the right
> > frequency you probably get just static).
> >
> > 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
