From: Sultan Alsawaf <sultan.alsawaf@canonical.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Problems on linux-image-4.15.0-1047-aws
Date: Fri, 6 Sep 2019 15:05:37 -0700 [thread overview]
Message-ID: <20190906220537.GA7694@sultan-box> (raw)
In-Reply-To: <CAHmME9pRjRgoqoEre4MnK47pU210DQ0bQ3GM3FyJ-ciVFSuT0Q@mail.gmail.com>
> On Fri, Sep 6, 2019 at 3:18 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> > available to the general population
>
> https://wiki.ubuntu.com/Testing/EnableProposed
>
> This might work.
Hi,
In the case of the 4.15 bug, there is a fixed kernel present in the Proposed
release channel which will be available in the normal Updates channel next week.
If needed, the fixed 4.15 kernel can be installed from Proposed now. To do so,
first enable access to Proposed updates by following the instructions in the
quoted link above, then install the desired kernel with the following command:
If you're using the generic kernel, replace FLAVOR with generic, i.e.,
$ sudo apt-get install linux-image-generic/bionic-proposed
Similarly, if you're using the AWS kernel, adjust the command as so:
$ sudo apt-get install linux-image-aws/bionic-proposed
Then disable access to the Proposed channel and reboot. Disabling access to
Proposed is important since it contains untested packages that are not
release-worthy.
Sultan
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-09-06 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 6:54 Johnny Rose Carlsen
2019-09-06 19:15 ` Jason A. Donenfeld
2019-09-06 21:18 ` Jason A. Donenfeld
2019-09-06 21:19 ` Jason A. Donenfeld
2019-09-06 22:05 ` Sultan Alsawaf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190906220537.GA7694@sultan-box \
--to=sultan.alsawaf@canonical.com \
--cc=Jason@zx2c4.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).