[pvrusb2] problem with a hvr-1900

Steffje steffje at web.de
Tue Sep 14 17:39:27 CDT 2010


Hi Tomas,
I had a similar problem with my hvr1900.
The tuner part was defect, and so I made a warranty exchange.
The new card works as it should.
I have tested the card with Windo** to be sure its defect.

Steffje

On Saturday 11 September 2010, Tomas Hylander wrote:
> The television-part still dont work tho. tried changing the frequency as
> above and it worked (cat ctl_frequency/cur_val) but there's no change in
> the picture.
> I know its the right frq since it works on my old pvr-350.
>
> So I guess there IS something wrong with the tuner-part...but how can I
> continue diagnostics?
>
> How do I upgrade my linux core? as mentioned above.
> /Tomas
>
> 2010/9/11 Mike Isely <isely at isely.net>
>
> > On Fri, 10 Sep 2010, Tomas Hylander wrote:
> > > strange, even if it says that root was the owner I coulnt do anything.
> > > Changed so all could read and write so now it works, sort of...
> >
> > (see previous reply)
> >
> > > I can change inputs and so but now Im only getting black...
> > > Tried changing to s-video and connected from my sat but still black.
> > > Changed back to television but still black...
> > > Tried changing frequency with
> > >
> > > sudo echo "210.250" >ctl_frequency/cur_val
> > > echo: write error: Invalid argument
> >
> > That didn't work because an integer value is expected ("." is not a
> > legal character).
> >
> > > sudo echo "210250" >ctl_frequency/cur_val
> > > echo: write error: Numerical result out of range
> >
> > And that didn't work because the frequency is expected in units of Hz,
> > not KHz (or MHz which you first had tried).  It interpreted what you
> > entered as 210250 Hz and complained that the value was outside the
> > allowed range of the tuner (far too low).  You were getting close with
> > your second attempt - you just gave up too soon.
> >
> > > How do I enter the frequency?
> >
> > This should work (just scale it up to the right units):
> >
> > echo 210250000 >ctl_frequency/cur_val
> >
> > > Looks strange thats I just getting black...no noise.
> >
> > Right, so the fact that you are getting data at all means that the video
> > pipeline is probably working but you don't have a signal to lock onto
> > because it's not tuned correctly.
> >
> >  -Mike
> >
> > --
> >
> > Mike Isely
> > isely @ isely (dot) net
> > PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
> > _______________________________________________
> > pvrusb2 mailing list
> > pvrusb2 at isely.net
> > http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
>
> _______________________________________________
> pvrusb2 mailing list
> pvrusb2 at isely.net
> http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2


More information about the pvrusb2 mailing list