On Wednesday 15 June 2005 16:06, Tyler Trafford wrote:
> On 6/15/05, belcampo <[EMAIL PROTECTED]> wrote:
> > On Wednesday 15 June 2005 12:27, Morten Rønseth wrote:
> > > Alas, 0.3.6 versions yet again show only black when starting myth after
> > > a cold boot.
> > > I do "/sbin/modprobe -v ivtv ivt
Bryan Mayland wrote:
> Tyler Trafford wrote:
>
> >Try setting these options for the tda9887 module:
> >
> >options tda9887 port1=0 port2=0
>
> Shouldn't that only fix the audio? I don't know what would make the
> screen all black though, unless ADC1 or CH1 was powered down, or the
> wrong inp
Tyler Trafford wrote:
Try setting these options for the tda9887 module:
options tda9887 port1=0 port2=0
Shouldn't that only fix the audio? I don't know what would make the
screen all black though, unless ADC1 or CH1 was powered down, or the
wrong input was selected.
On 6/15/05, belcampo <[EMAIL PROTECTED]> wrote:
> On Wednesday 15 June 2005 12:27, Morten Rønseth wrote:
>
> > Alas, 0.3.6 versions yet again show only black when starting myth after
> > a cold boot.
> > I do "/sbin/modprobe -v ivtv ivtv_std=2 tda9887=0" upon startup, but I
> > only get static...
>
On Wednesday 15 June 2005 12:27, Morten Rønseth wrote:
> Hi
>
>
>
> A while back I had problems initialising my 150MCE type 38 PAL card upon
> startup, I only got black picture with garbage at the bottom. Using
>
> 0.3.5p solved this:
> > Vedran Rodic wrote:
> >> Vedran Rodic wrote:
> >>> Okay, I w
Hi
A while back I had problems initialising my 150MCE type 38 PAL card upon
startup, I only got black picture with garbage at the bottom. Using
0.3.5p solved this:
Vedran Rodic wrote:
Vedran Rodic wrote:
Okay, I was using the wrong input number for tuner, it was 4 in
0.3.2d, and n
Vedran Rodic wrote:
Vedran Rodic wrote:
Okay, I was using the wrong input number for tuner, it was 4 in
0.3.2d, and now it's 6.
I've briefly tried 0.3.5o, and I get some hiccups in the mpeg2 stream.
To clarify my report, I'm now able to tune to a channel and get a
mpeg2 stream, but it
Vedran Rodic wrote:
Okay, I was using the wrong input number for tuner, it was 4 in
0.3.2d, and now it's 6.
I've briefly tried 0.3.5o, and I get some hiccups in the mpeg2 stream.
To clarify my report, I'm now able to tune to a channel and get a mpeg2
stream, but it seems to have some con
Morten Rønseth wrote:
I just tried 0.3.5n and did "/sbin/modprobe -v ivtv ivtv_std=2
tda9887=0" with same results as with al the other 0.3.5 series, apart
from 0.3.5 itself, which works. I've tried 0.3.5{c,d,g,h,j,n} none of
which work after a cold boot. If I install 0.3.5 cold booting is
Morten Rønseth wrote:
Hi,
Vedran Rodic wrote:
Hello
Version 0.3.2d is the last driver that worked for me in a
configuration with a single PVR 150 MCE PAL card.
I was loading drivers with modprobe like this:
tveeprom
cx25840
tuner
wm8775
ivtv ivtv_std=2 tuner=52
The tuner numbers have ch
On Mon, 30 May 2005, Vedran Rodic wrote:
I've tried 0.3.5f and 0.3.5n, with ivtv_std=2 tda9887=0 tuner=56, or without
tuner= line
In first few tries on 0.3.5n I got standard TV snow/static that happens when
card is not tuned to a valid channel. I've tried various tuners. Tveeprom
reports a
Christian Viller Hansen wrote:
On Mon, 30 May 2005, Vedran Rodic wrote:
Can somebody who is succesfully using 0.3.5 drivers with a single
150MCE PAL card tell me how exactly do they load the drivers and what
firmware they are using?
In /etc/modprobe.conf I have this line:
options ivtv iv
Hi,
Vedran Rodic wrote:
Hello
Version 0.3.2d is the last driver that worked for me in a
configuration with a single PVR 150 MCE PAL card.
I was loading drivers with modprobe like this:
tveeprom
cx25840
tuner
wm8775
ivtv ivtv_std=2 tuner=52
The tuner numbers have changed, so I've just remo
On Mon, 30 May 2005, Vedran Rodic wrote:
Can somebody who is succesfully using 0.3.5 drivers with a single 150MCE PAL
card tell me how exactly do they load the drivers and what firmware they are
using?
In /etc/modprobe.conf I have this line:
options ivtv ivtv_std=2 tda9887=0
The last option
14 matches
Mail list logo
