I think this is some kind of joke or something. Not at all consistent with
every single other email I've seen from Chris as far as signature, email
address, etc.
~Lou
On Sunday 05 June 2005 06:40 pm, Harry Orenstein wrote:
> On Sunday 05 June 2005 8:53 pm, ivtv wrote:
> > I have been experimen
Harry Orenstein wrote:
How new? Could you post MD5 sums or some other indication of the versions you
want people to try? Probably would be best to compare apples to apples.
It's version 2.05.32 or greater, I think that's the newest version
though. It's included on
every new pvr150/500 C
This may be useful:
http://ivtv.writeme.ch/tiki-index.php?page=FirmwareVersions
Harry Orenstein wrote:
How new? Could you post MD5 sums or some other indication of the
versions you
want people to try? Probably would be best to compare apples to apples.
-- Harry O.
--
On Sunday 05 June 2005 8:53 pm, ivtv wrote:
> I have been experimenting and have found that the newest firmware is
> working ok during my tests now, it seems we have possibly gotten the
> driver to the point of working with the old firmware and newer
> firmware. The newer firmware seems good at f
I have been experimenting and have found that the newest firmware is
working ok during my tests now, it seems we have possibly gotten the
driver to the point of working with the old firmware and newer
firmware. The newer firmware seems good at framebased DMA, doesn't do
block based, while the
I sent this message to the ivtv users group yesterday but have come up
dry. So I thought that hopefully the developers might have the answer.
Sorry for the repeat for those who belong to both groups.
I am following Jarod's instructions in setting up a PVR-350 for Mythtv
with output on FC3.
I can
Alan Secker wrote:
I exited mplayer and clicked the MythTVbackend. I then ran ps -ax|more
to check that it was
running. I clicked the MythTV Frontend icon and got a black screen
with the hard drive having
short bursts of activity at regular intervals. It reminded me of the
sound of pall bearer
Still seems to be at least one autodetection problem. I have two
PVR-150s, one MCE, one non-MCE, and my non-MCE (I think, don't have
physical access at the moment, tuner type is 39) NTSC pvr-150 is
defaulting to a pvr-250 with the 0.3.5y release. My other pvr-150 is
identifed correctly, but is a
Addendum to my earlier message.
I decided to reboot an run MythTV again:
1) MythTVbackend
2) MythTVfrontend
Get horizontally-striped b/w full screen
3) Right Nav Key returns - Skip ahead message
4) Left Nav Key returns - Skip back message
5) Up Nav key, after a delay showed a station icon, the
I have a two pvr-150s, one MCE, one non-MCE, one of them is tuner type
47 the other type 39. I can get the type 47 to work without any
problems by just doing a modprobe tveeprom followed by a modprobe
ivtv. I don't have anything in my modules.conf. Make sure that you
don't have a tuner module o
I was getting warnings that Mythfilldatabase wasn't running but
following some changes,
those seem to have stopped.
After further advances in learning to complete some of the missing
fields in MythTV Setup,
I was still having trouble. I tried $mplayer /dev/video0 and to my
surprise, up came
Lo
0.3.6 with PVR-150MCE (LG TAPE, PAL). Audio on tuner worked fine till
0.3.4s, got broken, fixed in 0.3.5, broken again in 0.3.5a.
Tried 0.3.6. Audio works with tda9887 qss=0 module option but with
crackling, popping sound.
N.
On 6/4/05, Bryan Mayland <[EMAIL PROTECTED]> wrote:
> I spent my mornin
They said it was fixed in 0.18.1, do not tested yet thoOn 6/5/05, Tyler Trafford <[EMAIL PROTECTED]> wrote:
Bryan Mayland <[EMAIL PROTECTED]
> wrote:> Nicholas Gibson wrote:>> >This is way off topic and I apologize but is anybody> >elseelse experiencing this problem with> >mythfilldatabase?> >>
Ulrich Mayer wrote:
excellent work, no crackling noise anymore.
Hooray! That's a good thing.
Picture quality for composite is also good, s-video is b&w.
If you go to cx24850-driver.c around line 723, for the
SX25840_SVIDEO case, if you change
CX25840_SET_PWR_DN_CH3(0x01);
to set i
I forgot: ivtv-0.3.6
Ulrich Mayer wrote:
Bryan, Chris,
excellent work, no crackling noise anymore. Picture quality for
composite is also good, s-video is b&w.
BUT... the audio for both composite and s-video is from the tuner.
MY VCR is connected to both composite and s-video and the antenna
Bryan, Chris,
excellent work, no crackling noise anymore. Picture quality for
composite is also good, s-video is b&w.
BUT... the audio for both composite and s-video is from the tuner.
MY VCR is connected to both composite and s-video and the antenna is
also wired via the video recorder.
I _c
Bryan Mayland <[EMAIL PROTECTED]> wrote:
> Nicholas Gibson wrote:
>
> >This is way off topic and I apologize but is anybody
> >elseelse experiencing this problem with
> >mythfilldatabase?
> >
> >
> Nope, I have guide data for the next 13 days. Looking at my logs
> shows everything is runn
I had a KnoppMyth R5A10 with a PVR250 that worked very well until we
had a bad lighting storm and the PVR250 was unable to lock onto the
picture (The picture would wiggle and lose sync not matter what the
channel was).
So I assumed that some of the tuner hardware was fried and I went
looking for
Uwe Wiggenhauser wrote:
ivtv: Card ready for firmware!
ivtv: Loading encoder image
ivtv: requesting firmware
ivtv: firmware load failed
ivtv: failed loading encoder firmware
ivtv: Error loading firmware -3!
ivtv: Error -3 initializing firmware.
Looks like firmware is being loaded by the ho
Hi,
I'm trying to get my pvr 350 to work since days but without luck.
ivtv: unsupported module, tainting kernel.
ivtv: START INIT IVTV
ivtv: version 0.3.2 (c) loading
ivtv: Linux version: 2.6.11.4-20a-default gcc-3.3
ivtv: In case of problems please inc
Nicholas Gibson wrote:
This is way off topic and I apologize but is anybody
elseelse experiencing this problem with
mythfilldatabase?
Nope, I have guide data for the next 13 days. Looking at my logs
shows everything is running as it should, with no 500 errors at all.
I'm using m
21 matches
Mail list logo
