Date: Fri, 22 Jun 2018 20:52:53 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: Yasuhiro KIMURA <yasu@utahime.org>, "bsd-lists@BSDforge.com" <bsd-lists@BSDforge.com> Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Subject: Re: Console is broken after updating to 11.2-RELEASE Message-ID: <YTOPR0101MB09530EDF11A459AEED559430DD750@YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <f7488c423497d4a62ce19966fa2cde83@udns.ultimatedns.net> References: <20180623.025635.943064292669730543.yasu@utahime.org>, <f7488c423497d4a62ce19966fa2cde83@udns.ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris H wrote: [stuff snipped] >> >> Thank you for information. I added above lines to /boot/loader.conf >> and rebooted system. Then all boot messages are displayed and console >> works fine! > >WooHoo! :-) > >I could make further observations based on *why* that worked. But several >are likely, and I don't have enough info on your hardware. But now that >you are no longer "blind". You should have little trouble sorting out the >cause. I have no idea if this helps, but running a fairly recent head kernel, when= I would switch virtual consoles, the screen would go blank until I power cycled the= SVGA monitor. I switched to "sc" and the problem went away. (This is an old Pentium 4 with what dmesg calls a "Generic VGA display".) I don't see the same problem with a laptop of the same era. Just in case it gives you a hint w.r.t. the problem, rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YTOPR0101MB09530EDF11A459AEED559430DD750>