WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: How install an external USB wireless adaptor?  (Read 9444 times)

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 2514
How install an external USB wireless adaptor?
« Reply #15 on: April 06, 2014, 05:14:38 AM »
:) I knew this would be asked, no I haven't made a comparison, but let's look at it, is the radio functional without firmware and driver?
Without radio scanning  there is negligible drain..   One can always disable the original onboard hardware   In addition to blacklisting drivers, the method I use is intended to provide flawless function with little regard to power consumption, but that doesn't mean there is any additional drain considering the radio may not be functional without correct firmware and driver. Perhaps it's a moot point?

:)


Sent from my iPhone using Tapatalk
« Last Edit: April 06, 2014, 05:19:36 AM by coreplayer2 »

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 9591
Re: How install an external USB wireless adaptor?
« Reply #16 on: April 06, 2014, 10:08:58 AM »
The radio is probably not functional, but as long as the stick is physically attached, it can draw power from usb/pci/etc.
The only barriers that can stop you are the ones you create yourself.

Offline Mike7

  • Full Member
  • ***
  • Posts: 143
Re: How install an external USB wireless adaptor?
« Reply #17 on: April 06, 2014, 10:51:06 AM »
Rich-

Please keep in mind: I want to be able to choose easily which wireless adaptor is enabled. This is important to me because I am using my netbook both portable, when the external adaptor is cumbersome and may be unnecessary, and as a desktop machine, when space is not a problem and the external adaptor is more powerful. So, whatever method I employ for making the external adaptor functional, it needs to allow easy switching between adaptors.

Quote
I'm guessing that  phy2  is your USB device. Try:
Code: [Select]
sudo rfkill unblock 3

Sorry, but why "unblock 3" if the 0cf3:1006 is phy2? I'm afraid I don't understand what's happening here.

Also, I need for you to specify the situation when I enter the command (Fn>F2 on or off, external device plugged or unplugged, etc.).

Mike
Asus eeePC 1000HA, Intel Atom N270 CPU, 1GB RAM, 160GB HDD, CorePlus-5.1 on 8GB flash drive.

Offline Mike7

  • Full Member
  • ***
  • Posts: 143
Re: How install an external USB wireless adaptor?
« Reply #18 on: April 06, 2014, 12:44:28 PM »
coreplayer2-

Sorry if I'm being repetitious or stating the obvious, but, like I said in my last reply to Rich, I want to be able to choose which wireless adaptor I'm using at any given time. We're in agreement about that, right?

Quote
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

That shouldn't be a problem for me, though, because I'll only be using one Core OS. Right?

Quote
sometimes the built-in device is automatically re-enabled when it's least wanted

Not good, but weird things happen all the time <grin>.

Quote
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.

How can you use a script to determine if wifi needs to be run at boot, or to determine which adaptor is enabled? The script is only read at or after the boot, and then it's too late to make decisions. Sounds like a catch-22 to me.

Quote
I boot up and always have the best connection available with the minimum of effort.

The best of all worlds. But how does the boot process know which adaptor and connection you want at the time?

Quote
I'd add the bootcode  blacklist=ath5k  to disable your onboard PCI WiFi device's driver

Is there an "unblacklist" command to re-enable the onboard device's driver when I want to use that device? If I'm switching between adaptors, why make either one the default with a boot code?

Quote
then install only these two extensions

wifi.tcz  (plus deps obviously) and
firmware.tcz

They are in the CorePlus-5.1 optional/ folder and also in onboot.lst.

Quote
should be all you require, then simply run wifi to connect

So all I'm missing is blacklist=ath5k? If that were the case, why isn't the external device already getting enabled, since the software for it is installed at the boot?

Quote
remove all unnecessary firmware extensions that you might have and you should be good to go

I'm not happy about removing firmware extensions willy-nilly, from either the optional/ folder or onboot.lst. What about firmware-atheros.tcz or firmware-zd12ll.tcz? If these are no longer necessary, or are contained in firmware.tcz or wireless-3.8.13-tinycore.tcz, why are they installed separately in CorePlus's optional/ folder?

Quote
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)

Cool.

M.
Asus eeePC 1000HA, Intel Atom N270 CPU, 1GB RAM, 160GB HDD, CorePlus-5.1 on 8GB flash drive.

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 5430
Re: How install an external USB wireless adaptor?
« Reply #19 on: April 06, 2014, 01:39:29 PM »
Hi Mike7
Quote
Sorry, but why "unblock 3" if the 0cf3:1006 is phy2? I'm afraid I don't understand what's happening here.
I got 3 from this:
Code: [Select]
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
The number on the left is the index number of the device. That is what you pass to rfkill.
Don't be afraid to take advice from coreplayer2. He has far more experience with wireless than I do.

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 2514
Re: How install an external USB wireless adaptor?
« Reply #20 on: April 07, 2014, 12:57:22 PM »
Quote
remove all unnecessary firmware extensions that you might have and you should be good to go

I'm not happy about removing firmware extensions willy-nilly, from either the optional/ folder or onboot.lst. What about firmware-atheros.tcz or firmware-zd12ll.tcz? If these are no longer necessary, or are contained in firmware.tcz or wireless-3.8.13-tinycore.tcz, why are they installed separately in CorePlus's optional/ folder?



Ok,
firmware extensions contain firmware files,
(modules)-3.8.13-tinycore extensions contain modules (drivers).   

eg:
"firmware.tcz" contains the following firmware files for a wide variety of hardware.
Code: [Select]
usr/local/lib/firmware/3com/3C359.bin
usr/local/lib/firmware/3com/typhoon.bin
usr/local/lib/firmware/GPL-3
usr/local/lib/firmware/LICENCE.agere
usr/local/lib/firmware/LICENCE.ca0132
usr/local/lib/firmware/LICENCE.ene_firmware
usr/local/lib/firmware/LICENCE.go7007
usr/local/lib/firmware/LICENCE.ibt_firmware
usr/local/lib/firmware/LICENCE.qla2xxx
usr/local/lib/firmware/LICENCE.tda7706-firmware.txt
usr/local/lib/firmware/LICENCE.via_vt6656
usr/local/lib/firmware/LICENCE.xc5000
usr/local/lib/firmware/LICENSE.dib0700
usr/local/lib/firmware/README
usr/local/lib/firmware/TDA7706_OM_v2.5.1_boot.txt
usr/local/lib/firmware/TDA7706_OM_v3.0.2_boot.txt
usr/local/lib/firmware/WHENCE
usr/local/lib/firmware/acenic/tg1.bin
usr/local/lib/firmware/acenic/tg2.bin
usr/local/lib/firmware/adaptec/starfire_rx.bin
usr/local/lib/firmware/adaptec/starfire_tx.bin
usr/local/lib/firmware/advansys/3550.bin
usr/local/lib/firmware/advansys/38C0800.bin
usr/local/lib/firmware/advansys/38C1600.bin
usr/local/lib/firmware/advansys/mcode.bin
usr/local/lib/firmware/agere_ap_fw.bin
usr/local/lib/firmware/agere_sta_fw.bin
usr/local/lib/firmware/ar3k/1020200/PS_ASIC.pst
usr/local/lib/firmware/ar3k/1020200/RamPatch.txt
usr/local/lib/firmware/ar3k/1020200/ar3kbdaddr.pst
usr/local/lib/firmware/ar3k/1020201/PS_ASIC.pst
usr/local/lib/firmware/ar3k/1020201/RamPatch.txt
usr/local/lib/firmware/ar3k/30000/PS_ASIC.pst
usr/local/lib/firmware/ar3k/30000/RamPatch.txt
usr/local/lib/firmware/ar3k/30000/ar3kbdaddr.pst
usr/local/lib/firmware/ar3k/30101/PS_ASIC.pst
usr/local/lib/firmware/ar3k/30101/RamPatch.txt
usr/local/lib/firmware/ar3k/30101/ar3kbdaddr.pst
usr/local/lib/firmware/ar3k/30101coex/PS_ASIC.pst
usr/local/lib/firmware/ar3k/30101coex/PS_ASIC_aclHighPri.pst
usr/local/lib/firmware/ar3k/30101coex/PS_ASIC_aclLowPri.pst
usr/local/lib/firmware/ar3k/30101coex/RamPatch.txt
usr/local/lib/firmware/ar3k/30101coex/ar3kbdaddr.pst
usr/local/lib/firmware/ar3k/AthrBT_0x01020001.dfu
usr/local/lib/firmware/ar3k/AthrBT_0x01020200.dfu
usr/local/lib/firmware/ar3k/AthrBT_0x01020201.dfu
usr/local/lib/firmware/ar3k/AthrBT_0x11020000.dfu
usr/local/lib/firmware/ar3k/AthrBT_0x31010000.dfu
usr/local/lib/firmware/ar3k/ramps_0x01020001_26.dfu
usr/local/lib/firmware/ar3k/ramps_0x01020200_26.dfu
usr/local/lib/firmware/ar3k/ramps_0x01020200_40.dfu
usr/local/lib/firmware/ar3k/ramps_0x01020201_26.dfu
usr/local/lib/firmware/ar3k/ramps_0x01020201_40.dfu
usr/local/lib/firmware/ar3k/ramps_0x11020000_40.dfu
usr/local/lib/firmware/ar3k/ramps_0x31010000_40.dfu
usr/local/lib/firmware/atmsar11.fw
usr/local/lib/firmware/av7110/bootcode.bin
usr/local/lib/firmware/carl9170-1.fw
usr/local/lib/firmware/cis/3CCFEM556.cis
usr/local/lib/firmware/cis/3CXEM556.cis
usr/local/lib/firmware/cis/COMpad2.cis
usr/local/lib/firmware/cis/COMpad4.cis
usr/local/lib/firmware/cis/DP83903.cis
usr/local/lib/firmware/cis/LA-PCM.cis
usr/local/lib/firmware/cis/MT5634ZLX.cis
usr/local/lib/firmware/cis/NE2K.cis
usr/local/lib/firmware/cis/PCMLM28.cis
usr/local/lib/firmware/cis/PE-200.cis
usr/local/lib/firmware/cis/PE520.cis
usr/local/lib/firmware/cis/RS-COM-2P.cis
usr/local/lib/firmware/cis/SW_555_SER.cis
usr/local/lib/firmware/cis/SW_7xx_SER.cis
usr/local/lib/firmware/cis/SW_8xx_SER.cis
usr/local/lib/firmware/cis/tamarack.cis
usr/local/lib/firmware/cpia2/stv0672_vp4.bin
usr/local/lib/firmware/ctefx.bin
usr/local/lib/firmware/ctspeq.bin
usr/local/lib/firmware/dabusb/bitstream.bin
usr/local/lib/firmware/dabusb/firmware.fw
usr/local/lib/firmware/dsp56k/bootstrap.bin
usr/local/lib/firmware/dvb-fe-xc5000-1.6.114.fw
usr/local/lib/firmware/dvb-usb-dib0700-1.20.fw
usr/local/lib/firmware/dvb-usb-terratec-h5-drxk.fw
usr/local/lib/firmware/edgeport/boot.fw
usr/local/lib/firmware/edgeport/boot2.fw
usr/local/lib/firmware/edgeport/down.fw
usr/local/lib/firmware/edgeport/down2.fw
usr/local/lib/firmware/edgeport/down3.bin
usr/local/lib/firmware/emi26/bitstream.fw
usr/local/lib/firmware/emi26/firmware.fw
usr/local/lib/firmware/emi26/loader.fw
usr/local/lib/firmware/emi62/bitstream.fw
usr/local/lib/firmware/emi62/loader.fw
usr/local/lib/firmware/emi62/midi.fw
usr/local/lib/firmware/emi62/spdif.fw
usr/local/lib/firmware/ene-ub6250/ms_init.bin
usr/local/lib/firmware/ene-ub6250/ms_rdwr.bin
usr/local/lib/firmware/ene-ub6250/msp_rdwr.bin
usr/local/lib/firmware/ene-ub6250/sd_init1.bin
usr/local/lib/firmware/ene-ub6250/sd_init2.bin
usr/local/lib/firmware/ene-ub6250/sd_rdwr.bin
usr/local/lib/firmware/ess/maestro3_assp_kernel.fw
usr/local/lib/firmware/ess/maestro3_assp_minisrc.fw
usr/local/lib/firmware/f2255usb.bin
usr/local/lib/firmware/go7007/go7007fw.bin
usr/local/lib/firmware/go7007/go7007tv.bin
usr/local/lib/firmware/go7007/lr192.fw
usr/local/lib/firmware/go7007/px-m402u.fw
usr/local/lib/firmware/go7007/px-tv402u.fw
usr/local/lib/firmware/go7007/s2250-1.fw
usr/local/lib/firmware/go7007/s2250-2.fw
usr/local/lib/firmware/go7007/wis-startrek.fw
usr/local/lib/firmware/htc_7010.fw
usr/local/lib/firmware/htc_9271.fw
usr/local/lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
usr/local/lib/firmware/intel/ibt-hw-37.7.bseq
usr/local/lib/firmware/intelliport2.bin
usr/local/lib/firmware/isci/isci_firmware.bin
usr/local/lib/firmware/kaweth/new_code.bin
usr/local/lib/firmware/kaweth/new_code_fix.bin
usr/local/lib/firmware/kaweth/trigger_code.bin
usr/local/lib/firmware/kaweth/trigger_code_fix.bin
usr/local/lib/firmware/keyspan/mpr.fw
usr/local/lib/firmware/keyspan/usa18x.fw
usr/local/lib/firmware/keyspan/usa19.fw
usr/local/lib/firmware/keyspan/usa19qi.fw
usr/local/lib/firmware/keyspan/usa19qw.fw
usr/local/lib/firmware/keyspan/usa19w.fw
usr/local/lib/firmware/keyspan/usa28.fw
usr/local/lib/firmware/keyspan/usa28x.fw
usr/local/lib/firmware/keyspan/usa28xa.fw
usr/local/lib/firmware/keyspan/usa28xb.fw
usr/local/lib/firmware/keyspan/usa49w.fw
usr/local/lib/firmware/keyspan/usa49wlc.fw
usr/local/lib/firmware/keyspan_pda/keyspan_pda.S
usr/local/lib/firmware/keyspan_pda/keyspan_pda.fw
usr/local/lib/firmware/keyspan_pda/xircom_pgs.S
usr/local/lib/firmware/keyspan_pda/xircom_pgs.fw
usr/local/lib/firmware/korg/k1212.dsp
usr/local/lib/firmware/lbtf_usb.bin
usr/local/lib/firmware/lgs8g75.fw
usr/local/lib/firmware/matrox/g200_warp.fw
usr/local/lib/firmware/matrox/g400_warp.fw
usr/local/lib/firmware/mt7650.bin
usr/local/lib/firmware/mts_cdma.fw
usr/local/lib/firmware/mts_edge.fw
usr/local/lib/firmware/mts_gsm.fw
usr/local/lib/firmware/mts_mt9234mu.fw
usr/local/lib/firmware/mts_mt9234zba.fw
usr/local/lib/firmware/myricom/lanai.bin
usr/local/lib/firmware/ositech/Xilinx7OD.bin
usr/local/lib/firmware/ql2100_fw.bin
usr/local/lib/firmware/ql2200_fw.bin
usr/local/lib/firmware/ql2300_fw.bin
usr/local/lib/firmware/ql2322_fw.bin
usr/local/lib/firmware/ql2400_fw.bin
usr/local/lib/firmware/ql2500_fw.bin
usr/local/lib/firmware/qlogic/1040.bin
usr/local/lib/firmware/qlogic/12160.bin
usr/local/lib/firmware/qlogic/1280.bin
usr/local/lib/firmware/qlogic/isp1000.bin
usr/local/lib/firmware/qlogic/sd7220.fw
usr/local/lib/firmware/r128/r128_cce.bin
usr/local/lib/firmware/rp2.fw
usr/local/lib/firmware/s2250.fw
usr/local/lib/firmware/s2250_loader.fw
usr/local/lib/firmware/s5p-mfc/s5p-mfc-v6.fw
usr/local/lib/firmware/s5p-mfc/s5p-mfc.fw
usr/local/lib/firmware/sb16/alaw_main.csp
usr/local/lib/firmware/sb16/ima_adpcm_capture.csp
usr/local/lib/firmware/sb16/ima_adpcm_init.csp
usr/local/lib/firmware/sb16/ima_adpcm_playback.csp
usr/local/lib/firmware/sb16/mulaw_main.csp
usr/local/lib/firmware/slicoss/gbdownload.sys
usr/local/lib/firmware/slicoss/gbrcvucode.sys
usr/local/lib/firmware/slicoss/oasisdbgdownload.sys
usr/local/lib/firmware/slicoss/oasisdownload.sys
usr/local/lib/firmware/slicoss/oasisrcvucode.sys
usr/local/lib/firmware/sun/cassini.bin
usr/local/lib/firmware/sxg/saharadbgdownloadB.sys
usr/local/lib/firmware/sxg/saharadownloadB.sys
usr/local/lib/firmware/tehuti/bdx.bin
usr/local/lib/firmware/ti_3410.fw
usr/local/lib/firmware/ti_5052.fw
usr/local/lib/firmware/tlg2300_firmware.bin
usr/local/lib/firmware/tr_smctr.bin
usr/local/lib/firmware/ttusb-budget/dspbootcode.bin
usr/local/lib/firmware/usbdux_firmware.bin
usr/local/lib/firmware/usbduxfast_firmware.bin
usr/local/lib/firmware/usbduxsigma_firmware.bin
usr/local/lib/firmware/v4l-cx231xx-avcore-01.fw
usr/local/lib/firmware/v4l-cx23418-apu.fw
usr/local/lib/firmware/v4l-cx23418-cpu.fw
usr/local/lib/firmware/v4l-cx23418-dig.fw
usr/local/lib/firmware/v4l-cx23885-avcore-01.fw
usr/local/lib/firmware/v4l-cx25840.fw
usr/local/lib/firmware/vicam/firmware.fw
usr/local/lib/firmware/vntwusb.fw
usr/local/lib/firmware/whiteheat.fw
usr/local/lib/firmware/whiteheat_loader.fw
usr/local/lib/firmware/yam/1200.bin
usr/local/lib/firmware/yam/9600.bin
usr/local/lib/firmware/yamaha/ds1_ctrl.fw
usr/local/lib/firmware/yamaha/ds1_dsp.fw
usr/local/lib/firmware/yamaha/ds1e_ctrl.fw
usr/local/lib/firmware/yamaha/yss225_registers.bin

Lets say I need firmware "9600.bin" for a yam device;  I would open Apps gui and search for 9600.bin under the "Provides" search feature of Apps gui.   The 9600.bin firmware will be found in firmware.tcz so that extension will be displayed. I then install it with onboot option selected.  Simple huh?

another example, lets say I need firmware "rtl8712u.bin" for a Realtek WiFi device;  I would open Apps gui and search for rtl8712u.bin under the "Provides" search feature of Apps gui.   The rtl8712u.bin firmware will be found in firmware-rtlwifi.tcz so that extension will be displayed. I then install it with onboot option selected.

We usually install software only for the devices we might use on a regular basis.  It's just not efficient to have all software mounted in the off chance you might install an old device at some later point in time which needs that driver/firmware, likely by then a newer device might be available which may require a new driver to support it.. 
If you provide an ISO for many folks who needs to support a wide range of hardware (CorePlus for example) for a one off application or install,  then by all means install all in the onboot list, but normally that's inefficient for your personal installation



« Last Edit: April 07, 2014, 01:11:28 PM by coreplayer2 »

Offline Mike7

  • Full Member
  • ***
  • Posts: 143
Re: How install an external USB wireless adaptor?
« Reply #21 on: April 07, 2014, 06:34:13 PM »
Rich-

Quote
I got 3 from this:
Code: [Select]
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

The number on the left is the index number of the device. That is what you pass to rfkill.

Okay, I get it.

Quote
Don't be afraid to take advice from coreplayer2. He has far more experience with wireless than I do.

Yes, he has been answering a lot of questions for me, in personal messages as well as here.

You're not suggesting that I abandon your rfkill fix in favor of coreplayer2's blacklist?

M.
Asus eeePC 1000HA, Intel Atom N270 CPU, 1GB RAM, 160GB HDD, CorePlus-5.1 on 8GB flash drive.

Offline Mike7

  • Full Member
  • ***
  • Posts: 143
Re: How install an external USB wireless adaptor?
« Reply #22 on: April 07, 2014, 06:45:13 PM »
coreplayer2-

I'd like to try out your blacklist method, but first I need answers to the questions about it in my reply #18 above.

Mike
Asus eeePC 1000HA, Intel Atom N270 CPU, 1GB RAM, 160GB HDD, CorePlus-5.1 on 8GB flash drive.

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 2514
Re: How install an external USB wireless adaptor?
« Reply #23 on: April 07, 2014, 09:36:15 PM »
You might need both the rfkill and blacklist methods..

But it's time to get the WiFi dongle up and running,  one thing at once..

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 5430
Re: How install an external USB wireless adaptor?
« Reply #24 on: April 07, 2014, 09:43:28 PM »
Hi Mike7
Quote
You're not suggesting that I abandon your rfkill fix in favor of coreplayer2's blacklist?
I suggested rfkill because based on the error message it seemed appropriate. There may be other ways to unblock and get
your wireless adapter up. My wireless experience consists of setting up my laptop which went without incident. Coreplayer2
on the other hand has actual hands on experience with multiple adapters. I would suggest following his advice and get your
adapter up and running. After that, you can still work out a couple of scripts to switch between adapters if needed.

Offline Mike7

  • Full Member
  • ***
  • Posts: 143
Re: How install an external USB wireless adaptor?
« Reply #25 on: April 07, 2014, 10:42:39 PM »
Rich (and everyone)-

Strangely, every time I plug in the external adapter and run "sudo rfkill list all" I get different device and index numbers for things. Weird.

Anyway, here's what I did:

With the Internal adaptor on and connected to the Internet, TP-Link unplugged:
Code: [Select]
tc@box:~$ sudo rfkill list all
0: eeepc-wlan: Wireless LAN
        Soft blocked: no
        Hard blocked: no
3: phy2: Wireless LAN
        Soft blocked: no
        Hard blocked: no
       
With the internal adapter on and connected, TP-Link plugged in:
Code: [Select]
tc@box:~$ sudo rfkill list all
0: eeepc-wlan: Wireless LAN
        Soft blocked: no
        Hard blocked: no
3: phy2: Wireless LAN
        Soft blocked: no
        Hard blocked: no
4: phy3: Wireless LAN
        Soft blocked: no
        Hard blocked: no

With the internal adapter on but disconnected from the Internet, TP-Link plugged in:
Code: [Select]
tc@box:~$ sudo rfkill list all
0: eeepc-wlan: Wireless LAN
        Soft blocked: no
        Hard blocked: no
3: phy2: Wireless LAN
        Soft blocked: no
        Hard blocked: no
4: phy3: Wireless LAN
        Soft blocked: no
        Hard blocked: no
(but LED on the external adapter still off)

Int adaptor off, disconnected, TP-Link plugged in:
Code: [Select]
tc@box:~$ sudo rfkill list all
0: eeepc-wlan: Wireless LAN
        Soft blocked: yes
        Hard blocked: no
4: phy3: Wireless LAN
        Soft blocked: yes
        Hard blocked: no

At this point I ran:

Code: [Select]
sudo rfkill unblock 4
and was able to run the wifi app and connect to the internet, and the LED on the external adapter went on!

and:

Code: [Select]
tc@box:~$ sudo rfkill list all
0: eeepc-wlan: Wireless LAN
        Soft blocked: yes
        Hard blocked: no
4: phy3: Wireless LAN
        Soft blocked: no
        Hard blocked: no

So. . . rfkill works to enable the external adapter. The only thing is that I have to find out its index number every time I plug it in (no big problem).

If I knew how to write scripts maybe I could automate the process, but it's easy enough to do it this way.

Now, if coreplayer2 will answer my questions above, I'll try his blacklist method and see which one works best for me.

Cheers!

Mike
Asus eeePC 1000HA, Intel Atom N270 CPU, 1GB RAM, 160GB HDD, CorePlus-5.1 on 8GB flash drive.

Offline Mike7

  • Full Member
  • ***
  • Posts: 143
Re: How install an external USB wireless adaptor?
« Reply #26 on: April 08, 2014, 07:09:46 PM »
Rich and all-

I've been tinkering some more with rfkill and the wireless adapter hardware switch, and I figured out a setup where I can switch between the internal and external adapters by simply plugging and unplugging the external one. No terminal commands needed. This is the best solution of all. The only question is whether or not this setup will hold through successive boots. If not, I'll be forced to try and write a script for it <grin>.

After such unexpected success, I hate to be downbeat. But a problem cropped up that sort of eliminates the use of 0cf3:1006: it doesn't capture the WEP-encrypted wifi signal that I wanted to use it for. Which is very strange because 0cf3:1006 does see that network when used with the WindowsXP and Puppy network managers. Also, it's the networl with the highest signal strength.

Another network, a local low-powered non-encrypted one, is registered by all three network managers when using 0cf3:1006. So the problem must have something to do with the way 0cf3:1006 is configured in Core, or the way it interfaces with Core's wifi app.

Anyone care to tackle this? It's the last stumbling block before breaking out the champagne <grin>.

Mike

Asus eeePC 1000HA, Intel Atom N270 CPU, 1GB RAM, 160GB HDD, CorePlus-5.1 on 8GB flash drive.

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 2514
Re: How install an external USB wireless adaptor?
« Reply #27 on: April 08, 2014, 10:01:20 PM »
I'd use two boot menu items.  One menu item boots to the built-in device whilst blacklisting the external device.   The other boot menu item will boot with external device support whilst blacklisting the built-in device.    Simply select which device you want to provide support for at the boot menu.  This is an improvised solution for simplicity, may not be the most correct either.

An example extlinux.conf boot file modified from one of my own config files
Code: [Select]
DEFAULT internal
UI menu.c32
PROMPT 0
TIMEOUT 50
ONTIMEOUT internal
F1 f1
F2 f2
F3 f3
F4 f4

MENU TITLE Boot Menu
MENU MARGIN 10
MENU VSHIFT 5
MENU ROWS 5
MENU TABMSGROW 14
MENU TABMSG Press ENTER to boot, TAB to edit, or press F1 for more information.
MENU HELPMSGROW 15
MENU HELPMSGENDROW -3
MENU AUTOBOOT BIOS default device boot in # second{,s}...

LABEL internal
MENU LABEL Internal WiFi
TEXT HELP

Boot with Built-in WiFi support
ENDTEXT
KERNEL /tce/boot/vmlinuz
APPEND initrd=/tce/boot/core.gz loglevel=3 noswap waitusb=5:UUID="3295e2df-4ee6-48d6-ba9c-d6c2912c189e" tce=UUID="3295e2df-4ee6-48d6-ba9c-d6c2912c189e" blacklist=ath9k_htc

LABEL external
MENU LABEL External WiFi
TEXT HELP

Boot with external USB WiFi
ENDTEXT
KERNEL /tce/boot/vmlinuz
APPEND initrd=/tce/boot/core.gz loglevel=3 noswap waitusb=5:UUID="3295e2df-4ee6-48d6-ba9c-d6c2912c189e" tce=UUID="3295e2df-4ee6-48d6-ba9c-d6c2912c189e" blacklist=iwlwifi (replace iwlwifi with name of module for internal WiFi chip)



obviously replace the UUID with your USB UUID and add the module name for the built-in WiFi device
« Last Edit: April 08, 2014, 11:54:07 PM by coreplayer2 »

Offline Mike7

  • Full Member
  • ***
  • Posts: 143
Re: How install an external USB wireless adaptor?
« Reply #28 on: April 11, 2014, 04:09:40 PM »
coreplayer2-

That's very interesting, and I appreciate the trouble you've gone to. I'm making a copy of the extlinux.conf file.

However, it's moot at this point because, like I said above, the external device isn't capturing (or at least not registering) the WEP-encrypted network I'm after.

I haven't given up the idea of using it, as my use of Core depends on it. But someone will have to help me configure it so that it does capture that signal. It can (see above), but for some reason isn't, not with Core.

Mike
Asus eeePC 1000HA, Intel Atom N270 CPU, 1GB RAM, 160GB HDD, CorePlus-5.1 on 8GB flash drive.