In the installer images, bsdinstall appears to be running on vt0, which is by default the (video) console. This means that any console spew, such as LOR warnings (which are ~guaranteed at present) will overwrite the installer dialogs. Running the installer on a vt that is not the console will prevent this.
Responsible Changed From-To: freebsd-bugs->freebsd-sysinstall fix synopsys and assign
On 2011-09-27, Ben Kaduk wrote: > In the installer images, bsdinstall appears to be running on vt0, > which is by default the (video) console. This means that any console > spew, such as LOR warnings (which are ~guaranteed at present) will > overwrite the installer dialogs. Running the installer on a vt that > is not the console will prevent this. I have an experimental patch to start bsdinstall on ttyv8 when the installer is run on syscons: http://people.freebsd.org/~jh/patches/bsdinstall-getty.3.diff -- Jaakko
Author: nwhitehorn Date: Mon Jan 23 15:44:52 2012 New Revision: 230482 URL: http://svn.freebsd.org/changeset/base/230482 Log: Per popular demand, if installing from a graphics terminal, run the installer on a VTY with no kernel messages (VTY 2), show the installer log in real time on VTY 3, and spawn a shell on VTY 4. PR: bin/161047, bin/161048 MFC after: 2 weeks Modified: head/release/rc.local Modified: head/release/rc.local ============================================================================== --- head/release/rc.local Mon Jan 23 15:39:45 2012 (r230481) +++ head/release/rc.local Mon Jan 23 15:44:52 2012 (r230482) @@ -10,8 +10,19 @@ kbdcontrol -d >/dev/null 2>&1 if [ $? -eq 0 ]; then - # Syscons: use xterm + # Syscons: use xterm, start interesting things on other VTYs TERM=xterm + + if [ "$EXTERNAL_VTY_STARTED" -ne 1 ]; then + vidcontrol -s 2 # Switch to a VTY with no kernel messages + # Init will clean these processes up if/when the system + # goes multiuser + touch /tmp/bsdinstall_log + tail -f /tmp/bsdinstall_log > /dev/ttyv2 & + /usr/libexec/getty autologin ttyv3 + EXTERNAL_VTY_STARTED=1 + trap "vidcontrol -s 1" EXIT + fi else # Serial or other console echo _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org"
Author: nwhitehorn Date: Mon Jan 23 16:17:54 2012 New Revision: 230484 URL: http://svn.freebsd.org/changeset/base/230484 Log: Part of r230482 didn't actually work. Revert it for now. This means PR 161047 isn't actually fixed. PR: bin/161047 Modified: head/release/rc.local Modified: head/release/rc.local ============================================================================== --- head/release/rc.local Mon Jan 23 15:50:16 2012 (r230483) +++ head/release/rc.local Mon Jan 23 16:17:54 2012 (r230484) @@ -14,14 +14,12 @@ if [ $? -eq 0 ]; then TERM=xterm if [ -z "$EXTERNAL_VTY_STARTED" ]; then - vidcontrol -s 2 # Switch to a VTY with no kernel messages # Init will clean these processes up if/when the system # goes multiuser touch /tmp/bsdinstall_log tail -f /tmp/bsdinstall_log > /dev/ttyv2 & /usr/libexec/getty autologin ttyv3 EXTERNAL_VTY_STARTED=1 - trap "vidcontrol -s 1" EXIT fi else # Serial or other console _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org"
batch change: For bugs that match the following - Status Is In progress AND - Untouched since 2018-01-01. AND - Affects Base System OR Documentation DO: Reset to open status. Note: I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Keyword: patch or patch-ready – in lieu of summary line prefix: [patch] * bulk change for the keyword * summary lines may be edited manually (not in bulk). Keyword descriptions and search interface: <https://bugs.freebsd.org/bugzilla/describekeywords.cgi>