Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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.4-STABLE to 6.1-PRE last week, and again over the weekend. I did the following: make buildworld and buildkernel with BOOT_COMCONSOLE_SPEED=115200 in / etc/make.conf, options CONSPEED=115200 in the kernel config. make installkernel, reboot, yada yada yada, installworld,.. then boot0cfg -B aacd0 to update the boot blocks. Now, at this point I expected to have a 115200 console on the next boot. Nope. Got 9600 baud again. The other side-effect is now I get this stupid Boot F1 for DOS and F2 for FreeBSD menu which defaults to DOS (which is the Dell utility partition). How do I get back to the original boot style where it just boots freebsd without any menu? So I updated my /boot.config to read: -Dh -S115200 now on boot, the boot0 drops to the prompt and makes me type in / boot/loader to continue the process. It is as if it forgot what file to load, and ignores the -S option anyhow, because I still end up with a 9600 baud console. I ran out of time to try setting the speed in /boot/loader.conf but I'm not expecting any miracles. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 buildworld and buildkernel with BOOT_COMCONSOLE_SPEED=115200 in / etc/make.conf, options CONSPEED=115200 in the kernel config. make installkernel, reboot, yada yada yada, installworld,.. then boot0cfg -B aacd0 to update the boot blocks. Now, at this point I expected to have a 115200 console on the next boot. Nope. Got 9600 baud again. 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 can optionally install in the MBR to give a menu of slices to boot from - it has nothing to do with reading /boot.config and doesn't set up the serial port. If the slice you boot from is aacd0s2 then you can use `disklabel -B aacd0s2' to install the new boot blocks (boot1 and boot2) into that slice. The other side-effect is now I get this stupid Boot F1 for DOS and F2 for FreeBSD menu which defaults to DOS (which is the Dell utility partition). How do I get back to the original boot style where it just boots freebsd without any menu? That's boot0. `fdisk -B /dev/aacd0' should put back the basic MBR. So I updated my /boot.config to read: -Dh -S115200 now on boot, the boot0 drops to the prompt and makes me type in / boot/loader to continue the process. It is as if it forgot what file to load, and ignores the -S option anyhow, because I still end up with a 9600 baud console. 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. Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 years of experience with running these boxes is just not enough :-( Perhaps UPDATING needs clarification as to which command to use to update boot blocks, because I'm *sure* it will bite others too. Thanks again. This was a very helpful post for me. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 strange char duplication after seeing the F1 prompt. The BIOS has console redirection, so I can see it throughout the bootup process. F1 FreeBSD Default: F1 //bbtt..ccoo- ffiigg:: --DDhh// BTX loader 1.00 BTX version is 1.01 Consoles:ointernal video/keyboardalserialiportoo//kkeeyybbooaarrdd sseerriiaaBIOSpdrivetA: is disk0 BIOSOdrivedC:risvdisk1AA:: iiss ddiisskk00 BIOSO638kB/504704kBeavailableimemoryiisskk11 BBIIOOSS 663388kkBB//550044770044kkBB aavvaaiillaabbllee mmeemmoorryy FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED],tSataMar 4l04:44:56rEST 2006)vviissiioonn LLoadingi/boot/defaults/loader.confauullttss//llooaaddeerr..ccoonnff a,, SSaat//boot/kernel/kerneletext=0x2e7378ddata=0x37d14+0x2ecf8ssyms=[0x4+0x3f8f0+0x4+0x513d4]dd44\\ \\\ If for some reason, boot.config is bogus, I can actually type in /boot/loader and it will load, just what I type is duplicated. I have # cat /boot/loader.conf #debug.acpi.disabled=sysresource beastie_disable=YES # Turn the beastie boot menu on and off comconsole_speed=19200 and # cat /boot.config -Dh -S19200 After hitting enter as I normally do, the rest of the boot process is normal looking and works fine /boot/kernel/acpi.koetext=0x42e34ddata=0x2280+0x10f0ssyms=[0x4+0x7ad0+0x4+0xa709]//a77009 Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-PRERELEASE #0: Sat Mar 4 07:20:49 EST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/gas Timecounter i8254 frequency 1193182 Hz quality 0 CPU: VIA C3 Nehemiah+RNG+ACE (796.77-MHz 686-class CPU) Origin = CentaurHauls Id = 0x698 Stepping = 8 Features=0x381b03fFPU,VME,DE,PSE,TSC,MSR,MTRR,PGE,CMOV,PAT,MMX,FXSR,SSE real memory = 517865472 (493 MB) avail memory = 497393664 (474 MB) ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 1.00 BTX version is 1.01 Consoles:ointernal video/keyboardalserialiportoo//kkeeyybbooaarrdd That's probably expected if you enable dual console mode (-D) when the BIOS is also redirecting VGA output to the serial port. Each character goes to both the serial port and the screen, but the BIOS is also copying screen characters to the serial port so each character appears twice. Once the kernel starts it no longer uses BIOS calls to output to the screen. There might be a BIOS option to disable the redirection when booting. Alternatively you could remove the -D, but you will no longer get kernel boot messages on the VGA console. Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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
115200 when /boot/loader started, so you didn't notice. Now the
settings from the boot blocks get used by /boot/loader.
Ah, but this still means that /boot/loader used to use a hardcoded
default specified in /etc/make.conf, and now it doesn't honor that anymore.
Have you checked with documentation?
: comconsole_speed
: Defines the speed of the serial console (i386 and amd64 only).
: If the previous boot stage indicated that a serial console is
: in use then this variable is initialized to the current speed
: of the console serial port. Otherwise it is set to 9600 unless
: this was overridden using the BOOT_COMCONSOLE_SPEED variable
: when loader was compiled. Changes to the comconsole_speed
: variable take effect immediately.
Boot blocks need to be installed manually - installworld installs
the boot blocks as files in /boot/boot{1,2}, but when booting, it
is the boot blocks in the first 8k of the slice that are used, not
the /boot/boot{1,2} files.
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 be a remote one, it can be a diskless system, etc.
Cheers,
--
Ruslan Ermilov
[EMAIL PROTECTED]
FreeBSD committer
pgpVnv0QPXRfw.pgp
Description: PGP signature
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 it's only boot[12] that is used. - boot1/2 reads the -P in /boot.config and detects no keyboard, and then sets the serial port to 9600 and the console to comconsole Indeed, I never got the /boot.config: -P message on the serial console before. Now I get it, using updated boot blocks. - the loader detects that the serial port is enabled and is already set to 9600 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. This turns out to be an error on my part, sorry to have you worried. :) I'd accidentally put console_speed=115200 in loader.conf. With comconsole_speed=115200 and 9600 baud boot blocks, it works okay, although you don't see any of the boot[12] messages, of course. 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 throw everything else that's related from make.conf and loader.conf. Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgprJ5XO3cqOf.pgp Description: PGP signature
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 throw everything else that's related from make.conf and loader.conf. I'll try this out, but I still usually like hardcoded defaults. :) signature.asc Description: OpenPGP digital signature
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 be a remote one, it can be a diskless system, etc. Not to mention that broken boot blocks will destroy the ability of your system to boot, and require major reconstructive surgery. Much safer to only install them on command. Kris pgpLFwYMuOsZO.pgp Description: PGP signature
Re: RELENG_6: serial console drops back from 115200 to 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 me totally by surprise that the console speed was now 9600. I thought I lost my serial console since the BIOS was booting up at 115200. If it weren't for the other error (ACPI) keeping the kernel from booting, I would have realized it *before* I drove down to the office late saturday night. See, I needed a serial console to disable part of acpi for debugging :-( Anyhow, please, please document this in UPGRADING so others won't be bitten by it. Thanks! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 console with the following after upgrade from 5.4: in make.conf: BOOT_COMCONSOLE_SPEED=115200 in kernel config: options CONSPEED=115200 # Speed for serial console /boot.config has just -Dh /boot/loader.conf just disables ACPI timer. The BIOS boots to 115200 serial output, too. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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? :) 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. Ah, but this still means that /boot/loader used to use a hardcoded default specified in /etc/make.conf, and now it doesn't honor that anymore. Have you checked with documentation? : comconsole_speed : Defines the speed of the serial console (i386 and amd64 only). : If the previous boot stage indicated that a serial console is : in use then this variable is initialized to the current speed : of the console serial port. Otherwise it is set to 9600 unless : this was overridden using the BOOT_COMCONSOLE_SPEED variable : when loader was compiled. Changes to the comconsole_speed : variable take effect immediately. 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 Handbook 22.6.5.1 Setting a Faster Serial Port Speed. Thanks, Rong-En Fan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 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 settings from the boot blocks get used by /boot/loader. Ah, but this still means that /boot/loader used to use a hardcoded default specified in /etc/make.conf, and now it doesn't honor that anymore. Have you checked with documentation? : comconsole_speed : Defines the speed of the serial console (i386 and amd64 only). : If the previous boot stage indicated that a serial console is : in use then this variable is initialized to the current speed : of the console serial port. Otherwise it is set to 9600 unless : this was overridden using the BOOT_COMCONSOLE_SPEED variable : when loader was compiled. Changes to the comconsole_speed : variable take effect immediately. Which way is preferred: setting comconsole_speed, -S in boot.config, or using harded code BOOT_COMCONSOLE_SPEED in make.conf? -S is the most convenient, as it will cause the serial port's speed to be consistent throughout all stages, boot2, loader, and kernel. If now the most preferred way is to using -S or comconsole_speed in loader.conf, please update that in Handbook 22.6.5.1 Setting a Faster Serial Port Speed. Someone with doc/-fu should pick it up I think. Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgpRZMBBYmm8W.pgp Description: PGP signature
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 Handbook 22.6.5.1 Setting a Faster Serial Port Speed. 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. Note that the instructions in 22.6.5.1 will still apply -- if you reinstall boot blocks compiled with BOOT_COMCONSOLE_SPEED=115200, the loader will automatically pick that up as well. You're right though that the handbook should document the preferred way of accomplishing this. -ed ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 comconsole is already in use. If you've changed BOOT_COMCONSOLE_SPEED in make.conf(5) and installed a new loader, but have not rebuilt and reinstalled the boot blocks, then your loader will leave the console at 9600 baud. You may either set comconsole_speed in loader.conf(5), or reinstall new boot blocks as described in boot(8). -ed ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 by the previous boot stage, if the comconsole is already in use. If you've changed BOOT_COMCONSOLE_SPEED in make.conf(5) and installed a new loader, but have not rebuilt and reinstalled the boot blocks, then your loader will leave the console at 9600 baud. You may either set comconsole_speed in loader.conf (5), or reinstall new boot blocks as described in boot(8). -ed ... or set -S option in boot.config. From other discussion, the -S option seems to be the most straightforward method. The boot block update is described in boot0cfg(8) not boot(8), and must be done post-installworld, just to be 100% clear. Thanks for adding it to UPDATING. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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
settings from the boot blocks get used by /boot/loader.
Ah, but this still means that /boot/loader used to use a hardcoded
default specified in /etc/make.conf, and now it doesn't honor that anymore.
There should at least be a notice in UPDATING, e.g. don't forget to set
comconsole_speed in your loader.conf, or your serial console won't work
anymore after upgrading. It would probably save some people a drive to
the colocation facility... ;)
Boot blocks need to be installed manually - installworld installs
the boot blocks as files in /boot/boot{1,2}, but when booting, it
is the boot blocks in the first 8k of the slice that are used, not
the /boot/boot{1,2} files.
Okay. I still think it would be wiser to just reinstall them during
installworld, just to be sure there's no incompatibilities...
signature.asc
Description: OpenPGP digital signature
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 blindly jamming in a compile-time setting. Fine, but please be aware that this new behaviour violates POLA, at least without a stern notice in UPDATING. :) My idea about hard coded defaults has always been that they are followed, not ignored... 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 previous stage, isn't there? So then you might as well remove the compile time default. Or at least make clear that the compile time default only applies to boot[12], and not the loader. Anyway, I also thought that installworld would take care of installing any updated boot blocks, if necessary. I'll manually install them and see what I end up with. It doesn't seem that way. They'll be placed in /boot, but not in the mbr or slice I think. Indeed, as Ian explained. FYI, I've just installed new boot blocks with a configured BOOT_COMCONSOLE_SPEED, commented out the console= and comconsole_speed= entries in loader.conf, and this works as expected now. However, please keep in mind that this might hit non-binary upgraders who use serial consoles, e.g. people with remote boxes in faraway places. They should be warned to either upgrade their bootblocks manually, or set the speed directives in loader.conf. signature.asc Description: OpenPGP digital signature
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 thinking on a dangerously dedicated disk. :) But after recovering the partition table with fdisk, the new boot blocks work as expected, thanks. Previously both /boot/loader and the boot blocks would override the serial port speed according to BOOT_COMCONSOLE_SPEED, but I believe that since the recent change, loader will assume that if the boot blocks requested a serial console, then they will have already set up the correct speed. Yes, so people should be urged to upgrade their boot blocks, in case of a non-binary upgrade. (I assume that a binary upgrade WILL install fresh boot blocks?) signature.asc Description: OpenPGP digital signature
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 detects no keyboard, and then sets the serial port to 9600 and the console to comconsole Indeed, I never got the /boot.config: -P message on the serial console before. Now I get it, using updated boot blocks. - the loader detects that the serial port is enabled and is already set to 9600 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. This turns out to be an error on my part, sorry to have you worried. :) I'd accidentally put console_speed=115200 in loader.conf. With comconsole_speed=115200 and 9600 baud boot blocks, it works okay, although you don't see any of the boot[12] messages, of course. 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... signature.asc Description: OpenPGP digital signature
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 previous stage, isn't there? The second case only applies if the previous stage has set the console to the comconsole. If your /boot.config is empty, and loader.conf has console=comconsole, the compile-time BOOT_COMCONSOLE_SPEED applies. -ed ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 the previous version, to see if that helps, but a permanent solution would be better. :) Confirmed, putting back rev 1.10 of comconsole.c restores the old behaviour. My serial console runs at 115200 baud again. I still don't get why comconsole_speed in /boot/loader.conf didn't work with the newer revision, though... signature.asc Description: OpenPGP digital signature
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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.1content-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 in make.conf) anymore, it always stays at 9600, even when I put comconsole_speed=115200 in loader.conf. The way this is supposed to work is that you can put -Sspeed 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. comconsole_speed=115200 in loader.conf should override it if you don't want to replace boot2 or change /boot.config. I'm looking into it now. -ed ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
Ed Maste wrote: The way this is supposed to work is that you can put -Sspeed 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_COMCONSOLE_SPEED override in /etc/make.conf would simply continue to work as it had. 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 again with the 1.10.10.1 rev of comconsole.c. signature.asc Description: OpenPGP digital signature
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
In message [EMAIL PROTECTED], Dimitry Andric writes: Ed Maste wrote: The way this is supposed to work is that you can put -Sspeed 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_COMCONSOLE_SPEED override in /etc/make.conf would simply continue to work as it had. 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 again with the 1.10.10.1 rev of comconsole.c. 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). Previously both /boot/loader and the boot blocks would override the serial port speed according to BOOT_COMCONSOLE_SPEED, but I believe that since the recent change, loader will assume that if the boot blocks requested a serial console, then they will have already set up the correct speed. Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 again with the 1.10.10.1 rev of comconsole.c. I've just rebuilt a fresh RELENG_6 and installed the GENERIC bootblocks, which default to 9600 baud. I get a serial loader console at 115200 baud under each of the following conditions: /boot.config contains -h -S115200 /boot/loader.conf empty /boot.config contains -h /boot/loader.conf contains comconsole_speed=115200 /boot.config empty /boot/loader.conf contains console=comconsole and comconsole_speed=115200 What's in your /boot.config? Are your bootblocks from the 6.1 beta as well, or from a previous install? -ed ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 console variable to be set too? In that case comc_probe might pick it up, and never change the speed from what the BIOS configured. (Note that I've never used boot0sio, and AFAICs the 'normal' boot0 doesn't mess with the serial port speed.) Are your bootblocks from the 6.1 beta as well, or from a previous install? I never actively reinstalled them, except of course for running installworld. I've always assumed installworld would take care of that, and I really would be amazed if it didn't. :) signature.asc Description: OpenPGP digital signature
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 through 6.x (these have all been on this particular machine) always boot with 115200 until now? :) Anyway, I also thought that installworld would take care of installing any updated boot blocks, if necessary. I'll manually install them and see what I end up with. Previously both /boot/loader and the boot blocks would override the serial port speed according to BOOT_COMCONSOLE_SPEED, but I believe that since the recent change, loader will assume that if the boot blocks requested a serial console, then they will have already set up the correct speed. Ah, but notice that I didn't use boot0sio, but the regular boot0. It seems the serial port speed setting is compiled out in the latter version. Hence the port speed will be the BIOS default, which I alas can't change; it's always 9600n1. signature.asc Description: OpenPGP digital signature
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 didn't notice. Now the
settings from the boot blocks get used by /boot/loader.
Anyway, I also thought that installworld would take care of installing
any updated boot blocks, if necessary. I'll manually install them and
see what I end up with.
Boot blocks need to be installed manually - installworld installs
the boot blocks as files in /boot/boot{1,2}, but when booting, it
is the boot blocks in the first 8k of the slice that are used, not
the /boot/boot{1,2} files.
Ah, but notice that I didn't use boot0sio, but the regular boot0. It
seems the serial port speed setting is compiled out in the latter
version. Hence the port speed will be the BIOS default, which I alas
can't change; it's always 9600n1.
The boot blocks in question here are the ones installed inside the
slice (boot1 and boot2), rather than the boot0 MBR boot code, which
is installed in the very first sector of the disk. The boot0 boot
manager selects which slice to boot from, and then it invokes the
boot{1,2} blocks within the slice, they load /boot/loader and it
loads the kernel.
Ian
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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 should be the slice that you boot from). 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 blindly jamming in a compile-time setting. The loader should use the following, in order of priority: comconsole_speed= in /boot/loader.conf existing speed, if comconsole is already set by previous stage BOOT_COMCONSOLE_SPEED compile time default Anyway, I also thought that installworld would take care of installing any updated boot blocks, if necessary. I'll manually install them and see what I end up with. It doesn't seem that way. They'll be placed in /boot, but not in the mbr or slice I think. -ed ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
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. However, commenting that out doesn't help either. I guess the -P option causes the console variable to be set too? In that case comc_probe might pick it up, and never change the speed from what the BIOS configured. (Note that I've never used boot0sio, and AFAICs the 'normal' boot0 doesn't mess with the serial port speed.) True, but boot.config is processed by boot1/2 that's installed in the slice. That boot does have knowedge of the serial port and sets the speed as Ian points out. So I suspect that the following happens when you boot: - your BIOS sets the serial port to 9600 - boot0 does nothing with the serial pot - boot1/2 reads the -P in /boot.config and detects no keyboard, and then sets the serial port to 9600 and the console to comconsole - the loader detects that the serial port is enabled and is already set to 9600 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. -ed ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
