P.S. Just if somebody is interested in fixing those "fast scrolling text turns into garbage" display issues, here is some screenshots of one of my 11-alpha3 systems captured with a camera at 120fps. As you can see text tears down quite badly. I am curious if it's some lack of proper ordering of updates in the vt code itself or just some effect of CPU cache not being disabled properly when accessing frame buffer. It might look like a minor issue, but that what's our default console produces. I really think we can do better than that in 2016. I don't have any VESA-capable system around to verify that claim, but I am quite sure it was not the case with the old sc(4) in the pixel mode.
https://postimg.org/image/3nz6rirdj/ https://postimg.org/image/fr4if32fr/ https://postimg.org/image/onfaj0t1z/ On Wed, Jun 22, 2016 at 4:21 AM, Ernie Luzar <luzar...@gmail.com> wrote: > Kurt Jaeger wrote: > >> Hi! >> >> If you want textmode like in the old days, add this line to >>> /boot/loader.conf: >>> >>> hw.vga.textmode="1" >>> >> >> If I do this on a laptop 10.3p5, sending the laptop to sleep with >> zzz causes a crash (!), which is reproducable. >> >> > submit a PR > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > > _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
