Jump to content
  • 0

Orange Pi3 lts


igorh
 Share

Question

Recommended Posts

  • 0
On 4/18/2022 at 3:45 PM, pierre-pret said:

When I start the hotspot, it stays on for about a minute. If it doesn't crash, this command does a WiFi scan and instantly crashes it: iw dev wlan0 scan

 

It turns out this isn't a problem with the Armbian image. I used the orangepi-config utility on official orange PI debian image to generate a WiFi hostapd.conf file.  I then copied this hostapd.conf file into armbian and the WiFI hotspot works without any firmware crashes. You can see the config file here:

 

https://github.com/orangepi-xunlong/firmware/issues/1

Link to comment
Share on other sites

Donate and support the project!

  • 0

What I did notice when using the Armbian build compared to the official Orange PI 3 LTS Debian build is that sometimes when I use "sudo reboot" the Armbian system wouldn't come back online.  Other times the ETH port lights doesn't come on and doesn't work when the system starts up.  There seems to be some extra u-boot config needed in the Armbian build to reliably reboot.  I see this is a fairly common problem that happened with many other Orange PI boards on Armbian and have been fixed.

Link to comment
Share on other sites

  • 0
On 4/19/2022 at 9:54 PM, pierre-pret said:

What I did notice when using the Armbian build compared to the official Orange PI 3 LTS Debian build is that sometimes when I use "sudo reboot" the Armbian system wouldn't come back online.  Other times the ETH port lights doesn't come on and doesn't work when the system starts up.  There seems to be some extra u-boot config needed in the Armbian build to reliably reboot.  I see this is a fairly common problem that happened with many other Orange PI boards on Armbian and have been fixed.

Any idea about solution?

Link to comment
Share on other sites

  • 0

Hi everyone. 

I am really sorry I haven't been very active since initial release. 

I have a few issue at home with the family, and haven't been able to do anything at all.

I will be back on this VERY soon. 

Please watch this space!

Link to comment
Share on other sites

  • 0

As promised, I tested the gpio. I2c is fine but there is a problem with spi. Default, cs pin is not working. This is how I changed the overlay file. It works flawlessly.

Spoiler

diff --git a/arch/arm64/boot/dts/allwinner/overlay/sun50i-h6-spi-spidev1.dts b/arch/arm64/boot/dts/allwinner/overlay/sun50i-h6-spi-spidev1.dts
index aee7da0a6..db0b1fdda 100644
--- a/arch/arm64/boot/dts/allwinner/overlay/sun50i-h6-spi-spidev1.dts
+++ b/arch/arm64/boot/dts/allwinner/overlay/sun50i-h6-spi-spidev1.dts
@@ -17,7 +17,7 @@ fragment@1 {
         target = <&spi1>;
         __overlay__ {
             pinctrl-names = "default";
-            pinctrl-0 = <&spi1_pins>;
+            pinctrl-0 = <&spi1_pins> , <&spi1_cs_pin>;
             status = "okay";
             #address-cells = <1>;
             #size-cells = <0>;

 

Link to comment
Share on other sites

  • 0

Tried to build Armbian for opi 3 lts from git and i get error:

AR      drivers/net/built-in.a
  AR      drivers/built-in.a
  GEN     .version
  CHK     include/generated/compile.h
  LD      vmlinux.o
  MODPOST vmlinux.symvers
  MODINFO modules.builtin.modinfo
  GEN     modules.builtin
  LD      .tmp_vmlinux.kallsyms1
[ error ] ERROR in function compile_kernel [ main.sh:589 -> main.sh:490 -> compilation.sh:507 -> general.sh:0 ]
[ error ] Kernel was not built [ @host ]


Debian 11 server normal

Link to comment
Share on other sites

  • 0

 

Hello, friends.

When trying to connect to WiFi, it gives a message:

"Could not activate connection: Activation failed: The Wi-Fi network could not be found"

At the same time, he sees the Wi-Fi network.

OrangePi 3LTS v1.4.

 

Armbian nightly build from 04/25/2022

 

In which direction to dig?

Edited by awolfman
Link to comment
Share on other sites

  • 0
4 hours ago, awolfman said:

Hello, friends.

When trying to connect to WiFi, it gives a message:

"Could not activate connection: Activation failed: The Wi-Fi network could not be found"

At the same time, he sees the Wi-Fi network.

OrangePi 3LTS v1.4.

 

Try connecting from the official Orange PI Debian image to see if it's an Armbian issue or not.

Link to comment
Share on other sites

  • 0
19 часов назад, pierre-pret сказал:

 

Try connecting from the official Orange PI Debian image to see if it's an Armbian issue or not.

 

Orangepi3-lts Debian kernel 5.10, wifi connection working.

 

On Armbian, when connected to Wi-Fi, the following messages appear: 

WCN_ERR: chip reset & notify every subsystem....

sdiohal err:sdiohal_aonwriteb xmit_cnt:0 xmit_start:0, not have card

Link to comment
Share on other sites

  • 0

dmesg | grep 'WCN\|wlan0'
 

Скрытый текст

[    5.024533] WCN: marlin_init entry!
[    5.025123] WCN: wcn config bt wake host
[    5.025412] WCN_ERR: dts node for bt_wake not found
[    5.025420] WCN: marlin2 parse_dt some para not config
[    5.031015] WCN: marlin_probe ok!
[    5.042118] WCN: marlin power state:0, subsys: [MARLIN_BLUETOOTH] power 0
[    5.141270] WCN: start_marlin [MARLIN_WIFI]
[    5.141294] WCN: marlin power state:0, subsys: [MARLIN_WIFI] power 1
[    5.141301] WCN: the first power on start
[    5.245422] WCN: marlin chip en dummy pull up -- need manually set GPIO  
[    5.273758] WCN: marlin_scan_finish!
[    5.273923] WCN: then marlin start to download
[    5.274151] WCN: marlin_get_wcn_chipid: chipid: 0x2355b001
[    5.274164] WCN: marlin_request_firmware from /lib/firmware/wcnmodem.bin start!
[    6.125631] WCN: combin_img 0 marlin_firmware_write finish and successful
[    6.126196] WCN: marlin_start_run read reset reg val:0x1
[    6.126227] WCN: after do marlin_start_run reset reg val:0x0
[    6.126453] WCN: s_marlin_bootup_time=6126452559
[    6.133167] WCN: clock mode: TSX
[    6.133467] WCN: marlin_write_cali_data sync init_state:0x128002b5
[    6.161797] WCN: marlin_write_cali_data sync init_state:0x128002b5
[    6.189958] WCN: marlin_write_cali_data sync init_state:0xf0f0f0f1
[    6.189981] WCN: sdio_config bt_wake_host trigger:[high]
[    6.189984] WCN: sdio_config irq:[inband]
[    6.189986] WCN: sdio_config wake_host_level_duration_time:[20ms]
[    6.189989] WCN: sdio_config wake_host_data_separation:[bt/wifi reuse]
[    6.189991] WCN: marlin_send_sdio_config_to_cp sdio_config:0x80f01 (enable config)
[    6.190404] WCN: marlin_write_cali_data finish
[    6.190600] WCN: check_cp_ready sync val:0xf0f0f0f2, prj_type val:0x0
[    6.217795] WCN: check_cp_ready sync val:0xf0f0f0f2, prj_type val:0x0
[    6.245643] WCN: check_cp_ready sync val:0xf0f0f0f2, prj_type val:0x0
[    6.273771] WCN: check_cp_ready sync val:0xf0f0f0f2, prj_type val:0x0
[    6.301614] WCN: check_cp_ready sync val:0xf0f0f0f6, prj_type val:0x0
[    6.301640] WCN: marlin_bind_verify confuse data: 0xcfe38251b04db73419dc5cae40581e72
[    6.301659] WCN: marlin_bind_verify verify data: 0x1ed7454972563e2294bc7cf590020acc
[    6.302202] WCN: check_cp_ready sync val:0xf0f0f0f7, prj_type val:0x0
[    6.329841] WCN: check_cp_ready sync val:0xf0f0f0ff, prj_type val:0x0
[    6.330017] WCN: get_cp2_version entry!
[    6.369055] WCN: WCND at cmd read:WCN_VER:Platform Version:MARLIN3_19B_W20.37.4~Project Version:sc2355_marlin3_lite_ott~09-11-2020
21:27:32~
[    6.369088] WCN: switch_cp2_log - close entry!
[    6.370375] WCN: WCND at cmd read:OK
[    6.370408] WCN: then marlin download finished and run ok
[    6.370422] WCN: start_loopcheck
[    6.370439] WCN: marlin power state:4, subsys: [MARLIN_BLUETOOTH] power 0
[    6.370449] WCN: can not power off, other module is on
[    6.383562] WCN: get_board_ant_num [one_ant]
[    6.444643] unisoc_wifi unisoc_wifi wlan0: mixed HW and IP checksum settings.
[   15.251502] WCN: mdbg_assert_read:WCN Assert in connect/source/wifi/rom/mac/cmd/cmd_tx_rom.c line 5111, 0,data length 128
[   15.251527] WCN: stop_loopcheck
[   15.251536] WCN_ERR: chip reset & notify every subsystem...
[   15.257474] WCN: [marlin_cp2_reset], DO BSP RESET
[   15.257485] WCN: marlin power state:4, subsys: [MARLIN_WIFI] power 0
[   15.257492] WCN: wcn chip start power off!
[   15.257592] WCN: chip_power_off
[   15.257595] WCN: marlin chip en dummy pull down -- need manually set GPIO  
[   15.257599] WCN: marlin power off!
[   15.257601] WCN: marlin power state:0, subsys: [MARLIN_BLUETOOTH] power 0

 


 

Link to comment
Share on other sites

  • 0
On 4/29/2022 at 6:46 AM, awolfman said:

rangepi3-lts Debian kernel 5.10, wifi connection working.

 

On Armbian, when connected to Wi-Fi, the following messages appear: 

 

 

Since others are reporting the WiFi as working (including myself) I would say the next step is to try and connect to a different WiFi network from Armbian to see if you get the same error.  This specific WiFi network might be using hardware support that doesn't currently work in Armbian with the OPI3 LTS.  Knowing what hardware feature makes it fail will be very helpful.  If a different WiFi network (such as phone hotspot) works then it's a good starting point to determining what fails exactly.

Link to comment
Share on other sites

  • 0
3 часа назад, pierre-pret сказал:

 

Since others are reporting the WiFi as working (including myself) I would say the next step is to try and connect to a different WiFi network from Armbian to see if you get the same error.  This specific WiFi network might be using hardware support that doesn't currently work in Armbian with the OPI3 LTS.  Knowing what hardware feature makes it fail will be very helpful.  If a different WiFi network (such as phone hotspot) works then it's a good starting point to determining what fails exactly.

Did an experiment: On the phone (I have Honor 20) I turned on the 2.4 GHz hotspot. Through armbian-config, I tried to connect to it and received the same message as before, while it looks like the chip responsible for Wi-Fi turned off, because. other Wi-Fi access points are no longer detected. Judging by the log, this is indeed the case.

dmesg | grep 'WCN\|wlan0':
 

Скрытый текст

[    5.071526] WCN: marlin_init entry!
[    5.072000] WCN: wcn config bt wake host
[    5.072222] WCN_ERR: dts node for bt_wake not found
[    5.072226] WCN: marlin2 parse_dt some para not config
[    5.080860] WCN: marlin_probe ok!
[    5.091684] WCN: marlin power state:0, subsys: [MARLIN_BLUETOOTH] power 0
[    5.189864] WCN: start_marlin [MARLIN_WIFI]
[    5.189888] WCN: marlin power state:0, subsys: [MARLIN_WIFI] power 1
[    5.189896] WCN: the first power on start
[    5.297339] WCN: marlin chip en dummy pull up -- need manually set GPIO  
[    5.329628] WCN: marlin_scan_finish!
[    5.329772] WCN: then marlin start to download
[    5.330114] WCN: marlin_get_wcn_chipid: chipid: 0x2355b001
[    5.330127] WCN: marlin_request_firmware from /lib/firmware/wcnmodem.bin start!
[    6.180667] WCN: combin_img 0 marlin_firmware_write finish and successful
[    6.180986] WCN: marlin_start_run read reset reg val:0x1
[    6.181000] WCN: after do marlin_start_run reset reg val:0x0
[    6.181213] WCN: s_marlin_bootup_time=6181212725
[    6.189100] WCN: clock mode: TSX
[    6.189389] WCN: marlin_write_cali_data sync init_state:0xb9005e80
[    6.217641] WCN: marlin_write_cali_data sync init_state:0xb9005e80
[    6.245793] WCN: marlin_write_cali_data sync init_state:0xf0f0f0f1
[    6.245816] WCN: sdio_config bt_wake_host trigger:[high]
[    6.245818] WCN: sdio_config irq:[inband]
[    6.245821] WCN: sdio_config wake_host_level_duration_time:[20ms]
[    6.245824] WCN: sdio_config wake_host_data_separation:[bt/wifi reuse]
[    6.245826] WCN: marlin_send_sdio_config_to_cp sdio_config:0x80f01 (enable config)
[    6.247561] WCN: marlin_write_cali_data finish
[    6.247757] WCN: check_cp_ready sync val:0xf0f0f0f2, prj_type val:0x0
[    6.273558] WCN: check_cp_ready sync val:0xf0f0f0f2, prj_type val:0x0
[    6.301524] WCN: check_cp_ready sync val:0xf0f0f0f2, prj_type val:0x0
[    6.329561] WCN: check_cp_ready sync val:0xf0f0f0f2, prj_type val:0x0
[    6.357545] WCN: check_cp_ready sync val:0xf0f0f0f2, prj_type val:0x0
[    6.389597] WCN: check_cp_ready sync val:0xf0f0f0f6, prj_type val:0x0
[    6.389623] WCN: marlin_bind_verify confuse data: 0xf71c8447f73048472ce84dba1253605a
[    6.389641] WCN: marlin_bind_verify verify data: 0xa4eb5eda181e56a4c79873c0e84c8018
[    6.390274] WCN: check_cp_ready sync val:0xf0f0f0f7, prj_type val:0x0
[    6.417691] WCN: check_cp_ready sync val:0xf0f0f0ff, prj_type val:0x0
[    6.417874] WCN: get_cp2_version entry!
[    6.456914] WCN: WCND at cmd read:WCN_VER:Platform Version:MARLIN3_19B_W20.37.4~Project Version:sc2355_marlin3_lite_ott~09-11-2020
21:27:32~
[    6.456977] WCN: switch_cp2_log - close entry!
[    6.458232] WCN: WCND at cmd read:OK
[    6.458277] WCN: then marlin download finished and run ok
[    6.458290] WCN: start_loopcheck
[    6.458306] WCN: marlin power state:4, subsys: [MARLIN_BLUETOOTH] power 0
[    6.458319] WCN: can not power off, other module is on
[    6.476390] WCN: get_board_ant_num [one_ant]
[    6.538484] unisoc_wifi unisoc_wifi wlan0: mixed HW and IP checksum settings.
[   14.784577] WCN: mdbg_assert_read:WCN Assert in connect/source/wifi/rom/mac/cmd/cmd_tx_rom.c line 5111, 0,data length 128
[   14.784602] WCN: stop_loopcheck
[   14.784608] WCN_ERR: chip reset & notify every subsystem...
[   14.790374] WCN: [marlin_cp2_reset], DO BSP RESET
[   14.790382] WCN: marlin power state:4, subsys: [MARLIN_WIFI] power 0
[   14.790390] WCN: wcn chip start power off!
[   14.790516] WCN: chip_power_off
[   14.790520] WCN: marlin chip en dummy pull down -- need manually set GPIO  
[   14.790524] WCN: marlin power off!
[   14.790526] WCN: marlin power state:0, subsys: [MARLIN_BLUETOOTH] power 0


A similar situation when working through wpa_supplicant.

After restarting OrangePi 3 LTS, Wi-Fi hotspots are again visible to the device.

Link to comment
Share on other sites

  • 0
On 4/28/2022 at 3:28 AM, Kamileon said:

Tried to build Armbian for opi 3 lts from git and i get error:

AR      drivers/net/built-in.a
  AR      drivers/built-in.a
  GEN     .version
  CHK     include/generated/compile.h
  LD      vmlinux.o
  MODPOST vmlinux.symvers
  MODINFO modules.builtin.modinfo
  GEN     modules.builtin
  LD      .tmp_vmlinux.kallsyms1
[ error ] ERROR in function compile_kernel [ main.sh:589 -> main.sh:490 -> compilation.sh:507 -> general.sh:0 ]
[ error ] Kernel was not built [ @host ]


Debian 11 server normal

There is an issue filed for this on github.  Use edge to build a new image.  I am currently running edge with a btrfs filesystem from yesterday.

Link to comment
Share on other sites

  • 0
On 4/19/2022 at 8:54 PM, pierre-pret said:

What I did notice when using the Armbian build compared to the official Orange PI 3 LTS Debian build is that sometimes when I use "sudo reboot" the Armbian system wouldn't come back online.  Other times the ETH port lights doesn't come on and doesn't work when the system starts up.  There seems to be some extra u-boot config needed in the Armbian build to reliably reboot.  I see this is a fairly common problem that happened with many other Orange PI boards on Armbian and have been fixed.

 

On 4/22/2022 at 9:14 AM, Eemeien said:

Any idea about solution?

 

Here are some cases where a board wouldn't reboot, then after a fix it can reboot consistently:

https://github.com/armbian/build/pull/3241

https://github.com/armbian/build/pull/3143

https://github.com/armbian/build/pull/3238/commits/362008cfb7b586abbba6330ce1a3b25846d89b68

 

I'm not sure exactly what needs to be changed, but the answer should be in this commit somewhere, as reboot works fine on the official orange PI debian:

https://github.com/orangepi-xunlong/orangepi-build/commit/9f400f169d4f6c5ee01d4faa31417937e2148b86

 

We will probably have to wait for @Ukhellfire to have free time and energy to spend on this. Unless someone else has an idea of how to fix it?  If an Armbian maintainer is willing to spend time on this, I'll be happy to place an order for an Orange PI 3 LTS to ship to them.

 

Link to comment
Share on other sites

  • 0

Hi all.

 

First I'd like to thanks @Ukhellfire for his work to support this board. I'm using his (?) desktop build of armbian, but just found a kind of odd problem. My use case is very simple, as I mainly use the board as kind of remote serial console server. I don't need the desktop environment so I just disabled it with a systemctl disable lightdm and everything seemed fine. But as soon as I turned off the TV where the board is connected, CPU usage went to ~50% and "top" showed this:

 

  248 root     -51   0       0      0      0 R  52.8   0.0  86:15.97 irq/46-6000000 

 

it seems that irq 46 is related the the HDMI:

 

ls /proc/irq/46/
6000000.hdmi  affinity_hint  dw-hdmi-cec  effective_affinity  effective_affinity_list  node  smp_affinity  smp_affinity_list  spurious

 

If I boot the board without a HDMI connection everything seems fine.... So the problem only happens when the HDMI is connected and the tv/monitor is off! I can live with it, but may be bother someone else, so I'm reporting it.

 

On a side note, what is the expected load average when the board is on, but doing nothing? I'm getting a constant load around 1.10.

Link to comment
Share on other sites

  • 0

Hi folks! I'm sorry to interrupt the conversation, but I encountered a strange error. I burn image "Armbian_22.08.0-trunk.0001_Orangepi3-lts_jammy_edge_5.17.11.img.xz" and a LAN doesn't work (no internet, no LED's on the network connector). I see message on boot: "stmmac_open: cannot attach to phy (error: -19)" Original Orange Pi 3 LTS Android image (pre-installed) works normal. Board connecter LAN RJ-45 cat 5 to router Asus AX88U. How to fix it? Thanks

Link to comment
Share on other sites

  • 0
On 6/8/2022 at 3:24 AM, Armael said:

Hi folks! I'm sorry to interrupt the conversation, but I encountered a strange error. I burn image "Armbian_22.08.0-trunk.0001_Orangepi3-lts_jammy_edge_5.17.11.img.xz" and a LAN doesn't work (no internet, no LED's on the network connector). I see message on boot: "stmmac_open: cannot attach to phy (error: -19)" Original Orange Pi 3 LTS Android image (pre-installed) works normal. Board connecter LAN RJ-45 cat 5 to router Asus AX88U. How to fix it? Thanks

I got the same problem. It's self-built image from 22.08.0-trunk,kernel version 5.15.46. I don't have ethernet cable plugged but dmesg is still spamming the log and it seems eat some CPU.

"

[  628.056717] dwmac-sun8i 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[  628.074771] dwmac-sun8i 5020000.ethernet eth0: no phy at addr -1

"

Link to comment
Share on other sites

  • 0
3 hours ago, EBK21 said:

I got the same problem. It's self-built image from 22.08.0-trunk,kernel version 5.15.46. I don't have ethernet cable plugged but dmesg is still spamming the log and it seems eat some CPU.

"

[  628.056717] dwmac-sun8i 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[  628.074771] dwmac-sun8i 5020000.ethernet eth0: no phy at addr -1

"

Can confirm the ethernet is not working. No leds after plugged in.

Link to comment
Share on other sites

  • 0
On 6/8/2022 at 3:24 AM, Armael said:

Hi folks! I'm sorry to interrupt the conversation, but I encountered a strange error. I burn image "Armbian_22.08.0-trunk.0001_Orangepi3-lts_jammy_edge_5.17.11.img.xz" and a LAN doesn't work (no internet, no LED's on the network connector). I see message on boot: "stmmac_open: cannot attach to phy (error: -19)" Original Orange Pi 3 LTS Android image (pre-installed) works normal. Board connecter LAN RJ-45 cat 5 to router Asus AX88U. How to fix it? Thanks

Workaround is found. It's literaly a copypaste based on https://github.com/u-boot/u-boot/commit/a246e21351778a93805b3f52302a420f4b268601#diff-ccc56a581b4ac88eb0c52ec34ef3ede020bd4deaff8ab53d3fdcfa85d8438b38


Decompile the dtb,find and do the following.

 

BEGIN

                ethernet@5020000 {
                        compatible = "allwinner,sun50i-h6-emac\0allwinner,sun50i-a64-emac";
                        syscon = <0x30>;
                        reg = <0x5020000 0x10000>;
                        interrupts = <0x00 0x0c 0x04>;
                        interrupt-names = "macirq";
                        resets = <0x04 0x21>;
                        reset-names = "stmmaceth";
                        clocks = <0x04 0x54>;
                        clock-names = "stmmaceth";
                        status = "okay";
                        pinctrl-names = "default";
                        pinctrl-0 = <0x31>;
                        phy-mode = "rgmii-id";
                        phy-handle = <0x32>;
                        phy-supply = <0x33>;

#Add the following entries
                        snps,reset-gpio = <0x1f 0x03 0x0e 0x01>;
                        snps,reset-delays-us = <0 10000 1000000>;
                        snps,reset-active-low;

#End adding
                        allwinner,rx-delay-ps = <0xc8>;
                        allwinner,tx-delay-ps = <0x12c>;
                        phandle = <0x76>;

                        mdio {
                                compatible = "snps,dwmac-mdio";
                                #address-cells = <0x01>;
                                #size-cells = <0x00>;
                                phandle = <0x77>;

                                ethernet-phy@1 {
                                        compatible = "ethernet-phy-ieee802.3-c22";
                                        reg = <0x01>;

#Comment out the following entries
                                        #reset-gpios = <0x1f 0x03 0x0e 0x01>;
                                        #reset-assert-us = <0x3a98>;
                                        #reset-deassert-us = <0x9c40>;

#End commenting
                                        phandle = <0x32>;
                                };
                        };
                };

END

Link to comment
Share on other sites

  • 0
46 minutes ago, EBK21 said:

Workaround is found. It's literaly a copypaste based on https://github.com/u-boot/u-boot/commit/a246e21351778a93805b3f52302a420f4b268601#diff-ccc56a581b4ac88eb0c52ec34ef3ede020bd4deaff8ab53d3fdcfa85d8438b38


Decompile the dtb,find and do the following.

 

Please make a pull request. I just made my first pull request to fix Bluetooth here: https://github.com/armbian/build/pull/3896

Link to comment
Share on other sites

  • 0
18 minutes ago, pierre-pret said:

 

Please make a pull request. I just made my first pull request to fix Bluetooth here: https://github.com/armbian/build/pull/3896

I actually don't know how to do it without affect other boards. The orangepi3 lts support patch seems use shared dts include files.
 

I didn't find other information related to the problem.It seems only happens on pi3lts which uses this new ethernet chip.

Edited by EBK21
update
Link to comment
Share on other sites

  • 0

Does the ethernet chip/driver supports only polling mode?

This is really wasting a lot of cpu cycles.

 

Well. From the driver,only polling mode is supported😢

Edited by EBK21
update
Link to comment
Share on other sites

  • 0

Hi!
Does anybody know how to downgrade kernel from 5.15 (or higher) to 5.4.
I have tryed armbian-config (System-other- kernel 5.4) but when it reboot, orange does not boot again.
May be there is another way? May be anyone has an img or iso with kernel 5.4 to flash it?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...