[mythtv-users] unresolved symbols in libranet/debian with pvr350

[Dave W]

Things were so simple yesterday, with my cheezy winTV card - it Just Worked
<tm>.  Now, trying to get TV out with my new PVR 350 card, life is much more
complicated <g>.  Last night I had video on my X monitor using the 350, but
since then I've gobbed something up and can't even get mythbackend to work. 
About the only significant thing I've done is recompile the kernel with
framebuffer support...

I see two main problems right now and don't know where to go with them. 

Starting mythbackend:

# mythbackend
Starting up as the master server.
Channel::Open(): Can't open: /dev/video
/dev/video: No such device
Channel::Open(): Can't open: /dev/video
/dev/video: No such device
Couldn't find input: Composite 0 on card
2004-01-17 18:31:00 Enabled verbose msgs : important general

I +do+ have video devices:

l /dev/video
lrwxrwxrwx    1 root     video           6 Jan 16 22:00 /dev/video -> video0

l /dev/video0
crwxrwxrwx    1 root     video     81,   0 Jan 16 22:00 /dev/video0

...and so on all the way down to /dev/video63.

Trying to do the modules manually:

root at twosixsix:/home/aftech/ivtv/driver# modprobe i2c-core
root at twosixsix:/home/aftech/ivtv/driver# modprobe i2c-algo-bit
root at twosixsix:/home/aftech/ivtv/driver# modprobe tuner type=21
root at twosixsix:/home/aftech/ivtv/driver# modprobe msp3400
root at twosixsix:/home/aftech/ivtv/driver# modprobe videodev
root at twosixsix:/home/aftech/ivtv/driver# insmod saa7127.o
root at twosixsix:/home/aftech/ivtv/driver# insmod ivtv-fb.o
ivtv-fb.o: ivtv-fb.o: unresolved symbol ivtv_clear_irq_mask
ivtv-fb.o: ivtv-fb.o: unresolved symbol ivtv_debug
ivtv-fb.o: ivtv-fb.o: unresolved symbol ivtv_cards_active
ivtv-fb.o: ivtv-fb.o: unresolved symbol ivtv_api
ivtv-fb.o: ivtv-fb.o: unresolved symbol ivtv_pal
ivtv-fb.o: ivtv-fb.o: unresolved symbol ivtv_cards

Output of /var/log/messages during this time:

# tail -f /var/log/messages
Jan 17 18:01:07 twosixsix kernel: i2c-algo-bit.o: i2c bit algorithm module
Jan 17 18:01:07 twosixsix kernel: bttv: driver version 0.7.107 loaded
Jan 17 18:01:07 twosixsix kernel: bttv: using 4 buffers with 2080k (8320k
total) for capture
Jan 17 18:01:07 twosixsix kernel: bttv: Host bridge is Intel Corp. 82845G/GL
[Brookdale-G] Chipset Host Bridge
Jan 17 18:01:07 twosixsix kernel: Linux video capture interface: v1.00
Jan 17 18:01:07 twosixsix kernel: i2c-core.o: i2c core module
Jan 17 18:01:07 twosixsix kernel: i2c-algo-bit.o: i2c bit algorithm module
Jan 17 18:01:07 twosixsix kernel: bttv: driver version 0.7.107 loaded
Jan 17 18:01:07 twosixsix kernel: bttv: using 4 buffers with 2080k (8320k
total) for capture
Jan 17 18:01:07 twosixsix kernel: bttv: Host bridge is Intel Corp. 82845G/GL
[Brookdale-G] Chipset Host Bridge
Jan 17 18:25:53 twosixsix kernel: i2c-core.o: i2c core module
Jan 17 18:26:03 twosixsix kernel: i2c-algo-bit.o: i2c bit algorithm module
Jan 17 18:26:11 twosixsix kernel: i2c-core.o: driver i2c TV tuner driver
registered.
        Jan 17 18:26:31 twosixsix kernel: i2c-core.o: driver i2c msp3400
driver registered.
Jan 17 18:26:44 twosixsix kernel: Linux video capture interface: v1.00
Jan 17 18:27:06 twosixsix kernel: [saa7127.c: INFO]: SAA7127 video encoder
driver loaded
Jan 17 18:27:06 twosixsix kernel: i2c-core.o: driver saa7127 registered.

It's those doggone unresolved symbols.  I'm not a coder, so this doesn't
mean a thing to me.  I'm assuming that doing all of this as root I should
have no permissions issues, but I have added my regular user and root both
to the mythtv group just to see if it helped, and it didn't.

I got ivtv from a tarball, and mythtv from a debian package via:

deb http://dijkstra.csh.rit.edu/~mdz/debian unstable mythtv

My BIGGEST problem at this point is I'm not comfortable enough with CVS
and/or with playing with drivers/modules to know what I'm doing, and the
various pages I've found for TV-Out and mythtv for Debian assume this
knowledge.  So I don't have the bleeding edge CVS version of ivtv, in case
that would help, and am not positive I have the modules "done" right.

Here's hoping this long message won't go ignored :)

david williamson