DKMS fails to remove old modules after kernel update

General system Newbie
1

I have a couple of DKMS packages installed (nvidia-open-dkms, v4l2loopback-dkms) and have recently started noticing some warnings during system upgrades (I use eos-update).

More specifically, when new kernel updates are installed, the pre-transaction hook to remove old DKMS modules fails to find the module directories for the existing kernels. It seems like the existing kernel module directories are deleted before DKMS is invoked to remove the existing modules, which causes DKMS to fail and modules to persist indefinitely (throwing warnings and eventually errors during future updates).

Here is an example update log (I’ve trimmed the irrelevant stuff here - none of the DKMS packages themselves were updated but this only seems to happen when the kernels are updated):

eos-update: package updater with additional features
Updating native and AUR apps...
:: Synchronising package databases...
 endeavouros                                                                 14.7 KiB  14.5 KiB/s 00:01 [-------------------------------------------------------------] 100%
 core                                                                       117.3 KiB   259 KiB/s 00:00 [-------------------------------------------------------------] 100%
 extra                                                                        7.5 MiB  6.33 MiB/s 00:01 [-------------------------------------------------------------] 100%
 multilib                                                                   132.7 KiB   311 KiB/s 00:00 [-------------------------------------------------------------] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Package (22)                 Old Version             New Version             Net Change  Download Size

...
core/linux                   6.12.6.arch1-1          6.12.7.arch1-1            0.00 MiB     137.70 MiB
core/linux-headers           6.12.6.arch1-1          6.12.7.arch1-1            0.12 MiB      26.66 MiB
core/linux-lts               6.6.67-1                6.6.68-1                  0.11 MiB     128.45 MiB
core/linux-lts-headers       6.6.67-1                6.6.68-1                  2.09 MiB      24.74 MiB
...

Total Download Size:   344.87 MiB
Total Installed Size:  638.30 MiB
Net Upgrade Size:        3.07 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
...
(22/22) checking for file conflicts                                                                     [-------------------------------------------------------------] 100%
:: Running pre-transaction hooks...
(1/2) Removing initramfs...
(2/2) Remove DKMS modules
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
:: Processing package changes...
...
(10/22) upgrading linux                                                                                 [-------------------------------------------------------------] 100%
(11/22) upgrading linux-headers                                                                         [-------------------------------------------------------------] 100%
(12/22) upgrading linux-lts                                                                             [-------------------------------------------------------------] 100%
(13/22) upgrading linux-lts-headers                                                                     [-------------------------------------------------------------] 100%
...
:: Running post-transaction hooks...
( 1/15) Creating system user accounts...
( 2/15) Reloading system manager configuration...
( 3/15) Reloading user manager configuration...
( 4/15) Restarting marked services...
( 5/15) Creating temporary files...
( 6/15) Arming ConditionNeedsUpdate...
( 7/15) Updating module dependencies...
( 8/15) Install DKMS modules
==> dkms install --no-depmod v4l2loopback/0.13.2 -k 6.12.7-arch1-1
==> dkms install --no-depmod v4l2loopback/0.13.2 -k 6.6.68-1-lts
==> dkms install --no-depmod nvidia/565.77 -k 6.6.68-1-lts
==> dkms install --no-depmod nvidia/565.77 -k 6.12.7-arch1-1
==> depmod 6.12.7-arch1-1
==> depmod 6.6.68-1-lts
( 9/15) Updating initramfs...
...
(10/15) Reloading system bus configuration...
(11/15) Warn about old perl modules
(12/15) Check if user should be informed about rebooting after certain system package upgrades.
(13/15) Updating icon theme caches...
(14/15) Checking which packages need to be rebuilt
...
(15/15) Updating the desktop file MIME type cache...

Running dkms status afterwards:

> dkms status
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
nvidia/565.77, 6.12.7-arch1-1, x86_64: installed
nvidia/565.77, 6.6.67-1-lts, x86_64: installedfind: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
 (Built modules are missing in the kernel modules folder)
nvidia/565.77, 6.6.68-1-lts, x86_64: installed
v4l2loopback/0.13.2, 6.12.6-arch1-1, x86_64: installedfind: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
 (Built modules are missing in the kernel modules folder)
v4l2loopback/0.13.2, 6.12.7-arch1-1, x86_64: installed
v4l2loopback/0.13.2, 6.6.67-1-lts, x86_64: installedfind: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
 (Built modules are missing in the kernel modules folder)
v4l2loopback/0.13.2, 6.6.68-1-lts, x86_64: installed

And sure enough, /usr/lib/modules now only contains the new kernel directories:

> ls /usr/lib/modules
6.12.7-arch1-1  6.6.68-1-lts

Whilst dkms itself still has listings for the previous module versions:

> ls /var/lib/dkms/nvidia/
565.77  kernel-6.12.6-arch1-1-x86_64  kernel-6.12.7-arch1-1-x86_64  kernel-6.6.67-1-lts-x86_64  kernel-6.6.68-1-lts-x86_64
> ls /var/lib/dkms/nvidia/565.77 
6.12.6-arch1-1  6.12.7-arch1-1  6.6.67-1-lts  6.6.68-1-lts  source

Going through and manually removing all old kernel versions for each package within /var/lib/dkms is enough to make DKMS happy:

> cd /var/lib/dkms/nvidia                                  
> sudo rm -r kernel-6.12.6-arch1-1-x86_64 kernel-6.6.67-1-lts-x86_64 565.77/6.12.6-arch1-1 565.77/6.6.67-1-lts
> cd ../v4l2loopback 
> sudo rm -r kernel-6.12.6-arch1-1-x86_64 kernel-6.6.67-1-lts-x86_64 0.13.2/6.12.6-arch1-1 0.13.2/6.6.67-1-lts 
> dkms status
nvidia/565.77, 6.12.7-arch1-1, x86_64: installed
nvidia/565.77, 6.6.68-1-lts, x86_64: installed
v4l2loopback/0.13.2, 6.12.7-arch1-1, x86_64: installed
v4l2loopback/0.13.2, 6.6.68-1-lts, x86_64: installed

But this doesn’t feel like something that should be happening and I can’t find anyone else online running into the same issue. I have tried fully uninstalling all DKMS modules and DKMS itself before clearing all related directories and reinstalling, but the issue persists.

2

Any chance also headers installed?

3

Hmm I’m not sure what you mean. The logs above show linux-headers and linux-lts-headers were updated as well as the kernels?

4

I have a very similar output and is way longer. It’s been going on for a while but i haven’t had any issues with booting or updating. Not sure what is causing it either. I could post it but it’s pretty large.

Edit: As per the man page

status [module/module-version] [-k kernel/arch]

           Returns the current status of modules, versions and kernels within the tree as well as whether  they  have
           been  added,  built or installed.  Status can be shown for just a certain module, a certain kernel, a mod‐
           ule/version combination or a module/version/kernel combination.

           If the source directory, or the symbolic link 'source' pointing to it is missing, the status of  the  mod‐
           ule/version  combination  will be displayed as 'broken'.  In that case dkms will not perform any other ac‐
           tion on that particular module/version combination.  Manual intervention is required.  If  only  the  sym‐
           bolic  link  'source'  is  missing, the add action may be used to re-add the module/version combination to
           dkms.

Edit: https://0x0.st/8s2f.txt

:point_up:

Edit: The only modules i see listed in /usr/lib/modules are the ones for the current kernel installed. Same for broadcom and vmware errors. Not sure if something needs to be added to dracut? Or?

Edit: I have never added the eos-defaults for dracut as per the wiki. Is this something that needs to be done?

5

Yeah mine used to be longer as well, but I started cleaning it up myself after every update.

It hasn’t caused any noticeable issues, but I did get that Error! Manual intervention required! on a couple of packages after a combination of kernel update (leaving source/build directories around for old kernels) followed by package update (which would then try to remove the old package version and fail for the same reason, upgrading the warning to an error).

This also meant that some packages would stick around even after I uninstalled them (eg. xone-dkms from AUR is now unmaintained) and continue to throw warnings/errors every system update.

Ultimately it looks like the “errors” just mean “this module version will not work” and it doesn’t stop new versions from installing/working so not a big deal, but I guess as a (relatively) new user seeing any “error” in a system upgrade is enough to make me want to be proactive about it just in case :slight_smile:

6

Okay so i have removed everything that was shown in my output. How do i get dkms status to show properly? Do i need to wait for a kernel update? Also there are still many older kernels in the directory yet. Should i remove them all except the kernel that’s current. Also have the same in vmware-workstation and broadcom.

7

I think something is needed for dkms module removal when newer versions are installed. I just don’t know how to do that properly. This seems to be an issue for anything that uses dkms such as broadcom, vmware-workstation, kernels, nvidia etc…

8

Yeah when I do it I basically remove everything from /var/lib/dkms that isn’t the most recent module/kernel version combo. You could do this by hand like I did in the original post:

> cd /var/lib/dkms/nvidia                                  
> sudo rm -r kernel-6.12.6-arch1-1-x86_64 kernel-6.6.67-1-lts-x86_64 565.77/6.12.6-arch1-1 565.77/6.6.67-1-lts
> cd ../v4l2loopback 
> sudo rm -r kernel-6.12.6-arch1-1-x86_64 kernel-6.6.67-1-lts-x86_64 0.13.2/6.12.6-arch1-1 0.13.2/6.6.67-1-lts 
> dkms status
nvidia/565.77, 6.12.7-arch1-1, x86_64: installed
nvidia/565.77, 6.6.68-1-lts, x86_64: installed
v4l2loopback/0.13.2, 6.12.7-arch1-1, x86_64: installed
v4l2loopback/0.13.2, 6.6.68-1-lts, x86_64: installed

If you have many though, the easiest way is probably to just uninstall all DKMS packages and DKMS itself, then completely delete /var/lib/dkms and reinstall the packages. Should fix itself up, but will start happening again after the next upgrade.

I’m far from an expert though, so there may be some hidden side-effect to this that I’m not aware of (you lose DKMS module history), but I’ve been doing it this way for a couple weeks now and haven’t had any issues of note.

1 Like
9

I think it needs some hook or something to do this automatically. Or in dracut? I don’t know. I’m not knowledgeable in this area.

Edit: Thanks for bringing this up as i was wondering what to do with the entries in the log. Now I’ve cleared it all I’ll see how it looks.

1 Like
10

@Namey5
I just did the same on my other desktop and i had to remove the nvidia entries as well. This is a pain so I’m going to have to do it every time there is an update to any dkms module. Or maybe I’ll try to get some help on figuring out how these entries can be removed automatically which would be nice and also make more sense. :wink:

Edit: What is weird though is it shows if i run dkms status that it still lists them. :thinking:

Edit: I wish I knew more about this because now it’s starting to bug me.I shouldn’t have to do this much manual intervention just because I’m using dkms versions of packages. Doesn’t make sense.

11

What is weird though is it shows if i run dkms status that it still lists them. :thinking:

Hmm yeah only thing I can think is that there are multiple copies of the built module directory for each module/kernel version, so in my case (i.e. 2 kernels) I have to delete 4 copies of the same module every time the kernels are updated.

For example, nvidia-open-dkms/565.77 after updating both linux/6.12.6->linux/6.12.7 and linux-lts/6.6.67->linux-lts/6.6.68:

> cd /var/lib/dkms/nvidia                                  
> sudo rm -r \
    kernel-6.12.6-arch1-1-x86_64 \
    kernel-6.6.67-1-lts-x86_64 \
    565.77/6.12.6-arch1-1 \
    565.77/6.6.67-1-lts

But after doing that for every installed module, dkms status shows all clear for me.

I wonder if there might be other metadata stored in /var/lib/dkms for broken modules as the last time I encountered those I went the route of fully uninstalling everything and just wiping the entire cache.

I do specifically note this occurring on kernel updates though as from memory just updating a DKMS package/module on the same kernel does cleanup after itself correctly, unless it already has an older kernel build still hanging around (which is when it starts complaining harder).

I shouldn’t have to do this much manual intervention just because I’m using dkms versions of packages.

The installed module folders for the kernels in /usr/lib/modules definitely are still around before the system upgrade, so it does just feel like something is happening slightly out of order. What doesn’t make sense to me is why those would be gone by the time the pre-transaction hooks are run - the only thing on my side that happens before dkms remove for the existing modules is downloading the package upgrades and Removing initramfs, so maybe the actual hook to remove the DKMS modules is not working/doing something weird.

12

I had so many in there and i removed them each individually so the only one left is the current modules. This goes for kernels and vmware in it’s own directory and nvidia in it’s own directory. There aren’t any left so I’m not sure why it’s still listing them. I can’t go back now because i couldn’t possibly remember every kernel file that was there for instance. Not sure where there would be other copies it would pick up on?

Edit: I removed them from /usr/lib/modules and also /var/lib/dkms

Edit: I’m going to keep a closer eye on the next updates to see exactly what happens in the process. I really don’t have the expertise to understand all these things in dracut happening and the hooks etc. :wink:

13

This is what needs to be confirmed i think? :thinking:

14

@Namey5

So running dkms status shows this still after removing everything.

[ricklinux@asus-tuff ~]$ dkms status
find: ‘/usr/lib/modules/6.12.3-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.3-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.3-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.4-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.4-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.4-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.6.63-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.63-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.63-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.64-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.64-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.64-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.65-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.65-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.65-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.12.4-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.4-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.4-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.6.65-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.65-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.65-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
nvidia/565.77, 6.12.7-arch1-1, x86_64: installed
nvidia/565.77, 6.6.63-1-lts, x86_64: builtfind: ‘/usr/lib/modules/6.6.63-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.63-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.63-1-lts/’: No such file or directory
 (Built modules are missing in the kernel modules folder)
nvidia/565.77, 6.6.64-1-lts, x86_64: builtfind: ‘/usr/lib/modules/6.6.64-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.64-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.64-1-lts/’: No such file or directory
 (Built modules are missing in the kernel modules folder)
nvidia/565.77, 6.6.65-1-lts, x86_64: builtfind: ‘/usr/lib/modules/6.6.65-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.65-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.65-1-lts/’: No such file or directory
 (Built modules are missing in the kernel modules folder)
nvidia/565.77, 6.6.67-1-lts, x86_64: builtfind: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
 (Built modules are missing in the kernel modules folder)
nvidia/565.77, 6.6.68-1-lts, x86_64: installed
vmware-workstation/17.6.2_24409262, 6.12.4-arch1-1, x86_64: builtfind: ‘/usr/lib/modules/6.12.4-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.4-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.4-arch1-1/’: No such file or directory
 (Built modules are missing in the kernel modules folder)
vmware-workstation/17.6.2_24409262, 6.12.6-arch1-1, x86_64: builtfind: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
find: ‘/usr/lib/modules/6.12.6-arch1-1/’: No such file or directory
 (Built modules are missing in the kernel modules folder)
vmware-workstation/17.6.2_24409262, 6.12.7-arch1-1, x86_64: installed
vmware-workstation/17.6.2_24409262, 6.6.65-1-lts, x86_64: builtfind: ‘/usr/lib/modules/6.6.65-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.65-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.65-1-lts/’: No such file or directory
 (Built modules are missing in the kernel modules folder)
vmware-workstation/17.6.2_24409262, 6.6.67-1-lts, x86_64: builtfind: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
find: ‘/usr/lib/modules/6.6.67-1-lts/’: No such file or directory
 (Built modules are missing in the kernel modules folder)
vmware-workstation/17.6.2_24409262, 6.6.68-1-lts, x86_64: installed
[ricklinux@asus-tuff ~]$

I even ran sudo dracut-rebuild

15

Did you reboot?

16

Don’t remember but i will now.

Edit:

Output is still the same. I don’t understand what’s telling it to find these modules because they don’t exist. I have removed them from the path it had shown.

Edit:

When a new kernel is installed it rebuilds the modules for dkms but it doesn’t seem to remove the existing ones. I had so many kernels and vmware-workstation and only a couple broadcom and many nvidia.

Edit:

Also when i run sudo dracut-rebuild it looks pristine.

Edit:

I am having this issue on both computers that are btrfs with btrfs-assistant, snapper-support, btrfsmaintenace and grub-btrfs.

Edit:

I am wondering if it’s picking this stuff up from the previous snapshots?

1 Like
17

Does give paccheck --list-broken output with dkms?

Dkms should have pacman remove/upgrade hooks?

18 
[ricklinux@asus-tuff ~]$ paccheck --list-broken 
warning: audit: '/etc/audit/plugins.d/af_unix.conf' read error (Permission denied)
warning: audit: '/etc/audit/plugins.d/au-remote.conf' read error (Permission denied)
warning: audit: '/etc/audit/plugins.d/audispd-zos-remote.conf' read error (Permission denied)
warning: audit: '/etc/audit/plugins.d/filter.conf' read error (Permission denied)
warning: audit: '/etc/audit/plugins.d/syslog.conf' read error (Permission denied)
warning: audit: '/usr/share/factory/etc/audit/plugins.d/af_unix.conf' read error (Permission denied)
warning: audit: '/usr/share/factory/etc/audit/plugins.d/au-remote.conf' read error (Permission denied)
warning: audit: '/usr/share/factory/etc/audit/plugins.d/audispd-zos-remote.conf' read error (Permission denied)
warning: audit: '/usr/share/factory/etc/audit/plugins.d/filter.conf' read error (Permission denied)
warning: audit: '/usr/share/factory/etc/audit/plugins.d/syslog.conf' read error (Permission denied)
audit
warning: bind: '/var/named/127.0.0.zone' read error (Permission denied)
warning: bind: '/var/named/localhost.ip6.zone' read error (Permission denied)
warning: bind: '/var/named/localhost.zone' read error (Permission denied)
bind
warning: cups: '/var/cache/cups/rss' read error (Permission denied)
warning: cups: '/var/spool/cups/tmp' read error (Permission denied)
cups
warning: nfs-utils: '/var/lib/nfs/statd/sm.bak' read error (Permission denied)
warning: nfs-utils: '/var/lib/nfs/statd/sm' read error (Permission denied)
warning: nfs-utils: '/var/lib/nfs/statd/state' read error (Permission denied)
nfs-utils
19

Not sure how to check this?

20

Sorry try with sudo