Good to hear Ulf. After reading the ivtv website I thought I would do a reasonably safe thing and get a PVR-250MCE:
http://www.i-tech.com.au/products/1919_HAUPPAUGE_TV_TUNER_FOR_WINDOWS_XP_MEDIA.asp But what showed up was not really a PVR-250 as best as I can tell, but a PVR-150. Pics: http://www.slabathon.com/~matt/pvr250/ 0000:02:0e.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01) Subsystem: Hauppauge computer works Inc.: Unknown device 8801 Flags: bus master, medium devsel, latency 32, IRQ 209 Memory at f8000000 (32-bit, prefetchable) [size=64M] Capabilities: [44] Power Management version 2 ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.3.2 () loading ivtv: Linux version: 2.6.9n 386 gcc-3.3 ivtv: In case of problems please include the debug info ivtv: between the START INIT IVTV and END INIT IVTV lines when ivtv: mailing the ivtv-devel mailinglist. ivtv: Autodetected WinTV PVR 150 card ivtv: Found an iTVC16 based chip ACPI: PCI interrupt 0000:02:0e.0[A] -> GSI 22 (level, low) -> IRQ 209 ivtv: Unreasonably low latency timer, setting to 64 (was 32) ivtv: XXX PCI device: 0x1a30 vendor: 0x8086 tveeprom: Hauppauge: model = 26559, rev = C257, serial# = 7525161 tveeprom: tuner = Philips FM1216 ME MK3 (idx = 57, type = 38) tveeprom: tuner fmt = PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17) tveeprom: audio_processor = MSP3410D (type = 5) ivtv: i2c attach [client=tveeprom[0],ok] tuner: Ignoring new-style parameters in presence of obsolete ones tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 ivtv: i2c attach [client=(tuner unset),ok] cx25840: Ignoring new-style parameters in presence of obsolete ones cx25840: starting probe for adapter ivtv i2c driver #0 (0x10005) cx25840: detecting client on address 0x88 cx25840: writing init values ivtv: i2c attach [client=cx25840[0],ok] cx25840: status: (0x40C) 0x00 (0x40D) 0x81, (0x40E) 0x08 wm8775: Ignoring new-style parameters in presence of obsolete ones wm8775: starting probe for adapter ivtv i2c driver #0 (0x10005) wm8775: detecting client on address 0x36 wm8775: writing init values ivtv: i2c attach [client=wm8775[0],ok] ivtv: Encoder revision: 0x02040011 ivtv: Configuring WinTV PVR 150 card with 4 streams ivtv: Create DMA stream 0 using 256 16384 byte buffers 4194304 kbytes total ivtv: Registered v4l2 device, streamtype 0 minor 0 ivtv: Create DMA stream 1 ivtv: Registered v4l2 device, streamtype 1 minor 32 ivtv: Create stream 2 using 40 52224 byte buffers 2097152 kbytes total ivtv: Registered v4l2 device, streamtype 2 minor 224 ivtv: Create DMA stream 3 using 455 4608 byte buffers 2097152 kbytes total ivtv: Registered v4l2 device, streamtype 3 minor 24 ivtv: Could not detect tuner standard, defaulting to NTSC. tuner: tuner type not set cx25840: decoder set input (6) cx25840: now setting Composite input ivtv: Switching standard to NTSC. tuner: tuner type not set cx25840: decoder set norm NTSC cx25840: set audio: 0x01 ivtv: Initialized WinTV PVR 150, card #0 ivtv: ==================== END INIT IVTV ==================== Bastards! I'm thinking of just sending it back and getting a DVB-T card at this point. I know I can get one of those working under linux. Any ETA on your changes Ulf? Are they likely to work with my PAL PVR-150? Matt __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ ivtv-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
