| View previous topic :: View next topic |
| Author |
Message |
83657664
n00b
Joined: 16 Mar 2011
Posts: 50
|
 Posted: Tue Dec 17, 2013 5:43 am Post subject: gnome3.8 systemd lead gentoo with grub1 for non-genkernel |
 |
|
hi,guys.
openrc still work,how systemd boot with system,
i follow http://wiki.gentoo.org/wiki/Systemd#Kernel,but it didn't answer my question.
gnome3.8 systemd lead gentoo with grub1 for non-genkernel user.
i want the systemd worked,boot gnome 3.8.
can anyone help!!! |
|
| Back to top |
|
 |
ulenrich
Veteran
Joined: 10 Oct 2010
Posts: 1480
|
| Posted: Tue Dec 17, 2013 3:06 pm Post subject: |
|
|
grub kernel cmdline has to specify init with non default systemd, add:
init=/usr/lib/systemd/systemd
... not sure if I understand your sentences. |
|
| Back to top |
|
|
83657664
n00b
Joined: 16 Mar 2011
Posts: 50
|
| Posted: Wed Dec 18, 2013 4:09 am Post subject: |
|
|
title Gentoo Linux 3.10.17
root (hd0,0)
kernel /boot/kernel-3.10.17-gentoo root=/dev/sda9 init=/usr/lib/systemd/systemd
is that right?
but when i type
| Code: | localhost ~ # systemctl start gdm.service
Failed to get D-Bus connection: No connection to service manager. |
it seems systemd did not start.
what i do now? |
|
| Back to top |
|
|
ulenrich
Veteran
Joined: 10 Oct 2010
Posts: 1480
|
| Posted: Wed Dec 18, 2013 10:52 am Post subject: |
|
|
| 83657664 wrote: | title Gentoo Linux 3.10.17
root (hd0,0)
kernel /boot/kernel-3.10.17-gentoo root=/dev/sda9 init=/usr/lib/systemd/systemd
is that right?
but when i type
| Code: | localhost ~ # systemctl start gdm.service
Failed to get D-Bus connection: No connection to service manager. |
it seems systemd did not start.
what i do now? |
It seems to have started at your machine to me: but dbus!
You are a step further! Next steps:
| Code: | systemctl enable gdm.service
systemctl set-default graphical.target
systemctl get-default
# should show now!
# reboot
|
If you want to experiment yourself,
also remember following commands as root to diagnose systemd:
| Code: | journalctl -b
# shows you the actual boot log
systemctl
# show the list of services
systemctl status <unit>
# shows the state of a service
systemctl disable <unit>
# don't willingly activate
systemctl mask <unit>
# prevent a service to ever load automatically
systemctl isolate multi-user.target
# change runlevel, later on you can:
systemctl isolate graphical.target
|
PS: I am a Kde user. As I know Gdm has problems 
To start a Gnome session you can also try lightdm or kdm as a displaymanager.
PS2: If you cannot solve your problem now we might further look at your kernel .config. |
|
| Back to top |
|
|
|
Desktop Environments
