Category: Hardware

Benchmark Your GPU In Lubuntu

Today we have a simple enough article, meant for fun and information, as we talk about how to benchmark your GPU in Lubuntu. This won’t be a very long and complicated article. Even a new user should be able to follow along.

We all like to know where we stand in life. This is true even with computers. At the very least, we want to know that our computer can accomplish the tasks we need it to accomplish. One of the ways you can do this is to benchmark your computer.

I’ve previously written a couple of articles that involve benchmarking.

Benchmark Your Linux Box With Geekbench 5
Check Disk Speed In The Terminal
Graphically Examine Hardware Info With HardInfo

So, this isn’t a foreign concept to my regular readers (whom I appreciate a great deal).

A benchmark pushes your hardware to the limits and then gives you a score telling you how well it did. Usually, the next step will be using your search engine to find out how well you did against other computers. (Those with older and slow computers may not do this, but I did with a recently purchased refurbished device, and it did not do well – but it still perfectly satisfies my needs.)

Your GPU obviously controls your graphics. I do not need massive graphic capabilities. I’m content with onboard graphics and my benchmark score shows this. At most, I’m going to stream a video, watch a movie, or play a game that doesn’t require high-end graphics.

You should know about Lubuntu already. The directions for this article are for Lubuntu, but will likely work with most other distros. For this exercise, we’ll be using glmark2.

Installing glmark2:

The first step to using glmark2 is opening your terminal. To open your terminal, CTRL + ALT + T. Then, with your terminal now open, enter the following command to ensure your system’s application database is up to date:

Let that run its course and don’t worry about upgrading at this point. You can always do that later, though I’d suggest doing so as soon as realistically possible because updates tend to contain security updates and those are important.

The next goal is to install glmark2 and you do that with this command:

If you’re not using Lubuntu and you’re using a distro with Wayland, then you want a different command. That command might be something like this:

With glmark2 now installed, it would be worth your time to check the man page. This article will only cover the very basic command, literally running the command without any flags, but there are many options available for you. To check the man page, use this command:

As you can see, there are quite a few options available. I will not be doing a deep dive into those options. You can easily figure most of them out on your own. Heck, you can probably figure them all out with a little trial and error.

Now that you have the GPU benchmarking tool, glmark2, installed in Lubuntu you can run the command in the terminal…

Benchmark Your GPU In Lubuntu:

If you’ve installed glmark2 and checked the man page, you’ll see that we’ve chosen the right tool for the job. The man page describes glmark2 as:

glmark2 – OpenGL (ES) 2.0 benchmark suite

So, assuming you’ve kept your terminal open (if not, open it again) then you need to simply use the command’s name to run a benchmark on your system. It’s that simple to benchmark your GPU in Lubuntu. Just try this command:

In theory, you should not do anything with your computer while this runs. I, of course, did not listen to that advice and I’m perfectly okay with that. As I mentioned above, my graphical needs are not high. The Intel graphics are just fine for me.

That’s going to take a while, especially on an older computer like mine – and one with just an onboard GPU. This should open a new window and display a bunch of graphics in that window. If you didn’t do this in full-screen mode, that is without any flags to set that value, you’ll also be able to see quite a lot of information scrolling by in your terminal. Someone smarter than I am can tell you what that information means.

Wait for the benchmark to end, that’s when the new window closes, and collect your score from the terminal. Mine was not very high.

Then, use your favorite search engine to see how well you did compared to other users. If you want to compare your score against other computers, you can try this OpenBenchmarking link. I’m sure there are other sites where you can compare your score with others. That’s just the one I happened to find in a very brief search.

Closure:

So, I don’t know if you actually want to benchmark your GPU in Lubuntu. If you do, now you know how. It’s not terribly complicated and it is something you can do in just a few short minutes.

You’re not supposed to use your computer at the same time, but I had dozens of windows open and was streaming a video during my benchmark. In my case, it doesn’t matter to me. I have no need for more powerful graphics and I’m content with the performance I get from this device. It’s perfectly capable of meeting my needs.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Show Your Graphics Card Version

Today’s article will not be all that complicated, consisting of just one real command that will show your graphics card version. This is information handy for things like finding drivers or for troubleshooting. You might also use this information to verify that you got the product you ordered without having to open the case.

This article won’t have a lot of substance to it. The content is just from my notes and I figured that it was useful information to have. I’m quite certain that this knowledge is out there somewhere. I’d credit the person(s) who shared the information with me, but I don’t have that information. So, thanks for the article idea, whoever you are.

There are all sorts of ways to learn about your graphics card. Of course, there are. This is Linux! We’ll just be covering one way to learn this information and to display this information in the terminal. That sounds just like the kind of thing we do here on Linux-Tips.

This time around, we’ll be installing an application. The application may not be installed by default in some distros, so we’ll cover the installation process as well. Ideally, even a brand-new user can follow along with this article. They’ll need to cut and paste as they learn a little about an application known as glxinfo.

About glxinfo:

The glxinfo application may not be installed by default and you may need to install it. You’ll find that it briefly describes itself as this:

glxinfo – show information about the GLX implementation

Importantly, the man page elaborates, giving more information:

The glxinfo program shows information about the OpenGL and GLX implementations running on a given X display.

The information includes details about the server and client-side GLX implementation, the OpenGL and GLU implementations as well as a list of available GLX visuals.

So, you can do more with glxinfo than just get the graphics card version. The odds are good that we’ll revisit glxinfo in a future article. It’s a good thing that you’ve already installed it by the time that article rolls off the presses!

Installing glxinfo:

We’ll be installing glxinfo with the terminal. You can usually just press CTRL + ALT + T and your default terminal will open up. If it doesn’t, you can assign it as a keyboard shortcut and open it from the application menu.

You may have glxinfo installed already, you can run the following command. If any information comes out the other side, you have glxinfo already installed and can skip the installation section:

With your terminal open (and you’ll need it for the next section), you may need to start this process by installing glxinfo. You should find that glxinfo is available for most distros, so use the appropriate command below:

Debian/Ubuntu/etc:

SUSE/OpenSUSE/etc:

RHEL/Fedora/etc:

Arch/Manjaro/etc:

I’m not 100% sure of the following, but:

Gentoo:

One of those should work to install glxinfo. Which one will depend on the package manager you’re using. I don’t have enough experience with Gentoo, but Google tells me that’s the command you want.

Now that you have glxinfo installed…

Show Your Graphics Card Version:

It’s hopefully true that you installed glxinfo and left your terminal open after that. If you didn’t, you’ll need to open your terminal again. You need an open terminal to run the glxinfo application. So, if you closed the terminal you should open it again now.

The first thing you can check is glxinfo’s man page. That’s nice and simple:

As you see, there aren’t a whole lot of options – but there’s a whole lot of information involved. If you want, you can just run this command:

See what I mean about being overwhelmed with information?

Fortunately, we only want to show the graphics card version. That means we can use grep for this exercise. To just show your graphics card version (and a little superfluous information, narrowed down nicely), you would want to use this command:

As you can see, the command uses grep to show fields with the vendor, the device, and the version number. That’s all you need to know for this exercise, though glxinfo does provide a great deal of additional information.

Closure:

Well, that’s about it for this article – and it is another article. This one can come in handy for things like new computers or reminding yourself what you have installed. It’s a quick and easy way to show your graphics card version and a handy application with a bunch of information. It has more information about your graphics than I’d care to know. I’m not even sure what to do with all that information.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

How To: Make A Linux Install USB

Today’s article is going to be a rather basic article, with worthwhile information, about how to make a Linux install USB. This won’t be too complicated, even if it looks complicated initially. It probably won’t even be a very long article.

If you want to install Linux, you will need some sort of install medium. That can be almost any sort of drive, including some distros that are still small enough to fit on a CD. Heck, if you can get your computer to boot to it, you could even use a MicroSD as your installation media.

We’ll be doing this in the terminal. Why? Well, because it’s not that hard and it’s a fairly universal process. You won’t even need to install anything new! But, if you don’t have any interest in doing this in the terminal (or if you’re not using Linux right now) you can always do this with a GUI. See the following article for more details:

balenaEtcher: A Tool To Turn Linux .ISO Files Into Bootable USB Drives

There’s also Rufus, should you be using a Windows computer. You have options outside of the terminal. Though, I haven’t done an article on using Rufus. I don’t have any Windows devices. (If you want to write said article, feel free to let me know. I love guest articles.)

What You Need:

These are the tools you’ll want to have available. It’s not a long list, so we won’t have too much to deal with.

  1. A blank USB drive, large enough to hold the data.
  2. Any distro with lsblk.
  3. The ability to unmount a disk.
  4. A distro with the dd command.

So, I’ll assume you have the first aspect covered. Everything else is software. They’re standard tools that are available on all but the tiniest of distros.

The first tool is lsblk, which the man page describes as:

lsblk – list block devices

Then you’ll need the obverse of mount, which is unmount. This is a part of the mount command. It doesn’t have a command of its own. That mount command is described as:

mount – mount a filesystem

And, finally, you’ll need the dd command. That’s simply described as:

dd – convert and copy a file

And that’ll be all you need. Well, you’ll need an open terminal, of course! So, let’s cover one way that you can…

Make A Linux Install USB:

Like I said, you’re going to need a USB drive. This drive must be big enough to hold the data. You’ll need to insert the drive and then open the terminal. To open the terminal, just press CTRL + ALT + T or open it from your application menu.

With your USB inserted, you need to identify where it is mounted. You can do that by running the following command:

You should be able to easily identify the USB drive by the size of the drive. The data you want will begin with “sd”, often something like “sdb” or “sdc” (enumerating as you increase mounted storage devices).

Take that information and run the following command:

The next command might look complicated, but just follow the directions and you shouldn’t have any trouble as you make a Linux install USB. The command looks like this:

For example, if the disk identifier was “sdc” and the path to the .iso was something like “~/Downloads/Lubuntu_22.04.iso” the command would look like this:

Then, just wait a few minutes. Let the dd command do its thing and you’ll end up with a bootable USB drive that will let you install Linux. (This also works for other image files, of course.)

Closure:

See? It’s not that complicated to make a Linux install USB. So long as you pay attention, you won’t have much to worry about. There are a few commands that you need to worry about, but those are basic commands in this instance.

I will warn you to be absolutely certain of the path for the dd command because it has the potential to make you have a really bad day. But, if you don’t want to deal with installing a GUI application, or you are in a position where you can’t install a GUI application, this is a way for you to make a Linux USB installation drive to get yourself out of a sticky situation.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

How To: Show Disk Information With hwinfo

Today we’re going to be having some fun with hwinfo, available everywhere and used (in this case) to show disk information with hwinfo. This isn’t going to be the most complicated of articles, so it’s safe to assume you can follow along – even if you’re a beginner. You just need to follow the directions.

The tool we’ll be using to show disk information will be hwinfo. This probably isn’t installed by default, but is a very useful tool. We’ll just explore one aspect of hwinfo but there’s a lot more to the application. There may be other articles on this hwinfo application.

Anyhow, if you’d already installed hwinfo and checked the man page, you’d learn that the application defines itself accurately, specifically as:

hwinfo – probe for hardware

That’s a pretty good description and might also be a bit of a clue about hwinfo’s features and goals. In this case, we’re simply examining one particular feature and that is how to show disk information with hwinfo.

I suppose that it’s a bit archaic calling it ‘disks’, but there are plenty of people with spinning platters. It could also be ‘drives’, to ensure we also cover solid-state drives. But, for this article, we’ll use the words interchangeably. After all, you know what I mean.

The hwinfo application is a great application, with a ton of options. It’d be far too much to cover in a single article. There’s enough fodder here for multiple applications, which is nice.

Install hwinfo:

As hwinfo is a terminal-based application, you’re going to need a terminal. You could trivially install this via a GUI application, but I needn’t explain that. I will show you how to install hwinfo with the terminal. It’s available for most distros by default. Just press CTRL + ALT + T to open your terminal, or open it manually from your application menu.

Once you have your terminal open, you’re ready to install hwinfo. You can pick from the following, as it’s a fairly universal application. Try one of the following to do so:

Debian/Ubuntu/etc:

SUSE/OpenSUSE/etc:

RHEL/Rocky/etc:

Arch/Manjaro/etc:

Gentoo/Calculate/etc:

See? You’ll find that hwinfo is an option in pretty much all the default reports. You can get a head start, and learn a lot, by checking the man page (with man hwinfo) if you’d like.

Show Disk Information With hwinfo:

Don’t close your terminal after installing hwinfo. You’re still going to need an open terminal to use hwinfo to show disk information. Fortunately, the commands are a bit unusual but not taxing. As we’re just covering how to show disk information, that will make it easier.

NOTE: To get complete information, you will need elevated permissions. In our case, we’ll be using sudo. If your distro doesn’t support sudo, you’ll need to gain elevated permissions in the manner your distro has designed.

So, with your still open terminal, you can try the first command, which is simply:

That will spit out a lot of information about the various disks you have in your system. It’s a lot of information, perhaps more than you need. If you want to show a nice summary, you’d want this command:

If you want to see a nice summary of block devices, you can just use the following command to show said block devices:

Most folks are either going to want the full information for troubleshooting or one of the latter two choices for basic information. But, you can use any of them that you want to show disk information. It’s a pretty easy process and hwinfo is a very useful application. Perhaps we’ll explore its uses soon.

Closure:

Well, today we have had a “Nor’easter” and the remains of Hurricane Lee. I was expecting it to be much more mild, but we have trees down and power outages all over the place. In fact, one outage has started a fire. 

However, that didn’t stop me! Nope! I have still not missed a single publication date. I’ve published an article every other day for a long time. So far, so good.

This time around, you got an article about how you can show disk information with hwinfo. That seemed like a fine article to write. It’s not all that long, nor is it all that complicated. If you follow the directions, you should be all set.

As such, I assume a beginner will be able to follow along and able to learn something in the process. I sometimes get feedback about using the terminal in so many articles, but it is a fairly universal tool. There’s no reason to be afraid of the terminal. Instead, embrace it and learn to use it. Once you do, you’ll understand why I write about it so frequently.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

A Couple More Ways To Find Your File System Type

Today we’re going to revisit a previous subject and share a couple more ways to find your file system type. I’ve covered this subject before, but I only shared a couple of ways. This being Linux, there are multiple file system types and multiple ways to find the details. So, let’s cover it again but with different options.

If you did your installation manually, you probably already know this information. You probably know the file system types you chose to use during the installation process. On the other hand, if you did your installation by just letting the installer use the defaults, you might not know this information. This may also be something like an unknown computer you’re tasked with fixing. So, there are real-world reasons why you might want to know the file system types in use.

If you want to visit the previous article, you can find that here:

How To: Find The File System Type

You could easily have multiple file system types in use right now. This is quite likely if you’re dual-booting with Windows or you’re using EFI as your boot method. You could even have external disks formatted in all sorts of file types.

All of these various file types may need specific commands to repair them and maintain them. You don’t want to go using the wrong tool for the wrong file type. That’d likely make your problems even worse. So, this is good information to have and this article will show you how to find your file system type.

Find Your File System Type:

This requires an open terminal. Like many of these articles, we’ll be using a terminal. It’s painless and it’s a good idea to know some of these commands. The terminal is fairly universal, so you can open your terminal (usually) by pressing CTRL + ALT + T.

In the previous article, we used lsblk and we also used df. Those are both excellent tools and excellent ways to get this information. They’re simple and easily memorized. The two commands we’ll use today will be similar in those regards. This truly is not a complicated task, it’s just fun to cover the different methods that one could use.

Using The mount Command:

The first command we’re going to learn about is the mount command. Don’t worry, this is part of your standard installation and you won’t need to do anything extra to use it. You can check the man page with man mount if you’d like. If you did do so, you’d find that the mount application is described as:

mount – mount a filesystem

No, we won’t be mounting and unmounting anything. We’ll just be using the command to find your file system types. That command’s syntax would look like this:

That’s the command that will show you all of your drives and all of the drive’s file system types in one go. I plugged a couple of external drives in so that I could run the command and show you the expected output:

using the mount command to find the file system type
You can see that there are vfat and ext4 file systems in use. That’s normal. It’s all good!

There’s nothing too eccentric in that output. Those are fairly normal file systems as far as Linux systems go. There are more. There are many more. You can check a list of file system types on Wikipedia.

Using The fsck Command:

Yes, you can even use the fsck command to find the file system types. You’re telling the command to not actually run and just spit out some information, so there’s nothing laborious or complicated with this command. You will need to know the path to the disk in question. I’m sure you know how to do that. Heck, the first command in this article will do that for you.

When you do this with the fsck command, you’re doing so on a disk-by-disk method. If you’re unfamiliar with the fsck command, you can check the man page with man fsck. Once again, you won’t have to install anything. The fsck command is a part of the standard base, files you’ll find on pretty much every distro by default. Anyhow, the man page describes fsck as:

fsck – check and repair a Linux filesystem

We will not be repairing a Linux filesystem (I’ve intentionally stylized this as ‘file system’ as it appears both spellings are in common usage) but we will sort of be checking them. We won’t be checking them for errors because that’d take too long and isn’t a part of this article. If you do want to check your file systems for errors with fsck, you should read this article:

How To: Check A Disk For Errors

Or maybe this article:

Repair Your Linux Filesystem With a Live USB or DVD

Anyhow, if you want to find your file system type with fsck, the syntax is simile and is as follows:

This is usually going to start with a /dev and then the drives populate  (enumerate?) as is logical. You would have drive sda, then partitions on that drive might be sda1, sda2, etc… So, an example command might be:

An example output is as follows:

you can use the fsck command to find the file system type for a specific drive
This only really works on one drive/partition at a time. That’s plenty useful.

See? Pretty useful if you need to know a file system type before working on it.

Closure:

So, we’ve covered a couple of new ways for you to find your file system type. This time around, we’ve used fsck and mount and both of them are perfectly useful for this application. If you work on multiple computers, if you work on someone else’s computers, if you work on remote computers, etc. then these commands may come in useful. 

Plus, this seemed like a fun article to write. There are all sorts of older articles that could have more information added to them. Some of the older articles contain errors that should be fixed. Some could use being written again but with a more suitable format.

A couple of the articles are just plain garbage and should have been deleted. They weren’t… They should have been, but they weren’t. I should probably go back and write those over again in their entirety. I’ve completely blown it a few times. I do like to point out that I probably learn more than you do by writing these articles and (importantly) getting feedback on them. I do love some feedback, though it’d be cool if it was left here when it adds something to the article.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Subscribe To Our Newsletter
Get notified when new articles are published! It's free and I won't send you any spam.
.
Linux Tips
Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.