It’s very possible the kernel upgrade used some feature of the chipset that
was buggy and resolved in a later release.
On Wed, 18 May 2022 at 14:58, Ken Smith via GLLUG
wrote:
>
> Chris Bell wrote:
> > On Sunday, 15 May 2022 17:32:50 BST you wrote:
> >> Chris Bell via GLLUG wrote:
> >>> On
Chris Bell wrote:
On Sunday, 15 May 2022 17:32:50 BST you wrote:
Chris Bell via GLLUG wrote:
On Sunday, 15 May 2022 13:37:10 BST Ken Smith via GLLUG wrote:
Any pearls of wisdom either about my question or about recovering a
miscreant ML350 motherboard that won't boot anything or go into the
Chris Bell via GLLUG wrote:
On Sunday, 15 May 2022 13:37:10 BST Ken Smith via GLLUG wrote:
Any pearls of wisdom either about my question or about recovering a
miscreant ML350 motherboard that won't boot anything or go into the
setup pages.
Thanks
Ken
Hello Ken,
I had a very lightly loaded
On Sunday, 15 May 2022 13:37:10 BST Ken Smith via GLLUG wrote:
> Hi All, This might seem a bit of an off the wall question. Would running
> the 5.4 Kernel stress a system such that it could cause a motherboard
> failure? I can't think how but.
>
>
> Any pearls of wisdom either about my
Hi All, This might seem a bit of an off the wall question. Would running
the 5.4 Kernel stress a system such that it could cause a motherboard
failure? I can't think how but.
More details — I’m running (or was running) various KVM VM’s as well as
MythTV server on the host machine with
