Join Chaim Krause for an in-depth discussion in this video Manage drivers, part of SUSE Linux Enterprise Server Essential Training.
- [Instructor] Let's take a look at managing drivers. First of all let's see what drivers are loaded. They're loaded as kernel modules. So what we do is we do an ls of the modules, and we get a listing of what is loaded, how big the driver is, and how many things depend on it. So for example if we take a look at dm_mod, we can see that it's one dependency, and that's dm_multipath.
If we want to find out information about that particular driver, we do mod info on dm_mod, and we will get information about that driver. Information about what its alias is, what version driver we got loaded, who signed it, and then we got a list of parameters that we can use so when we load the driver, these parameters can be set to affect how the driver works.
Let's take a look again at what is loaded and I happen to know that if we go to the top of this list, there's e1000. Which is a network card driver, and it's used by zero. So nobody's dependent upon it. The reason I picked that one is so we can, let's clear our screen here, we can do a mod probe with a -r, to remove that driver.
So we do that and we don't get any errors. Now we can do another ls mod, and grep for e1000, and we can see that it's no longer included in the list of loaded drivers. How do we load it manually? We do mod probe e1000. And now we've manually loaded the driver. So if I do a list of the loaded modules, we now see that e1000 shows up.
Let's clear our screen, and I'm in a particular directory of importance for modules, and that is etsy mod probe.d. Let's do a listing of this directory, and what's you see are a bunch of configurations scripts. These are what's loaded automatically and with the parameters that are required for your system. A comment I wanna make about this is that with the modern versions of Linux that we have, they're much better at detecting hardware and loading the appropriate drivers.
So less so now than you had to before, will you have to mock with these drivers manually, and make manual changes. Most likely the case is you've got a particular driver that is giving you some problems and you'll have to tweak it. But if you're running SUSE Linux Enterprise Server, you'll probably be wanting to stick with certified hardware, and then this won't be an issue. So this is something to keep in your back pocket, in case it comes up.
- What is SUSE Linux Enterprise?
- Installing SLES
- Linux file types
- Working at the command line
- Managing processes
- Working with background processes
- Managing users and groups
- Changing file permissions
- Configuring network interfaces
- Displaying hardware information
- Managing drivers