Caletronics Posted January 1, 2023 Posted January 1, 2023 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 0 Quote
Caletronics Posted January 3, 2023 Author Posted January 3, 2023 (edited) A followup: # apt-get --reinstall install linux-headers-current-sunxi # file /usr/src/linux-headers-5.15.80-sunxi/scripts/dtc/dtc ... ARM, EABI5 ... shows that this is a problem in the image. On the other hand doing this: apt-get install wpasupplicant/bullseye-backports still produces kernel backtraces. And after this: # apt-get install linux-image-edge-sunxi linux-headers-edge-sunxi linux-dtb-edge-sunxi reboot # uname -a Linux orangepi-r1 6.0.10-sunxi #22.11.1 SMP Wed Nov 30 11:14:43 UTC 2022 armv7l GNU/Linux I still get kernel backtraces from wpa_supplicant (direct or via nmtui). The wlan0 interface does work regardless. Edited January 3, 2023 by Caletronics add more info 0 Quote
going Posted January 4, 2023 Posted January 4, 2023 01.01.2023 в 19:03, Caletronics сказал: From https://redirect.armbian.com/orangepi-r1/Bullseye_current I downloaded: Armbian_22.11.1_Orangepi-r1_bullseye_current_5.15.80.img.xz This image is assembled incorrectly. This error has been fixed in the build system to date. You need to uninstall the kernel header package. Then install the dependencies necessary for the build. apt-get install build-essential kmod debhelper devscripts After that, install the kernel header package again. @Igor I still have a question about why the kernel headers are installed in the standard image? 0 Quote
Igor Posted January 4, 2023 Posted January 4, 2023 30 minutes ago, going said: why the kernel headers are installed in the standard image? To make it easier for installing drivers via DKMS is the only reason. But I guess its better to disable? 0 Quote
going Posted January 4, 2023 Posted January 4, 2023 7 минут назад, Igor сказал: To make it easier for installing drivers via DKMS is the only reason For me, it's still vague. The topic requires study for me. I assume that there should be no development packages in the standard image. The fakeroot package alone is a security issue. 0 Quote
Igor Posted January 4, 2023 Posted January 4, 2023 1 minute ago, going said: I assume that there should be no development packages in the standard image. We provide / have minimal images for software deployment purposes, where "nothing" comes preinstalled. Standard CLI image provides more things including possibility to recompile kernel, build armbian image, drivers, ... This was since ever, only default headers install was included recently. 0 Quote
going Posted January 4, 2023 Posted January 4, 2023 43 минуты назад, Igor сказал: But I guess its better to disable? This question is for a philosophical conversation. Let's leave it hanging in the air. 0 Quote
Recommended Posts
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.