General TC > Tiny Core Netbooks

How install an external USB wireless adaptor?

<< < (5/6) > >>

coreplayer2:

--- Quote from: Mike7 on April 06, 2014, 04:44:28 PM ---
--- Quote ---remove all unnecessary firmware extensions that you might have and you should be good to go
--- End quote ---

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?

--- End quote ---



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: ---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
--- End code ---

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



Mike7:
Rich-


--- Quote ---I got 3 from this:

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

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

Okay, I get it.


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

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.

Mike7:
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

coreplayer2:
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..

Rich:
Hi Mike7

--- Quote ---You're not suggesting that I abandon your rfkill fix in favor of coreplayer2's blacklist?
--- End quote ---
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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version