From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id v5EIN4hq018841 for ; Wed, 14 Jun 2017 14:23:08 -0400 Received: by smtp.corp.redhat.com (Postfix) id 1125D8E52F; Wed, 14 Jun 2017 18:23:04 +0000 (UTC) Received: from mx1.redhat.com (ext-mx02.extmail.prod.ext.phx2.redhat.com [10.5.110.26]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 0910F8E532 for ; Wed, 14 Jun 2017 18:23:01 +0000 (UTC) Received: from nov-007-i458.relay.mailchannels.net (nov-007-i458.relay.mailchannels.net [46.232.183.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 7B23180C10 for ; Wed, 14 Jun 2017 18:22:53 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 7B23180C10 Authentication-Results: ext-mx02.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=thechases.com Authentication-Results: ext-mx02.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=blinux.list@thechases.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 7B23180C10 X-Sender-Id: wwwh2|x-authuser|tim@thechases.com Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id A6471207975 for ; Wed, 14 Jun 2017 18:22:49 +0000 (UTC) Received: from uscentral455.accountservergroup.com (unknown [100.96.129.87]) (Authenticated sender: wwwh2) by relay.mailchannels.net (Postfix) with ESMTPA id C4786207E63 for ; Wed, 14 Jun 2017 18:22:46 +0000 (UTC) X-Sender-Id: wwwh2|x-authuser|tim@thechases.com Received: from uscentral455.accountservergroup.com (uscentral455.accountservergroup.com [172.20.120.92]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.9.4); Wed, 14 Jun 2017 18:22:49 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: wwwh2|x-authuser|tim@thechases.com X-MailChannels-Auth-Id: wwwh2 X-Coil-Inform: 3ea0ac2d7d5f822d_1497464567022_1806485174 X-MC-Loop-Signature: 1497464567021:3157607919 X-MC-Ingress-Time: 1497464567021 Received: from 172-0-250-193.lightspeed.rcsntx.sbcglobal.net ([172.0.250.193]:39450 helo=bigbox.christie.dr) by uscentral455.accountservergroup.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from ) id 1dLCwA-002RPI-QC for blinux-list@redhat.com; Wed, 14 Jun 2017 14:22:38 -0400 Date: Wed, 14 Jun 2017 13:22:37 -0500 To: Linux for blind general discussion Subject: Re: boot up messages Message-ID: <20170614132237.5a0eeffe@bigbox.christie.dr> In-Reply-To: References: <20170614124248.5c23b4a7@bigbox.christie.dr> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AuthUser: tim@thechases.com X-Greylist: Sender passed SPF test, Sender IP whitelisted by DNSRBL, ACL 203 matched, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Wed, 14 Jun 2017 18:22:59 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Wed, 14 Jun 2017 18:22:59 +0000 (UTC) for IP:'46.232.183.12' DOMAIN:'nov-007-i458.relay.mailchannels.net' HELO:'nov-007-i458.relay.mailchannels.net' FROM:'blinux.list@thechases.com' RCPT:'' X-RedHat-Spam-Score: -0.309 (BAYES_50, DCC_REPUT_13_19, NO_DNS_FOR_FROM, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2) 46.232.183.12 nov-007-i458.relay.mailchannels.net 46.232.183.12 nov-007-i458.relay.mailchannels.net X-Scanned-By: MIMEDefang 2.78 on 10.5.110.26 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-loop: blinux-list@redhat.com From: Linux for blind general discussion X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk Reply-To: blinux-list@redhat.com List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jun 2017 18:23:08 -0000 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