While updating the utilities to make them compile cleanly on x86_64, I
noticed that the Makefile did not represent dependencies correctly.
This meant that even if a I changed a file, make would not rebuild
programs that depended on it.
I have extensively updated utils/Makefile
- I hope that I rep
I had static on my type 47 until I forced the tuner type to 44, I may
have also upgraded to the 0.3.x version of ivtv at the same time. Have
you tried that?
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hund
ive tried 44, 45,46, 47 none seem to work. has anyone found a
solution to this yet?
-Jeff
On Fri, 25 Feb 2005 22:20:57 -0500, Maverick <[EMAIL PROTECTED]> wrote:
> Only way I could get my tuner type 47 to tune channels is to force it
> to type 44 in mod*.conf. I still haven't resolved the dma l
Several __u64 objects are printed with formats with ll modifiers.
This is correct if and only if __u64 is unsigned long long, the case
in i386 (and probably most 32-bit systems).
On x86_64 __u64 is unsigned long, so the ll modifier is wrong. The
result will be improper printing, possibly includin
It seems that type 47 is still being reported as NoTuner. Which device
did you get poor video on, video0 or video1? I got poor UHF reception
with type 50 on video0 and type 39 on video1, perhaps you have one of
those tuners.
* Noah Patton <[EMAIL PROTECTED]> [2005-02-25 23:01:25]:
> Thanks, that
Nevermind, reworked the cable routing and things are now
fine. Man, this thing is sensitive! Have it direct first
device now, though, and picture looks great.
Thanks everyone for the great assistance in making this
all work!
Noah
On Fri, 25 Feb 2005 19:56:56 -0800
"Noah Patton" <[EMAIL PROT
Thanks, that did the trick! I've now got my tuner up and
working, I can switch through channels, sound, etc -
however, picture quality is terrible. The cable line is
good, plugged into a tv it looks great, but with the
PVR-500MCE NTSC quality is terrible. Suggestions?
Thanks!
Noah
INIT IVTV
Only way I could get my tuner type 47 to tune channels is to force it
to type 44 in mod*.conf. I still haven't resolved the dma lockup
problem when you ff/rew alot.
-Kenneth
---
SF email is sponsored by - The IT Product Guide
Read honest & cand
ok, when i load the ivtv module and run the tac command, this is the
output to /var/log/messages
Feb 25 20:57:30 localhost kernel: ivtv: START
INIT IVTV === =
Feb 25 20:57:30 localhost kernel: ivtv: version 0.2.0 (rc3g) loading
Feb 25 20:57:30 localhost kernel:
Yeah, this config works for NTSC and PVR500mce. But I'm only using
tuner=54,54 as per the patch.
One missing part is that recording only works to the standar picture size.
If you try
to record to a smaller image size you get a crop image.
Good work,
Fernando Ramirez
Finally! Complete success wit
David Cain wrote:
... I've now accomplished what I set out to do and have UHF channels
(albeit not channel 69, but since that's UPN here it's no great
loss... ;)
...
OK, I'm going to go to bed and dream of amplifiers for my poor OTA TV
signal...
Just thought I'd chime in here with some info I've
Jeffrey Zellman wrote:
Hi,
So I tried the fix and I updated to 2.6.11-rc4 +
http://dl.bytesex.org/patches/2.6.11-rc4-2/ and
http://dl.bytesex.org/cvs-snapshots/video4linux-20050218-161823.tar.gz
but all my channels are still static.
Im in the US so I am using ntsc hrc here is the output of dme
Hi,
So I tried the fix and I updated to 2.6.11-rc4 +
http://dl.bytesex.org/patches/2.6.11-rc4-2/ and
http://dl.bytesex.org/cvs-snapshots/video4linux-20050218-161823.tar.gz
but all my channels are still static.
Im in the US so I am using ntsc hrc here is the output of dmesg |grep ivtv
ivtv: =
Sure, it's just a quick two-liner. You're right about the setup.
diff -aur ivtv-0.3.2e/driver/tuner.c ivtv-0.3.2e-ajm/driver/tuner.c
--- ivtv-0.3.2e/driver/tuner.c 2005-02-25 20:02:38.0 -0500
+++ ivtv-0.3.2e-ajm/driver/tuner.c 2005-02-25 20:03:51.0
-0500
@@ -232,8 +232,8 @
Anthony:
Can you post a patch with the additions from 2.6.10-mm1?
You are running the 0.3.2e with the addition of Jarod's cumulative
patch from this thread, plus your import of the tuner type 47 from
2.6.10-mm1 on a non-4kstacks kernel, right?
Thanks!
Noah
On Feb 25, 2005, at 4:09 PM, Anthony J.
Finally! Complete success with the PVR-500. Or almost complete
success. There doesn't appear to be a radio device, but both tuners are
working properly. I had to import tuner type 47 from 2.6.10-mm1 into
tuner.c from 0.3.2e. It also seems that I get tuner audio on all video
inputs, I don't hav
Here's a cumulative patch against ivtv 0.3.2e, containing Jelle's vsync patch,
Jaap's picture controls patch, Tyler's pg600/150mce patch and a tuner patch
that *hopefully* works with the PVR-500MCE NTSC's tuner.
I just applied these and "e" now works for me (it wouldn't without the
patches). s-
Has anyone to date had any progress on getting color input through
S-Video yet? What needs to be done to conquer this remaining issue? And
where in the code can we begin to look for possible answers?
I'll second that request. Though I have mine working through the
composite input now, s-video wo
On Fri, 25 Feb 2005 10:53:39 -0500
Tyler Trafford <[EMAIL PROTECTED]> wrote:
> Does the white noise still occur after after completely resetting the
> machine? (I had a similar problem, but it went away after temporarily
> removing power fromt he machine.)
>
Yes...it did work after a power cycl
there are illicit copies floating around the internet,
but conexant has not released it publicly to my
knowledge
for a mere $10k, you can buy a dev kit from conexant
which presumably comes with an NDA and all the docs
you want :)
-tmk
--- Ram Yalamanchili <[EMAIL PROTECTED]> wrote:
> Hey guys,
some of the older pvr cards had similar connectors. i
think i found pinouts at shspvr.com (or whatever that
site is)
at any rate, the guy who runs that forum can probably
get you the info from hauppauge. His name's anthony
toste (sp?) IIRC.
-tmk
--- Chris Kennedy <[EMAIL PROTECTED]> wrote:
> Th
My working theory is that its failing because ivtvdev_drv.o is compiled
as a 32-bit object, and that although it exists, something it relies on
doesn't... (such as a 32-bit version of glibc). This is the difference
between that driver and every other in the drivers directory:
OK, thanks to everyone
Hi all
I guess the FQ1216ME/I H-3 is compatible with the FM1216ME MK3 because I am
now using the kernel module of tuner.c - which was exactly the same with an
awful picture untill I selected to use tuner type=38 which is for the
FM1216ME MK3 and now the picture is perfect and I am getting all
This is something I've wondered too, maybe Hauppauge can release the pinouts
for the conector, probably have to make a custom one, but I couldn't ever
find exact information on each cards pinouts even to do that (all the cards,
250,350,150,500; all have different ones). I haven't seen it but heard
Jeremy Huddleston wrote:
Ok, I solved the tuner problem by using:
I updated to 2.6.11-rc4 + http://dl.bytesex.org/patches/2.6.11-rc4-2/
and
http://dl.bytesex.org/cvs-snapshots/video4linux-20050218-161823.tar.gz
Also to fix the green svideo out, I did:
ivtvctl -j reg=0x6c,val=0xfa -d /dev/video16
Hey guys,
i am looking for the datasheet for cx23416 chipset. i found a cached
version of the api datasheet, but thats not useful for me. i am trying
to use this chip to design a mpeg board, but couldn't find the
hardware datasheet.
please mail me if anyone got it.
-- R
On Fri, 25 Feb 2005 18
does anybody know where to purchase the necessary connector(s) to add a second
S-Video/audio input to the 500. apparently there is a header on the card with
these inputs. i want to connect two satellite receivers to it.
i realise i could use 2x PVR 150 but that would use two slots
regards
--
si
Hi all
I am looking at figuring out why the tuner on my AVC2410 is not working.
The tuner is an FQ1216ME/I H-3 and using the FM1216M3_MK3 data sheet which was
the only data sheet I could find on the net and I believe is probably
applicable.
I've been looking at the i2c numbers sent in windows:
Thanks for the feedback, Alan. I eventually got the remote working
earlier this week. Your response has motivated me to state the
following thing that confused me:
The IVTV Wiki called, "Remotes" had the following ambiguous statement:
"NOTE: once you get a remote config you like, you have to a
Does the white noise still occur after after completely resetting the
machine? (I had a similar problem, but it went away after temporarily
removing power fromt he machine.)
On Thu, 24 Feb 2005 06:51:03 -0600, James L. Reese <[EMAIL PROTECTED]> wrote:
> On Wed, 23 Feb 2005 13:19:49 -0800
> Jarod
On Thu, 24 Feb 2005 20:32:38 +0100, Nick Rosier <[EMAIL PROTECTED]> wrote:
> cx25840: Status: 'No detected audio standard' (Detected audio standard)
Could you try the audiofmt paramter, with values 0x1 to 0xe
--
Tyler Trafford
---
SF email is
Hi Steve
On Monday February 21 2005 22:48, Steven Poulakos wrote:
> Here's a link to the Wiki post:
> http://ivtv.writeme.ch/tiki-index.php?page=Remotes
>
> For the above link, I can successfully follow the instructions to just
> before the last line of the "Setting up ir-kbd-i2c" section. So, I
A lot of debugging info (gave no debug option for cx25840) so I didn't
get the top (my buffer is too small).
cx25840: Status: 0x01 (VLOCK, Vertical lock status)
cx25840: Status: 0x01 (CSC_LOCK, Color Subcarrier lock status)
cx25840: Status: 0x01 (AGC_LOCK, VGA lock status)
cx25840: Status: 0x01 (V
Rachel,
to make sure, compile the driver yourself; I use this guide:
http://www.schaefer.dhcp.biz/pvr350tvout.htm
[EMAIL PROTECTED]:~/library/ivtv-0.2.0-rc3a/utils# tar -zxf
XFree86-4.3-incr-DMA-06.tgz
[EMAIL PROTECTED]:~/library/ivtv-0.2.0-rc3a/utils# cd ../..
[EMAIL PROTECTED]
Rachel Willmer wrote:
> So, my question:
>
> a) does that theory make sense? Has anyone else got X working out a
> PVR-350 on an AMD64 machine?
Yes, you need to rebuild it for amd64.
Yes I have it working fine on my box and have installed for amd64 on
another box and it appears to work fine.
If yo
On Friday 25 February 2005 15:46, Rachel Willmer wrote:
> My working theory is that its failing because ivtvdev_drv.o is compiled
> as a 32-bit object, and that although it exists, something it relies on
> doesn't... (such as a 32-bit version of glibc). This is the difference
> between that driver
This was just discussed earlier today/last night.
"Pastor Doug Coats" <[EMAIL PROTECTED]> writes:
> Feb 24 19:47:06 media1 kernel: ivtv: Failed to load module tveeprom
This is your problem.
Go read the archives for the last 24 hours for a solution.
-derek
--
Derek Atkins, SB '93 MIT EE
On Wed, 23 Feb 2005 13:19:49 -0800
Jarod Wilson <[EMAIL PROTECTED]> wrote:
> Here's a cumulative patch against ivtv 0.3.2e, containing Jelle's vsync
> patch,
> Jaap's picture controls patch, Tyler's pg600/150mce patch and a tuner patch
> that *hopefully* works with the PVR-500MCE NTSC's tuner.
I am a bit of a niblet and shouldn't be allowed near linux machines. I
recompiled my kernel to get DMA working (there is a stutter watching tv
without it) and I had two versions of the ivtv driver. I thought that I
had been using the 3.2e version, but after going through my bash history I
found t
I've got problems getting my ivtvdev setup working with X, would
appreciate any pointers.
The situation is this: I'd got ivtvdev/mythtv working with a PVR-350
card on an old machine, so decided to move it onto a new fast machine.
The setup used to work, now I can't get it to run X out the PVR-350 c
> > --- Jonathan Martin <[EMAIL PROTECTED]> wrote:
> >> I am noticing that whenever I capture video with the
> >> PVR-150, it seems to
> >> be cropping the right side of the image. For
> >> example watching an ESPN
> >> basketball game, I can't see the score. Has anyone
> >> else had this issue?
I'm using a PVR-150MCE l.p. and so far have not had success yet. Last night
i clean installed FC3 with 2.6.10-1.760 from atrpms. Fresh ivtv-0.3.2e and
jarods latest patch. I now can see the card, but i cant tune to any
channels or get any sound using any of the inputs. Hope this helps. I have
Don't know if this would help but I've grabbed both dmesg from 0.3.2d
(working) and 0.3.2e (no audio)
# diff 0.3.2d.dmesg.txt 0.3.2e.dmesg.txt
12c12
< cx25840: Status: 0x17 (TUNE_OUT, The tuning code selected by the
auto-tune algorithm.)
---
> cx25840: Status: 0x16 (TUNE_OUT, The tuning code sele
| From: D. Hugh Redelmeier <[EMAIL PROTECTED]>
| Here are the top consumers of stack space in
| ivtv-0.3.2e/driver/cx25840-driver.c after my changes, but not Davids.
| I don't know the call graph, so I don't know if these need to be added
| together.
|
| 2632 setting_sequencer
| 1576 cx25840_de
Its on my monitor. I don't think its over scan because I can reduce the
image to say a 600x400 box on the screen with black borders all around it,
but still seems to cut off some of the image on the right.
> is this on a tv or on your computer?
>
> if it's on your tv, check the file on your PC fi
is this on a tv or on your computer?
if it's on your tv, check the file on your PC first
and see if the information is there.. might be an
overscan issue (with your output video device)
-tmk
--- Jonathan Martin <[EMAIL PROTECTED]> wrote:
> I am noticing that whenever I capture video with the
>
| From: Jelte van der Hoek <[EMAIL PROTECTED]>
| > | From: Jelte van der Hoek <[EMAIL PROTECTED]>
| > |
| > | I made a change to the cx25840 driver that changes the seq arrays to
| > | function calls (and uses an additional array to buffer the settings), I
| > | was still testing this but it seem
On Thursday 24 February 2005 18:59, Pastor Doug Coats wrote:
> I am using FC3 and trying to get Mythtv using Wilson's instructions. I am
> not sure if anyone has gotten ivtv to work with FC3 yet for TV output. If
> you have please help me out.
Its been done. First up, you probably need to add th
Rebuilding an older Myth box with FC3 and a PVR 250.
Compiling and installing 0.2.0rc3g, I get nothing but
static. dmesg (way below) looks good, my startup
script (below) runs without errors. When I tune to
known good channels all I get is static. I have
another Myth box nearby, and I can't seem to
49 matches
Mail list logo
