BPi-R4 with BE14 OpenWrt 24.10.0 new installation has many errors and Wifi does not work properly

Matze · February 6, 2025, 11:43pm

Hello everyone,

After reading a lot and following the recommendation from the forum, I decided on the BPi-R4 with BE14. Unfortunately, I can't get the router to work properly. I did a new OpenWrt 24.10.0 installation using an SD card and transferred it to Nand and then to EMMC using Uboot. Unfortunately, a lot of errors are appearing in the kernel log and WiFi isn't working properly. What am I doing wrong?

root@Router-BPi-R4-Wifi7:~# ubus call system board
{
        "kernel": "6.6.73",
        "hostname": "Router-BPi-R4-Wifi7",
        "system": "ARMv8 Processor rev 0",
        "model": "Bananapi BPI-R4",
        "board_name": "bananapi,bpi-r4",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "24.10.0",
                "revision": "r28427-6df0e3d02a",
                "target": "mediatek/filogic",
                "description": "OpenWrt 24.10.0 r28427-6df0e3d02a",
                "builddate": "1738624177"
        }
}

type or paste code here[    0.028193] PCI: CLS 0 bytes, default 64
[    0.029080] workingset: timestamp_bits=46 max_order=20 bucket_order=0
[    0.032785] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.032791] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.053454] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    0.054503] mtk-xsphy soc:xphy@11e10000: failed to get ref_clk(id-1)
[    0.055139] mtk-pcie-gen3 11280000.pcie: host bridge /soc/pcie@11280000 ranges:
[    0.055158] mtk-pcie-gen3 11280000.pcie: Parsing ranges property...
[    0.055169] mtk-pcie-gen3 11280000.pcie:       IO 0x0020000000..0x00201fffff -> 0x0020000000
[    0.055183] mtk-pcie-gen3 11280000.pcie:      MEM 0x0020200000..0x0027ffffff -> 0x0020200000
[    0.055281] mtk-pcie-gen3 11290000.pcie: host bridge /soc/pcie@11290000 ranges:
[    0.055292] mtk-pcie-gen3 11290000.pcie: Parsing ranges property...
[    0.055301] mtk-pcie-gen3 11290000.pcie:       IO 0x0028000000..0x00281fffff -> 0x0028000000
[    0.055311] mtk-pcie-gen3 11290000.pcie:      MEM 0x0028200000..0x002fffffff -> 0x0028200000
[    0.055330] /soc/pcie@11290000: Failed to get clk index: 0 ret: -517
[    0.055338] mtk-pcie-gen3 11290000.pcie: failed to get clocks
[    0.055400] mtk-pcie-gen3 11300000.pcie: host bridge /soc/pcie@11300000 ranges:
[    0.055410] mtk-pcie-gen3 11300000.pcie: Parsing ranges property...
[    0.055420] mtk-pcie-gen3 11300000.pcie:       IO 0x0030000000..0x00301fffff -> 0x0030000000
[    0.055429] mtk-pcie-gen3 11300000.pcie:      MEM 0x0030200000..0x0037ffffff -> 0x0030200000
[    0.055445] /soc/pcie@11300000: Failed to get clk index: 0 ret: -517
[    0.055453] mtk-pcie-gen3 11300000.pcie: failed to get clocks
[    0.055527] mtk-pcie-gen3 11310000.pcie: host bridge /soc/pcie@11310000 ranges:
[    0.055537] mtk-pcie-gen3 11310000.pcie: Parsing ranges property...
[    0.055546] mtk-pcie-gen3 11310000.pcie:       IO 0x0038000000..0x00381fffff -> 0x0038000000
[    0.055555] mtk-pcie-gen3 11310000.pcie:      MEM 0x0038200000..0x003fffffff -> 0x0038200000
[    0.055577] /soc/pcie@11310000: Failed to get clk index: 0 ret: -517
[    0.055585] mtk-pcie-gen3 11310000.pcie: failed to get clocks

Is this normal?

[    1.152627] spi-nand spi0.0: Winbond SPI NAND was found.
[    1.157945] spi-nand spi0.0: 128 MiB, block size: 128 KiB, page size: 2048, OOB size: 64
[    1.166235] 2 fixed-partitions partitions found on MTD device spi0.0
[    1.172605] OF: Bad cell count for /soc/spi@11007000/spi_nand@0/partitions
[    1.179477] OF: Bad cell count for /soc/spi@11007000/spi_nand@0/partitions
[    1.186491] Creating 2 MTD partitions on "spi0.0":
[    1.191273] 0x000000000000-0x000000200000 : "bl2"
[    1.197452] 0x000000200000-0x000008000000 : "ubi"

[    2.360219] mtk-cpufreq mtk-cpufreq: failed to initialize dvfs info for cpu0

[    2.792443] mtk-pcie-gen3 11280000.pcie: PCIe link down, current LTSSM state: detect.quiet (0x1)
[    2.801241] mtk-pcie-gen3: probe of 11280000.pcie failed with error -110
[    2.808278] mtk-pcie-gen3 11290000.pcie: host bridge /soc/pcie@11290000 ranges:
[    2.815595] mtk-pcie-gen3 11290000.pcie: Parsing ranges property...
[    2.821860] mtk-pcie-gen3 11290000.pcie:       IO 0x0028000000..0x00281fffff -> 0x0028000000
[    2.830296] mtk-pcie-gen3 11290000.pcie:      MEM 0x0028200000..0x002fffffff -> 0x0028200000
[    3.172458] mtk-pcie-gen3 11290000.pcie: PCIe link down, current LTSSM state: detect.quiet (0x1)
[    3.181241] mtk-pcie-gen3: probe of 11290000.pcie failed with error -110
[    3.188127] mtk-pcie-gen3 11300000.pcie: host bridge /soc/pcie@11300000 ranges:
[    3.195437] mtk-pcie-gen3 11300000.pcie: Parsing ranges property...
[    3.201697] mtk-pcie-gen3 11300000.pcie:       IO 0x0030000000..0x00301fffff -> 0x0030000000
[    3.210130] mtk-pcie-gen3 11300000.pcie:      MEM 0x0030200000..0x0037ffffff -> 0x0030200000

[   12.525662] crypto-safexcel 15600000.crypto: can't request region for resource [mem 0x15600000-0x1577ffff]
[   12.535348] crypto-safexcel 15600000.crypto: failed to get resource
[   12.541604] crypto-safexcel: probe of 15600000.crypto failed with error -16

root@Router-BPi-R4-Wifi7:~# iw list|grep -i dbm
#                       * 2412.0 MHz [1] (6.0 dBm)
                        * 2417.0 MHz [2] (6.0 dBm)
                        * 2422.0 MHz [3] (6.0 dBm)
                        * 2427.0 MHz [4] (6.0 dBm)
                        * 2432.0 MHz [5] (6.0 dBm)
                        * 2437.0 MHz [6] (6.0 dBm)
                        * 2442.0 MHz [7] (6.0 dBm)
                        * 2447.0 MHz [8] (6.0 dBm)
                        * 2452.0 MHz [9] (6.0 dBm)
                        * 2457.0 MHz [10] (6.0 dBm)
                        * 2462.0 MHz [11] (6.0 dBm)
                        * 2467.0 MHz [12] (6.0 dBm)
                        * 2472.0 MHz [13] (6.0 dBm)
                        * 5180.0 MHz [36] (7.0 dBm)
                        * 5200.0 MHz [40] (7.0 dBm)
                        * 5220.0 MHz [44] (7.0 dBm)
                        * 5240.0 MHz [48] (7.0 dBm)
                        * 5260.0 MHz [52] (7.0 dBm) (radar detection)
                        * 5280.0 MHz [56] (7.0 dBm) (radar detection)
                        * 5300.0 MHz [60] (7.0 dBm) (radar detection)
                        * 5320.0 MHz [64] (7.0 dBm) (radar detection)
                        * 5500.0 MHz [100] (7.0 dBm) (radar detection)
                        * 5520.0 MHz [104] (7.0 dBm) (radar detection)
                        * 5540.0 MHz [108] (7.0 dBm) (radar detection)
                        * 5560.0 MHz [112] (7.0 dBm) (radar detection)
                        * 5580.0 MHz [116] (7.0 dBm) (radar detection)
                        * 5600.0 MHz [120] (7.0 dBm) (radar detection)
                        * 5620.0 MHz [124] (7.0 dBm) (radar detection)
                        * 5640.0 MHz [128] (7.0 dBm) (radar detection)
                        * 5660.0 MHz [132] (7.0 dBm) (radar detection)
                        * 5680.0 MHz [136] (7.0 dBm) (radar detection)
                        * 5700.0 MHz [140] (7.0 dBm) (radar detection)
                        * 5720.0 MHz [144] (7.0 dBm) (radar detection)
                        * 5745.0 MHz [149] (7.0 dBm)
                        * 5765.0 MHz [153] (7.0 dBm)
                        * 5785.0 MHz [157] (7.0 dBm)
                        * 5805.0 MHz [161] (7.0 dBm)
                        * 5825.0 MHz [165] (7.0 dBm)
                        * 5845.0 MHz [169] (7.0 dBm)
                        * 5865.0 MHz [173] (7.0 dBm)
                        * 5955.0 MHz [1] (23.0 dBm)
                        * 5975.0 MHz [5] (23.0 dBm)
                        * 5995.0 MHz [9] (23.0 dBm)
                        * 6015.0 MHz [13] (23.0 dBm)
                        * 6035.0 MHz [17] (23.0 dBm)
                        * 6055.0 MHz [21] (23.0 dBm)
                        * 6075.0 MHz [25] (23.0 dBm)
                        * 6095.0 MHz [29] (23.0 dBm)
                        * 6115.0 MHz [33] (23.0 dBm)
                        * 6135.0 MHz [37] (23.0 dBm)
                        * 6155.0 MHz [41] (23.0 dBm)
                        * 6175.0 MHz [45] (23.0 dBm)
                        * 6195.0 MHz [49] (23.0 dBm)
                        * 6215.0 MHz [53] (23.0 dBm)
                        * 6235.0 MHz [57] (23.0 dBm)
                        * 6255.0 MHz [61] (23.0 dBm)
                        * 6275.0 MHz [65] (23.0 dBm)
                        * 6295.0 MHz [69] (23.0 dBm)
                        * 6315.0 MHz [73] (23.0 dBm)
                        * 6335.0 MHz [77] (23.0 dBm)
                        * 6355.0 MHz [81] (23.0 dBm)
                        * 6375.0 MHz [85] (23.0 dBm)
                        * 6395.0 MHz [89] (23.0 dBm)
                        * 6415.0 MHz [93] (23.0 dBm)

Matze · February 8, 2025, 8:22pm

I had previously had a problem with the WiFi card or the associated drivers with the various v24.10.0-rc(x) versions. But since I'm a newbie when it comes to OpenWrt and in-depth router configuration, I was still experimenting when the final release 24.10.0 came out. Full of hope, I flashed the SD card and inserted it into the BPi-R4, but unfortunately I got the same error messages. The error message also seems to occur more frequently with other users. I think that the PCI problems are related to the other things.

Since I'm still new to the topic, I would also be happy to receive tips on how I might be able to find the cause or how I can search for it.

In the meantime I have tried to set up my own OpenWrt firmware for the BPi-R4, but there is something wrong with the feed from mediatek:

# ./scripts/feeds update -a && ./scripts/feeds install -a
WARNING: Makefile 'package/feeds/mtksdk/crypto-eip/Makefile' has a dependency on 'kmod-tops', which does not exist
WARNING: Makefile 'package/feeds/mtksdk/flowtable/Makefile' has a dependency on 'kmod-nf-flow-netlink', which does not exist
WARNING: Makefile 'package/feeds/mtksdk/pce/Makefile' has a dependency on 'kmod-mediatek_hnat', which does not exist
WARNING: Makefile 'package/feeds/mtksdk/tops-tool/Makefile' has a dependency on 'kmod-tops', which does not exist
WARNING: Makefile 'package/feeds/mtksdk/crypto-eip/Makefile' has a dependency on 'kmod-tops', which does not exist
WARNING: Makefile 'package/feeds/mtksdk/flowtable/Makefile' has a dependency on 'kmod-nf-flow-netlink', which does not exist
WARNING: Makefile 'package/feeds/mtksdk/pce/Makefile' has a dependency on 'kmod-mediatek_hnat', which does not exist
WARNING: Makefile 'package/feeds/mtksdk/tops-tool/Makefile' has a dependency on 'kmod-tops', which does not exist

What can I do to fix the missing dependencies? Or do I have to wait for mediatek to do some work?

AlanDias17 · February 8, 2025, 9:27pm

on Raspberry Pi4 new firmware is working well (except other modules like aria2). Wifi is also functional. Fall back to older version 25.05.5 until devs fix it

Matze · February 11, 2025, 10:13am

I find it a bit difficult to get through the various information, especially when some of the information is already out of date or shortened or incomplete because explicit knowledge is deliberately assumed. Sometimes you only notice later that information and instructions are no longer applicable because you are not yet familiar with the topic and do not know that something fundamental has changed in the meantime.

For example, I do not know how to integrate a different .dst/.dtsi file into Openwrt. I think that would require creating an Openwrt image in the build process.

I have found the following solutions to my problem and would like to learn how to implement something like that:

github.com/openwrt/openwrt

bpi-r4 doesn't recognize all PCI devices

opened 01:20AM - 02 Mar 24 UTC

mmisiewicz

target/mediatek bug Official Image SNAPSHOT

### Describe the bug Compared to the [Banana pi-provided image](https://wiki.ba…nana-pi.org/Banana_Pi_BPI-R4#Release_image) which is based on kernel 5.4.246, the most recent snapshot of openwrt fails to detect all the PCI devices on. I'm specifically trying to get a T99W175 b-key modem working. On the sinovoip provided build, the modem is detected, but not on snapshot openwrt. There are some suggestive errors in the kernel log: ``` [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd090] [ 0.000000] Linux version 6.1.79 (builder@buildhost) (aarch64-openwrt-linux-musl-gcc (OpenWrt GCC 12.3.0 r25361-a86ff06d2e) 12.3.0, GNU ld (GNU Binutils) 2.40.0) #0 SMP Fri Mar 1 01:42:36 2024 [ 0.000000] Machine model: Bananapi BPI-R4 ... [ 0.042510] mtk-xsphy soc:xphy@11e10000: failed to get ref_clk(id-1) [ 0.043034] mtk-pcie-gen3 11280000.pcie: host bridge /soc/pcie@11280000 ranges: [ 0.043054] mtk-pcie-gen3 11280000.pcie: Parsing ranges property... [ 0.043065] mtk-pcie-gen3 11280000.pcie: IO 0x0020000000..0x00201fffff -> 0x0020000000 [ 0.043078] mtk-pcie-gen3 11280000.pcie: MEM 0x0020200000..0x0027ffffff -> 0x0020200000 [ 0.043174] mtk-pcie-gen3 11290000.pcie: host bridge /soc/pcie@11290000 ranges: [ 0.043185] mtk-pcie-gen3 11290000.pcie: Parsing ranges property... [ 0.043194] mtk-pcie-gen3 11290000.pcie: IO 0x0028000000..0x00281fffff -> 0x0028000000 [ 0.043204] mtk-pcie-gen3 11290000.pcie: MEM 0x0028200000..0x002fffffff -> 0x0028200000 [ 0.043223] /soc/pcie@11290000: Failed to get clk index: 0 ret: -517 [ 0.043232] mtk-pcie-gen3 11290000.pcie: failed to get clocks [ 0.043294] mtk-pcie-gen3 11300000.pcie: host bridge /soc/pcie@11300000 ranges: [ 0.043304] mtk-pcie-gen3 11300000.pcie: Parsing ranges property... [ 0.043313] mtk-pcie-gen3 11300000.pcie: IO 0x0030000000..0x00301fffff -> 0x0030000000 [ 0.043322] mtk-pcie-gen3 11300000.pcie: MEM 0x0030200000..0x0037ffffff -> 0x0030200000 [ 0.043337] /soc/pcie@11300000: Failed to get clk index: 0 ret: -517 [ 0.043345] mtk-pcie-gen3 11300000.pcie: failed to get clocks [ 0.043418] mtk-pcie-gen3 11310000.pcie: host bridge /soc/pcie@11310000 ranges: [ 0.043428] mtk-pcie-gen3 11310000.pcie: Parsing ranges property... [ 0.043436] mtk-pcie-gen3 11310000.pcie: IO 0x0038000000..0x00381fffff -> 0x0038000000 [ 0.043445] mtk-pcie-gen3 11310000.pcie: MEM 0x0038200000..0x003fffffff -> 0x0038200000 [ 0.043461] /soc/pcie@11310000: Failed to get clk index: 0 ret: -517 ... [ 2.264470] mtk-pcie-gen3 11280000.pcie: host bridge /soc/pcie@11280000 ranges: [ 2.271809] mtk-pcie-gen3 11280000.pcie: Parsing ranges property... [ 2.278074] mtk-pcie-gen3 11280000.pcie: IO 0x0020000000..0x00201fffff -> 0x0020000000 [ 2.285724] mtk-msdc 11230000.mmc: Final PAD_DS_TUNE: 0x13014 [ 2.286502] mtk-pcie-gen3 11280000.pcie: MEM 0x0020200000..0x0027ffffff -> 0x0020200000 ... [ 2.637311] mtk-pcie-gen3 11280000.pcie: PCIe link down, current LTSSM state: detect.quiet (0x0) [ 2.646106] mtk-pcie-gen3: probe of 11280000.pcie failed with error -110 [ 2.653141] mtk-pcie-gen3 11290000.pcie: host bridge /soc/pcie@11290000 ranges: [ 2.660455] mtk-pcie-gen3 11290000.pcie: Parsing ranges property... [ 2.666719] mtk-pcie-gen3 11290000.pcie: IO 0x0028000000..0x00281fffff -> 0x0028000000 [ 2.675154] mtk-pcie-gen3 11290000.pcie: MEM 0x0028200000..0x002fffffff -> 0x0028200000 [ 3.017310] mtk-pcie-gen3 11290000.pcie: PCIe link down, current LTSSM state: detect.quiet (0x1) [ 3.026086] mtk-pcie-gen3: probe of 11290000.pcie failed with error -110 [ 3.032937] mtk-pcie-gen3 11300000.pcie: host bridge /soc/pcie@11300000 ranges: [ 3.040244] mtk-pcie-gen3 11300000.pcie: Parsing ranges property... [ 3.046503] mtk-pcie-gen3 11300000.pcie: IO 0x0030000000..0x00301fffff -> 0x0030000000 [ 3.054938] mtk-pcie-gen3 11300000.pcie: MEM 0x0030200000..0x0037ffffff -> 0x0030200000 [ 3.397313] mtk-pcie-gen3 11300000.pcie: PCIe link down, current LTSSM state: detect.quiet (0x1) [ 3.406088] mtk-pcie-gen3: probe of 11300000.pcie failed with error -110 [ 3.412945] mtk-pcie-gen3 11310000.pcie: host bridge /soc/pcie@11310000 ranges: [ 3.420253] mtk-pcie-gen3 11310000.pcie: Parsing ranges property... [ 3.426511] mtk-pcie-gen3 11310000.pcie: IO 0x0038000000..0x00381fffff -> 0x0038000000 [ 3.434942] mtk-pcie-gen3 11310000.pcie: MEM 0x0038200000..0x003fffffff -> 0x0038200000 [ 3.707436] mtk-pcie-gen3 11310000.pcie: set IO trans window[0]: cpu_addr = 0x38000000, pci_addr = 0x38000000, size = 0x200000 [ 3.718816] mtk-pcie-gen3 11310000.pcie: set MEM trans window[1]: cpu_addr = 0x38200000, pci_addr = 0x38200000, size = 0x200000 [ 3.730281] mtk-pcie-gen3 11310000.pcie: set MEM trans window[2]: cpu_addr = 0x38400000, pci_addr = 0x38400000, size = 0x400000 [ 3.741743] mtk-pcie-gen3 11310000.pcie: set MEM trans window[3]: cpu_addr = 0x38800000, pci_addr = 0x38800000, size = 0x800000 [ 3.753206] mtk-pcie-gen3 11310000.pcie: set MEM trans window[4]: cpu_addr = 0x39000000, pci_addr = 0x39000000, size = 0x1000000 [ 3.764754] mtk-pcie-gen3 11310000.pcie: set MEM trans window[5]: cpu_addr = 0x3a000000, pci_addr = 0x3a000000, size = 0x2000000 [ 3.776303] mtk-pcie-gen3 11310000.pcie: set MEM trans window[6]: cpu_addr = 0x3c000000, pci_addr = 0x3c000000, size = 0x4000000 [ 3.787965] mtk-pcie-gen3 11310000.pcie: PCI host bridge to bus 0001:00 [ 3.794568] pci_bus 0001:00: root bus resource [bus 00-ff] [ 3.800048] pci_bus 0001:00: root bus resource [io 0x600000-0x7fffff] (bus address [0x38000000-0x381fffff]) [ 3.809863] pci_bus 0001:00: root bus resource [mem 0x38200000-0x3fffffff] [ 3.816724] pci_bus 0001:00: scanning bus [ 3.820747] pci 0001:00:00.0: [14c3:7988] type 01 class 0x060400 [ 3.826754] pci 0001:00:00.0: reg 0x10: [mem 0x00000000-0x00007fff 64bit] [ 3.833593] pci 0001:00:00.0: PME# supported from D0 D3hot D3cold [ 3.839680] pci 0001:00:00.0: PME# disabled [ 3.845052] pci_bus 0001:00: fixups for bus [ 3.849233] pci 0001:00:00.0: scanning [bus 00-00] behind bridge, pass 0 [ 3.855922] pci 0001:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 3.863919] pci 0001:00:00.0: scanning [bus 00-00] behind bridge, pass 1 [ 3.870661] pci_bus 0001:01: scanning bus [ 3.874682] pci 0001:01:00.0: [17cb:1103] type 00 class 0x028000 [ 3.880698] pci 0001:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit] [ 3.887594] pci 0001:01:00.0: PME# supported from D0 D3hot D3cold [ 3.893679] pci 0001:01:00.0: PME# disabled [ 3.927331] pci_bus 0001:01: fixups for bus [ 3.931504] pci_bus 0001:01: bus scan returning with max=01 [ 3.937063] pci_bus 0001:01: busn_res: [bus 01-ff] end is updated to 01 [ 3.943673] pci_bus 0001:00: bus scan returning with max=01 [ 3.949246] pci 0001:00:00.0: BAR 8: assigned [mem 0x38200000-0x383fffff] [ 3.956022] pci 0001:00:00.0: BAR 0: assigned [mem 0x38400000-0x38407fff 64bit] [ 3.963328] pci 0001:01:00.0: BAR 0: assigned [mem 0x38200000-0x383fffff 64bit] [ 3.970635] pci 0001:00:00.0: PCI bridge to [bus 01] [ 3.975590] pci 0001:00:00.0: bridge window [mem 0x38200000-0x383fffff] [ 3.982378] pci 0001:00:00.0: Max Payload Size set to 256/ 256 (was 128), Max Read Rq 256 [ 3.990818] pci 0001:01:00.0: Max Payload Size set to 128/ 128 (was 128), Max Read Rq 128 [ 3.999319] pcieport 0001:00:00.0: assign IRQ: got 112 [ 4.004450] pcieport 0001:00:00.0: enabling device (0000 -> 0002) [ 4.010547] pcieport 0001:00:00.0: enabling bus mastering [ 4.016199] mtk-pcie-gen3 11310000.pcie: msi#0x0 address_hi 0x0 address_lo 0x11310c00 data 0 [ 4.024635] mtk-pcie-gen3 11310000.pcie: msi#0x1 address_hi 0x0 address_lo 0x11310c00 data 1 [ 4.033062] mtk-pcie-gen3 11310000.pcie: msi#0x2 address_hi 0x0 address_lo 0x11310c00 data 2 [ 4.041488] mtk-pcie-gen3 11310000.pcie: msi#0x3 address_hi 0x0 address_lo 0x11310c00 data 3 [ 4.049917] mtk-pcie-gen3 11310000.pcie: msi#0x4 address_hi 0x0 address_lo 0x11310c00 data 4 [ 4.058342] mtk-pcie-gen3 11310000.pcie: msi#0x5 address_hi 0x0 address_lo 0x11310c00 data 5 [ 4.066766] mtk-pcie-gen3 11310000.pcie: msi#0x6 address_hi 0x0 address_lo 0x11310c00 data 6 [ 4.075191] mtk-pcie-gen3 11310000.pcie: msi#0x7 address_hi 0x0 address_lo 0x11310c00 data 7 [ 4.083617] mtk-pcie-gen3 11310000.pcie: msi#0x8 address_hi 0x0 address_lo 0x11310c00 data 8 [ 4.092042] mtk-pcie-gen3 11310000.pcie: msi#0x9 address_hi 0x0 address_lo 0x11310c00 data 9 [ 4.100471] mtk-pcie-gen3 11310000.pcie: msi#0xa address_hi 0x0 address_lo 0x11310c00 data 10 [ 4.108984] mtk-pcie-gen3 11310000.pcie: msi#0xb address_hi 0x0 address_lo 0x11310c00 data 11 [ 4.117496] mtk-pcie-gen3 11310000.pcie: msi#0xc address_hi 0x0 address_lo 0x11310c00 data 12 [ 4.126005] mtk-pcie-gen3 11310000.pcie: msi#0xd address_hi 0x0 address_lo 0x11310c00 data 13 [ 4.134517] mtk-pcie-gen3 11310000.pcie: msi#0xe address_hi 0x0 address_lo 0x11310c00 data 14 [ 4.143029] mtk-pcie-gen3 11310000.pcie: msi#0xf address_hi 0x0 address_lo 0x11310c00 data 15 [ 4.151541] mtk-pcie-gen3 11310000.pcie: msi#0x10 address_hi 0x0 address_lo 0x11310c00 data 16 [ 4.160140] mtk-pcie-gen3 11310000.pcie: msi#0x11 address_hi 0x0 address_lo 0x11310c00 data 17 [ 4.168742] mtk-pcie-gen3 11310000.pcie: msi#0x12 address_hi 0x0 address_lo 0x11310c00 data 18 [ 4.177341] mtk-pcie-gen3 11310000.pcie: msi#0x13 address_hi 0x0 address_lo 0x11310c00 data 19 [ 4.185937] mtk-pcie-gen3 11310000.pcie: msi#0x14 address_hi 0x0 address_lo 0x11310c00 data 20 [ 4.194536] mtk-pcie-gen3 11310000.pcie: msi#0x15 address_hi 0x0 address_lo 0x11310c00 data 21 [ 4.203134] mtk-pcie-gen3 11310000.pcie: msi#0x16 address_hi 0x0 address_lo 0x11310c00 data 22 [ 4.211733] mtk-pcie-gen3 11310000.pcie: msi#0x17 address_hi 0x0 address_lo 0x11310c00 data 23 [ 4.220332] mtk-pcie-gen3 11310000.pcie: msi#0x18 address_hi 0x0 address_lo 0x11310c00 data 24 [ 4.228931] mtk-pcie-gen3 11310000.pcie: msi#0x19 address_hi 0x0 address_lo 0x11310c00 data 25 [ 4.237530] mtk-pcie-gen3 11310000.pcie: msi#0x1a address_hi 0x0 address_lo 0x11310c00 data 26 [ 4.246127] mtk-pcie-gen3 11310000.pcie: msi#0x1b address_hi 0x0 address_lo 0x11310c00 data 27 [ 4.254726] mtk-pcie-gen3 11310000.pcie: msi#0x1c address_hi 0x0 address_lo 0x11310c00 data 28 [ 4.263325] mtk-pcie-gen3 11310000.pcie: msi#0x1d address_hi 0x0 address_lo 0x11310c00 data 29 [ 4.271924] mtk-pcie-gen3 11310000.pcie: msi#0x1e address_hi 0x0 address_lo 0x11310c00 data 30 [ 4.280522] mtk-pcie-gen3 11310000.pcie: msi#0x1f address_hi 0x0 address_lo 0x11310c00 data 31 [ 4.289419] mtk-pcie-gen3 11310000.pcie: msi#0x0 address_hi 0x0 address_lo 0x11310c00 data 0 [ 4.297910] pcieport 0001:00:00.0: PME: Signaling with IRQ 113 [ 4.303836] pcieport 0001:00:00.0: AER: enabled with IRQ 113 [ 4.309523] pcieport 0001:00:00.0: saving config space at offset 0x0 (reading 0x798814c3) [ 4.317692] pcieport 0001:00:00.0: saving config space at offset 0x4 (reading 0x100406) [ 4.325681] pcieport 0001:00:00.0: saving config space at offset 0x8 (reading 0x6040001) [ 4.333760] pcieport 0001:00:00.0: saving config space at offset 0xc (reading 0x10000) [ 4.341664] pcieport 0001:00:00.0: saving config space at offset 0x10 (reading 0x38400004) [ 4.349916] pcieport 0001:00:00.0: saving config space at offset 0x14 (reading 0x0) [ 4.357560] pcieport 0001:00:00.0: saving config space at offset 0x18 (reading 0x10100) [ 4.365549] pcieport 0001:00:00.0: saving config space at offset 0x1c (reading 0x1f1) [ 4.373367] pcieport 0001:00:00.0: saving config space at offset 0x20 (reading 0x38303820) [ 4.381618] pcieport 0001:00:00.0: saving config space at offset 0x24 (reading 0x1fff1) [ 4.389608] pcieport 0001:00:00.0: saving config space at offset 0x28 (reading 0x0) [ 4.397250] pcieport 0001:00:00.0: saving config space at offset 0x2c (reading 0x0) [ 4.404894] pcieport 0001:00:00.0: saving config space at offset 0x30 (reading 0x0) [ 4.412541] pcieport 0001:00:00.0: saving config space at offset 0x34 (reading 0x80) [ 4.420273] pcieport 0001:00:00.0: saving config space at offset 0x38 (reading 0x0) [ 4.427917] pcieport 0001:00:00.0: saving config space at offset 0x3c (reading 0x20170) ``` The device I'm expecting to see shows this output in lspci when booting on the 5.4 kernel: ``` 0003:01:00.0 Unassigned class [ff00]: Qualcomm Device 0306 Subsystem: Qualcomm Device 010c Flags: fast devsel Memory at 20200000 (64-bit, non-prefetchable) [disabled] [size=4K] Memory at 20201000 (64-bit, non-prefetchable) [disabled] [size=4K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/32 Maskable+ 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [148] Secondary PCI Express Capabilities: [168] Physical Layer 16.0 GT/s <?> Capabilities: [18c] Lane Margining at the Receiver <?> Capabilities: [19c] Transaction Processing Hints Capabilities: [228] Latency Tolerance Reporting Capabilities: [230] L1 PM Substates Capabilities: [240] Data Link Feature <?> ``` Those errors mentioning "probe failed" with code -110 seem like they might be related. This is from today's (2024-03-01) nightly downloaded directly from downloads.openwrt.org. I'm curious if there's any fix for this issue. ### OpenWrt version r25361-a86ff06d2e ### OpenWrt release SNAPSHOT ### OpenWrt target/subtarget mediatek/filogic ### Device Bananapi BPI-R4 ### Image kind Official downloaded image ### Steps to reproduce Put a PCIe card in the b key M2 slot, boot up. ### Actual behaviour Card not detected ### Expected behaviour Card is detected (and then drivers load) ### Additional info _No response_ ### Diffconfig _No response_ ### Terms - [X] I am reporting an issue for OpenWrt, not an unsupported fork.

github.com/frank-w/u-boot

clk: mediatek: mt7988: fix clocks for 2nd PCIe port like done in linux

committed 02:55PM - 12 Oct 24 UTC

frank-w

+1 -1

Due to what seems to be an undocumented oddity in MediaTek's MT7988 SoC design t…he CLK_INFRA_PCIE_PERI_26M_CK_P2 clock requires CLK_INFRA_PCIE_PERI_26M_CK_P3 to be enabled. This currently leads to PCIe port 2 not working in Linux. Reflect the apparent relationship in the clk driver to make sure PCIe port 2 of the MT7988 SoC works. https://patchwork.kernel.org/project/linux-mediatek/patch/1da2506a51f970706bf4ec9509dd04e0471065e5.1710367453.git.daniel@makrotopia.org/ Fixes: 421436981a22 ("clk: mediatek: add clock driver support for MediaTek MT7988 SoC") Suggested-by: Sam Shih <sam.shih@mediatek.com> Signed-off-by: Daniel Golle <daniel@makrotopia.org> Signed-off-by: Frank Wunderlich <frank-w@public-files.de>

In any case, I'll stay on the ball and if I achieve any success, I'll be happy to report back here.

madejackson · February 14, 2025, 10:17am

Hey, I'm also in the process of tuning my BPI-R4.

I have it running with 24.10.0 right now and it works well with the firmware from the firmware selector: https://firmware-selector.openwrt.org/?version=24.10.0&target=mediatek%2Ffilogic&id=bananapi_bpi-r4

One thing to mention is: The firmware selector fails to build with wpad, so I switched to hostapd for the time being.

Here's the built packages I am using:

Defaults (without wpad):

base-files ca-bundle dnsmasq dropbear firewall4 fitblk fstools kmod-crypto-hw-safexcel kmod-gpio-button-hotplug kmod-leds-gpio kmod-nft-offload kmod-phy-aquantia libc libgcc libustream-mbedtls logd mtd netifd nftables odhcp6c odhcpd-ipv6only opkg ppp ppp-mod-pppoe procd-ujail uboot-envtools uci uclient-fetch urandom-seed urngd hostapd-basic-mbedtls kmod-hwmon-pwmfan kmod-i2c-mux-pca954x kmod-eeprom-at24 kmod-mt7996-firmware kmod-mt7996-233-firmware kmod-rtc-pcf8563 kmod-sfp kmod-usb3 e2fsprogs f2fsck mkf2fs mt7988-wo-firmware luci

Additional Packages:

tailscale luci-ssl cfdisk kmod-fs-btrfs btrfs-progs block-mount resize2fs losetup lsblk docker dockerd luci-app-dockerman luci-app-uhttpd attendedsysupgrade-common dbus kmod-macvlan kmod-serial-8250 kmod-usb-serial kmod-usb-serial-ftdi kmod-usb-uhci libacl libdaemon libdbus libexpat libpopt0 lua-rs232 luci-app-attendedsysupgrade rpcd-mod-rpcsys rsync telnet-bsd

Beware, You may not need those packages. I'm running openwrt from 128MB NAND and using the 8GB eMMC as external btrfs mount as a docker host / cosmos server: https://discord.com/channels/1083875833824944188/1326911884020158464/1327038464516030466
Invite: https://discord.gg/PwMWwsrwHA

edit: nvm, the builder seems to be broken. Now the package kmod-mt7996-firmware is failing. Not sure how to fix that.

edit2: Building with SNAPSHOT works.

LilRedDog · February 14, 2025, 4:07pm

There are known intermittent issues generating custom images using the online image generator (firmware selector and sysupgrade servers). This affects Attended Sysupgrade (ASU), OWUT (OpenWrt Upgrade Tool), and the firmware-selector custom image tool. See [this thread](https://forum.openwrt.org/t/notice-problems-with-custom-firmware-image-creation/224829) for more details.

Please do not open new threads on this topic as it has already been discussed in numerous threads (with the same answers each time).

Matze · February 15, 2025, 7:34am

Thanks for the tips. The firmware selector with wpad-basic-mbedtls and also with hostapd-basic-mbedtls in the final release 24.10.0 doesn't work completely for me either. But I'll test it again and flash it onto an SD card and try out the system from the firmware selector.

The missing dependencies in the mtksdk feed have apparently been fixed, as I no longer had any errors with the MTK feeds. During my attempts to analyze the error, I found an interesting guide from Mediatek, which I am currently trying to follow: https://git01.mediatek.com/plugins/gitiles/openwrt/feeds/mtk-openwrt-feeds/+/master/autobuild/unified/

So I started building a u-boot (>=v2025.01) with arm-trusted firmware from https://github.com/mtk-openwrt for the BPi-R4. The build was successful so far and I am currently trying to flash it correctly as a package with OpenWrt or to get it to work on the BPi-R4.

I am currently facing the problem with dynamic MAC addresses:

F0: 102B 0000
FA: 1042 0000
FA: 1042 0000 [0200]
F9: 1041 0000
F3: 1001 0000 [0200]
F3: 1001 0000
F6: 380E 5800
F5: 0000 0000
V0: 0000 0000 [0001]
00: 0000 0000
BP: 0600 0041 [0000]
G0: 1190 0000
EC: 0000 0000 [3000]
MK: 0000 0000 [0000]
T0: 0000 01FF [0101]
Jump to BL

NOTICE:  BL2: v2.12.0(release):v2.4-rc0-8168-ge09077068
NOTICE:  BL2: Built : 02:23:34, Feb 14 2025
NOTICE:  WDT: Cold boot
NOTICE:  WDT: disabled
NOTICE:  CPU: MT7988
NOTICE:  EMI: Using DDR unknown settings
NOTICE:  EMI: Detected DRAM size: 4096 MB
NOTICE:  EMI: complex R/W mem test passed
NOTICE:  LVTS: Enable thermal HW reset
NOTICE:  BL2: Booting BL31
NOTICE:  BL31: v2.12.0(release):v2.4-rc0-8168-ge09077068
NOTICE:  BL31: Built : 02:23:39, Feb 14 2025
serial_mtk serial@11000000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19

U-Boot 2025.04-rc2-g70e5cec9ab65 (Feb 14 2025 - 01:52:19 -0500)

CPU:   MediaTek MT7988
Model: Bananapi BPI-R4
DRAM:  4 GiB
serial_mtk serial@11000000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-22
Core:  114 devices, 17 uclasses, devicetree: separate
MMC:
Loading Environment from nowhere... OK
In:    serial@11000000
Out:   serial@11000000
Err:   serial@11000000
Net:   MediaTek MT7988 built-in switch

Warning: ethernet@15100000 (eth2) using random MAC address - 7e:6b:f7:12:a4:7e
eth2: ethernet@15100000

The cosmos server sounds exciting. I will take a closer look at it. After the router upgrade, I planned to tackle my NAS and set up TrueNAS on my previous workstation and connect it via NVMe-of.

LilRedDog · February 15, 2025, 3:57pm


#### MAC Address more info

Locally administered addresses (LAA): the address is assigned to a device by a network administrator, overriding the burned-in address.

Note

It's also be a randomized MAC. Media Access Control (MAC) address randomization is a privacy technique whereby mobile devices rotate through random hardware addresses in order to prevent observers from singling out their traffic or physical location from other nearby devices.

Type of transmission: Unicast

Wire**shark**:

If you do not understand octets tell us.

What are you using eth2 for? Because you are using a local MAC address or a MAC intended to not be used to connect but to allow functions without being tracked; if you are using on the wan, why? If on the lan, again, why?

Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:

Remember to redact passwords, MAC addresses and any public IP addresses you may have:
ubus call system board
cat /etc/config/network
cat /etc/config/dhcp

Matze · February 16, 2025, 9:45am

ubus call system board (from OpenWrt firmware selector image v24.10.0):
This image has problems with the clocks, the PCIe slots and the BE14 Wifi card connected to them.

Matze:

root@Router-BPi-R4-Wifi7:~# ubus call system board
{
        "kernel": "6.6.73",
        "hostname": "Router-BPi-R4-Wifi7",
        "system": "ARMv8 Processor rev 0",
        "model": "Bananapi BPI-R4",
        "board_name": "bananapi,bpi-r4",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "24.10.0",
                "revision": "r28427-6df0e3d02a",
                "target": "mediatek/filogic",
                "description": "OpenWrt 24.10.0 r28427-6df0e3d02a",
                "builddate": "1738624177"
        }
}

My network configuration is mostly the standard OpenWrt configuration.
cat /etc/config/network

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd15:4042:3402::/48'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'lan1'
        list ports 'lan2'
        list ports 'lan3'
        list ports 'eth1'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'

config device
        option name 'br-wan'
        option type 'bridge'
        list ports 'wan'
        list ports 'eth2'

config device
        option name 'wan'
        option macaddr 'ea:9a:ad:32:41:aa'

config device
        option name 'eth2'
        option macaddr 'ea:9a:ad:32:41:aa'

config interface 'wan'
        option device 'br-wan'
        option proto 'dhcp'

config interface 'wan6'
        option device 'br-wan'
        option proto 'dhcpv6'

cat /etc/config/dhcp

config dnsmasq
        option domainneeded '1'
        option localise_queries '1'
        option rebind_protection '1'
        option rebind_localhost '1'
        option local '/lan/'
        option domain 'lan'
        option expandhosts '1'
        option cachesize '1000'
        option authoritative '1'
        option readethers '1'
        option leasefile '/tmp/dhcp.leases'
        option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
        option localservice '1'
        option ednspacket_max '1232'

config dhcp 'wan'
        option interface 'wan'
        option ignore '1'

config dhcp 'lan'
        option interface 'lan'
        option start '2'
        option limit '250'
        option leasetime '12h'
        option dhcpv4 'server'
        option dhcpv6 'server'
        option ra 'server'
        list ra_flags 'managed-config'
        list ra_flags 'other-config'
        option ra_default '1'

config odhcpd 'odhcpd'
        option maindhcp '0'
        option leasefile '/tmp/hosts/odhcpd'
        option leasetrigger '/usr/sbin/odhcpd-update'
        option loglevel '4'

config host
        option name 'fritzbox-7590-dect'
        list mac '3C:2F:A6:5F:C8:E3'
        option ip '192.168.1.2'
        option leasetime '12h'

...

Matze · February 16, 2025, 9:52am

Due to the problems with the clocks, the PCIe slots and the BE14 WiFi card connected to them, I tried to create a new Openwrt build with the patches myself. But I think I have a problem with my build finding the OpenWrt boot partition in U-Boot.

LilRedDog · February 16, 2025, 5:51pm

What setting, are you using, is generating random MAC addresses on your wan?
Cloning a MAC on your WAN, because your IP has locked your modem to another device, is one thing but this makes no sense.

Matze · February 16, 2025, 7:41pm

The random Mac address is something from U-Boot. I think, but no longer, that this is why the system won't boot up any further.

The network settings regarding wan (RJ45 wan) and eth2 (SFP+ wan) came from OpenWrt as default with the following bridge configuration:

config device
	option name 'br-wan'
	option type 'bridge'
	list ports 'wan'
	list ports 'eth2'

KFO · February 16, 2025, 7:58pm

Try Mr @woziwrt image its a great better than Official OpenWRT images (snapshot or Stable 24.10) where they are giving you a bad performance to be honest .

one of major issues not solved on Offical OpenWRT BPI-R4 (bottleneck CPUs ) I reported it before 8 months not solved until to now (I opened the ticket before 8 month on Openwrt Forum & github (Not Solved until to now ))....when you are doing speed test or downloading the large files you will face speeds limitations

also I'm facing wifi speed limitations on devices that has wifi QUALCOMM chips ... I reported this issue on OpenWRT forum before 4 months and I opened the ticket before a month on Openwrt github (Not Solved until to now )

So you will find a lot of issue not solved with Official OpenWRT and some of them solved .

but with image SDK that developed by woziwrt ( I didn't face these issues)

one issue I faced it the speeds are not stables always on WIFI but on ethernet they are 10/10

Matze · February 24, 2025, 2:37pm

I first compiled the version using ./build-mlo-beta2-version.sh following the instructions on Github (https://github.com/woziwrt/bpi-r4-mtk). I also had the PCI errors there, so I turned my attention to the version using ./build-mlo-beta2_ext_upd-1.2-version.sh. During the build time, I tried to build a version with Openwrt 24.10 again, but depending on the package configuration, you always run into build errors due to the missing dependencies from Mediatek. So I flashed the Woziwrt build, which had been completed in the meantime, onto an SD card and tried it out. The PCI errors are still there, just like in the versions of Openwrt in v24.10 and in the current snapshot. For me, WiFi worked in the various Openrt images, but only in Woziwrt was the maximum transmit power across all frequencies from 2.4GHz, 5GHz up to 6GHz at 27 dBm. This extends the range considerably and for me even makes it unnecessary to consider WiFi mesh.

lspci laut https://docs.banana-pi.org/en/BPI-R4/GettingStarted_BPI-R4

# lspic
0002:00:00.0 PCI bridge: MEDIATEK Corp. Device 7988 (rev 01)
0002:01:00.0 Non-Volatile memory controller: KIOXIA Corporation Device 0001
0004:00:00.0 Unclassified device [0002]: MEDIATEK Corp. Device 7981

lspci (with Woziwrt build-mlo-beta2_ext_upd-1.2-version)

# lspic
00:00.0 Class 0604: 14c3:7988
01:00.0 Class 0280: 14c3:7990
00:00.0 Class 0604: 14c3:7988
01:00.0 Class 0280: 14c3:7991

Is that still correct? And the BE14 card or the PCIE's are now working properly?

I noticed that the Woziwrt image does not have /sys/class/thermal/thermal_zone0, but rather /sys/class/thermal/cooling_device0. There I can turn the fan down using

# echo 2 > cur_state

but after every restart it runs at max again with cur_state at 3. How did you set that up? Or do you know how to set it?

I discovered the following about the fan, but I don't know how to adjust the fan speed to specific temperatures.

# cat /sys/devices/platform/pwm-fan/hwmon/hwmon0/name
pwmfan
# cat /sys/devices/platform/pwm-fan/hwmon/hwmon0/pwm1
255
# cat /sys/devices/platform/pwm-fan/hwmon/hwmon0/pwm1_enable
1
# cat /sys/devices/platform/pwm-fan/hwmon/hwmon0/uevent
OF_NAME=pwm-fan
OF_FULLNAME=/pwm-fan
OF_COMPATIBLE_0=pwm-fan
OF_COMPATIBLE_N=1

Matze · February 25, 2025, 11:14am

The shortened output was probably due to "pciutiles" not being installed or not being installed completely. Now I get the following output:

# lspci
0000:00:00.0 PCI bridge: MEDIATEK Corp. Device 7988 (rev 01)
0000:01:00.0 Network controller: MEDIATEK Corp. Device 7990
0001:00:00.0 PCI bridge: MEDIATEK Corp. Device 7988 (rev 01)
0001:01:00.0 Network controller: MEDIATEK Corp. Device 7991

# lspci -k
0000:00:00.0 PCI bridge: MEDIATEK Corp. Device 7988 (rev 01)
        Kernel driver in use: pcieport
lspci: Unable to load libkmod resources: error -2
0000:01:00.0 Network controller: MEDIATEK Corp. Device 7990
        Subsystem: MEDIATEK Corp. Device 6639
        Kernel driver in use: mt7996e
0001:00:00.0 PCI bridge: MEDIATEK Corp. Device 7988 (rev 01)
        Kernel driver in use: pcieport
0001:01:00.0 Network controller: MEDIATEK Corp. Device 7991
        Subsystem: MEDIATEK Corp. Device 6639
        Kernel driver in use: mt7996e_hif

I see this error: lspci: Unable to load libkmod resources: error -2

# lspci -v
0000:00:00.0 PCI bridge: MEDIATEK Corp. Device 7988 (rev 01) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 122
        Memory at 30500000 (64-bit, non-prefetchable) [size=32K]
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: [disabled] [32-bit]
        Memory behind bridge: 30400000-304fffff [size=1M] [32-bit]
        Prefetchable memory behind bridge: 30200000-303fffff [size=2M] [32-bit]
        Capabilities: [80] Express Root Port (Slot-), IntMsgNum 0
        Capabilities: [e0] MSI: Enable+ Count=1/32 Maskable+ 64bit+
        Capabilities: [f8] Power Management version 3
        Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?>
        Capabilities: [110] L1 PM Substates
        Capabilities: [200] Advanced Error Reporting
        Capabilities: [300] Secondary PCI Express
        Kernel driver in use: pcieport
lspci: Unable to load libkmod resources: error -2

0000:01:00.0 Network controller: MEDIATEK Corp. Device 7990
        Subsystem: MEDIATEK Corp. Device 6639
        Flags: bus master, fast devsel, latency 0, IRQ 121
        Memory at 30200000 (64-bit, prefetchable) [size=2M]
        Memory at 30400000 (64-bit, non-prefetchable) [size=32K]
        Capabilities: [80] Express Endpoint, IntMsgNum 0
        Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+
        Capabilities: [f8] Power Management version 3
        Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?>
        Capabilities: [108] Latency Tolerance Reporting
        Capabilities: [110] L1 PM Substates
        Capabilities: [200] Advanced Error Reporting
        Capabilities: [300] Secondary PCI Express
        Kernel driver in use: mt7996e

0001:00:00.0 PCI bridge: MEDIATEK Corp. Device 7988 (rev 01) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 125
        Memory at 38500000 (64-bit, non-prefetchable) [size=32K]
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: [disabled] [32-bit]
        Memory behind bridge: 38400000-384fffff [size=1M] [32-bit]
        Prefetchable memory behind bridge: 38200000-383fffff [size=2M] [32-bit]
        Capabilities: [80] Express Root Port (Slot-), IntMsgNum 0
        Capabilities: [e0] MSI: Enable+ Count=1/32 Maskable+ 64bit+
        Capabilities: [f8] Power Management version 3
        Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?>
        Capabilities: [110] L1 PM Substates
        Capabilities: [200] Advanced Error Reporting
        Capabilities: [300] Secondary PCI Express
        Kernel driver in use: pcieport

0001:01:00.0 Network controller: MEDIATEK Corp. Device 7991
        Subsystem: MEDIATEK Corp. Device 6639
        Flags: bus master, fast devsel, latency 0, IRQ 124
        Memory at 38200000 (64-bit, prefetchable) [size=2M]
        Memory at 38400000 (64-bit, non-prefetchable) [size=32K]
        Capabilities: [80] Express Endpoint, IntMsgNum 0
        Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+
        Capabilities: [f8] Power Management version 3
        Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?>
        Capabilities: [108] Latency Tolerance Reporting
        Capabilities: [110] L1 PM Substates
        Capabilities: [200] Advanced Error Reporting
        Capabilities: [300] Secondary PCI Express
        Kernel driver in use: mt7996e_hif

Unfortunately, I still find errors there. Does anyone have any advice? I reinstalled libkmod, but it did not worked to solve the error.

By the way, I have displayed all the errors from dmesg. It would be nice if someone could give me a little help and give me a little guidance on where and, above all, how I can look for the cause?