On Wednesday 09 March 2005 20:20, William wrote: > > I have installed ivtv doing the following: > > > > # apt-get install ivtv-firmware > > # apt-get install ivtv-kmdl-$KVER > > # apt-get install ivtv > > > > Then put the following into /etc/modprobe.conf: > > > > # ivtv modules setup > > alias char-major-81 videodev > > alias char-major-81-0 ivtv > > alias tveeprom tveeprom-ivtv > > > > I run these commands: > > > > # /sbin/depmod -a > > # /sbin/modprobe ivtv > > > > Which run with no errors. Then checking I run: > > > > # /sbin/lspci -v > > > > Which yields: > > > > 00:09.0 Multimedia video controller: Internext Compression Inc iTVC16 > > (CX23416)MPEG-2 Encoder (rev 01) > > Subsystem: Hauppauge computer works Inc. WinTV PVR 250 > > Flags: medium devsel, IRQ 10 > > Memory at 30000000 (32-bit, prefetchable) [size=64M] > > Capabilities: [44] Power Management version 2 > > > > Which worries me because I don't see the bus master and the latency > > flags that are in the results for both Jared's FC3 guide and > > the mythtv > > docs... but continuing...
Check your BIOS, make sure Bus Mastering is on. Might also try moving the card
to a different slot. Somewhere around here, I have some info on how to force
bus mastering on via the Linux cli, if your BIOS doesn't provide the option.
> > I then run and get:
> >
> > # ll /dev/video?
> > ls: /dev/video: No such file or directory
> > # /bin/dmesg |grep Initialized
> > ieee1394: Initialized config rom entry `ip1394'
> >
> > Which is not "ivtv: Initialized WinTV PVR 250, card #0" that
> > I hoped it
> > would be.
Please use the tac commands shown in my doc to rip out all the pertinent ivtv
info from your logs and send it to the ivtv mailing list.
> If this is on a FC3 distro its exactly the problem I ran into. If you look
> further down the dmesg output you will probably find an error message and
> the ivtv load process aborts. I personally was not able to resolve this and
> ended up going back to FC2 which plays perfectly.
I may well have missed it, but I don't recall seeing your log output between
the ivtv start and stop markers in /var/log/messages sent to the ivtv list,
which I what I suggest to (and what the ivtv developers request of) people
when they hit a major snag with ivtv.
> Good luck with it. My
> suggestion (which is sure to piss off the linux guru's) is to go with the
> older release.
A better suggestion is for us to get to the bottom of why this is happening. I
have several Fedora Core 3 boxes with ivtv cards, all of which load up ivtv
just fine (including a PVR-150 and a PVR-500 now). This is the first time
I've seen details on this problem, that I can recall (I was busy and not very
available on the list for a while, so I may have missed some prior postings
of yours, William).
> FC3 = Windows ME
That's a rather unkind comparison.
--
Jarod Wilson
[EMAIL PROTECTED]
Got a question? Read this first...
http://catb.org/~esr/faqs/smart-questions.html
MythTV, Fedora Core & ATrpms documentation:
http://wilsonet.com/mythtv/
MythTV Searchable Mailing List Archive
http://www.gossamer-threads.com/lists/mythtv/
pgpcWkttUN2qf.pgp
Description: PGP signature
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
