Replies: 3 comments 9 replies
-
|
u-boot is not really needed if system supports UEFI and can then boot a normal iso, from the video it seems the partitioning failed
|
Beta Was this translation helpful? Give feedback.
2 replies
-
|
I don't have exact details, but it looks like Talos thinks that the disk is too small |
Beta Was this translation helpful? Give feedback.
-
|
Hey folks, thanks for the blazing-fast answers :-) I dove a little bit deeper yesterday night and Maybe I just need to set Thanks for the support, fingers crossed ;-) |
Beta Was this translation helpful? Give feedback.
-
|
Quick update from my side: Booting Talos 1.6.4. from USB-key with UEFI/ACPI on Jetson Linux Firmware and installing it to an attached NVMe is working fine! So far I found two things that are not working
If anybody is interested, I attached the dmesg logs from a fresh boot after the cluster has been bootstrapped. I will do some further testing, maybe also check out the firmware of L4T 36.2 DP as this states "Flexibility to bring any upstream Linux Kernel" as a feature. Can anybody estimate how the chances would be to enable hardware support for the Tegra GPU via nvidia-container-runtime from here on? Would be happy about any hint. Cheers |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
if the nonfree/free nvidia drivers support this platform, enabling the nvidia-container extension should be good enough
Definitely ACPI, would recommend testing newer L4T
This data comes from smbios and i guess ARM UEFI firmware doesn't report all |
Beta Was this translation helpful? Give feedback.
-
|
Hi @frezbo Thanks for the fast response again! Not really sure if this is going to work out of the box with these extensions. I guess GPU passthrough with L4T is working differently than with standard GPUs. Is the Tegra GPU working on Jetson Nano devices under Talos (with nvidia-container-runtime) or did it just have CPU support? Kind regards |
Beta Was this translation helpful? Give feedback.
-
|
My findings of the day:
Where the I see two problems here: b. Currently with UEFI/ACPI most of the devices are not available (see the ls of the If I get it right, the required steps for compatibility would be
Did I miss something? Cheers P.S.: For comparison you can see the |
Beta Was this translation helpful? Give feedback.
5 replies
-
shouldn't be since it's a different runtimeclass and talos doesn't use those, might be something else
yeh probably needs some work and maybe can use the new
yeh, might also need enabling some extra kernel config |
Beta Was this translation helpful? Give feedback.
-
|
Ok, then I'll put further investigation on the problem with the image with the nvidia extensions. Unfortunately getting the kernel logs isn't really easy beside fotos/videos or am I missing an option here (api isn't working at this point)? Thanks for the hint regarding the ExtensionServiceConfig. I guess you mean that I could use this to overwrite the existing Regarding the Kernel Modules: Do you mean Nvidia Jetson/Tegra specific Kernel Modules or rather ACPI related Modules? It seems like Nvidia is commiting its patches to the upstream linux kernel as stated here . Jetson Orin is Is the "vanilla" Talos kernel built with the same config stated in this repo or are some of the modules not enabled to keep it small? Thanks again for the support! |
Beta Was this translation helpful? Give feedback.
-
|
I think this work can now be overlay if need be https://www.talos.dev/v1.7/advanced/overlays/ |
Beta Was this translation helpful? Give feedback.
-
This needs enabling in talos kernel |
Beta Was this translation helpful? Give feedback.
-
|
Hi @frezbo, thanks for the hints. I will check this out as soon as I'll come back to this topic. Regards |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there,
at first: a huge "thanks" to all maintainers of this great project. Just started using Talos and really got a great start so far (tested it on Docker, Proxmox and Hetzer Cloud so far and everything worked out great).
I saw that Nvidia Jetson Nano is supported as well and found this topic regarding support of the Jetson Xavier NX: #7124
I'm using a Jetson Orin AGX based System (not the DevKit, but a Custom Design) and was curious if it could run Talos as well. Regarding general support of SBCs it is stated, that there need to be upstream u-boot support (which isn't available for Jetson Orin AFAIK). But could UEFI/GRUB be an option here?
Jetson Orin uses UEFI and GRUB can be used as well. So I just gave it a try with the latest Talos Metal ISO (https://github.com/siderolabs/talos/releases/download/v1.6.4/metal-arm64.iso) and successfully booted it from an USB-Stick. I had L4T 35.3.1. installed and at first successfully booted a Live ISO of Fedora (following this guide https://forums.developer.nvidia.com/t/fedora-on-jetson-agx-orin/254293), then I tried it with the Talos USB-Stick and it booted directly und network was working as well (all I had to do is enable
ACPIin the UEFI underO/S Hardware Description).talosctl apply-config ...was recognized successfully as well but after the reboot the system didn't get up again. Furthermore I couldn't boot from the USB-Stick afterwards until I flashed it again und my L4T installation seemed to be broken as well.Here you'll find a video of the boot process: https://youtu.be/d-EZY0h2G9U
The logs show, that after applying the config, the installation process seems to be starting. It tries to reset the partition table of
/dev/sda(defined in thecontrolplane.yaml) but fails and it seems like the 16GB USB-Stick itself is attached here. Is there a way to check the attached devices before applying the controlplane config without ssh? Triedtalosctl -n 10.1.100.170 listbut that didn't work.Anyways, do you see any chance getting Talos running on Jetson Orin after my first success?
I'm completely new into the Linux Boot Process and it would be great if somebody could point me a proper direction / next steps at this point. Ideally I could even get the GPU running at a later point!?
Here are a few References regarding the Boot Process under L4T r35.4.1
https://docs.nvidia.com/jetson/archives/r35.4.1/DeveloperGuide/text/AR/BootArchitecture/JetsonOrinSeriesBootFlow.html
https://docs.nvidia.com/jetson/archives/r35.4.1/DeveloperGuide/text/SD/Bootloader.html
https://docs.nvidia.com/jetson/archives/r35.4.1/DeveloperGuide/text/SD/Bootloader/UEFI.html
https://docs.nvidia.com/jetson/archives/r35.4.1/DeveloperGuide/text/SD/Bootloader/UEFI.html#grub-support
Kind regards
Beta Was this translation helpful? Give feedback.
All reactions