Executable Permission Doesn't follow on Copy

Support Software & Applications
1

Running the latest version of Manjaro KDE 6.2.4, Kernel 6.11.11.1

I’m trying to update the ASUS BIOS. I’ve downloaded the BIOS file, changed the name as instructed, and given the file permission to be executable. That part is fine.

However, when I copy over to the USB drive, it loses it’s executable permission, and won’t hold the permission after checking it in properties.

I’ve updated the BIOS before without a problem. This one has me stumped. Thanks in advance for the help.

2

The USB drive probably has a non-POSIX-compatible filesystem on it, like vfat, exfat or ntfs.

Such filesystems do not understand or store POSIX permissions and file ownership, and thus the permissions have to be emulated in the virtual filesystem layer of the kernel when the filesystem is mounted.

As such, the emulated permissions mask is only applied upon mounting the filesystem as part of the mount options, and the emulated permissions apply to the whole filesystem; they cannot be altered on an individual basis, nor can they be altered for the whole filesystem without remounting it. And as I said already, they are also not stored on-disk.

3

But that doesn’t matter, because you will be updating with a program within your UEFI firmware that doesn’t care whether there are any execute permissions or not.
:footprints:

2 Likes
4

You can likely try this another way.

Please see the instructions on how to Update BIOS in BIOS Utility (with EZ Flash) at either of the following links:

There’s even a video, if you like that sort of thing.

(You will need a USB most likely formatted as FAT32).

Regards.

1 Like
5

I’ve used the same drive for the BIOS updates every time, and it’s formatted FAT32

6

FAT32 can´t transport POSIX permissions :man_shrugging:

1 Like
7

This is EOL in stable branch and already unsupported in testing, should be changed soon to a LTS kernel or 6.12.

2 Likes
8

Thanks guys for all the help. I looked further and opened the USB in Gparted and found there was an exclamation point next to it. I presume somehow the drive became corrupt. I reformatted, loaded the file, and voila! Everything loaded and all is good in the world again