From: Nathanael J Grix <NathGri@protonmail.com>
To: "Valentin Vidić" <vvidic@valentin-vidic.from.hr>
Cc: "kernelnewbies@kernelnewbies.org" <kernelnewbies@kernelnewbies.org>
Subject: Re: Trouble Installing Compiled Kernel
Date: Wed, 25 Mar 2020 16:52:27 +0000 [thread overview]
Message-ID: <2CGS-_atyMzfsMUUgV3lKqkjxpssMPovJURnMpI8_LjDBzP1iFrlzP6pTI4BWSvbELGqWq3Qtkzddv2zI8JByJBiaOD0x3a7eoxu-IchXR0=@protonmail.com> (raw)
In-Reply-To: <20200325163804.GD11863@valentin-vidic.from.hr>
On Wednesday, March 25, 2020 12:38 PM, Valentin Vidić <vvidic@valentin-vidic.from.hr> wrote:
> On Wed, Mar 25, 2020 at 04:22:47PM +0000, Nathanael J Grix wrote:
>
> > After getting it compiled I ran:
> > bash-4.3$ sudo make O=/home/nathanael/KernelBuild/ install_module install
>
> This should be modules_install.
>
> ----------------------------------
>
> Valentin
>
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Sorry, that was just a typo I believe that I used modules_install and not install_module. I ran it again with modules_install just to be sure and still got the same error message:
bash-4.3$ make O=/home/nathanael/Kernel-5.6.0/ install_modules install
make[1]: Entering directory '/home/nathanael/Kernel-5.6.0'
make[1]: *** No rule to make target 'install_modules'. Stop.
make[1]: Leaving directory '/home/nathanael/Kernel-5.6.0'
Makefile:180: recipe for target 'sub-make' failed
make: *** [sub-make] Error 2
If you have any other suggestions or resources that would be much appreciated. Thanks.
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-03-25 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 16:22 Trouble Installing Compiled Kernel Nathanael J Grix
2020-03-25 16:38 ` Valentin Vidić
2020-03-25 16:52 ` Nathanael J Grix [this message]
2020-03-25 17:00 ` Nathanael J Grix
2020-03-25 16:52 ` Marcelo Diop-Gonzalez
2020-03-27 10:42 ` Vishal Thanki
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='2CGS-_atyMzfsMUUgV3lKqkjxpssMPovJURnMpI8_LjDBzP1iFrlzP6pTI4BWSvbELGqWq3Qtkzddv2zI8JByJBiaOD0x3a7eoxu-IchXR0=@protonmail.com' \
--to=nathgri@protonmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=vvidic@valentin-vidic.from.hr \
/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).