Chris,

lspci -v

01:0a.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
        Subsystem: Hauppauge computer works Inc.: Unknown device c801
        Flags: bus master, medium devsel, latency 64, IRQ 11
        Memory at e4000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [44] Power Management version 2

lspci -vn

01:0a.0 Class 0400: 4444:0016 (rev 01)
        Subsystem: 0070:c801
        Flags: bus master, medium devsel, latency 64, IRQ 11
        Memory at e4000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [44] Power Management version 2

tveeprom

tveeprom: Hauppauge: model = 25012, rev = B158, serial# = 7751595
tveeprom: tuner = Philips FM1236 MK3 (idx = 58, type = 43)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
tveeprom: audio_processor = MSP3410D (type = 5)
ivtv: i2c attach [client=tveeprom[50],ok]

This is PVR150 MCE LP NTSC

On Wed, 2005-04-13 at 08:52 -0500, Chris Kennedy wrote:
Ah, yeah it's hard to find, but actually typing 'modinfo ivtv'  (which is
for some reason a little known command in Linux modules), you get...

Specify card type:
                1 = WinTV PVR 250
                2 = WinTV PVR 350
                3 = AVerMedia M179
                4 = YUAN MPG600/Kuroutoshikou iTVC16-STVLP
                5 = YUAN MPG160/Kuroutoshikou iTVC15-STVLP
                6 = WinTV PVR-150 or PVR-500
                7 = YUAN PG600/DIAMONDMM PVR-550 (CX Falcon 2)
                Default: Autodetect


But still really need the dmesg logs of startup to fix that, so it
autodetects properly (or a lspci -vn output on your system, probably
both actually), then I can fix it for everyone :-).

Thanks,
Chris 
On Wed, Apr 13, 2005 at 09:38:47AM -0400, Sergey Alexandrov wrote:
> Ye, got it. But nowhere in documentation I can find cardtype=6 option
> for 
> PVR150. Just found it in the source ;)
> 
> On Wed, 2005-04-13 at 08:16 -0500, Chris Kennedy wrote:
> 
> > It defaults to that now again because it originally did, and the
> > manual
> > config through module arguments were off and depended on the order to 
> > start with the 250.  What are the log messages, sounds like it isn't
> > autodetecting the pvr500 correctly, but should spit out the vender and
> > subvender/device id's.
> > 
> > 
> > Thanks,
> > Chris

Reply via email to