From: Praveen Kumar <kpraveen.lkml@gmail.com>
To: Aruna Hewapathirane <aruna.hewapathirane@gmail.com>
Cc: Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: /proc/modules not showing any output
Date: Wed, 19 Dec 2018 21:47:46 +0530 [thread overview]
Message-ID: <CABcWhv7og6-MqXgo9X=huachKo5gHV+S-GBLW6mhHUXmwkdW+A@mail.gmail.com> (raw)
In-Reply-To: <CAFSeFg9dyKEry_pbnn7395nFtOYixbgYuAunvoNa5roe9dVUTQ@mail.gmail.com>
On Wed, Dec 19, 2018 at 9:28 PM Aruna Hewapathirane
<aruna.hewapathirane@gmail.com> wrote:
>
> <snip>
>>
>> I think, on my test machine, by default, there are many modules which
>> get added during boot up, which with vanilla kernel is not happening.
>> Thanks for your input.
>>
>> Regards,
>>
>> ~Praveen.
>>
>
> What does lsmod show you in the vanilla kernel ? If you want the same modules to load in the vanilla
> kernel folow steps given below:
>
> 1 -boot into the older 4.4.162-78-defaultkernel
> 2 - change into the vanilla kernel source 4.20.0-rc6 builddirectory
> 3 - $ lsmod > lsmod.txt
> 4 - $ make LSMOD="lsmod.txt" localmodconfig
>
> Boot into your newly compiled vanilla kernel and run lsmod and smile :-)
>
> Hope this helps - Aruna
>
Thanks Aruna. This helps.
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2018-12-19 16:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 13:22 /proc/modules not showing any output Praveen Kumar
2018-12-19 15:06 ` Greg KH
2018-12-19 15:31 ` Praveen Kumar
2018-12-19 15:57 ` Aruna Hewapathirane
2018-12-19 16:17 ` Praveen Kumar [this message]
2018-12-19 16:34 ` Aruna Hewapathirane
2018-12-20 4:28 ` Praveen Kumar
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='CABcWhv7og6-MqXgo9X=huachKo5gHV+S-GBLW6mhHUXmwkdW+A@mail.gmail.com' \
--to=kpraveen.lkml@gmail.com \
--cc=aruna.hewapathirane@gmail.com \
--cc=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).