From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: boot up messages
Date: Wed, 14 Jun 2017 12:56:44 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1.1706141255040.4537@southernprince> (raw)
In-Reply-To: <20170614124248.5c23b4a7@bigbox.christie.dr>
Mark peveto here,
Hey Tim,
Is there another set of boot up messages I could be missing? These don't quite souhnd lime what doubletalk is reading when it comes up. What reads is
followed by a lot of "ok, done" type stuff, and I don't see that here.
Mark Peveto
Registered Linux user number 600552
Everything happens after coffee!
On Wed, 14 Jun 2017, Linux for blind general discussion wrote:
> Tim here. You should be able to use the `dmesg` utility to dump the
> startup messages, piping through `less` or dumping them into a
> text-file for your perusal in your favorite text-editor:
>
> $ dmesg | less
>
> or
>
> $ dmesg > startup_messages.txt
>
> -tim
>
>
> On June 14, 2017, Linux for blind general discussion wrote:
> > Mark Peveto here.
> > Where in debian do I find a record of the boot messages? It seems
> > when I have my doubletalk connected, it fails to load some sort of
> > module right away, but doubletalk is talking too fast for me to
> > make it out. Thanks.
> >
> >
> > Mark Peveto
> > Registered Linux user number 600552
> > Everything happens after coffee!
> >
> > _______________________________________________
> > Blinux-list mailing list
> > Blinux-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/blinux-list
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion [this message]
` Linux for blind general discussion
` Linux for blind general discussion
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.1.1706141255040.4537@southernprince \
--to=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).