<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
</head>
<body bgcolor="#FFFFFF" text="#000000">
morning ben :)<br>
<br>
hardware, evil-MS-Hardware .. naa, MS-Hardware mus stay also like
all others HW-Manufacturer on Standards and this be ISO-Standards
around of the world.. and this be in direction
IBM-compatble-Standards around the world. And MS have do this like
all other factory, maby can add MS some extra's for Windows like
Mediaplayer, office and Browser-key's (what can use the
Linuxcommunity also(like the Win-key)) but, they can not change the
Hardware fully for crashing others systems, this can you shoot out
from your brain Buddy *v-b-grin*<br>
So, it's just not an MS-Hardware-Fail, it's an software fail, there
therefor mus you the whole jornal-s garbage rummage through like by
a bigh Factory or Fasility for passwords .. But in your own /var,
therewor was the old syslog very nice, for all and everything clean
log-files ,there was really easy for finding the whole bugs..<br>
and where was the last crash and by what .. but since the systemctrl
exist.. yes, i know start i shoot again again the whole systemd, but
the initrd was really not bad .. was more easy .. how ever.. it can
not be the hardware..<br>
except if she were broken, so the hardware ..<br>
<br>
best regards<br>
Blacky<br>
<br>
<div class="moz-cite-prefix">Am 22.01.2016 um 21:50 schrieb Ben
Bullard:<br>
</div>
<blockquote class=" cite" id="mid_56A2961D_5050100_cox_net"
cite="mid:56A2961D.5050100@cox.net" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<font face="Bitstream Vera Sans">Results: Left computer on over
night. This morning after I woke it up I had the gray screen and
unresponsive computer (no kbd/mouse). So I believe this
indicates that it may not be M$ device that is crashing
computer. I've been wondering about this because why does system
work with M$ device for a period of hours and then crash?<br>
<br>
Some more important details: After these crashes system will
reboot and boots to sddm login screen with progress bar then to
my plasma5 desktop. All looks normal except mouse cursor in
middle of screen which of course won't move. Also I enable login
sound and after crash when rebooting I hear the login sound.<br>
<br>
So X works and sound works. All I know of that aren't working
are still kbd and mouse. This experiment just suggests that
crash happens with either wired cheap OMN devices or M$ wireless
device.<br>
<br>
Also to clear up a possible miscommunication on my part last
night. I don't ever leave the Live .iso running long enough to
know if that would/wouldn't crash. All I know is that on
hardware after install on SSD system works for a period of hours
and then at some point crashes. Crash has happened both while I
was using computer and while I was away. It is consistent. I've
documented now 8 installs in a row, the last one with different
kbd/mouse, the crash eventually happens.<br>
<br>
I'll provide any logs needed to resolve this just tell me what
is needed.<br>
</font>
<pre class="moz-signature" cols="72">Ben Bullard
ben79
--------------------
OpenMandriva-QA Team
</pre>
<div class="moz-cite-prefix">On 01/21/2016 04:08 PM, Ben Bullard
wrote:<br>
</div>
<blockquote class=" cite" id="mid_56A156E9_3_cox_net"
cite="mid:56A156E9.3@cox.net" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<font face="Bitstream Vera Sans">I've been working with Colin
(itchka_) and Bernhard (bero) on IRC on this issue. This is
an update. I'm in a period of time where I have to be mostly
away from computer so thought this best time for this
experiment. There help has been much appreciated.<br>
<br>
</font><font face="Bitstream Vera Sans">Experiment is:<b>
Install of OM Lx 3, System updated, and with wired kbd and
mouse</b> <u><b>only</b></u> <b>no M$ hardware attached</b>.</font><br>
<font face="Bitstream Vera Sans"><br>
If it does or does not crash that will tell us something. What
has happened with 7 previous installs w/M$ wireless kbd/mouse
is it works for about 2-4 hours and at some point blanks to a
gray screen and is completely unresponsive thereafter.<br>
<br>
But M$ kbd/mouse do work in live .iso and for a period of time
(2-4 hours) after install.<br>
Purpose of experiment is to see if M$ kbd/mouse is or isn't
cause of crash.<br>
<br>
Will stay logged in IRC@#open-mandriva (unless system
crashes) but will be in and out. Mostly out.<br>
<br>
System has been installed for a little over 2 and 1/2 hours so
far so we shall see what we shall see. Just for fun will
attach latest, from this install, output of journalctl -mxe.<br>
<br>
Also the broken system we were working on last night is still
available for debugging. Should have more time tomorrow. <br>
<br>
FWIW: This wired kbd is an elcheapo and it kinda sucks...<span
class="moz-smiley-s2"><span> :-( </span></span><br>
</font>
<pre class="moz-signature" cols="72">--
Ben Bullard
ben79
--------------------
OpenMandriva-QA Team
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OM-Cooker mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OM-Cooker@ml.openmandriva.org">OM-Cooker@ml.openmandriva.org</a>
<a class="moz-txt-link-freetext" href="http://ml.openmandriva.org/mailman/listinfo/om-cooker_ml.openmandriva.org">http://ml.openmandriva.org/mailman/listinfo/om-cooker_ml.openmandriva.org</a>
</pre>
</blockquote>
<br>
<br>
</body>
</html>