On Monday 28 February 2005 20:03, Winston Chang wrote:I have a PVR-500MCE (NTSC) that gives the exact same tveeprom output, except that my serial# is 7749933. �It's not working for me -- all I get is static on both video0 and video1; playing around with tuner 0 and 1 doesn't seem to do anything.
Here's what I did: - I'm using - I applied the megapatch and the tveeprom patch (I haven't done the patch to the v4l sources since I want to do the simple thing first) - make - insmod tveeprom.ko - insmod tuner.ko - insmod cx25840.ko - insmod ivtv.ko ivtv_std=1,1 tuner=55,55
I ran insmod on the modules instead of modprobe because, even after a
make install, it didn't seem to load the new tuner module properly (I
think it was still using the kernel version): I would get a "tuner type
not set".
Am I doing something wrong?
I'm not sure if you're getting all the required modules loaded if you're using
insmod instead of modprobe. One thing to try that I'm doing is add
"no_black_magic=1 audiofmt=1" as options to cx25840. If its still not working
at that point, get a full log dump and we'll see if something stands out.
OK, this is my FIFTH try sending this -- I guess my logfile attachment was too big in previous posts, because the mail just went into a black hole. I removed some extra log stuff and tried sending again, but it vanished again. I removed some extra info, like the date, time, and machine name and tried sending again, but sent it from the wrong address so it was awaiting moderation. Then I sent it AGAIN from the right address but it still awaits moderation because the attachment pushed the message size to 22k, which is above the 20k limit. And it's been sitting there for hours so I'm just going to send this message without the log attachment. Can you tell I'm frustrated?
It's very annoying that the message size limit is smaller than the size of the log data that often needs to be posted to this board. Also, the fact that large messages (like the first two I sent) just disappear instead of triggering some sort of notification is just wrong behavior. Can the message size limit be increased to something more practical?
Anyway... ---------------------------
Still no go. Here's what I've done:
I'm using FC3 with my 2.6.10-1.760-no4kstacks kernel. I'm using ivtv-0.3.2e, with the megapatch and the tveeprom patch (no v4l patch for me just yet).
- make
- make install
- I moved the kernel version of tuner.ko out of the way and replaced it with the new one.
- I added the following to my modprobe.conf:
---- modprobe.conf ----
alias char-major-81-0 ivtv
options ivtv ivtv_std=1,1 tuner=55,55
options cx25840 i2c_enable=1 no_black_magic=1 cardtype=1 audiofmt=1
------------------------
- modprobe tveeprom
- modprobe ivtv
With tuner 55 (the log says Philips FQ1236A MK4), I get nothing but color noise on both tuners. Changing channels with ptune-ui.pl did nothing at all. Jason advised me over email to try tuner 54 (with which the log says Philips FQ1286), and when I made this change I got b+w static on some channels, and red screens on others -- I couldn't get any real video, but the tuner did seem to do something, with the "wrong" tuner.
kernel: tveeprom: Hauppauge: model = 23552, rev = D292, serial# = 7749933
kernel: tveeprom: tuner = Philips FQ1236A MK4 (idx = 92, type = 55)
kernel: tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
kernel: tveeprom: audio_processor = MSP3410D (type = 5)
Thanks for helping get to the bottom of this!
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
