On Sat, Aug 31, 2013 at 9:53 AM, Adrian Chadd <adr...@freebsd.org> wrote:
> Ok. > > I'm glad this is actually working for people. > > But now comes the hard bit - figuring out why the VESA driver is breaking > resume. :( > > I actually use VESA text modes in console mode so I'll take a look but I > can't promise anything. > > Who actually has experience with the VESA code and may be able to help? > Does anyone know? > > Thanks, > > > > -adrian > > Of course this is the real issue. Removing VESA is just a band-aid and will become a problem once newcons makes it out the door (any day now). I'd like to try to figure out the scope of the problem, if possible. In most (all?) reports, removing VESA has worked on Thinkpads. I think I have seen reports that it works on other platforms, but I'm not positive. I also believe that it has been reported to not work for attempts to suspend/resume when in text mode... only when in X. (I guess I can test this myself.) For almost four years all vesa commits were by jkim. -- R. Kevin Oberman, Network Engineer E-mail: rkober...@gmail.com _______________________________________________ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscr...@freebsd.org"