From owner-freebsd-mobile Wed Mar 8 8: 5:37 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from sargasso.cse.msu.edu (sargasso.cse.msu.edu [35.9.20.14]) by hub.freebsd.org (Postfix) with ESMTP id 8C22B37B82F for ; Wed, 8 Mar 2000 08:05:33 -0800 (PST) (envelope-from bg@cse.msu.edu) Received: from dog.cse.msu.edu (dog.cse.msu.edu [35.9.20.45]) by sargasso.cse.msu.edu (8.8.8/8.8.8) with ESMTP id LAA17051 for ; Wed, 8 Mar 2000 11:05:29 -0500 (EST) From: Boris Gelfand Received: (from bg@localhost) by dog.cse.msu.edu (8.9.3/8.8.8) id LAA07044 for freebsd-mobile@FreeBSD.ORG; Wed, 8 Mar 2000 11:01:45 -0500 (EST) Date: Wed, 8 Mar 2000 11:01:45 -0500 (EST) Message-Id: <200003081601.LAA07044@dog.cse.msu.edu> To: freebsd-mobile@FreeBSD.ORG Subject: green_saver acting wacky in 3.4-R Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all, Prior to a complete re-install with 3.4-R, I ran 3.0 and 3.2 on my Panasonic CF-35 as well as a Gateway Solo at work with no problems. Since going to 3.4-R on both machine, my green_saver in console mode has started to go wacky. Whenever it fires up, both displays show color bleed and ghost images -- pretty scary stuff. One laptop has Neomagic and the other Chips&Tech. I've got my kernel with the speudo-device splace, and "VM86" & "VESA" options turned on. Other screen savers work fine (blank, snake, etc.) "power_saver" mode in XFree86 works fine as well -- suspend properly turns off the backlight, etc. Any idea as to what's up? Thanks in advance -- --Boris bg@cse.msu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message