From: drbob <drbob@gmx.co.uk>
To: linux-media@vger.kernel.org
Subject: Re: EC168 "dvb_usb: Unknown symbol release_firmware"
Date: Tue, 5 May 2009 01:55:59 +0000 (UTC) [thread overview]
Message-ID: <gto6be$f0e$1@ger.gmane.org> (raw)
In-Reply-To: 49FF7BAD.7010108@rogers.com
On Mon, 04 May 2009 19:35:09 -0400, CityK wrote:
> drbob,
>
> Off_Topic: that name takes me back: http://muppet.wikia.com/wiki/Dr._Bob
And I thought I'd picked that name at random. The muppets must have had a
deeper effect on my subconscious than I realised...
>
> On_Topic: You have built the drivers but you haven't installed them
> into the system as intended, consequently you will run into the set of
> observations that you have. Have a read through:
> http://www.linuxtv.org/wiki/index.php/How_to_Obtain%
2C_Build_and_Install_V4L-DVB_Device_Drivers
Thanks for the link. It put me on the right track. I needed to load the
"firmware-class" kernel module before dvb-usb - modprobe resolves module
dependencies automatically, insmod does not. dvb-usb also relies on
i2c_core but that was already loaded on my system.
So to manually load the ec168 modules I need to execute:
sudo modprobe firmware-class
Bdefore the the insmod commands.
For testing purposes I wanted to explicity load the new modules with
insmod rather than install them and overwrite all the modules included
with the kernel, which I know have been passed as stable. That seemed
more sensible than the course of action suggested by the wiki article.
next prev parent reply other threads:[~2009-05-05 1:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 20:28 EC168 "dvb_usb: Unknown symbol release_firmware" drbob
2009-05-04 23:35 ` CityK
2009-05-05 1:55 ` drbob [this message]
2009-05-05 10:47 ` Antti Palosaari
2009-05-05 15:41 ` drbob
2009-05-05 17:07 ` drbob
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='gto6be$f0e$1@ger.gmane.org' \
--to=drbob@gmx.co.uk \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox