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

opensuse rpi4 fails to boot in v3.0.9 #2563

Open
mauromorales opened this issue May 16, 2024 · 6 comments
Open

opensuse rpi4 fails to boot in v3.0.9 #2563

mauromorales opened this issue May 16, 2024 · 6 comments
Labels
bug Something isn't working triage Add this label to issues that should be triaged and prioretized in the next planning call unconfirmed

Comments

@mauromorales
Copy link
Member

DISTRO_BASE="opensuse"
DISTRO_VERSION="leap-15.5"
VARIANT="standard"
ARCH="arm64"
MODEL="rpi4"
KAIROS_VERSION="v3.0.9"
K3S_VERSION="1.29.3"

Is broken.
WhatsApp Bild 2024-05-02 um 23 32 50_c3b87247
WhatsApp Bild 2024-05-02 um 23 32 49_3ff67ccb

The old v3.0.6 works as expected. (v3.0.6...v3.0.9)

Originally posted by @kaiehrhardt in #2528 (comment)

@mauromorales mauromorales mentioned this issue May 16, 2024
30 tasks
@mauromorales mauromorales 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 May 16, 2024
@ci-robbot ci-robbot added the question Further information is requested label May 16, 2024
@ci-robbot
Copy link
Collaborator

Hello, I'm a bot assisting with ticket auditing in the Github project kairos-io/kairos. I've noticed that issue #2563 is missing the required information for a valid ticket as per the project's guidelines.

Please provide a detailed description of the issue and, if it's a bug, include steps to reproduce. Additionally, please specify the versions of the relevant artifacts you are using.

Thank you for your cooperation. I'm an experiment by @mudler and @jimmykarily, and I'm here to help ensure that all tickets meet the project's requirements.

@mauromorales mauromorales removed the question Further information is requested label May 16, 2024
@kaiehrhardt
Copy link
Contributor

i have not yet had time to instrument my installation with the debug arguments.

@kaiehrhardt
Copy link
Contributor

kaiehrhardt commented Jun 8, 2024

UPDATE: v3.0.12

grafik

Is it helpful? I could provide more info, if you want. Is there any dracut debug flag? Not sure where that script comes from.

@mauromorales
Copy link
Member Author

I think you can also pass rd.debug and/or rd.immucore.debug

@kaiehrhardt
Copy link
Contributor

This is the rd.debug log. I thought it's a global loglevel. Do i get more info if i also set rd.immucore.debug?

@jimmykarily
Copy link
Contributor

jimmykarily commented Jun 12, 2024

Immucore reads rd.immucore.debug to enable debug mode. But reading the actual logs might be tricky. You need to somehow get a shell. Probably using this: https://kairos.io/docs/reference/troubleshooting/#initramfs-breakpoints (with one of the stages described here)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage Add this label to issues that should be triaged and prioretized in the next planning call unconfirmed
Projects
Status: No status
Development

No branches or pull requests

4 participants