How to Install and Uninstall driverctl.noarch Package on Fedora 34
Last updated: November 28,2024
1. Install "driverctl.noarch" package
Please follow the step by step instructions below to install driverctl.noarch on Fedora 34
$
sudo dnf update
Copied
$
sudo dnf install
driverctl.noarch
Copied
2. Uninstall "driverctl.noarch" package
This tutorial shows how to uninstall driverctl.noarch on Fedora 34:
$
sudo dnf remove
driverctl.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the driverctl.noarch package on Fedora 34
Last metadata expiration check: 5:02:52 ago on Tue Sep 6 02:10:55 2022.
Available Packages
Name : driverctl
Version : 0.101
Release : 6.fc34
Architecture : noarch
Size : 25 k
Source : driverctl-0.101-6.fc34.src.rpm
Repository : fedora
Summary : Device driver control utility
URL : https://gitlab.com/driverctl/driverctl
License : LGPLv2
Description : driverctl is a tool for manipulating and inspecting the system
: device driver choices.
:
: Devices are normally assigned to their sole designated kernel driver
: by default. However in some situations it may be desireable to
: override that default, for example to try an older driver to
: work around a regression in a driver or to try an experimental alternative
: driver. Another common use-case is pass-through drivers and driver
: stubs to allow userspace to drive the device, such as in case of
: virtualization.
:
: driverctl integrates with udev to support overriding
: driver selection for both cold- and hotplugged devices from the
: moment of discovery, but can also change already assigned drivers,
: assuming they are not in use by the system. The driver overrides
: created by driverctl are persistent across system reboots
: by default.
Available Packages
Name : driverctl
Version : 0.101
Release : 6.fc34
Architecture : noarch
Size : 25 k
Source : driverctl-0.101-6.fc34.src.rpm
Repository : fedora
Summary : Device driver control utility
URL : https://gitlab.com/driverctl/driverctl
License : LGPLv2
Description : driverctl is a tool for manipulating and inspecting the system
: device driver choices.
:
: Devices are normally assigned to their sole designated kernel driver
: by default. However in some situations it may be desireable to
: override that default, for example to try an older driver to
: work around a regression in a driver or to try an experimental alternative
: driver. Another common use-case is pass-through drivers and driver
: stubs to allow userspace to drive the device, such as in case of
: virtualization.
:
: driverctl integrates with udev to support overriding
: driver selection for both cold- and hotplugged devices from the
: moment of discovery, but can also change already assigned drivers,
: assuming they are not in use by the system. The driver overrides
: created by driverctl are persistent across system reboots
: by default.