lxnay wrote:If you get timeout on LVM, it either means that your kernel is too old (3.3? 3.5, 3.6?) or you are not running our kernels. You probably built them yourself without using genkernel-next or the likes.
There is nothing to fix, if you diverge from what we provide out of the box, there is a high risk to run into real troubles.
lxnay wrote:If you are running GNOME 3.8, do yourself a favor: switch to systemd ASAP!, or you're going to get into real troubles in future. If you don't know how to configure it, you can read the Gentoo wiki on systemd services. If you still have troubles, just install Sabayon 13.08.
systemd-journald: failed to set ACL on /var/log/journal/63d287da47e2cf71e967c05d0000001b/user-109.journal, ignoring: invalid argument
bigears wrote:After the latest update, I get the login prompt. I login with root and do eselect sysvinit set systemd but it tells me that the file system is read only. How am I suppose to run switch to systemd.
mount / -o remount,rw
mount / -o remount,ro
slacker wrote:I have now installed the 3.10 sabayon kernel, switched to it using 'eselect kernel set' and 'eselect bzimage set' and installed the correct nvidia-drivers for that kernel then switched to systemd.
lxnay wrote:slacker wrote:I have now installed the 3.10 sabayon kernel, switched to it using 'eselect kernel set' and 'eselect bzimage set' and installed the correct nvidia-drivers for that kernel then switched to systemd.
"eselect kernel" is not a tool for switching between the default kernel used to boot the system. Instead, it only handles the /usr/src/linux symlink and this has absolutely nothing to do with the kernel used to boot. Since many people came out with the same thing about eselect kernel, I wonder where you did read this absolutely bogus information.
lxnay wrote:If you don't know or find it difficult to switch to systemd for whatever reason, just reinstall the latest Sabayon.
A crashing gdm may have to do with upstream bugs, not related to Sabayon in any way. Both GNOME and KDE are *known* to not care about migration paths between major releases. They keep introducing incompatibilities that may cause crashes when old configuration files are in place. There is nothing we can do about it, that's the way it is and yeah, upstream suck big time in this.
ph03 wrote:I already tried to switch to systemd, but almost all my init.d services are not supported, or maybe I wasn't able to find out how to start them. Is it possible to use these services in a kind of legacy mode using systemd?
Users browsing this forum: No registered users and 1 guest