Date: Sat, 29 Dec 2007 21:42:38 +0100 From: Erik Trulsson <ertr1013@student.uu.se> To: Chuck Robey <chuckr@chuckr.org> Cc: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= <des@des.no>, ticso@cicely.de, FreeBSD-Hackers <freebsd-hackers@freebsd.org> Subject: Re: printing boot probe messages Message-ID: <20071229204238.GA45376@owl.midgard.homeip.net> In-Reply-To: <477698D8.2040802@chuckr.org> References: <476AF132.4080304@chuckr.org> <86abo1g2pu.fsf@ds4.des.no> <476EA521.9020707@chuckr.org> <20071224131425.GF23337@cicely12.cicely.de> <47715E1F.9080502@chuckr.org> <86sl1qikam.fsf@ds4.des.no> <477440A2.4070601@chuckr.org> <86sl1n14vv.fsf@ds4.des.no> <477698D8.2040802@chuckr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 29, 2007 at 01:58:32PM -0500, Chuck Robey wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > Dag-Erling Sm=F8rgrav wrote: > > Chuck Robey <chuckr@chuckr.org> writes: > >> Anyhow, in the midst of all the screwing around, I now find that, on t= he > >> Ascii-graphics FreeBSD loader UI, if I choose Option #5 (verbose loadi= ng) > >> then the printing of the regular probe messages starts back up (this i= s NOT > >> the verbose probe messages, it's the printing of the regular probing > >> messages.) I have to admit, I don't clearly know the difference, in > >> setting the variables, between verbose loading the verbose probing. I= know > >> the difference in what prints, but I don't know how to set this up > >> permanently without getting me that verbose probing, which I would lik= e to > >> avoid. > >=20 > > I have absolutely no idea what "verbose loading" and "verbose probing" > > mean. All I know of is the boot_verbose loader variable, which enables > > additional kernel messages. It does not affect the way the kernel is > > loaded, or the way devices are probed. > >=20 > > DES >=20 > I'm sorry, Dag, but I am myself having problem describing it. I have been > asking for names, but while I get some guesses about the loss of printing, > they haven't given me names to use. I see two items that I can get, when > booting. If I stick "-v" in /boot.config, then when the kernel probes, a= ll > the probes are verbose. Stuff like my HDaudio card print incredibly > verbose listings. OK, that's what I will call here Print#1 >=20 > The other thing is what I can see if I see the ascii-graphical loader (the > picture, in ascii-graphics, either of a BSDaemon, or of the letters > "FreeBSD", and a list of about 9 options for booting. If I select item #= 5, > then I get a listing. The listing is quite distinct from what I identify > as Print#1, so I'll call this Print#2. If I either hit return at that > ascii booting menu (to get the default) or select item #1, then when it > boots, I get no print at all: I see the very first spinner character (but > it never prints the second one), and the next thing I see, it's printing > "Login:". This Print#2 looks like the old non-verbose booting messages > that I used to see, before I lost the printing of all booting messages. Using 'boot -v' from /boot.config or choosing "Boot FreeBSD with verbose logging" from the loader's menu are both supposed to do exactly the same thing: Enable verbose messages from the kernel. If you do not see any boot messages at all, then my guess is that you probably have messed around with /boot/device.hints (or compiled in a hints file in the kernel) and removed or disabled the hints for the video adapter/system console. (At least that is what I had done the one time I lost the boot messages =66rom the kernel. As soon as I restored the hints to normal the normal boot messages returned.) (Without the hints the kernel apparently cannot print to the console until after it has probed and configured the video hardware, which is among the last devices to be probed.) >=20 > So, what do you call Print#1 and Print#2? Sure would help out, if folks > would answer these, and not only answer the real question, which is why my > ordinary non-verbose printing of booting messages went away. If you wan= t, > I can tell you, referencing the "verbose loading", that's my Print#2 When > I talked about "verbose probing" I am talking about the Print#1. The > reason I grabbed those definitions (clearly in desperation) is because it > seems to me that Print#1 is called out as device probing is starting, and > Print#2 is called out before all loading has begun. Yes, I know that those > two times abut one another, and aren't particularly good names. BUT note > that when you supply a name, that one I guarantee I will stick with, > religiously, for now on. There are two different kinds of output you get at boot time. The first is all the messages from the kernel as probes and configures all the hardware. The second is the output from the startup scripts that run after the kernel has finished loading. (The kernel can output some messages at this stage too, when the scripts do things like bringing up or down network interfaces, etc.) Enabling verbose boot messages makes the kernel messages more verbose. The output from the startup scripts is not affected by that. --=20 <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071229204238.GA45376>