EM7455 Thinkpad T470 Debian Bookworm 12 Troubles

Connectivity and Cloud Services
1

Hello I am new here and don›t know where this questions belongs, I have a Refuhrbished Thinkpad T470 mit 4G LTE-A Qualcomm Snapdragon X7 LTE-A Sierra Wireless EM7455.

lsb_release -a; uname -a; lsusb

No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 12 (bookworm)
Release: 12
Codename: bookworm
Linux T470 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux
Bus 002 Device 003: ID 0bc2:231a Seagate RSS LLC Expansion Portable
Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. Card Reader
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 04f2:b5ab Chicony Electronics Co., Ltd Integrated Camera
Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 004: ID 1199:9079 Sierra Wireless, Inc. EM7455
Bus 001 Device 011: ID 046d:c07f Logitech, Inc. Gaming Mouse G302
Bus 001 Device 012: ID 145f:02c9 Trust Trust Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I downloaded the files:
SierraLinuxQMIdriversS2.42N2.64.tar.bz2
GCF & PTCRB Approved—Release 27 (current unused)
GCF Approved—Release 29 (current unused)
modemmanager_1.20.4-1_amd64.deb

I installed pppconfig

Then I tried:
Root Shell
sudo mkdir -p /usr/src/SierraLinuxQMIdrivers-S2.42N2.64
sudo tar -C /usr/src/SierraLinuxQMIdrivers-S2.42N2.64 -xvf SierraLinuxQMIdriversS2.42N2.64.tar.bz2

The modem manager accepts the Pin, but the modem cannot be activated
How can this be repaired?

Root Shell:

mmcli -m 0 -e

error: couldn’t find the ModemManager process in the bus

Then I tried to make a installation with:
sudo dkms build --verbose -m SierraLinuxQMIdrivers -v S2.42N2.64
{ make -j4 KERNELRELEASE=6.1.0-13-amd64 -C GobiSerial && make -C GobiNet; } >> /var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/make.log 2>&1
(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.1.0-13-amd64 (x86_64)

nano /var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/make.log
GNU nano 7.2 /var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/make.log
DKMS make.log for SierraLinuxQMIdrivers-S2.42N2.64 for kernel 6.1.0-13-amd64 (x86_64)
Di 31. Okt 22:16:49 CET 2023 make: Verzeichnis „/var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial“ wird betreten
rm -rf *.o ~ core .depend ..cmd *.ko .mod.c .tmp_versions Module. modules.order .cache.mk .o.ur-safe
make -C /lib/modules/6.1.0-13-amd64/build M=/var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial modules
make[1]: Verzeichnis „/usr/src/linux-headers-6.1.0-13-amd64“ wird betreten
CC [M] /var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial/GobiSerial.o
/var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial/GobiSerial.c:242:2: warning: #warning "Assuming disc_mutex is locked>
242 | #warning “Assuming disc_mutex is locked external to the module”
| ^~~~~~~
/var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial/GobiSerial.c:773:27: error: initialization of ‘void ()(struct usb_s>
773 | .port_remove = Gobi_portremove,
| ^~~~~~~~~~~~~~~
/var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial/GobiSerial.c:773:27: note: (near initialization for ‘gGobiDevice.por> cc1: some warnings being treated as errors
make[2]: *** [/usr/src/linux-headers-6.1.0-13-common/scripts/Makefile.build:255: /var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/buil>
make[1]: *** [/usr/src/linux-headers-6.1.0-13-common/Makefile:2039: /var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial]>
make[1]: Verzeichnis „/usr/src/linux-headers-6.1.0-13-amd64“ wird verlassen
make: *** [Makefile:25: all] Fehler 2
make: Verzeichnis „/var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial“ wird verlassen

disc_mutex is locked

unfortunately, i am not familiar with at!pcinfo Commands, but I have a backup before I tried to install EM7455, can also start from scratch again

I want to access the internet and work anywhere with my notebook

Please help me step by step.
Best regards Roburn

2

The gobi USB driver has been end of life.
you are using kernel 6.1.0, you can check the following MBPL USB driver:

https://source.sierrawireless.com/resources/airprime/software/mbpl/mbpl-software-latest/#sthash.5K53774e.dpbs

3

hello jyijyi,

i tried the installation on a freshly installed linux without gobi driver and gobi problems with disc_mutex is locked and dkms build

XXX

Repeat the command to verify (dkms add)

sudo dkms add - - verbose -m SierraLinuxQMIdrivers -v s2.42n2.64

Error The DKMS tree already contains SierraLinuxQMIdrivers -v s2.42n2.64

well done

XXX

Root shell: sudo dkms build --verbose -m SierraLinuxQMIdrivers -v S2.42N2.64

sudo dkms build --verbose -m SierraLinuxQMIdrivers -v S2.42N2.64

Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file

Signing key: /var/lib/dkms/mok.key

Public certificate (MOK): /var/lib/dkms/mok.pub

Translated with DeepL Translate: The world's most accurate translator (free version)

Build module:

make -C GobiSerial clean; make -C GobiNet clean

make: Directory “/var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial” is entered

rm -rf *.o ~ core .depend ..cmd *.ko .mod.c .tmp_versions Module. modules.order .cache.mk *.o.ur-safe

make: Directory “/var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial” is exited

make: Directory “/var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiNet” is entered

rm -rf *.o ~ core .depend ..cmd *.ko .mod.c .tmp_versions Module. modules.order .cache.mk *.o.ur-safe

make: Directory “/var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiNet” is exited

{ make -j4 KERNELRELEASE=6.1.0-13-amd64 -C GobiSerial && make -C GobiNet; } >> /var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/make.log 2>&1

(bad exit status: 2)

Error! Bad return status for module build on kernel: 6.1.0-13-amd64 (x86_64)

Read /var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/make.log for more information.

Root shell: nano /var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/make.log

DKMS make.log für SierraLinuxQMIdrivers-S2.42N2.64 für Kernel 6.1.0-13-amd64 (x86_64)

Sa 4. Nov 11:47:20 CET 2023

make: Verzeichnis “/var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial” wird betreten

rm -rf *.o ~ core .depend ..cmd *.ko .mod.c .tmp_versions Module. modules.order .cache.mk *.o.ur-safe

make -C /lib/modules/6.1.0-13-amd64/build M=/var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial Module

make[1]: Verzeichnis “/usr/src/linux-headers-6.1.0-13-amd64” wird betreten

CC [M] /var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial/GobiSerial.o

/var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial/GobiSerial.c:242:2: warning: #warning “Assuming disc_mutex is locked external to the module” [-Wcpp]

242 | #warning “Angenommen, disc_mutex ist außerhalb des Moduls gesperrt”

| ^~~~~~~

/var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial/GobiSerial.c:773:27: Error: Initialization of 'void (*)(struct usb_serial_port )’ of incompatible pointer type 'int ()(s>

773 | .port_remove = Gobi_portremove,

| ^~~~~~~~~~~~~~~

/var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial/GobiSerial.c:773:27: Note: (near initialization for ‘gGobiDevice.port_remove’)

cc1: some warnings are treated as errors

make[2]: *** [/usr/src/linux-headers-6.1.0-13-common/scripts/Makefile.build:255: /var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial/GobiSerial.o] Error 1

make[1]: *** [/usr/src/linux-headers-6.1.0-13-common/Makefile:2039: /var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial] Error 2

make[1]: Directory “/usr/src/linux-headers-6.1.0-13-amd64” is exited

make: *** [Makefile:25: all] Error 2

make: Directory “/var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64/build/GobiSerial” is exited

How can I solve this?

Thank you very much for your help

Roburn

4

The gobi USB driver has been end of life.
you are using kernel 6.1.0, you can check the following MBPL USB driver:

https://source.sierrawireless.com/resources/airprime/software/mbpl/mbpl-software-latest/#sthash.5K53774e.dpbs

5

Hi jyi jyi is your answer to my 2 posts 2 times the same?

and how do I solve this “Assuming disc_mutex is locked” ???

Best regards roburn

6

why are you still compiling Gobi driver?
It should not be used anymore

7

Hi Roburn,
did you get it to work? I have the same problem with a Lenovo X260 using Debian 12. It worked flawlessly using Debian 11.7.
If I do not get it to work I’ll have to downgrade back to 11.7 and test live versions of 12 every now and then to check if it gets fixed.

8

Hi jyi jyi, I have downloaded everything from your link, please tell me what I have to clean up, and please give me an installation guide, otherwise I am lost. Thank you very much for your help.
Sincerely roburn

9

Hello Paul, no at the moment it doesn’t work yet, but I also had the
same experience as you, with Debian 11.
When using Debian 11 again, then only as a virtual machine.
Best regards roburn

notifications@sierrawireless.discoursemail.com
Antwort an: Sierra Wireless Forum
<incoming+f8cd2808782bf6eb41b9fd13def57ddd@sierrawireless.discoursemail.com

10

Your latest log still compile the gobi driver

/var/lib/dkms/SierraLinuxQMIdrivers/S2.42N2.64

11

hello jyijyi,

ok sounds bad.
how can i purge it?

please, where can i get 4 an installations guide?

Best regards roburn

notifications@sierrawireless.discoursemail.com
Antwort an: Sierra Wireless Forum
<incoming+c03537f44c14e9b687667c67b79db8eb@sierrawireless.discoursemail.com

12

you are using kernel 6.1.0, you can check the following MBPL USB driver:

https://source.sierrawireless.com/resources/airprime/software/mbpl/mbpl-software-latest/#sthash.5K53774e.dpbs

There is document inside the link and there is readme file inside the USB driver folder

13

Hello jyijyi ,

thank you very much.

Best regards
roburn

notifications@sierrawireless.discoursemail.com
Antwort an: Sierra Wireless Forum
<incoming+c3d455de8a172057b122dd02d0ebfa8f@sierrawireless.discoursemail.com

14

Following the instructions benath by Bjørn I got the modem to work.

Paul

From: Bjørn Bürger bbu@penguin.de
To: 1004447@bugs.debian.org
Subject: Re: Bug#1004447: Acknowledgement (modemmanager: Sierra Wireless EM7455 stops working after upgrade to 1.18.4-1 (stays in FCC lock))
Date: Fri, 28 Jan 2022 20:49:27 +0100
Argh! Nevermind, just figured it out.

It’s actually documented in the original NEWS file, but it’s
not very obvious to the user, why suddenly the modem disappears.

This is the solution:

ln -sft /etc/ModemManager/fcc-unlock.d /usr/share/ModemManager/fcc-unlock.available.d/*

and it’s also documented quite nicely on the modemmanager.org
website. Maybe debian should add a prominent Warning, because
this will break modemmanager heavily for a lot of non-technical
people:

------------------------- cite from NEWS.gz ---------------------------

ModemManager 1.18.4

  • A new FCC unlock operation management via external scripts is
    introduced,
    which will avoid to automatically unlock FCC locked devices unless
    the user
    has configured the operation manually, or unless an official
    vendor-provided
    FCC unlock tool is found in the system.

    Please refer to the following URL for full details:
    FCC unlock procedure | ModemManager

    The following changes should be taken into account by distribution
    packagers:
    ** A set of FCC unlock scripts named as the specific vendor ‘vid’
    will be
    installed in ${datadir}/ModemManager/fcc-unlock.available.d.
    ** A set of symlinks is created named as the specific device
    ‘vid:pid’, and
    pointing to the per-vendor ‘vid’ files, in the same location inside
    ${datadir}.
    ** A new ${sysconfdir}/ModemManager/fcc-unlock.d directory is
    created, where
    users will manually install additional symlinks to the scripts
    shipped in
    ${datadir}.
    ** A new ${libdir}/ModemManager/fcc-unlock.d directory is created, where
    vendors will install their own official FCC unlock tools.
    ** Both fcc-unlock.d directories should be empty on a new install,
    and their
    contents (if any) should not be removed on ModemManager upgrades.

Have a nice weekend.
Bjørn