TL;DR: It does seem that the kernel was holding things back to the
point that things weren't working. :-(
On 6/8/19 12:01 PM, Grant Taylor wrote:
I'm having problems with newly compiled modules (zfs (et al.) and vbox
(et al.)) and kernel after doing two "emerge -DuNe @world"s.
I've managed
On 6/9/19 12:49 PM, Mick wrote:
3. Rebuild libtools, binutils, glibc.
Well, I've had some progress.
I'm now booted and running the kernel I just compiled. (Same config,
same genkernel command.)
I unmasked, downgraded, and selected (binutils-config) binutils to
2.30-r4 before re-running th
On 6/9/19 2:23 PM, Mick wrote:
I think Dale meant a later tree will contain updated packages, which
may fix previous breakages and incompatibilities.
Please clarify which tree: Kernel and / or Portage
Hypothetically, a later VBox version requires some later version libs,
which your current t
On Sunday, 9 June 2019 21:16:52 BST Grant Taylor wrote:
> On 6/9/19 1:38 PM, Dale wrote:
> > While I see that point and quite often it is a good idea, it could
> > also be that a fix is in the newer tree. It could even be that you
> > caught the tree in the middle of some sort of change and you mi
On 6/9/19 1:38 PM, Dale wrote:
While I see that point and quite often it is a good idea, it could
also be that a fix is in the newer tree. It could even be that you
caught the tree in the middle of some sort of change and you missed
part of it.
If it were me, I'd try everything you can but i
Grant Taylor wrote:
> On 6/9/19 12:49 PM, Mick wrote:
>
>> 2. Sync portage and upgrade gcc to the latest stable version. Switch
>> to it.
>
> Portage is within a few days of current.
>
> I do an emerge --sync -q before doing the emerge -DuNeq @world. I've
> not done a --sync since then while worki
On 6/9/19 12:49 PM, Mick wrote:
If you haven't done it already, perhaps have a look in the path
/lib/modules/ 4.9.76-gentoo-r1/misc/ to check the VBox modules are
present and owned by root:root with 0644 access rights.
They are there. I would have expected the error message to be different
i
On Sunday, 9 June 2019 18:55:34 BST Grant Taylor wrote:
> On 6/9/19 2:56 AM, Mick wrote:
> > This sounds as if it may be related to a move from an older gcc to
> > a newer version.
>
> I'm not sure it's related to a gcc version:
>
> # gcc-config -l
> [1] x86_64-pc-linux-gnu-6.4.0 *
> [2] x86_
On 6/9/19 2:56 AM, Mick wrote:
This sounds as if it may be related to a move from an older gcc to
a newer version.
I'm not sure it's related to a gcc version:
# gcc-config -l
[1] x86_64-pc-linux-gnu-6.4.0 *
[2] x86_64-pc-linux-gnu-8.3.0
I think that gcc 8.3 might have been selected and I re
On Saturday, 8 June 2019 20:45:45 BST Grant Taylor wrote:
> On 6/8/19 12:26 PM, Mick wrote:
> > Were these contents not there, or is it that the new version of
> > modules do not work?
>
> The old (original for the sake of this thread) versions (restored from
> backups) work just fine.
>
> The ve
On 6/8/19 1:17 PM, Dale wrote:
I'm not sure I completely understand this one but a thought occurred
to me.
Thoughts are good. That's why I asked.
This may be way off base here so feel free to ignore it if it is.
Did you make sure the kernel symlink is pointing to the right kernel
when you re
On 6/8/19 12:26 PM, Mick wrote:
Were these contents not there, or is it that the new version of
modules do not work?
The old (original for the sake of this thread) versions (restored from
backups) work just fine.
The version produced during the first emerge -DuNe @world worked. At
least I'
Grant Taylor wrote:
> I'm having problems with newly compiled modules (zfs (et al.) and vbox
> (et al.)) and kernel after doing two "emerge -DuNe @world"s.
>
> Everything worked fine after rebooting after the first "emerge -DuNe
> @world". So, I did another "emerge -DuNe @world". (This harks back
On Saturday, 8 June 2019 19:01:30 BST Grant Taylor wrote:
> I'm having problems with newly compiled modules (zfs (et al.) and vbox
> (et al.)) and kernel after doing two "emerge -DuNe @world"s.
>
> Everything worked fine after rebooting after the first "emerge -DuNe
> @world". So, I did another "
I'm having problems with newly compiled modules (zfs (et al.) and vbox
(et al.)) and kernel after doing two "emerge -DuNe @world"s.
Everything worked fine after rebooting after the first "emerge -DuNe
@world". So, I did another "emerge -DuNe @world". (This harks back to
the old stage 1 -> st
15 matches
Mail list logo
