Search the Community

I came across this thread but don't think I could get the reset button working (as it should). What am I missing? I followed exactly the correct 'short-ed' pins as the pic, but still no luck. Please suggest. Thanks!

Hey Gang, I'm a very novice linux user, just know enough to get around and follow instructions for the most part. I recently started getting the following error when trying to ssh to my armbian box from an up to date macbook. Unable to negotiate with <ip address> port 22: no matching host key type found. Their offer: rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519 I've read online that you can get around this with "-oHostKeyAlgorithms=+ssh-dss" temporarily, but I cant seem to find a guide on how to regenerate the host keys on armbian to match more current standards (or what I assume is ssh's up to date minimum) Does anyone have a quick guide on how to do this? Currently running: Welcome to Armbian 23.02.2 Jammy with Linux 5.15.93-rockchip64

Hello and Happy New Year, From https://redirect.armbian.com/orangepi-r1/Bullseye_current I downloaded: Armbian_22.11.1_Orangepi-r1_bullseye_current_5.15.80.img.xz and installed. I see a file that shouldn't exist: $ ls -l /*core -rw-r--r-- 1 root root 16789504 Nov 30 11:55 /qemu_fstype_20221130-195503_13162.core A short while later I found this: $ armbian-add-overlay /etc/keys-h3.dts /usr/sbin/armbian-add-overlay: line 62: /lib/modules/5.15.80-sunxi/build/scripts/dtc/dtc: cannot execute binary file: Exec format error Error: dtc does not support compiling overlays There is a symlink involved: $ ls -l /lib/modules/5.15.80-sunxi/build lrwxrwxrwx 1 root root 36 Nov 30 03:13 /lib/modules/5.15.80-sunxi/build -> /usr/src/linux-headers-5.15.80-sunxi and I find: $ file /usr/src/linux-headers-5.15.80-sunxi/scripts/dtc/dtc /usr/src/linux-headers-5.15.80-sunxi/scripts/dtc/dtc: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=739474e836a0c8fb69e7d3902622523128d499a4, for GNU/Linux 3.2.0, not stripped ... which should be ARM not x86_64. The most recent find: Jan 1 06:57:29 jeep wpa_supplicant[2776]: nl80211: kernel reports: Authentication algorithm number required Jan 1 06:57:30 jeep kernel: [50662.629441] ------------[ cut here ]------------ Jan 1 06:57:30 jeep kernel: [50662.629465] WARNING: CPU: 1 PID: 1930 at net/wireless/nl80211.c:17545 cfg80211_ch_switch_notify+0xc9/0xcc [cfg80211] Jan 1 06:57:30 jeep kernel: [50662.629817] Modules linked in: 8189es cfg80211 sun4i_gpadc_iio r8152 industrialio rfkill sun8i_thermal uio_pdrv_genirq uio cpufreq_dt usb_f_acm u_serial g_serial libcomposite sunrpc ip_tables x_tables autofs4 pwrseq_simple sunxi phy_generic [last unloaded: 8189es] Jan 1 06:57:30 jeep kernel: [50662.629926] CPU: 1 PID: 1930 Comm: RTW_CMD_THREAD Tainted: G W 5.15.80-sunxi #22.11.1 Jan 1 06:57:30 jeep kernel: [50662.629940] Hardware name: Allwinner sun8i Family Jan 1 06:57:30 jeep kernel: [50662.629954] [<c010cd21>] (unwind_backtrace) from [<c01095fd>] (show_stack+0x11/0x14) Jan 1 06:57:30 jeep kernel: [50662.629984] [<c01095fd>] (show_stack) from [<c09e1165>] (dump_stack_lvl+0x2b/0x34) Jan 1 06:57:30 jeep kernel: [50662.630009] [<c09e1165>] (dump_stack_lvl) from [<c011c3f9>] (__warn+0xad/0xc0) Jan 1 06:57:30 jeep kernel: [50662.630032] [<c011c3f9>] (__warn) from [<c09dadf7>] (warn_slowpath_fmt+0x43/0x7c) Jan 1 06:57:30 jeep kernel: [50662.630053] [<c09dadf7>] (warn_slowpath_fmt) from [<bf9044b5>] (cfg80211_ch_switch_notify+0xc9/0xcc [cfg80211]) Jan 1 06:57:30 jeep kernel: [50662.630243] [<bf9044b5>] (cfg80211_ch_switch_notify [cfg80211]) from [<bf9ba4d5>] (rtw_cfg80211_ch_switch_notify+0x97/0xd0 [8189es]) Jan 1 06:57:30 jeep kernel: [50662.631126] [<bf9ba4d5>] (rtw_cfg80211_ch_switch_notify [8189es]) from [<bf98de2b>] (rtw_chk_start_clnt_join+0x45/0x7a [8189es]) Jan 1 06:57:30 jeep kernel: [50662.631761] [<bf98de2b>] (rtw_chk_start_clnt_join [8189es]) from [<bf98dff1>] (join_cmd_hdl+0x191/0x254 [8189es]) Jan 1 06:57:30 jeep kernel: [50662.632388] [<bf98dff1>] (join_cmd_hdl [8189es]) from [<bf96e9fb>] (rtw_cmd_thread+0xe5/0x2e4 [8189es]) Jan 1 06:57:30 jeep kernel: [50662.633016] [<bf96e9fb>] (rtw_cmd_thread [8189es]) from [<c0136a73>] (kthread+0x117/0x12c) Jan 1 06:57:30 jeep kernel: [50662.633346] [<c0136a73>] (kthread) from [<c0100139>] (ret_from_fork+0x11/0x38) Jan 1 06:57:30 jeep kernel: [50662.633365] Exception stack(0xc433bfb0 to 0xc433bff8) Jan 1 06:57:30 jeep kernel: [50662.633377] bfa0: 00000000 00000000 00000000 00000000 Jan 1 06:57:30 jeep kernel: [50662.633389] bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Jan 1 06:57:30 jeep kernel: [50662.633400] bfe0: 00000000 00000000 00000000 00000000 00000013 00000000 Jan 1 06:57:30 jeep kernel: [50662.633471] ---[ end trace bb1537dfe65a110c ]--- The wlan0 interface seems to work as expected but this is still worrisome. Again, may or may not be related to the build. I'm not sure if the above are related because of some error during the build or if I should report these seperately. Thanks, Chris