General TC > Tiny Core Netbooks
How install an external USB wireless adaptor?
Mike7:
With the internal wireless adaptor on and the TP-LINK unplugged:
--- Code: ---tc@box:~$ sudo rfkill list all
0: eeepc-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
--- End code ---
With the internal adaptor disabled and the TP-LINK still unplugged:
--- Code: ---tc@box:~$ sudo rfkill list all
0: eeepc-wlan: Wireless LAN
Soft blocked: yes
Hard blocked: no
--- End code ---
With the internal adaptor disabled and the TP=LINK plugged in:
--- Code: ---tc@box:~$ sudo rfkill list all
0: eeepc-wlan: Wireless LAN
Soft blocked: yes
Hard blocked: no
3: phy2: Wireless LAN
Soft blocked: yes
Hard blocked: no
--- End code ---
Mike7:
Hi, Rich.
When I downloaded rfkill.tcz from the repo, the info screen said this:
Add this command to your bootlocal.sh:
sudo /usr/local/etc/init.d/rfkill start
Is this necessary? What does it do?
Mike
Rich:
Hi Mike7
It is a script used to set which devices are blocked or unblocked. It gets that configuration information from
/usr/local/etc/conf.d/rfkill. The default configuration is to unblock all devices. No, you do not need to run it.
I'm guessing that phy2 is your USB device. Try:
--- Code: ---sudo rfkill unblock 3
--- End code ---
coreplayer2:
IMO the rfkill method appears a little too complicated for my comfort, don't misunderstand though.. am sure rfkill works great. actually find that it's hard to remember whether to switch the device on or off when booting a desired operating system, sometimes the built-in device is automatically re-enabled when it's least wanted.. so I work around this problem by disabling or (as the case may be) blacklisting the built-in device's driver. then install the driver and/or firmware needed to support the external device and use a script to determine if wifi needs to be run at boot up. It's an easy method and has proven extremely reliable for my notebooks, I boot up and always have the best connection available with the minimum of effort.
I'd add the bootcode blacklist=ath5k to disable your onboard PCI WiFi device's driver, then
install only these two extensions
wifi.tcz (plus deps obviously) and
firmware.tcz
should be all you require, then simply run wifi to connect
remove all unnecessary firmware extensions that you might have and you should be good to go..
I believe you'll find that
ath9k_htc (kernel mode driver supporting 0cf3:1006 is provided in wireless-3.8.13-tinycore.tcz which is a dep of wifi.tcz extension)
htc_9271.fw (firmware supporting 0cf3:1006 is provided in firmware.tcz extension)
tinypoodle:
Have you compared impact on energy consumption between rfkill vs. blacklisting?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version