From: Ralf Mardorf <ralf.mardorf@alice-dsl.net>
To: linux-rt-users@vger.kernel.org
Subject: Re: Building 4.9 RT kernel help
Date: Mon, 26 Dec 2016 21:40:46 +0100 [thread overview]
Message-ID: <1482784846.9839.1.camel@alice-dsl.net> (raw)
In-Reply-To: <20161226212405.7758bea5@archlinux.localdomain>
On Mon, 2016-12-26 at 21:24 +0100, Ralf Mardorf wrote:
> On Mon, 26 Dec 2016 15:01:01 -0500, Vasiliy Gagin wrote:
> > I was able to build plain kernel v4.9.
> > It builds v4.9-rt1 fine too, but fails when I try to install it.
> >
> > console message is
>
> Message of what?
>
> Did you try to install packages, perhaps a linux package, before a
> linux-header package was installed?
>
> > run-parts: executing /etc/kernel/postinst.d/dkms 4.9.0-rt1
> > /boot/vmlinuz-4.9.0-rt1
> > Error! Bad return status for module build on kernel: 4.9.0-rt1 (x86_64)
> >
> > and there is following in make.log
> >
> > KMS make.log for open-vm-tools-9.4.6 for kernel 4.9.0-rt1 (x86_64)
> > Mon Dec 26 14:09:03 EST 2016
> > /bin/sh: 1: test: -I./arch/x86/include: unexpected operator
> > Using standalone build system.
> > Makefile:167: Makefile.normal: No such file or directory
> > make[3]: *** No rule to make target 'Makefile.normal'. Stop.
> > /bin/sh: 1: test: -I./arch/x86/include: unexpected operator
> > Using standalone build system.
> > Makefile:167: Makefile.normal: No such file or directory
> > make[3]: *** No rule to make target 'Makefile.normal'. Stop.
> >
> > I'm very new to the linux building process. Please Help
>
> There seems to be a DKMS hook. DKMS fails to build kernel modules. The
> kernel itself and all other modules might be installed, just some
> custom modules perhaps failed to build.
>
> I build 4.9-rt1 without issues and had also good luck with DKMS. It was
> able to build vbox modules.
>
> $ ls -hAl /lib/modules/4.9.0-rt1-1-rt-presonus/kernel/misc/ total 688K
> -rw-r--r-- 1 root root 582K Dec 24 08:14 vboxdrv.ko
> -rw-r--r-- 1 root root 16K Dec 24 08:14 vboxnetadp.ko
> -rw-r--r-- 1 root root 41K Dec 24 08:14 vboxnetflt.ko
> -rw-r--r-- 1 root root 39K Dec 24 08:14 vboxpci.ko
>
> However, sometimes DKMS can't build those modules, but then the kernel
> still could be used, just vbox doesn't work with this kernel.
>
> In your case, KMS is something graphics related and you seemingly use
> VMware.
Hahaha :D, pardon, "KMS" most likely is from "DKMS", just the "K" is
missing. But, the rest still might be correct. Did you try to boot the
kernel? I suspect it is installed, just running VMware might fail.
Assuming just a header package wasn't installed, simply reinstall the
kernel package, after the the headers are installed, or run DKMS
manually from command line.
> Again, perhaps a linux-header package wasn't installed and after
> installing the linux package DMKS was missing headers.
>
> Regards,
> Ralf
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2016-12-26 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 20:01 Building 4.9 RT kernel help Vasiliy Gagin
2016-12-26 20:24 ` Ralf Mardorf
2016-12-26 20:40 ` Ralf Mardorf [this message]
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=1482784846.9839.1.camel@alice-dsl.net \
--to=ralf.mardorf@alice-dsl.net \
--cc=linux-rt-users@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).