Description of problem: Whenever I start /usr/bin/radio (from xawtv-3.88-1) as root, the radio sound mutes for a part of second and then goes on and in the logs the following line appears : tuner: radio freq (400.00) out of range (65-108) ( after starting /usr/bin/radio , I leave it with 'x' , so it leaves the sound playing ) Version-Release number of selected component (if applicable): xawtv-3.88-1 kernel-2.4.20-1.1988-athlon How reproducible: Steps to Reproduce: 1. run radio 2. select a channel 3. leave with the 'x' key , so the sound keeps playing 4. start radio again Actual results: The sound "blurps" ( becomes muted ) for a part of second and the mentioned message appears in the log Expected results: nothing of the above Additional info:
Do you have this problem in old xawtv (3.81) ? >Whenever I start /usr/bin/radio (from xawtv-3.88-1) as root, the radio sound >mutes for a part of second and then goes on and in the logs the following line >appears : >tuner: radio freq (400.00) out of range (65-108) >( after starting /usr/bin/radio , I leave it with 'x' , so it leaves >the sound playing ) is this problem gone if you restart it again?
I discovered ( by adding an "exit(1)" right after the "open()" in radio.c ) that this happens whenever /dev/radio is opened, so it seems to be a driver problem. Simple test : [root@slave6 xawtv-3.88]# cat /dev/radio tuner: radio freq (400.00) out of range (65-108) cat: /dev/radio: Invalid argument If radio is playing when the "cat" is run , the sound is muted for a part of second. This happens also with other kernels : 2.4.20-20.1.2002.nptl - athlon bttv: driver version 0.7.104 loaded Shrike ( RHL 9 ) : kernel 2.4.20-8 athlon bttv: driver version 0.7.96 loaded Same on Psyche ( RHL 8.0 ) : kernel 2.4.18-18.8.0 athlon bttv: driver version 0.7.91 loaded
i assign it to correct to correct component
Looks like the radio powers up at a bogus frequency and the driver doesnt handle this corner case. You might want to drop a note about it to video4linux-list
What do you mean by "powers up" ? This happens way after power up. And the this is not some weird state of the tuner HW. The tuner HW is just fine ( playing the channel I selected before ). It is the driver explicitly calling its own channel tuning function to tune to an "out-of-range" frequency. I posted to video4linux-list and received zero response :-(
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/