Hey everyone. I'm trying to use a 16 GB SD card to store my Steam games, but selecting it gives me the following error.
New Steam library folder must be on a filesystem mounted with execute permissions
Here's a screenshot of the SD card in the Disks app.
After looking online for a fix, I think I mounted the SD card or something, and now Steam says "New Steam library folder must be writeable".
You might look at mounting it with full permissions, so that you can access it without having to grant permissions each time in the future:
I ran this command to unmount the SD card.
sudo umount /dev/mmcblk1p1
And then when trying to run the next command, I got "mount point does not exist".
sudo mount -o rw,users,umask=000 /dev/mmcblk1p1 /mnt/sd1
Now I got this.
special device /dev/sdb1 does not exist.
Usage:
mount [-lhV]
mount -a [options]
mount [options] [--source] <source> | [--target] <directory>
mount [options] <source> <directory>
mount <operation> <mountpoint> [<target>]
Because I don't even know what a mount point is or how this command works.
I mounted the SD card at /mnt/sd but now the card got a weird name in the files explorer and clicking it doesn't do anything.
I created the Steam folder right in the SD card. And no, I didn't eject the card. I'm not used to ejecting stuff, as I just assume it's not in use after a couple minutes of inactivity.
And why was it mounted in a different directory (/mnt), when I specified /mnt/sd in the terminal command?
Wait. It's mounted in /mnt/sd now. But I don't understand how to make it get that name instead of "Library" which is the partition's name. If I unmount and mount it using the Disks app, it does get the "Library" name and a nice SD card icon.
Update.
I messed around with the mount options in the Disks app and managed to give it a display name and icon.
But the main problem is still there.
Clicking the SD card simply shows a "loading" animation next to it for like a tenth of a second, and never actually opens the SD card in the files explorer.
I finally fixed it using the instructions in this answer.
Unmounting the partition and then using this command seems to have fixed it, though I'm not sure what exactly made it work this time.
sudo mount -o rw,users,umask=000,exec /dev/mmcblk1p1 /media/deso/Library
I can now create folders and files in the SD card, and Steam accepted the drive as a library without any issues.
How would I boot into Linux with secure boot enabled?
Anyway, while the card works fine now, removing it and inserting it again created a second mounting point called "Library1" (original was Library), and both of them show up in the files explorer.
Do I create a new issue?
You can test using Zorin OS with Secure Boot enabled - you may need to set up some mok-utils... But most users don't have too much trouble.
The issues caused by Secure Boot stem from the fact that Microsoft signed off on most Linux applications to allow Secure Boot to pass them through - but not all applications.
Users not using those unsigned apps have no trouble.
Those that do happen to use those unsigned apps run into trouble if they are also using secure boot.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
