GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I use one named phosphor, and as input for it I gave it dmesg! looks really nice, and far more complicated than it is (people will not touch your lt when they see it ;-) )
I use one named phosphor, and as input for it I gave it dmesg! looks really nice, and far more complicated than it is (people will not touch your lt when they see it ;-) )
It looks interesting. I was looking for it with no luck... where can I find it?
Regards
Ive used quite a few, ive noticed they all(except blank screen/lock screen) overtax my CPU, try running an 'uptime' after about 4-5 minutes of running a xscreensaver screen saver, see what you get.
Originally posted by Y0jiMb0 ...where can I find it?
hmmm goodquestion :-) I think it's part of Gnome 2.4 since that is what I am running, it just was there...
If you know how a linuxscreensaver works I am more than happy to find the file(s) and sent it to you
About the cpu usage, he is right they consume quite a bit, regarding that putting up a SETI screensaver would at least be more efficient instead of the waste of cpu power when the ss starts. On another note, I think the cpu is getting so busy maybe because the graphics accelerations of the card are not used. I for example have a VIA ProSavage DDR, and as far as I know there is no accelerated support for it yet under linux (Please corecct me if I am wrong, I would be glad to be wrong...)
Originally posted by BlackCell
hmmm goodquestion :-) I think it's part of Gnome 2.4 since that is what I am running, it just was there...
If you know how a linuxscreensaver works I am more than happy to find the file(s) and sent it to you
About the cpu usage, he is right they consume quite a bit, regarding that putting up a SETI screensaver would at least be more efficient instead of the waste of cpu power when the ss starts. On another note, I think the cpu is getting so busy maybe because the graphics accelerations of the card are not used. I for example have a VIA ProSavage DDR, and as far as I know there is no accelerated support for it yet under linux (Please corecct me if I am wrong, I would be glad to be wrong...)
cheers
He makes a good point accelerated graphics, I was thinking the same thing.
Originally posted by Tarts Ive used quite a few, ive noticed they all(except blank screen/lock screen) overtax my CPU, try running an 'uptime' after about 4-5 minutes of running a xscreensaver screen saver, see what you get.
Tarts
If you're running xscreensaver, most of the screen hacks have a -delay parameter that specifies the number of microseconds the hack sleeps between frames. Use -delay 15000 (experiment with this on each hack, some need more, some need less) on most of them, and you'll cut their CPU usage by quite a bit (though the OpenGL screen hacks will hog cycles no matter what.)
Originally posted by meldroc If you're running xscreensaver, most of the screen hacks have a -delay parameter that specifies the number of microseconds the hack sleeps between frames. Use -delay 15000 (experiment with this on each hack, some need more, some need less) on most of them, and you'll cut their CPU usage by quite a bit (though the OpenGL screen hacks will hog cycles no matter what.)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
*
