Date: Mon, 31 Aug 2015 18:42:11 +0200 From: Dirk Engling <erdgeist@erdgeist.org> To: Marcel Moolenaar <marcel@xcllnt.net>, hackers@freebsd.org Subject: Re: Puzzle involving serial console and ...??!? Message-ID: <20150831164211.5611597.78437.7008@erdgeist.org> In-Reply-To: <9D30425C-CFBF-4502-BA04-6F6B0352610F@xcllnt.net> References: <20150831030639.GH1153@albert.catwhisker.org> <9D30425C-CFBF-4502-BA04-6F6B0352610F@xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
=C2=A0 Original Message =C2=A0 From: Marcel Moolenaar Sent: Montag, 31. August 2015 18:20 To: hackers@freebsd.org Subject: Re: Puzzle involving serial console and ...??!? > On Aug 30, 2015, at 8:06 PM, David Wolfskill <david@catwhisker.org> wrote: >=20 > By doing so, I have a working serial console (once the FreeBSD > loader gains control from the BIOS, at least)... half the time. >=20 > I have determined that whether or not I have a functioning serial > console for freebeast depends on whether I boot albert from slice > 1 or slice 2: if from slice 1, it doesn't work; if from slice 2, > it does. Check your boot sectors. boot0 is shared between the slices, so that=E2=80=99s less of a concern, but boot2 is specific to each slice. You can force a serial console by writing =E2=80=9C-P=E2=80=9C to /boot.con= fig (if not already done). It helps if you tell the kernel specifically to use a serial console (as well): boot_serial=3Dyes hw.uart.console=3D=E2=80=9Cio:0x3f8=E2=80=9D boot_multicons=3Dyes I have found that with vt(4) it=E2=80=99s pretty much impossible to not have it claim the console. I haven=E2=80=99t figured out why... -- Marcel Moolenaar marcel@xcllnt.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150831164211.5611597.78437.7008>