From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: ycollette.nospam@free.fr
Cc: nando@ccrma.Stanford.EDU,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: v5.6.17 (was v5.4.17-rt10) does not boot on intel
Date: Thu, 25 Jun 2020 09:55:25 -0700 [thread overview]
Message-ID: <79b3de69-0a62-0591-a7c0-e5c24fa6cd4e@ccrma.stanford.edu> (raw)
In-Reply-To: <238119586.495839939.1592647783365.JavaMail.root@zimbra35-e6.priv.proxad.net>
On 6/20/20 3:09 AM, ycollette.nospam@free.fr wrote:
> Hello,
(best if you start a new thread or change the subject line)
> I am trying to build the last RT kernel on Fedora.
>
> So, I've downloaded linux-5.6.17 and the last rt patch from kernel.org
> I apply the RT patch to the linux sources.
> I clone https://src.fedoraproject.org/rpms/kernel.git and checked out to f32 branch
> I run $ ./build_configs.sh linux-5.6.17
> I copy linux-5.6.17.x86_64-fedora.config as .config in the linux-5.6.17 directory.
> Then, I do a make xconfig
> I check "General Setup -> Configure standard kernel features (expert users)" to be able to check "Fully preemptible kernel".
> I save the conf and copy the .config file to be able to build the kernel via a spec file.
>
> I used to build regularly the RT kernel via this procedure (the check "General Setup -> Configure standard kernel features (expert users) is new to 5.6) and it was working fine with 5.4 kernels. Now, the installed kernel doesn't boot.
Any errors?
> Is there something new I am missing to be able to boot the kernel ?
>
> Maybe it's the options selected by the fedora script which have a problem.
> I doesn't apply any patches to the RT kernel. I just wanted a "vanilla RT kernel" with fedora options but without fedora patches.
Hmmm, I just built a 5.6.17-rt10 for Fedora 32 a couple of days ago and
it boots on one system I have here (Intel I7 8559U processor, a small
NUC mobo in a fanless case). I based it on this .src.rpm (from Koji):
kernel-5.6.17-300.fc32.src.rpm
I don't remember doing anything different from previous versions (it is
now in the Planet CCRMA repo).
-- Fernando
next prev parent reply other threads:[~2020-06-25 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 16:58 [ANNOUNCE] v5.4.17-rt9 Sebastian Andrzej Siewior
2020-02-06 23:59 ` Fernando Lopez-Lezcano
2020-02-07 6:11 ` Mike Galbraith
2020-02-07 6:13 ` Fernando Lopez-Lezcano
2020-02-07 6:56 ` Mike Galbraith
2020-06-20 10:09 ` v5.4.17-rt10 does not boot on intel ycollette.nospam
2020-06-20 12:35 ` ycollette.nospam
2020-06-25 16:55 ` Fernando Lopez-Lezcano [this message]
2020-02-12 10:20 ` [ANNOUNCE] v5.4.17-rt9 Sebastian Andrzej Siewior
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=79b3de69-0a62-0591-a7c0-e5c24fa6cd4e@ccrma.stanford.edu \
--to=nando@ccrma.stanford.edu \
--cc=linux-rt-users@vger.kernel.org \
--cc=ycollette.nospam@free.fr \
/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).