Jump to content

3735943886

Members
  • Posts

    17
  • Joined

  • Last visited

  1. armbian-config seems to be under major modification currently. you may have to set up hotspot manually in case that armbian-config doesn't work.
  2. Try downgrade kernel version via armbian-config. My board(not orangepi tho) also had a kernel issue and it was gone after downgrade kernel version to 5.10
  3. NanoPi R4s, enp1s0 ethernet device not showed up after reboot - Beginners - armbian forum
  4. I upgraded my Nanopi from buster to bullseye recently. It looks like that your armbian version is not up to date. And please check your armbian.list is also pointing bullseye.
  5. Hello, I’m running nanopi r4s with armbian 22.02.1 bullseye. After finishing edit /etc/network/interfaces via armbian-config, there was an error while restarting services. Fail to stop network-manager.service: Unit network-manager.service not loaded. However, for bullseye, network-manager.service might be no longer available.
  6. I tested with 4 archived images today. GOOD is enp1s0 works fine with warm reboot. BAD is enp1s0 works only after cold boot. Armbian_20.11.10_Nanopi-r4s_focal_current_5.9.14.img.xz :GOOD Armbian_21.08.1_Nanopi-r4s_bullseye_current_5.10.60.img.xz :GOOD Armbian_21.08.1_Nanopi-r4s_hirsute_edge_5.13.12.img.xz :BAD Armbian_22.02.1_Nanopi-r4s_jammy_edge_5.16.11.img.xz :BAD and current my system is Armbian 22.02.1 with bullseye 5.15.25 :BAD So I think, Armbian version does not matter. Debian (or ubuntu) version does not matter, either. Kernel version (5.13 and above) may cause something. Now I downgraded my system's kernel to 5.10.63 with via armbian-config. And enp1s0 normally works after warm reboot again. If you need more information that I can provide for this issue, please let me know. Thank you.
  7. Thank you for reply. I'll try older images and post again later when I have time.
  8. I found a similar question here. And I don't think it's a hardware problem but may be a kernel issue or something, because it was OK for long time and the problem suddenly occurs after upgrade to bullseye.
  9. Thank you for prompt reply. I uploaded armbianmonitor -u http://ix.io/3WJi is for working state (power off and on) http://ix.io/3WJk is for non-working state (soft reboot) Thank you
  10. Hello, After NanoPi R4S reboot, ethernet interface `enp1s0` disappeared. I tried soft reboot for several times but failed. If I shutdown the board and power plug out/in again, then `enp1s0` appears. I tested it several times and 100% same results. Any idea please? wg* is for vpn. please ignore them.
  11. Then it seems that I can safely ignore the contents of armbian-image-release. I upgraded buster to bullseye and IMAGE_TYPE became stable again! Thank you.
  12. Thank you for answer. Now I looked into another SoC running on armbian and it also has different version values in those two files. The file date 'Sep 4 2020(above)' and 'May 8 2021(below)' of armbian-image-release files probably indicate the day of first time installation of armbian. It looks like that those two armbian-image-release files were not changed at all after first time installation. I only have done apt update & upgrade occasionally and did not manually upgrade (if exists) armbian version. Should I do something more to upgrade armbian version normally? Or there is any missing somethings in apt update & upgrade procedures? Or this is normal behavior if armbian is upgraded via apt? addendum) one more thing please. IMAGE_TYPE changed to user-built from stable. All I did was apt update & upgrade only. Is it normal? Please help me. Thank you.
  13. Hello I'm just wondering that there are two release files in /etc and why they have different VERSION values. In armbian-image-release file, VERSION is 20.08.1 But it is 21.08.8 in armbian-relase file. armbian-config and welcome massages also show version as 21.08.8 So I think 21.08.8 is correct one, but then why armbian-image-release has incorrect version value? Is it a bug? Or am I missing something? Please help me. Thank you.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines