H96 max x3 kernel panic and not work wifi/ethernet

Question

H96 max x3 kernel panic and not work wifi/ethernet

HelferP opened this issue 2 years ago · 32 comments

HelferP commented 2 years ago

Standard chat template, no routine, no chat.
标准聊天模板，无套路不聊天。

Device Information | 设备信息

SOC: [e.g. S905x3]
Model [H96 max x3]

Armbian Version | 系统版本

Kernel Version: [5.15.84]
Release: [jammy]

Describe the bug | 问题描述
Describe the problem in detail and attach screenshots if necessary.
详细描述问题，并在必要时附上屏幕截图。

The first download is good, but WiFi does not work, Ethernet does not receive the DHCP address. After rebooting, I get Kernel Panic and no longer loads. See Screen. I use boot-u-boot-x96maxplus.bin and dtb-meson-sm1-h96-max-x3.dtb
Armbian_23.02.0_amlogic_s905x3_jammy_5.15.84_server_2022.12.21.img.gz

Answer 1 · 2022-12-23T03:13:51.000Z

https://github.com/unifreq/linux-5.15.y/blob/main/arch/arm64/boot/dts/amlogic/meson-sm1-h96-max-x3.dts

jl2101 is support.
Try replacing the kernel with 5.4/5.10

Answer 2 · 2022-12-23T11:53:42.000Z

I re-downloaded the image to SD and replaced in two lines in meson-sm1-h96-max-x3.dtb see screenshot. After that, ethernet was able to get an IP from dhcp. Wi-Fi still does not work, it sees access points, but does not connect to them.

Saw this while uploading:
[ 35.628811] meson-gx-mmc ffe03000.sd: unaligned sg len 552 blksize 512, disabling descriptor DMA for transfer

Reboot also causes kernel panic
Maybe this will help:https://paste.armbian.com/xasidukisu

Answer 3 · 2022-12-24T04:46:30.000Z

https://github.com/unifreq/linux-5.15.y/blob/main/arch/arm64/boot/dts/amlogic/meson-sm1-h96-max-x3.dts

You submit the changes to the upstream kernel source code, so that you can use the correct configuration in the future.
What chip is your wifi.

Answer 4 · 2022-12-24T05:17:18.000Z

Yes, but you still need to remove the line.
For example, you can take the code from HK1. I copied from there.

There are two problems left to solve:

kernel panic after reboot.
wifi

>>What chip is your wifi.
HCY6355

Answer 5 · 2022-12-24T05:26:21.000Z

https://github.com/unifreq/linux-5.15.y/blob/main/arch/arm64/boot/dts/amlogic/meson-sm1-h96-max-x3.dts#L274-L281

I see that there is support for your wifi in the source code.

Kernel panics are individual kernels, right? You can test 5.4/5.10/5.15/6.0.

Submit your changes to the upstream kernel source code, and submit all 4 kernel repositories.
https://github.com/unifreq/linux-5.15.y/blob/main/arch/arm64/boot/dts/amlogic/meson-sm1-h96-max-x3.dts
https://github.com/unifreq/linux-5.10.y/blob/main/arch/arm64/boot/dts/amlogic/meson-sm1-h96-max-x3.dts
https://github.com/unifreq/linux-5.4.y/blob/main/arch/arm64/boot/dts/amlogic/meson-sm1-h96-max-x3.dts
https://github.com/unifreq/linux-6.0.y/blob/main/arch/arm64/boot/dts/amlogic/meson-sm1-h96-max-x3.dts

Answer 6 · 2022-12-24T05:59:14.000Z

>>I see that there is support for your wifi in the source code.
Yes, but for some reason it does not work correctly. Just like ethernet until I fixed the code.

>>You can test 5.4/5.10/5.15/6.0.
I can, but I don't know where to get images with these kernels.

>>Submit your changes to the upstream kernel source code, and submit all 4 kernel repositories.
I'm sorry, but I don't know how to do this.

Answer 7 · 2022-12-24T06:05:38.000Z

https://github.com/ophub/amlogic-s9xxx-armbian#update-armbian-kernel

https://github.com/ophub/kernel/tree/main/pub/stable

armbian-update -k 5.4.228

Answer 8 · 2022-12-24T07:01:50.000Z

meson-sm1-h96-max-x3-oc.dtb.zip

Download, decompress into dtb, overwrite the file with the same name in the /boot/dtb/amlogic directory, restart the test to see if it can start normally, and whether the wired network is normal.

Answer 9 · 2022-12-24T07:23:23.000Z

meson-sm1-h96-max-x3-oc.dtb.zip

not work, only black screen.

Should I replace the boot.sd and boot.usb files?

Answer 10 · 2022-12-24T07:29:43.000Z

No need, just replace dtb
I see that the modification result is the same as your feedback.

Answer 11 · 2022-12-24T07:34:50.000Z

I see that the modification result is the same as your feedback.

Yes, but with this file it doesn't boot

Answer 12 · 2022-12-24T07:51:31.000Z

meson-sm1-h96-max-x3.dtb.zip

try this is 5.15.85 kernel dtb

Answer 13 · 2022-12-24T10:12:30.000Z

try this is 5.15.85 kernel dtb

I tried updating the kernel to 5.15.85 and used this file. ethrnet works, wifi still can't connect to access point. After reboot also kernel panic.

Maybe some logs are needed to understand what could be the problem?

Answer 14 · 2022-12-24T10:49:00.000Z

Update to 5.10/5.4 kernel, and upload this file, try other kernels to see if it works.

Answer 15 · 2022-12-24T12:24:11.000Z

armbian-update -k 5.4.228

You update this kernel. When I submitted the dts modification just now, I found that this was correct before. Try this to see if there is a kernel panic.

Answer 16 · 2022-12-24T12:42:24.000Z

armbian-update -k 5.4.228

You update this kernel. When I submitted the dts modification just now, I found that this was correct before. Try this to see if there is a kernel panic.

Yes, I checked, there is no kernel panic on this kernel. At least it has rebooted several times.
WiFi also can't get ip

Answer 17 · 2022-12-24T12:49:59.000Z

Wired network is normal, use wired

Answer 18 · 2022-12-24T12:56:41.000Z

Wired network is normal, use wired

Bluetooth also finds devices but does not connect to them.

There is no ethernet where I want to use it, only WiFi is possible.

After installing BT in armbian-config, it stopped rebooting, after turning off the power it loads normally. Now I deleted BT and everything is fine again.

Possibly the wrong driver?

Answer 19 · 2022-12-24T13:17:56.000Z

You mean bluetooth is not working but wireless is working?

Answer 20 · 2022-12-24T13:22:52.000Z

You mean bluetooth is not working but wireless is working?

WiFi and Bluetooth find other devices, but cannot connect to them.
Dmesg contain this errors:

Answer 21 · 2022-12-24T13:47:02.000Z

Unable to connect to wireless network in armbian-config? Can't connect using commands? Show me what the error log says.

Answer 22 · 2022-12-24T13:59:10.000Z

dmesg|grep brcm
dmesg|grep Bluetooth

Answer 23 · 2022-12-24T14:00:36.000Z

Unable to connect to wireless network in armbian-config? Can't connect using commands? Show me what the error log says.


Dec 24 20:50:38 armbian NetworkManager[847]: <info>  [1671889838.7434] device
(wlan0): Activation: starting connection 'HOMEWIFI' (e077d37d-dbc9-4fda-8c5f-463f7465f536)
Dec 24 20:50:38 armbian NetworkManager[847]: <info>  [1671889838.7443] audit: op="connection-add-activate" uuid="e077d37d-dbc9-4fda-8c5f-463f7465f536" name="HOMEWIFI" pid=2255 uid=0 result="success"
Dec 24 20:50:38 armbian NetworkManager[847]: <info>  [1671889838.7469] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 24 20:50:38 armbian NetworkManager[847]: <info>  [1671889838.7487] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 24 20:50:38 armbian NetworkManager[847]: <info>  [1671889838.7499] device (wlan0): Activation: (wifi) access point 'HOMEWIFI' has security, but secrets are required.
Dec 24 20:50:38 armbian NetworkManager[847]: <info>  [1671889838.7500] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Dec 24 20:50:38 armbian NetworkManager[847]: <info>  [1671889838.7549] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 24 20:50:38 armbian NetworkManager[847]: <info>  [1671889838.7561] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 24 20:50:38 armbian NetworkManager[847]: <info>  [1671889838.7580] device (wlan0): Activation: (wifi) connection 'HOMEWIFI' has security, and secrets exist.  No new secrets needed.
Dec 24 20:50:38 armbian NetworkManager[847]: <info>  [1671889838.7775] Config: added 'ssid' value 'HOMEWIFI'
Dec 24 20:50:38 armbian NetworkManager[847]: <info>  [1671889838.7776] Config: added 'scan_ssid' value '1'
Dec 24 20:50:38 armbian NetworkManager[847]: <info>  [1671889838.7777] Config: added 'bgscan' value 'simple:30:-70:86400'
Dec 24 20:50:38 armbian NetworkManager[847]: <info>  [1671889838.7777] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Dec 24 20:50:38 armbian NetworkManager[847]: <info>  [1671889838.7778] Config: added 'auth_alg' value 'OPEN'
Dec 24 20:50:38 armbian NetworkManager[847]: <info>  [1671889838.7778] Config: added 'psk' value '<hidden>'
Dec 24 20:50:38 armbian NetworkManager[847]: <info>  [1671889838.8618] device (wlan0): supplicant interface state: disconnected -> scanning
Dec 24 20:50:38 armbian NetworkManager[847]: <info>  [1671889838.8620] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Dec 24 20:50:41 armbian wpa_supplicant[904]: wlan0: Trying to associate with SSID 'HOMEWIFI'
Dec 24 20:50:41 armbian NetworkManager[847]: <info>  [1671889841.7096] device (wlan0): supplicant interface state: scanning -> associating
Dec 24 20:50:41 armbian NetworkManager[847]: <info>  [1671889841.7097] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating
Dec 24 20:50:44 armbian wpa_supplicant[904]: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16
Dec 24 20:50:44 armbian NetworkManager[847]: <info>  [1671889844.4310] device (wlan0): supplicant interface state: associating -> disconnected
Dec 24 20:50:44 armbian NetworkManager[847]: <info>  [1671889844.4312] device (p2p-dev-wlan0): supplicant management interface state: associating -> disconnected
Dec 24 20:50:44 armbian NetworkManager[847]: <info>  [1671889844.5357] device (wlan0): supplicant interface state: disconnected -> scanning
Dec 24 20:50:44 armbian NetworkManager[847]: <info>  [1671889844.5358] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Dec 24 20:50:47 armbian wpa_supplicant[904]: wlan0: Trying to associate with SSID 'HOMEWIFI'
Dec 24 20:50:47 armbian NetworkManager[847]: <info>  [1671889847.2858] device (wlan0): supplicant interface state: scanning -> associating
Dec 24 20:50:47 armbian NetworkManager[847]: <info>  [1671889847.2860] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating
Dec 24 20:50:49 armbian wpa_supplicant[904]: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16
Dec 24 20:50:49 armbian NetworkManager[847]: <info>  [1671889849.9508] device (wlan0): supplicant interface state: associating -> disconnected
Dec 24 20:50:49 armbian NetworkManager[847]: <info>  [1671889849.9510] device (p2p-dev-wlan0): supplicant management interface state: associating -> disconnected
Dec 24 20:50:50 armbian NetworkManager[847]: <info>  [1671889850.4456] device (wlan0): supplicant interface state: disconnected -> scanning
Dec 24 20:50:50 armbian NetworkManager[847]: <info>  [1671889850.4457] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Dec 24 20:50:53 armbian wpa_supplicant[904]: wlan0: Trying to associate with SSID 'HOMEWIFI'
Dec 24 20:50:53 armbian NetworkManager[847]: <info>  [1671889853.2191] device (wlan0): supplicant interface state: scanning -> associating
Dec 24 20:50:53 armbian NetworkManager[847]: <info>  [1671889853.2193] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating
Dec 24 20:50:55 armbian wpa_supplicant[904]: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16
Dec 24 20:50:55 armbian NetworkManager[847]: <info>  [1671889855.8909] device (wlan0): supplicant interface state: associating -> disconnected
Dec 24 20:50:55 armbian NetworkManager[847]: <info>  [1671889855.8910] device (p2p-dev-wlan0): supplicant management interface state: associating -> disconnected
Dec 24 20:50:56 armbian NetworkManager[847]: <info>  [1671889856.9488] device (wlan0): supplicant interface state: disconnected -> scanning
Dec 24 20:50:56 armbian NetworkManager[847]: <info>  [1671889856.9489] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Dec 24 20:50:59 armbian wpa_supplicant[904]: wlan0: Trying to associate with SSID 'HOMEWIFI'
Dec 24 20:50:59 armbian NetworkManager[847]: <info>  [1671889859.6681] device (wlan0): supplicant interface state: scanning -> associating
Dec 24 20:50:59 armbian NetworkManager[847]: <info>  [1671889859.6682] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating
Dec 24 20:51:02 armbian wpa_supplicant[904]: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16
Dec 24 20:51:02 armbian wpa_supplicant[904]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="HOMEWIFI" auth_failures=1 duration=10 reason=CONN_FAILED
Dec 24 20:51:02 armbian NetworkManager[847]: <info>  [1671889862.3476] device (wlan0): supplicant interface state: associating -> disconnected
Dec 24 20:51:02 armbian NetworkManager[847]: <info>  [1671889862.3478] device (p2p-dev-wlan0): supplicant management interface state: associating -> disconnected
Dec 24 20:51:03 armbian NetworkManager[847]: <warn>  [1671889863.9291] device (wlan0): Activation: (wifi) association took too long
Dec 24 20:51:03 armbian NetworkManager[847]: <info>  [1671889863.9292] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Dec 24 20:51:03 armbian NetworkManager[847]: <warn>  [1671889863.9308] device (wlan0): Activation: (wifi) asking for new secrets
Dec 24 20:51:03 armbian NetworkManager[847]: <warn>  [1671889863.9320] device (wlan0): no secrets: No agents were available for this request.
Dec 24 20:51:03 armbian NetworkManager[847]: <info>  [1671889863.9322] device (wlan0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Dec 24 20:51:03 armbian NetworkManager[847]: <warn>  [1671889863.9343] device (wlan0): Activation: failed for connection 'HOMEWIFI'
Dec 24 20:51:03 armbian NetworkManager[847]: <info>  [1671889863.9356] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Dec 24 20:51:10 armbian NetworkManager[847]: <info>  [1671889870.3403] device (wlan0): supplicant interface state: disconnected -> inactive
Dec 24 20:51:10 armbian NetworkManager[847]: <info>  [1671889870.3404] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> inactive

Answer 24 · 2022-12-24T14:02:13.000Z

dmesg|grep brcm
dmesg|grep Bluetooth

Answer 25 · 2022-12-24T14:13:28.000Z

There are still such errors on the boot:

Answer 26 · 2022-12-25T05:35:01.000Z

From the log, your wireless and bluetooth are normally driven

Answer 27 · 2022-12-25T16:48:07.000Z

You're right. I found the wifi issue.
It was in setting my router to openwrt. Because of this setting, the box did not connect, while the rest of the devices, including the Raspberry Pi Zero W, work fine. In the picture is the line that caused the problem, it need delete:

I also think I solved the kernel panic problem on the 5.15.y kernel. I compared two dts from 5.4.228 and 5.15.85, found a discrepancy, added them in 5.15.85 and now I don't get kernel panic on reboot.
Add in opp-table from 5.5.228 dtb

	       opp-100000000 {
			status = "disabled";
		};

		opp-250000000 {
			status = "disabled";
		};

		opp-500000000 {
			status = "disabled";
		};

		opp-750000000 {
			opp-hz = <0x00 0x2cb41780>;
			opp-microvolt = <0xb71b0>;
		};

I'm still testing this and not completely sure.

Thank you very much for your help and great work!!!

Answer 28 · 2022-12-26T02:12:49.000Z

Ok, your tweak feedback has been submitted to the kernel repository

Answer 29 · 2022-12-26T06:12:56.000Z

added them in 5.15.85 and now I don't get kernel panic on reboot.

can u show ur box's cpufreq-info here?

Answer 30 · 2022-12-27T09:57:22.000Z

added them in 5.15.85 and now I don't get kernel panic on reboot.

can u show ur box's cpufreq-info here?


cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 50.0 us.
  hardware limits: 750 MHz - 1.91 GHz
  available frequency steps: 750 MHz, 1000 MHz, 1.20 GHz, 1.40 GHz, 1.50 GHz, 1.61 GHz, 1.70 GHz, 1.80 GHz, 1.91 GHz
  available cpufreq governors: userspace, conservative, powersave, ondemand, performance, schedutil
  current policy: frequency should be within 1.40 GHz and 1.91 GHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency is 1.91 GHz (asserted by call to hardware).
analyzing CPU 1:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 50.0 us.
  hardware limits: 750 MHz - 1.91 GHz
  available frequency steps: 750 MHz, 1000 MHz, 1.20 GHz, 1.40 GHz, 1.50 GHz, 1.61 GHz, 1.70 GHz, 1.80 GHz, 1.91 GHz
  available cpufreq governors: userspace, conservative, powersave, ondemand, performance, schedutil
  current policy: frequency should be within 1.40 GHz and 1.91 GHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency is 1.40 GHz (asserted by call to hardware).
analyzing CPU 2:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 50.0 us.
  hardware limits: 750 MHz - 1.91 GHz
  available frequency steps: 750 MHz, 1000 MHz, 1.20 GHz, 1.40 GHz, 1.50 GHz, 1.61 GHz, 1.70 GHz, 1.80 GHz, 1.91 GHz
  available cpufreq governors: userspace, conservative, powersave, ondemand, performance, schedutil
  current policy: frequency should be within 1.40 GHz and 1.91 GHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency is 1.40 GHz (asserted by call to hardware).
analyzing CPU 3:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 50.0 us.
  hardware limits: 750 MHz - 1.91 GHz
  available frequency steps: 750 MHz, 1000 MHz, 1.20 GHz, 1.40 GHz, 1.50 GHz, 1.61 GHz, 1.70 GHz, 1.80 GHz, 1.91 GHz
  available cpufreq governors: userspace, conservative, powersave, ondemand, performance, schedutil
  current policy: frequency should be within 1.40 GHz and 1.91 GHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency is 1.40 GHz (asserted by call to hardware).

Answer 31 · 2022-12-27T10:21:13.000Z

Ok, your tweak feedback has been submitted to the kernel repository

Tested for several days. After a while, I tried to reboot the device and got the kernel panic again. Now additionally disabled frequencies higher than the maximum specified in the processor specification. I've been testing for a day and have never received a kernel panic yet.

		opp-100000000 {
			status = "disabled";
		};

		opp-250000000 {
			status = "disabled";
		};

		opp-500000000 {
			status = "disabled";
		};

		opp-750000000 {
			opp-hz = <0x00 0x2cb41780>;
			opp-microvolt = <0xb71b0>;
		};

		opp-2016000000 {
			status = "disabled";
		};

		opp-2100000000 {
			status = "disabled";
					};

Answer 32 · 2023-03-26T04:31:03.000Z

ubuntu 18是哪个版本支持的，请问历史版本去哪里下载