On Fri, 13 Apr 2018 11:01:40 +0100
Mick wrote:
[…]
Yes, the broken symlinks are from the sysinit runlevel. I checked another
system of mine and it *also* has these broken symlinks ... :-/
So, whatever mistake I made, I must have made it at least twice! LOL!
I think this is nothing specia
On Thursday, 12 April 2018 22:47:31 BST Dave Trombley wrote:
> This has been broken for almost two years; the signature format switched to
> PKCS#7 and modinfo doesn't support it. It's not as simple as just
> patching kmod because evidently the kernel change regressed or disrespected
> the releve
On Wednesday, 11 April 2018 21:39:30 BST Ben Mezger wrote:
> Greetings,
>
> I have enabled module signature verification on my kernel, and it does
> seem to be enabled upon boot:
>
> $ dmesg | grep -i 'x.*509'
> [1.259988] Asymmetric key parser 'x509' registered
> [1.811026] Loading comp
On Tuesday, 10 April 2018 19:50:12 BST Floyd Anderson wrote:
> On Tue, 10 Apr 2018 17:11:17 +0100
>
> Mick wrote:
> >I've noticed udev has been playing up lately. In particular, switching on
> >wireless/bluetooth would cause udev to be pegged to 100% CPU and bluetooth
> >won't work. USB won't w
Before updating the nvidia driver, you should always check here:
Yes I've checked. That's why I was surprised by Portage build log. I
didn't build nvidia-drivers manually for a long time and do not remember
where this GPU checks are (ebuild or driver package).
I didn't think that this driver w
5 matches
Mail list logo