-
Notifications
You must be signed in to change notification settings - Fork 11
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
rpi4 - didn't boot. How to switch on debugging infos? #154
Comments
Thank you for testing :)
Increase the
66 is not associated to the initramfs in any way - I use the same initramfs for runit and 66. If a crash occurs after displaying Networking configuration is usually done outside of boot@system - I will gladly accept a frontend for rpi if there is something special needed :)
That is a first. I have tested 66/boot@ in constrained setups but I have never seen such behavior. It merits some investigation... |
https://gist.github.com/dreamcat4/3b80bbf902fc6e74d599c5359a2caae0
unfortunately no, there is no way to change the TTY, |
It seems i forgot to mention that i manually tried to change |
It is not possible to boot with this environment file, as it contains only a fraction of the needed keys. Νο idea how it was produced as |
ok great news! thank you. |
ok i checked - it's the same exact on my system. Sorry it was just copy / pasted wrong from the terminal. It cut off the file. All is there https://gist.github.com/dreamcat4/e2629ecce8f66dc22abddc37b88884a3 |
The early getty always starts in tty12. It starts very early in order to function as an emergency/rescue shell. It should be up at that stage. The other ttys start much later in the boot process.
Judging by the screenshot in the next post, you have |
thanks for these details. it is helpful and i shall try my best to follow these new instructions. will come back with further details in coming days |
Hi there @mobinmob & thanks for working on this project!
Tried having a go on rpi4 yesterday.
conf/void-66-conf.md
file.Any way I can provide a better feedback on this? Assuming that you don't have an rpi device yourself. Then it's necessary to help debug the problem.
I also tried to look for any specific customizations for rpi in void linux itself. However mostly it's just a few service that comes up later on in boot stages. Such as to configure networking etc. But we are nowhere near that when the boot failed. It's still like trying to mount early stuff (for example like
/proc
), or boot the initramfs.Then it does nothing for several minutes. And complains 'out of memory error' starts culling some task. Then a few minutes later it does out of memory again.
The text was updated successfully, but these errors were encountered: