On Wednesday 02 March 2005 19:47, Rob Comstock wrote:
> I have a system with the 250 MCE card and a 150 retail card. A remote is on
> the 150 and I would like to use the radio input on the 250.
>
> The latest incarnation of 0.3.2f has severely degraded the tuning on my
> pvr-250 MCE. Channels over
On Wednesday 02 March 2005 15:25, greg wrote:
> The tuner module is from kernel 2.6.7. ivtv is 0.2.0_rc3-r1 . ÂI have
> include the log lines as an attachment.
I forget, is that the one that knows about type 47?
You can tell by reading the source, its fairly easy to find.
If not try forcing type
Just as another data point I have use a dell with 2.8GHz P4 with HT
and it works fine with a pvr350 and pvr250 with mythtv 0.17.
Here are some output with dmesg.
ivtv: version 0.2.0 (rc3f) loading
ivtv: Linux version: 2.6.10 SMP PENTIUM4 gcc-3.3
This with debian unstable/testing combination
Well, my PVR-500MCE (NTSC) is working with 0.3.2f + Jarod's tuner
update patch. The only issue now is that the tuning seems slightly
off.
Suppose I tune into channel 10; 'ivtvctl -R' tells me that this is
frequency 3096. It comes in black and white until I push the frequency
up a little bit,
I have a system
with the 250 MCE card and a 150 retail card. A remote is on the150 and I
would like to use the radio input on the 250.The latest incarnation of
0.3.2f has severely degraded the tuning on my pvr-250 MCE.Channels over 60
are quite snowy and almost unwatchable. The 150, on the o
In myth tv I have tried setting the frequency table to cable-us and
cable-us-hrc (If that's what you mean by loading channel tunner
frequencies). The chann.c distributed with ivtv doesn't work. I had to
modify it to allow me to give it frequencies. It turns out that I have
to give it values WAY lo
Hi Paul,
> Paul Check wrote:
Hi: I have a problem that an earlier poster also had but I see no
follow-up
I suppose you refer to the Mail by Neil Sedger.
I have the same (or at least a very similar) problem and, like Neil,
have a Matrox 400. So just out of curiosity, do you have this card as well?
On Wed, 02 Mar 2005 22:44:02 +, Allan Stirling
<[EMAIL PROTECTED]> wrote:
> Jelte van der Hoek wrote:
>
> >- IOCTL for cx25840. Using utils/cx25840ctl one can write the registers
> >of the cx25840 directly using a name/value syntax.
> >
> >Either:
> >CX25840_SET_CH_1__SOURCE(0x0006)
> >or
> >C
There is some funding for anyone capable of assisting in getting CC
working on the PVR-500. Can you tell me how to get the i2c dump in the
meantime?
On Wed, 2005-03-02 at 09:05, Chris Kennedy wrote:
> It never worked, that's just left overs from the saa7115 file, Hans did
> that, but for the pvr15
Jelte van der Hoek wrote:
- IOCTL for cx25840. Using utils/cx25840ctl one can write the registers
of the cx25840 directly using a name/value syntax.
Either:
CX25840_SET_CH_1__SOURCE(0x0006)
or
CH_1__SOURCE=6
Thanks SO much for this.
And now... (Drum roll ;)
I have COLOR (Colour) input on S-Vid
This is more a snapshot of what I have working at this time. (See link
at the bottom)
The changes are on top of 0.3.2f and relate to the cx25840 driver:
- Fixes to make the cx25840 load on FC3 with 4KSTACKS
The large on-stack setting arrays are replaced by function calls. The
settings are stil
Jelte van der Hoek <[EMAIL PROTECTED]> wrote:
> I'll post a patch separately, but it also includes my changes for FC3
> with 4KSTACKS and adding IOCTL to cx25840 to make it easier to
> experiment these settings. But effectively what it looks like now is:
This makes sense.
--
Tyler Trafford
On Tue, 2005-03-01 at 23:43, Tyler Trafford wrote:
> Tell how this patch works for you, it's a very simple change against
> 0.3.2f. It sets it to 0 only for NTSC cards, and to 1 for anything
> else.
Yeah, this works. But the problem is the one that I referred to earlier.
The read_setting only re
Nope, this is the problem I have been talking about.
If the card is not tuned to a channel, the patch does not work.
-J
On Wed, 2005-03-02 at 21:52, Jaap Braam wrote:
> I SPOKE TOO SOON
>
> I had audio after a reboot of my box...
>
> After a power down, unplug, plug and boot again the sou
I SPOKE TOO SOON
I had audio after a reboot of my box...
After a power down, unplug, plug and boot again the sound was gone...
This is better than before, because I usually had no sound at all after
a reboot...
Apparently some necessary settings from the 0.3.2d driver survive a
reboot..
Tyler,
This patch WORKS I've got audio using the 0.3.2f driver. Only this
patch applied...
Thanx!
Jaap
Tyler Trafford wrote:
On Wed, 02 Mar 2005 00:01:40 +0100, Jaap Braam <[EMAIL PROTECTED]> wrote:
0.3.2f doesn't work for me (PVR150MCE PAL), no sound ... Neither did
0.3.2
On Tuesday 01 March 2005 21:33, Winston Chang wrote:
> 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
On Wednesday 02 March 2005 12:58, Joe Briggs wrote:
> I am trying to get valid closed captioning data from my PVR-500 and I am
> hacking through the ivtv-vbi.c, ivtv-fileops.c, and cx25840'.c files
> trying to understand the logic and data flow using the vbi.c example
> program in the utils directo
On Tuesday 01 March 2005 14:29, Tyler Trafford wrote:
> On Tue, 1 Mar 2005 14:02:39 -0800, Jarod Wilson <[EMAIL PROTECTED]> wrote:
> > On Tuesday 01 March 2005 08:05, Chris Kennedy wrote:
> > > This merges all recent patches except the most recent 4k stacks one
> >
> > And one more -- the updated t
Seems like your email got held up for a while, and I have somewhat already
answered this, but I'll go 'head and do it again.
On Tuesday 01 March 2005 03:57, Jason Knisley wrote:
> Well, give it a try with just the PVR-500MCE in and
> tell us the addresses. It'd be good to have two
> sightings of
On Wednesday 02 March 2005 08:28, Jim Karcz wrote:
> Following Jarod's directions, after the 'modprobe ivtv', my
> /var/log/messages file yielded this. I am running a P4 3G Prescott with HT
> enabled on an Intel 865perl MB. I am a bit of a newbie when it comes to
> Mythtv, ivtv, etc.
Have you tr
On Tuesday 01 March 2005 12:39, Lee Lists wrote:
> >That said, I'm not certain exactly what the problem is, but I highly
> > suggest the OP try an ivtv version newer than 0.1.10pre2-ck114k with that
> > kernel.
>
> I back-ported tuner.c from 0.3.2 to 0.114 and it worked.
>
> 0.114 is the only that
On Tuesday 01 March 2005 12:48, Chad Osmond wrote:
> Hi,
>
> My PVR350 running FC3 using IVTV-3.xxx from ATRpms is a little fuzzy on
> cable tuner channel 28, is there a value I can use to adjust the tuning
> by a small amount?
Check out ptune.pl and/or ptune-ui.pl. I believe the ATrpms package st
On Tuesday 01 March 2005 18:28, Pastor Doug Coats wrote:
> Thanks for your response Jarod.
>
> I added the two lines to my modprobe.conf file and made sure I installed
> ivtvdev(already done).
>
> I reran #depmod -a
>
> Here is my new modprobe.conf file.
>
> # ivtv modules setup
> alias tveeprom-iv
Op wo 02-03-2005, om 18:07 schreef Tyler Trafford:
> Setting the no_black_magic parameter nonzero will get rid of that i2c write.
According to this info I tryed to do a:
modprobe cx25840 no_black_magic=1
without loading SAA7127 att all, without difference.
It seems to function fine, but trows the
With SAA7127 loaded there's no problem (actualy there are no syslog
messages at all when switching channels).
Setting the no_black_magic parameter nonzero will get rid of that i2c write.
Interesting though, I think everyone has just assumed that write was
necessary to power up the PAL cards (
On Wed, 02 Mar 2005 17:55:51 +0100, Jaap Struyk <[EMAIL PROTECTED]> wrote:
> Op wo 02-03-2005, om 16:44 schreef [EMAIL PROTECTED]:
>
> > If I recall correctly, the SAA7127 is the Video Encoder chip.
> > It is only present on the PVR-350 as it is responsible for the TV-out.
>
> Your probebly right
not having the rest of the thread available to me right now, i may be
off base, but I had problems until I set the i2c_enable flags
correctly for my install with a 350 and a 150. I don't load the
SAA7127 at all, and set the cx25840 options to:
options cx25840 debug=0 i2c_enable=-1,1 no_black_magi
Op wo 02-03-2005, om 16:44 schreef [EMAIL PROTECTED]:
> If I recall correctly, the SAA7127 is the Video Encoder chip.
> It is only present on the PVR-350 as it is responsible for the TV-out.
Your probebly right, I yust restarted the box without loading the
SAA7127 and it seems to function fine, v
Sorry, i apologize. read too quickly through the log. Firmware is
ok. tveeprom still needs to load though, as a module.
-Dustin
On Wed, 2 Mar 2005 11:47:25 -0500, Dustin Lucien
<[EMAIL PROTECTED]> wrote:
> Mar 1 22:15:43 speedy kernel: ivtv: Error -19 reading Hauppauge eeprom.
> Mar 1 22:15
Mar 1 22:15:43 speedy kernel: ivtv: Error -19 reading Hauppauge eeprom.
Mar 1 22:15:43 speedy kernel: ivtv: Possible causes: the tveeprom module was
not loaded, or
Mar 1 22:15:43 speedy kernel: ivtv: the eeprom kernel module was loaded before
the tveeprom module.
tveeprom is not loading correct
Following Jarod's directions, after the 'modprobe ivtv', my /var/log/messages
file yielded this. I am running a P4 3G Prescott with HT enabled on
an Intel 865perl MB. I am a bit of a newbie when it comes to Mythtv,
ivtv, etc.
Mar 1 22:15:43 speedy kernel: Linux video capture interface: v1.00
M
Seems to work for me as well as "e" did with Jarod's patch collection.
composite works, nothing to test the tuner, and s-video still b&w :(
Late for work, so I can't see if my mythtv-related issues have gone away
or not (though I think those are mythtv-specific, not necessarily
ivtv-related -- i
Hi,
I was having similar problems on (almost) the same hardware.
I'm running Debian with a self-compiled 2.6.10 kernel, 2 PVR-350 cards,
software RAID5,
Asus P4P800 Deluxe, Intel P4 3,2GHz Prescott but with HT DISabled.
With HT enabled, when both PVR's were busy (recording, watching live TV,
p
Yeah, it records the right channel. I've since had to take it out of my box
because the rest of the days this week are *heavy* with recordings and I put
my other 250 back in.
I'll play with it more this weekend and verify.
-Todd
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAI
Okay, consider it redone.
Here's a patch that makes the cx25840 driver work on FC3 with 4KSTACKS
kernel.
It's a patch against ivtv-0.3.2f from
http://ivtv.no-ip.info/ivtv-0.3/ivtv-0.3.2f.tgz
I get a picture and the system does not hang! The only problem with the
ivtv-0.3.2e and f drivers seems
0.3.2f doesn't have the latest and greatest settings for the PVR-500 NTSC's
tuner. This patch includes an updated definition for that tuner, and syncs up
with the latest v4l tuner, so there are no more "NoTuner" entries, and the
tuner numbers are slightly different than previously.
Note that I'
Hi,
My PVR350 running FC3 using IVTV-3.xxx from ATRpms is a little fuzzy on
cable tuner channel 28, is there a value I can use to adjust the tuning
by a small amount?
Thanks,
Chad
---
SF email is sponsored by - The IT Product Guide
Read hones
Hi,
If I recall correctly, the SAA7127 is the Video Encoder chip.
It is only present on the PVR-350 as it is responsible for the TV-out.
Stanley.
> Op wo 02-03-2005, om 16:05 schreef Tyler Trafford:
>
> > It can tell you about your card- especially the tuner type.
>
> OK, that explains why t
Well, give it a try with just the PVR-500MCE in and
tell us the addresses. It'd be good to have two
sightings of it, not just the ramblings of some madman
like myself. :P
I think I asked you this before, but I'm going to
reask on a more open forum for people to butt in...
Have we found where the T
On Tue, 1 Mar 2005 17:49:26 -0500, Tyler Trafford <[EMAIL PROTECTED]> wrote:
> On Tue, 01 Mar 2005 23:13:01 +0100, Jelte van der Hoek
> <[EMAIL PROTECTED]> wrote:
> > It seems that you're querying the AFD_FMT_STAT based on the video
> > presented before switching the source. Is that correct?
>
> Y
Op wo 02-03-2005, om 16:05 schreef Tyler Trafford:
> It can tell you about your card- especially the tuner type.
OK, that explains why the card is working splendid without it.
> Does 'saa7127' really do anything for you? I'm wondering because it
> doesn't on my pvr150ntsc.
I set up the card a
Jaap Struyk <[EMAIL PROTECTED]> wrote:
> Maybe it's dumb, but what's the use of tveeprom?
It can tell you about your card- especially the tuner type. Ivtv can
also use it to autodetect the tuner type so you don't have to specify
it (but right now only does that for the PVR250 and PVR350- though
Hello,
Maybe it's dumb, but what's the use of tveeprom?
I have a pvr150pal and 0.3.2d and use:
modprobe tuner
modprobe saa7127
modprobe cx25840
modprobe wm8775
modprobe ivtv ivtv_std=2 tuner=51
This works fine, tveeprom doesn't add (as far as I can tell) anything,
why should it be needed?
--
Groe
I am trying to get valid closed captioning data from my PVR-500 and I am
hacking through the ivtv-vbi.c, ivtv-fileops.c, and cx25840'.c files
trying to understand the logic and data flow using the vbi.c example
program in the utils directory as a tester. When the user application
vbi.c opens up /de
Hi folks...
I was sending a long message before (>20kb, due to logs)
and finally got a message from SF now (27hours later), that my message
exceeded the sizelimit and awaits approval from a moderator.
Ignore the older message please. I deleted debian from the Computer and
gave Jarods Howto another
Jason Knisley wrote:
I scheduled several things to record to take up both
tuners and to record right in a row... Sometmies, the
tnuers just.. stop acquiring data. I have to kill
mybackend and restart it, then all is just fine. But
it just says "Waiting to acquire data." Again,
restarting Myth makes
On Mar 1, 2005, at 12:38 AM, Jarod Wilson wrote:
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
It never worked, that's just left overs from the saa7115 file, Hans did
that, but for the pvr150 it may be impossible because it uses a cx23416,
that isn't the cx23415 which Hans developed on and on the newer cards
(at least for CC this is the case), there hasn't been CC data captured for the
cx234
I've got it working now, I'll grab a patch together tonight, maybe you
can see if it works for you. (It's snowing now so I have to go out with
the kids ;-)
Basically, I changed the initial norm to -1 and consolidated all the
PATH1 and SRC3_PHASE stuff into the set_audio call. Setting the input
no
I'm having a pretty frequent lock-up on MythTV (0.17) on my PVR-350
(Jarod's guide, FC3, ivtv2).
Everything can work swimmingly for a couple of days, then seemingly
at random (no particular time of day or anything else I can yet
determine), I'll get a null recording (i.e., zero bytes).
m
Chris,
We are doing a project requiring VBI data on the PVR-500 under a 2.6
kernel. I don't know if you saw my post last night, but it looks like
the VBI ioctl calls are supported at the API level, but the low-level
chip config routines are commented out in the cx25840-driver.c file. The
cx25840 f
Hi all
I don't know how to create one of those patch files, but the tuner on my card
(and I also believe the MPG600, MPG160 and M179 cards) have their tuner at
address 0x60.
The line:
static unsigned short normal_i2c_range[] = {0x61,0x6f,I2C_CLIENT_END};
needs changing to:
static unsigned sh
I back-ported tuner.c from 0.3.2 to 0.114 and it worked.
0.114 is the only that work with my PVR-250 so i continue to use it.
Lee
Jarod Wilson a écrit :
On Monday 28 February 2005 15:53, greg wrote:
Patch your kernel: http://205.209.168.201/~ckennedy/ivtv/new_tuners/
Bzzt, wrong! That isn't
I have a wintv 350 card. It gets detected as a type 47. Mythtv only
picks up one channel (french channel) and it's fuzzy.
I am in Canada so we are using us-cable.
I used chann.c to write a program to set the frequency of the tuner.
With this program I can get several channels clear as a bell, b
Thanks for your response Jarod.
I added the two lines to my modprobe.conf file and made sure I installed
ivtvdev(already done).
I reran #depmod -a
Here is my new modprobe.conf file.
# ivtv modules setup
alias tveeprom-ivtv tveeprom
alias msp3400-ivtv msp3400
alias char-major-81 videodev
alias
Hi all
I have been looking at the tuner on my Adaptec AVC-2410 working.
The tda9887 module is not sending PAL setings to the tda9887.
To get it working I believe I need to set "V4L2_STD_PAL_I".
I have not installed mythtv, but I would be grateful if someone who has would
let me know if it has
On Wed, 02 Mar 2005 00:01:40 +0100, Jaap Braam <[EMAIL PROTECTED]> wrote:
> 0.3.2f doesn't work for me (PVR150MCE PAL), no sound ... Neither did
> 0.3.2e... I'm still using a full functional 0.3.2d driver (no patch
> needed)
>
> I'll try to locate the significant differences.
I just post
I just asked because it seems I can only get the correct sound now with
the 0.3.2f driver after changing tuners twice while tuning to a channel.
If after bootup the card is not tuned to a channel (ie no signal), my
card returns 0x01 which is set to NTSC in your logic. So when the tuner
is selected
Hi,
I have a similar problem: my cable company used a completely weird set of
channels/frequencies (they do not match any of the predefined tables).
I just entered the frequencies as six digit numbers in the initial
mythfilldatabase run
(well actually, I modified them directly in the channels t
On Tuesday 01 March 2005 19:14, greg wrote:
> I have a wintv 350 card. It gets detected as a type 47. Mythtv only
> picks up one channel (french channel) and it's fuzzy.
>
> I am in Canada so we are using us-cable.
>
> I used chann.c to write a program to set the frequency of the tuner.
> With this
61 matches
Mail list logo
