Status:--
Laptop <aptio 2015> runs TC64ver7.2 booting syslinux via:
LABEL tcPREmultivt
MENU LABEL Boot TinyCorePure64-PREmultivt
TEXT HELP
Boot TinyCorePure64 with Embedded X/GUI extensions.
Boot media is removable. Use TAB to edit options for specific needs.
ENDTEXT
KERNEL /boot/vmlinuz64
INITRD /boot/corepure64.gz
APPEND loglevel=3 cde vga=788 multivt
Laptop <aptio 2018> needs grub2-multi to boot via:
menuentry "TC64Fix" {
linux /boot64/vmlinuz64Fixd waitusb=10:UUID="bfe6116c-473a-4ee9-bbac-3638039dc9ad"
initrd /boot64/rootfs64.gz /boot64/modules64.gz
}
and except for the Ver10: vmlinuz64Fixd, rootfs64.gz, modules64.gz
the *.tcz & some of my own binaries are from the Ver7.2 system.
It looks OK and the V7.2 opera-12 hasn't got the screen-tearing as when
running under V7.2.
-----
The PROBLEM is that wifi doesn't show info in dmesg & <lspci> after <installing
the wifi firmware>. I can't discover the wifi hardware, except that Win10's
assumed-to-be-wifi-files mentions mostly "RTL18723bs", which is different
from the <aptio 2015> Laptop running Ver7.2 and copied to the V10 kernel system.
Further quirk is that <aptio 2018> doesn't show the <Win10 : native-disk>.
The grub2-multi USBstik shows as sda1,2 ?!
And it shows the SDcard as <mmcblok*1,2>
--------
After many failed attempts, my idea was to try to test/install V7.2 under
grub2-multi, to see if the hardware is shown, instead of <MIXING versions
of boot & *.tcz> files.
But now, I'm asking myself WHAT corresponds to grub2's modules64.gz
for isolinux.cfg?
As I understand it: there's the kernel & <initrd>.
What are the multitude of /EFI/BOOT/grub/x86_64-efi/*.mod files under grub2?
It seems that TC's HOWto, deceptively claims that the user can easily
<swap/chose between syslinux & grub> ?
If the problematic laptop HAS got RTL18723bc, how should I get matching
Wifi-firmware for the Ver10TC64 kernel ?
== TIA
PS. Since the various recommended <lspci probing> all failed, I investigated
using the powerfull *UEFI.shell* to probe the hardware. More extreme/absurd!
BTW. via: google > ubuntu > github: I found/tested a script [but needs bash]
which gives a MASSIVE-DETAILED hardware-equiped-report like:- .....
##### release ###########################
./wireless-info: line 155: lsb_release: command not found
##### kernel ############################
Linux 4.9.0-7-amd64 #1 SMP Debian 4.9.110-1 (2018-07-05) x86_64 unknown unknown GNU/Linux
Parameters: vga=normal, initrd=/slax/boot/initrfs.img, load_ramdisk=1, prompt_ramdisk=0, rw, printk.time=0, slax.flags=automount
##### desktop ###########################
sed: can't read /root/.dmrc: No such file or directory
Could not be determined.
##### lspci #############################
01:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
Subsystem: CLEVO/KAPOK Computer RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1558:0945]
Kernel driver in use: r8169
...
---------------------> The script & it's generated report have sizes:-
17452 : wireless-info
11943 : wireless-info.txt
# This script gathers the infos necessary for troubleshooting a wireless
# connection and saves them in a text file, wrapping it in an archive if it
# exceeds the 19.5 kB size limit for ".txt" attachments on the Ubuntu Forums.
------> Instead of "this complex network of files works for me",
I favour SIMPLIFICATION. Eg. using the proven grub2-bootable "core":
apparently a 32bit, non-gui OS to probe/expose the Wifi hardware.
== WDYS ?
Welcome
FAQ
Downloads
Wiki
