Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jetson orin not booting up #2467

Closed
nianyush opened this issue Apr 12, 2024 · 6 comments
Closed

Jetson orin not booting up #2467

nianyush opened this issue Apr 12, 2024 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@nianyush
Copy link

After resolving the issue in #2461, it still stuck in boot up process. Not able to login and collect logs
image

@nianyush nianyush added bug Something isn't working triage Add this label to issues that should be triaged and prioretized in the next planning call unconfirmed labels Apr 12, 2024
@mudler
Copy link
Member

mudler commented Apr 12, 2024

@nianyush can you reproduce this with the kairos images too?

Also, can you collect logs from the serial?

@jimmykarily
Copy link
Contributor

@jimmykarily
Copy link
Contributor

relevant? https://forums.developer.nvidia.com/t/orin-nano-wont-boot-lt4launcher-attempting-recovery-boot/255302/4

meh... not. It seems that ours is booting into palette.

@mudler
Copy link
Member

mudler commented Apr 13, 2024

seems we moved the iscsi.conf from the framework image to: https://github.com/kairos-io/packages/blob/99dec691da2d34468e2fcf2e14d3b9d388848da4/packages/static/kairos-overlay-files/files/system/oem/12_nvidia.yaml#L8

image (14)

However, the dracut configuration is needed while building the initramfs (and has to be added into the framework image)

@nianyush for the orin you might need to add a patch in the meantime in your Dockerfiles:

echo 'omit_dracutmodules+=" iscsi "' > /etc/dracut.conf.d/iscsi.conf

before generating the initramfs with dracut

@jimmykarily jimmykarily removed the triage Add this label to issues that should be triaged and prioretized in the next planning call label Apr 15, 2024
@ci-robbot ci-robbot added the triage Add this label to issues that should be triaged and prioretized in the next planning call label Apr 15, 2024
@ci-robbot
Copy link
Collaborator

Hello! I'm a bot that audits the tickets opened in this Github project. It seems like your issue is not completely clear, as the steps to reproduce and the versions of the relevant artifacts being used are not mentioned. According to the project's rules, these details should be provided in any new tickets.

Please provide more information such as the steps to reproduce the problem, the versions of the kairos images and the Jetson platform being used, as well as any other relevant details. This will help the maintainers of the project to better understand and address your issue.

I'm sure you're eager to get your problem solved, but please remember that I'm just a bot and I can't provide any direct assistance with the technical issue itself. If you have any further questions, feel free to ask!

Note: I am a bot, an experiment of @mudler and @jimmykarily.

@mauromorales mauromorales removed the triage Add this label to issues that should be triaged and prioretized in the next planning call label Apr 15, 2024
@mauromorales
Copy link
Member

Venkatesh confirmed that the jetson boots now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

5 participants