On 3/31/20 1:31 PM, Giancarlo Razzolini wrote:
> Em março 31, 2020 14:03 Eli Schwartz via arch-general escreveu:
>>
>> See the broadcom-wl PKGBUILD for how to avoid this. Also note the
>> wireguard-{arch,lts} packages have adopted this method.
>>
>> It's up to Sven-Hendrik Haase if he wants to do t
Em março 31, 2020 14:03 Eli Schwartz via arch-general escreveu:
See the broadcom-wl PKGBUILD for how to avoid this. Also note the
wireguard-{arch,lts} packages have adopted this method.
It's up to Sven-Hendrik Haase if he wants to do this, though.
Well, the best way to avoid this is a comple
On 3/31/20 12:54 PM, Chris Billington via arch-general wrote:
> On Tue, Mar 31, 2020 at 12:48 PM Amin Vakil wrote:
>
>>
>> So why should nvidia-dkms upgrades?
>>
>
> it's because nvidia-dkms is part of a split package that builds both nvidia
> and nvidia-dkms. The bump in pkgrel is to rebuild nv
On Tue, Mar 31, 2020 at 12:48 PM Amin Vakil wrote:
>
> So why should nvidia-dkms upgrades?
>
it's because nvidia-dkms is part of a split package that builds both nvidia
and nvidia-dkms. The bump in pkgrel is to rebuild nvidia for the new
kernel, and as a consequence the pkgrel for nvidia-dkms is
I have recently installed nvidia-dkms as I use linux-hardened, although
I have installed linux package as well, but I always boot to linux-hardened.
Anyway I've noticed that nvidia-dkms increases pkgrel everytime linux
package gets upgraded, why is that so?
Taken from NVIDIA wiki:
Custom kernel
5 matches
Mail list logo
