| 1 |
On Tuesday, 9 February 2021 10:01:04 GMT n952162 wrote: |
| 2 |
> On 2/9/21 10:05 AM, Dale wrote: |
| 3 |
> > n952162 wrote: |
| 4 |
> >> Are extra administrative steps necessary when --sync brings in a new |
| 5 |
> >> |
| 6 |
> >> kernel, as in: |
| 7 |
> >> https://wiki.gentoo.org/wiki/Kernel/Upgrade |
| 8 |
> >> |
| 9 |
> >> I currently have this situation: |
| 10 |
> >> |
| 11 |
> >> $ uname -a |
| 12 |
> >> Linux host *4.19.72-gentoo* #7 SMP Tue Jun 9 19:51:52 CEST 2020 x86_64 |
| 13 |
> >> GNU/Linux |
| 14 |
> >> |
| 15 |
> >> $ eselect kernel list |
| 16 |
> >> |
| 17 |
> >> Available kernel symlink targets: |
| 18 |
> >> [1] linux-5.4.72-gentoo |
| 19 |
> >> [2] linux-5.4.80-gentoo-r1 |
| 20 |
> >> [3] linux-5.4.92-gentoo |
| 21 |
> >> |
| 22 |
> >> If an update requires additional steps, shouldn't that have appeared |
| 23 |
> >> in the news? |
| 24 |
> > |
| 25 |
> > It depends I think. I say think because there may be a binary kernel |
| 26 |
> > available which will upgrade itself. I seem to recall reading about it |
| 27 |
> > on a mailing list somewhere. I have no experience with it tho. That |
| 28 |
> > said, if you use the old method, you have to upgrade the kernel |
| 29 |
> > yourself. There are scripts you can use to help automate it a good bit |
| 30 |
> > but some of us still do it the manual way. When you do updates, emerge |
| 31 |
> > will pull in the new sources but the rest is up to you. I suspect most |
| 32 |
> > that do it the old way, copy .config over to the new kernel directory, |
| 33 |
> > run make oldconfig and answer the questions, compile the new kernel, |
| 34 |
> > copy it to /boot using the right method which there is a few of and then |
| 35 |
> > configure your bootloader if needed. The link you posted explains this |
| 36 |
> > in more detail, and may be more complete too. |
| 37 |
> > |
| 38 |
> > I'm trying to remember what that binary kernel thing is called. I just |
| 39 |
> > skimmed the messages so it could be something else or not even in the |
| 40 |
> > tree yet. |
| 41 |
> > |
| 42 |
> > Dale |
| 43 |
> > |
| 44 |
> > :-) :-) |
| 45 |
> |
| 46 |
> Ah, maybe I have a theory what's going on ... maybe there's no news that |
| 47 |
> it's time to upgrade the kernel, because it's not meant that the kernel |
| 48 |
> necessarily needs to be upgraded ... except that it seems that the |
| 49 |
> virtualbox-modules package might have a (unfortunate) dependency on that... |
| 50 |
|
| 51 |
I'm not sure I understand completely why there should be a news item from |
| 52 |
portage whenever new kernel sources are updated and downloaded. It is up the |
| 53 |
system administrator to configure and build the new sources if desired. |
| 54 |
|
| 55 |
Each time you upgrade your kernel on the host, external modules will require |
| 56 |
updating/rebuilding. The set '@module-rebuild' does that instead of having to |
| 57 |
re-emerge manually each external module. |
| 58 |
|
| 59 |
You seem to be running an old kernel. VBox and its modules changed recently |
| 60 |
so these will need to be updated - there may be a conflict with older host |
| 61 |
kernels and as you report you've come across it. |
| 62 |
|
| 63 |
The eselect list you showed does not have a selected kernel source. What is |
| 64 |
linked to /usr/src/linux on your system? |
| 65 |
|
| 66 |
$ ls -l /usr/src/ |
| 67 |
|
| 68 |
Upgrading your kernel and any external modules (inc. VBox's) should fix |
| 69 |
whatever is currently giving you trouble. |
Archives