Cannot run script on X1 Yoga Gen 8 w/ Fedora 43 and a FM350-GL because "file system is read only"

[gitchutney]

Hey lovely people of Lenovo! I need some help getting the modem working.

I have ThinkPad X1 Yoga Gen 8 with a German keyboard and the following modem hardware:

 -----------------------------------
  Hardware  |           manufacturer: mtk
            |                  model: MBIM [14C3:4D75]
            |      firmware revision: 81600.0000.00.29.22.19_DT
            |                         E24
            |           h/w revision: V1.0.6
            |              supported: gsm-umts, lte, 5gnr
            |                current: gsm-umts, lte, 5gnr
            |           equipment id: 016177003395504

As I understand it, this is the Fibocom FM350-GL. I have already downloaded and installed the firmware provided by Lenovo even though this particular modem is supposedly supported directly in current kernels.

After installing the firmware, and adding a SIM, unlocking the SIM (I since disabled the PIN completely) and attempting to initiate a mobile broadband connection (the APN is in place and configured to the network providers specs) the modem gets stuck attempting to connect for no apparent reason.

Output from mmcli -m 0 -w gives me the following in a constant loop:

/org/freedesktop/ModemManager1/Modem/2: Initial state, 'enabling'
	/org/freedesktop/ModemManager1/Modem/2: State changed, 'enabling' --> 'disabled' (Reason: None or unknown)
	/org/freedesktop/ModemManager1/Modem/2: State changed, 'disabled' --> 'enabling' (Reason: User request)
	/org/freedesktop/ModemManager1/Modem/2: State changed, 'enabling' --> 'disabled' (Reason: None or unknown)
	/org/freedesktop/ModemManager1/Modem/2: State changed, 'disabled' --> 'enabling' (Reason: User request)
	/org/freedesktop/ModemManager1/Modem/2: State changed, 'enabling' --> 'disabled' (Reason: None or unknown)

I thought it must be the FCC lock I've read about in a bunch of places (which confuses me because the FCC have nothing to do with cell networks and hardware in Europe/Germany) and attempted to run the script. The result is failure and it presents similar to when I try to install a RPM over the command line:

$ chmod ugo+x fcc_unlock_setup.sh
./fcc_unlock_setup.sh
Copying files and libraries...
Legen Sie Ihren Finger auf den Fingerabdruckleser
Fedora Linux
tar: fcc-unlock.d: Funktion mkdir fehlgeschlagen: Das Dateisystem ist nur lesbar
tar: fcc-unlock.d: Funktion mkdir fehlgeschlagen: Das Dateisystem ist nur lesbar
tar: fcc-unlock.d/14c3\:4d75: Funktion open fehlgeschlagen: Datei oder Verzeichnis nicht gefunden
tar: fcc-unlock.d: Funktion mkdir fehlgeschlagen: Das Dateisystem ist nur lesbar
tar: fcc-unlock.d/1eac\:100d: Funktion open fehlgeschlagen: Datei oder Verzeichnis nicht gefunden
tar: fcc-unlock.d: Funktion mkdir fehlgeschlagen: Das Dateisystem ist nur lesbar
tar: fcc-unlock.d/8086\:7560: Funktion open fehlgeschlagen: Datei oder Verzeichnis nicht gefunden
tar: fcc-unlock.d: Funktion mkdir fehlgeschlagen: Das Dateisystem ist nur lesbar
tar: fcc-unlock.d/2c7c\:6008: Funktion open fehlgeschlagen: Datei oder Verzeichnis nicht gefunden
tar: fcc-unlock.d: Funktion mkdir fehlgeschlagen: Das Dateisystem ist nur lesbar
tar: fcc-unlock.d/1eac\:1007: Funktion open fehlgeschlagen: Datei oder Verzeichnis nicht gefunden
tar: Beende mit Fehlerstatus aufgrund vorheriger Fehler
chmod: Zugriff auf '/usr/lib64/ModemManager/fcc-unlock.d/*' nicht möglich: Datei oder Verzeichnis nicht gefunden
ln: die symbolische Verknüpfung '/usr/bin/lspci' konnte nicht angelegt werden: Die Datei existiert bereits
'libmodemauth.so' -> '/opt/fcc_lenovo/lib/libmodemauth.so'
'libmodemauth.so.1.1' -> '/opt/fcc_lenovo/lib/libmodemauth.so.1.1'
'libconfigserviceR+.so' -> '/opt/fcc_lenovo/lib/libconfigserviceR+.so'
'libconfigservice350.so' -> '/opt/fcc_lenovo/lib/libconfigservice350.so'
'libconfigservice350.so.1.1' -> '/opt/fcc_lenovo/lib/libconfigservice350.so.1.1'
'libmbimtools.so' -> '/opt/fcc_lenovo/lib/libmbimtools.so'
'mm_FccUnlock.cil' -> '/opt/fcc_lenovo/mm_FccUnlock.cil'
'mm_dmidecode.cil' -> '/opt/fcc_lenovo/mm_dmidecode.cil'
'mm_sh.cil' -> '/opt/fcc_lenovo/mm_sh.cil'
'DPR_Fcc_unlock_service' -> '/opt/fcc_lenovo/DPR_Fcc_unlock_service'
'configservice_lenovo' -> '/opt/fcc_lenovo/configservice_lenovo'
'lenovo-cfgservice.service' -> '/etc/systemd/system/./lenovo-cfgservice.service'
sed: Temporäre Datei /lib/systemd/system/sedlgSPTN kann nicht geöffnet werden: Das Dateisystem ist nur lesbar

Please forgive the German output. Essentially I'm being told that the file system is read only or that "function open failed: file or directory not found" and the script is thus unable to execute successfully. I tried running the commands with an additional sudo but that had no effect, either.

Any idea what is going on here?

[andreashaerter]

tar: Funktion mkdir fehlgeschlagen: Das Dateisystem ist nur lesbar

So the FCC unlock script can’t copy its helper files, That literally means: “Cannot create directory: filesystem is read-only.” So The FCC unlock script can’t copy its helper files to.

In which directory are you in when running ./fcc_unlock_setup.sh?

What is

mount | grep tmp
mount | grep ' / '

giving you as output?

[gitchutney]

Hi Andreas, thank you for he response!

I'm attempting to run the script from the directory into which I unpacked the archive:

/var/home/mangochutney/Downloads/lenovo-wwan-unlock-main

The output from the command you gave me is the following:

$ sudo mount | grep tmp
mount | grep ' / '

devtmpfs on /dev type devtmpfs (rw,nosuid,seclabel,size=16129856k,nr_inodes=4032464,mode=755,inode64)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,seclabel,inode64,usrquota)
tmpfs on /run type tmpfs (rw,nosuid,nodev,seclabel,size=6499780k,nr_inodes=819200,mode=755,inode64)
tmpfs on /run/credentials/systemd-cryptsetup@luks\x2d9ee337f4\x2df531\x2d4a94\x2dac78\x2dd7190e3f5ca4.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,seclabel,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
tmpfs on /run/credentials/systemd-journald.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,seclabel,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,seclabel,size=16249452k,nr_inodes=1048576,inode64,usrquota)
tmpfs on /run/credentials/systemd-resolved.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,seclabel,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=3249888k,nr_inodes=812472,mode=700,uid=1000,gid=1000,inode64)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=3249888k,nr_inodes=812472,mode=700,inode64)
composefs on / type overlay (ro,relatime,seclabel,lowerdir+=/run/ostree/.private/cfsroot-lower,datadir+=/sysroot/ostree/repo/objects,redirect_dir=on,metacopy=on)

Thanks to a friend I learned that Fedora Silverblue intentionally isolates various system-level folders into a read-only state and this might be the entire reason for this. My apologies for not mentioning the specific distro I'm using in the first post.

[gitchutney]

Any idea @andreashaerter?

[gitchutney]

Can someone please tell me if the issues I've been running into simply stem from the fact that I'm using Fedora Silverblue?
I checked the documentation and the entire root filesystem is isolated and read-only. I found this part in the Silverblue documentation and it states that sym-linked directories exist at in var/ and I now I wonder if modifying the script itself to write the files var/us/… etc. is going to help.