-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Here is how to do it without the acpi_call kernel module #34
Comments
Thank you for pointing this out! I also want to get it to work on a ThinkPad X1 Carbon 7 gen and Fedora 40. However, I could not find the line you're indicating. Where in the project is the line? |
See here: xmm7360-usb-modeswitch/xmm2usb Lines 37 to 38 in 224e60c
|
Wow, thanks for the quick response. I found it now. modprobe acpi_call || \
die "Could not load acpi_call module. Is it missing?" and modem_id=${path##*/}
read -r acpi_path < "${path}/firmware_node/path" || \
die "Cannot read firmware node path"
printf "Found XMM7360 modem at %s (%s)\n" "${modem_id}" "${acpi_path}" >&2 |
I disabled the references to Found XMM7360 modem at 0000:02:00.0 ()
Parent port is at 0000:00:1c.0
Disabling PCIe link...
pcilib: sysfs_write: write failed: Operation not permitted
OK! Did you have to take additional steps to get it to work? |
For me it just works, so I can only guess. According to this, one possible cause might be secure boot. Is secure boot enabled in your BIOS? It's disabled for me. |
Under Fedora 40 (kernel 6.9.6) running on a ThinkPad X1 Carbon (7th generation), I found that the use of
acpi_call
can be replaced by using the following line:instead of
Obviously, you can then also skip the lines with
modprobe acpi_call
and you don't need to extract the$acpi_path
.The text was updated successfully, but these errors were encountered: