xawtv

Thu Apr 3 17:54:43 EST 2003

Well, I'm *still* in over my head.  Help would be appreciated!

As you pointed out, Mandrake loads usbvision as a module/driver for my
WINTV.
I went to:
http://usbvision.sourceforge.net/index.php?page=documentation

and it appears that Mandrake did about half of what I need.  In the
following, I will assume that you have (or hopefully, will<G>) taken a look
at the above URL so I won't repeat its contents.
I edited /usr/include/linux/videodev.h and added the line
#define VID_HARDWARE_USBVISION 36
(I know this won't do anything unless I compile something that references
it.)
I verified that /dev/video and /dev/video0 exist and have the proper
permissions.
I did a find / -name tuner.o and came up empty handed.
It seems to want BT848 support (whatever that is!) or something else that
will give me a tuner.o file.
I didn't see any file called BT848*, but I may not know where to look.
Also, I reviewed my lsmod and see that while usb-uhci is loaded, ohci-hcd is
not.

So, I need a tuner module and I need someone to review the install
instructions and suggest what I should try next.

Oh, and one small weirdness:  When I run xawtv, a new icon appears on my
desktop for GTKam video1.  When I select it, it wants to configure a webcam,
but when I select autodetect, it doesn't find one. I do have a usb camera
(Ezonics) hooked up to my usb hub, but so far, everything seems to have
ignored it.  It's real low on my priority list of things to get working.   I
just wanted you to know it's there in case it's confusing the issue.

Joe

----- Original Message -----
From: "Robert Meyer" <meyer_rm at yahoo.com>
To: <nflug at nflug.org>
Sent: Saturday, March 29, 2003 6:16 PM
Subject: Re: xawtv

> Nope, you don't want bttv loaded.  Looks to me like you have a video
> module called usbvision loaded.  That is the device that we want to
> work with.  I did a little poking around in google and found a bunch
> of pages about this thing.
>
> I need all of the information from the 'lsmod' command.  I need to
> know if the module 'tuner' is loaded.
>
> The reason that you couldn't remove the i2c modules is that they are
> used by the 'usbvision' module.  It looks like you're very close to
> having it work.  We may need to add a 'tuner type=x' type flag where
> the 'x' is the tuner type number to the /etc/modules.conf file.
>
> Peter, what was the option that we put in your machine for the tuner?
>
> Cheers
>
> Bob
> --- Joe <josephj at main.nc.us> wrote:
> > Still haven't quite got it.
> >
> > Looked at dmesg:
> >
> > hub.c: new USB device 00:07.2-2.1, assigned address 3
> > usb.c: USB device 3 (vend/prod 0x4a7/0x201) is not claimed by any active
> > driver.
> > hub.c: new USB device 00:07.2-2.2, assigned address 4
> > usb.c: USB device 4 (vend/prod 0x573/0x4d00) is not claimed by any
active
> > driver.
> > hub.c: new USB device 00:07.2-2.3, assigned address 5
> > usb.c: USB device 5 (vend/prod 0x572/0x1) is not claimed by any active
> > driver.
> > i2c-core.o: i2c core module version 2.7.0 (20021208)
> > i2c-algo-usb.o: i2c usb algorithm module
> > Linux video capture interface: v1.00
> > usb.c: registered new driver usbvision
> > usbvision: HAUPPAUGE WINTV-USB USA found
> > i2c-algo-usb.o: hw routines for usbvision #0 registered.
> >
> > /etc/modules.conf: (I added the bttv line)
> >
> > probeall scsi_hostadapter ide-scsi
> > alias eth0 tulip
> > alias sound-slot-0 es1371
> > probeall usb-interface usb-uhci
> > alias eth1 3c59x
> > options bttv tuner=1
> >
> > lsmod shows:
> >
> > usbvision              77872   0
> > videodev                7872   1 [usbvision]
> > i2c-algo-usb            2844   1 [usbvision]
> > i2c-core               21192   0 [i2c-algo-usb]
> > usb-uhci               24652   0 (unused)
> > usbcore                72992   1 [usbvision usb-uhci]
> >
> > Then I tried the rmmod:
> >
> > [root at localhost bigbird]# rmmod -vr i2c-algo-usb i2c-core
> > rmmod: i2c-algo-usb is in use
> > rmmod: i2c-core is in use
> >
> > I think I got the same thing when I reversed the order of modules in the
> > command.  I notice that the activity led on the USBTV is lit.
> >
> > I tried rebooting with the TV unplugged.  The i2c modules went away as
> > expected, but I didn't know what to do next.  depmod -a didn't do
anything
> > visibe, because there wasn't any video stuff loaded.
> >
> > I think what I need to do next is put the modprobe bttv in an init
script
> > somewhere so it gets there before the i2c stuff is loaded.
> >
> > Did I miss something?  What do I try next?
> >
> > Thanks.  Joe
> >
> > ----- Original Message -----
> > From: "Robert Meyer" <meyer_rm at yahoo.com>
> > To: <nflug at nflug.org>
> > Sent: Monday, March 24, 2003 7:44 PM
> > Subject: Re: xawtv
> >
> >
> > > Hmmm... Methinks you need to tell the tuner driver what tuner module
you
> > > have.  I think that the thing needs something like:
> > > options bttv tuner=1
> > > or some such in /etc/modules.conf.  Take a look at /var/log/messages
or
> > run
> > > the 'dmesg' command and look for references to the video device to
find
> > > out what the type is.  I suspect that all Hauppauge devices use bt878
> > > type video devices but the tuner has to be identified.  I think that
there
> > > are something like 8 of them.  After you make the change, you need to
> > > 'rmmod' the 'i2c-core' device and everything listed to the right of it
> > > when you do an 'lsmod'.  You will need to edit /etc/modules.conf to
add
> > the
> > > line, type 'depmod -a', remove the modules and then do a 'modprobe
bttv'.
> > > You may have to try several 'tuner=' numbers until you get it.
> > >
> > > Hope this helps...
> > >
> > > Cheers!
> > >
> > > Bob
> > > --- Joe Pollock <josephj at buffnet.net> wrote:
> > > > Thanks to Bob Meyer, I now have Mandrake 9.1 rc 2 on my machine!
I'm
> > > > working on getting xawtv to work with my Hauppauge WINTV USB.  The
> > program
> > > > runs, but has no channels to select and displays a black screen.
When I
> > run
> > > > the companion program - scantv - which sets up the channel list for
> > xawtv,
> > > > it starts up, asks a few initial questions and then fails with the
> > following
> > > > message:
> > > >
> > > > vbi: open failed [/dev/v41/vbi0]
> > > > /dev/v41/vbi0 no such file or directory
> > > >
> > > > I checked, it doesn't exist.  /dev/v41/ is there.
> > > >
> > > > I did a quick Google search and found some stuff on /dev/vbi, but
> > nothing
> > > > with a v41 in it.
> > > >
> > > > Any ideas on how to fix this or what driver it needs?
> > > >
> > > > Thanks,
> > > >
> > > > Joe
> >
>
>
> =====
> Bob Meyer
> Knightwing Communications, Inc.
> 36 Cayuga Blvd
> Depew, NY 14043
> Phone: 716-308-8931 or 716-681-0076
> Meyer_RM at Yahoo.com
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
> http://platinum.yahoo.com