On Wednesday 30 August 2006 13:50, John Kelly wrote:
> On Wed, 30 Aug 2006 14:35:12 -0700, tom arnall <[EMAIL PROTECTED]>
>
> wrote:
> >Is there another place where bootup messages are recorded?
>
> Does your /etc/default/bootlogd say:
> > # Run bootlogd at
On Wed, 30 Aug 2006 14:35:12 -0700, tom arnall <[EMAIL PROTECTED]>
wrote:
>Is there another place where bootup messages are recorded?
Does your /etc/default/bootlogd say:
> # Run bootlogd at startup ?
> BOOTLOGD_ENABLE=yes
That captures additional messages in /var/log/boot
Be
of dmesg. Is there
> another place where bootup messages are recorded?
Perhaps you'd like to try the Scroll Lock during boot-up
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Recently I have begun to get a great number of messages at boot-up which are
about 'querying' scsi drives. I need to get a better look at the messages but
cannot find them in the logs in /var/log nor in the output of dmesg. Is there
another place where bootup messages are recorded?
Colin Ingram wrote:
Greg wrote:
It matters because if Paulo or anyone else is not using udev then they
want be affected by the udev/bootlogd init script bug. Mainly because
they want have /etc/init.d/udev on their system which umounts /dev/pts
so bootlogd can no longer work.
I can't bel
Greg wrote:
Paulo M C Aragão wrote:
Colin Ingram wrote on Jun, 15:
This is curious. I'm running Debian stock kernel 2.4.27-2-686 and
neither:
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
I don't think these are needed or that they are the problem
seem to be configured (checked /b
Paulo M C Aragão wrote:
Colin Ingram wrote on Jun, 15:
This is curious. I'm running Debian stock kernel 2.4.27-2-686 and
neither:
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
I don't think these are needed or that they are the problem
seem to be configured (checked /boot/config-2.4
Paulo M C Aragão wrote:
My ignorance: how do I check if I am using devfs or udev ?
Good question. I think `mount' will tell you in the case of devfs. I
thought it would for udev too, but it hasn't uttered anything useful for me.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
Colin Ingram wrote on Jun, 15:
> >This is curious. I'm running Debian stock kernel 2.4.27-2-686 and
> >neither:
> >
> >CONFIG_LEGACY_PTYS=y
> >CONFIG_LEGACY_PTY_COUNT=256
> >
> >
> I don't think these are needed or that they are the problem
>
> >seem to be configured (checked /boot/config-2.4.27
Paulo M C Aragão wrote:
Stephen R Laniel wrote on Jun, 14:
See also
http://lists.debian.org/debian-user/2005/03/msg03789.html
This is curious. I'm running Debian stock kernel 2.4.27-2-686 and
neither:
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
I don't think these are neede
Stephen R Laniel wrote:
On Tue, Jun 14, 2005 at 09:20:07PM -0300, Paulo M C Aragão wrote:
This fantastic list help me on this one before.
Put this in /etc/default/bootlogd:
BOOTLOGD_ENABLE=yes
Next time you boot, every msg sent to /dev/console will end up in
/var/log/boot.
Cool! Tw
Stephen R Laniel wrote on Jun, 14:
> See also
> http://lists.debian.org/debian-user/2005/03/msg03789.html
This is curious. I'm running Debian stock kernel 2.4.27-2-686 and
neither:
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
seem to be configured (checked /boot/config-2.4.27-2-686), but bo
On Tue, Jun 14, 2005 at 09:20:07PM -0300, Paulo M C Aragão wrote:
> This fantastic list help me on this one before.
>
> Put this in /etc/default/bootlogd:
>
> BOOTLOGD_ENABLE=yes
>
> Next time you boot, every msg sent to /dev/console will end up in
> /var/log/boot.
Cool! Two things.
1) When I
John Kelly wrote on Jun, 13:
> When booting, I see console messages from programs using stdout and
> stderr, scrolling by too fast to read. They are not logged in dmesg
> or any /var/log file.
>
> How to capture them?
This fantastic list help me on this one before.
Put this in /etc/default/boo
On Mon, Jun 13, 2005 at 03:59:23PM -0400, John Kelly wrote:
> I used sysv-rc-conf to enable it, but it did not start. Then I
> noticed its script checks BOOTLOGD_ENABLE in /etc/default/bootlogd
> before starting.
>
> Debian has a lot of knobs to turn; I see it will take some time to
> learn my wa
On Mon, 13 Jun 2005 20:21:06 +0100, michael
<[EMAIL PROTECTED]> wrote:
>On Mon, 2005-06-13 at 15:15 -0400, John Kelly wrote:
>> When booting, I see console messages from programs using stdout and
>> stderr, scrolling by too fast to read. They are not logged in dmesg
>> or any /var/log file.
>>
On Monday 13 June 2005 21.21, michael wrote:
> On Mon, 2005-06-13 at 15:15 -0400, John Kelly wrote:
> > When booting, I see console messages from programs using stdout and
> > stderr, scrolling by too fast to read. They are not logged in dmesg
> > or any /var/log file.
> >
> > How to capture them?
On Mon, 2005-06-13 at 15:15 -0400, John Kelly wrote:
> When booting, I see console messages from programs using stdout and
> stderr, scrolling by too fast to read. They are not logged in dmesg
> or any /var/log file.
>
> How to capture them?
man bootlogd
--
Michael Bane
Atmospheric Physics Grou
When booting, I see console messages from programs using stdout and
stderr, scrolling by too fast to read. They are not logged in dmesg
or any /var/log file.
How to capture them?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Capturing all bootup messages
Date: Tue, 3 Aug 2004 16:54:31 +0200
On Tue, Aug 03, 2004 at 09:40:35AM -0500, Kent West wrote:
> >My question now is this: how can I record all those messages into a
> >log file or, how can
We really need some standard way of capturing those messages. I think I've
heard of some switch you can add or line you can uncomment in
/etc/init.d/bootlog, but I'm not sure.
One way that should work is to deactivate any auto-startup of X (kdm, etc)
and then the next boot will stop at a cons
On Tue, Aug 03, 2004 at 09:40:35AM -0500, Kent West wrote:
> >My question now is this: how can I record all those messages into a
> >log file or, how can I pause the system to read those message?
> >Pressing control-C or shift-break does not pause the system.
> >
> We really need some standard wa
Ogya Chief wrote:
Hi All,
When my machine is booting up, I see some fatal error messages
scrolling past very fast. Running dmesg does not show those messages,
neither does /var/log/messages.
My question now is this: how can I record all those messages into a
log file or, how can I pause the sys
Hi All,
When my machine is booting up, I see some fatal error messages scrolling
past very fast. Running dmesg does not show those messages, neither does
/var/log/messages.
My question now is this: how can I record all those messages into a log file
or, how can I pause the system to read those
On Sun, Apr 25, 2004 at 11:37:44AM +0200, Niels L. Ellegaard wrote:
> PS: I never understood why is bootlogd turned of by default. In case
> some big guru is reading this, I would be grateful for a pointer to an
> explanation. :)
Gurus become gurus by reading. :) See the sysvinit changelog.
sysvi
[EMAIL PROTECTED] writes:
> Does dmesg holds the complete log of the bootup messages? If not, is
> there any way for me to retrieve and view the complete log of the
> bootup messages?
There is daemon called bootlogd which creates a bootlog-file named
/var/log/boot. The bootlogd is pa
L PROTECTED] wrote:
> > >>Before hitting the display manager, the bootup messages are
> > >> scrolling off the screen too fast. I saw some lines mentioning
> > >> about some modules not found. One of them is microcode module
> > >> (couldn't catch th
Geoff Thurman wrote:
Hello Hugo,
That's interesting; I'll have to remember to add YMMV in future. I
think the Ctrl-s and Ctrl-q bit might be in Paul Sheer's RUTE User's
Tutorial and Exposition, but I'm not sure. I first saw it in a post on
this list, from, I think, Colin Watson. The shift-Pgup
On Sat, Apr 17, 2004 at 10:09:41AM +0200, John L Fjellstad wrote:
> Set BOOTLOGD_ENABLE to yes in /etc/default/bootlogd
...you'll need version 2.85-9 of sysvinit / initscripts.
--
Pigeon
Be kind to pigeons
Get my GPG key here: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x21C61F7F
pgp00
On Saturday 17 April 2004 1:41 pm, hugo vanwoerkom wrote:
> Geoff Thurman wrote:
> > On Saturday 17 April 2004 1:57 am, [EMAIL PROTECTED] wrote:
> >>Before hitting the display manager, the bootup messages are
> >> scrolling off the screen too fast. I saw some lines
Geoff Thurman wrote:
On Saturday 17 April 2004 1:57 am, [EMAIL PROTECTED] wrote:
Before hitting the display manager, the bootup messages are scrolling
off the screen too fast. I saw some lines mentioning about some
modules not found. One of them is microcode module (couldn't catch
the rest).
On Saturday 17 April 2004 1:57 am, [EMAIL PROTECTED] wrote:
> Before hitting the display manager, the bootup messages are scrolling
> off the screen too fast. I saw some lines mentioning about some
> modules not found. One of them is microcode module (couldn't catch
> the re
Set BOOTLOGD_ENABLE to yes in /etc/default/bootlogd
--
John L. Fjellstad
web: http://www.fjellstad.org/ Quis custodiet ipsos custodes
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
type in
as root
$ demsg | more
GM
- Original Message -
From: "Kent West" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, April 17, 2004 2:46 AM
Subject: Re: Is there a complete log to the bootup messages?
> [EMAIL PROTECTED] wrote:
>
> >
[EMAIL PROTECTED] wrote:
Do you know where can I find logs for the various init level?
They should be in /var/log. For example, in my /etc/rc2.d, I have the
script "S99kdm", which is a symlink to /etc/init.d/kdm. So I look in
/var/log, and sure enough there's a "kdm.log" file.
However, not a
Do you know where can I find logs for the various init level?
Thanks :)
> Kent Westwrote:
[EMAIL PROTECTED] wrote:
>
> Before hitting the display manager, the bootup messages are
scrolling
> off the screen too fast. I saw some lines mentioning about some
> modules not found.
[EMAIL PROTECTED] wrote:
Before hitting the display manager, the bootup messages are scrolling
off the screen too fast. I saw some lines mentioning about some
modules not found. One of them is microcode module (couldn't catch
the rest). However, when I do a dmesg | grep -i
microcode, it i
Before hitting the display manager, the bootup messages are scrolling
off the screen too fast. I saw some lines mentioning about some
modules not found. One of them is microcode module (couldn't catch
the rest). However, when I do a dmesg | grep -i
microcode, it is not found.
Does dmesg hold
Quoting Jose Marin ([EMAIL PROTECTED]):
>
> No, I don't mean the messages from the init scripts (I guess you can use
> the VERBOSE variable in /etc/default/rcS for that); I mean the bootup
> messages from the _kernel_, the ones you can read again with dmsg.
Try Documentation/
No, I don't mean the messages from the init scripts (I guess you can use
the VERBOSE variable in /etc/default/rcS for that); I mean the bootup
messages from the _kernel_, the ones you can read again with dmsg.
I searched the file /usr/src/linux/Documentation/kernel-parameters.txt
an
Quoting Jonas Steverud ([EMAIL PROTECTED]):
> "Krosigk, Lorenz Von" <[EMAIL PROTECTED]> writes:
>
> > is there a way to hide the bootup messages at the screen, to direct them
> > (the important ones like warnings and errors) to a file and to show
> > so
Hi,
is there a way to hide the bootup messages at the screen, to direct them
(the important ones like warnings and errors) to a file and to show
something else on the screen meanwhile the machine starts up?
I didn't find anything in the Boot-Promt HowTo nor in the init or inittab
manpages (
Hello Debian Land...
The best way to see all the messages is to not run any programs on tty1 (the
first
virtual terminal - also the default terminal). You can then scroll all the way
back
to the bios boot information using the shift+pageup key combination.
So long as you run no programs (or at
>
> On Thu, 26 Nov 1998, Stan Brown wrote:
>
> > In FreeBSD, you can hit the {Scroll Lock} button and scroll back on the
> > console using {Page Up and {Page Donw} keys.
> >
> > Is there anything similar in Debian?
> >
>
> Sure. Shift-PageUp and Shift-PageDown. At least, they work
On Thu, 26 Nov 1998, Stan Brown wrote:
>In FreeBSD, you can hit the {Scroll Lock} button and scroll back on the
> console using {Page Up and {Page Donw} keys.
>
> Is there anything similar in Debian?
It is possible with SHIFT+PGUP, but you can also look at boot kernel messages
by the c
works... but if it's just bootup messages you're looking for you can
type 'dmesg' at the prompt and it will spit out all the kernel bootup
stuff. HTH
.adam
--
Adam Lazur - Computer Engineering Undergrad - Lehigh University
icq# 3354423 - http://www.lehigh.edu
On Thu, 26 Nov 1998, Stan Brown wrote:
> In FreeBSD, you can hit the {Scroll Lock} button and scroll back on the
> console using {Page Up and {Page Donw} keys.
>
> Is there anything similar in Debian?
>
Sure. Shift-PageUp and Shift-PageDown. At least, they work in xterms. I
*t
In FreeBSD, you can hit the {Scroll Lock} button and scroll back on the
console using {Page Up and {Page Donw} keys.
Is there anything similar in Debian?
--
Stan Brown [EMAIL PROTECTED]770-996-6955
Factory Automation Systems
Atlanta
"...jade login: Jun 20 14:59:59 could not find host name "jade".
VV_DTerminated."
Then nothing else. But when I press enter it goes to the login prompt as usual.
Any ideas?
Timothy
PS: My linux logo also kind of stopped working; its not on any of the VCs any
more, what would cause this?
>
> Zenon Fortuna wrote:
> >
> > Depending on the system setup, the most of the boot-up messages are also
> > collected into "/var/log/messages". At least my Debian system works like
> > that.
>
> this is unlikely to contain the kernel start up messages (as opposed to
> stuff that started after
Easy enough to fix... Edit your /etc/conf.modules and add the
following:
alias net-pf-4 off
alias net-pf-5 off
alias netmask off
alias broadcast off
(I only use the first two on my system, but it works for me...)
-Erik
--
Erik B. Andersen Web:http://www.et.byu.edu/~andersee/
248
I recently recompiled, packaged, and installed a 2.0.20 kernel.
I edited /etc/modules so that no modules are loaded at bootup (just using
"auto"). However I now get the following messages at bootup:
modprobe: can't locate module net-pf-4
modprobe: can't locate module net-pf-5
"""
52 matches
Mail list logo
