Red Hat Bugzilla – Bug 230897
Recent kernels remove v4l API- fmio doesn't support v4l2
Last modified: 2008-02-07 23:29:18 EST
Description of problem:
FM Radio tools rely on V4L API which has been removed from recent kernels.
Bug is not really kernel- other tools need updating to keep pace.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Upgrade FC5 to a recent kernel (noticed on 2.6.19, v4l docs suggest >2.6.15)
2. Plug in a USB FM tuner.
3. Kernel supports tuner, creates /dev/radio*
4. Run fmio to control a FM radio tuner via V4L drivers
5. IOCTL error
3. Kernel creates /dev/radio? correctly and logs in /var/log/messages:
Mar 4 09:28:27 foobar kernel: drivers/media/radio/dsbr100.c: v0.41:D-Link
4. IOCTL error from kernel as it only supports V4L2 after original V4L call has
$ fmio -d v4l 92.9
fmio: VIDIOCGTUNER: Invalid argument
fmio: card not found: Video4Linux Driver
5. No sound!
V4L2 DSB-R100 USB FM radio driver loads and works.
Radio tunes to station and plays.
Looks like recent kernels have removed the orignal V4L API and now only support
V4L2. This link suggests this happened >2.6.15:
fmio and serveral other FM radio userspace tuner programs appear to use the V4L
API which has been removed.
For example, the error above looks to me caused by using IOCTL VIDIOCGTUNER from
V4L rather than the new VIDIOC_G_TUNER for V4L2:
gnomeradio-1.6-3.fc5 doesn't work either, although this could be down to the
'mixer source' setting containing garbage.
(This is a mass-update to all current FC6 kernel bugs in NEW state)
I'm reviewing this bug list as part of the kernel bug triage project, an attempt
to isolate current bugs in the Fedora kernel.
I am CC'ing myself to this bug, however this version of Fedora is no longer
Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.
Thanks for using Fedora!
Per the previous comment in this bug, I am closing it as INSUFFICIENT_DATA,
since no information has been lodged for over 30 days.
Please re-open this bug or file a new one if you can provide the requested data,
and thanks for filing the original report!