Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1503851 > unrolled thread
| Started by | Alban Browaeys <alban.browaeys@gmail.com> |
|---|---|
| First post | 2016-10-19 17:20 +0200 |
| Last post | 2016-10-19 17:20 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Unable to boot linux-next build Alban Browaeys <alban.browaeys@gmail.com> - 2016-10-19 17:20 +0200
| From | Alban Browaeys <alban.browaeys@gmail.com> |
|---|---|
| Date | 2016-10-19 17:20 +0200 |
| Subject | Re: Unable to boot linux-next build |
| Message-ID | <su0OR-308-3@gated-at.bofh.it> |
Le dimanche 11 septembre 2016 à 20:00 +0200, Quentin Lambert a écrit :
>
> On 09/09/2016 10:31, Quentin Lambert wrote:
> > I have been trying to build and boot the last version available
> > on linux-next.
> > During the build I am being prompted with "has no CRC!" warnings
> > for a bunch
> > of modules.
There is a thread about this issue, with patches on the list (lkml)
titled "[GIT PULL] kbuild changes for v4.9-rc1" starting on Mon, 17 Oct
2016, with initial author "Michal Marek".
To sum up, you could disable CONFIG_MODVERSIONS in your config or
downgrade binutils to <= 2.26 or revert 784d5699eddc ("x86: move
exports to actual definitions") or apply the two patches from the
above thread if on x86:
- first one : from Nicholas Piggin for all archs:
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1250340.htm
l
- second from Adam Borowski , x86 specific bits :
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1250599.htm
l
Back to top | Article view | linux.kernel
csiph-web