mt76 icon indicating copy to clipboard operation
mt76 copied to clipboard

OpenWrt 21.02.0 r16279 R6220 Problem with 2.4 GHz Radio

Open ABusuuu opened this issue 3 years ago • 32 comments

Tue Sep 28 16:16:19 2021 daemon.notice netifd: radio0 (1899): Could not find PHY for device 'radio0' Tue Sep 28 16:16:19 2021 daemon.notice netifd: radio0 (2019): WARNING: Variable 'data' does not exist or is not an array/object Tue Sep 28 16:16:19 2021 daemon.notice netifd: radio0 (2019): Bug: PHY is undefined for device 'radio0'

In luci i have Wireless is not associated and in Radio 0 settings, Operation frequency field is empty, i can't choose anythink. I noticed when i change 5Ghz radio 1 channel to higher than 40 i have this same problem as radio 0.

ABusuuu avatar Oct 05 '21 18:10 ABusuuu

Openwrt Version: OpenWrt 21.02.1 r16325-88151b8303

System Log:

Sat Nov 13 20:23:38 2021 daemon.notice netifd: radio1 (4423): Could not find PHY for device 'radio1'
Sat Nov 13 20:23:38 2021 daemon.notice netifd: radio1 (4438): WARNING: Variable 'data' does not exist or is not an array/object
Sat Nov 13 20:23:38 2021 daemon.notice netifd: radio1 (4438): Bug: PHY is undefined for device 'radio1'

(I want upload log file and screen shot file, but there is a bug from github, Therefore I cannot upload files) (github bug: POST https://github-production-upload-manifest-file-7fdce7.s3.amazonaws.com/ net::ERR_SSL_VERSION_OR_CIPHER_MISMATCH )

I used megasync and shared this files

kernel_log.txt https://mega.nz/file/Hwl0VIQQ#XUCMgYO44eFTQYZL4Bz-Tz3A7NcYFc7xHMCxLRLTjns system_log.txt https://mega.nz/file/ngkyXKYD#R4T2W2cZR8lJhGbzJZikUmW7SBnwb47tuWpaZ3D8kJA Screenshot 2021-11-13 202837.png https://mega.nz/file/mssgCCAK#2CbenxfAqq5mq48JMjbVpZbsadchXvGQnSH9YrFOSrM

weiqi-chen avatar Nov 13 '21 12:11 weiqi-chen

I got the following error too

Fri Mar 18 19:10:35 2022 daemon.notice netifd: radio0 (3331): Could not find PHY for device 'radio0'
Fri Mar 18 19:10:35 2022 daemon.notice netifd: Wireless device 'radio0' set retry=0
Fri Mar 18 19:10:35 2022 daemon.crit netifd: Wireless device 'radio0' setup failed, retry=0
Fri Mar 18 19:10:35 2022 daemon.notice netifd: radio0 (3343): WARNING: Variable 'data' does not exist or is not an array/object
Fri Mar 18 19:10:35 2022 daemon.notice netifd: radio0 (3343): Bug: PHY is undefined for device 'radio0'
Fri Mar 18 19:10:35 2022 daemon.notice netifd: Wireless device 'radio0' is now down

and it looks like iw doesn't recognize 2.4 GHz radio interface at all

root@router:~# iw list
Wiphy phy0
	wiphy index: 0
	max # scan SSIDs: 4
	max scan IEs length: 2247 bytes
	max # sched scan SSIDs: 0
	max # match sets: 0
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Device supports AP-side u-APSD.
	Device supports T-DLS.
	Available Antennas: TX 0x3 RX 0x3
	Configured Antennas: TX 0x3 RX 0x3
	Supported interface modes:
		* IBSS
		* managed
		* AP
		* AP/VLAN
		* monitor
		* mesh point
		* P2P-client
		* P2P-GO
	Band 2:
		Capabilities: 0x1ff
			RX LDPC
			HT20/HT40
			SM Power Save disabled
			RX Greenfield
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 3839 bytes
			No DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: No restriction (0x00)
		HT TX/RX MCS rate indexes supported: 0-15
		VHT Capabilities (0x318001b0):
			Max MPDU length: 3895
			Supported Channel Width: neither 160 nor 80+80
			RX LDPC
			short GI (80 MHz)
			TX STBC
			RX antenna pattern consistency
			TX antenna pattern consistency
		VHT RX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: not supported
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT RX highest supported: 0 Mbps
		VHT TX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: not supported
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT TX highest supported: 0 Mbps
		Frequencies:
			* 5180 MHz [36] (20.0 dBm)
			* 5200 MHz [40] (20.0 dBm)
			* 5220 MHz [44] (20.0 dBm)
			* 5240 MHz [48] (20.0 dBm)
			* 5260 MHz [52] (20.0 dBm) (no IR, radar detection)
			* 5280 MHz [56] (20.0 dBm) (no IR, radar detection)
			* 5300 MHz [60] (20.0 dBm) (no IR, radar detection)
			* 5320 MHz [64] (20.0 dBm) (no IR, radar detection)
			* 5500 MHz [100] (20.0 dBm) (no IR, radar detection)
			* 5520 MHz [104] (20.0 dBm) (no IR, radar detection)
			* 5540 MHz [108] (20.0 dBm) (no IR, radar detection)
			* 5560 MHz [112] (20.0 dBm) (no IR, radar detection)
			* 5580 MHz [116] (20.0 dBm) (no IR, radar detection)
			* 5600 MHz [120] (20.0 dBm) (no IR, radar detection)
			* 5620 MHz [124] (20.0 dBm) (no IR, radar detection)
			* 5640 MHz [128] (20.0 dBm) (no IR, radar detection)
			* 5660 MHz [132] (20.0 dBm) (no IR, radar detection)
			* 5680 MHz [136] (20.0 dBm) (no IR, radar detection)
			* 5700 MHz [140] (20.0 dBm) (no IR, radar detection)
			* 5720 MHz [144] (20.0 dBm) (no IR, radar detection)
			* 5745 MHz [149] (20.0 dBm) (no IR)
			* 5765 MHz [153] (20.0 dBm) (no IR)
			* 5785 MHz [157] (20.0 dBm) (no IR)
			* 5805 MHz [161] (20.0 dBm) (no IR)
			* 5825 MHz [165] (20.0 dBm) (no IR)
			* 5845 MHz [169] (disabled)
			* 5865 MHz [173] (disabled)
	valid interface combinations:
		* #{ IBSS } <= 1, #{ managed, AP, mesh point, P2P-client, P2P-GO } <= 8,
		  total <= 8, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }

	HT Capability overrides:
		* MCS: ff ff ff ff ff ff ff ff ff ff
		* maximum A-MSDU length
		* supported channel width
		* short GI for 40 MHz
		* max A-MPDU length exponent
		* min MPDU start spacing
	max # scan plans: 1
	max scan plan interval: -1
	max scan plan iterations: 0
	Supported extended features:
		* [ VHT_IBSS ]: VHT-IBSS
		* [ RRM ]: RRM
		* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
		* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
		* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
		* [ AIRTIME_FAIRNESS ]: airtime fairness scheduling
		* [ AQL ]: Airtime Queue Limits (AQL)
		* [ SCAN_RANDOM_SN ]: use random sequence numbers in scans
		* [ SCAN_MIN_PREQ_CONTENT ]: use probe request with only rate IEs in scans
		* [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
		* [ DEL_IBSS_STA ]: deletion of IBSS station support
		* [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
		* [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support

This is a 2.4 GHz radio on R6220.

robin92 avatar Mar 18 '22 18:03 robin92

@robin92 I have the same issue, have you fix your issue ?

pierrepinon avatar Jun 25 '22 13:06 pierrepinon

No, not really. I wanted to buy another router anyway and haven't got enough time to look deeper into the issue with this one.

Message ID: @.***>

robin92 avatar Jun 25 '22 15:06 robin92

https://forum.openwrt.org/t/r6220-could-not-find-phy-for-device-radio0-mt76x2-issue-continues/116665/4 @ligthpower said add these pcie reset pin definition to mt7621_netgear_r6220.dts solve the problem.

&pcie {
        status = "okay";

        reset-gpios = <&gpio 19 GPIO_ACTIVE_LOW>,
                      <&gpio 8 GPIO_ACTIVE_LOW>;
};

DragonBluep avatar Jun 25 '22 15:06 DragonBluep

@DragonBluep I try solution and share my feedback. Thx

pierrepinon avatar Jun 25 '22 17:06 pierrepinon

I add PR with fix in openwrt repository (https://github.com/openwrt/openwrt/pull/10125)

pierrepinon avatar Jun 26 '22 15:06 pierrepinon

https://forum.openwrt.org/t/r6220-could-not-find-phy-for-device-radio0-mt76x2-issue-continues/116665/4 @ligthpower said add these pcie reset pin definition to mt7621_netgear_r6220.dts solve the problem.

&pcie {
        status = "okay";

        reset-gpios = <&gpio 19 GPIO_ACTIVE_LOW>,
                      <&gpio 8 GPIO_ACTIVE_LOW>;
};

I tried updated: $ cat target/linux/ramips/dts/mt7621_netgear_sercomm_ayx.dtsi

...
&pcie {
        status = "okay";
        reset-gpios = <&gpio 19 GPIO_ACTIVE_LOW>,
                      <&gpio 8 GPIO_ACTIVE_LOW>;
};
...

or put changes into target/linux/ramips/dts/mt7621_netgear_r6220.dts

then created the image:

make image PROFILE="netgear_r6220" FILES="files" PACKAGES="luci"

root@netgear-openwrt:~# dmesg | grep pci
[    2.306509] mt7621-pci 1e140000.pcie: Parsing DT failed
[    2.523125] rt2880-pinmux pinctrl: pcie is already enabled
[    2.534238] mt7621-pci-phy 1e149000.pcie-phy: PHY for 0xbe149000 (dual port = 1)
[    2.549183] mt7621-pci-phy 1e14a000.pcie-phy: PHY for 0xbe14a000 (dual port = 0)
[    2.663730] mt7621-pci-phy 1e149000.pcie-phy: Xtal is 40MHz
[    2.674847] mt7621-pci-phy 1e14a000.pcie-phy: Xtal is 40MHz
[    2.785675] mt7621-pci 1e140000.pcie: pcie1 no card, disable it (RST & CLK)
[    2.799542] mt7621-pci 1e140000.pcie: pcie2 no card, disable it (RST & CLK)
[    2.813416] mt7621-pci 1e140000.pcie: PCIE0 enabled
[    2.823137] mt7621-pci 1e140000.pcie: PCI coherence region base: 0x60000000, mask/settings: 0xf0000002
[    2.841877] mt7621-pci 1e140000.pcie: PCI host bridge to bus 0000:00
[    2.854558] pci_bus 0000:00: root bus resource [io  0x1e160000-0x1e16ffff]
[    2.868259] pci_bus 0000:00: root bus resource [mem 0x60000000-0x6fffffff]
[    2.881960] pci_bus 0000:00: root bus resource [bus 00-ff]
[    2.892952] pci 0000:00:00.0: [0e8d:0801] type 01 class 0x060400
[    2.904956] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x7fffffff]
[    2.917447] pci 0000:00:00.0: reg 0x14: [mem 0x00000000-0x0000ffff]
[    2.930012] pci 0000:00:00.0: supports D1
[    2.938003] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    2.950985] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    2.967172] pci 0000:01:00.0: [14c3:7662] type 00 class 0x028000
[    2.979205] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x000fffff 64bit]
[    2.992784] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[    3.006238] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
[    3.019902] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[    3.030322] pci 0000:00:00.0:   bridge window [io  0x0000-0x0fff]
[    3.042467] pci 0000:00:00.0:   bridge window [mem 0x00000000-0x000fffff]
[    3.055998] pci 0000:00:00.0:   bridge window [mem 0x00000000-0x000fffff pref]
[    3.070390] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    3.083616] pci 0000:00:00.0: BAR 0: no space for [mem size 0x80000000]
[    3.096807] pci 0000:00:00.0: BAR 0: failed to assign [mem size 0x80000000]
[    3.110680] pci 0000:00:00.0: BAR 8: assigned [mem 0x60000000-0x600fffff]
[    3.124212] pci 0000:00:00.0: BAR 9: assigned [mem 0x60100000-0x601fffff pref]
[    3.138604] pci 0000:00:00.0: BAR 1: assigned [mem 0x60200000-0x6020ffff]
[    3.152141] pci 0000:00:00.0: BAR 7: assigned [io  0x1e160000-0x1e160fff]
[    3.165673] pci 0000:01:00.0: BAR 0: assigned [mem 0x60000000-0x600fffff 64bit]
[    3.180250] pci 0000:01:00.0: BAR 6: assigned [mem 0x60100000-0x6010ffff pref]
[    3.194640] pci 0000:00:00.0: PCI bridge to [bus 01]
[    3.204543] pci 0000:00:00.0:   bridge window [io  0x1e160000-0x1e160fff]
[    3.218069] pci 0000:00:00.0:   bridge window [mem 0x60000000-0x600fffff]
[    3.231594] pci 0000:00:00.0:   bridge window [mem 0x60100000-0x601fffff pref]
[   13.563339] mt7621-pci 1e140000.pcie: bus=1 slot=0 irq=19
[   13.574253] pci 0000:00:00.0: enabling device (0004 -> 0007)

But still no 2.4g wireless...

I noticed my imagebuilder is on 21.02.3. I'm tring 22.03.0-rc4 now.

weiqi-chen avatar Jun 28 '22 02:06 weiqi-chen

I tried imagebuilder 22.03.0-rc4, still no good.

root@OpenWrt:~# iw dev
phy#0
        Interface wlan0
                ifindex 8
                wdev 0x1
                addr cc:40:d0:9c:0c:44
                type managed
                txpower 3.00 dBm
                multicast TXQ:
                        qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol tx-bytes        tx-packets
                        0       0       0       0       0       0       0       0               0


root@OpenWrt:~# dmesg | grep pci
[    2.329732] mt7621-pci 1e140000.pcie: host bridge /pcie@1e140000 ranges:
[    2.343148] mt7621-pci 1e140000.pcie:   No bus range found for /pcie@1e140000, using [bus 00-ff]
[    2.360730] mt7621-pci 1e140000.pcie:      MEM 0x0060000000..0x006fffffff -> 0x0000000000
[    2.377062] mt7621-pci 1e140000.pcie:       IO 0x001e160000..0x001e16ffff -> 0x0000000000
[    2.393531] mt7621-pci 1e140000.pcie: Parsing DT failed
[    2.643767] rt2880-pinmux pinctrl: pcie is already enabled
[    2.654866] mt7621-pci 1e140000.pcie: host bridge /pcie@1e140000 ranges:
[    2.668238] mt7621-pci 1e140000.pcie:   No bus range found for /pcie@1e140000, using [bus 00-ff]
[    2.685770] mt7621-pci 1e140000.pcie:      MEM 0x0060000000..0x006fffffff -> 0x0000000000
[    2.702073] mt7621-pci 1e140000.pcie:       IO 0x001e160000..0x001e16ffff -> 0x0000000000
[    2.718483] mt7621-pci-phy 1e149000.pcie-phy: PHY for 0xbe149000 (dual port = 1)
[    2.733648] mt7621-pci-phy 1e14a000.pcie-phy: PHY for 0xbe14a000 (dual port = 0)
[    2.748746] mt7621-pci 1e140000.pcie: failed to parse bus ranges property: -22
[    2.863422] mt7621-pci-phy 1e149000.pcie-phy: Xtal is 40MHz
[    2.874547] mt7621-pci-phy 1e14a000.pcie-phy: Xtal is 40MHz
[    2.985890] mt7621-pci 1e140000.pcie: pcie1 no card, disable it (RST & CLK)
[    2.999754] mt7621-pci 1e140000.pcie: pcie2 no card, disable it (RST & CLK)
[    3.013627] mt7621-pci 1e140000.pcie: PCIE0 enabled
[    3.023357] mt7621-pci 1e140000.pcie: PCI coherence region base: 0x60000000, mask/settings: 0xf0000002
[    3.042072] mt7621-pci 1e140000.pcie: PCI host bridge to bus 0000:00
[    3.054786] pci_bus 0000:00: root bus resource [io  0x1e160000-0x1e16ffff]
[    3.068497] pci_bus 0000:00: root bus resource [mem 0x60000000-0x6fffffff]
[    3.082204] pci_bus 0000:00: root bus resource [bus 00-ff]
[    3.093147] pci_bus 0000:00: root bus resource [mem 0x60000000-0x6fffffff] (bus address [0x00000000-0x0fffffff])
[    3.113476] pci 0000:00:00.0: [0e8d:0801] type 01 class 0x060400
[    3.125467] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x7fffffff]
[    3.137971] pci 0000:00:00.0: reg 0x14: [mem 0x60200000-0x6020ffff]
[    3.150524] pci 0000:00:00.0: supports D1
[    3.158519] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    3.171935] pci 0000:01:00.0: [14c3:7662] type 00 class 0x028000
[    3.183997] pci 0000:01:00.0: reg 0x10: initial BAR value 0x00000000 invalid
[    3.198076] pci 0000:01:00.0: reg 0x10: [mem size 0x00100000 64bit]
[    3.210603] pci 0000:01:00.0: reg 0x30: initial BAR value 0x00000000 invalid
[    3.224647] pci 0000:01:00.0: reg 0x30: [mem size 0x00010000 pref]
[    3.237065] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
[    3.250859] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[    3.261317] pci 0000:00:00.0:   bridge window [io  0x0000-0x0fff]
[    3.273459] pci 0000:00:00.0:   bridge window [mem 0x60000000-0x600fffff]
[    3.286989] pci 0000:00:00.0:   bridge window [mem 0x60100000-0x601fffff pref]
[    3.301387] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    3.314618] pci 0000:00:00.0: BAR 0: no space for [mem size 0x80000000]
[    3.327800] pci 0000:00:00.0: BAR 0: failed to assign [mem size 0x80000000]
[    3.341672] pci 0000:00:00.0: BAR 8: assigned [mem 0x60000000-0x600fffff]
[    3.355202] pci 0000:00:00.0: BAR 9: assigned [mem 0x60100000-0x601fffff pref]
[    3.369595] pci 0000:00:00.0: BAR 1: assigned [mem 0x60200000-0x6020ffff]
[    3.383132] pci 0000:00:00.0: BAR 7: assigned [io  0x1e160000-0x1e160fff]
[    3.396671] pci 0000:01:00.0: BAR 0: assigned [mem 0x60000000-0x600fffff 64bit]
[    3.411248] pci 0000:01:00.0: BAR 6: assigned [mem 0x60100000-0x6010ffff pref]
[    3.425638] pci 0000:00:00.0: PCI bridge to [bus 01]
[    3.435546] pci 0000:00:00.0:   bridge window [io  0x1e160000-0x1e160fff]
[    3.449069] pci 0000:00:00.0:   bridge window [mem 0x60000000-0x600fffff]
[    3.462597] pci 0000:00:00.0:   bridge window [mem 0x60100000-0x601fffff pref]
[   14.706474] mt7621-pci 1e140000.pcie: bus=1 slot=0 irq=18
[   14.717319] pci 0000:00:00.0: enabling device (0006 -> 0007)

weiqi-chen avatar Jun 28 '22 02:06 weiqi-chen

@WeiqiChenCN Please build source code directly, imagebuilder seems only pack the packages, it won't build dts again.

DragonBluep avatar Jun 29 '22 11:06 DragonBluep

I compiled openwrt by source cdoe. And I noticed that wireless is missing from Network.

Is there some options I not enabled in menuconfig or kernel_menuconfig? Who could help me out :rofl: ?

weiqi-chen avatar Jun 30 '22 04:06 weiqi-chen

@WeiqiChenCN I post a message on openwrt PR, you are right, the fix doesn't works as expected

pierrepinon avatar Jun 30 '22 06:06 pierrepinon

I have a WAC104 and R6220 in my network. It's build on same architecture with same chipsets, the only differences that R6220 have WAN interface and USB port

I have no issue with WAC104 after many reboot or electric issue, the 2.4Ghz card is always up

So, I flash R6220 with WAC104 image, but the issue is always there 😓

pierrepinon avatar Jun 30 '22 06:06 pierrepinon

I compiled openwrt by source cdoe. And I noticed that wireless is missing from Network.

Is there some options I not enabled in menuconfig or kernel_menuconfig? Who could help me out rofl ?

@pierrepinon Do you konw which options/switch to enable wifi drivers or somethings?

weiqi-chen avatar Jun 30 '22 07:06 weiqi-chen

@weiqi-chen follow the build wiki

Don't forgot to download official build config to build system with same official build parameters : https://openwrt.org/docs/guide-developer/toolchain/use-buildsystem

Great day

pierrepinon avatar Jun 30 '22 08:06 pierrepinon

Right now I build new image with some fix pull from wac104 dts file

pierrepinon avatar Jun 30 '22 08:06 pierrepinon

I used this steps to build my image

git clone https://git.openwrt.org/openwrt/openwrt.git src
cd src
git checkout --detach v22.03.0-rc4
#modify: target/linux/ramips/dts/mt7621_netgear_r6220.dts
./scripts/feeds update -a
./scripts/feeds install -a
wget https://downloads.openwrt.org/releases/22.03.0-rc4/targets/ramips/mt7621/config.buildinfo -O .config
make -j $(nproc) defconfig 
make -j $(nproc) menuconfig
make -j $(nproc) world

Still no wireless interfaces...

weiqi-chen avatar Jun 30 '22 17:06 weiqi-chen

Updated:

make distclean
export all_proxy=socks5://rpi-ubuntu:1090
git checkout -- .
./scripts/feeds update -a
./scripts/feeds install -a

wget https://downloads.openwrt.org/releases/22.03.0-rc4/targets/ramips/mt7621/config.buildinfo -O .config

make -j $(nproc) defconfig

make -j $(nproc) download clean world

#flash firmware, then reboot, and reboot again.
#Now I can see wireless(radio0, 5G).

#patch ./target/linux/ramips/dts/mt7621_netgear_r6220.dts

make -j $(nproc) world

#flash firmware, then reboot, and reboot again.
#Still no wireless(radio1, 2.4G).

This patch is not work as expected.


weiqi-chen avatar Jul 02 '22 09:07 weiqi-chen

FYI, when the device is switch off and start after a few minutes, 2.4Ghz pcie card works

pierrepinon avatar Jul 03 '22 19:07 pierrepinon

FYI, when the device is switch off and start after a few minutes, 2.4Ghz pcie card works

But After time of about between a half of a day and a day, the 2.4G wireless is down. And could not start up again.

on Jul  4 17:54:06 2022 user.info : luci: accepted login on / for root from 192.168.10.147
Mon Jul  4 17:54:44 2022 daemon.notice netifd: radio1 (5926): Phy not found
Mon Jul  4 17:54:44 2022 daemon.notice netifd: radio1 (5926): Could not find PHY for device 'radio1'
Mon Jul  4 17:54:44 2022 daemon.notice netifd: Wireless device 'radio1' set retry=0
Mon Jul  4 17:54:44 2022 daemon.crit netifd: Wireless device 'radio1' setup failed, retry=0
Mon Jul  4 17:54:44 2022 daemon.notice netifd: radio1 (5937): WARNING: Variable 'data' does not exist or is not an array/object
Mon Jul  4 17:54:44 2022 daemon.notice netifd: radio1 (5937): Bug: PHY is undefined for device 'radio1'
Mon Jul  4 17:54:44 2022 daemon.notice netifd: Wireless device 'radio1' is now down
Mon Jul  4 17:57:31 2022 daemon.notice netifd: radio1 (6075): Phy not found
Mon Jul  4 17:57:31 2022 daemon.notice netifd: radio1 (6075): Could not find PHY for device 'radio1'
Mon Jul  4 17:57:31 2022 daemon.notice netifd: Wireless device 'radio1' set retry=0
Mon Jul  4 17:57:31 2022 daemon.crit netifd: Wireless device 'radio1' setup failed, retry=0
Mon Jul  4 17:57:31 2022 daemon.notice netifd: radio1 (6086): WARNING: Variable 'data' does not exist or is not an array/object
Mon Jul  4 17:57:31 2022 daemon.notice netifd: radio1 (6086): Bug: PHY is undefined for device 'radio1'
Mon Jul  4 17:57:31 2022 daemon.notice netifd: Wireless device 'radio1' is now down

I'm afraid that I need to switch off the router and wait minutes and turn it back on to make wifi work again...

weiqi-chen avatar Jul 04 '22 18:07 weiqi-chen

@weiqi-chen I doesn’t have the same issue. But can you try to flash your device with WAC104 firmware (with force) ?

pierrepinon avatar Jul 04 '22 18:07 pierrepinon

FYI, when the device is switch off and start after a few minutes, 2.4Ghz pcie card works

This solution works randomly. Sometime it never work, regardless of number of minutes or number of reboots.

gj86 avatar Jul 21 '22 09:07 gj86

Yes. That is a sad story.

weiqi-chen avatar Jul 21 '22 09:07 weiqi-chen

I just tried the last snapshot and I do not reproduce the problem for the moment

pierrepinon avatar Jul 21 '22 12:07 pierrepinon

I just tried the last snapshot and I do not reproduce the problem for the moment

Same for me. Even if the 2.4G not detected, next reboot (without any wait) fixes it.

gj86 avatar Jul 22 '22 03:07 gj86

I just tried the last snapshot and I do not reproduce the problem for the moment

Same for me. Even if the 2.4G not detected, next reboot (without any wait) fixes it.

Spoke too soon. It's same as before, not fixed.

gj86 avatar Jul 22 '22 07:07 gj86

The same issue on one of mine R6220 after upgrading 19.07->22.03 (probably no matter which build). I have to restart several times until 2.4G radio is discovered. Apparently, the 7603 chip disappears on PCIe, It is not visible in dmesg when enumeration is done, thus firmware not loaded. mt7621-pci 1e140000.pcie: pcie2 no card, disable it (RST & CLK)

jacgl avatar Aug 04 '22 13:08 jacgl

@gj86 I have rebooted my device many times (for new settings or by electrical issues) and have no issues with radio 2.4GHZ

Do you have news issues or try new build ?

pierrepinon avatar Aug 04 '22 15:08 pierrepinon

From stock, I tried 21.02.3 yesterday, with 5 or so reboots, powering off for up to 5 mins I could not get my 2.4Ghz radio to show up. I downgraded to 19.07.9 and its been working fine.

kgrodrigues avatar Aug 04 '22 19:08 kgrodrigues

@gj86 I have rebooted my device many times (for new settings or by electrical issues) and have no issues with radio 2.4GHZ

Do you have news issues or try new build ?

The issue is not fixed, tried with August 5 snapshot.

gj86 avatar Aug 05 '22 03:08 gj86