ap17 Posted September 19, 2018 Posted September 19, 2018 Has anyone had the following error when using kernel 4.18 and 19? 1. Start hostapd (with or without dhcpd) 2. Try connecting via WiFi 3. Result... ---------------------------------------------- Aug 01 15:06:24 P2E vmunix: [ 5553.586947] ------------[ cut here ]------------ Aug 01 15:06:24 P2E vmunix: [ 5553.591573] kernel BUG at mm/slub.c:3902! Aug 01 15:06:24 P2E vmunix: [ 5553.595577] Internal error: Oops - BUG: 0 [#1] SMP ARM Aug 01 15:06:24 P2E vmunix: [ 5553.600707] Modules linked in: cpufreq_userspace realtek sy8106a_regulator evdev dwmac_sun8i mdio_mux stmmac_platform stmmac i2c_mv64xxx sun8i_ths ptp 8189fs sunxi_wdt cfg80211 rfkill cpufreq_dt gpio_keys thermal_sys uio_pdrv_genirq uio ip_tables x_tables Aug 01 15:06:24 P2E vmunix: [ 5553.623305] CPU: 2 PID: 668 Comm: RTW_CMD_THREAD Not tainted 4.19.0-rc1-H23.a1 #1 Aug 01 15:06:24 P2E vmunix: [ 5553.630775] Hardware name: Allwinner sun8i Family Aug 01 15:06:24 P2E vmunix: [ 5553.635481] PC is at kfree+0xfc/0x140 Aug 01 15:06:24 P2E vmunix: [ 5553.639233] LR is at nl80211_send_station+0xb10/0xc80 [cfg80211] Aug 01 15:06:24 P2E vmunix: [ 5553.645229] pc : [<c0135f04>] lr : [<bf09710c>] psr: 40000013 Aug 01 15:06:24 P2E vmunix: [ 5553.651483] sp : ed193dc8 ip : 00000008 fp : ecfaa030 Aug 01 15:06:24 P2E vmunix: [ 5553.656697] r10: ecfaa168 r9 : 00000000 r8 : ed193e50 Aug 01 15:06:24 P2E vmunix: [ 5553.661912] r7 : ed193de0 r6 : ecffd840 r5 : c082ae88 r4 : ecfaa014 Aug 01 15:06:24 P2E vmunix: [ 5553.668428] r3 : eee44b78 r2 : eee44b74 r1 : 00000024 r0 : c0135f40 Aug 01 15:06:24 P2E vmunix: [ 5553.674944] Flags: nZcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none Aug 01 15:06:24 P2E vmunix: [ 5553.682067] Control: 10c5387d Table: 6cda006a DAC: 00000051 Aug 01 15:06:24 P2E vmunix: [ 5553.687808] Process RTW_CMD_THREAD (pid: 668, stack limit = 0x68dce8d5) Aug 01 15:06:24 P2E vmunix: [ 5553.694410] Stack: (0xed193dc8 to 0xed194000) Aug 01 15:06:24 P2E vmunix: [ 5553.698763] 3dc0: 00000005 00000013 ecfaa014 c082ae88 00000012 ecfaa034 Aug 01 15:06:24 P2E vmunix: [ 5553.706929] 3de0: e598c000 e3a010c0 00000000 3085c00e 00000000 ee707800 00480020 ee7071a0 Aug 01 15:06:24 P2E vmunix: [ 5553.715094] 3e00: ed193e50 ecffd840 00000000 ed2efe8a f0db4108 bf09741c 00000000 ee707000 Aug 01 15:06:24 P2E vmunix: [ 5553.723260] 3e20: ee707800 ed2efe8a ed193e50 bf10b294 c082ae88 0000001c 00000000 00000000 Aug 01 15:06:24 P2E vmunix: [ 5553.731425] 3e40: f0db40f8 00080416 ed192000 bf11ac28 00000000 00000000 c082ae88 00060040 Aug 01 15:06:24 P2E vmunix: [ 5553.739590] 3e60: 00000002 01d40801 00000000 3085c00e 00000001 f0db3000 00000001 c082ae88 Aug 01 15:06:24 P2E vmunix: [ 5553.747754] 3e80: 00000007 bf0d79e0 00000001 bf13c8a4 ed192000 00000001 00210d00 00060040 Aug 01 15:06:24 P2E vmunix: [ 5553.755919] 3ea0: c082ae88 ed2f4180 ee472000 c082ae88 00000006 00000000 ed2efe9c 00000038 Aug 01 15:06:24 P2E vmunix: [ 5553.764084] 3ec0: 00000000 00000000 f0db4108 3085c00e f0e1d074 ee401d00 ed193ef8 00012785 Aug 01 15:06:24 P2E vmunix: [ 5553.772249] 3ee0: ed2efe80 f0db40f8 00080416 ed192000 f0db4108 c0135f40 00000001 bf0de80c Aug 01 15:06:24 P2E vmunix: [ 5553.780414] 3f00: f0db40f8 3085c00e f0e1d074 f0db3000 f0e1d074 00000054 ed2efe80 bf0de838 Aug 01 15:06:24 P2E vmunix: [ 5553.788579] 3f20: 00000058 ee5c7a00 f0db3000 bf173990 f0db40f8 bf0ed70c ecca40c0 f0db3000 Aug 01 15:06:24 P2E vmunix: [ 5553.796745] 3f40: f0db4118 f0db4000 f0db40f8 bf0ccbc4 ffffe000 bf0ed698 f0db4144 ee5c7a00 Aug 01 15:06:24 P2E vmunix: [ 5553.804910] 3f60: ffffe000 ed368b80 ece06980 00000000 ed192000 f0db3000 bf0cc8dc ed368b9c Aug 01 15:06:24 P2E vmunix: [ 5553.813075] 3f80: ed5cd864 c0045244 000000af ece06980 c0045124 00000000 00000000 00000000 Aug 01 15:06:24 P2E vmunix: [ 5553.821239] 3fa0: 00000000 00000000 00000000 c00090e8 00000000 00000000 00000000 00000000 Aug 01 15:06:24 P2E vmunix: [ 5553.829403] 3fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Aug 01 15:06:24 P2E vmunix: [ 5553.837569] 3fe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000 Aug 01 15:06:24 P2E vmunix: [ 5553.845741] [<c0135f04>] (kfree) from [<3085c00e>] (0x3085c00e) Aug 01 15:06:24 P2E vmunix: [ 5553.851655] Code: 1a000003 e5923004 e3130001 1a000000 (e7f001f2) Aug 01 15:06:24 P2E vmunix: [ 5553.857742] ---[ end trace 964b2ab036abba84 ]--- ---------------------------------------------- I solved this problem and can share the result.
Igor Posted September 19, 2018 Posted September 19, 2018 21 minutes ago, ap17 said: I solved this problem and can share the result. https://docs.armbian.com/Process_Contribute/
Igor Posted September 21, 2018 Posted September 21, 2018 On 9/19/2018 at 4:55 PM, ap17 said: Has anyone had the following error when using kernel 4.18 and 19? Can't reproduce with our 4.18.y kernel hostapd combo (upgraded from 4.14.y) ... I tried with onboard Broadcom wireless (Bananapi M2+) and Alfa AC via USB. In both cases, I didn't have any troubles. Logs can be observed here: http://ix.io/1naG
kkj Posted October 29, 2018 Posted October 29, 2018 I have same issue on vanilla 4.19 kernel and OrangePi Lite board. I think it is related to rtl8189fs driver. @ap17 Can you share solution for this issue?
ant333 Posted January 18, 2019 Posted January 18, 2019 Same on OrangePi R1 after update to ARMBIAN 5.70. Anybody found solution?
Igor Posted January 18, 2019 Posted January 18, 2019 2 hours ago, ant333 said: Same on OrangePi R1 after update to ARMBIAN 5.70. Anybody found solution? Workaround is by switching to kernel 4.14.y and freeze kernel upgrades. armbian-config -> system
ap17 Posted January 19, 2019 Author Posted January 19, 2019 Hi! I did not understand what you mean. I do not use OS Armbian and don't know what Armbian-5.70 is. But if we are talking about a problem found in the drivers RT 8189es, 8189fs, 8188eu, 8812au, then after applying the proposed patch, the mentioned drivers are used and work fine from 4.18 up to 5.0 on O.Pi. Zero (88eu), R1 (89es?fs), Lite (89es?fs), PC (eu, au), PC+ (89es?fs), Plus2e (fs). There is no time to check it on O.Pi Prime with its 8723bs. October 29, 2018 I sent the"patches" to user KKJ (vanilla 4.19 O.Pi Lite board) and he replies me that this solved his problem.
Igor Posted January 19, 2019 Posted January 19, 2019 1 hour ago, ap17 said: I do not use OS Armbian and don't know what Armbian-5.70 is. This is Armbian forum so one would assume you use kernel with our patches. 1 hour ago, ap17 said: and he replies me that this solved his problem. Can we also be a part of this joy?
ant333 Posted January 20, 2019 Posted January 20, 2019 Hi! 17 hours ago, ap17 said: But if we are talking about a problem found in the drivers RT 8189es Yes, crash on client connect after kernel upgrade to 4.19. Here https://github.com/jwrdegoede/rtl8189ES_linux/tree/master one of last commits is "fix for 4.19", but building and installing this driver not solves problem(
ap17 Posted January 20, 2019 Author Posted January 20, 2019 Hi Igor, Hi Ant333! Due to the fact that I use a drivers with my own “patches” (essentially, I think they are the same as yours), the lines numbering and structures of files that you and I use are different. Therefore, I can not send a patch in the form of a patch file. The correction consists of insert of 1 line. In the kernel tree where the 8189fs (es/eu/au/?bs?) driver is located, in the file drivers/net/wireless/realtek/rtl8189fs/os_dep/linux/ioctl_cfg80211.c in the function “rtw_cfg80211_indicate_sta_assoc(…)” during filling of fields of structure “sinfo“ insert indicated line. . . . . . . void rtw_cfg80211_indicate_sta_assoc(_adapter *padapter, u8 *pmgmt_frame, uint frame_len) { s32 freq; int channel; struct wireless_dev *pwdev = padapter->rtw_wdev; struct mlme_ext_priv *pmlmeext = &(padapter->mlmeextpriv); struct net_device *ndev = padapter->pnetdev; #if defined(RTW_USE_CFG80211_STA_EVENT) || defined(COMPAT_KERNEL_RELEASE) { struct station_info sinfo; u8 ie_offset; if (GetFrameSubType(pmgmt_frame) == WIFI_ASSOCREQ) ie_offset = _ASOCREQ_IE_OFFSET_; else // WIFI_REASSOCREQ ie_offset = _REASOCREQ_IE_OFFSET_; . . . . . . sinfo.pertid = 0; // Somewhere here (before cfg80211_new_sta(…)) insert this line. sinfo.filled = 0; sinfo.assoc_req_ies = pmgmt_frame + WLAN_HDR_A3_LEN + ie_offset; sinfo.assoc_req_ies_len = frame_len - WLAN_HDR_A3_LEN - ie_offset; cfg80211_new_sta(ndev, GetAddr2Ptr(pmgmt_frame), &sinfo, GFP_ATOMIC); } . . . . . . Please let me know if this solves the problem. If you're interested, I can explain how the "error" occures.
ant333 Posted January 21, 2019 Posted January 21, 2019 22 hours ago, ap17 said: Please let me know if this solves the problem. Solved, thank you.
Igor Posted January 21, 2019 Posted January 21, 2019 Added. https://github.com/armbian/build/commit/e5b292799bdda76097367742653da9a3bd951086 Thanks!
vfrolov Posted January 25, 2019 Posted January 25, 2019 all this is very encouraging. but how can a mere mortal get these sweeties
martinayotte Posted January 25, 2019 Posted January 25, 2019 46 minutes ago, vfrolov said: but how can a mere mortal get these sweeties By learning how to build image yourself ... It seems complex, but it is not ! https://docs.armbian.com/Developer-Guide_Build-Preparation/
Calvin Posted February 28, 2019 Posted February 28, 2019 (edited) Hi, I'm just reporting that I'm getting basically the same error with hostapd on an Asus Tinkerboard, and building an image with the latest kernel (Armbian_5.76_Tinkerboard_Debian_stretch_next_4.19.26.img) doesn't seem to fix the problem. The only solution I have found is reverting back to the mainline kernel, but since I would like to use the spidev devices on the tinkerboard, it would be great if I didn't need to. For reference, here is the journalctl output that mirrors the original post, but still occurring in an image I built yesterday. Spoiler Feb 28 16:23:34 tinkerboard kernel: ------------[ cut here ]------------ Feb 28 16:23:34 tinkerboard kernel: kernel BUG at mm/slub.c:3901! Feb 28 16:23:34 tinkerboard kernel: Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM Feb 28 16:23:34 tinkerboard kernel: Modules linked in: ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter zstd snd_soc_hdmi_codec gpio_keys mali_k Feb 28 16:23:34 tinkerboard kernel: CPU: 1 PID: 1402 Comm: RTW_CMD_THREAD Tainted: G C 4.19.26-rockchip #5.76 Feb 28 16:23:34 tinkerboard kernel: Hardware name: Rockchip (Device Tree) Feb 28 16:23:34 tinkerboard kernel: PC is at kfree+0x248/0x268 Feb 28 16:23:34 tinkerboard kernel: LR is at nl80211_send_station+0x940/0xc94 Feb 28 16:23:34 tinkerboard kernel: pc : [<c02a4b50>] lr : [<c0dbb67c>] psr: 400e0013 Feb 28 16:23:34 tinkerboard kernel: sp : ecb35d40 ip : ecb35d70 fp : ecb35d6c Feb 28 16:23:34 tinkerboard kernel: r10: ebab7014 r9 : ecb35e18 r8 : 00000000 Feb 28 16:23:34 tinkerboard kernel: r7 : ecb35d90 r6 : ef4efe74 r5 : c0dbb67c r4 : f17f5f84 Feb 28 16:23:34 tinkerboard kernel: r3 : c1401e34 r2 : 00000000 r1 : ec52a4eb r0 : 001bd79d Feb 28 16:23:34 tinkerboard kernel: Flags: nZcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none Feb 28 16:23:34 tinkerboard kernel: Control: 10c5387d Table: 2c88c06a DAC: 00000051 Feb 28 16:23:34 tinkerboard kernel: Process RTW_CMD_THREAD (pid: 1402, stack limit = 0x2350dd13) Feb 28 16:23:34 tinkerboard kernel: Stack: (0xecb35d40 to 0xecb36000) Feb 28 16:23:34 tinkerboard kernel: 5d40: ec52a49c c074774c c1406588 ec4dd780 f17f5f84 ecb35d90 00000000 ecb35e18 Feb 28 16:23:34 tinkerboard kernel: 5d60: ecb35dcc ecb35d70 c0dbb67c c02a4914 00000005 00000013 00000000 ebab7034 Feb 28 16:23:34 tinkerboard kernel: 5d80: 00000011 c1406588 ebab7014 ebab7030 00000000 00000000 00000000 9360c3c2 Feb 28 16:23:34 tinkerboard kernel: 5da0: ec52a48a ec4fb1c0 ec4fa800 00000000 00480020 ec52a48a ecb35e18 ec4dd780 Feb 28 16:23:34 tinkerboard kernel: 5dc0: ecb35e14 ecb35dd0 c0dbbd54 c0dbad48 00000000 ec4fb000 ec4fa800 ec52a48a Feb 28 16:23:34 tinkerboard kernel: 5de0: ecb35e18 ecb35df0 bf0ac050 c1406588 f17f5f84 00000000 00000000 0003ee28 Feb 28 16:23:34 tinkerboard kernel: 5e00: bf0d6038 ecb26780 ecb35eec ecb35e18 bf0c975c c0dbbcd0 00000000 00000000 Feb 28 16:23:34 tinkerboard kernel: 5e20: 8020000c c02a4450 ecb35ebc ecb35e38 c02a4450 c015200c bf0ac2d4 bf0abfcc Feb 28 16:23:34 tinkerboard kernel: 5e40: ecb35e83 ebe3f380 c1406588 9360c3c2 00210d00 8020000b 00000001 00000001 Feb 28 16:23:34 tinkerboard kernel: 5e60: ebe3f380 600e0013 00000000 00000fff ecb35e9c c02a3338 ecb35ec4 8020000b Feb 28 16:23:34 tinkerboard kernel: 5e80: ec52a49c 0000004f 001fff00 ffffe000 00000201 0000006b ecb35eb4 ecb35ea8 Feb 28 16:23:34 tinkerboard kernel: 5ea0: c06fce90 c012bf30 ecb35ed4 ecb35eb8 c012bf30 c015200c bf080828 f17f5f84 Feb 28 16:23:34 tinkerboard kernel: 5ec0: ec52a480 0000006b ecb35eec 9360c3c2 c0ea05a0 f1661000 ec52a480 0000006b Feb 28 16:23:34 tinkerboard kernel: 5ee0: ecb35f0c ecb35ef0 bf080840 bf0c96e8 f1662000 00000000 f16624b8 c1404900 Feb 28 16:23:34 tinkerboard kernel: 5f00: ecb35f24 ecb35f10 bf08b7d0 bf0806bc f1662000 f1664000 ecb35f74 ecb35f28 Feb 28 16:23:34 tinkerboard kernel: 5f20: bf075d1c bf08b750 ecb35f4c ecb35f38 f166249c ec4fca00 bf0e8000 f1661000 Feb 28 16:23:34 tinkerboard kernel: 5f40: ecb34000 f1662480 c0147f4c eb91ac80 ec56f580 00000000 ecb34000 f1661000 Feb 28 16:23:34 tinkerboard kernel: 5f60: bf075b84 ebd51790 ecb35fac ecb35f78 c0148470 bf075b90 eb91aca8 eb91aca8 Feb 28 16:23:34 tinkerboard kernel: 5f80: 00000000 ec56f580 c0148304 00000000 00000000 00000000 00000000 00000000 Feb 28 16:23:34 tinkerboard kernel: 5fa0: 00000000 ecb35fb0 c01010e8 c0148310 00000000 00000000 00000000 00000000 Feb 28 16:23:34 tinkerboard kernel: 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Feb 28 16:23:34 tinkerboard kernel: 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000 Feb 28 16:23:34 tinkerboard kernel: [<c02a4b50>] (kfree) from [<c0dbb67c>] (nl80211_send_station+0x940/0xc94) Feb 28 16:23:34 tinkerboard kernel: [<c0dbb67c>] (nl80211_send_station) from [<c0dbbd54>] (cfg80211_new_sta+0x90/0x1c4) Feb 28 16:23:34 tinkerboard kernel: [<c0dbbd54>] (cfg80211_new_sta) from [<bf0c975c>] (rtw_cfg80211_indicate_sta_assoc+0x80/0x9c [r8723bs]) Feb 28 16:23:34 tinkerboard kernel: [<bf0c975c>] (rtw_cfg80211_indicate_sta_assoc [r8723bs]) from [<bf080840>] (rtw_stassoc_event_callback+0x190/0x1d8 [r8723bs]) Feb 28 16:23:34 tinkerboard kernel: [<bf080840>] (rtw_stassoc_event_callback [r8723bs]) from [<bf08b7d0>] (mlme_evt_hdl+0x8c/0xb4 [r8723bs]) Feb 28 16:23:34 tinkerboard kernel: [<bf08b7d0>] (mlme_evt_hdl [r8723bs]) from [<bf075d1c>] (rtw_cmd_thread+0x198/0x3c8 [r8723bs]) Feb 28 16:23:34 tinkerboard kernel: [<bf075d1c>] (rtw_cmd_thread [r8723bs]) from [<c0148470>] (kthread+0x16c/0x174) Feb 28 16:23:34 tinkerboard kernel: [<c0148470>] (kthread) from [<c01010e8>] (ret_from_fork+0x14/0x2c) Feb 28 16:23:34 tinkerboard kernel: Exception stack(0xecb35fb0 to 0xecb35ff8) Feb 28 16:23:34 tinkerboard kernel: 5fa0: 00000000 00000000 00000000 00000000 Feb 28 16:23:34 tinkerboard kernel: 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Feb 28 16:23:34 tinkerboard kernel: 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000 Feb 28 16:23:34 tinkerboard kernel: Code: 1a000003 e5963004 e3130001 1a000000 (e7f001f2) Feb 28 16:23:34 tinkerboard kernel: ---[ end trace cd8a58d5622fc25d ]--- Also, the current wifi driver seems to be r8723bs, which I'm not sure was addressed in your original fix. Do I need to add a patch somewhere? I'm a kernel noob and not sure where to add the patch in the build directory, or what to even patch against in the linux kernel. Edited February 28, 2019 by Tido added spoiler - for better reading, please do that yourself next time. thx
Dysmas Posted March 6, 2020 Posted March 6, 2020 One year later, I have exactly the same problem with the ASUS Tinker board S. This error appears the first time I try to connect, once the proper password has been entered. The next time I try to connect, I get only the line : RTL8723BS: ap recv disassoc reason code(8) sta:<my mac address> Has there been any progress on this question since last year ? Someone suggested an incompatibility with wpa_supplicant. If I uninstall it, the error no longer appears, but there is still no connection.
ap17 Posted March 11, 2020 Author Posted March 11, 2020 You are probably using bs driver version 4.3.x, but try version 5.2.17 - it works well with kernel versions up to 5.6.
Dysmas Posted March 22, 2020 Posted March 22, 2020 On 3/11/2020 at 9:23 PM, ap17 said: bs driver version 4.3.x, but try version 5.2.17 Maybe my question is stupid, but where can I find this bs driver ?
Dysmas Posted March 24, 2020 Posted March 24, 2020 OK thanks. When making, I get the following error : Makefile:244 /ha1/phydm/phydm.mk: no such file or directory make: *** No rule to make target '/ha1/phydm/phydm.mk'. Stop The reason is at line 156 : export TopDIR ?= $(src) because src has not been defined before. If I fix this,I get a new error : make[1]: *** /home/android_sdk/Allwinner/a64/android-51/lichee/linux-3.10/ : Aucun fichier ou dossier de ce type. But I am in Linux, not in Android. So I fear I will not be able to use your work.
ap17 Posted March 24, 2020 Author Posted March 24, 2020 This source is not for android, it is for Linux. It seems to me that you are trying to build this driver in "out-of-tree" mode. This driver must be built in "in-tree" mode. 1. put driver sources to ".../drivers/net/wireless/realtek/rtl8723bs" 2. into file ".../drivers/net/wireless/realtek/Kconfig" insert line: source "/drivers/net/wireless/realtek/rtl8723bs/Kconfig" 3. into file ".../drivers/net/wireless/realtek/Makefile" insert line: obj-$(CONFIG_RTL8723BS) += rtl8723bs/ 4. do : make menuconfig -> device drivers-> network device support -> wireless LAN -> select 8723bs 5. by hand deselect 8723bs in ".../drivers/staging/Makefile" -- just comment out 8723bs line by #, driver 8723bs from staging does not work. 6. do make.
Dysmas Posted April 7, 2020 Posted April 7, 2020 I have tried to do what you say. For anyone who would like to do the same, the first step is to install the tree on the Tinker Board. install armbian-config install libncurses-dev log in as root in armbian-config select Software / kernel headers in armbian-config select Software / kernel source Then you have the full tree in linux-headers-5.4.28-rockchip, and the directory linux-source-5.4.28-rockchip contains a single file, .config. Running make menuconfig in the "source" does not gove anything this is not surprising. Running make menu in the "headers" directorcy, which contains the full tree works fine, but arrived in the Wireless LAN page, there is nothing to choose 8723bs. Nevertheless, I notice that in the .config file, I have a line CONFIG_RTL8723BS=m So perhaps everything is fine. Try make. This leads quickly to an error : no rule to make target arch/arm/tools/syscall.tbl needed by arch/arm/include/generated/uapi/asm/unistd-common-h arch/arm/Makefile:325: archheaders Error 2 This line is : archheaders: $(Q)$(MAKE) $BUILD=arch/arm/tools uapi I fear the task is too difficult for me. But thanks for the help, I hope I will find someone who is able to do the job.
ap17 Posted April 7, 2020 Author Posted April 7, 2020 Dear Dysmas! You did not understand me at all. Have you ever built the Linux kernel yourself? Please try to find some article on how to build a Linux kernel somewhere on the Internet. Or ask someone to help you step by step. X1. install the tree on the Tinker Board - ??? 1. install armbian-config -- for what? 2. Install libncurses-dev -- required. 3. Log in as root -- required. 4. in armbian-config select Software / kernel headers -- what is it? 5. in armbian-config select Software / kernel source -- what is it? X2. what does the "full tree in linux-headers (etc.)" have to do with it ? I wish you good luck.
Dysmas Posted April 7, 2020 Posted April 7, 2020 1 hour ago, ap17 said: what does the "full tree in linux-headers (etc.)" have to do with it ? Because this is the kernel source, the tree structure with all the directories and files you are speaking of : ".../drivers/net/wireless/realtek/Kconfig" ".../drivers/net/wireless/realtek/Makefile" with the lines like the one you mention : obj-$(CONFIG_RTL8723BS) += rtl8723bs/ and so on. And the simplest way to have it in armbian, is using armbian-config. But never mind, I'll find someone to help. Thank you for your work. Update : Quote Have you ever built the Linux kernel yourself? I had not, but now yes, I tested with this tutorial and a standard linux and the kernel built without errors : https://www.cyberciti.biz/tips/compiling-linux-kernel-26.html I think this is exactly what I did with armbian. Get the tarball and extract (done by armbian-config) on a linux machine (the Tinker board is the best I have, running Debian Buster), and so on. The steps are OK. Maybe I made a mistake somewhere. I'll try again.
ap17 Posted April 8, 2020 Author Posted April 8, 2020 23 hours ago, Dysmas said: This leads quickly to an error : no rule to make target arch/arm/tools/syscall.tbl needed by arch/arm/include/generated/uapi/asm/unistd-common-h arch/arm/Makefile:325: archheaders Error 2 This error has no relation, it has nothing to do with 8723bs driver. This means that the distributive you are using has an internal incorrectness. 23 hours ago, Dysmas said: but arrived in the Wireless LAN page, there is nothing to choose 8723bs You probably forgot : On 3/24/2020 at 11:16 PM, ap17 said: 1. put driver sources to ".../drivers/net/wireless/realtek/rtl8723bs" 2. into file ".../drivers/net/wireless/realtek/Kconfig" insert line: source "/drivers/net/wireless/realtek/rtl8723bs/Kconfig" Open the file ".../drivers/net/wireless/realtek/Kconfig" in a text editor, look at what it contains and add the line mentioned. Remember to select “Realtek Devices” in the menuconfig: make menuconfig -> device drivers-> network device support -> wireless LAN And after all, don't forget : On 3/24/2020 at 11:16 PM, ap17 said: 5. by hand deselect 8723bs in ".../drivers/staging/Makefile" -- just comment out 8723bs line by #, driver 8723bs from staging does not work.
Dysmas Posted April 8, 2020 Posted April 8, 2020 There was an error in the downloaded sources. It is fixed. steps 1, 2 and 3 were made carefully (adding the line in Kconfig and Makefile). Step 5 (staging) was done. On 3/24/2020 at 9:16 PM, ap17 said: do : make menuconfig -> device drivers-> network device support -> wireless LAN -> select 8723bs perhaps I misunderstood this line. I have Realtek devices, and it is selected. And inside this section, after making your modifications, I have a new line : REALTEK 8723B SDIO or SPI WiF I selected by Y [*] which was perhaps not the good option. I compiled, installed and rebooted. Still the same problem. But there is still a point to discuss. I have no longer time this week, I'll explain next week. But I have made good progress and I hope we will manage it in the end. And after that I will try to obtain that the modification is pushed in armbian. Thanks for your help.
Recommended Posts