Steve Nuffer wrote:
I finally got it working but I dont understand why. I have had
the following problem for several days which I couldn't fix.
I started playing with ptune-ui.pl and changed "NTSC" --> "NTSC-hrc".
It worked after that
NTSC-HRC is just another frequency table. Most cabl
I used VNC to connect to my system which brings up twm.
Make sure vncserver is installed on your system
Install VNC onto a client
SSH to your myth system
start VNCserver : vncserver
On a client (Linux,Unix, Windows) start VNC viewer
Check http://www.realvnc.com/
[EMAIL PROTECTED] wrote:
On Su
On Sun, Jun 26, 2005 at 03:00:25PM -0700, Steve Nuffer wrote:
>
> # ivtvctl --input-detect
> check SAA7115 input signal
> ioctl: VIDEO_STATUS = Bad
>
> I started playing with ptune-ui.pl and changed "NTSC" --> "NTSC-hrc". It
> worked after that.
>
> # ivtvctl -I
> check SAA7115 input signal
>
I finally got it working but I dont understand why. I have had the following problem for several days which I couldn't fix.
# ivtvctl --input-detect check SAA7115 input signal ioctl: VIDEO_STATUS = Bad
I started playing with ptune-ui.pl and changed "NTSC" --> "NTSC-hrc". It worked after that.
#
In article <[EMAIL PROTECTED]>, jerome lacoste
mailto:[EMAIL PROTECTED]> wrote:
> On Wed, 16 Mar 2005 19:14:31 +0100, MythTV user <[EMAIL PROTECTED]> wrote:
> > I said thanks Daniel because he suggested that I would look at Thomas
> > Olsson's post and yes, you provided the link so I guess I owe yo
On Wed, 16 Mar 2005 19:14:31 +0100, MythTV user <[EMAIL PROTECTED]> wrote:
> I added my original problem and the solution to the post since everything
> inbetween is irrelevant now.
>
> I said thanks Daniel because he suggested that I would look at Thomas
> Olsson's post and yes, you provided the
On Wednesday 16 March 2005 18:21, MythTV user wrote:
> Yep, that was it. This really should be posted somewhere more accessible.
> I have spent countless hours trying various tests with no luck and it was
> this easy.
>
> Thanx Daniel!
>
> :) Mat
> :
> > On Wed, 16 Mar 2005 11:12:11 +0100, Daniel F
ion.
/Mat
- Original Message -
From: "jerome lacoste" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, March 16, 2005 7:03 PM
Subject: Re: [ivtv-devel] PVR-350 Tuner problem [SOLVED]
> On Wed, 16 Mar 2005 18:21:42 +0100, MythTV user <[EMAIL PROTECTED]> wrote:
> > Yep,
On Wed, 16 Mar 2005 18:21:42 +0100, MythTV user <[EMAIL PROTECTED]> wrote:
> Yep, that was it. This really should be posted somewhere more accessible.
> I have spent countless hours trying various tests with no luck and it was
> this easy.
which information did you use?
You said "thanks Daniel" b
odprobe and /usr/src/linux/Documentation/modules.txt for information.
- Original Message -
From: "MythTV user" <[EMAIL PROTECTED]>
To:
Sent: Sunday, March 13, 2005 7:25 PM
Subject: [ivtv-devel] PVR-350 Tuner problem
> I have searched for all keywords I can find in this list. I h
obe for adapter crt2 (0x3)
26c31
< saa7115: status: (1E) 0x00, (1F) 0xc0
---
> saa7115: status: (1E) 0x40, (1F) 0xc0
39c44
< tda9885/6/7: chip found @ 0x86
< ivtv: i2c attach [client=tda9887,ok]
48c51
Regards,
Mat
- Original Message -
From: "jerome lacoste" <
On Tue, 15 Mar 2005 13:23:07 +0100, MythTV user <[EMAIL PROTECTED]> wrote:
> Gijs,
>
> I am now running 2.4.27. I tried the latest 0.2.0 and 0.3.0 ivtv drivers.
> They still load without errors and I still have static only. I also tried
> grabbing bttv 0.9 and recompiling the kernel but there's no
olution is just too crippled.
Thanks,
Mat
- Original Message -
From: "Gijs de Wachter" <[EMAIL PROTECTED]>
To:
Sent: Sunday, March 13, 2005 10:02 PM
Subject: Re: [ivtv-devel] PVR-350 Tuner problem
> Mat,
>
> I have the exact same problem you have (with the s
Mat,
I have the exact same problem you have (with the same card/tuner combination).
Last week I decided to give kernel 2.4 a try instead of the 2.6 I was running
and it just worked the first time I tried. It even kept working when I
upgraded the i2c or bttv drivers for the 2.4 kernel.
I used
I have searched for all keywords I can find in this list. I have read all
posts with the slightest chance of helping me but I cannot make my tuner
find the TV channels. All I get is static. I was hoping not to have to bug
you all on this list but this is now my last hope of getting the TV working.
Looks like everything is in place there. I'm using the bttv-build that
came with 2.6.9. I'm running all out of ideas.
On Mon, 6 Dec 2004 09:54:40 +0100, Gijs de Wachter
<[EMAIL PROTECTED]> wrote:
> On Sunday 05 December 2004 23:55, Nick Rosier wrote:
>
>
> > Just thought of something; you said t
On Sunday 05 December 2004 23:55, Nick Rosier wrote:
> On Sun, 5 Dec 2004 17:37:10 +0100, Gijs de Wachter
>
> > I replaced my Pinnacle PCTV Pro for the PVR 350, but I'm still using the
> > Pinnacle remote which is on the serial port. I plan on using the
> > Hauppauge remote when the pvr350 is worki
On Sun, 5 Dec 2004 17:37:10 +0100, Gijs de Wachter
<[EMAIL PROTECTED]> wrote:
> On Sunday 05 December 2004 16:28, Nick Rosier wrote:
> > Do you have a module called lirc_driver? PVR-350's remote uses the
> > lirc_i2c driver. It doesn't use a serial-port; do you have another
> > remote connected to
On Sunday 05 December 2004 16:28, Nick Rosier wrote:
> Do you have a module called lirc_driver? PVR-350's remote uses the
> lirc_i2c driver. It doesn't use a serial-port; do you have another
> remote connected to your box?
I replaced my Pinnacle PCTV Pro for the PVR 350, but I'm still using the
P
Your problem is exactly the same as I had before I
No clue what this stuff does, probably not IVTV-related:
alias block-major-9 off
alias block-major-114 off
alias block-major-43 off
alias block-major-80 off
alias ide-cd off
Not in my modules.conf:
alias char-major-89 i2c-dev
Do you have a mo
This doesn't make any difference either.
On Saturday 04 December 2004 19:56, Nick Rosier wrote:
> Had the same problems; try this in your modules.conf.
>
> alias char-major-81 videodev
> alias char-major-81-0 ivtv
> alias char-major-61 lirc_i2c
>
> options ivtv ivtv_std=2 tda9887=0
> ins
On Saturday 04 December 2004 20:11, Nick Rosier wrote:
> Gijs,
>
> also make sure to remove the msp3400.ko from the kernel so the one
> from ivtv is used.
The only msp3400.ko I have is in the extra directory together with the ivtv
modules.
> In other news; me and some others have been having pro
Gijs,
also make sure to remove the msp3400.ko from the kernel so the one
from ivtv is used.
In other news; me and some others have been having problems getting
the colors right on the s-video and composite out. I'm kinda hoping
that the register-settings that are set by the windows drivers are not
Had the same problems; try this in your modules.conf.
alias char-major-81 videodev
alias char-major-81-0 ivtv
alias char-major-61 lirc_i2c
options ivtv ivtv_std=2 tda9887=0
install ivtv /sbin/modprobe --ignore-install ivtv
N.
On Sat, 4 Dec 2004 19:33:17 +0100, Gijs de Wachter
<[EMAIL
On Saturday 04 December 2004 17:51, Michael T. Dean wrote:
> Have you tried tda9887=1?
OK.. did that, but it does not make any difference.
> >options msp3400 simple=0 once=1 simpler=1
> >add below ivtv msp3400 saa7115 tuner saa7127
>
> These lines are not necessary with ivtv-0.2.0rc's. I recomme
Gijs de Wachter wrote:
I have the same problem Dennis Oelkers had last week. When cold booting to
Linux I only get static from my PVR-350 and when first booting to Windows and
then booting to Linux everything works fine.
As Henrik Mühe suggested to Dennis, I added tda9887=0 to the ivtv options
Hi,
I have the same problem Dennis Oelkers had last week. When cold booting to
Linux I only get static from my PVR-350 and when first booting to Windows and
then booting to Linux everything works fine.
As Henrik Mühe suggested to Dennis, I added tda9887=0 to the ivtv options
in /etc/modules.co
27 matches
Mail list logo
