On 09/16/15 19:50, Jonathan Billings wrote:> On Sep 16, 2015, at 5:21 PM, m.roth at 5-cent.us wrote: >> I tried systemctl start multi-user.target. I tried systemctl stop >> graphical.target. I finally had to set the multi-user.target as the >> default, and reboot, to get rid of the nouveau drivers. >> >> Note that I tried to modprobe -r, and rmmod with all the modules using >> nouveau, and couldn't - I kept getting "in use" - it seemed like a >> circular reference. >> >> As I said, I rebooted. Then I ran the proprietary build, ran fine. I try >> starting the graphical target, no joy. I changed the default target back >> to graphical, and rebooted. Still no xorg. Googling (yahooing?), I added >> rdblacklist=nouveau in grub.conf, *then* had to rebuild the grub2 (grub2 >> must *die*). >> >> Still wouldn't see the nvidia drivers on reboot. Finally, I rebuild the >> initramfs, which got the now-built and installed nvidia drivers (and I'd >> yum uninstalled nouveau), and finally, it came up. >> >> Oh, and for some reason, without the reboot, the Xorg.0.log wasn't >> renewed, as though it hadn't actually restarted X. Plus, it appears that >> <ctrl-alt-bkspc> is disabled....<snip>> > Of course, none of this had anything to do with systemd, other than the > commands you had to change runlevels. It?d be the same problem with > Upstart in CentOS6, just different commands. The kernel modesetting stuff > is at fault here. But who needs facts to get in the way of a good rant?Really? In Centos 6, if I do an init 3, it shuts down X; none of the above did that,> > I suggest looking at http://elrepo.org/tiki/kmod-nvidiaI'm familiar with elrepo. mark
On Thu, 17 Sep 2015, mark wrote:> I'm familiar with elrepo.Then why didn't you use them for the nvidia driver? jh
On 09/17/2015 03:53 AM, mark wrote:> Really? In Centos 6, if I do an init 3, it shuts down X; none of the > above did that,You ran "systemctl start multi-user" when you meant to "systemctl isolate multi-user". The man page describes isolate: "This is similar to changing the runlevel in a traditional init system." Aside from the fact that you use the same command, systemctl, to "start" a service and "isolate" a runlevel, none of the problems you described had anything to do with systemd. In fact, even switching runlevels/targets is unrelated to the video modules. You always have to blacklist the video driver, or boot with "nomodeset" to remove the video card's kernel module (Actually, you might be able to "echo 0000:<pci ID>" > /sys/bus/pci/devices/0000:<pci ID>/driver/unbind" sometimes. Some drivers might cause a kernel panic, though.) because even in multi-user mode with no X.org, the kernel is still using the module for its console.
On Thu, Sep 17, 2015 at 08:52:57AM -0700, Gordon Messmer wrote:> You ran "systemctl start multi-user" when you meant to "systemctl > isolate multi-user". > The man page describes isolate: "This is similar to changing the > runlevel in a traditional init system."Note that you can actually do 'telinit 3' and telinit 5' with systemd. I do, even though the documentation is a little complainy about it. This maps to `systemctl isolate runlevel3.target` or `systemctl isolate runlevel2.target` (which in turn are symlinks to multi-user.target and graphical.target), and is a lot less typing. :) -- Matthew Miller <mattdm at fedoraproject.org> Fedora Project Leader