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
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 "
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 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'
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
5 matches
Mail list logo
