kernel: usbnet: Restore usb%d naming for cdc-ethernet devices with local MAC
Prior to commit https://github.com/torvalds/linux/commit/8a7d12d674ac6f2147c18f36d1e15f1a48060edf, cdc-ethernet USB LTE modems (e.g. Quectel EC200A) were consistently named usb0. After 8a7d12d67, devices began renaming to eth1 due to an assumption that local MAC addresses originate exclusively from the kernel. Some devices provide driver-assigned local MACs, causing point-to-point interfaces with driver-set MACs to adopt eth%d names instead of usb%d.
Restore the naming exception for point-to-point devices: interfaces without driver MACs or with driver-provided local MACs will retain the usb%d convention. This addresses issues reported in [1] and fixed in [2].
Tested-by: Ahmed Naseef <naseefkm@gmail.com> Signed-off-by: Ahmed Naseef <naseefkm@gmail.com> Link: https://github.com/openwrt/openwrt/pull/17757 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: ecd609f)
I selected one subtarget after the other and refreshed their configuration using this command: make kernel_oldconfig CONFIG_TARGET=subtarget
For MT7629 I had to re-add CONFIG_LEDS_SMARTRG_LED manually. Otherwise, building MT7629 with ALL_KMODS we get prompted for LEDS_SMARTRG_LED and this will break CI and in future buildbot compilation. See commit 6bdea8c7bd85 ("mediatek: mt7629: 6.6: disable LEDS_SMARTRG_LED by default") for more details.
Signed-off-by: Martin Schiller <ms@dev.tdt.de> (commit: 5013efc)
Due to API changes during the backport, the default value of Tx LPI timer is accidentally left unset, breaking the network if EEE is on. Set the default timer to 1ms on init, and fix an incorrect condition.
qualcommax: fap650: fix dtc warnings on partitions
This commit adds the missing properties to address the following warnings: Warning (reg_format): /soc@0/spi@78b5000/flash@0/partitions/partition@x:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1)"
Signed-off-by: Weikai Kong <priv@pppig236.com> Link: #18180 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 213799e)
Quoting the kconfig description for CONFIG_PCPU_DEV_REFCNT:
network device refcount are using per cpu variables if this option is set. This can be forced to N to detect underflows (with a performance drop).
This was introduced from kernel 5.13 and was wrongly set as disabled. Some target actually enables it but this should be always enabled unless refcount needs to be debugged (unlikely for production images)
Enable in generic and drop the entry in every other target.
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com> Link: https://github.com/openwrt/openwrt/pull/18174 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: ea6f3e4)
This board is also as known as SuperElectron ZN-M5 and ZN-M8. However, for ZN-M5 and ZN-M8, there's another version uses ZX279128 as CPU chip, which is unsupported. You can check it in "高级设置" > "系统日志" > "内核日志" page from webUI.
Stock layout flash instructions: Login into webUI and upload sysupgrade firmware in "系统管理" > "升级固件" page. Remember to unselect "保留配置" ("Keep configurations") first before doing that.
OpenWrt U-Boot layout flash instructions: 1. Flash stock layout firmware first. 2. Connect to the device via SSH, and backup everything, especially 'Factory' partition. 3. Unlock MTD partitions: apk update && apk add kmod-mtd-rw insmod mtd-rw i_want_a_brick=1 4. Write new BL2 and FIP: mtd write openwrt-mediatek-filogic-cmcc_a10-ubootmod-preloader.bin BL2 mtd write openwrt-mediatek-filogic-cmcc_a10-ubootmod-bl31-uboot.fip FIP 5. Set static IP on your PC: IP 192.168.1.254/24, GW 192.168.1.1 6. Serve OpenWrt initramfs image using TFTP server. 7. Cut off the power and re-engage, wait for TFTP recovery to complete. 8. After OpenWrt has booted, perform sysupgrade.
The spaces in variables have been stripped since commit 551e04f3c9c0 ("base-files: strip space and tab characters from ASCII mac address"), resulting "Vfac_mac " matches nothing. Fix the issue by removing the space at end.
d8b43985e4d7 ubus: fix token_create policy 7326459bd743 ubus: dump service information on network_get 6c9c8fbd8128 service: add @all as alias for all members, unless defined differently
Signed-off-by: Felix Fietkau <nbd@nbd.name> (commit: 84909c6)
MAC Addresses: - There is one on the label, e.g. xx:xx:xx:xx:xx:1C - LAN (bottom connector) is the same as the label, e.g. xx:xx:xx:xx:xx:1C - WAN (top connector) is label +2, e.g. xx:xx:xx:xx:xx:1E - WLAN (2.4G) is the same as the label, e.g. xx:xx:xx:xx:xx:1C - WLAN (5G) is the same as WAN, e.g. xx:xx:xx:xx:xx:1E
UART: - is available via the pin holes on the board - From inner to outer pin: TX, RX, GND, VCC - Do NOT connect VCC - Settings: 3.3V, 115200, 8N1
GPIO: - There are two LEDs: Red (GPIO 3) and White (GPIO 4) - There are two buttons: Reset (GPIO 8) and WPS (GPIO 10)
Migration to OpenWrt: - Download the migration image from the Cudy website (it should be available as soon as OpenWrt officially supports the device) - The migration image is also available here until a image is provided by Cudy: https://github.com/RolandoMagico/openwrt-build/releases/tag/M1300_Build_20240222 - File: openwrt-ramips-mt7621-cudy_m1300-v2-squashfs-flash-signed.bin - Connect computer to LAN (bottom connector) and flash the migration image via OEM web interface - In the migration image, LAN and WAN are swapped. Computer must be connected to the other port after flashing - OpenWrt is now accessible via 192.168.1.1 - After flashing an up to date OpenWrt image, LAN and WAN settings are again the same as in the OEM firmware - So use the other connector again
Revert back to OEM firmware: - Set up a TFTP server on IP 192.168.1.88 and connect to the LAN port (lower port) - Provide the Cudy firmware as recovery.bin in the TFTP server - Press the reset button while powering on the device - Recovery process is started now - When recovery process is done, OEM firmware is accessible via 192.168.10.1 again
General information: - No possibility to load a initramfs image via U-Boot because there is no option to interrupt U-Boot
The kmod-mlxsw-spectrum driver activated CONFIG_DCB indirectly already on all targets which are building this driver. All other DCB capable driver did not activate their DCB support.
CONFIG_DCB increases the uncompressed kernel size by about 7.8KB.
CONFIG_DCB is only needed some data center Ethernet cards and not used on normal routers. Activate it only on the x86_64 and the armsr_arm64 target which are used on normal servers or in VMs.
dnsmasq: fix handlers for options `filter_rr` and `cache_rr`
According to: - https://github.com/openwrt/luci/blob/master/modules/luci-mod-network/htdocs/luci-static/resources/view/network/dhcp.js#L700 - https://github.com/openwrt/luci/blob/master/modules/luci-mod-network/htdocs/luci-static/resources/view/network/dhcp.js#L402
These two options should be of type `MultiValue` but here there're used as single value. This results in dnsmasq crashes when either of these options are set with multiple values, which leads to an invalid space-separated value.
As these options are designed to take multiple values, I think it's better to use list format eg. `list filter_rr 'AAAA'`, instead of `option filter_rr 'AAAA,HTTPS'`.
Amber LAN LED appears hardwired to ethernet port. Power LED is green only. Other LEDs are amber/green.
**MAC addresses:**
1 MAC Address in flash at end of uboot ASCII encoded, no delimiters Labeled as "MAC Address" on case
**Serial Access:**
Pinout: (arrow) VCC GND RX TX
Pins are populated with a header and traces not blocked. Bootloader is set to 9600 baud, 8 data, 1 stop.
**Console Access:**
Bootloader:
Interrupt boot with Ctrl+C Press "k" and enter password "1" OR Hold reset button for 5 sec during power on Interrupt the TFTP transfer with Ctrl+C
to print commands available, enter "help"
OEM:
default username is "admin", password blank telnet is available at default address 192.168.1.2 serial is available with baud 9600
to print commands available, enter "help" or tab-tab (busybox list of commands)
**Installation:**
Use factory.bin with OEM upgrade procedures OR Use initramfs.bin with uboot TFTP commands. Then perform a sysupgrade with sysupgrade.bin
**TFTP Recovery:**
Using serial console, load initramfs.bin using TFTP to boot openwrt without touching the flash.
**Return to OEM:**
The best way to return to OEM firmware is to have a copy of the MTD partitions before flashing Openwrt.
Backup copies should be made of partitions "fwconcat0", "loader", and "fwconcat1" which together is the same flash range as OEM's "rootfs" and "uimage" by loading an initramfs.bin and using LuCI to download the mtdblocks.
It is also possible to extract from the OEM firmware upgrade image by splitting it up in parts of lengths that correspond to the partitions in openwrt and write them to flash, after gzip decompression.
After writing to the firmware partitions, erase the "reserved" partition and reboot.
![[Jenkins]](/jenkins/static/07718dac/images/svgs/logo.svg){kind=logo}
