Char11e

This is a problem of interaction between the phy driver and MAC in the Linux kernel. ./stmicro/stmmac/stmmac_main.c:928: pr_err("%s: Cannot attach to PHY (error: %d)\n", __func__, ret); ./stmicro/stmmac/stmmac_main.c-894-static int stmmac_open(struct net_device *dev) ./stmicro/stmmac/stmmac_main.c:299:static int stmmac_init_phy(struct net_device *dev) ../phy/phy_device.c:371:struct phy_device * phy_connect(struct net_device *dev, const char *bus_id, ./phy_device.c:336:int phy_connect_direct(struct net_device *dev, struct phy_device *phydev, ./phy_device.c:441:static int phy_attach_direct(struct net_device *dev, struct phy_device *phydev, ./phy_device.c:413:int phy_init_hw(struct phy_device *phydev) It is known that an error will be reported during phy initialization, but I am still looking for the kernel source code for Sunxi Linux 6.1.xx and 5.15.xx. Error code flow: stmmac_open > stmmac_init_phy > phy_connect > phy_connect_direct > phy_attach_direct > phy_init_hw

Hi @Igor, Thank you for your useful and honest advice. I appreciate it. https://github.com/CGarces/rtl8192eu-linux-driver/commit/d32dfa2c2b2a1b8e75d163d23e9e18f750ebfbe4 I have found that someone has provided a fix for Tx power in the rtl8192eu driver. I am currently compiling and testing this method to work in the RTL8189FS driver.

Thank you for your explanation and contribution, I appreciate and admire it. https://linux-sunxi.org/Wifi#RTL8189FTV I will try to look into rtl8189fs, thank you very much!

At present, I tested and found that wlan0&wlan1 can only connect to the same SSID at the same time. However, the information in iw points out that the two have different phy numbers.

pi@orangepipcplus:~$ sudo iwconfig wlan0 txpower 20 Error for wireless request "Set Tx Power" (8B26) : SET failed on device wlan0 ; Operation not permitted. pi@orangepipcplus:~$ sudo iw dev wlan0 set txpower fixed 2000 pi@orangepipcplus:~$ I tried to use iwconfig and iw commands to configure txpower. However, iwconfig will give an error response of "Set tx power". iw does not respond to any messages.

I'm not sure if this is related to a limitation of the rtl8189fs firmware. I tried closing the wlan0 interface first and then configuring txpower, but it didn't seem to work. After executing the command, check dmesg and no relevant logs are found.

pi@orangepipcplus:~$ sudo lshw -C network *-network:0 description: Ethernet interface physical id: 12 logical name: eth0 serial: 02:81:64:17:11:3d size: 100Mbit/s capacity: 100Mbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=st_mac100 driverversion=6.6.44-current-sunxi duplex=full ip=192.168.1.100 link=yes multicast=yes port=twisted pair speed=100Mbit/s *-network:1 description: Wireless interface physical id: 13 bus info: mmc@1:0001:1 logical name: wlan0 serial: 12:81:64:17:11:3d capabilities: ethernet physical wireless configuration: broadcast=yes driver=rtl8189fs driverversion=6.6.44-current-sunxi ip=192.168.0.214 multicast=yes wireless=IEEE 802.11bgn *-network:2 description: Wireless interface physical id: 14 bus info: mmc@1:0001:1 logical name: wlan1 serial: 12:81:64:17:13:3d capabilities: ethernet physical wireless configuration: broadcast=yes driver=rtl8189fs driverversion=6.6.44-current-sunxi multicast=yes wireless=unassociated

pi@orangepipcplus:~$ uname -a Linux orangepipcplus 6.6.44-current-sunxi #1 SMP Sat Aug 3 06:54:42 UTC 2024 armv7l armv7l armv7l GNU/Linux pi@orangepipcplus:~$ cat /etc/os-release PRETTY_NAME="Armbian 24.8.0-trunk.581 jammy" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.armbian.com" SUPPORT_URL="https://forum.armbian.com" BUG_REPORT_URL="https://www.armbian.com/bugs" PRIVACY_POLICY_URL="https://www.armbian.com" UBUNTU_CODENAME=jammy ARMBIAN_PRETTY_NAME="Armbian 24.8.0-trunk.581 jammy"

pi@orangepipcplus:~$ iwconfig lo no wireless extensions. eth0 no wireless extensions. wlan0 IEEE 802.11bgn ESSID:"R15-3437" Nickname:"<WIFI@REALTEK>" Mode:Managed Frequency:2.417 GHz Access Point: A4:2A:95:33:34:3B Bit Rate:72.2 Mb/s Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Power Management:off Link Quality=97/100 Signal level=40/100 Noise level=0/100 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 wlan1 unassociated Nickname:"<WIFI@REALTEK>" Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 pi@orangepipcplus:~$ ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.100 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::81:64ff:fe17:113d prefixlen 64 scopeid 0x20<link> ether 02:81:64:17:11:3d txqueuelen 1000 (Ethernet) RX packets 249637 bytes 216991539 (216.9 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 273259 bytes 225570858 (225.5 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 35 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 346 bytes 44456 (44.4 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 346 bytes 44456 (44.4 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.214 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::606f:e755:6337:dbe5 prefixlen 64 scopeid 0x20<link> ether 12:81:64:17:11:3d txqueuelen 1000 (Ethernet) RX packets 62772 bytes 196306992 (196.3 MB) RX errors 0 dropped 184 overruns 0 frame 0 TX packets 18238 bytes 6340912 (6.3 MB) TX errors 0 dropped 2 overruns 0 carrier 0 collisions 0 wlan1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 12:81:64:17:13:3d txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 pi@orangepipcplus:~$ sudo iw dev wlan0 info Interface wlan0 ifindex 3 wdev 0x1 addr 12:81:64:17:11:3d ssid R15-3437 type managed wiphy 0 txpower 12.00 dBm pi@orangepipcplus:~$ ^C pi@orangepipcplus:~$ sudo iw dev wlan0 set txpower fixed 2000 pi@orangepipcplus:~$ sudo iw dev wlan0 info Interface wlan0 ifindex 3 wdev 0x1 addr 12:81:64:17:11:3d ssid R15-3437 type managed wiphy 0 txpower 12.00 dBm pi@orangepipcplus:~$ sudo iw dev wlan0 set txpower fixed 1500 pi@orangepipcplus:~$ sudo iw dev wlan0 info Interface wlan0 ifindex 3 wdev 0x1 addr 12:81:64:17:11:3d ssid R15-3437 type managed wiphy 0 txpower 12.00 dBm

I want to modify the antenna strength of wlan0 in orangepipcplus, but using software settings does not work.

@Gunjan Gupta Thank you for your suggestion. Currently, the kernel is upgraded to 6.6.36-current-sunxi. I found that the dts file has the USB defaulted to otg mode, and the USB storage device can be read and used normally. usb@1c19000 { compatible = "allwinner,sun8i-h3-musb"; reg = <0x1c19000 0x400>; clocks = <0x03 0x20>; resets = <0x03 0x11>; interrupts = <0x00 0x47 0x04>; interrupt-names = "mc"; phys = <0x18 0x00>; phy-names = "usb"; extcon = <0x18 0x00>; dr_mode = "otg"; status = "okay"; phandle = <0x57>;

@Igor Thank you very much for your information! At present, I have synchronized the kernel to the latest version and can already see the wlan0 network card.

@Dmitriy Golovin Can I add RTL8189FS settings to armbian-config to enable the network card?

dmesg also shows that mmc1 has detected the sdio card. pi@orangepipcplus:~$ dmesg | grep mmc [ 0.000000] Kernel command line: root=UUID=f9fc34f5-ca46-43b7-8daf-4f52710744dd rootwait rootfstype=ext4 splash=verbose console=ttyS0,115200 console=tty1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 consoleblank=0 loglevel=1 ubootpart=6f12a333-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1 [ 0.000000] Unknown kernel command line parameters "splash=verbose ubootpart=6f12a333-01 ubootsource=mmc sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory", will be passed to user space. [ 2.190752] sunxi-mmc 1c0f000.mmc: Got CD GPIO [ 2.215138] sunxi-mmc 1c0f000.mmc: initialized, max. request size: 16384 KB [ 2.219150] sunxi-mmc 1c11000.mmc: initialized, max. request size: 16384 KB [ 2.250971] mmc0: host does not support reading read-only switch, assuming write-enable [ 2.254281] mmc0: new high speed SDHC card at address aaaa [ 2.255979] mmcblk0: mmc0:aaaa SE32G 29.7 GiB [ 2.262583] mmcblk0: p1 [ 2.279121] ubootsource=mmc [ 2.339350] mmc2: new DDR MMC card at address 0001 [ 2.341100] mmcblk2: mmc2:0001 8GTF4R 7.28 GiB [ 2.344746] mmcblk2: p1 [ 2.346628] mmcblk2boot0: mmc2:0001 8GTF4R 4.00 MiB [ 2.350919] mmcblk2boot1: mmc2:0001 8GTF4R 4.00 MiB [ 3.048466] sunxi-mmc 1c10000.mmc: allocated mmc-pwrseq [ 3.071233] sunxi-mmc 1c10000.mmc: initialized, max. request size: 16384 KB [ 3.108016] mmc1: new high speed SDIO card at address 0001 [ 3.989616] EXT4-fs (mmcblk0p1): mounted filesystem f9fc34f5-ca46-43b7-8daf-4f52710744dd ro with writeback data mode. Quota mode: none. [ 7.657890] EXT4-fs (mmcblk0p1): re-mounted f9fc34f5-ca46-43b7-8daf-4f52710744dd r/w. Quota mode: none. pi@orangepipcplus:~$

I checked the dts settings and it shows that wifi is implemented in mmc1. mmc@1c10000 { reg = <0x1c10000 0x1000>; pinctrl-names = "default"; pinctrl-0 = <0x17>; resets = <0x03 0x08>; reset-names = "ahb"; interrupts = <0x00 0x3d 0x04>; status = "okay"; #address-cells = <0x01>; #size-cells = <0x00>; compatible = "allwinner,sun7i-a20-mmc"; clocks = <0x03 0x17 0x03 0x4a 0x03 0x4c 0x03 0x4b>; clock-names = "ahb\0mmc\0output\0sample"; vmmc-supply = <0x15>; mmc-pwrseq = <0x18>; bus-width = <0x04>; non-removable; phandle = <0x56>; sdio_wifi@1 { reg = <0x01>; phandle = <0x57>; }; };

After orangepiplus upgraded the kernel, the native wifi interface card disappeared. Output log of sudo armbianmonitor -u: https://paste.armbian.com/ilufiwukav Currently, after upgrading the kernel to 6.6.36-current-sunxi, the native wlan0 will disappear.

At present, when I check the status of the phy controller, it is unlocked. But I am very curious about the relationship between wdev 0x100000001 in wlan1 and wdev 0x1 in wlan0. Does this mean that wlan1 is simulated from wlan0? pi@orangepipcplus:~$ iw dev phy#1 Interface wlan1 ifindex 4 wdev 0x100000001 addr 12:81:64:17:13:3d type managed txpower 12.00 dBm phy#0 Interface wlan0 ifindex 3 wdev 0x1 addr 12:81:64:17:11:3d ssid R15-3437 type managed txpower 12.00 dBm pi@orangepipcplus:~$ rfkill ID TYPE DEVICE SOFT HARD 0 wlan phy0 unblocked unblocked 1 wlan phy1 unblocked unblocked pi@orangepipcplus:~$

I am using orange pi pc plus after using armbian system, there is an infinite network with WLAN0 and WLAN1, but at present there is no law to use both networks at the same time and connect different SSIDs. Error: Connection activation failed: (7) Secrets were required, but not provided. pi@orangepipcplus:~$ cat /etc/os-release PRETTY_NAME="Armbian 24.5.0-trunk.512 jammy" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.armbian.com" SUPPORT_URL="https://forum.armbian.com" BUG_REPORT_URL="https://www.armbian.com/bugs" PRIVACY_POLICY_URL="https://www.armbian.com" UBUNTU_CODENAME=jammy ARMBIAN_PRETTY_NAME="Armbian 24.5.0-trunk.512 jammy" pi@orangepipcplus:~$ uname -a Linux orangepipcplus 6.6.29-current-sunxi #1 SMP Sat Apr 27 15:11:44 UTC 2024 armv7l armv7l armv7l GNU/Linux pi@orangepipcplus:~$ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff inet 192.168.1.101/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0 valid_lft 4555sec preferred_lft 4555sec inet6 fe80::9f55:6e99:c16e:8c7/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff inet 192.168.0.214/24 brd 192.168.0.255 scope global dynamic noprefixroute wlan0 valid_lft 604097sec preferred_lft 604097sec inet6 fe80::faea:304c:b4b2:2c53/64 scope link noprefixroute valid_lft forever preferred_lft forever 4: wlan1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff pi@orangepipcplus:~$ nmcli device wifi connect <ssid> password <pwd> ifname wlan1 Error: Connection activation failed: (7) Secrets were required, but not provided.

Yes, when I captured the dmesg log, I had the otg usb cable connected and an 8g usb2.0 flash drive connected.

This is the dmesg_log of my system. dmseg_log.txt

Thank you for your answer. However, after I restarted the system, the g_serial module has been uninstalled. However, after I connected the USB OTG external device, the device was still not read. pi@orangepipc:~$ lsmod | grep serial pi@orangepipc:~$ lsmod | grep usb pi@orangepipc:~$ lsusb Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 0080:a001 Unknown JMS578 based SATA bridge Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub pi@orangepipc:~$ lsusb Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 0080:a001 Unknown JMS578 based SATA bridge Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub pi@orangepipc:~$ My device is a USB2.0 8G flash drive. I'm not sure if I've set it up correctly?

I uninstalled g_serial using modprobe but it doesn't seem to work. I tried using the lsusb and lsblk commands to check. When I connected the OTG USB, the system did not automatically detect the new device. pi@orangepipc:~$ lsmod | grep serial u_serial 24576 1 usb_f_acm pi@orangepipc:~$ lsusb Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 0080:a001 Unknown JMS578 based SATA bridge Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub pi@orangepipc:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 2.7T 0 disk └─sda1 8:1 0 2.7T 0 part /home/pi/dl mmcblk0 179:0 0 14.8G 0 disk └─mmcblk0p1 179:1 0 14.7G 0 part /var/log.hdd / zram0 254:0 0 499M 0 disk [SWAP] zram1 254:1 0 50M 0 disk /var/log zram2 254:2 0 0B 0 disk

pi@orangepipc:~$ sudo modprobe g_serial pi@orangepipc:~$ lsmod | grep serial g_serial 16384 0 u_serial 24576 1 usb_f_acm libcomposite 45056 2 g_serial,usb_f_acm I have the g_serial module enabled, but this seems to be the function that makes otg a serial port.

pi@orangepipc:~$ dmesg |grep musb [ 2.610963] musb-hdrc musb-hdrc.4.auto: MUSB HDRC host driver [ 2.611005] musb-hdrc musb-hdrc.4.auto: new USB bus registered, assigned bus number 9 [ 2.611363] usb usb9: Manufacturer: Linux 6.1.63-current-sunxi musb-hcd [ 2.611373] usb usb9: SerialNumber: musb-hdrc.4.auto

The system I currently use: Armbian 23.11.1 jammy Linux kernel version: Linux orangepipc 6.1.63-current-sunxi #1 SMP Mon Nov 20 10:52:19 UTC 2023 armv7l armv7l armv7l GNU/Linux Currently I want to make this OTG USB work like the other three USB Ports. Do I need to recompile DTS?