Re: [gentoo-user] Re: Since when does module-rebuild delete modules for previous kernel version?

2021-07-07 Thread Dale
Nikos Chantziaras wrote: > On 08/07/2021 02:18, Neil Bothwick wrote: >> On Thu, 8 Jul 2021 02:09:17 +0300, Nikos Chantziaras wrote: >> >>> So far, so good. But when I ran "emerge @module-rebuild", which >>> rebuilds these two packages: >>> >>>     app-emulation/vmware-modules >>>    

[gentoo-user] Re: Since when does module-rebuild delete modules for previous kernel version?

2021-07-07 Thread Nikos Chantziaras
On 08/07/2021 02:18, Neil Bothwick wrote: On Thu, 8 Jul 2021 02:09:17 +0300, Nikos Chantziaras wrote: So far, so good. But when I ran "emerge @module-rebuild", which rebuilds these two packages: app-emulation/vmware-modules x11-drivers/nvidia-drivers The vmwware and nvidia kernel

Re: [gentoo-user] Since when does module-rebuild delete modules for previous kernel version?

2021-07-07 Thread Neil Bothwick
On Thu, 8 Jul 2021 02:09:17 +0300, Nikos Chantziaras wrote: > So far, so good. But when I ran "emerge @module-rebuild", which > rebuilds these two packages: > >app-emulation/vmware-modules >x11-drivers/nvidia-drivers > > The vmwware and nvidia kernel modules got deleted from >

[gentoo-user] Since when does module-rebuild delete modules for previous kernel version?

2021-07-07 Thread Nikos Chantziaras
So I just noticed that when I run: emerge @module-rebuild after having installed a kernel update, the kernel modules of the previous kernel version are being deleted. I am sure this didn't use to be the case. I have two entries configured in grub: Gentoo Gentoo (previous kernel) They

Re: [gentoo-user] glibc-2.33-r1 crashes out at the start before building.

2021-07-07 Thread Alan Mackenzie
Hello, Dan. On Wed, Jul 07, 2021 at 12:28:35 -0700, Daniel Frey wrote: > On 7/7/21 11:16 AM, Alan Mackenzie wrote: > > Hello, Gentoo. > > Would somebody help me here, please. > > When I try to emerge glibc-2.33-r1, the very first phase of the build > > crashes out with: > >

Re: [gentoo-user] glibc-2.33-r1 crashes out at the start before building.

2021-07-07 Thread Daniel Frey
On 7/7/21 11:16 AM, Alan Mackenzie wrote: Hello, Gentoo. Would somebody help me here, please. When I try to emerge glibc-2.33-r1, the very first phase of the build crashes out with: x86_64-pc-linux-gnu-gcc -O2 -pipe -march=native -Wl,-O1 -Wl,--as-needed glibc-test.c -o glibc-test *

Re: [gentoo-user] glibc-2.33-r1 crashes out at the start before building.

2021-07-07 Thread Alan Mackenzie
Hi, Dale. On Wed, Jul 07, 2021 at 13:23:21 -0500, Dale wrote: > Alan Mackenzie wrote: > > Hello, Gentoo. > > Would somebody help me here, please. > > When I try to emerge glibc-2.33-r1, the very first phase of the build > > crashes out with: > > x86_64-pc-linux-gnu-gcc -O2 -pipe -march=native

Re: [gentoo-user] glibc-2.33-r1 crashes out at the start before building.

2021-07-07 Thread Dale
Alan Mackenzie wrote: > Hello, Gentoo. > > Would somebody help me here, please. > > When I try to emerge glibc-2.33-r1, the very first phase of the build > crashes out with: > > x86_64-pc-linux-gnu-gcc -O2 -pipe -march=native -Wl,-O1 -Wl,--as-needed > glibc-test.c -o glibc-test > *

[gentoo-user] glibc-2.33-r1 crashes out at the start before building.

2021-07-07 Thread Alan Mackenzie
Hello, Gentoo. Would somebody help me here, please. When I try to emerge glibc-2.33-r1, the very first phase of the build crashes out with: x86_64-pc-linux-gnu-gcc -O2 -pipe -march=native -Wl,-O1 -Wl,--as-needed glibc-test.c -o glibc-test * Checking that IA32 emulation is enabled in the

Re: [gentoo-user] cryptsetup close and device in use when it is not

2021-07-07 Thread Dale
Dr Rainer Woitok wrote: > Ramon, Dale, > > On Tuesday, 2021-07-06 20:40:32 +0200, Ramon Fischer wrote: > >> This is just a guess. Maybe you have two devices with the same UUID? >> >> If so, you can change it with: >> >> $ cryptsetup --uuid="" luksUUID "/dev/sdx1" > Good idea. But to find out

Re: [gentoo-user] cryptsetup close and device in use when it is not

2021-07-07 Thread Dr Rainer Woitok
Ramon, Dale, On Tuesday, 2021-07-06 20:40:32 +0200, Ramon Fischer wrote: > This is just a guess. Maybe you have two devices with the same UUID? > > If so, you can change it with: > > $ cryptsetup --uuid="" luksUUID "/dev/sdx1" Good idea. But to find out whether or not this is the cause