9:18 p.m.
Hi all. OS is 5.7.8-200.fc32.aarch64 Fedora Server running headless on Pine64
sbc. The system works well. Currently eth0 is the main network device, but I
have another use for this cable and wish to implement the wifi. This is
proving problematic as it seems to use the rtl8723bs module. Despite a lot of
googling there is no sign of wlan0.
Here I load the realtek module.
r8723bs: module is from the staging directory, the quality is unknown, you
have been warned.
[34784.402732] RTL8723BS: module init start
[34784.406673] RTL8723BS: rtl8723bs
v4.3.5.5_12290.20140916_BTCOEX20140507-4E40
[34784.413770] RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40
[34784.420437] RTL8723BS: module init ret =0
If I go to /usr/lib/firmware/rtlwifi - these files are present.
│-rw-r--r-- 1 root root 20886 Jun 20 02:37 rtl8723bs_ap_wowlan.bin
│
│-rw-r--r-- 1 root root 9120 Jun 20 02:37 rtl8723bs_bt.bin
│
│-rw-r--r-- 1 root root 32108 Jun 20 02:37 rtl8723bs_nic.bin
│
│-rw-r--r-- 1 root root 26398 Jun 20 02:37 rtl8723bs_wowlan.bin
I am not sure how to use these. I was hoping that modprobe would activate the
device and wlan0 would appear. But this is not the case. Any ideas?
9:32 p.m.
likely the device tree file needs to have the wif device added for it
to show up.
Dennis
On Tue, Jul 21, 2020 at 9:19 PM brm <brm(a)deadjoe.org> wrote:
>
> Hi all. OS is 5.7.8-200.fc32.aarch64 Fedora Server running headless on Pine64
> sbc. The system works well. Currently eth0 is the main network device, but I
> have another use for this cable and wish to implement the wifi. This is
> proving problematic as it seems to use the rtl8723bs module. Despite a lot of
> googling there is no sign of wlan0.
>
> Here I load the realtek module.
>
> r8723bs: module is from the staging directory, the quality is unknown, you
> have been warned.
> [34784.402732] RTL8723BS: module init start
> [34784.406673] RTL8723BS: rtl8723bs
> v4.3.5.5_12290.20140916_BTCOEX20140507-4E40
> [34784.413770] RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40
> [34784.420437] RTL8723BS: module init ret =0
>
> If I go to /usr/lib/firmware/rtlwifi - these files are present.
>
> │-rw-r--r-- 1 root root 20886 Jun 20 02:37 rtl8723bs_ap_wowlan.bin
> │
> │-rw-r--r-- 1 root root 9120 Jun 20 02:37 rtl8723bs_bt.bin
> │
> │-rw-r--r-- 1 root root 32108 Jun 20 02:37 rtl8723bs_nic.bin
> │
> │-rw-r--r-- 1 root root 26398 Jun 20 02:37 rtl8723bs_wowlan.bin
>
> I am not sure how to use these. I was hoping that modprobe would activate the
> device and wlan0 would appear. But this is not the case. Any ideas?
> _______________________________________________
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
11:40 p.m.
Where to look . . . lspci does not return a result. Should I see a device in dmesg ?
Nothing so far.
6:32 a.m.
Where to look . . . lspci does not return a result. Should I see a
device in dmesg ? Nothing so far.
It's attached via SDIO not PCI so you wouldn't expect it to be visible
via a tool like lspci.
Also there's a completely different r8723cs driver that is not
upstream, I think that the r8723bs driver could be made to support the
CS variant but no one has actually done that work that I'm aware of. I
took a little bit of a poke the other day at the published driver but
it was purely investigatory.
Finally as Dennis mentioned there probably needs to be the device tree
bits added. The issue with the Pine64 is that the WiFi/BT module is
optional so it should probably be added as an overlay, again someone
needs to do the work.
So sadly it's not a simple or quick fix. I kind of want to take a look
at the driver side of things as it's the same module in the original
Pinebook, but also the PinePhone and PineTab but I have little time to
spare and a lot of things to work upon, I'm also by no means a WiFi
driver expert.
Peter
4:49 a.m.
Booted into the Armbian image today - 5.4.43-sunxi64. The wlan0 was able to be activated
ok.
Dmesg had some detail of the module being loaded. This is much the same as appears in
Fedora.
Jun 7 18:11:54 localhost kernel: [ 8.369702] RTL8723BS: module init start
Jun 7 18:11:54 localhost kernel: [ 8.369710] RTL8723BS: rtl8723bs
v4.3.5.5_12290.20140916_BTCOEX20140507-4E40
Jun 7 18:11:54 localhost kernel: [ 8.369712] RTL8723BS: rtl8723bs BT-Coex version =
BTCOEX20140507-4E40
Jun 7 18:11:54 localhost kernel: [ 8.369941] pnetdev = (____ptrval____)
Jun 7 18:11:54 localhost kernel: [ 8.395745] axp20x-adc axp813-adc: DMA mask not set
Jun 7 18:11:54 localhost kernel: [ 8.436782] RTL8723BS: rtw_ndev_init(wlan0)
Jun 7 18:11:54 localhost kernel: [ 8.439808] RTL8723BS: module init ret =0
But then this
Jun 7 18:11:59 localhost kernel: [ 127.473668] rtl8723bs: acquire FW from
file:rtlwifi/rtl8723bs_nic.bin
And this
Jun 7 18:11:54 localhost kernel: [ 9.421354] Bluetooth: hci0: RTL: examining
hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723
Jun 7 18:11:54 localhost kernel: [ 9.425867] Bluetooth: hci0: RTL: rom_version
status=0 version=1
Jun 7 18:11:54 localhost kernel: [ 9.425878] Bluetooth: hci0: RTL: loading
rtl_bt/rtl8723bs_fw.bin
Jun 7 18:11:54 localhost kernel: [ 9.426773] bluetooth hci0: Direct firmware load for
rtl_bt/rtl8723bs_fw.bin failed with error -2
Jun 7 18:11:54 localhost kernel: [ 9.426789] Bluetooth: hci0: RTL: firmware file
rtl_bt/rtl8723bs_fw.bin not found
Jun 7 18:11:54 localhost kernel: [ 10.320346] zram0: detected capacity change from 0 to
52428800
Jun 7 18:11:54 localhost kernel: [ 12.973703] zram2: detected capacity change from 0 to
1044611072
Can I glean anything from Armbian that might help me get r8723bs working in Fedora?
The file rtlwifi/rtl8723bs_nic.bin is present in my Fedora 32 Arm.
7:12 a.m.
On Tue, Jul 28, 2020 at 10:51 AM brm <brm(a)deadjoe.org> wrote:
Booted into the Armbian image today - 5.4.43-sunxi64. The wlan0 was able to be activated
ok.
Dmesg had some detail of the module being loaded. This is much the same as appears in
Fedora.
Jun 7 18:11:54 localhost kernel: [ 8.369702] RTL8723BS: module init start
Jun 7 18:11:54 localhost kernel: [ 8.369710] RTL8723BS: rtl8723bs
v4.3.5.5_12290.20140916_BTCOEX20140507-4E40
Jun 7 18:11:54 localhost kernel: [ 8.369712] RTL8723BS: rtl8723bs BT-Coex version =
BTCOEX20140507-4E40
Jun 7 18:11:54 localhost kernel: [ 8.369941] pnetdev = (____ptrval____)
Jun 7 18:11:54 localhost kernel: [ 8.395745] axp20x-adc axp813-adc: DMA mask not set
Jun 7 18:11:54 localhost kernel: [ 8.436782] RTL8723BS: rtw_ndev_init(wlan0)
Jun 7 18:11:54 localhost kernel: [ 8.439808] RTL8723BS: module init ret =0
But then this
Jun 7 18:11:59 localhost kernel: [ 127.473668] rtl8723bs: acquire FW from
file:rtlwifi/rtl8723bs_nic.bin
And this
Jun 7 18:11:54 localhost kernel: [ 9.421354] Bluetooth: hci0: RTL: examining
hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723
Jun 7 18:11:54 localhost kernel: [ 9.425867] Bluetooth: hci0: RTL: rom_version
status=0 version=1
Jun 7 18:11:54 localhost kernel: [ 9.425878] Bluetooth: hci0: RTL: loading
rtl_bt/rtl8723bs_fw.bin
Jun 7 18:11:54 localhost kernel: [ 9.426773] bluetooth hci0: Direct firmware load for
rtl_bt/rtl8723bs_fw.bin failed with error -2
Jun 7 18:11:54 localhost kernel: [ 9.426789] Bluetooth: hci0: RTL: firmware file
rtl_bt/rtl8723bs_fw.bin not found
Jun 7 18:11:54 localhost kernel: [ 10.320346] zram0: detected capacity change from 0
to 52428800
Jun 7 18:11:54 localhost kernel: [ 12.973703] zram2: detected capacity change from 0
to 1044611072
Can I glean anything from Armbian that might help me get r8723bs working in Fedora?
The file rtlwifi/rtl8723bs_nic.bin is present in my Fedora 32 Arm.
That they have non upstreamed patches, and by the look of the kernel
naming a forked kernel that's 10 releases out of date of the 5.4
stable series and likely has security CVEs?
7:29 a.m.
On Tue, 28 Jul 2020, brm wrote:
Can I glean anything from Armbian that might help me get r8723bs
working in Fedora? The file rtlwifi/rtl8723bs_nic.bin is present in
my Fedora 32 Arm.
Compare the device tree between the two. I have an Ubuntu install
on pinebook that also has wifi working.
Device tree as loaded by kernel is in /sys/firmware/devicetree
Fedora keeps compiled devicetrees in /boot/dtb. The PineBook is
probably in /boot/dtb/allwinner/sun50i-a64-pinebook.dtb, "probably" is
why you compare to /sys/firmware/devicetree.
In Ubuntu, it is probably loading /boot/pine64/sun50i-a64-pine64-pinebook.dtb.
Somewhere, there is a decompiler for dtb -> dts.
1361
days inactive
1367
days old
6 comments
4 participants
participants (4)
-
brm -
Dennis Gilmore -
Peter Robinson -
Stuart D Gathman