* Status of Xenomai-images @ 2023-09-01 13:26 Per Oberg 2023-09-01 13:34 ` Jan Kiszka 0 siblings, 1 reply; 5+ messages in thread From: Per Oberg @ 2023-09-01 13:26 UTC (permalink / raw) To: xenomai 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 ? [1] https://source.denx.de/Xenomai/xenomai-images Per Öberg ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Status of Xenomai-images 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 0 siblings, 1 reply; 5+ messages in thread From: Jan Kiszka @ 2023-09-01 13:34 UTC (permalink / raw) To: Per Oberg, xenomai 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 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Status of Xenomai-images 2023-09-01 13:34 ` Jan Kiszka @ 2023-09-01 13:44 ` Per Oberg 2023-09-01 13:48 ` Jan Kiszka 0 siblings, 1 reply; 5+ messages in thread From: Per Oberg @ 2023-09-01 13:44 UTC (permalink / raw) To: Jan Kiszka; +Cc: xenomai ----- 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 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Status of Xenomai-images 2023-09-01 13:44 ` Per Oberg @ 2023-09-01 13:48 ` Jan Kiszka 2023-09-01 13:50 ` Per Oberg 0 siblings, 1 reply; 5+ messages in thread From: Jan Kiszka @ 2023-09-01 13:48 UTC (permalink / raw) To: Per Oberg; +Cc: xenomai On 01.09.23 15:44, Per Oberg wrote: > > ----- 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. ...or we lack USB support in the kernel built-in or as modules in the initrd so that your USB stick can be found. That may be a matter of tuning the x86 defconfig in use. Jan -- Siemens AG, Technology Linux Expert Center ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Status of Xenomai-images 2023-09-01 13:48 ` Jan Kiszka @ 2023-09-01 13:50 ` Per Oberg 0 siblings, 0 replies; 5+ messages in thread From: Per Oberg @ 2023-09-01 13:50 UTC (permalink / raw) To: Jan Kiszka; +Cc: xenomai ----- Den 1 sep 2023, på kl 15:48, Jan Kiszka <jan.kiszka@siemens.com> skrev: > On 01.09.23 15:44, Per Oberg wrote: > > ----- 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. > ...or we lack USB support in the kernel built-in or as modules in the > initrd so that your USB stick can be found. That may be a matter of > tuning the x86 defconfig in use. > Jan > -- > Siemens AG, Technology > Linux Expert Center Per Öberg Wolfram MathCore AB Teknikringen 1E SE-583 30 Linköping Sweden Cellphone: +46 76 877 89 70 Phone: +46 85 592 16 41 Please visit us at: [ http://www.wolframmathcore.com/ | wolframmathcore.com ] or [ http://www.wolfram.com/ | wolfram.com ] ----- Den 1 sep 2023, på kl 15:48, Jan Kiszka jan.kiszka@siemens.com skrev: > On 01.09.23 15:44, Per Oberg wrote: > > ----- 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. > ...or we lack USB support in the kernel built-in or as modules in the > initrd so that your USB stick can be found. That may be a matter of > tuning the x86 defconfig in use. > Jan > -- > Siemens AG, Technology > Linux Expert Center Yes, right again. I have no keyboard either. Regards Per Öberg ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2023-09-01 13:50 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 2023-09-01 13:48 ` Jan Kiszka 2023-09-01 13:50 ` Per Oberg
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.