On Monday, 1 August 2016 12:18:11 CEST you wrote: > Package: radio > Version: 3.103-4+b1 > Severity: normal > > --- Please enter the report below this line. --- > > Using in with Pinnacle PC-TV 110i tuner (SAA7143 based). It corrrectly shows > the band frequency range: > alex@bootes:~$ radio -b ? > Possible band values: > 1. FM 65,00 - 108,00 MHz > but on attempt to scan it starts from some weird number: > alex@bootes:/etc/modprobe.d$ radio -s > Scanning: 1,04 MHz - 43008
You need to call it with -b 1 > Also, when trying to set the frequency manually it initially works (I can > hear the station!) but then the app closes with the following: > alex@bootes:~$ radio -f 104,5 > Tuning to 104,50 MHz > Invalid freq '1672000'. Current freq out of range? Mmh, that shouldn't happen, but it's also triggered by not calling it with -b 1. The frequencies have a factor modifier (16000), and radio reads the frequency back from the hardware after setting it, I guess your radio driver is reporting back a value with the factor modifier applied twice. > (And who the hell use this pertified mammoth crap anyways? Is it really > needed to be mantained?) This kind of comments will get you far. If you don't want to use it, no one is forcing you. Happy hacking, -- "If I ask another professor what he teaches in the introductory programming course, whether he answers proudly "Pascal" or diffidently "FORTRAN," I know that he is teaching a grammar, a set of semantic rules, and some finished algorithms, leaving the students to discover, on their own, some process of design." -- Robert W. Floyd Saludos /\/\ /\ >< `/
signature.asc
Description: This is a digitally signed message part.

