On Thu, Apr 02, 2020 at 10:55:16AM -0700, Ross Vandegrift wrote:
> I don't think just saying "yes" automatically is the best approach. But
> I'm not sure we can come up with a clear set of rules. Evaluating the
> use cases will involve judgment calls about size vs functionality. I
> guess I
On Wed, Apr 01, 2020 at 03:15:37PM -0400, Noah Meyerhans wrote:
> Should we simply say "yes" to any request to add functionality to the
> cloud kernel? None of the drivers will add *that* much to the size of
> the image, and if people are asking for them, then they've obviously got
> a use case
Hi!
I'd be happy to work on creating documentation for the Debian cloud kernel,
especially for OpenStack.
I"ve worked with Debian as my primary OS for several years now, and have
also been exploring OpenStack.
I'm also honing my Technical Writer skills through on online course.
Writing this
Hi,
I think the bug can be closed.
I switched the BIOS to UEFI and now kernel 5.4 is able to use the
megaraid_sas controller without any issue.
Regards
--
Robert Sander
Heinlein Support GmbH
Schwedter Str. 8/9b, 10119 Berlin
https://www.heinlein-support.de
Tel: 030 / 405051-43
Fax: 030 /
Hi again,
2 avr. 2020 à 00:30 de l0f...@tuta.io:
> => From now on, it seems I have 2 workarounds: turbo boost deactivation and
> Debian thermald.
> I guess I should do some A/B testing...
>
I've just uninstalled thermald manually built from 01.org, and installed the
official Debian package as
@John try to install Linux Kernel 5.5.13 (aka 5.5.0-1) from sid
https://packages.debian.org/sid/kernel/linux-image-5.5.0-1-amd64-unsigned
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5.12/CHANGES
Chris Wilson (1):
drm/i915/execlists: Track active elements during dequeue
Matt
6 matches
Mail list logo
