On Mon, 2008-10-13 at 14:00 -0400, Jeff Campbell wrote: > Hello everyone, > > I'm new to the cx18 driver, but familiar with the ivtv family. > > I am building a new system that has two HVR-1600s in it. The > motherboard is a Via C7 based board with a dual PCI riser. It has 1GB > of memory. > > I am running a custom built 2.6.27 (final) kernel with the cx18 and > ivtv drivers built in. > > After adding vmalloc=192M to my kernel boot line, both cards appear to > initialize properly: > > Here is my dmesg output segment: > > cx18: Start initialization, version 1.0.0 > cx18-0: Initializing card #0 [snip] > cx18-1: Initialized card #1: Hauppauge HVR-1600 > cx18: End initialization > > After boot, I can talk to and utilize /dev/video0 relatively normally > (I am getting a slight jerkiness in watching video off /dev/video0 but > I can investigate that one later).
I know some of the cause here. For now, you'll have to be satisfied with buffered playback. Use the -cache 16384 command line option option for mplayer or use MythTV which always buffers. > cat /dev/video0 > sample.mpg > > Yields the firmware load info in /var/log/messages as well as a file > with a size greater than zero > est.mpg > Good. > However, if I try > > cat /dev/video1 > test1.mpg > > I get zero length file > > -rw-r--r-- 1 root root 0 Oct 13 17:46 test1.mpg At first glance, I'd say you're not getting interrupts for some reason. PLease provide the output of # cat /proc/interrupts after the failed attempt. You may also wish to load the cx18 module with some of the debug flags enabled. Namely the flags for info, warn, mailbox, & irq. See the output of modinfo cx18 for details on how to set them. > If I try and do the cat test again, I get: > > enc239-009-060:~# cat /dev/video1 > test1.mpg > cat: /dev/video1: Input/output error Hmm. I got something like this only once or twice, when mailbox debug messaging showed somethings happening out of order. Please send the debug messages I mentioned above if you can reproduce this. > Here is the output of > > lspci -vv > > (after the failed attempts) > > enc239-009-060:~# cat pcilog.txt > 00:00.0 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro > Host Bridge > Subsystem: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro > Host Bridge > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium > >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx- > Latency: 8 > Region 0: Memory at f8000000 (32-bit, prefetchable) [size=32M] > Capabilities: [80] AGP version 3.5 > Status: RQ=8 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- > HTrans- 64bit- FW- AGP3+ Rate=x4,x8 > Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- > FW- Rate=<none> > Capabilities: [50] Power Management version 2 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA > PME(D0-,D1-,D2-,D3hot-,D3cold- > ) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- Nothing too unusual that I see. The host bridge is showing a Master Abort, which typically happens on the bridge device the CX23418 is behind (which both of yours are in this case). The host bridge latency timer of 8 seems odd - it's a little low. Regards, Andy _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
