boot up messages

boot up messages

[Linux for blind general discussion]

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!

Re: boot up messages

[Linux for blind general discussion]

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

Re: boot up messages

[Linux for blind general discussion]

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
>

Re: boot up messages

[Linux for blind general discussion]

Tim replying.  Startup messages should be emitted using specific
kernel-log facilities.  The absence of such messages from your
`dmesg` output suggests one of a couple possible situations:

- the drivers are emitting the text via a facility that doesn't log
  things in the kernel's logs.  Maybe using the standard printf()
  functions instead of the kernel-log-specific printk() function

- the "ok, done" messages could be the doubletalk emitting responses
  to changes in settings sent by the driver.  That is, the driver does
  something like send a "hey, set the volume to 80%" and the
  doubletalk replies speaking "ok, done" without the messages ever
  appearing in the kernel or driver software

There might be other situations, but those are the first ones that
occur to me.  I'm not sure how I'd diagnose them though.  Perhaps the
doubletalk driver has the ability to increase logging levels and send
them to a specified file?

-tim


On June 14, 2017, Linux for blind general discussion wrote:
> 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
> >
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list

Re: boot up messages

[Linux for blind general discussion]

Willem here.
You could try the boot.log in /var/log.
What is actually not working?
Regards, Willem


On Wed, 14 Jun 2017, Linux for blind general discussion wrote:

> Tim replying.  Startup messages should be emitted using specific
> kernel-log facilities.  The absence of such messages from your
> `dmesg` output suggests one of a couple possible situations:
>
> - the drivers are emitting the text via a facility that doesn't log
>  things in the kernel's logs.  Maybe using the standard printf()
>  functions instead of the kernel-log-specific printk() function
>
> - the "ok, done" messages could be the doubletalk emitting responses
>  to changes in settings sent by the driver.  That is, the driver does
>  something like send a "hey, set the volume to 80%" and the
>  doubletalk replies speaking "ok, done" without the messages ever
>  appearing in the kernel or driver software
>
> There might be other situations, but those are the first ones that
> occur to me.  I'm not sure how I'd diagnose them though.  Perhaps the
> doubletalk driver has the ability to increase logging levels and send
> them to a specified file?
>
> -tim
>
>
> On June 14, 2017, Linux for blind general discussion wrote:
>> 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
>>>
>>
>> _______________________________________________
>> 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
>
>

--

This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. 

Please consider the environment before printing this email.