After a lot of fiddling, I finally got it working. :-)
As it turned out, the problem wasn't ivtv-related at all, but came from my
lack of knowledge about how kernel modules are loaded.
At some point during the gathering of mailing list tips, I had inserted
ivtv and ivtv-fb into /etc/modules so th
first guess alsa? mute is on by default
On Wed, 19 Jan 2005 21:03:20 -0500, John Hare <[EMAIL PROTECTED]> wrote:
> Er, yes. I'll assume that means to try a newer version of ivtv. Fair
> enough. I did that and sure enough, I can capture video. Thanks. Of
> course, I don't seem to have au
Er, yes. I'll assume that means to try a newer version of ivtv. Fair
enough. I did that and sure enough, I can capture video. Thanks. Of
course, I don't seem to have audio. I'm not sure if I should try to
play it to the TV and see if that works before I get worried about it.
On Wed, 19 Jan
> Well, it sounded good... but eeprom isn't even
> loaded. And tveeprom
> IS loaded. So neither of the "suggestions" from the
> error message are
> useful. Any other ideas?
yes. read the thread:
>> type 'modprobe tveeprom'
>>
>> then type 'dmesg'
>>
>> last few lines of output will
>> ha
Ronald, thanx for your reaction...
I've checked dmesg once I've tuned into a working channel. (see dmesg
output below)
It turns out that the audio is stereo in the sense that it is two
channel. My sound card is connected to a dolby prologic amplifier that
derives 5.1 sound from incoming 2 chann
Well, it sounded good... but eeprom isn't even loaded. And tveeprom
IS loaded. So neither of the "suggestions" from the error message are
useful. Any other ideas?
On Wed, 19 Jan 2005 09:10:45 -0800 (PST), kevin thayer
<[EMAIL PROTECTED]> wrote:
> Actually, it looks like you may have a new-enou
hi,
i have got all working remote and the tuner, the sound...
thanx to this maillist for helps :)
but i need to use a trick to get all working...
---
cat /etc/modules.d/ivtv
-
Hi,
I know you guys have put loads of work in on this and it's much
appreciated by everyone on this list I'm sure, Has anyone got any idea
on this?
I've now taken out the PVR250 card, because I thought it was some weird
interaction between the two cards, but I've now managed to get the
problem with
OK, this make sense. I suspected that error was in some way
responsible. But since I installed with apt-get, I didn't know what had
been done to monkey things up.
Do I not need eeprom at all? I think I heard something to the effect
that it will be loaded by ivtv automatically, so perhaps if
Anyway, I loaded the wrong msp3400 driver. When using the msp3400-ivtv.ko
module
sound works. Failure to RTFM on my part, sorry for the spam. Here's hoping for
trouble free recordings!
---
This SF.Net email is sponsored by: IntelliVIEW -- I
tveeprom reads the hauppauge chip which describes the
hardware on the card. Tuners have no way of
identifying themselves via i2c (generally speaking) so
this is needed to tell what sort of tuner you have.
tveeprom was based on an exsiting module called
eeprom, which does something similar, but is
does tveeprom print out any tuner information?
'rmmod tveeprom;modprobe tveeprom;dmesg'
this error:
> ivtv: i2c client addr: 0x50 not found!
makes me think there's some sort of problem reading
the eeprom. perhaps yours has a different i2c addr?
try loading i2c manually:
modprobe i2c-core
modp
hi,
i have got all working remote and the tuner, the sound...
thanx to this maillist for helps :)
but i need to use a trick to get all working...
---
cat /etc/modules.d/ivtv
-
Actually, it looks like you may have a new-enough
version of ivtv, and you loaded the eeprom module
before tveeprom. see this error from your post:
Jan 18 20:22:18 localhost kernel: ivtv: Error -19
reading Hauppauge eeprom.
Jan 18 20:22:18 localhost kernel: ivtv: Possible
causes: the tveeprom modu
type 'modprobe tveeprom'
then type 'dmesg'
last few lines of output will have the information you
need:
here's mine:
tveeprom: Hauppauge: model = 32552, rev = B123,
serial# = 6947765
tveeprom: tuner = Philips FM1236 (idx = 23, type = 2)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 =
0x000
I used Jarod's instructions to install mythtv with apt-get. I do not seem to
have either eeprom or tveeprom modules on the system. here is an lsmod, and
all I get is static on all channels, I eliminated the physical connection as
the problem as the card works under windows and the cable works on
How do I load the tveeprom module?
kevin thayer wrote:
you don't have any tuner type set (or detected)
load the tveeprom module
it will tell you which tuner types to set
you can set the tuner type with the 'tuner' option to
ivtv
ie
modprobe ivtv tuner=2,37
for first card tuner type 2, second card
you don't have any tuner type set (or detected)
load the tveeprom module
it will tell you which tuner types to set
you can set the tuner type with the 'tuner' option to
ivtv
ie
modprobe ivtv tuner=2,37
for first card tuner type 2, second card tuner type 37
newer versions of ivtv will detect
> >I am trying to install an PVR-150MCE in a box where i 've got a
> >PVR-350 running. The PVR-150 seems to initialise well but I am unable
> >to get any output from it.
> >When running cat /dev/video1 > test.mpg I get a 0kb file. Someone has
> >an idea what is going wrong?
> >
> >...
> >ivtv: vers
I was going along with the Fedora Myth(TV)ology HowTo and hit a wall
at the "test the capture card" step. That being, I can't seem to
capture anything but static. Looks exactly like the static on a TV
with no cable hooked in (assuming it's not a newer TV that just shows
a blue screen). I actuall
20 matches
Mail list logo
