From: R0b0t1 <r030t1@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] virtualbox: no x-server after kernel upgrade to 4.12.12-gentoo
Date: Sat, 16 Sep 2017 00:02:06 -0500 [thread overview]
Message-ID: <CAAD4mYijC_WsnMtx_MLqQsexT-UqeTaS6r5Pn0zi3NazQUXk0Q@mail.gmail.com> (raw)
In-Reply-To: <2288639.imYotmn4d9@thetick>
On Fri, Sep 15, 2017 at 3:36 PM, Marc Joliet <marcec@gmx.de> wrote:
> Am Freitag, 15. September 2017, 17:43:52 CEST schrieb R0b0t1:
>> Details on this are sparse but you need to run @x11-modules-rebuild
>> after a kernel upgrade.
>
> Since when has that been the case? AIUI X11 modules live 100% in userspace,
> the kernel component is its own thing (unless you use nvidia, I suppose).
> @x11-modules-rebuild is for xorg-server upgrades, and even then, strictly
> speaking only when there is an ABI change (see the first of your links).
>
> But even so, the way Xorg stabilisations are handled in Gentoo (i.e.,
> everything is stabilised simultaneously) you shouldn't really need it in the
> first place; at least, I can't remember the last time I needed to use it.
>
Starting around a decade ago, I think. When I was originally given
this advice there was no detailed explanation available as to why it
was needed. However, I rebuilt my kernel a few times and was forced to
merge that package to get X11 working again, so causation was
established.
Recently I can verify that I haven't been doing it manually between
kernel upgrades.
R0b0t1
next prev parent reply other threads:[~2017-09-16 5:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 14:47 [gentoo-user] virtualbox: no x-server after kernel upgrade to 4.12.12-gentoo Alexander Puchmayr
2017-09-15 15:43 ` R0b0t1
2017-09-15 16:40 ` Alexander Puchmayr
2017-09-15 20:36 ` Marc Joliet
2017-09-16 5:02 ` R0b0t1 [this message]
2017-09-15 17:35 ` Alexander Kapshuk
2017-09-16 6:58 ` [gentoo-user] virtualbox: no x-server after kernel upgrade to 4.12.12-gentoo [SOLVED] Alexander Puchmayr
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=CAAD4mYijC_WsnMtx_MLqQsexT-UqeTaS6r5Pn0zi3NazQUXk0Q@mail.gmail.com \
--to=r030t1@gmail.com \
--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