@
Tolkem Thanks for the tip on nano /etc/modprobe.d/blacklist.conf.
This version of Q4OS / 32 bit is using a TRINITY desktop and "nano /etc/modprobe.d/blacklist.conf" cannot be found in the CLI , or, I should say that it opens a large blank space with a menu across the bottom.
The first text, which is highlighted, reads
"Directory 'etc/modprobe.d' is not writable."
Below this text is a selection menu:
^G Get Help ^O Write Out ^W Where is ^K Cut Text ^J Justify (and so on)
Included in the menu is ^X for Exit.
Up-carat plus x, or plus X. or any combination of ALT, CTRL, Fn or SHIFT, nor x by itself nor X by itself, does anything to exit that menu, or even close the TERMINAL.
QUESTION #1:
What does ^X actually translate into in the form of key combinations?
QUESTION #2:
If the Debian driver package for the Linksys WPC564G-2 has been installed .....
==========================
dpkg --list | grep firmware-b43-installer
ii firmware-b43-installer 1:019-4
==========================
... what is the next step in un-blacklisting it, or, stated another way;
How do I get this device and its driver to wake up and operate the PCMCIA WLAN card? (BTW it is Wireless G).
As always
Thanks in advance.
========================
EDIT: AFTER LOADING PUPPY LINUX
========================
The PCMCIA WLAN card (Linksys WPC54G-2) was recognized upon boot process, network detected and logged in once password was entered. Indeed, this entry is made by the same Vaio machine running Puppy from a CD.
Prognosis: Lubuntu-based LXLE recognizes the hardware upon bootup, Linux Puppy, 32-bit, does too.
Unfortunately, Q4OS does not.
@Q4OSteam, can you address this please?