| 1 |
On 08/02/21 21:39, n952162 wrote: |
| 2 |
> On 2/8/21 9:17 PM, n952162 wrote: |
| 3 |
>> VBoxClient --clipboard seems to be broken with a recent update |
| 4 |
>> |
| 5 |
>> You can start it without error but it just goes away. The last thing in |
| 6 |
>> the strace is a clone. |
| 7 |
>> |
| 8 |
>> Anybody else seen this problem or know of a fix? |
| 9 |
>> |
| 10 |
>> VBoxClient has behaved like this before, if memory serves. Either I've |
| 11 |
>> just forgotten what the problem was, or something new has popped up. |
| 12 |
>> |
| 13 |
>> |
| 14 |
> |
| 15 |
> I just saw that my virtualbox-modules emerge failed. |
| 16 |
> |
| 17 |
> Probably related to this: |
| 18 |
> |
| 19 |
> $ uname -a |
| 20 |
> Linux txm0 *4.19.72-gentoo* #7 SMP Tue Jun 9 19:51:52 CEST 2020 x86_64 |
| 21 |
> GNU/Linux |
| 22 |
> |
| 23 |
> $ lt /usr/src/ |
| 24 |
> total 16 |
| 25 |
> drwxr-xr-x 25 root root 4096 Feb 3 02:14 linux-5.4.92-gentoo |
| 26 |
> drwxr-xr-x 25 root root 4096 Dec 30 19:17 linux-5.4.80-gentoo-r1 |
| 27 |
> drwxr-xr-x 23 root root 4096 Dec 12 21:55 linux-4.19.72-gentoo |
| 28 |
> drwxr-xr-x 25 root root 4096 Oct 20 23:50 linux-5.4.72-gentoo |
| 29 |
> lrwxrwxrwx 1 root root 20 Nov 8 2019 linux -> linux-*4.19.72-gentoo* |
| 30 |
> |
| 31 |
> I'm not sure why I have all these newer versions of the kernel ... |
| 32 |
> |
| 33 |
> What should I be at? For an amd64... |
| 34 |
> |
| 35 |
> Oh man... |
| 36 |
> |
| 37 |
> $ eselect kernel list |
| 38 |
> Available kernel symlink targets: |
| 39 |
> [1] linux-5.4.72-gentoo |
| 40 |
> [2] linux-5.4.80-gentoo-r1 |
| 41 |
> [3] linux-5.4.92-gentoo |
| 42 |
> |
| 43 |
> Was there an adminstrative step that I missed there? |
| 44 |
> |
| 45 |
> |
| 46 |
When you do a sync, it pulls down the latest version of kernel source. I |
| 47 |
don't do it all the time, but you really ought to upgrade to 5.4.92. |
| 48 |
|
| 49 |
What I do (can't remember exactly because my live system hasn't been |
| 50 |
upgraded since forever :-) is copy .config from the old kernel to the |
| 51 |
new, and then is it "make oldconfig"? Either way, it configures the new |
| 52 |
kernel using the old config file so all my local-specific stuff is kept. |
| 53 |
|
| 54 |
Then just set it up in grub/whatever, make sure it works, and switch |
| 55 |
over to it. |
| 56 |
|
| 57 |
ALWAYS make sure your kernel is up-to-date before a depclean, because |
| 58 |
this is what happens ... |
| 59 |
|
| 60 |
(I *THINK* your old config will still be left lying around - as a |
| 61 |
locally modified file it shouldn't be cleaned up ...) |
| 62 |
|
| 63 |
Cheers, |
| 64 |
Wol |
Archives