[mythtv-users] Module loading errors with IVTV

Michael Janer michael at janernet.com
Tue Nov 11 13:48:39 EST 2003


I am using the 10-31-03 alpha drivers and I can compile the drivers fine.  It's just when I do a modprobe that I get a few error messages unrelated to my system which I can't figure out.  One is an error loading a bttv driver, and the other is a rivatv driver, both of which I don't have installed on my system, AFAIK
 
I am trying to get output working on my PVR 350
 
Here's the log of when I try to do the modprobe ivtv-fb:
 
[root at myth root]# tail -f /var/log/messages
Nov 12 01:01:38 myth modprobe: modprobe: Can't locate module sound-slot-1
Nov 12 01:01:39 myth modprobe: modprobe: Can't locate module sound-service-1-0
Nov 12 01:01:39 myth modprobe: modprobe: Can't locate module sound-slot-1
Nov 12 01:01:39 myth modprobe: modprobe: Can't locate module sound-service-1-0
Nov 12 01:01:49 myth gconfd (root-4278): starting (version 2.2.0), pid 4278 user
 'root'
Nov 12 01:01:50 myth gconfd (root-4278): Resolved address "xml:readonly:/etc/gco
nf/gconf.xml.mandatory" to a read-only config source at position 0
Nov 12 01:01:50 myth gconfd (root-4278): Resolved address "xml:readwrite:/root/.
gconf" to a writable config source at position 1
Nov 12 01:01:50 myth gconfd (root-4278): Resolved address "xml:readonly:/etc/gco
nf/gconf.xml.defaults" to a read-only config source at position 2
Nov 12 01:33:05 myth sshd(pam_unix)[9801]: authentication failure; logname= uid=
0 euid=0 tty=NODEVssh ruser= rhost=rayvns.rayva.org  user=root
Nov 12 01:33:08 myth sshd(pam_unix)[9801]: session opened for user root by (uid=
0)
Nov 12 01:38:03 myth kernel: i2c-core.o: i2c core module version 2.8.0 (20030714
)
Nov 12 01:38:03 myth kernel: Linux video capture interface: v1.00
Nov 12 01:38:03 myth kernel: [saa7127.c: INFO]: SAA7127 video encoder driver loa
ded
Nov 12 01:38:03 myth kernel: ivtv: SGarray_size = 200, DSGarray_size = 16
Nov 12 01:38:03 myth kernel: ivtv: Found an iTVC15 based chip
Nov 12 01:38:03 myth kernel: PCI: Found IRQ 11 for device 00:0f.0
Nov 12 01:38:03 myth kernel: tuner: probing ivtv i2c driver #0 i2c adapter [id=0
x10005]
Nov 12 01:38:03 myth kernel: tuner: chip found @ 0xc2
Nov 12 01:38:03 myth kernel: tuner(bttv): type forced to 2 (Philips NTSC (FI1236
,FM1236 and compatibles)) [insmod]
Nov 12 01:38:05 myth kernel: saa7127: Configuring encoder...<6>saa7114.c: starti
ng probe for adapter ivtv i2c driver #0 (0x10005)
Nov 12 01:38:05 myth kernel: saa7114.c: detecting saa7114 client on address 0x42
Nov 12 01:38:05 myth kernel: saa7115.c: writing init values
Nov 12 01:38:07 myth kernel: status: (1E) 0x89, (1F) 0xb1
Nov 12 01:38:07 myth kernel: msp34xx: init: chip=MSP3448W-A2, has NICAM support
Nov 12 01:38:07 myth kernel: msp3410: daemon started
Nov 12 01:38:10 myth kernel: ivtv: Encoder revision: 0x02040011
Nov 12 01:38:10 myth kernel: ivtv: Decoder revision: 0x02020023
Nov 12 01:38:10 myth kernel: ivtv: No mem on buf alloc!
Nov 12 01:38:10 myth kernel: ivtv: Buffer alloc failed!
Nov 12 01:38:10 myth kernel: ivtv: No mem on buf alloc!
Nov 12 01:38:10 myth kernel: ivtv: Buffer alloc failed!
Nov 12 01:38:10 myth kernel: ivtv: No mem on buf alloc!
Nov 12 01:38:10 myth kernel: ivtv: Buffer alloc failed!
Nov 12 01:38:10 myth kernel: ivtv: Registered v4l2 device, minor 0
Nov 12 01:38:10 myth kernel: ivtv: Registered v4l2 device, minor 32
Nov 12 01:38:10 myth kernel: ivtv: Registered v4l2 device, minor 224
Nov 12 01:38:10 myth kernel: ivtv: Registered v4l2 device, minor 16
Nov 12 01:38:10 myth kernel: lirc_dev: IR Remote Control driver registered, at m
ajor 61
Nov 12 01:38:10 myth kernel: bttv: driver version 0.7.104 loaded
Nov 12 01:38:10 myth kernel: bttv: using 4 buffers with 2080k (8320k total) for
capture
Nov 12 01:38:10 myth kernel: bttv: Host bridge is Intel Corp. 440LX/EX - 82443LX
/EX Host bridge
Nov 12 01:38:10 myth insmod: /lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/med
ia/video/bttv.o: init_module: No such device
Nov 12 01:38:10 myth kernel: bttv: Host bridge needs ETBF enabled.
Nov 12 01:38:10 myth insmod: Hint: insmod errors can be caused by incorrect modu
le parameters, including invalid IO or IRQ parameters.       You may find more i
nformation in syslog or the output from dmesg
Nov 12 01:38:10 myth insmod: /lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/med
ia/video/bttv.o: insmod bttv failed
Nov 12 01:38:10 myth modprobe: modprobe: Can't locate module rivatv
Nov 12 01:38:10 myth kernel: lirc_i2c: chip found @ 0x18 (Hauppauge IR)
Nov 12 01:38:10 myth kernel: lirc_dev: lirc_register_plugin:sample_rate: 10
Nov 12 01:38:10 myth kernel: ivtv: You've not seen the last of willy!
Nov 12 01:38:10 myth kernel: [saa7127.c: INFO]: SAA7127 video encoder driver unl
oaded
 
And here's my command line output:
 
[root at myth utils]# modprobe ivtv-fb
/lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/media/video/ivtv-fb.o: unresolve
d symbol ivtv_debug
/lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/media/video/ivtv-fb.o: unresolve
d symbol ivtv_pal
/lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/media/video/ivtv-fb.o: insmod /l
ib/modules/2.4.20-20_29.rh9.at/kernel/drivers/media/video/ivtv-fb.o failed
/lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/media/video/ivtv-fb.o: insmod iv
tv-fb failed
 
Any help would be appreciated, and thanks in advance.
 
mikejaner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20031111/7f1e66c8/attachment.htm


More information about the mythtv-users mailing list