In message <[EMAIL PROTECTED]>, Mike Tancsa writes:
>I think I am almost there, but in my case, I get some strange char
>duplication after seeing the F1 prompt. The BIOS has console
>redirection, so I can see it throughout the bootup process.
...
>//bbtt..ccoo- ffiigg:: --DDhh//
>BTX loader
At 04:19 PM 06/03/2006, Ian Dowse wrote:
Presumably the boot loader (boot1/2) drops you at the prompt because
it is old and does not understand the "-S115200". Once you update
the boot blocks with disklabel, that /boot.config should work.
I think I am almost there, but in my case, I get some
On Mar 6, 2006, at 4:19 PM, Ian Dowse wrote:
There are a lot of steps to the boot process so it can be confusing
- the command you wanted was disklabel, not boot0cfg. The boot0cfg
program installs boot0, which is a 512-byte boot manager that you
Yow. Thanks for the clarification. I guess 10
In message <[EMAIL PROTECTED]>, Vivek Khera writes
:
>
>On Feb 27, 2006, at 12:29 PM, Ed Maste wrote:
>I'm not having any luck getting my 115200 baud serial console back.
>The machine was upgraded from 5.4-STABLE to 6.1-PRE last week, and
>again over the weekend. I did the following:
>
>make
On Feb 27, 2006, at 12:29 PM, Ed Maste wrote:
Probably the "best" way is now -S in boot.config, since it means that
you don't have to recompile and you only have to change it in one
place.
I'm not having any luck getting my 115200 baud serial console back.
The machine was upgraded from 5.
On Feb 27, 2006, at 1:19 PM, Ed Maste wrote:
On Mon, Feb 27, 2006 at 11:07:35AM -0500, Vivek Khera wrote:
I get a 9600 baud console with the following after upgrade from 5.4:
This is what I'm planning on putting in UPDATING:
The i386 loader(8) now defaults to the serial speed set b
On Mon, Feb 27, 2006 at 11:07:35AM -0500, Vivek Khera wrote:
> I get a 9600 baud console with the following after upgrade from 5.4:
This is what I'm planning on putting in UPDATING:
The i386 loader(8) now defaults to the serial speed set by the
previous boot stage, if the comcons
On Mon, Feb 27, 2006 at 12:01:08PM -0500, Rong-En Fan wrote:
> Which way is preferred: setting comconsole_speed, -S in
> boot.config, or using harded code BOOT_COMCONSOLE_SPEED in make.conf?
> If now the most preferred way is to using -S or
> comconsole_speed in loader.conf, please update that in
On Mon, Feb 27, 2006 at 12:01:08PM -0500, Rong-En Fan wrote:
> On 2/27/06, Ruslan Ermilov <[EMAIL PROTECTED]> wrote:
> > On Sun, Feb 26, 2006 at 08:26:42PM +0100, Dimitry Andric wrote:
> > > Ian Dowse wrote:
> > > >> Okay, but why did 4.x through 5.x through 6.x (these have all been on
> > > >> thi
On 2/27/06, Ruslan Ermilov <[EMAIL PROTECTED]> wrote:
> On Sun, Feb 26, 2006 at 08:26:42PM +0100, Dimitry Andric wrote:
> > Ian Dowse wrote:
> > >> Okay, but why did 4.x through 5.x through 6.x (these have all been on
> > >> this particular machine) always boot with 115200 until now? :)
> >
> > > T
On Feb 25, 2006, at 9:14 PM, Ed Maste wrote:
Thus, I'm not surprised that you get a 9600 baud console without
an rc.conf setting. The thing that concerns me is your report that
the console does not run at 115200 even if /boot/loader.conf
contains comconsole_speed="115200".
I get a 9600 baud
On Feb 25, 2006, at 8:56 PM, Ian Dowse wrote:
They probably used 9600 for the boot blocks, and then switched to
115200 when /boot/loader started, so you didn't notice. Now the
settings from the boot blocks get used by /boot/loader.
Please document this loudly in the UPGRADING file. It caught
On Mon, Feb 27, 2006 at 10:38:20AM +0200, Ruslan Ermilov wrote:
> > Okay. I still think it would be wiser to just reinstall them during
> > installworld, just to be sure there's no incompatibilities...
> >
> It's not always possible to do: there can be different boot locations,
> the root FS can
Ruslan Ermilov wrote:
>> That's why installing 115200 baud boot blocks is still the better
>> solution for me; my BIOS doesn't have any possibility to set the COM
>> port speeds...
> The best for you would be to add -S115200 in /boot.config, after
> reinstalling new boot blocks (bsdlabel -B), and t
On Sun, Feb 26, 2006 at 09:26:02PM +0100, Dimitry Andric wrote:
> Ed Maste wrote:
> > So I suspect that the following happens when you boot:
> >
> > - your BIOS sets the serial port to 9600
>
> Yes.
>
> > - boot0 does nothing with the serial pot
>
> I'm using 'dangerously dedicated' disks, so i
On Sun, Feb 26, 2006 at 08:26:42PM +0100, Dimitry Andric wrote:
> Ian Dowse wrote:
> >> Okay, but why did 4.x through 5.x through 6.x (these have all been on
> >> this particular machine) always boot with 115200 until now? :)
>
> > They probably used 9600 for the boot blocks, and then switched to
On Sun, Feb 26, 2006 at 09:19:35PM +0100, Dimitry Andric wrote:
> > comconsole_speed= in /boot/loader.conf
> > existing speed, if comconsole is already set by previous stage
> > BOOT_COMCONSOLE_SPEED compile time default
>
> Well, the last item will simply never be hit, since there is ALWAYS a
>
Ed Maste wrote:
> So I suspect that the following happens when you boot:
>
> - your BIOS sets the serial port to 9600
Yes.
> - boot0 does nothing with the serial pot
I'm using 'dangerously dedicated' disks, so it's only boot[12] that is used.
> - boot1/2 reads the -P in /boot.config and detect
Ian Dowse wrote:
> The problem may be that your boot blocks were compiled with
> BOOT_COMCONSOLE_SPEED set to 9600. Try reinstalling them with e.g.
> `disklabel -B ad0s1' (make sure you get the right device name -
> it should be the slice that you boot from).
Argh, shouldn't have done this without
Ed Maste wrote:
>> Okay, but why did 4.x through 5.x through 6.x (these have all been on
>> this particular machine) always boot with 115200 until now? :)
> Because now the loader has new behaviour of using the existing speed
> if the previous stage indicates a serial port is in use, instead
> of
Ian Dowse wrote:
>> Okay, but why did 4.x through 5.x through 6.x (these have all been on
>> this particular machine) always boot with 115200 until now? :)
> They probably used 9600 for the boot blocks, and then switched to
> 115200 when /boot/loader started, so you didn't notice. Now the
> settin
On Sun, Feb 26, 2006 at 02:37:08AM +0100, Dimitry Andric wrote:
> Ed Maste wrote:
> > What's in your /boot.config?
>
> In my case, I use -P, because I usually don't have a keyboard hooked up,
> but ocasionally do use it. Additionally, I had console="comconsole" in
> my /boot/loader.conf. Howeve
On Sun, Feb 26, 2006 at 02:40:17AM +0100, Dimitry Andric wrote:
> Ian Dowse wrote:
> > The problem may be that your boot blocks were compiled with
> > BOOT_COMCONSOLE_SPEED set to 9600. Try reinstalling them with e.g.
> > `disklabel -B ad0s1' (make sure you get the right device name -
> > it shoul
In message <[EMAIL PROTECTED]>, Dimitry Andric writes:
>Okay, but why did 4.x through 5.x through 6.x (these have all been on
>this particular machine) always boot with 115200 until now? :)
They probably used 9600 for the boot blocks, and then switched to
115200 when /boot/loader started, so you d
Ian Dowse wrote:
> The problem may be that your boot blocks were compiled with
> BOOT_COMCONSOLE_SPEED set to 9600. Try reinstalling them with e.g.
> `disklabel -B ad0s1' (make sure you get the right device name -
> it should be the slice that you boot from).
Okay, but why did 4.x through 5.x thro
Ed Maste wrote:
> What's in your /boot.config?
In my case, I use -P, because I usually don't have a keyboard hooked up,
but ocasionally do use it. Additionally, I had console="comconsole" in
my /boot/loader.conf. However, commenting that out doesn't help either.
I guess the -P option causes the
On Sun, Feb 26, 2006 at 12:23:59AM +0100, Dimitry Andric wrote:
> > comconsole_speed="115200" in loader.conf should override it
> > if you don't want to replace boot2 or change /boot.config.
>
> Yes, I've tried this, but it didn't work, or maybe I just didn't try
> hard enough. :) I'll try it ag
In message <[EMAIL PROTECTED]>, Dimitry Andric writes:
>Ed Maste wrote:
>> The way this is supposed to work is that you can put -S
>> in /boot.config, which gets used by boot2, and the loader then
>> detects that the serial console is already in use and defaults
>> to the existing speed.
>
>Ah, I d
Ed Maste wrote:
> The way this is supposed to work is that you can put -S
> in /boot.config, which gets used by boot2, and the loader then
> detects that the serial console is already in use and defaults
> to the existing speed.
Ah, I didn't try that yet. However, I would expect that the
BOOT_COM
On Sat, Feb 25, 2006 at 10:55:01PM +0100, Dimitry Andric wrote:
> Hi,
>
> I believe this MFC commit:
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/boot/i386/libi386/comconsole.c?rev=1.10.10.1&content-type=text/x-cvsweb-markup
> broke the speed-setting of the serial console at boot time, for REL
Dimitry Andric wrote:
> whereas in the previous version it was set (hardcoded) to COMSPEED,
> which in its turn came from BOOT_COMCONSOLE_SPEED in
> boot/i386/libi386/Makefile.
>
> Anyone know of a way to restore the old behaviour? I'll experiment here
> with reverting the comconsole.c file to th
Hi,
I believe this MFC commit:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/boot/i386/libi386/comconsole.c?rev=1.10.10.1&content-type=text/x-cvsweb-markup
broke the speed-setting of the serial console at boot time, for RELENG_6.
At least for me, it doesn't set the speed to 115200 (as specified i
32 matches
Mail list logo
