to my (current) knowledge, this bug is not an issue of the V4L1 API dropped in recent Linux kernels, since particularly KRadio supports V4L2. Furthermore, even mplayer does not solve the problems on such systems.
Those V4L2 drivers seem to report an invalid frequency range (0 to 0 Hz).
The problem seems to be at least narrowed down on the LKML since November 2011:
... unfortunately without answers to those posts on the LKML yet.
Therefore, I'd propose to consider this bug as a kernel bug - unfortunately without any clue how to further approach a solution of this issue.