New Cheapo laptops: UEFI & rtl8723bs problems.

[labeas]

=> /mnt/sda2/Core32/Log17Dec  2019 Dec 17

After <install Wifi>
# df ==
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                 1737004     17120   1719884   1% /
tmpfs                   965000         0    965000   0% /dev/shm
/dev/sda1              3632412    523832   2904344  15% /mnt/sda1
/dev/sda2             11367568    836576  10530992   7% /mnt/sda2
/dev/loop0                 388       388         0 100% /tmp/tcloop/firmware-rtl_bt
/dev/loop1                 800       800         0 100% /tmp/tcloop/firmware-rtlwifi
/dev/loop2                3208      3208         0 100% /tmp/tcloop/wireless-4.19.10-tinycore
/dev/loop3                 216       216         0 100% /tmp/tcloop/rtl8723bs-4.19.10-tinycore
/dev/loop4                  12        12         0 100% /tmp/tcloop/libiw
/dev/loop5                 320       320         0 100% /tmp/tcloop/libnl
/dev/loop6                 212       212         0 100% /tmp/tcloop/ncursesw
/dev/loop7                1124      1124         0 100% /tmp/tcloop/openssl
/dev/loop8                 128       128         0 100% /tmp/tcloop/readline
/dev/loop9                   8         8         0 100% /tmp/tcloop/wifi
/dev/loop10                 48        48         0 100% /tmp/tcloop/wireless_tools
/dev/loop11                340       340         0 100% /tmp/tcloop/wpa_supplicant
Shows SEQUENCE/TimeORDER of installation ?!

After <install gpm.mc>
# df == ...
/dev/loop10                 48        48         0 100% /tmp/tcloop/wireless_tools
/dev/loop11                340       340         0 100% /tmp/tcloop/wpa_supplicant
/dev/loop12               1300      1300         0 100% /tmp/tcloop/glib2
/dev/loop13                108       108         0 100% /tmp/tcloop/gpm
/dev/loop14                 16        16         0 100% /tmp/tcloop/libffi
/dev/loop15                344       344         0 100% /tmp/tcloop/libgcrypt
/dev/loop16                 44        44         0 100% /tmp/tcloop/libgpg-error
/dev/loop17                 92        92         0 100% /tmp/tcloop/libssh2
/dev/loop18               1356      1356         0 100% /tmp/tcloop/mc
/dev/loop19                256       256         0 100% /tmp/tcloop/pcre
/dev/loop20                412       412         0 100% /tmp/tcloop/slang

# which wifi.sh == /usr/local/bin/wifi.sh

# wifi.sh == <DELAY>
No wifi devices found!

# dmesg | tail -22 ==
usb 1-1: USB disconnect, device number 11
ACPI: AC: found native INT33F4 PMIC, not loading
ACPI: AC: found native INT33F4 PMIC, not loading
ACPI: AC: found native INT33F4 PMIC, not loading
ACPI: AC: found native INT33F4 PMIC, not loading
ACPI: AC: found native INT33F4 PMIC, not loading
ACPI: AC: found native INT33F4 PMIC, not loading
ACPI: AC: found native INT33F4 PMIC, not loading
ACPI: AC: found native INT33F4 PMIC, not loading
platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
platform regulatory.0: Falling back to syfs fallback for: regulatory.db
cfg80211: failed to load regulatory.db
r8723bs: module is from the staging directory, the quality is unknown, you have been warned.
RTL8723BS: module init start
RTL8723BS: rtl8723bs v4.3.5.5_12290.20140916_BTCOEX20140507-4E40
RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40
RTL8723BS: module init ret =0
ACPI: AC: found native INT33F4 PMIC, not loading
ACPI: AC: found native INT33F4 PMIC, not loading
usb 1-1: new low-speed USB device number 12 using xhci_hcd
input: Genius USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:0458:003A.0005/input/input12
hid-generic 0003:0458:003A.0005: input,hidraw0: USB HID v1.11 Mouse [Genius USB Optical Mouse] on usb-0000:00:14.0-1/input0
root@box:/mnt/sda2/Core32/Wifi#

=> We've never had an explanation for this OFTEN REPORTED "...INT33F4 PMIC..." ?!

==> Some comands cited in a <WifiWiki>:----------
# iwconfig ==
ip_vti0   no wireless extensions.
lo        no wireless extensions.
tunl0     no wireless extensions.
dummy0    no wireless extensions.

# modprobe -l | grep rtl8723bs ==
kernel.tclocal/drivers/net/wireless/realtek/rtl8723bs/r8723bs.ko.gz

# wpa_supplicant -i*interface* -c/opt/wpa_configure.conf -d ==
wpa_supplicant v2.6
random: Trying to read entropy from /dev/random
Successfully initialized wpa_supplicant
Initializing interface '*interface*' conf '/opt/wpa_configure.conf' driver 'default' ctrl_interface
'N/A' bridge 'N/A'
Configuration file '/opt/wpa_configure.conf' -> '/opt/wpa_configure.conf'
Reading configuration file '/opt/wpa_configure.conf'
Failed to open config file '/opt/wpa_configure.conf', error: No such file or directory
Failed to read or parse configuration '/opt/wpa_configure.conf'.
Failed to add interface *interface*
: Cancelling scan request
: Cancelling authentication timeout

# # udhcpc -i *interface*  ==
udhcpc: SIOCGIFINDEX: No such device

? Possibly relevant files, via `du / | grep ...` ==
/tmp/tcloop/rtl8723bs-4.19.10-tinycore/usr/local/lib/modules/4.19.10-tinycore/kernel/drivers/net/wireless/realtek/rtl8723bs
/sys/bus/sdio/drivers/rtl8723bs
/usr/local/lib/modules/4.19.10-tinycore/kernel/drivers/net/wireless/realtek/rtl8723bs

[labeas]

Apparently, my posts are fraudulently altered/reformatted?
This could never happen under NNTP, of past decades.

[Juanito]

Your posts were not fraudulently altered/reformatted, they were edited to make them readable and understandable as you have been requested to do on several occasions.

[Juanito]

platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
platform regulatory.0: Falling back to syfs fallback for: regulatory.db
cfg80211: failed to load regulatory.db
r8723bs: module is from the staging directory, the quality is unknown, you have been warned.
RTL8723BS: module init start
RTL8723BS: rtl8723bs v4.3.5.5_12290.20140916_BTCOEX20140507-4E40
RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40
RTL8723BS: module init ret =0

This part looks OK - the regulatory database is not normally required to make things work.

However, since wlan0 has not been created, something must be wrong.

You could try the following

1. load the rfkill extension and check your wifi hardware is enabled with "rfkill list"

2. Download and copy regulatory.db to /usr/local/lib/firmware before loading the rtl8723bs-KERNEL extension

download from: https://kernel.googlesource.com/pub/scm/linux/kernel/git/sforshee/wireless-regdb/+/refs/heads/master

[Rich]

Hi labeas

Apparently, my posts are fraudulently altered/reformatted?

Fraudulently implies there was deception involved with the intent of concealing the act. As I always do when editing a post, I added a
note to the end of the post indicating what I had done. In addition, I addressed a post to you asking you to behave yourself.

This could never happen under NNTP, of past decades.

Well this is an HTML based forum. Rather than whining, complaining, and criticizing, maybe you could try using this forum as intended.
In your attempt to force this forum and its members to conform to your cryptic syntax and unformatted posts, you likely discourage
most members from responding, let alone even read your posts. Making your posts difficult to understand serves as a disincentive
to anyone even considering trying to help you.

   Learn how to wrap terminal commands and responses in  Code Tags  (see below).
   Learn the proper use of  Quote Tags  so others can find where the quote came from (see below).

Please use  Code Tags  when posting commands and responses seen in a terminal. To use  Code Tags  click on the  #  icon
above the reply box and paste your text between the  Code Tags

Code Tags  serve as visual markers between what you are trying to say and the information you are posting. They also preserve
spacing so column aligned data displays properly.

[Rich]

Hi labeas

... => We've never had an explanation for this OFTEN REPORTED "...INT33F4 PMIC..." ?! ...

That message is coming from the  battery.ko.gz  driver. You can try adding this to your bootloaders config file:

Code: [Select]

blacklist=batteryThat should make the messages go away. It's likely the kernel was not configured to support your  Power Management IC.

[labeas]

on: December 13, 2019 Juanito wrote:-
> I compiled a 32-bit rtl8723bs driver for you since you said you'd
> managed to boot your machine with 32-bit Core.
>
> It would be helpful if you could test the 32-bit driver and
> verify that it works.
 ---
Yes please; but include info on all steps for incremental testing.
eg: `instr A` confirms/or-not condition A ....
    `instr N` confirms/or-not condition N.
Or better still: refer to the ALREADY EXISTING TC's <Wifi wiki> ?

[Juanito]

If you read back through this thread the instructions are given.

We're waiting on you to confirm what happened with rfkill and regulatory.db

[labeas]

on: December 13, 2019 Juanito wrote:-
> I compiled a 32-bit rtl8723bs driver for you since you said you'd
> managed to boot your machine with 32-bit Core.
>
> It would be helpful if you could test the 32-bit driver and
> verify that it works.
---
Sorry for delay! I've got a lot of test results from 2019 Dec.
Yes: Ver10:32bCore [with gpm & mc] is usable.
It's very difficult being forced to use Win10 to D/L all files.
I prefer to not abandon all my Ver10 efforts for current V11 ?
Please provide <action...confirm chain> to install/test rtl8723bs-based
  wifi for ver10:32bCore.
 

[labeas]

on: December 13, 2019 Juanito wrote:-
> I compiled a 32-bit rtl8723bs driver for you since you said you'd
> managed to boot your machine with 32-bit Core.
>
> It would be helpful if you could test the 32-bit driver and
> verify that it works.
===== Try SECOND REPLY:---
PLEASE post:
$ tce-load -i <URL of 32b Wifi *.tcz>
Sequence of test & use wifi.

[Juanito]

It has already been explained to you several times, please use the forum search function.