From: Kushal Kumaran
Sent: 27 February 2022 19:01
To: debian-user@lists.debian.org
Cc: Michael Grant
Subject: Re: strange boot messages
cc-ing as requested
On Sun, Feb 27 2022 at 09:01:31 AM, Michael Grant wrote:
> I'm running Debian 11.2 stable on a Linode (a popular VPS). After
cc-ing as requested
On Sun, Feb 27 2022 at 09:01:31 AM, Michael Grant wrote:
> I'm running Debian 11.2 stable on a Linode (a popular VPS). After a recent
> update, I think from
> around 25th of January, I'm starting to see some strange messages in
> my logs:
>
> systemd[1]: First Boot Complete
On 2/27/22, Michael Grant wrote:
> I'm running Debian 11.2 stable on a Linode (a popular VPS). After a recent
> update, I think from
> around 25th of January, I'm starting to see some strange messages in
> my logs:
>
> systemd[1]: First Boot Complete was skipped because of a failed condition
> ch
I'm running Debian 11.2 stable on a Linode (a popular VPS). After a recent
update, I think from
around 25th of January, I'm starting to see some strange messages in
my logs:
systemd[1]: First Boot Complete was skipped because of a failed condition check
(ConditionFirstBoot=yes).
systemd[1]: ge
On 7/10/20 4:14 PM, Sven Hartge wrote:
Klaus Jantzen wrote:
On 7/10/20 11:48 AM, Sven Hartge wrote:
Klaus Jantzen wrote:
the first messages that appear on the screen during the boot process
seem to be messages from the BIOS;
they have a different format than the subsequent messages from bust
Klaus Jantzen wrote:
> On 7/10/20 11:48 AM, Sven Hartge wrote:
>> Klaus Jantzen wrote:
>>> the first messages that appear on the screen during the boot process
>>> seem to be messages from the BIOS;
>>> they have a different format than the subsequent messages from buster
>>> and they begin with
On 7/10/20 11:48 AM, Sven Hartge wrote:
Klaus Jantzen wrote:
the first messages that appear on the screen during the boot process
seem to be messages from the BIOS;
they have a different format than the subsequent messages from buster
and they begin with 'ACPI '.
As they disappear so fast, I
On Fri 10 Jul 2020 at 09:52:26 +0200, Klaus Jantzen wrote:
> Hi,
>
> the first messages that appear on the screen during the boot process seem to
> be messages from the BIOS;
>
> they have a different format than the subsequent messages from buster and
> they begin with 'ACPI '.
>
> As they di
Klaus Jantzen wrote:
> the first messages that appear on the screen during the boot process
> seem to be messages from the BIOS;
> they have a different format than the subsequent messages from buster
> and they begin with 'ACPI '.
> As they disappear so fast, I cannot read them.
> Where ar
hi,
phone videorecord?
Klaus Jantzen ezt írta (időpont: 2020. júl. 10.,
P 9:52):
> Hi,
>
> the first messages that appear on the screen during the boot process
> seem to be messages from the BIOS;
>
> they have a different format than the subsequent messages from buster
> and they begin with '
Hi,
the first messages that appear on the screen during the boot process
seem to be messages from the BIOS;
they have a different format than the subsequent messages from buster
and they begin with 'ACPI '.
As they disappear so fast, I cannot read them.
Where are these messages logged or
On 2015-12-01, Brian wrote:
> On Tue 01 Dec 2015 at 12:33:23 +, Liam O'Toole wrote:
>
>> On 2015-11-30, Klaus Jantzen wrote:
>> > Hallo,
>> >
>> > where are the messages stored that Debain produces during booting (checking
>> > of various components, startup of e.g. postgresql, messages issue
On Tue 01 Dec 2015 at 12:33:23 +, Liam O'Toole wrote:
> On 2015-11-30, Klaus Jantzen wrote:
> > Hallo,
> >
> > where are the messages stored that Debain produces during booting (checking
> > of various components, startup of e.g. postgresql, messages issued by
> > /udev,
> > error messages in
On 2015-11-30, Klaus Jantzen wrote:
> Hallo,
>
> where are the messages stored that Debain produces during booting (checking
> of various components, startup of e.g. postgresql, messages issued by
> /udev,
> error messages in case a routine could not be started, etc).
>
> I looked in /var/log thro
On Mon, 30 Nov 2015 19:04:08 +0100
Klaus Jantzen wrote:
> Hallo,
>
> where are the messages stored that Debain produces during booting (checking
> of various components, startup of e.g. postgresql, messages issued by
> /udev,
> error messages in case a routine could not be started, etc).
>
> I
Hallo,
where are the messages stored that Debain produces during booting (checking
of various components, startup of e.g. postgresql, messages issued by
/udev,
error messages in case a routine could not be started, etc).
I looked in /var/log through all logs but could not find those messages.
--
On Tuesday, August 25, 2015 at 8:30:05 AM UTC-5, Darac Marjal wrote:
> "mountpoint" is a utility which reports if a given path is a mountpoint.
> It would appear that this utility is missing.
You sir, are correct. I was mis-reading the errors as the mount point (the
location) was not being found
Am 25.08.2015 um 14:51 schrieb brett.frierm...@gmail.com:
> Running Debian Jessie on a desktop and did an upgrade Sunday night.
Which version of util-linux and initscripts do you have installed?
This tools moved from initscripts to util-linux, so maybe you have a new
initscripts version combined
On Tue, Aug 25, 2015 at 05:51:48AM -0700, brett.frierm...@gmail.com wrote:
> Running Debian Jessie on a desktop and did an upgrade Sunday night.
> Everything continued working fine, although I don't think I rebooted at all.
> Last night went to boot and I get a ton of "mountpoint: not found" mess
Running Debian Jessie on a desktop and did an upgrade Sunday night. Everything
continued working fine, although I don't think I rebooted at all. Last night
went to boot and I get a ton of "mountpoint: not found" messages during boot.
After boot the console login displays for a fraction of a seco
Am 2014-03-15 15:34, schrieb Hans:
Hi folks,
at boot I get lotsa of messages of this kind:
6.782635] systemd[1]: Job setserial.service/start deleted to break
ordering
cycle starting with basic.target/start
6.782433] systemd[1]: Breaking ordering cycle by deleting job
sockets.target/start
On Sb, 15 mar 14, 15:34:54, Hans wrote:
> Hi folks,
>
> at boot I get lotsa of messages of this kind:
>
> 6.782635] systemd[1]: Job setserial.service/start deleted to break ordering
> cycle starting with basic.target/start
I'm guessing you have some cruft in /etc/init.d/. You could try
d
On Sat 15 Mar 2014 at 18:25:54 +0100, Hans wrote:
> I understand, systemd is still beta, and things will not work as expected
> from
> the beginning on, so I can live with this problem at the moment. When I will
> understand systemd better in the future, maybe I can solve problems on my
> own.
On Sat, Mar 15, 2014 at 05:35:18PM +0100, Ralf Mardorf wrote:
> I could write what ever I want to send to this list, but as soon
> "systemd" is part of the subject, my mails are delayed or won't come
> through the list.
It isn't only you this happens to. *All* messages with systemd in the
subject
Am Samstag, 15. März 2014, 17:22:34 schrieb Ralf Mardorf:
> Take a look at all services, perhaps a service want's to start _after_
> and _before_ another service.
Hmm, I am a liitle bit overstrained. I do not know, how to change the order
of the services. On the other hand, these messages appea
On Sat 15 Mar 2014 at 17:35:18 +0100, Ralf Mardorf wrote:
> I could write what ever I want to send to this list, but as soon
> "systemd" is part of the subject, my mails are delayed or won't come
> through the list.
The first is by design, The second is your problem and between you and
your ISP.
orf
To: debian-user@lists.debian.org
Subject: Re: systemd - boot messages
Date: Sat, 15 Mar 2014 17:22:34 +0100
Mailer: Evolution 3.10.4
Take a look at all services, perhaps a service want's to start _after_
and _before_ another service.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debi
Take a look at all services, perhaps a service want's to start _after_
and _before_ another service.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1394900554.3587.1
Hi folks,
at boot I get lotsa of messages of this kind:
6.782635] systemd[1]: Job setserial.service/start deleted to break ordering
cycle starting with basic.target/start
6.782433] systemd[1]: Breaking ordering cycle by deleting job
sockets.target/start
[6.782438] systemd[1]: Job sock
Hello Camaleón,
Excerpt from Camaleón:
> On Sun, 15 Apr 2012 18:48:21 +0200, Thilo Six wrote:
-- --
> the "--noclear" parameter so I think it has to be placed in "/etc/
> inittab" file:
>
> 1:2345:respawn:/sbin/getty --noclear 38400 tty1
Excellent. Thats it. Apparently i did look into '/etc/i
On 04/15/2012 12:48 PM, Thilo Six wrote:
Hello
since the upgrade to wheezy i have a problem with the messages that are shown
during boot. Currently during boot messages are shown as usual on vt1 but then
at some point late in the boot process these messages are cleared and then only
the login
On Sun, 15 Apr 2012 18:48:21 +0200, Thilo Six wrote:
> since the upgrade to wheezy i have a problem with the messages that are
> shown during boot. Currently during boot messages are shown as usual on
> vt1 but then at some point late in the boot process these messages are
> cleared a
Hello
since the upgrade to wheezy i have a problem with the messages that are shown
during boot. Currently during boot messages are shown as usual on vt1 but then
at some point late in the boot process these messages are cleared and then only
the login prompt is shown on vt1 just like on vt2.
I
On Mon, Jan 17, 2011 at 11:43 AM, Stephen Powell wrote:
> On Mon, 17 Jan 2011 11:02:15 -0500 (EST), frank thyes wrote:
>> On Mon, 2011-01-17 at 10:53 -0500, Stephen Powell wrote:
>>> Hello, list. I am trying to find a way to track boot messages. I know
>>
On Mon, 17 Jan 2011 13:03:27 -0700, Bob Proulx wrote:
> T o n g wrote:
>> Camaleón wrote:
>> > What I can't see is why this logging facility is not enabled by
>> > default. I also think it should be kept in a unique file, instead to
>> > be split in "/ var/log/dmesg" and "/var/log/boot", IMO it wo
T o n g wrote:
> Camaleón wrote:
> > What I can't see is why this logging facility is not enabled by default.
> > I also think it should be kept in a unique file, instead to be split in
> > "/ var/log/dmesg" and "/var/log/boot", IMO it would be easier to read,
> > interpret and debug...
>
> Strong
different from messages displayed on the console by any process. You
could even set /proc/sys/kernel/printk to not display kernel messages on
the console.
> Still, I was hoping for all boot messages in a single file somewhere.
> /var/log/boot starts with
>
>Setting parameters of di
On Mon, 17 Jan 2011 16:34:21 +, Camaleón wrote:
> What I can't see is why this logging facility is not enabled by default.
> I also think it should be kept in a unique file, instead to be split in
> "/ var/log/dmesg" and "/var/log/boot", IMO it would be easier to read,
> interpret and debug...
en Powell wrote:
>>> Hello, list. I am trying to find a way to track boot messages. I know
>>> about
>>> things like
>>>
>>> dmesg|less
>>>
>>> and
>>>
>>> less /var/log/syslog
>>>
>>> bu
On Mon, 17 Jan 2011 11:02:15 -0500 (EST), frank thyes wrote:
> On Mon, 2011-01-17 at 10:53 -0500, Stephen Powell wrote:
>> Hello, list. I am trying to find a way to track boot messages. I know about
>> things like
>>
>>dmesg|less
>>
>> and
>>
On Mon, Jan 17, 2011 at 10:53 AM, Stephen Powell wrote:
>
> Hello, list. I am trying to find a way to track boot messages. I know about
> things like
>
> dmesg|less
>
> and
>
> less /var/log/syslog
>
> but they don't cover everything. For example
On Mon, 17 Jan 2011 10:53:51 -0500, Stephen Powell wrote:
> Hello, list. I am trying to find a way to track boot messages. I know
> about things like
>
>dmesg|less
>
> and
>
>less /var/log/syslog
>
> but they don't cover everything. For example, /
Hello,
Stephen Powell a écrit :
> Hello, list. I am trying to find a way to track boot messages. I know about
> things like
>
>dmesg|less
>
> and
>
>less /var/log/syslog
>
> but they don't cover everything. For example, /etc/init.d/console-setup
On Mon, 2011-01-17 at 10:53 -0500, Stephen Powell wrote:
> Hello, list. I am trying to find a way to track boot messages. I know about
> things like
>
>dmesg|less
>
> and
>
>less /var/log/syslog
>
> but they don't cover everything. For example, /
Hello, list. I am trying to find a way to track boot messages. I know about
things like
dmesg|less
and
less /var/log/syslog
but they don't cover everything. For example, /etc/init.d/console-setup
issues a message during boot that goes something like this:
Setting up console
I use logcheck to report changes in logs which need attention. Most
messages are filtered out so as to leave unusual messages for attention.
Today I got the following 2 messages:
Feb 18 09:48:55 compaq kernel: hda: hda1 < hda5 hda6ACPI: PCI Interrupt
Link [LNKB] enabled at IRQ 5
Feb 18 09:4
On Thu, Dec 13, 2007 at 10:39:39AM -0500, Marc Auslander wrote:
> Is there a boot option to have the terminal pause at each page of
> messages. For early boot problems, I can't see the messages that lead
> to the panic, because they scroll off the screen.
Best bet is to set up a serial console an
Is there a boot option to have the terminal pause at each page of
messages. For early boot problems, I can't see the messages that lead
to the panic, because they scroll off the screen.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTE
OK, here goes. I would really like to be able to modify my bootup
messages to have some color, similar to what a Knoppix boot does. Maybe
not as garish, something to my taste.
I've looked at bootsplashes, but they tend to be bulky and usually ugly
in execution. The bootsplash package requires a
El Diumenge 17 Setembre 2006 09:06, Ron Johnson va escriure:
> Edit /etc/default/bootlogd so that "BOOTLOGD_ENABLE=Yes". Next time
> you reboot, such messages should be in /var/log/boot.
Thanks!
Finally I can see boot errors :)
-
Mon Sep 18 16:52:28 2006: Configuring network interfaces.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/17/06 00:04, Benjamí Villoslada wrote:
> How I can read the boot messages? With /var/log grep and zgrep I
> can't locate some error messages that appears when the system
> starts. I.e. today have read some about /etc/ntp...
How I can read the boot messages? With /var/log grep and zgrep I can't locate
some error messages that appears when the system starts. I.e. today have read
some about /etc/ntp... ? and ntpdate doesn't sync the system clock.
--
Benjamí
http://blog.bitassa.cat
.
On Sun, Aug 14, 2005 at 10:24:01PM -0700, Wu-Kung Sun wrote:
>On 8/14/05, Ed Young <[EMAIL PROTECTED]> wrote:
>> Type "dmesg" at the command line.
>>
>
>Well there are several boot messages that don't appear in dmesg. Is
>there a way to make dmes
> For Debian >3.1, check the file "/etc/default/bootlogd" and set the
> variable in it:
> BOOTLOGD_ENABLE=Yes
>
> After booting, the file "/var/log/boot" is available. It might contain what
> you are looking for..
>
> Apart from that, messages from pppd can be found in "/var/log/syslog" (for
> me
Hi Lubos,
>> how can I read the boot messages? I've had some big problems today
>> information. Any help?
For Debian >3.1, check the file "/etc/default/bootlogd" and set the
variable in it:
BOOTLOGD_ENABLE=Yes
After booting, the file "/var/log/boot" is
Lubos Vrbka wrote:
>> how can I read the boot messages? I've had some big problems today
>> which I'll use other emails for but now when I reboot, suddenly
>> ifconfig reports a ppp0 and ppp1. Before I only had a ppp0. I got
>> some sort of ppp error with ins
how can I read the boot messages? I've had some big problems today
which I'll use other emails for but now when I reboot, suddenly
ifconfig reports a ppp0 and ppp1. Before I only had a ppp0. I got
some sort of ppp error with instructions but I can't read it fast
enough.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wu-Kung Sun wrote:
> Hello all,
> how can I read the boot messages? I've had some big problems today
> which I'll use other emails for but now when I reboot, suddenly
> ifconfig reports a ppp0 and ppp1. Before I only had a pp
Wu-Kung Sun wrote:
On 8/14/05, Ed Young <[EMAIL PROTECTED]> wrote:
Type "dmesg" at the command line.
Well there are several boot messages that don't appear in dmesg. Is
there a way to make dmesg exactly the same? Also dmesh quickly fills
with what I guess
On 8/14/05, Ed Young <[EMAIL PROTECTED]> wrote:
> Type "dmesg" at the command line.
>
Well there are several boot messages that don't appear in dmesg. Is
there a way to make dmesg exactly the same? Also dmesh quickly fills
with what I guess are iptables messages (I&
Type "dmesg" at the command line.
Cheers, Ed
-Original Message-
From: Wu-Kung Sun [mailto:[EMAIL PROTECTED]
Sent: Sunday, August 14, 2005 9:44 PM
To: Debian-users
Subject: reading boot messages
Hello all,
how can I read the boot messages? I've had some big problems t
Hello all,
how can I read the boot messages? I've had some big problems today
which I'll use other emails for but now when I reboot, suddenly
ifconfig reports a ppp0 and ppp1. Before I only had a ppp0. I got
some sort of ppp error with instructions but I can't read it fast
enoug
On Fri, 2004-11-26 at 21:42 +0100, Bram Mertens wrote:
> On Sun, 2004-11-21 at 11:53, Miquel van Smoorenburg wrote:
> > In article <[EMAIL PROTECTED]>,
> > Bram Mertens <[EMAIL PROTECTED]> wrote:
[snip]
> with non-i386 you probably refer to AMD etc.? This laptop is an i686
> and I had no problem
On Sun, 2004-11-21 at 11:53, Miquel van Smoorenburg wrote:
> In article <[EMAIL PROTECTED]>,
> Bram Mertens <[EMAIL PROTECTED]> wrote:
> >On my desktop (running SuSE 8.2) the messages printed to tty1 when the
> >machine is booting are stored in /var/log/boot.msg. On my laptop I
> >can't find any
On Sun, Nov 21, 2004 at 11:15:53AM +0100, Bram Mertens wrote:
> On my desktop (running SuSE 8.2) the messages printed to tty1 when the
> machine is booting are stored in /var/log/boot.msg. On my laptop I
> can't find any file in /var/log/ that contains these messages.
/var/log/boot seems the plac
In article <[EMAIL PROTECTED]>,
Bram Mertens <[EMAIL PROTECTED]> wrote:
>On my desktop (running SuSE 8.2) the messages printed to tty1 when the
>machine is booting are stored in /var/log/boot.msg. On my laptop I
>can't find any file in /var/log/ that contains these messages.
Suse uses bootlogd f
Hello
Bram Mertens (<[EMAIL PROTECTED]>) wrote:
> On my desktop (running SuSE 8.2) the messages printed to tty1 when the
> machine is booting are stored in /var/log/boot.msg. On my laptop I
> can't find any file in /var/log/ that contains these messages.
Debian Sarge and Sid also have a boot lo
Bram Mertens wrote (21-11-2004 11:15):
Hi
On my desktop (running SuSE 8.2) the messages printed to tty1 when the
machine is booting are stored in /var/log/boot.msg. On my laptop I
can't find any file in /var/log/ that contains these messages.
Are they logged somewhere else? If so where and how sh
Hi
On my desktop (running SuSE 8.2) the messages printed to tty1 when the
machine is booting are stored in /var/log/boot.msg. On my laptop I
can't find any file in /var/log/ that contains these messages.
Are they logged somewhere else? If so where and how should I have been
able to find them?
Hi, I don't get a start up log while debian is booting
> and I don't understand that. Does someone know what, if any, line in
my menu ist (posted below) would cause the start up log to be blanked?
In other words I don't see anything no boot messages.The first thing I
see after selecting debian in
ickly to
> > read that I wanted to take another look at. I think they just have
> > something to do with my CD-ROM drives (possibly because there's no
> > discs in them).
> >
> > How can I log *all* of the kernel's boot messages ?? "dmesg" doesn'
On Sat, Jan 13, 2001 at 10:18:59AM -0500, Hall Stevenson wrote:
>
> Casey, thanks for the reply. I've only recently switched to Debian and I
> don't recall either RedHat or Mandrake logging all of this info (or more
> likely, I never checked for it). Nonetheless, the error I'm looking for
> didn't
raded my kernel to 2.4.0 with no apparent problems... I did
> > notice on bootup some messages that scroll by far too quickly to read that
> > I wanted to take another look at. I think they just have something to do
> > with my CD-ROM drives (possibly because there's no discs
notice
> on bootup some messages that scroll by far too quickly to read that I wanted
> to take another look at. I think they just have something to do with my
> CD-ROM drives (possibly because there's no discs in them).
>
> How can I log *all* of the kernel's boot m
w can I log *all* of the kernel's boot messages ?? "dmesg" doesn't show
everything.
Thanks in advance
Hall
Kelly Corbin <[EMAIL PROTECTED]> wrote:
>Is there a way to view/log boot messages besides those generated by the
>kernel i.e. besides dmesg? I believe my modules are not loading
>correctly at boot. Thanks
Use Ctrl-S to pause the output and scroll up and down with Shift-PageUp
and
> Quoting Kelly Corbin ([EMAIL PROTECTED]):
> > Is there a way to view/log boot messages besides those generated by the
> > kernel i.e. besides dmesg? I believe my modules are not loading
> > correctly at boot. Thanks
>
> Shift-PageUp (and PageDown)
>
but note
Quoting Kelly Corbin ([EMAIL PROTECTED]):
> Is there a way to view/log boot messages besides those generated by the
> kernel i.e. besides dmesg? I believe my modules are not loading
> correctly at boot. Thanks
Shift-PageUp (and PageDown)
Cheers,
--
Email: [EMAIL PROTECTED] Tel:
> Is there a way to view/log boot messages besides those generated by the
> kernel i.e. besides dmesg? I believe my modules are not loading
> correctly at boot. Thanks
>
look at /var/log/kern.log - at least on potato module output it there.
--
Hi! I'm a .signature virus!
Is there a way to view/log boot messages besides those generated by the
kernel i.e. besides dmesg? I believe my modules are not loading
correctly at boot. Thanks
Kelly Corbin
[EMAIL PROTECTED]
recently after updating my potato system I started getting the
following messages right after the root filesystem is checked:
IRQ 0 in use
IRQ 1 in use
IRQ 2 in use
IRQ 8 in use
IRQ 13 in use
IRQ 14 in use
IRQ 15 in use
it does not seem to hurt anything but it annoys me :) i have not
figured
/var/log/messages
-gnana
> The original question was about suppressing verbose messages at boot.
My question: I want to know what the computer said at boot time.
Something like dmesg. dmesg isn't useful anymore after a few months
uptime, because it only contains new information which has pused the old
boot mess
Sorry, I deleted the original message before I realized that I might
have an answer.
The original question was about suppressing verbose messages at boot.
In the file: /etc/defaults/rcS
# Set VERBOSE to "no" if you would like a more quiet bootup.
VERBOSE=yes
Hope this helps.
--
Subject: boot messages too fast to read.
Date: Thu, Aug 19, 1999 at 06:14:02PM +1000
In reply to:Alexander Jankowsky
Quoting Alexander Jankowsky([EMAIL PROTECTED]):
>
>
> How do you look at all the start up information that scrolls past
> too quickly to read when
In article <[EMAIL PROTECTED]>,
Hwei Sheng TEOH <[EMAIL PROTECTED]> wrote:
>It seems that certain messages are not recorded by dmesg: such as isapnp
>messages. (I've never been able to see the board ID and "activated OK" message
>in dmesg -- only on the console.) Anybody can explain why??
Yes. Th
On Tue, Aug 24, 1999 at 12:40:19AM -0400, Hwei Sheng TEOH wrote:
> It seems that certain messages are not recorded by dmesg: such as isapnp
> messages. (I've never been able to see the board ID and "activated OK" message
> in dmesg -- only on the console.) Anybody can explain why?? I'd like to hav
On Tue, 24 Aug 1999, Mark Wagnon wrote:
> On Mon 08/23/99 11:31PM, David Teague wrote:
>
> > After boot, dmesg will give a good bit of the boot messages, but
> > sometimes it fails to give parts of the boot message that I want :(
>
> I have this problem, and it driv
On Mon 08/23/99 11:31PM, David Teague wrote:
> After boot, dmesg will give a good bit of the boot messages, but
> sometimes it fails to give parts of the boot message that I want :(
I have this problem, and it drives me crazy. Sometimes I want to cut
and paste the info into my pleas fo
r.
Wait until the login message. Then scroll back with shift-PgUp
back to the start of boot.
This loses the beginnning of the boot messages if there is more to
display than the scroll back (ring?) buffer can handle. In that
event, stop the scrolling with Control-S in the middle and use
shift-PgUp/
You shouldn't need to do anything special to enable this, but if you switch
virtual consoles the buffer that Shift-PGUP/PGDN scrolls through is reset.
Pat
On Thu, Aug 19, 1999 at 01:16:48AM -0700, Steve Lamb wrote:
> Thursday, August 19, 1999, 1:14:02 AM, Alexander wrote:
> > How do you look at all the start up information that scrolls past
> > too quickly to read when the computer is first booted.
>
> dmesg from the command prompt.
>
> Shi
Alexander Jankowsky <[EMAIL PROTECTED]> wrote:
>How do you look at all the start up information that scrolls past
>too quickly to read when the computer is first booted.
>
>
Use Shift + pgup/pgdown before you logon to see the messages.
Henning Olsen
___
Alexander Jankowsky wrote on Thursday, August 19, 1999 10:14 AM:
-- snip --
> How do you look at all the start up information that scrolls past
> too quickly to read when the computer is first booted.
-- snip --
Try SHIFT a
Thursday, August 19, 1999, 1:14:02 AM, Alexander wrote:
> How do you look at all the start up information that scrolls past
> too quickly to read when the computer is first booted.
dmesg from the command prompt.
Shift-PGUP/PGDN for console scrolling.
--
Steve C. Lamb |
How do you look at all the start up information that scrolls past
too quickly to read when the computer is first booted.
Please send your reply to the senders
email address, otherwise I'll miss it.
___
DO YOU YAHOO!?
Get your fr
Hi tony,
you wrote on: 24 Jan 99 at 22:05 (received 25.01.99)
about : _boot messages/logging_
>I'm at a loss to find the way to get all the
>boot messages logged to a file. Is there a
>recommended procedure or configuration file
>change that I can make?
Afte
Hi Tony,
> I'm at a loss to find the way to get all the
> boot messages logged to a file. Is there a
> recommended procedure or configuration file
> change that I can make?
dmesg displays boot messages. It is usually run at system startup and
it's output redirected to
I'm at a loss to find the way to get all the
boot messages logged to a file. Is there a
recommended procedure or configuration file
change that I can make?
thanks,
--
tony mollica
[EMAIL PROTECTED]
On Fri, Sep 18, 1998 at 12:20:27PM -0700, Ian Eure wrote:
> >
> In some cases, with older drive types and/or systems, you can cheat a bit
> by enabling the system ROM shadow option in your CMOS. I really doubt
> that this would work on a PS/2, but my older AMD 386DX/40 (a truly super
> system) wit
1 - 100 of 122 matches
Mail list logo
