Removing a Program

[Bart]

I did an install for a booster to pick internet from the house to an outbuilding by just hooking up the booster & it installed a program automatically which it has never done before now I always get 2 bar reception indication on my 2.2 lite system most of the time it tries to hook up with out the program with 2 bars indicated & when the window comes up asking if I want to use the program I say no & it hooks up 3-5 bars indicated reception there seems to be a clash between the 2 ways of hooking up here. On the other laptop I get 4-5 bar indication all the time without the program. Where do I have to look in the Lite 2.2 system to find this program & remove it?

[Scott(0)]

Hi Bart,

Where do I have to look in the Lite 2.2 system to find this program & remove it?

Here's a link to the LL online user manual. Scroll down to the section Installing & Removing Software.
https://www.freecinema2022.gq/manual/software.html

Does that help?

[anon222]

Hello,
In case you installed it from the repository.
Ctrl+Alt+T to start the command line
then type in

Code:

gksudo synaptic

That will open a synaptic package manager.
There you can find the package you installed and remove it.

In case you compiled it from source:
cd into the directory where you compiled the program

Code:

cd /path/to/

Then run

Code:

make uninstall

or

Code:

sudo make uninstall

[Bart]

Neither one of these suggestions helped. It wasn't installed from the list. It was automatically installed when I plugged in the hardware this didn't happen on my windows based laptop I would have had to install it from the CD.

[N4RPS]

Hello!

Welcome to Linux Lite.

Sadly for your situation, it will auto-install at every startup, because support for the offending wireless chipset is built into the Linux kernel itself. You can try not turning it on until after you boot, to see what happens. I imagine, though, that the kernel would once again auto-detect it.

Unless someone's written something to 'switch off' selective parts of the kernel, I'm afraid that to uninstall the offending driver, you would have to:

Get the source code for the kernel (easy enough),

then remove the offending driver(s) from the kernel source,

find and remove anything ELSE in the kernel that calls on those drivers to be there,

and then compile the modified kernel source into your own custom kernel.

Additionally, you would have to repeat that whole process every time the kernel is updated. Sorry for all the bad news.

I run a second wireless router here as a repeater, also. Keep in mind that going through any repeater or other 'range booster' will cut your data speed to half that of the primary router...

73 DE N4RPS
Rob

[Wirezfree]

Hi,

I have been following this thread, and I'm curious.?

Can you tell us what the "Boosters" device is, name/model.??

When you say "Hook it Up", do mean physically plug the Booster into your Laptops.?
If you are plugging it in, what type of cable is it.??

I possibly have an idea, because a friend had a similar situation who wanted to "extend" his range.
He had bought a Wireless Adapter/Bridge by mistake, which was plugged in via USB,

"Boosters" or "Range Extenders" are "not" normally plugged into a PC/Laptop
You normally configure them through it's web admin page by connecting to it's default address.
You then select your main Routers "WiFi" Name(SSID) from a list, and then enter your WiFi key.
The extender is now linked to your main router.

Depending on the device/config it may have it's own default name, or it may just append a "-1" to the name(SSID) of main router.
So from your Laptop will now see your main router and a new device in it's Wireless list, You now connect to the new device.

From then on your Laptop should just roam/associate between your main router and the new device.



Dave

[AustinTexas]

Sadly for your situation, it will auto-install at every startup, because support for the offending wireless chipset is built into the Linux kernel itself. You can try not turning it on until after you boot, to see what happens. I imagine, though, that the kernel would once again auto-detect it.

Unless someone's written something to 'switch off' selective parts of the kernel, I'm afraid that to uninstall the offending driver, you would have to:

Get the source code for the kernel (easy enough),

then remove the offending driver(s) from the kernel source,

find and remove anything ELSE in the kernel that calls on those drivers to be there,

and then compile the modified kernel source into your own custom kernel.

Wouldn't it simply be a matter of blacklisting that particular module?
sudo gedit /etc/modprobe.d/blacklist.conf




Bart

To list all manually installed programs enter this command:

Code:

zgrep 'get install' /var/log/apt/history.log*