Red Hat Bugzilla – Bug 187270
kernel error for maestro radio driver, found in /var/log/messages
Last modified: 2015-01-04 17:26:17 EST
Description of problem:
New install of FC5 on a Dell Latitude CPx laptop. Found these entries in
Mar 26 14:16:02 discsander kernel: videodev: "Maestro radio" has no release
callback. Please fix your driver for proper sysfs support, see
Mar 26 14:16:02 discsander kernel: maestro_radio: probe of 0000:00:08.0 failed
with error -5
Version-Release number of selected component (if applicable):
Linux discsander.slh.lan 2.6.15-1.2054_FC5 #1 Tue Mar 14 15:48:33 EST 2006 i686
i686 i386 GNU/Linux
This problem has been in place since loading FC5 on this laptop.
Steps to Reproduce:
1. Load FC5
2. Boot system
Error message as indicated above.
Message indicates this driver has an error and should be corrected.
Not sure what this driver is for or which package loads it. As far as I can
tell I don't need this driver. Other than the error message I can do with out
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
This bug has been mass-closed along with all other bugs that
have been in NEEDINFO state for several months.
Due to the large volume of inactive bugs in bugzilla, this
is the only method we have of cleaning out stale bug reports
where the reporter has disappeared.
If you can reproduce this bug after installing all the
current updates, please reopen this bug.
If you are not the reporter, you can add a comment requesting
it be reopened, and someone will get to it asap.