On Wed, Aug 07, 2019 at 11:23:57PM +1000, terryc wrote:
> Fixed and now I'm back to chasing down HW/memory fault.
> A side benefit is that now I have a consistent way of crashing the
> system and might finally get to a working solution for this pair of
> identical AMD B350 systems.
Sounds like
On Wed, 7 Aug 2019 17:13:50 +1000
"Ralph Ronnquist \(rrq\) via Dng" wrote:
...snip..
>
> Maybe there's a spurious back-quote in /etc/default/grub ?
Bingo. Thanks all who replied.
The successive posts jogged my brain to look again and the May-2019
date reminded me that I had actually
terryc wrote on 7/8/19 8:20 pm:
> On Wed, 7 Aug 2019 17:13:50 +1000
> "Ralph Ronnquist \(rrq\) via Dng" wrote:
>
>> terryc wrote on 7/8/19 4:39 pm:
>>> In the midst of removing a package that frequently crashes* and
>>> attempting a general package update/upgrade, somehow the package
>>> upgrade
On Wed, 7 Aug 2019 17:13:50 +1000
"Ralph Ronnquist \(rrq\) via Dng" wrote:
> terryc wrote on 7/8/19 4:39 pm:
> > In the midst of removing a package that frequently crashes* and
> > attempting a general package update/upgrade, somehow the package
> > upgrade system has borked something.
> >
> >
terryc wrote on 7/8/19 4:39 pm:
> In the midst of removing a package that frequently crashes* and
> attempting a general package update/upgrade, somehow the package
> upgrade system has borked something.
>
> Specifically it seems to have come about following a
> sudo apt autoremove where a
In the midst of removing a package that frequently crashes* and
attempting a general package update/upgrade, somehow the package
upgrade system has borked something.
Specifically it seems to have come about following a
sudo apt autoremove where a depreciated image was listed to go.
Now I am at
