I'm running slackware 10.2. Another note: during installation, there's a part that talks about moving and renaming .ko files. I never did find a single ko file on my whole system.
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.4.6 (tagged release) loading
ivtv: Linux version: 2.4.31
ivtv: In case of problems please include the debug info between
ivtv: the START INIT IVTV and END INIT IVTV lines, along with
ivtv: any module options, when mailing the ivtv-users mailinglist.
ivtv0: Autodetected WinTV PVR 150 card (cx23416 based)
PCI: Found IRQ 11 for device 02: 0a.0
PCI: Sharing IRQ 11 with 00:1f.2
i2c-core.o: adapter ivtv i2c driver #0 registered as adapter 0.
i2c-core.o: driver tveeprom registered.
tveeprom: ivtv version
tveeprom: Hauppauge: model = 26552, rev = C268, serial# = 8330483
tveeprom: tuner = LG TAPE H001F MK3 (idx = 68, type = 47)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
tveeprom: audio processor = CX25843 (type = 25)
tveeprom: decoder processor = CX25843 (type = 1e)
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
i2c-core.o: client [tveeprom] registered to adapter [ivtv i2c driver #0](pos. 0).
i2c-core.o: driver i2c TV tuner driver registered.
tuner: chip found @ 0xc2
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
i2c-core.o: client [(tuner unset)] registered to adapter [ivtv i2c driver #0](pos. 1).
i2c-core.o: driver cx25840 registered.
cx25840 0-0044: ivtv driver
cx25840 0-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 0-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44]
i2c-core.o: client [cx25840] registered to adapter [ivtv i2c driver #0](pos. 2).
i2c-core.o: driver wm8775 registered.
wm8775 0-001b: ivtv driver
wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b]
i2c-core.o: client [wm8775] registered to adapter [ivtv i2c driver #0](pos. 3).
i2c-core.o: driver i2c tda9887 driver registered.
tda9887: chip found @ 0x86
ivtv0: i2c attach to card #0 ok [client=tda9887, addr=43]
i2c-core.o: client [tda9887] registered to adapter [ivtv i2c driver #0](pos. 4).
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02050032
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
ivtv0: Create encoder radio stream
ivtv0: Initialized WinTV PVR 150, card #0
ivtv: ==================== END INIT IVTV ====================
And here's a chunck of my syslog...
Aug 6 05:29:34 slacker insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
Aug 6 05:29:34 slacker insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Aug 6 05:29:34 slacker insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
Aug 6 05:29:34 slacker kernel: i810_rng: RNG not detected
Aug 6 05:29:34 slacker insmod: /lib/modules/2.4.31/kernel/drivers/char/i810_rng.o.gz: init_module: No such device
Aug 6 05:29:34 slacker insmod: /lib/modules/2.4.31/kernel/drivers/char/i810_rng.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Aug 6 05:29:34 slacker insmod: /lib/modules/2.4.31/kernel/drivers/char/i810_rng.o.gz: insmod i810_rng failed
Aug 6 05:29:34 slacker kernel: hw_random: RNG not detected
Aug 6 05:29:34 slacker insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: init_module: No such device
Aug 6 05:29:34 slacker insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Aug 6 05:29:34 slacker insmod: /lib/modules/2.4.31/kernel/drivers/char/hw_random.o.gz: insmod hw_random failed
Aug 6 05:29:34 slacker kernel: shpchp: shpc_init : shpc_cap_offset == 0
Aug 6 05:29:34 slacker kernel: shpchp: shpc_init : shpc_cap_offset == 0
Aug 6 05:29:34 slacker insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
Aug 6 05:29:34 slacker insmod: /lib/modules/2.4.31/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module
Any tips would be appreciated. Should I have ko files?
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
