21.02.2020 13:32, Peter Suetterlin пишет:
Michael Pujos wrote:
I run latest TW as of today.
Looking more closely, this is the nvidia modules that are never removed (see end of mail), and since they take quite a bit of space (around 70 MB) if takes a huge amount of space quickly.
These modules are part of the regular nvidia-gfxG05-kmp-default package. So is the issue in that package not removing old modules, or a more general issue higher up in the distro with the removal of old kernels not removing relevant /lib/modules/ folders ?
The issue is, they are not part of the package.
They most certainly are, at least today: bor@bor-Latitude-E5450:~/Загрузки$ rpm -q --qf '[%{filenames} flags=%{fileflags:fflags}\n]' -p nvidia-gfxG05-kmp-default-440.59_k5.5.1_1-24.2.x86_64.rpm | grep /lib/modules /lib/modules/5.5.1-1-default flags= /lib/modules/5.5.1-1-default/updates flags= /lib/modules/5.5.1-1-default/updates/nvidia-drm.ko flags=g /lib/modules/5.5.1-1-default/updates/nvidia-modeset.ko flags=g /lib/modules/5.5.1-1-default/updates/nvidia-uvm.ko flags=g /lib/modules/5.5.1-1-default/updates/nvidia.ko flags=g bor@bor-Latitude-E5450:~/Загрузки$ flags 'g' == %ghost - file payload is not delivered with package but file should be removed when package is removed. It is possible that this was not the case in the past.
They are compiled by the init/trigger scripts of the package, so they do not 'belong' to any package. And thus don't get removed :o
And removing tham *can* be dangerous, if the weak-updates method is used, as that only creates links to the original module.
I doubt kernel ABI remained stable between 4.19 and 5.5, so if weak updates actually created links it looks like an own issue by itself.
AFAIK at least in TW the weak-updates is not used anymore, no idea how that is for Leap.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org