Tiny Core Linux
Tiny Core Base => Corepure64 => Topic started by: labeas on December 24, 2016, 10:04:08 AM
-
TC on a USBstik sure is a convenient debugging tool;
but I'm having big problems trying to install a WiFi driver to linux.
Becaause I thought I already had the compiler, installer facilities
on a [mostly] working Debian7, I tried that to get the WiFi working
under Linux Debian, before copying it to TC.
Compiling the Network adapter Realtek RTL8723BE device driver's few
source files turns out to be a massive problem:
first to update/fix the make/gcc. Then I still fail.
The d/l is from
https://github.com/lwfinger/rtlwifi_new/tree/rock.new_btcoex
and the sources are documented as coming from RealT [Taiwan].
So why can't they just provide the binary executable for the specific
RTL8723BE, instead of the whole directory-tree to compile/maintain
for 6 different models ?
I can't advance the capability of my TC without WiFi connectivity.
== lab.eas
-
Did you try to compile the drivers on corepure64?
If so, you could post the error message(s) here so people can help.
-
I just built the entire selection of WiFi kernel drivers from their latest git source for corepure64 without issues.
These files are available from one source now
https://github.com/lwfinger/rtlwifi_new.git
firmware
rtl8188ee
rtl8192c
rtl8192ce
rtl8192cu
rtl8192de
rtl8192ee
rtl8192se
rtl8723ae
rtl8723be
rtl8723com
rtl8821ae
rtl_pci
rtl_usb
rtlwifi
It's assumed they will be installed with latest kernel but whether that translates to backporting to earlier kernel versions is left to be seen.
I'll submit an updated RTL extension here asap, hopefully they will be included in tc-8.x
The firmware is included in the download.
...
Building modules, stage 2.
MODPOST 15 modules
CC /tmp/RTL/rtlwifi_new/btcoexist/btcoexist.mod.o
LD [M] /tmp/RTL/rtlwifi_new/btcoexist/btcoexist.ko
CC /tmp/RTL/rtlwifi_new/rtl8188ee/rtl8188ee.mod.o
LD [M] /tmp/RTL/rtlwifi_new/rtl8188ee/rtl8188ee.ko
CC /tmp/RTL/rtlwifi_new/rtl8192c/rtl8192c-common.mod.o
LD [M] /tmp/RTL/rtlwifi_new/rtl8192c/rtl8192c-common.ko
CC /tmp/RTL/rtlwifi_new/rtl8192ce/rtl8192ce.mod.o
LD [M] /tmp/RTL/rtlwifi_new/rtl8192ce/rtl8192ce.ko
CC /tmp/RTL/rtlwifi_new/rtl8192cu/rtl8192cu.mod.o
LD [M] /tmp/RTL/rtlwifi_new/rtl8192cu/rtl8192cu.ko
CC /tmp/RTL/rtlwifi_new/rtl8192de/rtl8192de.mod.o
LD [M] /tmp/RTL/rtlwifi_new/rtl8192de/rtl8192de.ko
CC /tmp/RTL/rtlwifi_new/rtl8192ee/rtl8192ee.mod.o
LD [M] /tmp/RTL/rtlwifi_new/rtl8192ee/rtl8192ee.ko
CC /tmp/RTL/rtlwifi_new/rtl8192se/rtl8192se.mod.o
LD [M] /tmp/RTL/rtlwifi_new/rtl8192se/rtl8192se.ko
CC /tmp/RTL/rtlwifi_new/rtl8723ae/rtl8723ae.mod.o
LD [M] /tmp/RTL/rtlwifi_new/rtl8723ae/rtl8723ae.ko
CC /tmp/RTL/rtlwifi_new/rtl8723be/rtl8723be.mod.o
LD [M] /tmp/RTL/rtlwifi_new/rtl8723be/rtl8723be.ko
CC /tmp/RTL/rtlwifi_new/rtl8723com/rtl8723-common.mod.o
LD [M] /tmp/RTL/rtlwifi_new/rtl8723com/rtl8723-common.ko
CC /tmp/RTL/rtlwifi_new/rtl8821ae/rtl8821ae.mod.o
LD [M] /tmp/RTL/rtlwifi_new/rtl8821ae/rtl8821ae.ko
CC /tmp/RTL/rtlwifi_new/rtl_pci.mod.o
LD [M] /tmp/RTL/rtlwifi_new/rtl_pci.ko
CC /tmp/RTL/rtlwifi_new/rtl_usb.mod.o
LD [M] /tmp/RTL/rtlwifi_new/rtl_usb.ko
CC /tmp/RTL/rtlwifi_new/rtlwifi.mod.o
LD [M] /tmp/RTL/rtlwifi_new/rtlwifi.ko
make[1]: Leaving directory '/usr/src/linux-4.2.9'
first install compiletc.tcz, git.tcz and linux-kernel-sources-env.tcz
tce-load -iw git compiletc linux-kernel-sources-env
then run the kernel sources
linux-kernel-sources-env.sh
download the module source files & firmware
mkdir -p /tmp/RTL
cd /tmp/RTL
git clone https://github.com/lwfinger/rtlwifi_new.git
cd rtlwifi_new
make modules
sudo make clean
sudo make
copy
rtl8723be.ko
rtl8723-common.ko
rtl_pci.ko
rtl_usb.ko
rtlwifi.ko
to /lib/modules/4.2.9-tinycore64/kernel/drivers/RTL
(create directories as needed)
and copy firmware
rtl8723fw.bin
rtl8723fw_B.bin
to /usr/local/lib/firmware/rtlwifi
Looks like you'll need the Wifi.tcz (extension) installed and loaded before modprobe'ing the driver
tce-load -iw Wifi
sudo depmod -a
sudo modprobe rtlwifi check dmesg for any install info
then run the Wifi extension
with your module there is support for antenna selection, which might need a config file.
not sure if you need to copy the BT module (btcoexist.ko) aswell?
And don't forget to make a TC backup of all these files in their locations
-
it turns out that all but the actual rtl8723be module is installed when loading wifi.tcz
You might only need to copy
rtl8723be.ko
and both firmware files
-
>I just built the entire selection of WiFi kernel drivers from their
> latest git source for corepure64 without issues....etc.
That seems a massive task, you've done. Apparentlly the hardware supplier
give the drivers to M$pook; but where are the drivers from the rest of the
linux community for these relatively <not new> devices?
...
>it turns out that all but the actual rtl8723be module is installed when loading wifi.tcz
>
>You might only need to copy
>rtl8723be.ko <-available from: https://github.com/lwfinger/rtlwifi_new.git
>and both firmware files <-The firmware is included in the download.
The <slick> search facility of:
https://github.com/lwfinger/rtlwifi_new.git
indicated that no rtl8723be.ko exists there;
so just to prove that I've been there, I fetched:
rtl8723befw.bin 31762 bytes
-
>I just built the entire selection of WiFi kernel drivers from their
> latest git source for corepure64 without issues....etc.
That seems a massive task, you've done. Apparentlly the hardware supplier
give the drivers to M$pook; but where are the drivers from the rest of the
linux community for these relatively <not new> devices?
...
>it turns out that all but the actual rtl8723be module is installed when loading wifi.tcz
>
>You might only need to copy
>rtl8723be.ko <-available from: https://github.com/lwfinger/rtlwifi_new.git
>and both firmware files <-The firmware is included in the download.
The <slick> search facility of:
https://github.com/lwfinger/rtlwifi_new.git
indicated that no rtl8723be.ko exists there;
so just to prove that I've been there, I fetched:
rtl8723befw.bin 31762 bytes
I'm sorry, let me try explaining this another way here..
As always, the *.ko files have to be compiled for the specific Kernel version. No body makes the binaries available for multiple kernel versions, That's not the way this works. the driver is provided in later kernels, however make no mistake here someone who maintains the distribution had to compile it and you can too if you need this today (well, in five minutes).
Only the firmware binaries are compatible with various kernels.
It appears that all you need for this device to function correctly is
rtl8723be.ko
rtl8723-common.ko
and
rtl8723fw.bin
rtl8723fw_B.bin
And install the Wifi.tcz (extension) from the ropo
I'll upload the driver (built for kernel v4.2.9 used in TC-7.x) and firmware files in two separate extensions to the repo, however this process takes a few weeks. So I've detailed the very easy steps for you to build the rtl8723be.ko driver file right now for your system, follow the steps as shown. The process detailed in my last post was easy and actually completed in less than five minutes.
Without the hardware it impossible to test driver functionality. I suspect you may need the bluetooth driver and possibly create a config file to specify which antennae to use. You'll know if anything else is needed after installing the driver and firmware by running dmesg from the terminal. Also you know if we have success by running Wifi and the wifi adapter connects to your local network.
-
Ok Please install
firmware-rtlwifi.tcz
wireless-4.2.9-tinycore64.tcz
wifi.tcz
then use wifi to connect
Assuming x86_64 repo, your device is already supported. I'm not sure how I missed that detail :p
-
============ View previous 2 dialogs in Oberon:Color:--
Re: Need WiFi connection
« Reply #6 on: December 25, 2016, 03:12:59 PM »
Quote
Ok Please install
Code: [Select]
firmware-rtlwifi.tcz
wireless-4.2.9-tinycore64.tcz
wifi.tcz
then use wifi to connect
Assuming x86_64 repo, your device is already supported.
I'm not sure how I missed that detail :p
============
« Reply #5 on: December 25, 2016, 08:14:41 AM »
As always, the *.ko files have to be compiled for the specific Kernel
version.
Only the firmware binaries are compatible with various kernels.
It appears that all you need for this device to function correctly is
rtl8723be.ko
rtl8723-common.ko
and
rtl8723fw.bin
rtl8723fw_B.bin
And install the Wifi.tcz (extension) from the repo.
I'll upload the driver (built for kernel v4.2.9 used in TC-7.x)
and firmware files in two separate extensions to the repo,
however this process takes a few weeks.
So I've detailed the very easy steps for you to build the
rtl8723be.ko driver file right now for your system,
follow the steps as shown.
The process detailed in my last post was easy and actually completed
in less than five minutes.
...
...
============
? Where to fetch these files?
?Perhaps <repository> ?
? Search HOW2s for "repo" ?
=> See RepoBrowser http://packages.tinycorelinux.net/
=> Paste URL: <//packages> to on-line IE
& try to fetch 4 packages listed above.
== "COMMING SOON"
=> where:URL did I fetch previously?
http://tinycorelinux.net/7.x/x86_64/tcz
== BIG alphabetic list: no apparent <hot links>
scroll dow == NO rtl*
=> try to follow preiously logged fetches ?
/mc.tcz.dep
=> NB <alphaListing> has <firmware*rtl*wifi*>
Perhaps the TC system is OOO ?
-
? Where to fetch these files?
?Perhaps <repository> ?
? Search HOW2s for "repo" ?
=> See RepoBrowser http://packages.tinycorelinux.net/
=> Paste URL: <//packages> to on-line IE
& try to fetch 4 packages listed above.
== "COMMING SOON"
=> where:URL did I fetch previously?
http://tinycorelinux.net/7.x/x86_64/tcz
== BIG alphabetic list: no apparent <hot links>
scroll dow == NO rtl*
=> try to follow preiously logged fetches ?
/mc.tcz.dep
=> NB <alphaListing> has <firmware*rtl*wifi*>
Perhaps the TC system is OOO ?
How do you mean??
Please use one of these methods
Use the APPS graphical application to install from repo
Or use tce-ab
Or use tce-load -iw
firmware-rtlwifi.tcz
wireless-4.2.9-tinycore64.tcz
wifi.tcz
then use wifi to connect
-
Re: Need WiFi connection
« Reply #6 on: December 25, 2016, 03:12:59 PM »
]Quote
]Ok Please install
]Code: [Select]
]firmware-rtlwifi.tcz <-try:http://tinycorelinux.net/7.x/x86_64/tcz/firmware-rtlwifi.tcz
]wireless-4.2.9-tinycore64.tcz
]wifi.tcz
]
]then use wifi to connect
==> M$ Fetched above 3 files to TCusb:\4tcz
==> Find & read instructions: HOW2 install
=> FAQ:HOW2 install assumes a live inet connection for existing/running TC;
which is *NOT* the case for a user needing to install WiFi for TC,
because no direct inet is available YET under TC.
I could <decode> the probable script which does:
d/l & install <extentions> and simulate it manually;
but I've got enough problems already.
Also:
]dCore Wiki
] A Tiny Core variant that imports packages from Debian or Ubuntu
] repositories to create mountable SCEs (self-contained extensions):
could be of interest, since I've got a Debian7 DVD;
which may be less problematic than REPEATEDLY:
booting M$:Win to d/l files;
booting TC to manually install new files.
-
As mentioned earlier in the thread, to avoid having to go back and forth between m$ and tc to download extensions, take a look at the *tree files in a browser in m$.
For example: http://www.tinycorelinux.net/7.x/x86_64/tcz/wifi.tcz.tree
wifi.tcz
wireless_tools.tcz
wireless-4.2.7-tinycore64.tcz
libiw.tcz
wpa_supplicant.tcz
openssl.tcz
libnl.tcz
wireless_tools.tcz
wireless-4.2.7-tinycore64.tcz
libiw.tcz
..and remember to download the *tcz, *dep and *md5.txt files for each extension.
-
Note, the .tree files do not list the currently used kernel version.
So when this file is used for reference to download extension manually, substitute
wireless-4.2.7-tinycore64.tcz
with
wireless-4.2.9-tinycore64.tcz
-
Sorry, I always assume an Ethernet connection available nearby to use. Temporarily at least for downloading of WiFi drivers and tools. Where there's WiFi there's typically an Ethernet port as well, didn't say readily available but nearby.
:)
-
>As mentioned earlier in the thread, to avoid having to go back and forth between m$ >and tc to download extensions, take a look at the *tree files in a browser in m$.
>For example: http://www.tinycorelinux.net/7.x/x86_64/tcz/wifi.tcz.tree
Now in M$:WiFi that fetched 3 files.
OMG I didn't know that klik-on M$:FarManager [similar to Linux:mc] opens
*tcz files. So I don't need to re-boot to TC to inspect the newly fetched
dir-trees. BTW. the tree/S look excessively deep.
I'll report back if/how I finally got TC:WiFi working.
Thanks.
-
BTW. the tree/S look excessively deep.
What do you mean by this?
-
> the Tree looks excessively deep means:
The depth of the Dir-tree, has many nodes to <pass through> to reach
the deepest leaf. eg.
/home/dog/ears/flea/eyes/molecule/atom/electron/color/LEAF
is the <pattern> that I remember seeing ?
-
Hi labeas
BTW. the tree/S look excessively deep.
Here is the tree file for 7.x/x86_64/tcz/wifi.tcz:
wifi.tcz
wireless_tools.tcz
wireless-4.2.7-tinycore64.tcz
libiw.tcz
wpa_supplicant.tcz
openssl.tcz
libnl.tcz
wireless_tools.tcz
wireless-4.2.7-tinycore64.tcz
libiw.tczwireless_tools.tcz shows up 2 times because both wifi.tcz and wpa_supplicant.tcz depend on it. Since wireless_tools.tcz
shows up 2 times, its dependencies will also show up 2 times.
-
And in addition to those extension dependacies, you'll also need:
" firmware-rtlwifi.tcz " extension loaded onboot
:)
-
]]Ok Please install
]Code: [Select]
]firmware-rtlwifi.tcz <-try:http://tinycorelinux.net/7.x/x86_64/tcz/firmware-rtlwifi.tcz
]wireless-4.2.9-tinycore64.tcz
]wifi.tcz
]
]then use wifi to connect
==> M$ Fetched above 3 files to TCusb:\4tcz
==> Find & read instructions: HOW2 install
=> FAQ:HOW2 install assumes a live inet connection for existing/running TC;
which is *NOT* the case for a user needing to install WiFi for TC,
because no direct inet is available YET under TC.
Try to imagine how2, if your only inet connection was a M$:WiFi,
and you needed to fetch the files under M$,
and then copy them to the TCbootStik,
and then reboot to TC,
and then install the M$-fetched *.tcz
*NOT* by the <klik instruction> which assumes the *.tcz will be fetched
by TC and handed to the <tcz installer utility>.
NB. I have installed ONLY the original <CD: iso> and some of my own
utility scripts: to USBstik/usrlocal/sbin
Also `which gcc` ==nX I.e. I can't compile [yet].
But am looking forward to compile/install a x64 version of
the killer utility: wily.
-
]]Ok Please install
]Code: [Select]
]firmware-rtlwifi.tcz <-try:http://tinycorelinux.net/7.x/x86_64/tcz/firmware-rtlwifi.tcz
]wireless-4.2.9-tinycore64.tcz
]wifi.tcz
]
]then use wifi to connect
==> M$ Fetched above 3 files to TCusb:\4tcz
As stated earlier, you need to download:
firmware-rtlwifi.tcz, firmware-rtlwifi.tcz.dep, firmware-rtlwifi.tcz.md5.txt
wireless-4.2.9-tinycore64.tcz, wireless-4.2.9-tinycore64.tcz.dep, wireless-4.2.9-tinycore64.tcz.md5.txt
wifi.tcz, wifi.tcz.dep, wifi.tcz.md5.txt
..as well as any dependency extensions as listed by the relevant tree file - note also that some extensions may not have a *.tcz.dep file.
NB. I have installed ONLY the original <CD: iso> and some of my own
utility scripts: to USBstik/usrlocal/sbin
Did you try the coreplus iso (it has some of the wifi extensions in the iso)?
Also `which gcc` ==nX I.e. I can't compile [yet].
You need the compiletc extension and its (many) deps, so get wifi working first :P
-
The <bottom bar> has now got the WiFi Icon, but I can't find any
commands to test/use WiFi under Linux, without having googled.
It's looking good.
======================
Ok Please install
Code: [Select]
firmware-rtlwifi.tcz =ok
wireless-4.2.9-tinycore64.tcz =ok
wifi.tcz =ok
then use wifi to connect
=====================================
==> Check Got 3 files above: =OK
Try:
-> tce-load -i ./firmware-rtlwifi.tcz =OK
-> tce-load -i ./wireless-4.2.9-tinycore64.tcz =OK
-> tce-load -i ./wifi.tcz =OK
-> dmesg | tail ==
FAT-fs (sda2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
r8169 0000:01:00.1: Direct firmware load for rtl_nic/rtl8411-2.fw failed with error -2
r8169 0000:01:00.1: Falling back to user helper
r8169 0000:01:00.1 eth0: unable to load firmware patch rtl_nic/rtl8411-2.fw (-11)
r8169 0000:01:00.1 eth0: link down
rtl8723be: Using firmware rtlwifi/rtl8723befw.bin
rtl8723be 0000:02:00.0: Direct firmware load for rtlwifi/rtl8723befw.bin failed with error -2
rtl8723be 0000:02:00.0: Falling back to user helper
ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
rtlwifi: rtlwifi: wireless switch is on
=?=> NEW
-> df
Filesystem Size Used Available Use% Mounted on
rootfs 1.6G 31.8M 1.6G 2% /
tmpfs 933.7M 0 933.7M 0% /dev/shm
/dev/sdb1 7.4G 624.4M 6.8G 8% /mnt/sdb1
/dev/loop0 48.0K 48.0K 0 100% /tmp/tcloop/libgpg-error
/dev/loop1 256.0K 256.0K 0 100% /tmp/tcloop/libgcrypt
/dev/loop2 128.0K 128.0K 0 100% /tmp/tcloop/libssh2
/dev/loop3 384.0K 384.0K 0 100% /tmp/tcloop/slang
/dev/loop4 1.2M 1.2M 0 100% /tmp/tcloop/mc
/dev/loop5 352.0K 352.0K 0 100% /tmp/tcloop/firmware-rtlwifi
/dev/loop6 3.0M 3.0M 0 100% /tmp/tcloop/wireless-4.2.9-tinycore64
/dev/loop7 8.0K 8.0K 0 100% /tmp/tcloop/wifi
=> root@box:/home/tc# wget http://dailymaverick.co.za
wget: bad address 'dailymaverick.co.za'
root@box:/home/tc# wget "http://dailymaverick.co.za"
wget: bad address 'dailymaverick.co.za'
!! OMG => WiFi Icon has been added to <bottom bar> !!
But how to use WiFi ? Try <Install gpm>
=> BottomBar>:Apps -> <Picker> => <couldn't load mirror list ? Maybe network issue>
-> which ping == /bin/ping
=> found an IP; but several `ping <IP>` fails.
==> RAM: /etc/resolv.conf 0 Jul 4 201 <-empty: needs IPs
? will need to be re-filled by Setup ??
== Thanks.
-
Did you connect to an access point?
-
Honestly i have no clue what is meant by
==>
<-
etc etc.., sorry
it just makes the request for assistance confusing
-
First you need to add only
firmware-rtlwifi.tcz
wifi.tcz
to the onboot.lst
then you'd never have to load via tce-load -i
-
dmesg | tail
FAT-fs (sda2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
r8169 0000:01:00.1: Direct firmware load for rtl_nic/rtl8411-2.fw failed with error -2
r8169 0000:01:00.1: Falling back to user helper
r8169 0000:01:00.1 eth0: unable to load firmware patch rtl_nic/rtl8411-2.fw (-11)
r8169 0000:01:00.1 eth0: link down
rtl8723be: Using firmware rtlwifi/rtl8723befw.bin
rtl8723be 0000:02:00.0: Direct firmware load for rtlwifi/rtl8723befw.bin failed with error -2
rtl8723be 0000:02:00.0: Falling back to user helper
ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
rtlwifi: rtlwifi: wireless switch is on
I believe nothing wrong here
At this point you need to connect to an access point, run the wifi extension
or
sudo wifi.shvia commandline
-
Hi coreplayer2
Honestly i have no clue what is meant by
==>
<-
etc etc.., sorry
it just makes the request for assistance confusing
Oh good, I was beginning to think maybe it was some new lingo all the kids were using that I was just too old to understand. ::)
-
Rich, for a moment I thought I was going blind..
Meanwhile
select the WiFi icon
or run
sudo wifi.shfrom the command line
-
Are my posts being blocked?
This is the 3rd notification that WiFi is apparently installed now.
Based on Bottom-line ICON & dmesg.
Thanks for help.
What are commands to test & use WiFi ?
So far `ping <IPs>` fails.
Thanks.
-
...Based on Bottom-line ICON & dmesg.
What are commands to test & use WiFi ?
So far `ping <IPs>` fails.
...
Yes the Wifi icon? click on it
Or as explained eirlier..
sudo wifi.shfrom a command prompt
then select from a suitable access point.
-
Hi labeas
I copied this from your other thread
PS. I'm still googling to know how to use the apparently
installed & working WiFi.
Here's the thing, reading your posts it's not clear if you've managed to use wifi extension to connect with an access point.
When all extensions are loaded and you've successfully connected to an access point there's little else you can do in terms of testing.
After loading extensions and you're still having issue, you can run
ifconfig
iwconfig
dmesg | tail 20
to check for anomalies
The wifi connection script is not self launching (by default, though you can change that) therefore you must initiate running the wifi connection script
which activates the wifi interface, scans for access points, requests an IP and passes the SSID and password.
select the Wifi icon, Or run
sudo wifi.sh
follow the prompts to connect with the access point of your choice.
DHCP is enabled by default
:)
-
Notaion:--------
-> : Keyin to system
== : resulting output from system
=> : extra observations/ideas related to above in/out function
<...> : not verbatim/pasted text
]]What are commands to test & use WiFi ?
]]So far `ping <IPs>` fails.
...
] Yes the Wifi icon? click on it
Of course I did that: it opens a <sudo labeled TextFrame> which
disapears when a char is keyed into it.
]r as explained eirlier..
]
]ode: [Select]
]sudo wifi.sh
]from a command prompt
-> sudo wifi.sh == <no device found>
=> must go back to M$ to see if WiFi <router> is still <enabled>.
It goes <off> regularly; not under my control.
I stopped on the way at 32-bit-Debian7 very slow USBstik, and
when I got to M$: its WiFi is/was working.
] then select from a suitable access point.
---------------------------
PS. I posted the following on NNTP:--
Re. 64-bit wily: I'm can't d/l [& install] with my.
[very slow USBstik based] debian7 which is 32-bit; and the TinyCore64
where I want it installed has no inet-connection yet.
If I had the 64-bit binaries, I could perhaps just copy them to TC,
like I've migrated 32-bit wily to several installations.
Does Debian make the binaries available?
-
Did you remember to load the appropriate firmware before you loaded the wifi extension?
You should see something analogous to this in dmesg if things are working: $ dmesg | tail -30
...
Intel(R) Wireless WiFi driver for Linux
Copyright(c) 2003- 2015 Intel Corporation
iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7260-15.ucode failed with error -2
iwlwifi 0000:02:00.0: Falling back to user helper
iwlwifi 0000:02:00.0: loaded firmware version 15.227938.0 op_mode iwlmvm
iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144
iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
wlan0: authenticate with a0:55:4f:66:d5:18
wlan0: send auth to a0:55:4f:66:d5:18 (try 1/3)
wlan0: authenticated
wlan0: associate with a0:55:4f:66:d5:18 (try 1/3)
wlan0: RX AssocResp from a0:55:4f:66:d5:18 (capab=0x411 status=0 aid=3)
wlan0: associated
..and: $ iwconfig
wlan0 IEEE 802.11abgn ESSID:"box"
Mode:Managed Frequency:2.447 GHz Access Point: A0:55:4F:66:D5:18
Bit Rate=11 Mb/s Tx-Power=22 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
Link Quality=54/70 Signal level=-56 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:3 Missed beacon:0
-
It would also be good if you could paste the output of "tce-status -i"
-
Preferably using
[ code ]your text here
[ /code ]
tags (without the spaces), instead of ==> etc. for better readability.
-
Notaion:--------
-> : Keyin to system
== : resulting output from system
=> : extra observations/ideas related to above in/out function
<...> : not verbatim/pasted text
...
I'm sorry, I'm not used to this fancy notation..
I did decipher from your last post, this
sudo wifi.sh
no device found
When the the driver finds the correct firmware you should see the results of scanning access points at the command line
tc@box:~$ sudo wifi.sh
Found wifi device wlan0
Standby for scan of available networks...
Select Wifi Network
ESSID Enc Qual Channel Type
1. coop on 70 4 WPA
2. coop-5G on 70 44 WPA
3. HP-Print-65-LaserJet Pro MFP on 64 4 WPA
4. coop-5G on 63 0 WPA
5. MyCharterWiFi34-2G on 58 1 WPA
6. Vortex-Prime on 51 3 WPA
7. MySpectrumWiFia4-2G on 48 1 WPA
8. Jeffdlightman-Guest on 44 11 WPA
9. RedSpruce-guest off 43 2
10. Jeffdlightman on 43 11 WPA
11. RedSpruce on 42 2 WPA
12. cark Guest Network on 41 11 WPA
13. cark on 41 11 WPA
14. Vortex-Prime-5G on 41 0 WPA
Enter selection ( 1 - 32 ) or (q)uit, (n)ext, (p)revious: :
It looks suspiciously like the driver is loaded before the firmware, so please do in this order: firmware first, driver last
1. place all wireless and required dep. and firmware extensions in /tce/optional (assuming TCL is installed on a USB and is the x86_64 version which I believe it is, otherwise adjust as necessary)
2. reboot
3. tce-load -i firmware-rtlwifi.tcz
4. tce-load -i wifi.tcz
Along with wifi.tcz should see these dep's loaded also
wireless_tools.tcz
wireless-4.2.9-tinycore64.tcz
libiw.tcz
wpa_supplicant.tcz
openssl.tcz
libnl.tcz
Then run
sudo wifi.sh
If you receive the same "device not found" message as before, then post the output of
dmesg | tail -20
-
I find the Forum thread-format confusing:
for a NOT permanently-on-line user.
What about the several *.ko files mentioned.
Must I also install them, to get the <live Icon WiFi> to see the signal?
---------------------------
I'm writing this partly to exercise/prove LinuxNativeOberon,
which runs nicely under TC64, from VT-mode, in a Framebuffer.
With LNO I'm able to clean-up my forum-thread.
Sorry to have to say: the arty/grafiti format of the forum
makes it less functional than NNTPs of the 90s.
The ETHO/wily family allows the user to:
have multiple text frames accessible together on the screen;
mouse driven - at the extreme can be used without keybrd;
no need to look-away from the screen to find the X-key;
User created menus of Commands are just <moused>
also to include parameter/s;
ETHO change color & font to give extra dimension/association
to complexly related text-pieces in several TextFrames,
by merely wipe-text & <dab in sample> of required color/font;
and much more.
-
It's a little difficult to help you solve your problem because, even though several users have suggested things to try, you have not reported back the results clearly.
To repeat what several users have already suggested:
1. Re-boot without loading anything "onboot"
2. Load the firmware-rtlwifi extension.
3. Load the wifi extension
4. Double-check that the wireless_tools, wireless-4.2.9-tinycore64, libiw, wpa_supplicant, openssl and libnl extensions are also loaded.
5. Execute the "sudo wifi.sh" command from a terminal window.
6. Report what you see in the terminal window.
7. Report the results of "dmesg | tail -20"
8. Reports the results of "iwconfig"
Once you have clearly reported back on the results of the above, it will be a lot easier to help you.
-
There are multiple & changing opinions about the procedure to
install WiFi. That's why you need `wily` or even LNO to color
the different opinions, to distinguish the different opinions.
Instead of the ad-hok method: a sequntial/piped operation
is best diagnosed by confirming Sequentially. Eg for a 3G dongle:
* confirm plugged USB device is detected
* confirm it's seen as a CDROM
* confirm that it switched to be a <modem>
* confirm that it's mounted to the <modem device>
...etc.
Importantly: it's pointless to consider stage N if stage N-1 has not
yet been confirmed.
The new opinion, in this thread is that the sequence of loading the
*.tcz is significant?
]1. Re-boot without loading anything "onboot"
No! I need `mc` to control & log the testing process.
]2. Load the firmware-rtlwifi extension.
]3. Load the wifi extension
]4. Double-check that the wireless_tools, wireless-4.2.9-tinycore64,
libiw, wpa_supplicant, openssl and libnl extensions are also loaded.
]5. Execute the "sudo wifi.sh" command from a terminal window.
]6. Report what you see in the terminal window.
]7. Report the results of "dmesg | tail -20"
]8. Reports the results of "iwconfig"
================= Tests done ===================
]4.Confirm loaded: wireless_tools, wireless-4.2.9-tinycore64, libiw,
wpa_supplicant, openssl libnl
-> less `which /mnt/sdb1/Setup` ==
echo "Now load WiFi extentions ? See ICON"
tce-load -i /mnt/sdb1/tce/optional/firmware-rtlwifi.tcz
tce-load -i /mnt/sdb1/tce/optional/wireless-4.2.9-tinycore64.tcz
tce-load -i /mnt/sdb1/tce/optional/wifi.tcz
=> The forum record shows: the above 3 *.tcz ONLY to be loaded ?!
]5. Execute the "sudo wifi.sh" command from a terminal window.
-> sudo wifi.sh == delay & "No wifi devices found!"
=> Previously a TextFrame opened, which dissapeared when any char
was keyed-in.
-> dmesg <relevant lines> == ...
r8169 0000:01:00.1: Direct firmware load for rtl_nic/rtl8411-2.fw failed with error -2
r8169 0000:01:00.1: Falling back to user helper
r8169 0000:01:00.1 eth0: unable to load firmware patch rtl_nic/rtl8411-2.fw (-11)
r8169 0000:01:00.1 eth0: link down
rtl8723be: Using firmware rtlwifi/rtl8723befw.bin
rtl8723be 0000:02:00.0: Direct firmware load for rtlwifi/rtl8723befw.bin failed with error -2
rtl8723be 0000:02:00.0: Falling back to user helper
ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
rtlwifi: rtlwifi: wireless switch is on
usb 1-5.4: new high-speed USB device number 7 using xhci_hcd
usb 1-5.4: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
usb 1-5.4: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
usb-storage 1-5.4:1.0: USB Mass Storage device detected
scsi host5: usb-storage 1-5.4:1.0
]8. Reports the results of "iwconfig"
-> iwconfig == sh: iwconfig: not found
========================================
If someone knows the SEQUENCE of the installation & switch-on &
connect procedure, they should provide the corresponding sequence
of confirmation-tests.
Thanks.
-
]4.Confirm loaded: wireless_tools, wireless-4.2.9-tinycore64, libiw,
wpa_supplicant, openssl libnl
-> less `which /mnt/sdb1/Setup` ==
echo "Now load WiFi extentions ? See ICON"
tce-load -i /mnt/sdb1/tce/optional/firmware-rtlwifi.tcz
tce-load -i /mnt/sdb1/tce/optional/wireless-4.2.9-tinycore64.tcz
tce-load -i /mnt/sdb1/tce/optional/wifi.tcz
=> The forum record shows: the above 3 *.tcz ONLY to be loaded ?!
$ cat wifi.tcz.dep
wireless_tools.tcz
wpa_supplicant.tcz
$ cat wireless_tools.tcz.dep
wireless-KERNEL.tcz
libiw.tcz
$ cat wpa_supplicant.tcz.dep
openssl.tcz
libnl.tcz
wireless_tools.tcz
As already stated, if the deps of the wifi extension are not loaded, it will not work.
]8. Reports the results of "iwconfig"
-> iwconfig == sh: iwconfig: not found
This shows that the wireless_tools extension is not loaded.
You can check which extensions are loaded with the command "tce-status -i".
-
labeas, we realize it's frustrating to learn a new system and how it handles program (extension) installations. So I think it's best we derail your current methodology and suggest you download coreplus.iso then burn it to disk. That way when you boot it with wifi support selected, you'll know immediately how to load and run the WiFi connection utility. I believe all required 32bit extensions are supplied in coreplus.iso, however in worst case scenario you might have to download and install only one extension, maybe..?
Learn the 32bit tinycore using coreplus.iso before diving head first into corepure64.
Don't try to complicate the experience by using corepure64, or core64, or even using MC. Without question, None of these are needed to have a working desktop environment. I'll be honest, I've never figured out how to use MC. If you're more comfortable with MC, then go for it.. However, the Terminal is king, learn to use it, please :)
Know that when you load wifi.tcz and firmware-rtlwifi.tcz automatically at boot using onboot.lst to load extensions, all dependencies listed within dep files are loaded automatically and in the correct order. The important issue here is "firmware must be loaded first", heads up here because there's little or no exception to this rule; "firmware must be loaded before the driver". Otherwise the driver when it loads will never ever find it's firmware and will not work, end of story! You'll have to reboot to try again when attempting manual loading.
Almost every extension has a dep file and md5 file, these are not considered optional. Life will definitely be more relaxing if you download ALL these at the same time.
eg:
wifi.tcz
wifi.tcz.dep
wifi.tcz.md5.txt
Manually loading firmware-rtlwifi.tcz and wifi.tcz requires all extensions and their dep file lists (for those that have dep files) as well. They all need to be installed within mnt/sdb1/tce/optional/ directory.
When you have all required extensions and their supporting files in place within /tce/optional directory the process of connecting to an access point becomes easy.
We're here to help, just ask