Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: labeas on December 09, 2019, 11:14:54 AM
-
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.
-
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?
-
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?
-
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.
-
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.
-
Reboot Core without any wifi related extensions set "onboot".
Then: $ tce-load -i rtl8723bs-KERNEL
$ tce-load -i wifi
$ sudo wifi.sh
If things do not work, post the output from: $ dmesg | tail -20
$ lsmod
-
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.
-
$ 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...
-
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.
-
Yes, but I never include *.dep...
..which explains why things don't work for you...
-
Of course, I was wrong: the <tree doc> contains all info
allowing a SINGLE M$ onLine session to get all needed *.tcz.
Instructions: ----------------------->
$ 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
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 ==
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
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
-
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".
-
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
-
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.
-
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.
-
=> /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
-
Apparently, my posts are fraudulently altered/reformatted?
This could never happen under NNTP, of past decades.
-
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.
-
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
-
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.
-
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:
blacklist=batteryThat should make the messages go away. It's likely the kernel was not configured to support your Power Management IC.
-
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> ?
-
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
-
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.
-
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.
-
It has already been explained to you several times, please use the forum search function.