From owner-freebsd-questions@freebsd.org Fri Apr 14 18:34:25 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27B1AD3E85F for ; Fri, 14 Apr 2017 18:34:25 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay15.qsc.de (mailrelay15.qsc.de [212.99.187.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A1A397D4 for ; Fri, 14 Apr 2017 18:34:24 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay15.qsc.de; Fri, 14 Apr 2017 20:34:15 +0200 Received: from r56.edvax.de (port-92-195-127-117.dynamic.qsc.de [92.195.127.117]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 38F723CBF9; Fri, 14 Apr 2017 20:34:13 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v3EIYCMF003731; Fri, 14 Apr 2017 20:34:13 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Fri, 14 Apr 2017 20:34:12 +0200 From: Polytropon To: Manish Jain Cc: "freebsd-questions@freebsd.org" Subject: Re: Is it possible to load saver without reboot ? Message-Id: <20170414203412.17b102e4.freebsd@edvax.de> In-Reply-To: References: <20170414165359.62149261.freebsd@edvax.de> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay15.qsc.de with 99A356A0026 X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1246 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2017 18:34:25 -0000 On Fri, 14 Apr 2017 18:24:49 +0000, Manish Jain wrote: > > > On 04/14/17 20:23, Polytropon wrote: > > On Fri, 14 Apr 2017 14:49:09 +0000, Manish Jain wrote: > >> As part of my experiments with my tertiary box (FreeBSD 12-CURRENT > >> amd64), I am trying an apparently weird thing : load the saver without > >> rebooting. I configured the beastie saver by running 'bsdconfig console' > >> (although I could have just as well simply edited rc.conf myself). > >> > >> Normally, beastie would be expected to run only when I reboot. But in > >> theory, it should be possible to load the saver without rebooting. > >> > >> Anyone has any tips ? Thanks. > > > > If I understand the mechanism correctly, the beastie saver > > is run depending on the kernel screen saver module. When this > > module has been loaded with kldload, the saver functionality > > should be enabled - when all other dependencies are met, just > > as /etc/rc would execute them when the system boots (rc.conf > > entries, service configuration and start for console). It > > should be possible to do this manually without rebooting. > > Just check which steps are involved during boot. > > Hi Poly, > > For some reason, it does not work. Normally, I would expect the saver to > show up in 5 (max 10) minutes. > > I disabled the saver by deleting the line saver="beastie" in rc.conf, > and rebooted the system. On reboot, kldstat did not list the beastie > module. I then used 'bsdconfig console' to again set the saver, and then > kldloaded beastie_saver. I then waited 13 minutes - the saver did not > show up. So there is something else too which stops saver invocation. I'd say it's never started. If I remember correctly, there is a rc.d script which obtains the rc.conf information and then initiates the appropriate console behaviour. The following idea is to be read with the "sc->vt problem" in mind - on my home system, I'm still using VT because switching between X and 80x25 text mode somehow feels essential to me. :-) >From quick examination, I suggest you run "/etc/rc.d/syscons restart" or at least check which commands it will execute, related to the saver: This is the "vidcontrol" program where the required "flags string" is constructed; see "man vidcontrol" for details. Actually, I have no idea about vt, or if/how it uses vidcontrol, because "unusable black console after X" is something I now have accepted as unpleasant, but inevitable... :-/ > This is not exactly a tragedy, but a nice fun-thing to note. Perhaps you > have knowledge to hack my system further. Check your more recent /etc/rc.d/syscons (or other rc.d script that contains the string "saver") on how it's done today. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...