Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: pan on September 11, 2015, 12:34:44 PM
-
I tce-ab installed what's listed in the wireless Wiki page, and firmware-intel and iwlwifi. iwconfig still says no wireless connections. I downloaded a ucore firmware file from Intel's site but didn't know what to do with it. I'm running an x86 OS on a 64 machine to use less space. Thanks in advance.
-
Pending the results of "lsusb" for your hardware, you need to load firmware-intel before you load iwlwifi and then load and use the wifi extension.
If this doesn't work, then the last few lines of "dmesg" would be useful in troubleshooting.
-
By load, do you mean tce-ab, "s" key, query, type number of correct tcz, "q" key when documentation comes up, "i" for install, and then "q" to quit?
-
Yes, but once you've done that, the next time "tce-load -i extension_name" will be enough
-
lsusb doesn't show my wireless because it's PCI, I think, and lspci says the model in the subject title as the last entry. iwconfig shows wlan0 and empty-ish stats. https://plus.google.com/+DanielHithereClemente/posts/3sxz84Bh1bH (https://plus.google.com/+DanielHithereClemente/posts/3sxz84Bh1bH)
-
Did you do as suggested above (load firmware-intel then iwlwifi then wifi)?
What was the output of "sudo wifi.sh" and "dmesg | tail -20"?
-
Yes, and it worked. Sorry for not making it clearer. wifi.sh successfully recognized the network I want to connect to. I put in the password, it looked like it worked, but I couldn't download anything with tce, so I think it failed. https://plus.google.com/+DanielHithereClemente/posts/RitRDAb821b (https://plus.google.com/+DanielHithereClemente/posts/RitRDAb821b)
-
Look at the output, it appears to have worked, but it also looks like you possibly had a wired link, eth0, up?
To be sure that the wireless link is working, it might be better to kill the wired link before connecting: $ ps aux | grep udhcpc
2555 root /sbin/udhcpc -b -i eth0 -x hostname boxdell -p /var/run/udhcpc.eth0.pid
14804 tc grep udhcpc
$ sudo kill 2555
..and then, after connecting with wireless: $ ping -c2 google.com
-
Nothing. Check out my G+ page again. Am I supposed to ifconfig wlan0 up?
-
It'd be easier to follow if you copy/pasted the appropriate lines of dmesg here..
..but no, you shouldn't need "ifconfig wlan0 up".
I'm using an intel wireless 7260 and it works fine without that.
-
I don't know how to do that yet. https://drive.google.com/file/d/0B0xuPaNbyFdsWkd5dG54S2s5QVE/view?usp=docslist_api]]]https://drive.google.com/file/d/0B0xuPaNbyFdsWkd5dG54S2s5QVE/view?usp=docslist_api] (http://)
-
Here's what I get, which seems very similar to yours...
cfg80211: Calling CRDA to update world regulatory domain
Intel(R) Wireless WiFi driver for Linux, in-tree:
Copyright(c) 2003- 2014 Intel Corporation
iwlwifi 0000:02:00.0: irq 63 for MSI/MSI-X
iwlwifi 0000:02:00.0: Direct firmware load failed with error -2
iwlwifi 0000:02:00.0: Falling back to user helper
iwlwifi 0000:02:00.0: loaded firmware version 25.228.9.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 Disabled; Enabling L0S
iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
wlan0: authenticate with 00:19:70:af:ae:26
wlan0: send auth to 00:19:70:af:ae:26 (try 1/3)
wlan0: authenticated
wlan0: associate with 00:19:70:af:ae:26 (try 1/3)
wlan0: RX AssocResp from 00:19:70:af:ae:26 (capab=0x431 status=0 aid=8)
wlan0: associated
cfg80211: Calling CRDA to update world regulatory domain
-
Hi pan
I don't know how to do that yet.
You could redirect the output of the command into a file. For example:
dmesg | tail -20 >dmesg.txtThis will create a file called dmesg.txt which you can now open with an editor so you can copy and paste.
-
It works now, thanks, but sometimes it's slow for some reason.