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?
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?
sometimes the built-in device is automatically re-enabled when it's least wanted
Not good, but weird things happen all the time <grin>.
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.
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?
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?
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.
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?
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?
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.
Welcome
FAQ
Downloads
Wiki
