runit warning: unable to open /dev/console: file does not exist #92
Comments
|
I've been testing it with Arch Linux and the device I wonder if Void Linux requires extra modules/configurations to get console available via kernel. Where I can find an image with Void Linux so I can boot and check what is going on there. Or another option if you can boot with some working initramfs (that does not have this warning) and show me output of |
|
I can definitely assist. Otherwise would Another (possibly related) issue is that, when my laptop is docked, I can use external keyboard to type password only if that initramfs was built while docked. Is there a way to always include the necessary stuff? This is using and |
|
A few things to try:
Let me know if any of the options make difference for you. |
|
After adding 1 and 2, I still get the warning. |
|
On the other hand, the keyboard issue is gone (possibly due to |
|
@dkwo |
|
With I still get the warning. (The minor keyboard issue is gone.) |
|
I can add the mkinitcpio output if that helps. |
@travankor it would be great. Could you please also increase verbosity level ( |
Just to clarify, with the config above ( |
|
Just to clarify, with the config above (`modules_force_load: usbkbd` option) the only issue you see is following error from runit `warning: unable to open /dev/console: file does not exist`. Is my assumtion correct?
That is correct.
|
anatol
changed the title
anatol
added a commit
that referenced
this issue
Jun 29, 2021
At initram stage booster mounts several filesystems that needed for successful boot process. At this moment we preserve /run (because it contains udev state) and other mountpoints are unmounted. It turns out runit used at Void Linux expects that /dev is present from the very beginning. And it differs from systemd that parses fstab and mount the fs before it tries to use. Help runit and move /dev /sys /proc to host filesystem. It fixes the runit unable to open /dev/console warning. Closes #92
anatol
added a commit
that referenced
this issue
Jun 29, 2021
At initram stage booster mounts several filesystems that needed for successful boot process. At this moment we preserve /run (because it contains udev state) and other mountpoints are unmounted. It turns out runit used at Void Linux expects that /dev is present from the very beginning. And it differs from systemd that parses fstab and mount the fs before it tries to use. Help runit and move `/dev` `/sys` `/proc` to host filesystem. It fixes the runit "unable to open /dev/console" warning. Closes #92
|
I setup Void Linux for my integration tests and I see this warning now. It looks like it comes from the fact that Anyway I just added https://github.com/anatol/booster/tree/issue-92 branch with potential solution. It fixes the warning and my QEMU with Void seems boot fine. Please give a try and let me know your results. |
anatol
added a commit
that referenced
this issue
Jun 29, 2021
At initram stage booster mounts several filesystems that needed for successful boot process. At this moment we preserve /run (because it contains udev state) and other mountpoints are unmounted. It turns out runit used at Void Linux expects that /dev is present from the very beginning. And it differs from systemd that parses fstab and mount the fs before it tries to use. Help runit and move `/dev` `/sys` `/proc` to host filesystem. It fixes the runit "unable to open /dev/console" warning. Closes #92
anatol
added a commit
that referenced
this issue
Jun 29, 2021
|
Great! Let me try it. |
|
It works well for me: warning is gone, and everything else still works as expected.
Thank you for helping with this.
|
anatol
added a commit
that referenced
this issue
Jul 1, 2021
|
The fix got merged I also added an integration test for VoidLinux userspace image to make sure booster boots it correctly. |
|
Great! Looking forward to next release :) |
|
Thanks again. |
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After it prompts for LUKS password, just before entering stage 1, I see
runit: warning: unable to open /dev/console: file does not existIf I add
vconsole: true, then it saysopen /etc/vconsole.conf: no such file or directory, and the warning is still there, even though I haveThis is not blocking, but I'd like to understand the problem.
Also, on an unrelated matter, could you comment on Void linux
boosterpackage PR?Thanks.
The text was updated successfully, but these errors were encountered: