in tuner.c function set_radio_freq (or something like that) there's a wrong check: if freq <radio_range[1] and freq > radio_range[1] ... the first index must be 0 On Tue, 6 Mar 2001, Eric Jorgensen wrote: > > My bet is that it's the changes to the tuner range checks tweaks, since > any frequency comes back as out of range when you check the logs. > > Currently. the fm tuner on these boards, for some reason, has to be > initialized by setting it to an impossible frequency, such as 500mhz. > Once you've tuned it to 500mhz, it works fine within the normal range. > Before you do that, all you get is static. > > Backleveling to 0.7.57 i can get the fm tuner to work again. > > I would have loved to check to see if setting the ranges via an insmod > option would fix it, but it wasn't listed in Insmod-options and i > couldn't find it in the code. (at least, not in the 10 seconds it took > to decide that I'd rather just backlevel) > > Also, for whatever reason, card=40 doesn't work, I've always had to > specify radio=1 tuner=2 instead. Not a big problem, but maybe the STB2 > definition is simply inappropriate for these cards. > > - Eric > > > > _______________________________________________ > Video4linux-list mailing list > Video4linux-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/video4linux-list >
