screen saver
hello, i am new to the freebsd world and i am trying to put screen saver to my box. i have a freebsd 8.0-release,i386 system i have loaded to rc.conf saver=rain i have gave the command vidcontrol -t 3 in the ttyv and i am in ttyv but screen saver doesn't appear after 3 seconds. the command kldstat shows that the module rain_saver.ko is loaded. i think that i am doing everything right but screen saver doesn't appear.. thanks in advance ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: screen saver
On 11/07/2010 4:00 π.μ., Giorgos Tsiapaliokas wrote: hello, i am new to the freebsd world and i am trying to put screen saver to my box. i have a freebsd 8.0-release,i386 system i have loaded to rc.conf saver=rain i have gave the command vidcontrol -t 3 in the ttyv and i am in ttyv but screen saver doesn't appear after 3 seconds. the command kldstat shows that the module rain_saver.ko is loaded. i think that i am doing everything right but screen saver doesn't appear.. thanks in advance Did you run /etc/rc.d/syscons restart (or reboot) after changing the saver= line in rc.conf? It works fine here. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Screen saver hangs: can't retrieve user sessions
On Sun, 7 Feb 2010 03:39:57 + dhaneshk k dhanes...@hotmail.com wrote: I am facing a serious issue, when my notebook(IBM Lenova T60+ FreeBSD-7.2+gnome2 ) goes idle screen saver enabled and when I hit enter it asks user password and I am able to logged in . but yesterday on wards when machine goes idle screen saver appears but when I hit any key it not giving the password screen, just hangs in the screen saver image and pressing any key no matter. I want to press hold the powerbutton and power off the machine all the time. ( it cause damage to system ?). how can I fix the hang of screen saver ? I am attaching the var/log/messages and Xorg log files.. The radeon driver and/or microcode still has bugs that lead to GPU crashes. One or more of the xscreensaver modules can trigger a crash. Once the GPU is dead, you may still be able to do something about it. For example, I have sometimes been able to type in a shutdown -r now and have it work, but only if either an xterm is currently the window in focus or I can move the cursor to a place I remember has an xterm and then clicking on it to get the focus to that xterm. Unfortunately, the ctl-backspace method doesn't help because even if the X server quits, there is still no display of the console because the GPU is halted/looping/whatever. A full reboot appears to be necessary to reset and restart the GPU. It would indeed be good to have an easy way to recover without rebooting, e.g., using the F11 or F12 key as a way to run some command that could reinitialize the GPU. Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at cs.niu.edu * ** * A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army. * *-- Gov. John Hancock, New York Journal, 28 January 1790 * ** ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
need help: crashing appears to be caused by/within console screen saver
I do not know where I should ask for help but I have core files from July 24, 23, 21 (x2), 19, 16 (x2) and May 17. All of the July crashes appear similar. The May crash was unrelated but shows that things were relatively stable until the first of these glitches. I am currently using the nvidia driver version 180.60 from ports on FreeBSD 7.2-RELEASE #0. The crashes typically take place when running through port rebuilds and upgrades, which I often do from the 3rd terminal. It usually occurs when I am away, but I just saw it where it looked like it was going to load the terminal screen saver and the screen just sat blank for maybe 10 seconds and then the system was restarting. I have since unloaded logo_saver.ko but would still like to resolve the source of the crashes if possible. Any suggestions where I should go from here and what other information would be helpful? At the end I copied a kgdb with a backtrace; It is what lead me to see that it crashed each time as the screen saver was activating (or so it now seems likely). Thanks again, Edward Sutton # kgdb kernel.debug /var/crash/vmcore.22 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd... Unread portion of the kernel message buffer: panic: pmap_mapdev: Couldn't alloc kernel virtual memory cpuid = 0 Uptime: 11h49m19s Physical memory: 2031 MB Dumping 233 MB: 218 202 186 170 154 138 122 106 90 74 58 42 26 10 Reading symbols from /boot/kernel/splash_bmp.ko...Reading symbols from /boot/kernel/splash_bmp.ko.symbols...done. done. Loaded symbols for /boot/kernel/splash_bmp.ko Reading symbols from /boot/kernel/vesa.ko...Reading symbols from /boot/kernel/vesa.ko.symbols...done. done. Loaded symbols for /boot/kernel/vesa.ko Reading symbols from /boot/kernel/geom_vinum.ko...Reading symbols from /boot/kernel/geom_vinum.ko.symbols...done. done. Loaded symbols for /boot/kernel/geom_vinum.ko Reading symbols from /boot/kernel/linux.ko...Reading symbols from /boot/kernel/linux.ko.symbols...done. done. Loaded symbols for /boot/kernel/linux.ko Reading symbols from /boot/kernel/snd_ich.ko...Reading symbols from /boot/kernel/snd_ich.ko.symbols...done. done. Loaded symbols for /boot/kernel/snd_ich.ko Reading symbols from /boot/kernel/sound.ko...Reading symbols from /boot/kernel/sound.ko.symbols...done. done. Loaded symbols for /boot/kernel/sound.ko Reading symbols from /boot/kernel/aio.ko...Reading symbols from /boot/kernel/aio.ko.symbols...done. done. Loaded symbols for /boot/kernel/aio.ko Reading symbols from /boot/kernel/sem.ko...Reading symbols from /boot/kernel/sem.ko.symbols...done. done. Loaded symbols for /boot/kernel/sem.ko Reading symbols from /boot/modules/nvidia.ko...done. Loaded symbols for /boot/modules/nvidia.ko Reading symbols from /boot/modules/kqemu.ko...done. Loaded symbols for /boot/modules/kqemu.ko Reading symbols from /boot/modules/ltmdm.ko...done. Loaded symbols for /boot/modules/ltmdm.ko Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi.ko Reading symbols from /boot/kernel/linprocfs.ko...Reading symbols from /boot/kernel/linprocfs.ko.symbols...done. done. Loaded symbols for /boot/kernel/linprocfs.ko Reading symbols from /boot/kernel/logo_saver.ko...Reading symbols from /boot/kernel/logo_saver.ko.symbols...done. done. Loaded symbols for /boot/kernel/logo_saver.ko Reading symbols from /usr/local/modules/rtc.ko...done. Loaded symbols for /usr/local/modules/rtc.ko #0 doadump () at pcpu.h:196 196 __asm __volatile(movl %%fs:0,%0 : =r (td)); (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc0590dbf in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc0591084 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc07ffc54 in pmap_mapdev_attr (pa=3489660928, size=268435456, mode=0) at /usr/src/sys/i386/i386/pmap.c:4349 #4 0xc07ffcfe in pmap_mapdev (pa=3489660928, size=268435456) at /usr/src/sys/i386/i386/pmap.c:4366 #5 0xc09b51d5 in vesa_set_mode (adp=0xc08e5620, mode=259) at /usr/src/sys/modules/vesa/../../i386/isa/vesa.c:835 #6 0xc642ea58 in logo_saver (adp=0xc08e5620, blank=1) at /usr/src/sys/modules/syscons/logo/../../../dev/syscons/logo/logo_saver.c:117 #7 0xc04909f6 in splash (adp=0xc08e5620, on=1) at /usr/src/sys/dev/fb/splash.c:211 #8 0xc04da60c in scsplash_saver (sc=0xc08f2960, show=1) at /usr/src/sys/dev/syscons/syscons.c:1957 #9 0xc04dc72e in scrn_timer (arg=0xc08f2960) at /usr/src/sys/dev/syscons/syscons.c:1767 #10 0xc05a27af in softclock (dummy=0x0) at /usr/src/sys/kern/kern_timeout.c:274 #11
rss-glx screen saver compilation fails?
Hey List, running FreeBSD-7-stable (from April or so) i386 binary nVidia drivers Has anybody successfully got rss-glx (really slick screensavers; http://rss-glx.sourceforge.net/ ) to compile for them? It isn't in ports and I was trying to compile it. I think I got all of the dependencies, etc... as ./configure completes without issue. I'm getting the following error when running make or gmake: spirographx.c: In function 'getAll': spirographx.c:99: warning: implicit declaration of function 'sincosf' spirographx.c:99: warning: incompatible implicit declaration of built-in function 'sincosf' /usr/local/bin/bash ../libtool --tag=CC --mode=link gcc -O2 -Wall -I/usr/local/include -o spirographx driver.o spirographx.o -lGLU -lGL -L/usr/local/lib -R/usr/local/lib -lSM -lICE -lX11 -lm gcc -O2 -Wall -I/usr/local/include -o spirographx driver.o spirographx.o -lGLU -lGL -L/usr/local/lib /usr/local/lib/libSM.so /usr/local/lib/libICE.so /usr/local/lib/libX11.so /usr/local/lib/libXau.so /usr/local/lib/libXdmcp.so -lrpcsvc -lm -Wl,--rpath -Wl,/usr/local/lib -Wl,--rpath -Wl,/usr/local/lib /usr/bin/ld: warning: libm.so.3, needed by /usr/local/lib/libGL.so, may conflict with libm.so.5 spirographx.o(.text+0x30f): In function `getAll': : undefined reference to `sincosf' Any ideas? Henrik -- Henrik Hudson [EMAIL PROTECTED] -- God, root, what is difference? Pitr; UF (http://www.userfriendly.org/) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rss-glx screen saver compilation fails?
spirographx.o(.text+0x30f): In function `getAll': : undefined reference to `sincosf' Per Google, it's a gnu-ism: http://linux.die.net/man/3/sincosf void sincosf(float x, float *sin, float *cos); Several applications need sine and cosine of the same angle x. This function computes both at the same time, and stores the results via the given pointers. Probably a 10-liner by just calling sin() and cos() separately -- a bit more work to do it properly -- or just grab the gnu code if you don't need to be BSD-licensed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Can't get rid of screen 'saver'
I'm running a picture slideshow on a laptop (TFT screen) and I dont want a screen saver/blanker or whatever it's called. No, I don't want it at all. So I edited my /etc/rc.conf: saver=NO blanktime=NO But still will the screen go black after a few minutes. I have turned off all Power Management features in the BIOS aswell. The computer is a Dell Latitude Cpx50 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't get rid of screen 'saver'
On Tue, Jan 25, 2005 at 04:12:29PM +0100, Joachim Dagerot wrote: I'm running a picture slideshow on a laptop (TFT screen) and I dont want a screen saver/blanker or whatever it's called. No, I don't want it at all. If you're running X, it has it's own set of DPMS powersave rules. Try xset dpms off in X to turn it off for one session. I think removing Options DPMS from the monitor section in your X config file will make it the default. I don't know what else it could be if you're not in X. HTH, --Stijn -- Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music. -- Kristian Wilson, Nintendo, Inc., 1989 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't get rid of screen 'saver'
apparently there are some hardcoded defaults in the X server that need to be overridden to remove the 10 minute blanktime. just add the serverflags section in your config file as explained here: http://xorg.freedesktop.org/X11R6.8.0/doc/xorg.conf.5.html and it should be fine. the one affecting you is probably this: Option BlankTime time sets the inactivity timeout for the blanking phase of the screensaver. time is in minutes. This is equivalent to the Xorg server's `-s' flag, and the value can be changed at run-time with xset(1x) . Default: 10 minutes. you might also want to get rid of all those others options StandbyTime, SuspendTime and OffTime just to be on the safe side. HTH, g. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Programmatic control of screen-saver
I have a machine controlling a tester. Tester control and display is via a virtual console terminal. (X is not installed on the machine) I need to blank the screen (screen saver style) when there is no terminal activity for some time -- much the same as as normal screen-saver operation except that screen output as well as keyboard input should inhibit the screen-saver taking over or cause the normal terminal display to be restored if the saver is already in effect. I would hope that there might be some ioctl call to the terminal which could be used from within the tester control software to wake up the terminal or prevent the screen saver taking over until a further timeout has elapsed. I've not been able to find such an ioctl call parameter. Does anyone have any ideas or a solution please? (FreeBSD 4.8-Release) Malcolm Kay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Programmatic control of screen-saver
On Wed, Nov 12, 2003 at 11:33:07PM +1030, Malcolm Kay wrote: I have a machine controlling a tester. Tester control and display is via a virtual console terminal. (X is not installed on the machine) I need to blank the screen (screen saver style) when there is no terminal activity for some time -- much the same as as normal screen-saver operation except that screen output as well as keyboard input should inhibit the screen-saver taking over or cause the normal terminal display to be restored if the saver is already in effect. I would hope that there might be some ioctl call to the terminal which could be used from within the tester control software to wake up the terminal or prevent the screen saver taking over until a further timeout has elapsed. I've not been able to find such an ioctl call parameter. Does anyone have any ideas or a solution please? See vidcontrol(1): # vidcontrol -t 30 sets the console screensaver timeout to 30s, and # vidcontrol -t off turns off the console screensaver. This does indeed operate using the CONS_BLANKTIME ioctl -- see the code in the set_screensaver_timeout() function in /usr/src/usr.sbin/vidcontrol/vidcontrol.c and the sys/consio.h header file. I think that ioctl should do what you want, although I'm not sure that setting the blanking time to zero would actually cancel a running screen saver. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: Screen Saver (almost off topic)
# [EMAIL PROTECTED] / 2002-10-08 15:27:53 +0300: Hello! I have a problem who's driving me crazy! I want to make it not appear on my screen but i didn't succeed it. Do you have any idea? I have to mention that my server runs Sinix/Reliant Unix. First, this is a FreeBSD mailing list. Second, I think you should read this: http://www.tuxedo.org/~esr/faqs/smart-questions.html#intro -- begin 666 nonexistent.vbs FreeBSD 4.7-RC 3:52PM up 20 days, 23:07, 12 users, load averages: 0.21, 0.31, 0.33 end To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Screen Saver Setup
Trying to load a screen saver. I've set /etc/rc.conffor it (see attachment), but it doesn't load. Or at least it doesn't activate, and kldstatdoesn't indicate that it has loaded. How come? Pb screensave_load=YES screensave_name=green_saver blanktime=600
Re: Screen Saver Setup
where did you pull those variables from? you want: saver=green_saver.ko blanktime=600 -Adam (07.25.2002 @ 1209 PST): Parker Brown said, in 0.8K: Trying to load a screen saver. I've set /etc/rc.conffor it (see attachment), but it doesn't load. Or at least it doesn't activate, and kldstatdoesn't indicate that it has loaded. How come? Pb screensave_load=YES screensave_name=green_saver blanktime=600 end of Screen Saver Setup from Parker Brown -- Oh good, my dog found the chainsaw. -Lilo, Lilo Stitch Adam Weinberger [EMAIL PROTECTED] http://vectors.cx To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Screen Saver Setup
On Thu, Jul 25, 2002 at 12:26:37PM -0700, Adam Weinberger wrote:
you want:
saver=green_saver.ko
blanktime=600
Make that:
saver=green
The _saver bit gets filled in for you automatically:
happy-idiot-talk:~:% grep saver /etc/defaults/rc.conf
saver=NO # screen saver: Uses /modules/${saver}_saver.ko
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
Tel: +44 1628 476614 Marlow
Fax: +44 0870 0522645 Bucks., SL7 1TH UK
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
