From: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
To: Srishti Sharma <srishtishar@gmail.com>
Cc: linux-iio@vger.kernel.org
Subject: Re: Unknown symbols in module
Date: Wed, 7 Mar 2018 20:25:23 +0000 [thread overview]
Message-ID: <20180307202523.7b84fe6c@archlinux> (raw)
In-Reply-To: <CAB3L5ozYkWv0qO5LrKUHyfXXdRf2RCgAOorHp-DNiKCMzDof6Q@mail.gmail.com>
On Mon, 5 Mar 2018 16:49:24 +0530
Srishti Sharma <srishtishar@gmail.com> wrote:
> Hello,
> I was trying to work with the iio dummy driver, and when I try to load
> the iio_dummy_evgen.ko module I am getting unknown symbols found in
> module error on running modprobe.
>
> These variables are unknown
> iio_bus_type
> irq_sim_init
> irq_sim_fini
> irq_sim_fire
> irq_sim_fini
>
> All of these variables are present in the Module.symvers file in the
> /lib/modules/<kernel version>/build directory. The kernel and the
> modules versions match. I ran make clean, make, and make
> modules_install before trying to load them. I am unable to figure out
> the problem. Where I might be going wrong any ideas ?
The required functions are built into the kernel - there is no option
to build them as a module. As such you'd need to also install the
kernel image in order to be able to probe the module.
The selected to be built when the dummy_evgen module is configured
to be built.
Jonathan
>
> Thanks,
> Srishti
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-03-07 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 11:19 Unknown symbols in module Srishti Sharma
2018-03-07 20:25 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-05 11:17 Srishti Sharma
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=20180307202523.7b84fe6c@archlinux \
--to=jic23@jic23.retrosnub.co.uk \
--cc=linux-iio@vger.kernel.org \
--cc=srishtishar@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.