On Tue, Mar 24, 2009 at 11:10 AM, Gustau Perez <gperez_at_entel.upc.edu> wrote: > >> >> For now, it seems X is required. The "switch-to-VTY-and-back-again" >> solution works for me: >> >> http://www.freebsd.org/doc/en/articles/laptop/power-management.html >> >> In my /etc/rc.suspend: >> >> ... >> /usr/sbin/vidcontrol -s 1 < /dev/console >> ... >> >> In my /etc/rc.resume: >> >> ... >> /usr/sbin/vidcontrol -s 9 < /dev/console >> ... >> >> I've also seen various posts in forums and on mailing lists >> about using the "vbetool" program (in ports), but I haven't messed >> with it myself. >> >> See here for more detail on this issue (under "Low Priority Tasks"): >> >> http://www.freebsd.org/projects/acpi/#todo-list >> >> -Brandon >> > > Thank you, I'll try it at home (leaving work in a few second ;)) However, > what I cannot understand is why if_bge is giving me problems, while I've > seen some successful reports of people with the same hard (at least > supported by the same driver). > > Greets, > > Gus > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" > Well, I just went through a suspend/resume cycle on my notebook without the 'vidcontrol' statements in my /etc/rc.* (from Xorg) and my display lit right up! I guess I no longer require the VTY switch to save the video state as I once did... -BrandonReceived on Tue Mar 24 2009 - 15:35:01 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:44 UTC