Terrance

@David I don't remember everything I said. Maybe that is good? All I remember was getting very frustrated over it all. Maybe I shouldn't answer questions at the end of my day when I am tired (and grumpy). :)

@andrew.46 No argument from me on that one! :D

@andrew.46. Indeed! For now, I am just going to stay away from that one and possible questions from them in the near future just to let things cool down more. If someone else wants to tackle that one that would be cool! As for me, I really don't know how to answer that one other than what I did. And I don't need my blood pressure shooting through the roof. :)

@andrew.46. That works too! I am thinking though that there really was a language gap there happening on that one.

@andrew.46 I did. It was getting heated on that one. I think I was letting my frustrations get the most of me as it seemed like OP was looking for a specific answer. I was trying to give them information about a simple renaming of the backup files back since there was no restore option and that isn't what they wanted to hear. But now that I have had today to cool down, I will drop it from here.

I got lost on askubuntu.com/questions/1434622/… as OP just didn't want to read or rename or anything. Kind of wanted us to hold their hand while we figured it out for them. It was very frustrating. Too bad most comments got deleted as OP was upset that I was telling them things they already knew, but failed to mention it. Also, they don't want to rename any files or read anything else. Good luck to anyone that wants to try to help!

@David Yeah, my brain hurts more and more the more I read it. ;-)

Modifying config files has made an OS not boot, but I have never seen a system get "bricked" to the point of no return because you modified a config file.

Do people not understand what "bricking" a system actually means? askubuntu.com/questions/1402580/… and askubuntu.com/questions/1227070/… My understanding is that the term "bricking" basically means turning the system into a "brick" like a door stop. The hardware at that point is rendered useless and will not boot.

@NotTheDr01ds Agreed! I'll leave it open.

???? askubuntu.com/questions/1402550/… Maybe I should have just voted to close it? The recent comment to me made me ask, what? I have no clue at all.....

Please ignore my previous comment. I figured something out about it.

What is the point in using UA if you don't have an internet connection? askubuntu.com/questions/1402477/ubuntu-advantage-with-landscape

I think I am done with that one.

Able to connect locally when VPN is disabled but UFW is enabled. How can it be a UFW issue? askubuntu.com/questions/1398708/… As far as I know, you can only connect to a system running a VPN through the VPN.

How does one explain that a RAID1+0 or a RAID10 are the same, but also that a RAID1+0 is not a RAID0 and will not increase in speed when you add on more drives? Also, the question really does not have to do with Ubuntu specifically. askubuntu.com/questions/1368524/…

Unfortunately, I have seen systems be bad right out of the box. While rare, it can happen. Anyways, try pulling the 4GB module out and run with it. I would recommend Memtest86+, but it has a bug that doesn't work well above the 1GB range. I am currently running 24GB in my system, but I hate to say it, but Windows was the one telling me I had bad memory. It kept crashing with a memory error, and yet my Ubuntu never crashed, except for Google Chrome which was odd. There are free diagnostic tools that you can download to run on your system, Hiren's Boot CD is one I can think of.

Also, another good tool for checking max amount of RAM and available slots in a system is using sudo inxi -mx that will show you the total capacity that your motherboard can do and occupied or empty slots.

VDI in a different location doesn't matter. I run VirtualBox 6.1.32 (From VirtualBox themselves) and all my VDIs are on an external 3TB drive and never a corruption issue. Have you had your RAM checked since pretty much everything goes through RAM at one point or another? Also, have you checked all your hardware in your system? Bad motherboards can cause bus issues and file corruption. A bad power supply with a bad 12v or 5v rail can cause issues. Environmental issues around your system like fluorescent light ballasts that might be going bad putting out EMPs.

Glad you got it working. :) You can write up your own answer below to help others that may be experiencing the same issue as you. You might also want to include details of the USB LAN so that it can help others know what will work right away. I would definitely upvote your answer as well.

You might want to see askubuntu.com/questions/1241362/… and replace your package name in the answers instead of what they have.

Yes it is......

apt-get download $(apt-rdepends dkms|grep -v "^ ")

See if you can just run the sudo dpkg -i rtl8821xxxxxxxxxx file name now

Go to your Software & Updates under Settings. Then in the Other Software tab, unselect the CD-ROM. You might need to create a Live USB on another system just to give you a source.

Yes, I would go with that. I tried to see if there were any other dependencies for dkms but it looks like they are already installed into the system. apt download dkms

On one of the other Ubuntu systems that are working you can run apt download rtl8821ce-dkms then copy it to a USB drive, then install it from the USB drive on the system where the Wifi is not working.

@heynnema I am out of here!

@heynnema Help him, don't help me!

@heynnema Good to know, but the fact is here that the driver installation here is completely messed up.

Yes. That is what you run.

Your 470 driver is trying to install the 495 which won't happen. That will error out like crazy. Try reinstalling the 470 driver first.

You will have to remove the 470 driver before installing the 495 driver. After the 495 driver is installed you will have to reboot the system. sudo apt remove --autoremove nvidia-driver-470.

That's the one you need to remove It is listing the 470 driver and yet it was not installed by the sources. nvidia.com/download/driverResults.aspx/176525/en-us is the driver that you will probably need. Somehow your video drivers are completely messed up. If this fails, I am going to recommend that you backup what you have then perform a clean install of the OS, and make sure to use the Ubuntu drivers for the NVIDIA.

The ones you are seeing in the Software & Updates is what is available for installation. 495 is the newest one available. Not knowing what you installed to begin with can make it hard for me to help. In the NVIDIA X Server settings you might be able to see what version is installed. You might be able to get away with running sudo apt remove nvidia-* from a terminal window to clean up the currently installed.

Your error is showing 495 and that you should reinstall it. sudo apt install --reinstall nvidia-driver-495 But I am also seeing the 470 driver. Maybe try reinstalling the 470 driver the same way as the 495 is here.

Looks like you are going to have to uninstall the Official NVIDIA Driver. Some good instructions are linuxconfig.org/… to remove them before installing the nvidia-driver-495. But after following those instructions and before installing the nvidia-driver-495 run sudo apt update so that the sources are updated before installing.

In your error you need to correct it. Run the sudo dpkg --configure -a in a terminal window before you run anything else.

Try running that nvidia installation command in a terminal window, but first try sudo apt autoremove, then run sudo apt install nvidia-driver-495

You might need to boot back to the older kernel, remove the NVIDIA driver, then install from the Ubuntu sources ( command line: sudo apt install nvidia-driver-495). That will install the DKMS version of the driver that will carry over into new Kernel installs and updates.

How did you install the NVIDIA drivers? From the Ubuntu sources (Additional Drivers) or from NVIDIA themselves?

Anyway, I am tired of your condescending attitude you have given me here from day one, so that said, I am out of here.

My comment was about just to follow ubuntu-security-status which you did not mention at all. I know that I was late, but that was the only comment I could find at the time. Any new ones I will bring up, but it seems that we all make up our own rules. This whole damn thing though was brought up because someone was asking about a non-official release, I can't remember what is was, but it was built out on Ubuntu 18.04

askubuntu.com/questions/1342454/… has a note about the 3 year in a comment

The flavors are not there, only Ubuntu. Xubuntu 18.04 is not there.

People here seem to post about the other flavors only having 3 years. Plus, you can no longer download them after that 3 years is up!

But it is not on the official supported pages. Yoo much crap on this site!!

I'm always late, apparently... ;)

NO!!! I am not going to share it if you are just going to downvote me!!!

You know, it is interesting since I run Xubuntu 20.04 right now, and all the packages that come default state that they are supported until 4/2025 according to the ubuntu-security-status app that replaced ubuntu-support-status. Maybe we should go off the output of ubuntu-security-status?