Only boots up with Sysvinit

Questions specific to the KDE DE go here
User avatar
Zill
Posts: 1850
Joined: 13 Aug 2013 14:28
Location: Lincolnshire, UK

Re: Only boots up with Sysvinit

Postby Zill » 15 Feb 2017 17:01

Ensure you have a backup of your original "/etc/default/grub". Then open a terminal and start the nano editor by entering the following:

Code: Select all

sudo nano /etc/default/grub
Then add "init=/lib/sysvinit/init" to the line "GRUB_CMDLINE_LINUX_DEFAULT" so that it reads as follows:

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="init=/lib/sysvinit/init quiet nosplash"
Hit Ctrl-o to save and Ctrl-x to exit the nano editor.
Check the file has been edited correctly with the following command:

Code: Select all

cat /etc/default/grub
If correct, update grub with the following command:

Code: Select all

sudo update-grub
Reboot and, hopefully, the system will boot correctly into SolydK using sysvinit.

Fargo
Posts: 896
Joined: 17 Sep 2013 14:40

Re: Only boots up with Sysvinit

Postby Fargo » 15 Feb 2017 17:45

That worked. I'll just run it like this the next couple months until the new SolydK 9 is ready.

Thanks again for the help.

kurotsugi
Posts: 2225
Joined: 09 Jan 2014 00:17

Re: Only boots up with Sysvinit

Postby kurotsugi » 16 Feb 2017 00:18

journalctl give you rubbish. you'll need to filter it to get useful information. "sudo dmesg -l warn" or "sudo dmesg -l err" is lot easier to read but it only provide kernel related information. I have tendency to use systemctl to show systemd related logs. "systemctl status <servicename>" if I know which service is broken, or "systemctl list-services" if I want to know the complete service and status list.


Return to “KDE specific (SolydK)”

Who is online

Users browsing this forum: No registered users and 2 guests