From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel 4.14.7 no longer switches to VT7
Date: Sun, 31 Dec 2017 00:42:23 +0000 [thread overview]
Message-ID: <1929480.VEiyYHLp7T@peak> (raw)
In-Reply-To: <2024427.CpBGOPiNpi@peak>
On Sunday, 31 December 2017 00:33:34 GMT Peter Humphrey wrote:
> On Saturday, 30 December 2017 00:18:12 GMT Alan McKinnon wrote:
> > If you want to fix the bugs, then by all means soldier on. But if your
> > intent is to have a working system that boots, probably drop using
> > 4.14.x and go back to say 4.12.x ?
>
> But the whole 4.12 branch has been masked, so that won't do. Here, I've
> had to go back to 4.9.49-r1 (amd64, not ~amd64). But now I see 4.9.72 has
> been stabilised.
Oops! That's on an x86 box. On this amd64 box the latest version is still
4.9.49-r1.
> I think I'll wait for some stabiliity in the kernel
> version offerings before I make another move. Three kernel compilations
> on six systems within a week are a few too many.
--
Regards,
Peter.
next prev parent reply other threads:[~2017-12-31 0:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 15:41 [gentoo-user] Kernel 4.14.7 no longer switches to VT7 Jörg Schaible
2017-12-24 6:59 ` Raymond Jennings
2017-12-25 10:07 ` [gentoo-user] " Jörg Schaible
2017-12-25 17:27 ` Mick
2017-12-28 21:39 ` Raymond Jennings
2017-12-29 23:48 ` Kai Krakow
2018-01-01 14:20 ` Jörg Schaible
2017-12-30 0:18 ` [gentoo-user] " Alan McKinnon
2017-12-30 22:16 ` Frank Steinmetzger
2017-12-30 22:26 ` Michael Orlitzky
2017-12-30 23:56 ` [gentoo-user] " Ian Zimmerman
2017-12-31 0:33 ` [gentoo-user] " Peter Humphrey
2017-12-31 0:42 ` Peter Humphrey [this message]
2017-12-31 1:13 ` [gentoo-user] " Ian Zimmerman
2017-12-31 1:56 ` Peter Humphrey
2017-12-31 8:16 ` Bill Kenworthy
2017-12-31 18:46 ` Ian Zimmerman
2018-01-01 9:00 ` Peter Humphrey
2018-01-01 14:27 ` Jörg Schaible
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=1929480.VEiyYHLp7T@peak \
--to=peter@prh.myzen.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/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