How To: Properly Install Proprietary Drivers in Ubuntu

There is some confusion about installing the proprietary drivers in Ubuntu. This article hopes to clear that up by telling you how to properly install drivers in Ubuntu.

First, this only works for the drivers that Ubuntu has access to. In this case, it’s usually things like graphics cards, sound cards, some networking gear, and things like that. 

Ubuntu does not have all the possible drivers. If you have to go get them from GitHub and compile them yourself, this obviously isn’t the article for you.

One of the most confusing is the Nvidia video card drivers. If you use Ubuntu, an official flavor of Ubuntu, or a derivative of Ubuntu, DO NOT download the .run file from Nvidia’s site. While it may work, it will quite possibly not work with dkms and you will have to spend significant time fixing it every time the kernel is updated. It quite likely lead to breakage. 

Yes, this means having some patience. But, have some patience because the drivers will make it down to the repos and will have then been tested. The drivers you get from the official repos will not only update, they’ll update with the rest of the system AND they’ll work properly with the kernel updates. When the kernel updates, the system itself will insert the appropriate drivers calls.

Doing this any other way will quite likely lead to hardship – and it’s a hardship that you don’t need to have. It’s a hardship that’s easily avoided. If you read the forums and question/answer sites, doing this the wrong way results in at least one question almost every single day.

The first way is easy. It’s even in the GUI. Search your menu for ‘Additional Drivers’ or similar (it may be only listed as “Software & Updates” depending on your Ubuntu flavor). It looks like this:

add additional drivers via gui
This should be self-explanatory, so I will just leave this here.

See? Pretty easy. Just pick what you want, apply the changes, and reboot.

NOTE: You will need to have the ‘restricted’ repository enabled in order to do this. That should be assumed, but some of you may not know this. So, a quick screenshot should make this even easier to figure out – it’s in the same app as the above screenshot, but it’s in the first tab. It looks a little like this:

enable restricted repo
The arrow should make it clear. That repo needs to be enabled for this.

The second way is to use the terminal. Let’s go ahead and get the terminal opened by pressing CTRL + ALT + T on your keyboard.

Now, let’s check and see what drivers we can automatically install from the terminal:

The output should let you know what drivers are available for your devices. Again, this is pretty self-explanatory. You really don’t even need to enter that command, you can do it all automatically and get the recommended drivers automatically installed. It’s easy. Just run this:

That will go through and install the recommended drivers for your devices automatically. That will install the proprietary drivers, the ones with binary blobs and decidedly not opensource drivers. If those are the drivers you want, that’s the easiest way to install them.

Simply run the command, reboot, and you’re done. Not only are you done, you shouldn’t have to mess with them again – ever again. They will update automatically, they will automatically be applied when you update the kernel, and they will generally just work.

For the time being, we’re ignoring the idea of using the opensource drivers. I’ll simply say that I do quite well without needing proprietary drivers. I hardly ever bother installing them – unless I absolutely need a feature that’s not offered with the opensource drivers. I find that it’s still a working operating system and I can still easily meet my goals. You do you and you make the decision, but at least do it the right way after making that decision.

As always, thanks for reading. There’s a newsletter that will email you when a new article is published. That’s all it does. If you’re wanting to keep up with the site, that’s exactly how you do it! Well, there are push notifications available for those that prefer that. So, you do have choices! Either way, I won’t send you any spam. I promise!

Smash a Button
[Total: 0 Average: 0]
About Me: I'm just some retired dude with a little bit more free time on my hands. If you want to support the site, why not help yourself out too by ordering some inexpensive web hosting so that you can start your own site?


Install ‘Docky’ on Ubuntu 20.04+

Docky is a Linux application that provides a dock for applications you’d frequently use. It’s no longer in the default repositories. This is how you install Docky on newer versions of Ubuntu. 

First, open your terminal.

Next, you’ll need Docky’s dependencies:

Now, let’s install them all at once:

Alright, you’ve now taken care of the dependencies. Let’s grab the Docky .deb:

And, of course, you can now install it:

There. You now have a running/working Docky and you can customize it and use it just like you did on older versions of Ubuntu. This should, of course, work with all official flavors of Ubuntu and with those distros that base themselves on Ubuntu’s 20.04+ version.

Smash a Button
[Total: 1 Average: 4]
About Me: I'm just some retired dude with a little bit more free time on my hands. If you want to support the site, why not help yourself out too by ordering some inexpensive web hosting so that you can start your own site?


Check Your Ubuntu Support Status

Want to know how long your version of Ubuntu is supported? You can find the support status by cracking open your terminal and entering:

ubuntu-support-status

If you’re using 20.04 or newer, then the command is slightly different:

ubuntu-security-status

Smash a Button
[Total: 0 Average: 0]
About Me: I'm just some retired dude with a little bit more free time on my hands. If you want to support the site, why not help yourself out too by ordering some inexpensive web hosting so that you can start your own site?


Use Wayland in a Live Instance of Ubuntu

This is from an AU question that I answered. The person wanted to know how to use Wayland while in a live instance of Ubuntu. It is something you can do.

The first thing you need to do, assuming you’re already booted into the live instance of Ubuntu, is change the way you login. You can click in the bottom right and ‘Show Applications.’ Once there, you can enter the word ‘users’, click on the settings app offered, and disable logging in automatically.

When you’re done with that, change the password. It turns out this is mandatory – and perhaps a bug. You’ll need to deal with Ubuntu’s need for a complex password, so just make sure it’s at least 12 characters long, not a dictionary word, and has a mix of numbers and letters. Yes, even in the live instance that’s temporary they want a complex password meeting whatever criteria they set.

Next, you want to edit /etc/gdm3/custom.conf and comment out the line that disables Wayland.

Find the line:

Change it to:

Make sure to save it, obviously.

Restart gdm3 with:

Note: That may log you out, that’s fine. If it doesn’t automatically, log out manually.

Log back in, but after you click the user, there’s an icon in the lower right. It’s a gear icon. Click it and choose  Ubuntu on Wayland. Then enter your password and press ENTER.

If everything worked, you’re logged in with Wayland.

Now, to verify this…

Press CTRL + ALT + T and open the terminal and enter:

Which should tell you that you’re using Wayland. If done correctly, it looks like this:

Good luck!

Smash a Button
[Total: 0 Average: 0]
About Me: I'm just some retired dude with a little bit more free time on my hands. If you want to support the site, why not help yourself out too by ordering some inexpensive web hosting so that you can start your own site?