ophub / amlogic-s9xxx-armbian

Support for Armbian in Amlogic, Rockchip and Allwinner boxes. Support a311d, s922x, s905x3, s905x2, s912, s905d, s905x, s905w, s905, s905l, rk3588, rk3568, rk3399, rk3328, h6, etc.
GNU General Public License v2.0
6.22k stars 1.99k forks source link

king3399 LTE module don't work #2565

Open TheRainstorm opened 2 months ago

TheRainstorm commented 2 months ago

Device Information | 设备信息

Armbian Version | 系统版本

Describe the bug | 问题描述 All issues will only remain open for one week to prioritize resolving them. After that period, they will be closed but can still continue to be discussed in the thread. 所有的问题都只保留一周的开启状态供重点关注解决,超时将关闭,但仍然可以长期继续跟帖讨论。

Please provide a detailed description of the issue and, if necessary, attach a screenshot. 详细描述问题,并在必要时附上屏幕截图。

I purchased a Quectel EC20 LTE module and plugged it into the mini-PCIe slot of king3399 board, but it doesn't seem to work. The lsusb command does not show the device.

Expected Behavior: The Quectel LTE modem should be detected and shown in lsusb:

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 2c7c:0125 Quectel Wireless Solutions Co., Ltd. EC25 LTE modem
Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

After recompiling the kernel using the patches from this repository (https://github.com/cyyself/king3399-kernel-patches), the module worked, indicating it's not a hardware issue. I suspect the problem might be with the device tree file (rk3399-king3399.dtb) in this repository.

However, I'm not familiar with reading or modifying device tree files. I would appreciate if anyone willing to fix this problem.

Manssizz commented 1 month ago

try this method in startup script or use crontab @reboot https://github.com/ophub/amlogic-s9xxx-armbian/issues/1225#issuecomment-1644265175

TheRainstorm commented 3 weeks ago

try this method in startup script or use crontab @reboot #1225 (comment)

Thanks, works like a charm! :D