All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: "Xie, Nick" <nick.xie@festo.com>
Cc: "xenomai@lists.linux.dev" <xenomai@lists.linux.dev>
Subject: Re: Error during libevl build and runtime settings failed
Date: Sat, 13 Sep 2025 16:56:28 +0200	[thread overview]
Message-ID: <87plbuz9ib.fsf@xenomai.org> (raw)
In-Reply-To: <AS8PR03MB100561B2E374D4680213E55DD8B09A@AS8PR03MB10056.eurprd03.prod.outlook.com> (Nick Xie's message of "Thu, 11 Sep 2025 17:14:51 +0000")

"Xie, Nick" <nick.xie@festo.com> writes:

> Hi Philippe,
>
> Thank you for your response. I tried to enable the console output in grub setup, but nothing is showed and it stuck at the same place. 
>
> You mentioned booting over a ramdisk inherited from some
> distro-specific boot setup builder is discouraged. It reminded me that
> the first time I run " sudo make modules_install install ". It failed
> and reported as below. I have to enable "support initial ramdisk/ramfs
> compressed using gzip and zstd option under general setup" to get the
> install done. This is very different from my previous build. I have
> never need to do this. I would redo everything from the beginning and
> see any different. Is 6.12 the correct version I can use with new
> libevl? Do you have other through? Please advise.
>

6.12 is the latest LTS supported by evl, so yes, this may be a good
choice in your case. The grub installation issues you are seeing are not
related to evl which has no influence on the aspects you mentioned, you
would have the same with a plain stock linux kernel. You may want to
refer to other online resources explaining how to build and install a
mainline kernel in place of the one shipped by your linux
distro.

In the early stage of bringing up your target system, you may want to
disable CONFIG_EVL, CONFIG_DOVETAIL and CONFIG_IRQ_PIPELINE options in
your Kconfig, until you get a v6.12 kernel properly booting your box, in
order to rule out any issue with evl.

Once this kernel boots with a working console in order to get the
information you need to progress, then you could enable these options
back one by one in reverse order, discussing on this mailing list any
issue observed while doing so.

-- 
Philippe.

  parent reply	other threads:[~2025-09-13 14:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 16:06 Error during libevl build and runtime settings failed Xie, Nick
     [not found] ` <AM5PR03MB2882F38E95A99A0760C60D1F8B27A@AM5PR03MB2882.eurprd03.prod.outlook.com>
2025-07-31 22:10   ` Xie, Nick
2025-08-01  9:05     ` Philippe Gerum
2025-08-01 14:30       ` Xie, Nick
2025-08-01 15:19         ` Philippe Gerum
2025-09-10 19:54       ` Xie, Nick
2025-09-10 20:35         ` Philippe Gerum
2025-09-11 17:14           ` Xie, Nick
2025-09-11 17:37             ` Xie, Nick
2025-09-13 14:56             ` Philippe Gerum [this message]
2025-09-18 21:58               ` Xie, Nick
2025-09-19  6:18                 ` Jan Kiszka
2025-09-19 16:36                   ` Xie, Nick
2025-09-21 21:26                     ` Xie, Nick
2025-09-24 21:09                       ` Xie, Nick

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=87plbuz9ib.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=nick.xie@festo.com \
    --cc=xenomai@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.