Date: Tue, 5 Feb 2013 11:11:44 -0500 From: John Baldwin <jhb@freebsd.org> To: Sergey Kandaurov <pluknet@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r245848 - head/sys/boot/i386/libi386 Message-ID: <201302051111.44833.jhb@freebsd.org> In-Reply-To: <CAE-mSOJk2B55rVsftxiJTFSsBzndW%2BXUW9NEhX4myoHVOGRWsg@mail.gmail.com> References: <201301231834.r0NIYLnp006407@svn.freebsd.org> <201302041446.55786.jhb@freebsd.org> <CAE-mSOJk2B55rVsftxiJTFSsBzndW%2BXUW9NEhX4myoHVOGRWsg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, February 05, 2013 2:46:15 am Sergey Kandaurov wrote: > Err.. No, I haven't set hw.uart.console. Sorry for being misleading. > The cited snippet from my previous mail was to demonstrate how the > resulting hw.uart.console value depends (or rather not :)) on hints. > All I have (changed) wrt console is: > > /boot/device.hints > #hint.uart.0.flags="0x10" > hint.uart.1.flags="0x10" > > /boot/loader.conf > boot_multicons="YES" > boot_serial="YES" > boot_verbose="YES" > console="comconsole,vidconsole" > > This setup worked for ages. To isolate this problem I took /boot/loader > from my older current machine (also with COM2) to replace it here, > and it started to work again. Right, so with this setup, you are using a non-working serial console for the loader on COM1 and then wanting the kernel to use COM2? Why? If you want to do that, set hw.uart.console manually. I think that is a very rare case and that most folks want to use the same console in both the loader and kernel. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201302051111.44833.jhb>