[manjaro-dev] [Support] a short report on my own findings on the latest mate image.

[Jude DaShiell]

The script I sent earlier to sonargnulinux.com email list extracted 
fatals; errors, and warnings from dmesg output.  If additional 
categories of material ought to have been extracted I didn't know about 
that or how to find them.  If more categories are needed I'd like to 
know how to locate them.  What I sent earlier was:

dmesg|grep -i "fatal" >dmesg.fat
dmesg|grep -i "error" >dmesg.err
dmesg|grep -i "warning" >dmesg.wrn

Relevant output is in dmesg.fat; dmesg.err, and dmesg.wrn.
I tried using wc-l as a filter to erase zero length files but didn't 
figure how to do that yet.
For those three files, the ones having lines of text in them it would be 
useful to cat those to dmesg.out for reading.

On Sun, 1 Jan 2017, Mark Peveto wrote:

> Date: Sun, 1 Jan 2017 14:16:54
> From: Mark Peveto <southernprince73 at gmail.com>
> To: Jude DaShiell <jdashiel at panix.com>,
>     Sonar Support List <support at sonargnulinux.com>
> Cc: manjaro-dev at manjaro.org
> Subject: Re: [Support] a short report on my own findings on the latest mate
>     image.
> 
> I sent a reply to this message with the dmesg output, but I dunno if it'll 
> make it or not.  That particular message is awaiting approval.
>
>
> Mark Peveto
> Registered Linux user 600552
>
> On 01/01/2017 08:46 AM, Jude DaShiell wrote:
>> what fatals; errors, and warnings are in dmesg output for failing system 
>> once booted?
>> 
>> On Sun, 1 Jan 2017, Mark Peveto via Support wrote:
>> 
>>> Date: Sun, 1 Jan 2017 08:36:59
>>> From: Mark Peveto via Support <support at sonargnulinux.com>
>>> Reply-To: Mark Peveto <southernprince73 at gmail.com>
>>> To: Sonar Support List <support at sonargnulinux.com>
>>> Cc: manjaro-dev at manjaro.org
>>> Subject: [Support] a short report on my own findings on the latest mate 
>>> image.
>>> 
>>> Hi all,
>>> 
>>> I've written the same report to both the manjaro dev list and the sonar 
>>> list.
>>> 
>>> I can confirm Kendell's findings on the mate basic image we've been 
>>> testing. The installer runs, and after the install is complete, all that 
>>> comes up on reboot is a console with no speech.
>>> 
>>> I logged into the console blindly, as it were, with no speech, and had to 
>>> do the following to even access the system remotely with the working 
>>> version of Sonar that I have running on another machine.
>>> 
>>> sudo systemctl enable sshd
>>> 
>>> sudo systemctl start sshd
>>> 
>>> sudo systemctl enable dhcpcd
>>> 
>>> sudo systemctl start dhcpcd
>>> 
>>> Once that was done, I was able to ssh into the test machine with the 
>>> working version of Sonar from back in July, and enable and start lightdm.
>>> 
>>> sudo systemctl enable lightdm
>>> 
>>> sudo systemctl start lightdm
>>> 
>>> Ad Kendell indicated, the mate gui then comes up, but still no orca.  I 
>>> started it with alt f-2 and tping orca.  I've now got a keystroke defined 
>>> to do that once the system boots.  Kendell's right when he said that most 
>>> newer users won't want to go through all that when they install sonar.
>>> 
>>> Anyhow, I do have a talking mate basic image now, even though it took 
>>> jumping through some hoops to get it going.
>>> 
>>> What is needed from this point?  I can probably do some stuff after church 
>>> this morning.
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
>
>

--