New Cheapo laptops: UEFI & rtl8723bs problems.

[labeas]

BTW this web-based forum is a DISASTER compared to the
proper NNTP of the 80s. Pity that the kiddies follow
inappropriate fads? I can't find the thread were someone
asked <does it run on the 7.2 laptop...>, which would
have been immediately accessable under NNTP.
---
Let's simplify; start from a MINIMUM:-
 The 4coreAtom boots our <grub2dos..>, also "core" [not 64b]?
 It's showing: $ uname -a =...4.19.10...i686...
 $ which wget = OK ;$ lsmod | wc -l = 35 ; no <rtl>.
From this minimal state: start INCREMENTALLY [CONFIRMING
EACH STAGE] install the wifi.
eg. immediately after the module is installed, should not
`lsmod` confirm the fact?!
Forget/delay the smart-ass GUI. Start from basics.

[Juanito]

eg. immediately after the module is installed, should not
`lsmod` confirm the fact?!

Yes - if the correct kernel module for your hardware is present.

Can you confirm if you have rtl8723bs WiFi hardware and whether you need a 32bit or 64bit driver?

[labeas]

Because of exploded data/files quantity for this project: finding the.
 Win10 supplied rtl8723bs info is a problem.
Besides I intend to install TC64 and "core".
KNOWING that there are 2 different kernels is what's important?

[Juanito]

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.

[labeas]

The attempt to install TC64:wifi to the Atom, with Ver7.2 *.tcz/S
has become unmanageable [also because I tried and failed to
be able to remove the USBstik, after installation].
  Better to evolve a non-GUI wifi for 32bit:Core, where I've
now installed gpm & mc & various OwnScripts.
--A strange quirk, which I noticed before is:---
Each of the Ver10*.tcz [for gpm & mc] shows "OK".
 But what's the "...INT33F4..." ?
----------------------------->Pasted Verbatum !
tc@box:/mnt/sda2/Core32/gpm.mc$  ./InstallThese ==
glib2.tcz: OK
gpm.tcz: OK
libffi.tcz: OK
libgcrypt.tcz: OK
libgpg-error.tcz: OK
libssh2.tcz: OK
mc.tcz: OK
ncursesw.tcz: OK
pcre.tcz: OK
slang.tcz: OK
tc@box:/mnt/sda2/Core32/gpm.mc$ ACPI: AC: found native INT33F4 PMIC, not loading
ACPI: AC: found native INT33F4 PMIC, not loading
------------------------------
=> /mnt/sda2/Core32/gpm.mc/InstallThese ==
for FILE in `ls *tcz*` ; do
  tce-load -i $FILE ; done
exit 0
-------------
Please provide instructions for installing wifi to non-GUI:Core:32bit:Ver10,
 [with staged testing/confirmation].
Yes I've got the <TCwifiWiki>.
== TIA.
I'm in Win10 now. The new <kernel ? this stupid-web-based forum: where you
can't read the previous thread, once a reply is started> was assumed to be b64.
What is its size - that you made. Now I need b32:rtl*23bc for Core.
OK now I see your text BELOW my editing: illogical reversed sequence!!
>It would be helpful if you could test the 32-bit driver and verify that it works.
Yes, give a sequence of test commands.

[Juanito]

Reboot Core without any wifi related extensions set "onboot".

Then:

Code: [Select]

$ tce-load -i rtl8723bs-KERNEL
$ tce-load -i wifi
$ sudo wifi.sh
If things do not work, post the output from:

Code: [Select]

$ dmesg | tail -20
$ lsmod

[labeas]

Now I'm back in Atom:UEFI:TC64:Ver10:withVer7.2<apps>, searching
# find /mnt -name *23bs* =
ls -l /mnt/sda1/WiFiInstall/10.x/rtl8723bs-4.19.10-tinycore.tcz 221184
ls -l /mnt/sda2/Core32/Wifi/rtl8723bs-4.19.10-tinycore.tcz 221184
See how all the stuff is duplicated in the CHAOS!
Now I'll boot to Core & install *rtl8723bs* and try some tests from
 <TCwifiWiki>.
======= Now in Atom:Core.
$ tce-load -i /mnt/sda2/Core32/Wifi/rtl8723bs-4.19.10-tinycore.tcz
= Screen overflowed trace pasted:----
ACPI: AC: found native INT33F4 PMIC, not loading
usb 1-1: new low-speed USB device number 19 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.000E/input/input21
hid-generic 0003:0458:003A.000E: input,hidraw0: USB HID v1.11 Mouse [Genius USB Optical Mouse] on usb-0000:00:14.0-1/input0

tc@box:/mnt/sda2/Core32/gpm.mc$ tce-load -i /mnt/sda2/Core32/Wifi/rtl8723bs-4.19.10-tinycore.tcz
rtl8723bs-4.19.10-tinycore.tcz: OK
tc@box:/mnt/sda2/Core32/gpm.mc$ ACPI: AC: found native INT33F4 PMIC, not loading
ACPI: AC: found native INT33F4 PMIC, not loading
udevd[1935]: symlink '../event9' '/dev/input/by-id/usb-SINO_WEALTH_USB_KEYBOARD-event-if01.udev-tmp' failed: File exists

r8723bs: module is from the staging directory, the quality is unknown, you have been warned.
r8723bs: Unknown symbol cfg80211_inform_bss_frame_data (err -2)
r8723bs: Unknown symbol cfg80211_scan_done (err -2)
r8723bs: Unknown symbol cfg80211_new_sta (err -2)
r8723bs: Unknown symbol cfg80211_disconnected (err -2)
r8723bs: Unknown symbol wiphy_new_nm (err -2)
r8723bs: Unknown symbol wiphy_register (err -2)
r8723bs: Unknown symbol cfg80211_put_bss (err -2)
r8723bs: Unknown symbol cfg80211_roamed (err -2)
r8723bs: Unknown symbol cfg80211_ibss_joined (err -2)
r8723bs: Unknown symbol cfg80211_michael_mic_failure (err -2)
r8723bs: Unknown symbol wiphy_apply_custom_regulatory (err -2)
r8723bs: Unknown symbol ieee80211_get_channel (err -2)
r8723bs: Unknown symbol cfg80211_del_sta_sinfo (err -2)
r8723bs: Unknown symbol wiphy_unregister (err -2)
r8723bs: Unknown symbol cfg80211_get_bss (err -2)
r8723bs: Unknown symbol cfg80211_mgmt_tx_status (err -2)
r8723bs: Unknown symbol cfg80211_rx_mgmt (err -2)
r8723bs: Unknown symbol ieee80211_frequency_to_channel (err -2)
r8723bs: Unknown symbol cfg80211_connect_done (err -2)
r8723bs: Unknown symbol cfg80211_unlink_bss (err -2)
r8723bs: Unknown symbol wiphy_free (err -2)

-> # df == ...
/dev/loop9                 412       412         0 100% /tmp/tcloop/slang
/dev/loop10                216       216         0 100% /tmp/tcloop/rtl8723bs-4.19.10-tinycore
/dev/sdc2              5253408   2945268   2018240  59% /mnt/sdc2
? rtl8723bs <small size> from attempted: `tce-load -i <rtl8723bs>`  ?
=====> Find <TCwifiWiki> for some test-commands:-
-> # find /mnt -name *iki* = not applicable
-> # FnDirDayStr /mnt 22 iki | less == ...

/mnt/sda1/fimwrLog:====> Follow trace/confirm steps per <TC:wifiWiki>
/mnt/sda1/fimwrLog:> find /mnt/sdc2/CRG -name *iki* => /mnt/sdc2/CRG/wikiWifi
Some comands to test:
# modprobe -l | grep rtl == ...
kernel.tclocal/drivers/net/wireless/realtek/rtl8723bs/r8723bs.ko.gz
# iwconfig = iwconfig: not found
# iwlist scanning = iwlist: not found
# udhcpc -i *interface* = udhcpc: SIOCGIFINDEX: No such device
# wpa_passphrase *essid* *passphrase*  = wpa_passphrase: not found
These are not commands of <rtl8723bs-4.19.10>
How to continue testing ? Now Core has only <rtl8723bs> & mc & gpm.
-------------------Now at Win10:wifi-capable.
> Reboot Core without any wifi related extensions set "onboot".
 ? onboot ?
OK: tce-load -i wifi <- must seek URL
  will allow some tests.

[Juanito]

$ tce-load -i /mnt/sda2/Core32/Wifi/rtl8723bs-4.19.10-tinycore.tcz

I would guess that the directory /mnt/sda2/Core32/Wifi/ does not contain rtl8723bs-4.19.10-tinycore.tcz.dep and thus the extensions wireless-KERNEL, firmware-rtlwifi and firmware-rtl_bt do not get loaded, which is why you get the "r8723bs: Unknown symbol cfg80211" errors...

[labeas]

Quote from: labeas on December 14, 2019, 11:59:06 PM
$ tce-load -i /mnt/sda2/Core32/Wifi/rtl8723bs-4.19.10-tinycore.tcz
Quote:----
I would guess that the directory /mnt/sda2/Core32/Wifi/
 does not contain rtl8723bs-4.19.10-tinycore.tcz.dep and
 thus the extensions wireless-KERNEL,
 firmware-rtlwifi and firmware-rtl_bt do not get loaded,
 which is why you get the "r8723bs: Unknown symbol cfg80211" errors...
----  Yes, but I never include *.dep if I MUST <wget via M$>,
since I must manually trace-down-to-the-tree-leaves.
It's intolerable! Where's the *.bat which would allow M$ get the whole tree,
by using the *.dep info. Or at least a TCscript which would:
 getTopDep ...... no: it's not that easy. It must recursively: fetch & read.
It was very painfull installing gpm & mc via win10.
I should never have started this journey.

[Juanito]

Yes, but I never include *.dep...

..which explains why things don't work for you...

[labeas]

Of course, I was wrong: the <tree doc> contains all info
allowing a SINGLE M$ onLine session to get all needed *.tcz.

Instructions: ----------------------->

Code: [Select]

$ tce-load -i rtl8723bs-KERNEL <- <kernel>
$ tce-load -i wifi <- must seek URL-LIST
$ sudo wifi.sh
If things do not work, post the output from:
$ dmesg | tail -20
$ lsmod
-----------------------> # dmesg | tail -22

Code: [Select]

r8723bs: Unknown symbol cfg80211_ibss_joined (err -2)
r8723bs: Unknown symbol cfg80211_michael_mic_failure (err -2)
r8723bs: Unknown symbol wiphy_apply_custom_regulatory (err -2)
r8723bs: Unknown symbol ieee80211_get_channel (err -2)
r8723bs: Unknown symbol cfg80211_del_sta_sinfo (err -2)
r8723bs: Unknown symbol wiphy_unregister (err -2)
r8723bs: Unknown symbol cfg80211_get_bss (err -2)
r8723bs: Unknown symbol cfg80211_mgmt_tx_status (err -2)
r8723bs: Unknown symbol cfg80211_rx_mgmt (err -2)
r8723bs: Unknown symbol ieee80211_frequency_to_channel (err -2)
r8723bs: Unknown symbol cfg80211_connect_done (err -2)
r8723bs: Unknown symbol cfg80211_unlink_bss (err -2)
r8723bs: Unknown symbol wiphy_free (err -2)
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
-------------------------------> # lsmod ==

Code: [Select]

Module                  Size  Used by    Tainted: G 
r8723bs               364544  0
cfg80211              167936  1 r8723bs
cpufreq_userspace      12288  0
cpufreq_powersave      12288  0
cpufreq_conservative    12288  0
mmc_block              24576  0
squashfs               28672 19
zstd_decompress        53248  1 squashfs
xxhash                 16384  1 zstd_decompress
loop                   20480 38
rtsx_usb_ms            12288  0
rtsx_usb_sdmmc         16384  0
memstick               12288  1 rtsx_usb_ms
rtsx_usb               12288  2 rtsx_usb_ms,rtsx_usb_sdmmc
sdhci_acpi             12288  0
sdhci                  32768  1 sdhci_acpi
mmc_core               65536  5 r8723bs,mmc_block,rtsx_usb_sdmmc,sdhci_acpi,sdhci
8250_dw                12288  0
int3403_thermal        12288  0
int3406_thermal        12288  0
video                  28672  1 int3406_thermal
pcspkr                 12288  0
backlight              12288  2 int3406_thermal,video
int3400_thermal        12288  0
acpi_thermal_rel       12288  1 int3400_thermal
xhci_pci               12288  0
xhci_hcd               86016  1 xhci_pci
mei_txe                16384  0
intel_hid              12288  0
sparse_keymap          12288  1 intel_hid
processor_thermal_device    12288  0
intel_soc_dts_iosf     12288  1 processor_thermal_device
int340x_thermal_zone    12288  2 int3403_thermal,processor_thermal_device
lpc_ich                20480  0
iosf_mbi               12288  2 sdhci_acpi,intel_soc_dts_iosf
mei                    36864  1 mei_txe
--------------------------> dfOrder shows the ORDER of: tce-load -i *.tcz

Code: [Select]

Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                 1737004     17320   1719684   1% /
tmpfs                   965000         0    965000   0% /dev/shm
/dev/sda1              3632412    523832   2904344  15% /mnt/sda1
/dev/sda2             11367568    836472  10531096   7% /mnt/sda2
/dev/loop0                1300      1300         0 100% /tmp/tcloop/glib2
/dev/loop1                 108       108         0 100% /tmp/tcloop/gpm
/dev/loop2                  16        16         0 100% /tmp/tcloop/libffi
/dev/loop3                 344       344         0 100% /tmp/tcloop/libgcrypt
/dev/loop4                  44        44         0 100% /tmp/tcloop/libgpg-error
/dev/loop5                  92        92         0 100% /tmp/tcloop/libssh2
/dev/loop6                1356      1356         0 100% /tmp/tcloop/mc
/dev/loop7                 212       212         0 100% /tmp/tcloop/ncursesw
/dev/loop8                 256       256         0 100% /tmp/tcloop/pcre
/dev/loop9                 412       412         0 100% /tmp/tcloop/slang
/dev/loop10                216       216         0 100% /tmp/tcloop/rtl8723bs-4.19.10-tinycore
/dev/loop11                 12        12         0 100% /tmp/tcloop/libiw
/dev/loop12                320       320         0 100% /tmp/tcloop/libnl
/dev/loop13               1124      1124         0 100% /tmp/tcloop/openssl
/dev/loop14                128       128         0 100% /tmp/tcloop/readline
/dev/loop15                  8         8         0 100% /tmp/tcloop/wifi
/dev/loop16               3208      3208         0 100% /tmp/tcloop/wireless-4.19.10-tinycore
/dev/loop17                 48        48         0 100% /tmp/tcloop/wireless_tools
/dev/loop18                340       340         0 100% /tmp/tcloop/wpa_supplicant
    [EDIT]: Added code tags.  Rich

[Juanito]

The reason that you were requested to use rtl8723bs-KERNEL.tcz.dep was to ensure that all of the required extensions were loaded and in the correct order.

From your post above, it does not appear that you loaded the firmware extensions?

If you do not wish to use the dep file, the extensions need to be loaded in the following order:

1. firmware-rtl_bt
2. firmware-rtlwifi
3. wireless-4.19.10-tinycore
4. rtl8723bs-4.19.10-tinycore

After loading these extensions, you can then load the wifi extension and all of its deps and run "sudo wifi.sh".

[labeas]

Given the number of Microsoft fans here: why haven't you got a *.bat
 with args: <baseURL>, tczName, mkdir:ORDER
----
Sorry TCboys: I'm not interested in monkey-style: doA,doB...
I need to understand the underlying theory.
Let's see if/how <dep file> can give REQUIRED-ORDER of `tce-load`?
ORDER implies <time sequencing>; implies A must happen before B.
The order of loading the nodes of any stand-alone-binary, like mc,
is normally irrelevant.
OTOH once, any <pid of mc is active> theoretically some event
 [eg. start pidX] could be programed to be prevented from running.

    [EDIT]: Removed MS slur.  Rich

[Juanito]

The order of loading extensions does not matter in many cases.

The "underlying theory" in this specific case is that many of the wireless device drivers need firmware to work.

When the wireless device driver loads it tries once to load the firmware and if it does not find it, it gives up - this means that the firmware needs to be loaded before the wireless device driver or wifi will not work.

[Rich]

Hi labeas
Please refrain from your  "clever"  spelling of Microsoft. If you feel a need to bash them, take it elsewhere. I'm sure there are sites
out there that specialize in that. Politics have no place here.