Each module that was loaded into the kernel had the following warning message: "module not supported by Novell, setting U taint flag." This could possibly imply that you need to use a vanilla kernel instead of the default one that came with your distro.
However, this is more a warning message than an error message. What steps did you take to verify that the drivers are not working correctly? Please elaborate.
-Rob
On 5/11/06,
Thomas Peter <[EMAIL PROTECTED]> wrote:
Hello,
i tried to install my PVR 250 with the latest ivtv drivers(0.4.5).
I am running Suse 10.0 (Kernel 2.6.13-15.8).
I followed the howto on ivtvdrivers.org, but the card wont work....plzzz help me :-)
this is the output of dmesg:
ivtv: module not supported by Novell, setting U taint flag.
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.4.5 (tagged release) loading
ivtv: Linux version: 2.6.13-15.8-default 586 REGPARM gcc-4.0
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 250 card (cx23416 based)
ACPI: PCI Interrupt Link [LNK2] enabled at IRQ 11
ACPI: PCI Interrupt 0000:01:09.0[A] -> Link [LNK2] -> GSI 11 (level, low) -> IRQ
11
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
ohci_hcd 0000:00:02.1: wakeup
tveeprom: module not supported by Novell, setting U taint flag.
tveeprom: ivtv version
tveeprom: Hauppauge: model = 32054, rev = B148, serial# = 7159978
tveeprom: tuner = LG TP18PSB11D (idx = 48, type = 29)
tveeprom: tuner fmt = PAL(B/G) (eeprom = 0x04, v4l2 = 0x00000007)
tveeprom: audio processor = MSP4418 (type = 19)
tveeprom: decoder processor = SAA7115 (type = 13)
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
ieee1394: Initialized config rom entry `ip1394'
ohci1394: $Rev: 1299 $ Ben Collins <[EMAIL PROTECTED]>
ACPI: PCI Interrupt Link [LNK4] enabled at IRQ 5
ACPI: PCI Interrupt 0000:01: 08.2[B] -> Link [LNK4] -> GSI 5 (level, low) -> IRQ
5
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[5] MMIO=[df004000-df0047ff] Max
Packet=[2048]
ACPI: PCI Interrupt Link [LNK3] enabled at IRQ 11
ACPI: PCI Interrupt 0000:01:08.0[A] -> Link [LNK3] -> GSI 11 (level, low) -> IRQ
11
tuner: module not supported by Novell, setting U taint flag.
tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
saa7115: module not supported by Novell, setting U taint flag.
saa7115 2-0021: ivtv driver
saa7115 2-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21]
msp3400: module not supported by Novell, setting U taint flag.
msp3400 2-0040: ivtv driver
msp3400 2-0040: chip=MSP4418G-A2 +nicam +simple +simpler +radio mode=simpler
ivtv0: i2c attach to card #0 ok [client=MSP4418G-A2, addr=40]
msp3400 2-0040: msp34xxg daemon started
tda9887: module not supported by Novell, setting U taint flag.
oto 2 vid 0x04A9 pid 0x107F
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: 161 x 12960 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
tuner: type set to 29 (LG PAL_BG (TPI8PSB11D)) by ivtv i2c driver #0
ivtv0: Initialized WinTV PVR 250, card #0
ivtv: ==================== END INIT IVTV ====================
Thx for any ideas...
Tom
_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
--
-Rob
As seen on bash.org:
The problem with America is stupidity. I'm not saying there
should be a capital punishment for stupidity, but why don't
we just take the safety labels off of everything and let
the problem solve itself?
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
