Project

General

Profile

Bug #35047

Screen Saver not working with vt

Added by Waqar Ahmed about 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
No priority
Assignee:
Alexander Motin
Category:
OS
Target version:
Severity:
Medium
Reason for Closing:
Not to be fixed
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Screen saver is not working in nightlies. The steps taken to make it work were,
I typed in the shell the following commands in the given order
1) kldload daemon_saver
2) vidcontrol -t 5

Now this should load the daemon_saver and make the saver appear after 5 seconds. But that doesn't happen. After doing a kldstat | grep daemon_saver, it can be seen that it has been successfully loaded into the kernel.
The same commands types in 11.1 U3, give us a screen saver after 5 seconds of inactivity.


Related issues

Related to FreeNAS - Bug #28952: Fix bug in loading screensaverClosed
Related to FreeNAS - Feature #35948: Remove syscons terminal from kernelDone

History

#1 Updated by Waqar Ahmed about 1 year ago

  • Status changed from Unscreened to In Progress

#2 Updated by Dru Lavigne about 1 year ago

  • Related to Bug #28952: Fix bug in loading screensaver added

#3 Updated by Waqar Ahmed about 1 year ago

  • Category changed from Middleware to OS
  • Status changed from In Progress to Unscreened
  • Assignee changed from Waqar Ahmed to Alexander Motin

This issue maybe stems from the fact that the console system has been changed to vt from syscons.
https://wiki.freebsd.org/Newcons

#4 Updated by Alexander Motin about 1 year ago

  • Subject changed from Screen Saver not working to Screen Saver not working with vt

The problem is indeed specific to vty type. I can reproduce it on FreeBSD head with vt, while savers work fine with sc. Need to google what people think about it, but not sure what can we do about it. Development of console screensavers support for vt is not our priority.

#5 Updated by Dru Lavigne about 1 year ago

  • Target version changed from 11.2-BETA1 to 11.2-RC2

#6 Updated by Alexander Motin about 1 year ago

  • Status changed from Unscreened to Screened

Googling confirmed that vt indeed does not support screen saved, but that is an old news. What is new in 11.2 is that while before we used GRUB, we had 10_ktrueos script in it, which enabled syscons driver when system booted in legacy non-UEFI mode. With GRUB removal in 11.2 that code has gone, and now vt is probably default always where not explicitly switched via loader tunable. We need to decide whether this is good, or there is any significant reason to keep syscons in our kernel at all. May be it would be more beneficial to include kernel mode setting drivers instead, which are using vt, as some people ask.

#7 Updated by Alexander Motin about 1 year ago

  • Status changed from Screened to Closed
  • Target version changed from 11.2-RC2 to N/A
  • Reason for Closing set to Not to be fixed
  • Needs QA changed from Yes to No
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

VT terminal indeed does not have a screen-saver support. Considering it was not implemented before, I guess it may be not exactly trivial thing to focus on that. I am thinking about removing syscons terminal completely in 11.2, since it would save us significant amount of kernel type descriptions space, which is a limited resource for DTrace. Unless there will be any objections, I'll do it and create a ticket to remove the middleware/UI pieces after we done with BETA1.

#8 Updated by Alexander Motin about 1 year ago

  • Related to Feature #35948: Remove syscons terminal from kernel added

Also available in: Atom PDF