Tiny Core Base > Corepure64
wifi on Linx 7 (rtl8723bs)
mdt01:
Hi
I wonder if anyone can help with this? I have some Linx 7 tablets for a project. They have an atom processor and originally came with Windows 8.1 (32 bit) and have been running Windows 10 (32 bit) fine. I would like to run a 64 bit program so need a 64 bit OS. They only have 32 bit efi so Windows 64 will not load but I have been using Ubuntu_16.04 64 bit thanks to the methods of Linuxium detailed here: http://linuxiumcomau.blogspot.com/2017/06/customizing-ubuntu-isos-documentation.html .
Ubuntu works fine but uses a lot of the availabe 1GB of RAM, leaving not much for my program which becomes very slow due to lots of swapping to disk. I would like more free memory to use, so TinyCore64 seems ideal.
I have managed to boot TinyCore64 (from USB so far) by borrowing the modified 32-64 boot_efi file from Linuxium's method and it mostly seems to work except I can't get the wifi working. A usb-ethernet adaptor is giving me internet access for now but I need the wifi for operational use.
I have followed the steps detailed in the wifi setup instructions but the wifi is not found.
The wifi device is a RTL8723bs. It works fine under Windows or Ubuntu.
Specifically I have tried the following:
Boot with no wifi extensions loaded
Load firmware-rtlwifi extension
Load the wifi extension, which also loads wireless_tools, wireless -4.19.10-tinycore64, libiw, wpa_supplicant-dbus, openssl and libnl
Run sudo wifi.sh which reports : No wifi devices found
Run iwconfig which reports: dummy0 no wireless extensions, eth0 no wireless extensions, lo no wireless extensions, tun10 no wireless extensions, ip_vti0 no wireless extensions.
dmesg | tail -20 gives :
loop: module loaded
zram0: detected capacity change from 0 to 213274624
random: mkswap: uninitialized urandom read (16 bytes read)
Adding 208272k swap on /dev/zram0. Priority:-2 extents:1 across:208272k SSFS
squashfs: version 4.0 (2009/01/31) Phillip Lougher
FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
random: crng init done
r8152 1-1.4.2:1.0 eth0: carrier on
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
ACPI: AC: found native INT33F4 PMIC, not loading
ACPI: AC: found native INT33F4 PMIC, not loading
ACPI: AC: found native INT33F4 PMIC, not loading
I also tried the wicd method which shows the usb ethernet connection but says no wirless device found.
Any help would be much appreciated.
Thanks
Martin
jazzbiker:
Hi, mdt01!
Looks strange, firmware-rtlwifi.tcz includes binaries for your rtl8723bs. Do you load this extension manually or it stands first in your onboot.lst?
You can load then pci-utils.tcz and list your devices using
--- Code: ---lspci
--- End code ---
or
--- Code: ---lspci -v
--- End code ---
to see more details including driver in use, maybe with some grepping.
Also You can use lshw.tcz for
--- Code: ---sudo lshw -c network
--- End code ---
Good luck!
jazzbiker:
By the way, what the use of running 64-bit on 1G RAM?
Can the efi correction disturb something?
mdt01:
Thanks jazzbiker
I have tried loading firmware-rtlwifi.tcz onboot, first in the onboot.lst, or manually and it makes no difference.
Interestingly lspci, lspci -v or even lspci -vv gives nothing about the wifi device or driver. lsusb finds only the wired usb-ethernet device and driver.
I can't find lshw.tcz in the app browser - could lshw be in another extension or have I missed something?
I can run sudo lshw on Ubuntu on the same machine and it finds wlan0. I don't inderstand the output of lshw but it looks like the wlan0 is listed separately at the end rather than under the pci section. I wonder if it is on some other bus - I don't know enough about computer architecture to understand the possibilities.
I know it sounds odd wanting to run a 64 bit os on a machine with 1GB RAM, but part of my project works best with a windows binary which was compiled in 64 bit and running this in WINE on Ubuntu does the job nicely apart from the Ubuntu OS using up so much memory which slows it down bigtime. I don't think the 64 bit os on 32 bit efi should be the issue as I think I undertand that Linux takes over once you have got it to boot.
It works OK on Ubuntu - I wonder if they have more drivers/firmware and if there is a way I can figure out how Ubuntu is making it work - but I am not that knowledgeable about Linux internals.
Thanks for your help.
Rich:
Hi mdt01
--- Quote from: mdt01 on September 27, 2019, 08:48:12 PM --- ... Interestingly lspci, lspci -v or even lspci -vv gives nothing about the wifi device or driver. lsusb finds only the wired usb-ethernet device and driver. ...
--- End quote ---
Maybe you need to update the PCI database:
--- Quote --- use "sudo update-pciids" to get the latest pci device data from the web
note that the full gnu versions of gzip and curl are required for the above
add usr/local/share/hwdata/pci.ids.gz to your backup to keep the update
--- End quote ---
This was from the .info file of the 32 bit version. This note is missing from the 64 bit .info file.
--- Quote ---I can't find lshw.tcz in the app browser - could lshw be in another extension or have I missed something?
--- End quote ---
It doesn't appear to exist in the 64 bit repository.
--- Quote ---It works OK on Ubuntu - I wonder if they have more drivers/firmware and if there is a way I can figure out how Ubuntu is making it work - but I am not that knowledgeable about Linux internals.
--- End quote ---
If you run:
--- Code: ---lsmod
--- End code ---
you'll get a list of loaded drivers.
Navigation
[0] Message Index
[#] Next page
Go to full version