Nevermind, I found it, a failed process in the background had a lock on it.. :$
On Wed, Nov 19, 2008 at 12:36 AM, Al McIntosh <[EMAIL PROTECTED]> wrote: > Has anyone run into this issue before trying to test the hvr 1600? > > cat /dev/video0 > out.mpg > cat: /dev/video0: Device or resource busy > > > dmesg|grep cx18 > [ 11.159274] cx18: Start initialization, version 1.0.2 > > [ 11.159324] cx18-0: Initializing card #0 > [ 11.159329] cx18-0: Autodetected Hauppauge card > [ 11.159727] cx18 0000:01:08.0: PCI INT A -> Link[APC3] -> GSI 18 (level, > low) -> IRQ 18 > [ 11.159737] cx18-0: Unreasonably low latency timer, setting to 64 (was 32) > > [ 11.162638] cx18-0: cx23418 revision 01010000 (B) > [ 11.420693] cx18-0: Autodetected Hauppauge HVR-1600 > [ 11.420695] cx18-0: VBI is not yet supported > [ 11.624599] tuner 3-0061: chip found @ 0xc2 (cx18 i2c driver #0-1) > > [ 11.624647] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0) > [ 12.833874] cx18-0: Disabled encoder IDX device > [ 12.834026] cx18-0: Registered device video0 for encoder MPEG (2 MB) > [ 12.834030] DVB: registering new adapter (cx18) > > [ 13.494761] cx18-0: DVB Frontend registered > [ 13.494825] cx18-0: Registered device video32 for encoder YUV (2 MB) > [ 13.494882] cx18-0: Registered device video24 for encoder PCM audio (1 MB) > [ 13.494886] cx18-0: Initialized card #0: Hauppauge HVR-1600 > > [ 13.495451] cx18: End initialization > [ 33.337294] cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000 (141200 > bytes) > [ 33.951668] cx18-0: loaded v4l-cx23418-cpu.fw firmware (158332 bytes) > [ 33.957827] cx18-0: FW version: 0.0.74.0 (Release 2007/03/12) > > [ 35.319069] cx18-0: loaded v4l-cx23418-dig.fw firmware (16382 bytes) > > > > >
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
