From: Per Oberg <pero@wolfram.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: xenomai@lists.linux.dev
Subject: Re: Status of Xenomai-images
Date: Fri, 1 Sep 2023 08:44:31 -0500 (CDT) [thread overview]
Message-ID: <955481814.1525807.1693575870993.JavaMail.zimbra@wolfram.com> (raw)
In-Reply-To: <926e7876-c2b0-43eb-91b7-7b7f969ab208@siemens.com>
----- Den 1 sep 2023, på kl 15:34, Jan Kiszka jan.kiszka@siemens.com skrev:
> On 01.09.23 15:26, Per Oberg wrote:
> > Hello list
>> I just tried out the xenomai-images [1] but I couldn't make the images boot on
> > my hardware. The qemu variants worked.
>> I used "kas-container menu" without any changes and tried a few combinations
> > like
> > * Generic x86-64 EFI target
> > * Latest 3.2.x release / Head of stable/v3.2.x branch
>> * Latest 4.19-cip I-pipe version / Latest 5.4 I-pipe version / Latest 5.10
> > Dovetail version
>> The hardware I tried so far were PCs with intel core i3 or AMD Ryzen based
>> architectures. I managed to get my USB stick flashed with the wic-file and boot
>> into grub. But then it hung with a blinking cursor when trying to boot the
> > linux kernel.
> > Am I making some sort of silly mistake ?
> Maybe framebuffer output is not working, and you are only "seeing" boot
> messages on the UART then.
> Not sure if we allow for an interactive grub session, but you could try
> adjusting the kernel command line there to use console=tty0 instead of
> ttyS. If that was the reason, we should likely fix something.
> Jan
> --
> Siemens AG, Technology
> Linux Expert Center
Yes, that was it.
Completely removing console=ttyS0 showed me the regular linux boot.
But then it got stuck in initrd because it couln't find the root partition.
Seems to be looking for the wrong uuid.
Per Öberg
next prev parent reply other threads:[~2023-09-01 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 13:26 Status of Xenomai-images Per Oberg
2023-09-01 13:34 ` Jan Kiszka
2023-09-01 13:44 ` Per Oberg [this message]
2023-09-01 13:48 ` Jan Kiszka
2023-09-01 13:50 ` Per Oberg
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=955481814.1525807.1693575870993.JavaMail.zimbra@wolfram.com \
--to=pero@wolfram.com \
--cc=jan.kiszka@siemens.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.