Unable to get screensaver working.

jimp

splash is in GENERIC so it's on a full install because full install kernels include GENERIC and specify additional options beyond what is there. NanoBSD kernels are pruned down and do not include things like that.

So it will work on a full install, but not NanoBSD.

stephenw10

Thanks Jim, as always. :)

Steve

OrBy

Ahhhh ok. Since this is running on a SSD - the RO default state of the NanoBSD was one of the traits I was looking to keep. Is there any chance that in the future that the splash device option be added to the NanoBSD VGA build since it's more then likely going to have a screen attached?

jimp

seems like it might be OK… feel free to submit a pull request on github with the changes, or a redmine feature request.

OrBy

Thank you again stephenw10 and jimp! I have done so and will wait to see what they say/do.

jimp

https://github.com/bsdperimeter/pfsense-tools/commit/eace068d57a040c9013d1d3124094262944338d8 :-)

OrBy

Whoa - that was quick!
Updated today and redid the steps in my 1st post - went down to check the local console and it has already went to sleep! I would say that's tested, working, and my issue is solved!

Thank you again jimp and stephenw10!

This thread can be closed as solved as far my issue.

NOYB

Now that you got it working, figured it was something I'd like to give a try.

I'm running an old DELL Inspiron 5100 notebook and in the case of an extended power outage that drains the battery the BIOS (RTC) is set to wake the computer once a day so the machine will eventually boot up again after power is restored.

However this seems to only work if the screen is up (not closed). So thought it would be nice to blank the screen.

It does blank the screen so that is nice, however it does not turn off the backlight. That's a big energy consumer, so not quite so green.

Also it blanks the screen for about the middle half of boot up. That could be real problem if it should hang during boot up with the screen blank.

Thanks for getting this working and sharing.


Put i386 version of green_saver.ko in /boot/modules/
Added green_saver_load="YES" to /boot/loader.conf.local
Added <shellcmd>vidcontrol -t 60</shellcmd> at end of config system section
rebooted

stephenw10

Try using <afterbootupshellcmd>instead.

Steve</afterbootupshellcmd>

NOYB

Nice thought, but it is blanking before it gets to the pfSense load.

Seems to be blanking upon loading the green_saver_load module in /boot/loader.conf.local.

jimp

Instead of putting that in loader.conf.local you could use the shell command tag to kldload it and then use vidcontrol.

NOYB

That works. :) Thanks.

Now if could just turn off the backlight.

NOYB

Loading green_saver.ko and configuring with vidcontrol with the afterbootupshellcmd and getting the following message. It does clear the screen though.

vidcontrol: getting active vty: Inappropriate ioctl for device'

Details:

/cf/conf/config.xml
<afterbootupshellcmd>/var/After_Bootup_Shell_Cmds.sh</afterbootupshellcmd>

/var/After_Bootup_Shell_Commands.sh
#!/bin/sh

After Bootup Shell Commands Script

kldload -v green_saver.ko;
vidcontrol -t 60

Log Output
php: : The command 'kldload -v green_saver.ko; vidcontrol -t 60' returned exit code '1', the output was 'Loaded green_saver.ko, id=2
vidcontrol: getting active vty: Inappropriate ioctl for device'