The officially official Devuan Forum!

webman

Member

Registered: 2022-08-27

Posts: 58  

After installing firmware, runlevel is unknown

Hi!
I am reading invoke-rc.d: could not determine current runlevel already on my last install
and faceing it at my current install again. So I have two setups with this error and I do not
know, where to look for it.
I am not a specialist, but one mentioned (together with other hints):

The service’s startup script is not working properly.

https://hatchjs.com/invoke-rc-d-could-n … -runlevel/
The message is in bootlog and appears between:

Starting Setting kernel variables: sysctl.
Starting: AppArmorLoading AppArmor profiles...done.
.
Configuring network interfaces...invoke-rc.d: could not determine current runlevel
invoke-rc.d: could not determine current runlevel
done.
Cleaning up temporary files....

And a mysterious DOT in a single line - WHO logs????
The network is ok.

The first computer does not start my LXC (container) which is set to autostart.
At this box, I tracked the occurence better (and I am just in an eraly state after
the networked setup) and it appears, after I installed some firmware packages
(amd64-microcode firmware-amd-graphics firmware-linux firmware-linux-free firmware-linux-nonfree firmware-realtek)
But the error persists if I remove (including purge) the packages and reboot.

For the first box, the problem may cause this:

$ ls /var/lib/lxcfs
ls: cannot access '/var/lib/lxcfs/sys': Input/output error
ls: cannot access '/var/lib/lxcfs/cgroup': Input/output error
total 0
dr-xr-xr-x 2 root root 0 2024-07-19 09:23:27 proc/
?????????? ? ?    ?    ?                   ? cgroup
?????????? ? ?    ?    ?                   ? sys

I am using fresh network install of devuan daedalus with kernel 6.1.0-23-amd64
Can someone help?
Thanks,
Manfred

lynch9

Member

Registered: 2024-07-17

Posts: 27  

Re: After installing firmware, runlevel is unknown

Heyo, start by checking the runlevel of your runlevel settings and check your init scripts in /etc/init.d/ for any incorrect settings. Might want to check into your boot logs with dmesg and journalctl -xb too. then check /etc/lxc/auto and check the LXC logs in /var/log/lxc/ to verify that your LXC container's autostart settings are correct. Re-configuring all packages with dpkg-reconfigure -a may also help... If the problem persists, hit up the #devuan IRC channel or something... anyways, good luck

P.s. In last resort, reinstall the firmware packages one by one to see if any of them are the culprits

---

Hey, it's lynchian9.
Feel free to reach out via email.