On Fri, Nov 5, 2021 at 4:25 PM The Wanderer wrote:
> On 2021-11-05 at 18:14, Mark Copper wrote:
>
> > Where to start diagnosing a problem like this?
>
> At first blush: look into ways to disable kernel modesetting.
>
> The details tend to vary depending on the GPU involved, but one thing
> they u
On Fri, Nov 5, 2021 at 5:18 PM The Wanderer wrote:
>
> (Is there a reason why the line after the quote and before your new
> text, in both cases where that happened, consisted of a string of 11 tab
> characters instead of being empty? I had to delete the tabs manually in
> order to avoid having it
(Is there a reason why the line after the quote and before your new
text, in both cases where that happened, consisted of a string of 11 tab
characters instead of being empty? I had to delete the tabs manually in
order to avoid having it mess up quoting in this reply.)
On 2021-11-05 at 19:03, Feli
The Wanderer composed on 2021-11-05 18:25 (UTC-0400):
> There's a specific kernel-command-line parameter (on top of 'nomodeset')
> for disabling KMS with certain types of Intel integrated GPU; I don't
> remember it off the top of my head, but I believe it involves the string
> 'i915'.
On 2021-11-05 at 18:14, Mark Copper wrote:
> Where to start diagnosing a problem like this?
At first blush: look into ways to disable kernel modesetting.
The details tend to vary depending on the GPU involved, but one thing
they usually have in common is adding 'nomodeset' to the kernel command
Where to start diagnosing a problem like this?
Minimal install -- no desktop.
No "oops" in syslog though there are some warnings.
System seems to shut down properly when power button pressed.
Yesterday I could even ssh in, but that facility disappeared.
Asrock H570M-ITX/ac with Intel i3-10100.
6 matches
Mail list logo
